acme.com

Checked 22 October 2026, 07:40 UTC · via 8.8.8.8
✗Problems found
24 passed 1 warning 1 failed 5 info

Registration

info

.com generic · eNom, LLC · expires 2027-04-18

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
eNom, LLC
Registered
17 April 1991
Last changed
17 April 2026
Expires
18 April 2027
Status
client transfer prohibited
Registry nameservers
ns1.hover.com, ns2.hover.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-18 #3
    The registration is valid until 2027-04-18 (177 days).
  • ✓ 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

info

ns1.hover.com, ns2.hover.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.hover.com, ns2.hover.com
NS in the zone
ns1.hover.com, ns2.hover.com
NameserverAddressesNetwork (AS)Glue
ns1.hover.com216.40.47.26 2604:4000:0:d:216:40:47:26AS15348 TUCOWS - Tucows.com Co., CA AS15348 TUCOWS - Tucows.com Co., CA216.40.47.26 2604:4000:0:d:216:40:47:26
ns2.hover.com64.98.148.13 2604:4000:2800:d:64:99:148:13AS32491 TUCOWS-3 - Tucows.com Co., CA AS32491 TUCOWS-3 - Tucows.com Co., CA2604:4000:2800:d:64:99:148:13 64.98.148.13

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.hover.com, ns2.hover.com.
    #6
  • ✓ 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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS15348 (TUCOWS - Tucows.com Co., CA): 2 addresses; AS32491 (TUCOWS-3 - Tucows.com Co., CA): 2 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

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.hover.com 216.40.47.26NOERROR, 100 ms, authoritativenoyes / yesrefusedhoverpg-dns
ns1.hover.com 2604:4000:0:d:216:40:47:26NOERROR, 94 ms, authoritativenono / yesrefusedhoverpg-dns
ns2.hover.com 64.98.148.13NOERROR, 122 ms, authoritativenoyes / yesrefusedhoverpg-dns
ns2.hover.com 2604:4000:2800:d:64:99:148:13NOERROR, 122 ms, authoritativenoyes / yesrefusedhoverpg-dns

Checks

  • ✓ All respond #14
    All 4 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.hover.com: "hoverpg-dns"; ns2.hover.com: "hoverpg-dns".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.hover.com (2604:4000:0:d:216:40:47:26): read tcp [2a01:4f8:1c1c:eebf::1]:46348->[2604:4000:0:d:216:40:47:26]:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 1772076125 · primary ns1.hover.com

Found

Primary (MNAME)
ns1.hover.com
Contact (RNAME)
dnsmaster.hover.com
Serial
1772076125
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.hover.com (216.40.47.26)1772076125
ns1.hover.com (2604:4000:0:d:216:40:47:26)1772076125
ns2.hover.com (64.98.148.13)1772076125
ns2.hover.com (2604:4000:2800:d:64:99:148:13)1772076125

Checks

  • ✓ Serial 1772076125 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.hover.com is one of the listed nameservers.
  • ✓ Contact dnsmaster@hover.com #25
    The SOA RNAME dnsmaster.hover.com means dnsmaster@hover.com.
  • ✓ Timestamp serial #26
    The serial 1772076125 is a Unix timestamp (2026-02-26 03:22 UTC).

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

4 records at the apex

Found

Read from
216.40.47.26:53
TypeValueTTL
SOAns1.hover.com. dnsmaster.hover.com. 1772076125 10800 3600 604800 300900
NSns2.hover.com.900
NSns1.hover.com.900
A184.23.246.145900

Checks

  • ✓ TTLs within range #32
    TTLs: A 15m, NS 15m. The NS TTL at the parent is 2d and in the zone 15m; resolvers may use either.
  • ✓ 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