xanga.com

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

Registration

info

.com generic · PDR Ltd. d/b/a PublicDomainRegistry.com · expires 2027-04-03

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
PDR Ltd. d/b/a PublicDomainRegistry.com
Registered
3 April 1999
Last changed
1 March 2026
Expires
3 April 2027
Status
client transfer prohibited
Registry nameservers
cody.ns.cloudflare.com, ivy.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 2027-04-03 #3
    The registration is valid until 2027-04-03 (162 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

cody.ns.cloudflare.com, ivy.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
cody.ns.cloudflare.com, ivy.ns.cloudflare.com
NS in the zone
cody.ns.cloudflare.com, ivy.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
cody.ns.cloudflare.com173.245.59.107 108.162.193.107 172.64.33.107 2803:f800:50::6ca2:c16b 2606:4700:58::adf5:3b6b 2a06:98c1:50::ac40:216bAS13335 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.107 172.64.33.107 173.245.59.107 2606:4700:58::adf5:3b6b 2803:f800:50::6ca2:c16b 2a06:98c1:50::ac40:216b
ivy.ns.cloudflare.com108.162.192.120 172.64.32.120 173.245.58.120 2803:f800:50::6ca2:c078 2a06:98c1:50::ac40:2078 2606:4700:50::adf5:3a78AS13335 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.120 172.64.32.120 173.245.58.120 2606:4700:50::adf5:3a78 2803:f800:50::6ca2:c078 2a06:98c1:50::ac40:2078

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: cody.ns.cloudflare.com, ivy.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
cody.ns.cloudflare.com 173.245.59.107NOERROR, 17 ms, authoritativenoyes / yesrefused2026.10.2
cody.ns.cloudflare.com 108.162.193.107NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
cody.ns.cloudflare.com 172.64.33.107NOERROR, 14 ms, authoritativenoyes / yesrefused2026.10.2
cody.ns.cloudflare.com 2803:f800:50::6ca2:c16bNOERROR, 21 ms, authoritativenoyes / yesrefused2026.10.2
cody.ns.cloudflare.com 2606:4700:58::adf5:3b6bNOERROR, 21 ms, authoritativenoyes / yesrefused2026.10.2
cody.ns.cloudflare.com 2a06:98c1:50::ac40:216bNOERROR, 21 ms, authoritativenoyes / yesrefused2026.10.2
ivy.ns.cloudflare.com 108.162.192.120NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
ivy.ns.cloudflare.com 172.64.32.120NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
ivy.ns.cloudflare.com 173.245.58.120NOERROR, 15 ms, authoritativenoyes / yesrefused2026.10.2
ivy.ns.cloudflare.com 2803:f800:50::6ca2:c078NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
ivy.ns.cloudflare.com 2a06:98c1:50::ac40:2078NOERROR, 16 ms, authoritativenoyes / yesrefused2026.10.2
ivy.ns.cloudflare.com 2606:4700:50::adf5:3a78NOERROR, 15 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: cody.ns.cloudflare.com: "2026.10.2"; ivy.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 2417642161 · primary cody.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
cody.ns.cloudflare.com (173.245.59.107)2417642161
cody.ns.cloudflare.com (108.162.193.107)2417642161
cody.ns.cloudflare.com (172.64.33.107)2417642161
cody.ns.cloudflare.com (2803:f800:50::6ca2:c16b)2417642161
cody.ns.cloudflare.com (2606:4700:58::adf5:3b6b)2417642161
cody.ns.cloudflare.com (2a06:98c1:50::ac40:216b)2417642161
ivy.ns.cloudflare.com (108.162.192.120)2417642161
ivy.ns.cloudflare.com (172.64.32.120)2417642161
ivy.ns.cloudflare.com (173.245.58.120)2417642161
ivy.ns.cloudflare.com (2803:f800:50::6ca2:c078)2417642161
ivy.ns.cloudflare.com (2a06:98c1:50::ac40:2078)2417642161
ivy.ns.cloudflare.com (2606:4700:50::adf5:3a78)2417642161

Checks

  • ✓ Serial 2417642161 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 cody.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 2417642161 is a Unix timestamp (2046-08-11 23:16 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

12 records at the apex

Found

Read from
173.245.59.107:53
TypeValueTTL
SOAcody.ns.cloudflare.com. dns.cloudflare.com. 2417642161 10000 2400 604800 18001800
NScody.ns.cloudflare.com.86400
NSivy.ns.cloudflare.com.86400
A192.95.33.1633600
MX1 aspmx.l.google.com.3600
MX10 aspmx2.googlemail.com.3600
MX10 aspmx3.googlemail.com.3600
MX30 aspmx4.googlemail.com.3600
MX30 aspmx5.googlemail.com.3600
MX5 alt1.aspmx.l.google.com.3600
MX5 alt2.aspmx.l.google.com.3600
TXT"v=spf1 ip4:192.95.33.163 include:_spf.google.com -all"3600

Checks

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