visitportugal.com

Checked 22 October 2026, 11:22 UTC · via 8.8.8.8
✗Problems found
22 passed 5 warnings 1 failed 3 info

Registration

warn

.com generic · eNom, LLC · expires 2026-11-06

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
eNom, LLC
Registered
6 November 2001
Last changed
11 August 2025
Expires
6 November 2026
Status
client transfer prohibited
Registry nameservers
dns1.host-redirect.com, dns2.host-redirect.com, dns3.host-redirect.com, dns4.host-redirect.com
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • !
    Expires in 14 days
    The registration expires on 2026-11-06. Make sure it is renewed.
    #3
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

dns1.host-redirect.com, dns2.host-redirect.com, dns3.host-redirect.com, dns4.host-redirect.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns1.host-redirect.com, dns2.host-redirect.com, dns3.host-redirect.com, dns4.host-redirect.com
NS in the zone
dns1.host-redirect.com, dns2.host-redirect.com, dns3.host-redirect.com, dns4.host-redirect.com
NameserverAddressesNetwork (AS)Glue
dns1.host-redirect.com91.198.47.1 2001:4cc0:4:1::5AS33876 Flesk-AS - DMNS - DOMINIOS, S.A., PT AS5533 CLARANET-PT - Claranet Portugal S.A, PT2001:4cc0:4:1::5 91.198.47.1
dns2.host-redirect.com194.8.30.2 2001:4cc0:4:10::5AS33876 Flesk-AS - DMNS - DOMINIOS, S.A., PT AS5533 CLARANET-PT - Claranet Portugal S.A, PT194.8.30.2 2001:4cc0:4:10::5
dns3.host-redirect.com94.126.175.203 2001:4cc0:4:3::5AS33876 Flesk-AS - DMNS - DOMINIOS, S.A., PT AS5533 CLARANET-PT - Claranet Portugal S.A, PT2001:4cc0:4:3::5 94.126.175.203
dns4.host-redirect.com185.15.23.202 2001:4cc0:3:a::6dfeAS24768 ALMOUROLTEC - ALMOUROLTEC SERVICOS DE INFORMATICA E INTERNET LDA, PT AS5533 CLARANET-PT - Claranet Portugal S.A, PT185.15.23.202

Checks

  • ✓ 4 nameservers #6
    Delegated to dns1.host-redirect.com, dns2.host-redirect.com, dns3.host-redirect.com, dns4.host-redirect.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: dns4.host-redirect.com (glue 185.15.23.202, zone 185.15.23.202, 2001:4cc0:3:a::6dfe). Update the glue at your registrar.
    #8
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 4 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS24768 (ALMOUROLTEC - ALMOUROLTEC SERVICOS DE INFORMATICA E INTERNET LDA, PT): 1 address; AS33876 (Flesk-AS - DMNS - DOMINIOS, S.A., PT): 3 addresses; AS5533 (CLARANET-PT - Claranet Portugal S.A, PT): 4 addresses.
  • i
    All nameserver names under .com
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

6 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns1.host-redirect.com 91.198.47.1NOERROR, 42 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.0 (built Nov 30 2017 10:16:12 by mockbuild@jenkins.monshouwer.eu)
dns1.host-redirect.com 2001:4cc0:4:1::5no responsenono / no--
dns2.host-redirect.com 194.8.30.2NOERROR, 43 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.0 (built Nov 30 2017 10:16:12 by mockbuild@jenkins.monshouwer.eu)
dns2.host-redirect.com 2001:4cc0:4:10::5NOERROR, 44 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.0 (built Nov 30 2017 10:16:12 by mockbuild@jenkins.monshouwer.eu)
dns3.host-redirect.com 94.126.175.203NOERROR, 43 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.0 (built Nov 30 2017 10:16:12 by mockbuild@jenkins.monshouwer.eu)
dns3.host-redirect.com 2001:4cc0:4:3::5NOERROR, 43 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.0 (built Nov 30 2017 10:16:12 by mockbuild@jenkins.monshouwer.eu)
dns4.host-redirect.com 185.15.23.202NOERROR, 39 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.1.14
dns4.host-redirect.com 2001:4cc0:3:a::6dfeno responsenono / no--

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: dns1.host-redirect.com (2001:4cc0:4:1::5): read udp [2a01:4f8:1c1c:eebf::1]:50228->[2001:4cc0:4:1::5]:53: i/o timeout; dns4.host-redirect.com (2001:4cc0:3:a::6dfe): read udp [2a01:4f8:1c1c:eebf::1]:34156->[2001:4cc0:3:a::6dfe]:53: i/o timeout.
    #14
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: dns1.host-redirect.com: "PowerDNS Authoritative Server 4.1.0 (built Nov 30 2017 10:16:12 by mockbuild@jenkins.monshouwer.eu)"; dns2.host-redirect.com: "PowerDNS Authoritative Server 4.1.0 (built Nov 30 2017 10:16:12 by mockbuild@jenkins.monshouwer.eu)"; dns3.host-redirect.com: "PowerDNS Authoritative Server 4.1.0 (built Nov 30 2017 10:16:12 by mockbuild@jenkins.monshouwer.eu)"; dns4.host-redirect.com: "PowerDNS Authoritative Server 4.1.14". Hide or replace the version string.
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2026061900 · primary dns1.host-redirect.com

Found

Primary (MNAME)
dns1.host-redirect.com
Contact (RNAME)
hostmaster.visitportugal.com
Serial
2026061900
Refresh / retry
3600 s / 600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
dns1.host-redirect.com (91.198.47.1)2026061900
dns2.host-redirect.com (194.8.30.2)2026061900
dns2.host-redirect.com (2001:4cc0:4:10::5)2026061900
dns3.host-redirect.com (94.126.175.203)2026061900
dns3.host-redirect.com (2001:4cc0:4:3::5)2026061900
dns4.host-redirect.com (185.15.23.202)2026061900

Checks

  • ✓ Serial 2026061900 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 10m, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns1.host-redirect.com is one of the listed nameservers.
  • ✓ Contact hostmaster@visitportugal.com #25
    The SOA RNAME hostmaster.visitportugal.com means hostmaster@visitportugal.com.
  • ✓ Date-based serial #26
    The serial 2026061900 follows the YYYYMMDDnn convention (2026-06-19).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Records

warn

9 records at the apex

Found

Read from
91.198.47.1:53
TypeValueTTL
SOAdns1.host-redirect.com. hostmaster.visitportugal.com. 2026061900 3600 600 604800 36007200
NSdns2.host-redirect.com.7200
NSdns1.host-redirect.com.7200
NSdns3.host-redirect.com.7200
NSdns4.host-redirect.com.7200
A195.225.181.13860
MX1 visitportugal-com.mail.protection.outlook.com.60
TXT"v=spf1 mx a ip4:195.23.58.153 ip4:195.225.181.131 include:spf.protection.outlook.com ~all"3600
TXT"MS=ms37059831"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 2h; resolvers may use either.
    #32
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35