thecrimson.com

Checked 22 October 2026, 11:02 UTC · via 8.8.8.8
!Passed with warnings
24 passed 2 warnings 0 failed 5 info

Registration

info

.com generic · Tucows Domains Inc. · expires 2030-07-03

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Tucows Domains Inc.
Registered
4 July 1997
Last changed
7 December 2025
Expires
3 July 2030
Status
client transfer prohibited, client update prohibited
Registry nameservers
chan.ns.cloudflare.com, yichun.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 2030-07-03 #3
    The registration is valid until 2030-07-03 (1349 days).
  • ✓ Transfer locked #4
    Registry status: 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

chan.ns.cloudflare.com, yichun.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
chan.ns.cloudflare.com, yichun.ns.cloudflare.com
NS in the zone
chan.ns.cloudflare.com, yichun.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
chan.ns.cloudflare.com173.245.58.82 172.64.32.82 108.162.192.82 2803:f800:50::6ca2:c052 2606:4700:50::adf5:3a52 2a06:98c1:50::ac40:2052AS13335 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.82 172.64.32.82 173.245.58.82 2606:4700:50::adf5:3a52 2803:f800:50::6ca2:c052 2a06:98c1:50::ac40:2052
yichun.ns.cloudflare.com108.162.193.248 172.64.33.248 173.245.59.248 2a06:98c1:50::ac40:21f8 2803:f800:50::6ca2:c1f8 2606:4700:58::adf5:3bf8AS13335 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.248 172.64.33.248 173.245.59.248 2606:4700:58::adf5:3bf8 2803:f800:50::6ca2:c1f8 2a06:98c1:50::ac40:21f8

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: chan.ns.cloudflare.com, yichun.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
chan.ns.cloudflare.com 173.245.58.82NOERROR, 7 ms, authoritativenoyes / yesrefused2026.10.2
chan.ns.cloudflare.com 172.64.32.82NOERROR, 7 ms, authoritativenoyes / yesrefused2026.10.2
chan.ns.cloudflare.com 108.162.192.82NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
chan.ns.cloudflare.com 2803:f800:50::6ca2:c052NOERROR, 7 ms, authoritativenoyes / yesrefused2026.10.2
chan.ns.cloudflare.com 2606:4700:50::adf5:3a52NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
chan.ns.cloudflare.com 2a06:98c1:50::ac40:2052NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
yichun.ns.cloudflare.com 108.162.193.248NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
yichun.ns.cloudflare.com 172.64.33.248NOERROR, 10 ms, authoritativenoyes / yesrefused2026.10.2
yichun.ns.cloudflare.com 173.245.59.248NOERROR, 7 ms, authoritativenoyes / yesrefused2026.10.2
yichun.ns.cloudflare.com 2a06:98c1:50::ac40:21f8NOERROR, 8 ms, authoritativenoyes / yesrefused2026.10.2
yichun.ns.cloudflare.com 2803:f800:50::6ca2:c1f8NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
yichun.ns.cloudflare.com 2606:4700:58::adf5:3bf8NOERROR, 5 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: chan.ns.cloudflare.com: "2026.10.2"; yichun.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 2416949164 · primary chan.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
chan.ns.cloudflare.com (173.245.58.82)2416949164
chan.ns.cloudflare.com (172.64.32.82)2416949164
chan.ns.cloudflare.com (108.162.192.82)2416949164
chan.ns.cloudflare.com (2803:f800:50::6ca2:c052)2416949164
chan.ns.cloudflare.com (2606:4700:50::adf5:3a52)2416949164
chan.ns.cloudflare.com (2a06:98c1:50::ac40:2052)2416949164
yichun.ns.cloudflare.com (108.162.193.248)2416949164
yichun.ns.cloudflare.com (172.64.33.248)2416949164
yichun.ns.cloudflare.com (173.245.59.248)2416949164
yichun.ns.cloudflare.com (2a06:98c1:50::ac40:21f8)2416949164
yichun.ns.cloudflare.com (2803:f800:50::6ca2:c1f8)2416949164
yichun.ns.cloudflare.com (2606:4700:58::adf5:3bf8)2416949164

Checks

  • ✓ Serial 2416949164 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 chan.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 2416949164 is a Unix timestamp (2046-08-03 22:46 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

22 records at the apex

Found

Read from
173.245.58.82:53
TypeValueTTL
SOAchan.ns.cloudflare.com. dns.cloudflare.com. 2416949164 10000 2400 604800 18001800
NSchan.ns.cloudflare.com.86400
NSyichun.ns.cloudflare.com.86400
A104.26.11.24300
A104.26.10.24300
A172.67.69.155300
AAAA2606:4700:20::681a:a18300
AAAA2606:4700:20::ac43:459b300
AAAA2606:4700:20::681a:b18300
MX1 aspmx.l.google.com.300
MX10 aspmx2.googlemail.com.300
MX5 alt1.aspmx.l.google.com.300
MX5 alt2.aspmx.l.google.com.300
MX8 aspmx3.googlemail.com.300
TXT"google-site-verification=0gedn3m1G899nbBiuVoT5eSkhhKSn6dlWV8ZVqUrWAA"300
TXT"google-site-verification=Bc2mavk4zJ06JnNGlSdJAaPXsQeWGkG5KIKJMwYa4VA"300
TXT"google-site-verification=S8W2lMDWzUGmvXg0weczzkaBMDKULjVqRLw4X_FGC_A"300
TXT"google-site-verification=fdluDl-kC_f4IyybfhURNvCyMLMOcOpBi_Mptm4TWv4"300
TXT"google-site-verification=hB3V4xG4hjpF48YyVB0F7s0CkL6hU_Zo3LxHYZb-j1o"300
TXT"google-site-verification=hhPRNRXS8gFocM89wq9A8-B-mR_l0xeM1p9BXKJqtUY"300
TXT"spf2.0/pra include:amazonses.com ?all"300
TXT"v=spf1 include:amazonses.com include:_spf.google.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.
  • ✓ 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