webopedia.com

Checked 22 October 2026, 11:25 UTC · via 8.8.8.8
!Passed with warnings
23 passed 2 warnings 0 failed 6 info

Registration

info

.com generic · GoDaddy.com, LLC · expires 2032-04-03

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
4 April 1998
Last changed
14 June 2024
Expires
3 April 2032
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
kanye.ns.cloudflare.com, zoe.ns.cloudflare.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 2032-04-03 #3
    The registration is valid until 2032-04-03 (1989 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

kanye.ns.cloudflare.com, zoe.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
kanye.ns.cloudflare.com, zoe.ns.cloudflare.com
NS in the zone
kanye.ns.cloudflare.com, zoe.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
kanye.ns.cloudflare.com173.245.59.189 172.64.33.189 108.162.193.189 2803:f800:50::6ca2:c1bd 2a06:98c1:50::ac40:21bd 2606:4700:58::adf5:3bbdAS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US108.162.193.189 172.64.33.189 173.245.59.189 2606:4700:58::adf5:3bbd 2803:f800:50::6ca2:c1bd 2a06:98c1:50::ac40:21bd
zoe.ns.cloudflare.com173.245.58.149 108.162.192.149 172.64.32.149 2a06:98c1:50::ac40:2095 2803:f800:50::6ca2:c095 2606:4700:50::adf5:3a95AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US AS13335 CLOUDFLARENET - Cloudflare, Inc., US108.162.192.149 172.64.32.149 173.245.58.149 2606:4700:50::adf5:3a95 2803:f800:50::6ca2:c095 2a06:98c1:50::ac40:2095

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: kanye.ns.cloudflare.com, zoe.ns.cloudflare.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 6 IPv4 /24s and 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS13335 (CLOUDFLARENET - Cloudflare, Inc., US): 12 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

warn

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
kanye.ns.cloudflare.com 173.245.59.189NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
kanye.ns.cloudflare.com 172.64.33.189NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
kanye.ns.cloudflare.com 108.162.193.189NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
kanye.ns.cloudflare.com 2803:f800:50::6ca2:c1bdNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
kanye.ns.cloudflare.com 2a06:98c1:50::ac40:21bdNOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
kanye.ns.cloudflare.com 2606:4700:58::adf5:3bbdNOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
zoe.ns.cloudflare.com 173.245.58.149NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
zoe.ns.cloudflare.com 108.162.192.149NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
zoe.ns.cloudflare.com 172.64.32.149NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
zoe.ns.cloudflare.com 2a06:98c1:50::ac40:2095NOERROR, 21 ms, authoritativenoyes / yesrefused2026.10.2
zoe.ns.cloudflare.com 2803:f800:50::6ca2:c095NOERROR, 20 ms, authoritativenoyes / yesrefused2026.10.2
zoe.ns.cloudflare.com 2606:4700:50::adf5:3a95NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2

Checks

  • ✓ All respond #14
    All 12 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: kanye.ns.cloudflare.com: "2026.10.2"; zoe.ns.cloudflare.com: "2026.10.2". 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 2417583687 · primary kanye.ns.cloudflare.com

Found

Primary (MNAME)
kanye.ns.cloudflare.com
Contact (RNAME)
dns.cloudflare.com
Serial
2417583687
Refresh / retry
10000 s / 2400 s
Expire
604800 s
Negative TTL
1800 s

Serial per nameserver

NameserverSerial
kanye.ns.cloudflare.com (173.245.59.189)2417583687
kanye.ns.cloudflare.com (172.64.33.189)2417583687
kanye.ns.cloudflare.com (108.162.193.189)2417583687
kanye.ns.cloudflare.com (2803:f800:50::6ca2:c1bd)2417583687
kanye.ns.cloudflare.com (2a06:98c1:50::ac40:21bd)2417583687
kanye.ns.cloudflare.com (2606:4700:58::adf5:3bbd)2417583687
zoe.ns.cloudflare.com (173.245.58.149)2417583687
zoe.ns.cloudflare.com (108.162.192.149)2417583687
zoe.ns.cloudflare.com (172.64.32.149)2417583687
zoe.ns.cloudflare.com (2a06:98c1:50::ac40:2095)2417583687
zoe.ns.cloudflare.com (2803:f800:50::6ca2:c095)2417583687
zoe.ns.cloudflare.com (2606:4700:50::adf5:3a95)2417583687

Checks

  • ✓ Serial 2417583687 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 2h46m40s, retry 40m, expire 7d, negative TTL 30m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver kanye.ns.cloudflare.com is one of the listed nameservers.
  • ✓ Contact dns@cloudflare.com #25
    The SOA RNAME dns.cloudflare.com means dns@cloudflare.com.
  • ✓ Timestamp serial #26
    The serial 2417583687 is a Unix timestamp (2046-08-11 07:01 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

18 records at the apex

Found

Read from
173.245.59.189:53
TypeValueTTL
SOAkanye.ns.cloudflare.com. dns.cloudflare.com. 2417583687 10000 2400 604800 18001800
NSkanye.ns.cloudflare.com.86400
NSzoe.ns.cloudflare.com.86400
A172.66.40.224300
A172.66.43.32300
AAAA2606:4700:3108::ac42:2b20300
AAAA2606:4700:3108::ac42:28e0300
MX1 aspmx.l.google.com.300
MX10 alt3.aspmx.l.google.com.300
MX10 alt4.aspmx.l.google.com.300
MX5 alt1.aspmx.l.google.com.300
MX5 alt2.aspmx.l.google.com.300
TXT"anthropic-domain-verification-e8m5pk=pRH3mKmHcGzQ7fYOh17IBbeAO"300
TXT"google-site-verification=7qoOAI8JDOSzqMJxnD2lPzlTnRCrIOjDemEhrVdTKAI"300
TXT"google-site-verification=fxbJRA9ydbkTxLEYVh9ugmIObK_SPOSaBNJw7EF9G2w"300
TXT"google-site-verification=xoos5e3oNjP-LEYrB545En037if0UyspTonml4CINPk"300
TXT"google-site-verification=y94oJL3wOCYuk9vU73_cQzx7BXfDpmB-O4o_eI5UIyQ"300
TXT"v=spf1 include:_spf.google.com include:amazonses.com ~all"300

Checks

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