numbeo.com

Checked 22 October 2026, 10:04 UTC · via 8.8.8.8
!Passed with warnings
23 passed 3 warnings 0 failed 5 info

Registration

info

.com generic · DreamHost, LLC · expires 2027-04-27

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
DreamHost, LLC
Registered
27 April 2009
Last changed
26 March 2025
Expires
27 April 2027
Status
active
Registry nameservers
ns1.dreamhost.com, ns2.dreamhost.com, ns3.dreamhost.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 on 2027-04-27 #3
    The registration is valid until 2027-04-27 (187 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.dreamhost.com, ns2.dreamhost.com, ns3.dreamhost.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.dreamhost.com, ns2.dreamhost.com, ns3.dreamhost.com
NS in the zone
ns1.dreamhost.com, ns2.dreamhost.com, ns3.dreamhost.com
NameserverAddressesNetwork (AS)Glue
ns1.dreamhost.com162.159.26.14AS13335 CLOUDFLARENET - Cloudflare, Inc., US162.159.26.14
ns2.dreamhost.com162.159.26.81AS13335 CLOUDFLARENET - Cloudflare, Inc., US162.159.26.81
ns3.dreamhost.com162.159.27.84AS13335 CLOUDFLARENET - Cloudflare, Inc., US162.159.27.84

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.dreamhost.com, ns2.dreamhost.com, ns3.dreamhost.com.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ 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 2 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 3 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.dreamhost.com 162.159.26.14NOERROR, 93 ms, authoritativenoyes / yesrefused2026.10.8
ns2.dreamhost.com 162.159.26.81NOERROR, 93 ms, authoritativenoyes / yesrefused2026.10.8
ns3.dreamhost.com 162.159.27.84NOERROR, 93 ms, authoritativenoyes / yesrefused2026.10.8

Checks

  • ✓ All respond #14
    All 3 nameserver addresses answered.
  • ✓ 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: ns1.dreamhost.com: "2026.10.8"; ns2.dreamhost.com: "2026.10.8"; ns3.dreamhost.com: "2026.10.8". 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 2025110604 · primary ns1.dreamhost.com

Found

Primary (MNAME)
ns1.dreamhost.com
Contact (RNAME)
hostmaster.dreamhost.com
Serial
2025110604
Refresh / retry
20853 s / 600 s
Expire
1814400 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.dreamhost.com (162.159.26.14)2025110604
ns2.dreamhost.com (162.159.26.81)2025110604
ns3.dreamhost.com (162.159.27.84)2025110604

Checks

  • ✓ Serial 2025110604 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 5h47m33s, retry 10m, expire 21d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.dreamhost.com is one of the listed nameservers.
  • ✓ Contact hostmaster@dreamhost.com #25
    The SOA RNAME hostmaster.dreamhost.com means hostmaster@dreamhost.com.
  • ✓ Date-based serial #26
    The serial 2025110604 follows the YYYYMMDDnn convention (2025-11-06).

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

info

16 records at the apex

Found

Read from
162.159.26.14:53
TypeValueTTL
SOAns1.dreamhost.com. hostmaster.dreamhost.com. 2025110604 20853 600 1814400 300300
NSns3.dreamhost.com.14400
NSns1.dreamhost.com.14400
NSns2.dreamhost.com.14400
A135.181.18.181300
MX20 ALT1.ASPMX.L.GOOGLE.com.300
MX30 ASPMX4.GOOGLEMAIL.com.300
MX30 ASPMX3.GOOGLEMAIL.com.300
MX20 ALT2.ASPMX.L.GOOGLE.com.300
MX10 ASPMX.L.GOOGLE.com.300
MX30 ASPMX5.GOOGLEMAIL.com.300
MX30 ASPMX2.GOOGLEMAIL.com.300
TXT"v=DMARC1; p=quarantine; aspf=r; adkim=r; pct=80; rua=mailto:root@numbeo.com"300
TXT"google-site-verification=2Z3BsFDVkcWwxuix86SaQE4N8KH-oHQTa5dE2XGgAKo"300
TXT"v=spf1 a mx include:_spf.google.com ~all"300
CAA0 issuewild "letsencrypt.org"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 4h. The NS TTL at the parent is 2d and in the zone 4h; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org.