art-antiquephoenixcollection.com

Checked 22 October 2026, 07:50 UTC · via 8.8.8.8
✗Problems found
20 passed 4 warnings 2 failed 5 info

Registration

info

.com generic · Chengdu West Dimension Digital Technology Co., Ltd. · expires 2027-10-13

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Chengdu West Dimension Digital Technology Co., Ltd.
Registered
13 October 2015
Last changed
3 September 2026
Expires
13 October 2027
Status
active
Registry nameservers
ns15.xincache.com, ns16.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-10-13 #3
    The registration is valid until 2027-10-13 (356 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

ns15.xincache.com, ns16.xincache.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns15.xincache.com, ns16.xincache.com
NS in the zone
ns15.xincache.com, ns16.xincache.com
NameserverAddressesNetwork (AS)Glue
ns15.xincache.com125.94.59.210 117.89.178.173 36.155.149.180 129.211.176.209 1.12.0.4 112.80.181.45 2402:4e00:1470:2::e 2402:4e00:1730::eAS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, 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 AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, 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
ns16.xincache.com1.12.0.1 129.211.176.239 36.155.149.176 163.177.5.23 117.89.178.184 112.80.181.111 2402:4e00:111:fff::cAS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, 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, CN1.12.0.1 112.80.181.111 117.89.178.184 129.211.176.224 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: ns15.xincache.com, ns16.xincache.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: ns15.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 125.94.59.210, 117.89.178.173, 36.155.149.180, 129.211.176.209, 1.12.0.4, 112.80.181.45, 2402:4e00:1470:2::e, 2402:4e00:1730::e); ns16.xincache.com (glue 1.12.0.1, 112.80.181.111, 117.89.178.184, 129.211.176.224, 2402:4e00:111:fff::c, 36.155.149.176, zone 1.12.0.1, 129.211.176.239, 36.155.149.176, 163.177.5.23, 117.89.178.184, 112.80.181.111, 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): 1 address; AS134756 (ChinaNet-NANJING-JISHAN-IDC - CHINANET Nanjing Jishan IDC network, CN): 2 addresses; AS136958 (UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN): 1 address; AS4134 (CHINANET-BACKBONE - No.31,Jin-rong Street, CN): 1 address; AS45090 (TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN): 6 addresses; AS4837 (CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN): 2 addresses; AS56046 (CMNET-Jiangsu-AP - China Mobile communications corporation, CN): 2 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

14 of 15 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns15.xincache.com 125.94.59.210NOERROR, 199 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns15.xincache.com 117.89.178.173NOERROR, 165 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns15.xincache.com 36.155.149.180no responsenono / no--
ns15.xincache.com 129.211.176.209NOERROR, 234 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns15.xincache.com 1.12.0.4NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns15.xincache.com 112.80.181.45NOERROR, 150 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns15.xincache.com 2402:4e00:1470:2::eNOERROR, 200 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns15.xincache.com 2402:4e00:1730::eNOERROR, 239 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns16.xincache.com 1.12.0.1NOERROR, 5 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns16.xincache.com 129.211.176.239NOERROR, 177 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns16.xincache.com 36.155.149.176NOERROR, 199 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns16.xincache.com 163.177.5.23NOERROR, 278 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns16.xincache.com 117.89.178.184NOERROR, 221 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns16.xincache.com 112.80.181.111NOERROR, 162 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns16.xincache.com 2402:4e00:111:fff::cNOERROR, 184 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns15.xincache.com (36.155.149.180): read udp 46.225.38.91:48978->36.155.149.180: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: ns15.xincache.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns16.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 1647941459 · primary ns15.xincache.com

Found

Primary (MNAME)
ns15.xincache.com
Contact (RNAME)
enterprise1dnsadmin.dnspod.com
Serial
1647941459
Refresh / retry
3600 s / 180 s
Expire
1209600 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns15.xincache.com (125.94.59.210)1647941459
ns15.xincache.com (117.89.178.173)1647941459
ns15.xincache.com (129.211.176.209)1647941459
ns15.xincache.com (1.12.0.4)1647941459
ns15.xincache.com (112.80.181.45)1647941459
ns15.xincache.com (2402:4e00:1470:2::e)1647941459
ns15.xincache.com (2402:4e00:1730::e)1647941459
ns16.xincache.com (1.12.0.1)1647941459
ns16.xincache.com (129.211.176.239)1647941459
ns16.xincache.com (36.155.149.176)1647941459
ns16.xincache.com (163.177.5.23)1647941459
ns16.xincache.com (117.89.178.184)1647941459
ns16.xincache.com (112.80.181.111)1647941459
ns16.xincache.com (2402:4e00:111:fff::c)1647941459

Checks

  • ✓ Serial 1647941459 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 ns15.xincache.com is one of the listed nameservers.
  • ✓ Contact enterprise1dnsadmin@dnspod.com #25
    The SOA RNAME enterprise1dnsadmin.dnspod.com means enterprise1dnsadmin@dnspod.com.
  • ✓ Timestamp serial #26
    The serial 1647941459 is a Unix timestamp (2022-03-22 09:30 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

fail

3 records at the apex

Found

Read from
125.94.59.210:53
TypeValueTTL
SOAns15.xincache.com. enterprise1dnsadmin.dnspod.com. 1647941459 3600 180 1209600 180180
NSns15.xincache.com.86400
NSns16.xincache.com.86400

Checks

  • ✓ TTLs within range #32
    TTLs: NS 1d. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
  • ✗
    CNAME at the apex
    The zone apex is a CNAME to jk6699.gotoip2.com. A CNAME can't coexist with the SOA and NS records (RFC 1034); use your provider's ALIAS/flattening feature instead.
    #33
  • ✓ 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