yiche.com

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

Registration

info

.com generic · Alibaba Cloud Computing (Beijing) Co., Ltd. · expires 2027-02-23

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Alibaba Cloud Computing (Beijing) Co., Ltd.
Registered
23 February 2004
Last changed
11 December 2025
Expires
23 February 2027
Status
server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns3.dnsv5.com, ns4.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 2027-02-23 #3
    The registration is valid until 2027-02-23 (124 days).
  • ✓ Transfer locked #4
    Registry status: 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

ns3.dnsv5.com, ns4.dnsv5.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns3.dnsv5.com, ns4.dnsv5.com
NS in the zone
ns3.dnsv5.com, ns4.dnsv5.com
NameserverAddressesNetwork (AS)Glue
ns3.dnsv5.com15.160.102.38 162.62.49.74 1.12.0.18 163.177.5.52 1.12.14.18 13.37.58.163 1.12.0.17 18.134.75.163 1.12.14.17 240d:c000:3011::10AS16509 AMAZON-02 - Amazon.com, Inc., US AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, 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 AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN1.12.0.17 1.12.0.18 1.12.14.17 1.12.14.18 101.227.168.52 108.136.87.44 163.177.5.52 220.196.136.52 2402:4e00:1470:2::f 35.165.107.227
ns4.dnsv5.com1.12.14.16 13.48.202.4 1.12.0.19 1.12.14.19 18.194.2.137 162.62.49.12 63.34.1.181 1.12.0.16 240d:c000:3011::fAS132203 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 AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, 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 AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN1.12.0.16 1.12.0.19 1.12.14.16 1.12.14.19 117.135.128.152 124.64.205.152 13.37.58.163 2402:4e00:111:fff::8 49.7.107.152

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3.dnsv5.com, ns4.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: ns3.dnsv5.com (glue 1.12.0.17, 1.12.0.18, 1.12.14.17, 1.12.14.18, 101.227.168.52, 108.136.87.44, 163.177.5.52, 220.196.136.52, 2402:4e00:1470:2::f, 35.165.107.227, zone 15.160.102.38, 162.62.49.74, 1.12.0.18, 163.177.5.52, 1.12.14.18, 13.37.58.163, 1.12.0.17, 18.134.75.163, 1.12.14.17, 240d:c000:3011::10); ns4.dnsv5.com (glue 1.12.0.16, 1.12.0.19, 1.12.14.16, 1.12.14.19, 117.135.128.152, 124.64.205.152, 13.37.58.163, 2402:4e00:111:fff::8, 49.7.107.152, zone 1.12.14.16, 13.48.202.4, 1.12.0.19, 1.12.14.19, 18.194.2.137, 162.62.49.12, 63.34.1.181, 1.12.0.16, 240d:c000:3011::f). 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 240d:c000:3011::/48, while the other address family is spread over several networks.
    #10
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS132203 (TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN): 9 addresses; AS136958 (UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN): 1 address; AS16509 (AMAZON-02 - Amazon.com, Inc., US): 6 addresses; AS45090 (TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN): 3 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

18 of 19 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.dnsv5.com 15.160.102.38NOERROR, 13 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 162.62.49.74NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 1.12.0.18NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 163.177.5.52no responsenono / no--
ns3.dnsv5.com 1.12.14.18NOERROR, 201 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 13.37.58.163NOERROR, 11 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 1.12.0.17NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 18.134.75.163NOERROR, 15 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 1.12.14.17NOERROR, 191 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv5.com 240d:c000:3011::10NOERROR, 96 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 1.12.14.16NOERROR, 203 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 13.48.202.4NOERROR, 23 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 1.12.0.19NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 1.12.14.19NOERROR, 202 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 18.194.2.137NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 162.62.49.12NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 63.34.1.181NOERROR, 23 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 1.12.0.16NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv5.com 240d:c000:3011::fNOERROR, 99 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01

Checks

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

Found

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

Serial per nameserver

NameserverSerial
ns3.dnsv5.com (15.160.102.38)1789898748
ns3.dnsv5.com (162.62.49.74)1789898748
ns3.dnsv5.com (1.12.0.18)1789898748
ns3.dnsv5.com (1.12.14.18)1789898748
ns3.dnsv5.com (13.37.58.163)1789898748
ns3.dnsv5.com (1.12.0.17)1789898748
ns3.dnsv5.com (18.134.75.163)1789898748
ns3.dnsv5.com (1.12.14.17)1789898748
ns3.dnsv5.com (240d:c000:3011::10)1789898748
ns4.dnsv5.com (1.12.14.16)1789898748
ns4.dnsv5.com (13.48.202.4)1789898748
ns4.dnsv5.com (1.12.0.19)1789898748
ns4.dnsv5.com (1.12.14.19)1789898748
ns4.dnsv5.com (18.194.2.137)1789898748
ns4.dnsv5.com (162.62.49.12)1789898748
ns4.dnsv5.com (63.34.1.181)1789898748
ns4.dnsv5.com (1.12.0.16)1789898748
ns4.dnsv5.com (240d:c000:3011::f)1789898748

Checks

  • ✓ Serial 1789898748 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.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 1789898748 is a Unix timestamp (2026-09-20 10: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

info

9 records at the apex

Found

Read from
15.160.102.38:53
TypeValueTTL
SOAns3.dnsv5.com. enterprise3dnsadmin.dnspod.com. 1789898748 3600 180 1209600 180180
NSns3.dnsv5.com.86400
NSns4.dnsv5.com.86400
A152.136.4.16600
MX5 mail2.yiche.com.600
TXT"_globalsign-domain-verification=sd5NKtQXEbzzX7hdNfDsUeWesdxd6yG5z-VUxu9bRL"600
TXT"v=spf1 mx ip4:109.244.0.124 ip4:124.70.112.254 ip4:124.70.113.6 ip4:62.234.81.117 -all"600
TXT"MS=F9FE391AA9C284E0D07D56D2A43368B885444896"600
TXT"_globalsign-domain-verification=iQUXluFc8aA3nrqlhPJ-aAkPa7nT_09UgYTzPc7HDR"600

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