xiaodiandou.com

Checked 22 October 2026, 11:35 UTC · via 8.8.8.8
✗Problems found
17 passed 3 warnings 1 failed 7 info

Registration

info

.com generic · Jiangsu Bangning Science & technology Co. Ltd. · expires 2027-09-01

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Jiangsu Bangning Science & technology Co. Ltd.
Registered
1 September 2015
Last changed
28 August 2026
Expires
1 September 2027
Status
active
Registry nameservers
dns7.4cun.com, dns8.51dns.top
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-09-01 #3
    The registration is valid until 2027-09-01 (313 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

dns7.4cun.com, dns8.51dns.top

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
dns7.4cun.com, dns8.51dns.top
NameserverAddressesNetwork (AS)Glue
dns7.4cun.com (parent only)61.172.183.74 2408:4005:3dc:af00:a6be:339e:a1a0:d2b8AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN240e:d9:c200:300::36 61.172.183.74
dns8.51dns.top (parent only)219.138.102.210 2408:4005:3dc:af00:a6be:339e:a1a0:d2b8AS136191 CHINATELECOM-HUBEI-YICHANG-IDC - YICHANG, Hubei Province, P.R.China., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns7.4cun.com, dns8.51dns.top.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: dns7.4cun.com (glue 240e:d9:c200:300::36, 61.172.183.74, zone 61.172.183.74, 2408:4005:3dc:af00:a6be:339e:a1a0:d2b8). Update the glue at your registrar.
    #8
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • i
    One address family in one network
    all IPv6 addresses are in 2408:4005:3dc::/48, while the other address family is spread over several networks.
    #10
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS136191 (CHINATELECOM-HUBEI-YICHANG-IDC - YICHANG, Hubei Province, P.R.China., CN): 1 address; AS37963 (ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN): 2 addresses; AS4811 (CHINANET-SHANGHAI-MAN - China Telecom (Group), CN): 1 address.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .top.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

fail

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns7.4cun.com 61.172.183.74NOERROR, 184 ms, authoritativenono / norefuseddns server
dns7.4cun.com 2408:4005:3dc:af00:a6be:339e:a1a0:d2b8NOERROR, 207 ms, authoritativenono / yesrefuseddns server
dns8.51dns.top 219.138.102.210NOERROR, 232 ms, authoritativenono / norefuseddns server
dns8.51dns.top 2408:4005:3dc:af00:a6be:339e:a1a0:d2b8NOERROR, 240 ms, authoritativenono / yesrefuseddns server

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: dns7.4cun.com: "dns server"; dns8.51dns.top: "dns server".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: dns7.4cun.com (61.172.183.74): dial tcp 61.172.183.74:53: i/o timeout; dns7.4cun.com (2408:4005:3dc:af00:a6be:339e:a1a0:d2b8): read tcp [2a01:4f8:1c1c:eebf::1]:35844->[2408:4005:3dc:af00:a6be:339e:a1a0:d2b8]:53: i/o timeout; dns8.51dns.top (219.138.102.210): dial tcp 219.138.102.210:53: i/o timeout; dns8.51dns.top (2408:4005:3dc:af00:a6be:339e:a1a0:d2b8): read tcp [2a01:4f8:1c1c:eebf::1]:35848->[2408:4005:3dc:af00:a6be:339e:a1a0:d2b8]:53: i/o timeout.
    #19
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: dns7.4cun.com (61.172.183.74), dns8.51dns.top (219.138.102.210).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

info

serial 1772528621 · primary dns.4cun.com

Found

Primary (MNAME)
dns.4cun.com
Contact (RNAME)
admin.xiaodiandou.com
Serial
1772528621
Refresh / retry
3600 s / 180 s
Expire
1209600 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
dns7.4cun.com (61.172.183.74)1772528621
dns7.4cun.com (2408:4005:3dc:af00:a6be:339e:a1a0:d2b8)1772528621
dns8.51dns.top (219.138.102.210)1772528621
dns8.51dns.top (2408:4005:3dc:af00:a6be:339e:a1a0:d2b8)1772528621

Checks

  • ✓ Serial 1772528621 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 3m, expire 14d, negative TTL 10m.
  • i
    Hidden master
    The primary nameserver dns.4cun.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact admin@xiaodiandou.com #25
    The SOA RNAME admin.xiaodiandou.com means admin@xiaodiandou.com.
  • ✓ Timestamp serial #26
    The serial 1772528621 is a Unix timestamp (2026-03-03 09:03 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

read udp 46.225.38.91:60934->61.172.183.74:53: i/o timeout

Checks

  • i
    Could not be checked
    The apex records lookup failed, so this could not be checked: read udp 46.225.38.91:60934->61.172.183.74:53: i/o timeout
    #32