test.com

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

Registration

info

.com generic · Network Solutions, LLC · expires 2027-06-17

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Network Solutions, LLC
Registered
18 June 1997
Last changed
18 April 2025
Expires
17 June 2027
Status
client transfer prohibited
Registry nameservers
ns1.safesecureweb.com, ns2.safesecureweb.com, ns3.safesecureweb.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-06-17 #3
    The registration is valid until 2027-06-17 (237 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

warn

ns1.safesecureweb.com, ns2.safesecureweb.com, ns3.safesecureweb.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.safesecureweb.com, ns2.safesecureweb.com, ns3.safesecureweb.com
NS in the zone
ns1.safesecureweb.com, ns2.safesecureweb.com, ns3.safesecureweb.com
NameserverAddressesNetwork (AS)Glue
ns1.safesecureweb.com204.12.76.1AS20021 LNH-INC - Ntirety, Inc., US204.12.76.1
ns2.safesecureweb.com76.12.92.1AS20021 LNH-INC - Ntirety, Inc., US76.12.92.1
ns3.safesecureweb.com216.74.36.1AS20021 LNH-INC - Ntirety, Inc., US216.74.36.1

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.safesecureweb.com, ns2.safesecureweb.com, ns3.safesecureweb.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 3 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS20021 (LNH-INC - Ntirety, 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.safesecureweb.com 204.12.76.1NOERROR, 106 ms, authoritativenoyes / yesrefused9.9.11-HDC-20170731
ns2.safesecureweb.com 76.12.92.1NOERROR, 107 ms, authoritativenoyes / yesrefused9.9.11-HDC-20170731
ns3.safesecureweb.com 216.74.36.1NOERROR, 138 ms, authoritativenoyes / yesrefused9.9.11-HDC-20170731

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.safesecureweb.com: "9.9.11-HDC-20170731"; ns2.safesecureweb.com: "9.9.11-HDC-20170731"; ns3.safesecureweb.com: "9.9.11-HDC-20170731". 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 534 · primary ns1.safesecureweb.com

Found

Primary (MNAME)
ns1.safesecureweb.com
Contact (RNAME)
jposch.testcentral.com
Serial
534
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.safesecureweb.com (204.12.76.1)534
ns2.safesecureweb.com (76.12.92.1)534
ns3.safesecureweb.com (216.74.36.1)534

Checks

  • ✓ Serial 534 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.safesecureweb.com is one of the listed nameservers.
  • ✓ Contact jposch@testcentral.com #25
    The SOA RNAME jposch.testcentral.com means jposch@testcentral.com.
  • ✓ Counter serial #26
    The serial 534 is a plain counter.

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

7 records at the apex

Found

Read from
204.12.76.1:53
TypeValueTTL
SOAns1.safesecureweb.com. jposch.testcentral.com. 534 10800 3600 604800 36003600
NSns1.safesecureweb.com.3600
NSns2.safesecureweb.com.3600
NSns3.safesecureweb.com.3600
TXT"google-site-verification=kW9t2V_S7WjOX57zq0tP8Ae_WJhRwUcZoqpdEkvuXJk"3600
TXT"9dad2f5b-fa2d-4141-8ee6-d26ec6994d18"3600
TXT"55d34914-636b-4a56-b349-fdb9f2c1eaca"3600

Checks

  • ✓ TTLs within range #32
    TTLs: NS 1h. The NS TTL at the parent is 2d and in the zone 1h; 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
  • 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