yourdomain.com

Checked 22 October 2026, 11:41 UTC · via 8.8.8.8
!Passed with warnings
25 passed 1 warning 0 failed 5 info

Registration

info

.com generic · GoDaddy.com, LLC · expires 2030-05-21

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
20 May 1997
Last changed
22 December 2023
Expires
21 May 2030
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns03.domaincontrol.com, ns04.domaincontrol.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 2030-05-21 #3
    The registration is valid until 2030-05-21 (1306 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns03.domaincontrol.com, ns04.domaincontrol.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns03.domaincontrol.com, ns04.domaincontrol.com
NS in the zone
ns03.domaincontrol.com, ns04.domaincontrol.com
NameserverAddressesNetwork (AS)Glue
ns03.domaincontrol.com97.74.101.2 2603:5:2150::2AS26496 AS-26496-GO-DADDY-COM-LLC - GoDaddy.com, LLC, US AS44273 GODADDY-DNS - Host Europe GmbH, DE2603:5:2150::2 97.74.101.2
ns04.domaincontrol.com173.201.69.2 2603:5:2250::2AS44273 GODADDY-DNS - Host Europe GmbH, DE AS44273 GODADDY-DNS - Host Europe GmbH, DE173.201.69.2 2603:5:2250::2

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns03.domaincontrol.com, ns04.domaincontrol.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: AS26496 (AS-26496-GO-DADDY-COM-LLC - GoDaddy.com, LLC, US): 1 address; AS44273 (GODADDY-DNS - Host Europe GmbH, DE): 3 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

pass

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns03.domaincontrol.com 97.74.101.2NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns03.domaincontrol.com 2603:5:2150::2NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns04.domaincontrol.com 173.201.69.2NOERROR, 3 ms, authoritativenoyes / yesrefused-
ns04.domaincontrol.com 2603:5:2250::2NOERROR, 4 ms, authoritativenoyes / yesrefused-

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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2025012300 · primary ns03.domaincontrol.com

Found

Primary (MNAME)
ns03.domaincontrol.com
Contact (RNAME)
dns.jomax.net
Serial
2025012300
Refresh / retry
28800 s / 7200 s
Expire
604800 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
ns03.domaincontrol.com (97.74.101.2)2025012300
ns03.domaincontrol.com (2603:5:2150::2)2025012300
ns04.domaincontrol.com (173.201.69.2)2025012300
ns04.domaincontrol.com (2603:5:2250::2)2025012300

Checks

  • ✓ Serial 2025012300 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 2h, expire 7d, negative TTL 10m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns03.domaincontrol.com is one of the listed nameservers.
  • ✓ Contact dns@jomax.net #25
    The SOA RNAME dns.jomax.net means dns@jomax.net.
  • ✓ Date-based serial #26
    The serial 2025012300 follows the YYYYMMDDnn convention (2025-01-23).

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

13 records at the apex

Found

Read from
97.74.101.2:53
TypeValueTTL
SOAns03.domaincontrol.com. dns.jomax.net. 2025012300 28800 7200 604800 6003600
NSns03.domaincontrol.com.3600
NSns04.domaincontrol.com.3600
A192.124.249.6600
MX1 aspmx.l.google.com.3600
MX5 alt1.aspmx.l.google.com.3600
MX5 alt2.aspmx.l.google.com.3600
MX10 alt3.aspmx.l.google.com.3600
MX10 alt4.aspmx.l.google.com.3600
TXT"_3pmpcuhp6jstt2dodbe1o3gza32x1g0"600
TXT"v=spf1 include:dc-aa8e722993._spfm.yourdomain.com ~all"600
TXT"google-site-verification=4rN5hw3d_MF7oMXmnmJurl4rQf5mWOJ9qX35hUuz7T4"600
TXT"google-gws-recovery-domain-verification=49221658"600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, MX 1h, 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