liepin.com

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

Registration

info

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

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Alibaba Cloud Computing (Beijing) Co., Ltd.
Registered
27 August 2004
Last changed
10 June 2025
Expires
27 August 2027
Status
client transfer prohibited, client update 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 on 2027-08-27 #3
    The registration is valid until 2027-08-27 (308 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, client update 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.com1.13.76.53 36.155.149.53 124.64.205.153 125.94.59.153 1.12.0.24 43.134.249.54 1.12.0.25 2402:4e00:1470:2::10AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN AS4134 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 AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, 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.com111.13.203.53 220.196.136.53 1.12.0.23 49.7.107.153 117.135.128.153 101.227.168.53 163.177.5.53 1.12.0.26 43.130.172.54 2402:4e00:111:fff::dAS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS140979 UNICOM-SHFT-IDC - China Unicom Shanghai FuTe IDC network, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, 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): 4 addresses; AS136958 (UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN): 1 address; AS140979 (UNICOM-SHFT-IDC - China Unicom Shanghai FuTe IDC 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): 5 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

16 of 18 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.dnsv4.com 1.13.76.53NOERROR, 202 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 36.155.149.53NOERROR, 237 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 124.64.205.153NOERROR, 185 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 125.94.59.153no responsenono / no--
ns3.dnsv4.com 1.12.0.24NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 43.134.249.54NOERROR, 161 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 1.12.0.25NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 2402:4e00:1470:2::10NOERROR, 194 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 111.13.203.53NOERROR, 139 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 220.196.136.53NOERROR, 150 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 49.7.107.153NOERROR, 137 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 117.135.128.153NOERROR, 235 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 101.227.168.53NOERROR, 175 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 163.177.5.53NOERROR, 157 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 43.130.172.54NOERROR, 102 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 2402:4e00:111:fff::dno responsenono / no--

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns3.dnsv4.com (125.94.59.153): read udp 46.225.38.91:52304->125.94.59.153:53: i/o timeout; ns4.dnsv4.com (2402:4e00:111:fff::d): read udp [2a01:4f8:1c1c:eebf::1]:43918->[2402:4e00:111:fff::d]: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 1790736646 · primary ns3.dnsv4.com

Found

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

Serial per nameserver

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

Checks

  • ✓ Serial 1790736646 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 1790736646 is a Unix timestamp (2026-09-30 02:50 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.13.76.53:53
TypeValueTTL
SOAns3.dnsv4.com. enterprise2dnsadmin.dnspod.com. 1790736646 3600 180 1209600 180180
NSns3.dnsv4.com.86400
NSns4.dnsv4.com.86400
A39.96.251.72180
MX5 mxbiz1.qq.com.300
MX5 mxbiz2.qq.com.300
TXT"google-site-verification=2XUx7NcTLx9GCgfuWKk0f5PuWuGLkhbCPxWtcFHPflo"3600
TXT"globalsign-domain-verification=VQC0hZSjbCWd61yT98QEaUpo8KB2h5vp9CY9DkL8Ah"3600
TXT"v=spf1 include:spf.mail.qq.com -all"3600
TXT"MS=B49E2282179545714757E01DC34D76BE21343F81"3600

Checks

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