xywy.com

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

Registration

warn

.com generic · eName Technology Co., Ltd. · expires 2026-11-18

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
eName Technology Co., Ltd.
Registered
18 November 2002
Last changed
17 September 2025
Expires
18 November 2026
Status
client delete prohibited, client transfer prohibited
Registry nameservers
ns3.dnsv4.com, ns4.dnsv4.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 in 27 days
    The registration expires on 2026-11-18. Make sure it is renewed.
    #3
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns3.dnsv4.com, ns4.dnsv4.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns3.dnsv4.com, ns4.dnsv4.com
NS in the zone
ns3.dnsv4.com, ns4.dnsv4.com
NameserverAddressesNetwork (AS)Glue
ns3.dnsv4.com43.134.249.54 36.155.149.53 1.12.0.25 124.64.205.153 125.94.59.153 1.12.0.24 1.13.76.53 2402:4e00:1470:2::10AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, 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.24 1.12.0.25 1.13.76.53 124.64.205.153 125.94.59.153 2402:4e00:1470:2::10 36.155.149.53 43.134.249.54
ns4.dnsv4.com101.227.168.53 1.12.0.26 117.135.128.153 163.177.5.53 111.13.203.53 220.196.136.53 43.130.172.54 49.7.107.153 1.12.0.23 2402:4e00:111:fff::dAS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS17621 CNCGROUP-SH - China Unicom Shanghai network, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN1.12.0.23 1.12.0.26 101.227.168.53 111.13.203.53 117.135.128.153 163.177.5.53 220.196.136.53 2402:4e00:111:fff::d 43.130.172.54 49.7.107.153

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3.dnsv4.com, ns4.dnsv4.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 13 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 10 autonomous systems #11
    The nameservers are spread over: AS132203 (TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN): 5 addresses; AS136958 (UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN): 1 address; AS17621 (CNCGROUP-SH - China Unicom Shanghai network, CN): 1 address; AS23724 (CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, 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): 4 addresses; AS4808 (CHINA169-BJ - China Unicom Beijing Province Network, CN): 1 address; 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): 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

17 of 18 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.dnsv4.com 43.134.249.54NOERROR, 187 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 36.155.149.53NOERROR, 261 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 1.12.0.25NOERROR, 5 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 124.64.205.153NOERROR, 135 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 125.94.59.153NOERROR, 201 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 1.12.0.24NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 1.13.76.53NOERROR, 203 ms, authoritativenoyes / yesrefused-
ns3.dnsv4.com 2402:4e00:1470:2::10NOERROR, 197 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 101.227.168.53NOERROR, 173 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 1.12.0.26NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 117.135.128.153NOERROR, 242 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 163.177.5.53no responsenono / no--
ns4.dnsv4.com 111.13.203.53NOERROR, 143 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 220.196.136.53NOERROR, 252 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 43.130.172.54NOERROR, 100 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 49.7.107.153NOERROR, 151 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 1.12.0.23NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 2402:4e00:111:fff::dNOERROR, 197 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns4.dnsv4.com (163.177.5.53): read udp 46.225.38.91:37396->163.177.5.53: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: ns3.dnsv4.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns4.dnsv4.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 1792631154 · primary ns3.dnsv4.com

Found

Primary (MNAME)
ns3.dnsv4.com
Contact (RNAME)
enterprise2dnsadmin.dnspod.com
Serial
1792631154
Refresh / retry
3600 s / 180 s
Expire
1209600 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns3.dnsv4.com (43.134.249.54)1792631154
ns3.dnsv4.com (36.155.149.53)1792631154
ns3.dnsv4.com (1.12.0.25)1792631154
ns3.dnsv4.com (124.64.205.153)1792631154
ns3.dnsv4.com (125.94.59.153)1792631154
ns3.dnsv4.com (1.12.0.24)1792631154
ns3.dnsv4.com (1.13.76.53)1792631154
ns3.dnsv4.com (2402:4e00:1470:2::10)1792631154
ns4.dnsv4.com (101.227.168.53)1792631154
ns4.dnsv4.com (1.12.0.26)1792631154
ns4.dnsv4.com (117.135.128.153)1792631154
ns4.dnsv4.com (111.13.203.53)1792631154
ns4.dnsv4.com (220.196.136.53)1792631154
ns4.dnsv4.com (43.130.172.54)1792631154
ns4.dnsv4.com (49.7.107.153)1792631154
ns4.dnsv4.com (1.12.0.23)1792631154
ns4.dnsv4.com (2402:4e00:111:fff::d)1792631154

Checks

  • ✓ Serial 1792631154 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 ns3.dnsv4.com is one of the listed nameservers.
  • ✓ Contact enterprise2dnsadmin@dnspod.com #25
    The SOA RNAME enterprise2dnsadmin.dnspod.com means enterprise2dnsadmin@dnspod.com.
  • ✓ Timestamp serial #26
    The serial 1792631154 is a Unix timestamp (2026-10-22 01:05 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

11 records at the apex

Found

Read from
43.134.249.54:53
TypeValueTTL
SOAns3.dnsv4.com. enterprise2dnsadmin.dnspod.com. 1792631154 3600 180 1209600 180180
NSns4.dnsv4.com.86400
NSns3.dnsv4.com.86400
A180.163.29.15160
A140.207.188.11960
MX5 mxn.mxhichina.com.600
MX10 mxw.mxhichina.com.600
TXT"google-site-verification=M6pmEJtFzOLAakS4VMAkrUfxeSBprlH-w6dklcEDORY"600
TXT"v=spf1 include:spf.mxhichina.com -all"600
TXT"71be1d9bbbf2de2b20e934b16746b9eb7550d6a1960dc194ede0f5ba19708b89"600
TXT"ed76ed4e7da47f958288ef21dad9eb42b4d0da24bbd95c787c490e072705be75"600

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