kuaidi100.com

Checked 22 October 2026, 09:33 UTC · via 8.8.8.8
!Passed with warnings
20 passed 6 warnings 0 failed 5 info

Registration

info

.com generic · Xin Net Technology Corporation · expires 2033-04-10

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Xin Net Technology Corporation
Registered
23 June 2010
Last changed
16 September 2026
Expires
10 April 2033
Status
active
Registry nameservers
ns1.dnsv5.com, ns2.dnsv5.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 2033-04-10 #3
    The registration is valid until 2033-04-10 (2362 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

ns1.dnsv5.com, ns2.dnsv5.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.dnsv5.com, ns2.dnsv5.com
NS in the zone
ns1.dnsv5.com, ns2.dnsv5.com
NameserverAddressesNetwork (AS)Glue
ns1.dnsv5.com1.12.0.20 1.12.0.18 1.12.14.18 52.220.136.67 1.12.0.17 18.194.2.137 101.227.168.52 36.155.149.52 163.177.5.52AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS16509 AMAZON-02 - Amazon.com, Inc., US AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS16509 AMAZON-02 - Amazon.com, Inc., US AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN1.12.0.17 1.12.0.18 1.12.0.20 1.12.14.18 101.227.168.52 108.136.87.44 163.177.5.52 18.194.2.137 35.165.107.227 36.155.149.52 52.220.136.67
ns2.dnsv5.com1.12.0.19 1.12.14.19 52.198.159.146 117.89.178.52 49.7.107.152 117.135.128.152 1.12.0.16AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS16509 AMAZON-02 - Amazon.com, Inc., US AS134756 ChinaNet-NANJING-JISHAN-IDC - CHINANET Nanjing Jishan IDC network, CN AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN1.12.0.16 1.12.0.19 1.12.14.19 117.135.128.152 117.89.178.52 13.37.58.163 150.109.248.236 49.7.107.152 52.198.159.146

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.dnsv5.com, ns2.dnsv5.com.
    #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: ns1.dnsv5.com (glue 1.12.0.17, 1.12.0.18, 1.12.0.20, 1.12.14.18, 101.227.168.52, 108.136.87.44, 163.177.5.52, 18.194.2.137, 35.165.107.227, 36.155.149.52, 52.220.136.67, zone 1.12.0.20, 1.12.0.18, 1.12.14.18, 52.220.136.67, 1.12.0.17, 18.194.2.137, 101.227.168.52, 36.155.149.52, 163.177.5.52); ns2.dnsv5.com (glue 1.12.0.16, 1.12.0.19, 1.12.14.19, 117.135.128.152, 117.89.178.52, 13.37.58.163, 150.109.248.236, 49.7.107.152, 52.198.159.146, zone 1.12.0.19, 1.12.14.19, 52.198.159.146, 117.89.178.52, 49.7.107.152, 117.135.128.152, 1.12.0.16). Update the glue at your registrar.
    #8
  • ✓ 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 11 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 9 autonomous systems #11
    The nameservers are spread over: AS132203 (TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN): 5 addresses; AS134756 (ChinaNet-NANJING-JISHAN-IDC - CHINANET Nanjing Jishan IDC network, CN): 1 address; AS136958 (UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN): 1 address; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 3 addresses; AS23724 (CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN): 1 address; AS45090 (TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN): 2 addresses; AS4811 (CHINANET-SHANGHAI-MAN - China Telecom (Group), CN): 1 address; AS56046 (CMNET-Jiangsu-AP - China Mobile communications corporation, CN): 1 address; AS9808 (CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN): 1 address.
  • 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

warn

16 of 16 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.dnsv5.com 1.12.0.20NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv5.com 1.12.0.18NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv5.com 1.12.14.18NOERROR, 218 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv5.com 52.220.136.67NOERROR, 238 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv5.com 1.12.0.17NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv5.com 18.194.2.137NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv5.com 101.227.168.52NOERROR, 192 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv5.com 36.155.149.52NOERROR, 246 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv5.com 163.177.5.52NOERROR, 254 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns2.dnsv5.com 1.12.0.19NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns2.dnsv5.com 1.12.14.19NOERROR, 203 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns2.dnsv5.com 52.198.159.146NOERROR, 242 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns2.dnsv5.com 117.89.178.52NOERROR, 208 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns2.dnsv5.com 49.7.107.152NOERROR, 156 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns2.dnsv5.com 117.135.128.152NOERROR, 240 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns2.dnsv5.com 1.12.0.16NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01

Checks

  • ✓ All respond #14
    All 16 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: ns1.dnsv5.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns2.dnsv5.com: "DNSPod AUTHORITY DNS 7.3.2512.01". 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

warn

serial 1774866189 · primary ns1.dnsv5.com

Found

Primary (MNAME)
ns1.dnsv5.com
Contact (RNAME)
enterprise3dnsadmin.dnspod.com
Serial
1774866189
Refresh / retry
3600 s / 180 s
Expire
1209600 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns1.dnsv5.com (1.12.0.20)1774866189
ns1.dnsv5.com (1.12.0.18)1774866189
ns1.dnsv5.com (1.12.14.18)1774866189
ns1.dnsv5.com (52.220.136.67)1774866189
ns1.dnsv5.com (1.12.0.17)1774866189
ns1.dnsv5.com (18.194.2.137)1774866189
ns1.dnsv5.com (101.227.168.52)1774866189
ns1.dnsv5.com (36.155.149.52)1774866189
ns1.dnsv5.com (163.177.5.52)1774866189
ns2.dnsv5.com (1.12.0.19)1774866189
ns2.dnsv5.com (1.12.14.19)1774866189
ns2.dnsv5.com (52.198.159.146)1774866189
ns2.dnsv5.com (117.89.178.52)1774866189
ns2.dnsv5.com (49.7.107.152)1774866189
ns2.dnsv5.com (117.135.128.152)1774866189
ns2.dnsv5.com (1.12.0.16)1774866189

Checks

  • ✓ Serial 1774866189 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 3m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1h, retry 3m, expire 14d, negative TTL 3m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.dnsv5.com is one of the listed nameservers.
  • ✓ Contact enterprise3dnsadmin@dnspod.com #25
    The SOA RNAME enterprise3dnsadmin.dnspod.com means enterprise3dnsadmin@dnspod.com.
  • ✓ Timestamp serial #26
    The serial 1774866189 is a Unix timestamp (2026-03-30 10:23 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

warn

10 records at the apex

Found

Read from
1.12.0.20:53
TypeValueTTL
SOAns1.dnsv5.com. enterprise3dnsadmin.dnspod.com. 1774866189 3600 180 1209600 180180
NSns2.dnsv5.com.86400
NSns1.dnsv5.com.86400
A120.92.182.5810
MX5 mail.kuaidi100.com.600
TXT"google-site-verification=dX2FbltTlN_g4DHv9tNDUqPaVhmJBu-4b2GuCtv4VuE"600
TXT"google-site-verification=ypJWKRbjWr-Dj51-mOBCZJyOOV-gOWyYfEhDRtXF0uI"600
TXT"tiktok-developers-site-verification=yKbTcEIWvsTlvpNEzbujiyEoFnVGYAxU"600
TXT"v=spf1 ip4:120.92.182.57 -all"600
TXT"420b6bf332404809afaee0e24ae00627"600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (10s). 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