travelchinaguide.com

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

Registration

info

.com generic · Network Solutions, LLC · expires 2028-10-26

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Network Solutions, LLC
Registered
27 October 1998
Last changed
9 January 2025
Expires
26 October 2028
Status
client transfer prohibited
Registry nameservers
rene.ns.cloudflare.com, reza.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 2028-10-26 #3
    The registration is valid until 2028-10-26 (734 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

rene.ns.cloudflare.com, reza.ns.cloudflare.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
rene.ns.cloudflare.com, reza.ns.cloudflare.com
NS in the zone
rene.ns.cloudflare.com, reza.ns.cloudflare.com
NameserverAddressesNetwork (AS)Glue
rene.ns.cloudflare.com172.64.35.180 162.159.44.180 108.162.195.180 2606:4700:58::a29f:2cb4 2803:f800:50::6ca2:c3b4 2a06:98c1:50::ac40:23b4AS13335 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.195.180 162.159.44.180 172.64.35.180 2606:4700:58::a29f:2cb4 2803:f800:50::6ca2:c3b4 2a06:98c1:50::ac40:23b4
reza.ns.cloudflare.com173.245.58.217 108.162.192.217 172.64.32.217 2606:4700:50::adf5:3ad9 2803:f800:50::6ca2:c0d9 2a06:98c1:50::ac40:20d9AS13335 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.217 172.64.32.217 173.245.58.217 2606:4700:50::adf5:3ad9 2803:f800:50::6ca2:c0d9 2a06:98c1:50::ac40:20d9

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: rene.ns.cloudflare.com, reza.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
rene.ns.cloudflare.com 172.64.35.180NOERROR, 7 ms, authoritativenoyes / yesrefused2026.10.2
rene.ns.cloudflare.com 162.159.44.180NOERROR, 33 ms, authoritativenoyes / yesrefused2026.10.2
rene.ns.cloudflare.com 108.162.195.180NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
rene.ns.cloudflare.com 2606:4700:58::a29f:2cb4NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
rene.ns.cloudflare.com 2803:f800:50::6ca2:c3b4NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
rene.ns.cloudflare.com 2a06:98c1:50::ac40:23b4NOERROR, 8 ms, authoritativenoyes / yesrefused2026.10.2
reza.ns.cloudflare.com 173.245.58.217NOERROR, 5 ms, authoritativenoyes / yesrefused2026.10.2
reza.ns.cloudflare.com 108.162.192.217NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
reza.ns.cloudflare.com 172.64.32.217NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
reza.ns.cloudflare.com 2606:4700:50::adf5:3ad9NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
reza.ns.cloudflare.com 2803:f800:50::6ca2:c0d9NOERROR, 6 ms, authoritativenoyes / yesrefused2026.10.2
reza.ns.cloudflare.com 2a06:98c1:50::ac40:20d9NOERROR, 7 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: rene.ns.cloudflare.com: "2026.10.2"; reza.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 2418151182 · primary rene.ns.cloudflare.com

Found

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

Serial per nameserver

NameserverSerial
rene.ns.cloudflare.com (172.64.35.180)2418151182
rene.ns.cloudflare.com (162.159.44.180)2418151182
rene.ns.cloudflare.com (108.162.195.180)2418151182
rene.ns.cloudflare.com (2606:4700:58::a29f:2cb4)2418151182
rene.ns.cloudflare.com (2803:f800:50::6ca2:c3b4)2418151182
rene.ns.cloudflare.com (2a06:98c1:50::ac40:23b4)2418151182
reza.ns.cloudflare.com (173.245.58.217)2418151182
reza.ns.cloudflare.com (108.162.192.217)2418151182
reza.ns.cloudflare.com (172.64.32.217)2418151182
reza.ns.cloudflare.com (2606:4700:50::adf5:3ad9)2418151182
reza.ns.cloudflare.com (2803:f800:50::6ca2:c0d9)2418151182
reza.ns.cloudflare.com (2a06:98c1:50::ac40:20d9)2418151182

Checks

  • ✓ Serial 2418151182 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 rene.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 2418151182 is a Unix timestamp (2046-08-17 20:39 UTC).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC
Signatures valid until
23 October 2026

DNSKEY in the zone

Key tagRoleAlgorithm
2371KSK (257)ECDSAP256SHA256 (13)
34505ZSK (256)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-21 10:12 UTC and expires at 2026-10-23 12:12 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

warn

11 records at the apex

Found

Read from
172.64.35.180:53
TypeValueTTL
SOArene.ns.cloudflare.com. dns.cloudflare.com. 2418151182 10000 2400 604800 18001800
NSrene.ns.cloudflare.com.86400
NSreza.ns.cloudflare.com.86400
A54.88.14.22660
A100.27.184.6460
A44.218.147.14460
MX10 mxw.mxhichina.com.300
MX5 mxn.mxhichina.com.300
TXT"google-site-verification=DUjumbPBhwhjYKjE3m8YGddCQxkxnRtRQu2flZig6xM"300
TXT"google-site-verification=Uebh0dmtcXb8JoCMCx7mxv3x5mNjBfG3PnlKCOaynwE"300
TXT"uo1nic53aa4pvm5nl2noq68e45"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
    #32
  • ✓ 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