xinnet.com

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

Registration

info

.com generic · Xin Net Technology Corporation · expires 2027-12-17

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Xin Net Technology Corporation
Registered
17 December 1999
Last changed
16 January 2025
Expires
17 December 2027
Status
client delete prohibited, client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns17.xincache.com, ns18.xincache.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-12-17 #3
    The registration is valid until 2027-12-17 (421 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns17.xincache.com, ns18.xincache.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns17.xincache.com, ns18.xincache.com
NS in the zone
ns11.xincache.com, ns12.xincache.com
NameserverAddressesNetwork (AS)Glue
ns11.xincache.com (zone only)125.94.59.210 129.211.176.209 1.12.0.4 112.80.181.45 117.89.178.173 36.155.149.180 2402:4e00:1470:2::e 2402:4e00:1730::eAS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS134756 ChinaNet-NANJING-JISHAN-IDC - CHINANET Nanjing Jishan IDC network, CN AS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN-
ns12.xincache.com (zone only)163.177.5.23 36.155.149.176 1.12.0.1 129.211.176.239 117.89.178.184 112.80.181.111 2402:4e00:111:fff::cAS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS134756 ChinaNet-NANJING-JISHAN-IDC - CHINANET Nanjing Jishan IDC network, CN AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN-
ns17.xincache.com (parent only)117.89.178.173 1.12.0.4 129.211.176.209 125.94.59.210 112.80.181.45 36.155.149.180 2402:4e00:1730::e 2402:4e00:1470:2::eAS134756 ChinaNet-NANJING-JISHAN-IDC - CHINANET Nanjing Jishan IDC network, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN1.12.0.4 112.80.181.45 117.89.178.173 129.211.176.209 2402:4e00:1470:2::e 36.155.149.180
ns18.xincache.com (parent only)36.155.149.176 1.12.0.1 163.177.5.23 112.80.181.111 129.211.176.239 117.89.178.184 2402:4e00:111:fff::cAS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS134756 ChinaNet-NANJING-JISHAN-IDC - CHINANET Nanjing Jishan IDC network, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN1.12.0.1 112.80.181.111 117.89.178.184 129.211.176.239 2402:4e00:111:fff::c 36.155.149.176

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns17.xincache.com, ns18.xincache.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns17.xincache.com, ns18.xincache.com; only in the zone: ns11.xincache.com, ns12.xincache.com. ns11.xincache.com, ns12.xincache.com, ns17.xincache.com, ns18.xincache.com report NS ns11.xincache.com ns12.xincache.com.
    #7
  • !
    Glue differs from the zone
    The addresses at the parent (glue) differ from the addresses in the zone: ns17.xincache.com (glue 1.12.0.4, 112.80.181.45, 117.89.178.173, 129.211.176.209, 2402:4e00:1470:2::e, 36.155.149.180, zone 117.89.178.173, 1.12.0.4, 129.211.176.209, 125.94.59.210, 112.80.181.45, 36.155.149.180, 2402:4e00:1730::e, 2402:4e00:1470:2::e); ns18.xincache.com (glue 1.12.0.1, 112.80.181.111, 117.89.178.184, 129.211.176.239, 2402:4e00:111:fff::c, 36.155.149.176, zone 36.155.149.176, 1.12.0.1, 163.177.5.23, 112.80.181.111, 129.211.176.239, 117.89.178.184, 2402:4e00:111:fff::c). 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 7 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 7 autonomous systems #11
    The nameservers are spread over: AS132203 (TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN): 2 addresses; AS134756 (ChinaNet-NANJING-JISHAN-IDC - CHINANET Nanjing Jishan IDC network, CN): 4 addresses; AS136958 (UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN): 2 addresses; AS4134 (CHINANET-BACKBONE - No.31,Jin-rong Street, CN): 2 addresses; AS45090 (TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN): 12 addresses; AS4837 (CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN): 4 addresses; AS56046 (CMNET-Jiangsu-AP - China Mobile communications corporation, CN): 4 addresses.
  • 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

fail

28 of 30 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns11.xincache.com 125.94.59.210NOERROR, 196 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns11.xincache.com 129.211.176.209NOERROR, 204 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns11.xincache.com 1.12.0.4NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns11.xincache.com 112.80.181.45NOERROR, 164 ms, authoritativenoyes / yesrefused-
ns11.xincache.com 117.89.178.173NOERROR, 176 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns11.xincache.com 36.155.149.180NOERROR, 253 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns11.xincache.com 2402:4e00:1470:2::eNOERROR, 204 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns11.xincache.com 2402:4e00:1730::eNOERROR, 244 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns12.xincache.com 163.177.5.23NOERROR, 218 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns12.xincache.com 36.155.149.176NOERROR, 237 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns12.xincache.com 1.12.0.1NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns12.xincache.com 129.211.176.239NOERROR, 217 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns12.xincache.com 117.89.178.184NOERROR, 212 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns12.xincache.com 112.80.181.111NOERROR, 216 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns12.xincache.com 2402:4e00:111:fff::cNOERROR, 189 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns17.xincache.com 117.89.178.173NOERROR, 200 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns17.xincache.com 1.12.0.4NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns17.xincache.com 129.211.176.209NOERROR, 210 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns17.xincache.com 125.94.59.210no responsenono / no--
ns17.xincache.com 112.80.181.45NOERROR, 223 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns17.xincache.com 36.155.149.180NOERROR, 240 ms, authoritativenoyes / yesrefused-
ns17.xincache.com 2402:4e00:1730::eNOERROR, 241 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns17.xincache.com 2402:4e00:1470:2::eno responsenono / no--
ns18.xincache.com 36.155.149.176NOERROR, 243 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns18.xincache.com 1.12.0.1NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns18.xincache.com 163.177.5.23NOERROR, 270 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns18.xincache.com 112.80.181.111NOERROR, 213 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns18.xincache.com 129.211.176.239NOERROR, 191 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns18.xincache.com 117.89.178.184NOERROR, 166 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns18.xincache.com 2402:4e00:111:fff::cNOERROR, 199 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns17.xincache.com (125.94.59.210): read udp 46.225.38.91:58129->125.94.59.210:53: i/o timeout; ns17.xincache.com (2402:4e00:1470:2::e): read udp [2a01:4f8:1c1c:eebf::1]:33347->[2402:4e00:1470:2::e]:53: i/o timeout.
    #14
  • ✓ 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: ns11.xincache.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns12.xincache.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns17.xincache.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns18.xincache.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 1791431065 · primary ns11.xincache.com

Found

Primary (MNAME)
ns11.xincache.com
Contact (RNAME)
ns12.xincache.com
Serial
1791431065
Refresh / retry
3600 s / 180 s
Expire
1209600 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns11.xincache.com (125.94.59.210)1791431065
ns11.xincache.com (129.211.176.209)1791431065
ns11.xincache.com (1.12.0.4)1791431065
ns11.xincache.com (112.80.181.45)1791431065
ns11.xincache.com (117.89.178.173)1791431065
ns11.xincache.com (36.155.149.180)1791431065
ns11.xincache.com (2402:4e00:1470:2::e)1791431065
ns11.xincache.com (2402:4e00:1730::e)1791431065
ns12.xincache.com (163.177.5.23)1791431065
ns12.xincache.com (36.155.149.176)1791431065
ns12.xincache.com (1.12.0.1)1791431065
ns12.xincache.com (129.211.176.239)1791431065
ns12.xincache.com (117.89.178.184)1791431065
ns12.xincache.com (112.80.181.111)1791431065
ns12.xincache.com (2402:4e00:111:fff::c)1791431065
ns17.xincache.com (117.89.178.173)1791431065
ns17.xincache.com (1.12.0.4)1791431065
ns17.xincache.com (129.211.176.209)1791431065
ns17.xincache.com (112.80.181.45)1791431065
ns17.xincache.com (36.155.149.180)1791431065
ns17.xincache.com (2402:4e00:1730::e)1791431065
ns18.xincache.com (36.155.149.176)1791431065
ns18.xincache.com (1.12.0.1)1791431065
ns18.xincache.com (163.177.5.23)1791431065
ns18.xincache.com (112.80.181.111)1791431065
ns18.xincache.com (129.211.176.239)1791431065
ns18.xincache.com (117.89.178.184)1791431065
ns18.xincache.com (2402:4e00:111:fff::c)1791431065

Checks

  • ✓ Serial 1791431065 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 ns11.xincache.com is one of the listed nameservers.
  • ✓ Contact ns12@xincache.com #25
    The SOA RNAME ns12.xincache.com means ns12@xincache.com.
  • ✓ Timestamp serial #26
    The serial 1791431065 is a Unix timestamp (2026-10-08 03:44 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
125.94.59.210:53
TypeValueTTL
SOAns11.xincache.com. ns12.xincache.com. 1791431065 3600 180 1209600 180180
NSns11.xincache.com.86400
NSns12.xincache.com.86400
A117.50.32.147600
MX5 mxc.global-mail.cn.600
MX50 mxu.global-mail.cn.600
TXT"qhcwdydkgphh0xj1xcqhqlcsj2xyg5sv"3600
TXT"zh6hvjzk1bz47ys92w3jy6twtjtr1tj8"3600
TXT"v=spf1 include:spfv.global-mail.cn -all"3600
TXT"MS=92F81F325231DE0B38BBCC58E21BB856DE49183E"3600
TXT"rmpg8pt4erjh841idpvuqmbie7"3600
TXT"66bspm4qqjbc85jsdgwg7g8kqx4mb9y3"3600

Checks

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