zhibo8.com

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

Registration

info

.com generic · GoDaddy.com, LLC · expires 2034-05-23

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
GoDaddy.com, LLC
Registered
18 May 2007
Last changed
22 April 2026
Expires
23 May 2034
Status
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Registry nameservers
ns1.dnsv2.com, ns2.dnsv2.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 2034-05-23 #3
    The registration is valid until 2034-05-23 (2769 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.dnsv2.com, ns2.dnsv2.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.dnsv2.com, ns2.dnsv2.com
NS in the zone
ns3.dnsv4.com, ns4.dnsv4.com
NameserverAddressesNetwork (AS)Glue
ns1.dnsv2.com (parent only)1.13.76.55 1.12.0.29 117.89.178.55 117.135.128.155 163.177.5.55 125.94.59.155AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS134756 ChinaNet-NANJING-JISHAN-IDC - CHINANET Nanjing Jishan IDC network, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN1.12.0.29 1.13.76.55 117.135.128.155 117.89.178.55 125.94.59.155 163.177.5.55
ns2.dnsv2.com (parent only)36.155.149.55 124.64.205.155 101.227.168.55 1.12.0.30AS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN1.12.0.30 101.227.168.55 124.64.205.155 36.155.149.55
ns3.dnsv4.com (zone only)36.155.149.53 1.12.0.25 124.64.205.153 1.12.0.24 125.94.59.153 43.134.249.54 1.13.76.53 2402:4e00:1470:2::10AS56046 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 AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, 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, CN-
ns4.dnsv4.com (zone only)220.196.136.53 101.227.168.53 49.7.107.153 43.130.172.54 117.135.128.153 163.177.5.53 1.12.0.23 111.13.203.53 1.12.0.26 2402:4e00:111:fff::dAS140979 UNICOM-SHFT-IDC - China Unicom Shanghai FuTe IDC network, CN AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.dnsv2.com, ns2.dnsv2.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.dnsv2.com, ns2.dnsv2.com; only in the zone: ns3.dnsv4.com, ns4.dnsv4.com. ns1.dnsv2.com, ns2.dnsv2.com, ns3.dnsv4.com, ns4.dnsv4.com report NS ns3.dnsv4.com ns4.dnsv4.com.
    #7
  • ✓ 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 14 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 11 autonomous systems #11
    The nameservers are spread over: AS132203 (TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN): 7 addresses; AS134756 (ChinaNet-NANJING-JISHAN-IDC - CHINANET Nanjing Jishan IDC network, CN): 1 address; AS136958 (UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN): 2 addresses; 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): 2 addresses; AS45090 (TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN): 5 addresses; AS4808 (CHINA169-BJ - China Unicom Beijing Province Network, CN): 2 addresses; AS4811 (CHINANET-SHANGHAI-MAN - China Telecom (Group), CN): 2 addresses; AS56046 (CMNET-Jiangsu-AP - China Mobile communications corporation, CN): 2 addresses; AS9808 (CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.dnsv2.com, ns2.dnsv2.com.
    #13

Nameservers

warn

28 of 28 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.dnsv2.com 1.13.76.55NOERROR, 197 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv2.com 1.12.0.29NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv2.com 117.89.178.55NOERROR, 235 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv2.com 117.135.128.155NOERROR, 230 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv2.com 163.177.5.55NOERROR, 219 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns1.dnsv2.com 125.94.59.155NOERROR, 215 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns2.dnsv2.com 36.155.149.55NOERROR, 201 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns2.dnsv2.com 124.64.205.155NOERROR, 193 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns2.dnsv2.com 101.227.168.55NOERROR, 200 ms, authoritativenoyes / yesrefused-
ns2.dnsv2.com 1.12.0.30NOERROR, 3 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 36.155.149.53NOERROR, 197 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 124.64.205.153NOERROR, 141 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 125.94.59.153NOERROR, 215 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 43.134.249.54NOERROR, 162 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 1.13.76.53NOERROR, 199 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv4.com 2402:4e00:1470:2::10NOERROR, 198 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 220.196.136.53NOERROR, 168 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 49.7.107.153NOERROR, 139 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 117.135.128.153NOERROR, 236 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv4.com 163.177.5.53NOERROR, 261 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 111.13.203.53NOERROR, 134 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 2402:4e00:111:fff::dNOERROR, 185 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01

Checks

  • ✓ All respond #14
    All 28 nameserver addresses answered.
  • ✓ 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: ns1.dnsv2.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns2.dnsv2.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; 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 1792490617 · primary ns3.dnsv4.com

Found

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

Serial per nameserver

NameserverSerial
ns1.dnsv2.com (1.13.76.55)1792490617
ns1.dnsv2.com (1.12.0.29)1792490617
ns1.dnsv2.com (117.89.178.55)1792490617
ns1.dnsv2.com (117.135.128.155)1792490617
ns1.dnsv2.com (163.177.5.55)1792490617
ns1.dnsv2.com (125.94.59.155)1792490617
ns2.dnsv2.com (36.155.149.55)1792490617
ns2.dnsv2.com (124.64.205.155)1792490617
ns2.dnsv2.com (101.227.168.55)1792490617
ns2.dnsv2.com (1.12.0.30)1792490617
ns3.dnsv4.com (36.155.149.53)1792490617
ns3.dnsv4.com (1.12.0.25)1792490617
ns3.dnsv4.com (124.64.205.153)1792490617
ns3.dnsv4.com (1.12.0.24)1792490617
ns3.dnsv4.com (125.94.59.153)1792490617
ns3.dnsv4.com (43.134.249.54)1792490617
ns3.dnsv4.com (1.13.76.53)1792490617
ns3.dnsv4.com (2402:4e00:1470:2::10)1792490617
ns4.dnsv4.com (220.196.136.53)1792490617
ns4.dnsv4.com (101.227.168.53)1792490617
ns4.dnsv4.com (49.7.107.153)1792490617
ns4.dnsv4.com (43.130.172.54)1792490617
ns4.dnsv4.com (117.135.128.153)1792490617
ns4.dnsv4.com (163.177.5.53)1792490617
ns4.dnsv4.com (1.12.0.23)1792490617
ns4.dnsv4.com (111.13.203.53)1792490617
ns4.dnsv4.com (1.12.0.26)1792490617
ns4.dnsv4.com (2402:4e00:111:fff::d)1792490617

Checks

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

11 records at the apex

Found

Read from
1.13.76.55:53
TypeValueTTL
SOAns3.dnsv4.com. enterprise2dnsadmin.dnspod.com. 1792490617 3600 180 1209600 180180
NSns3.dnsv4.com.86400
NSns4.dnsv4.com.86400
MX5 mxbiz1.qq.com.600
MX10 mxbiz2.qq.com.600
TXT"google-site-verification=SAa2XY6Qqi1muTztggoUSXu3fhI-vb6puaMr-89ywfU"600
TXT"_globalsign-domain-verification=7rIVqKgnR-Ct0fZjUJvm4MfgElc4tHrjLGECyjz7AV"600
TXT"_globalsign-domain-verification=91CBSGb3IsatYxr_SFm_P55cXqmOtxrqvg2d5od1cK"600
TXT"_globalsign-domain-verification=N_FWmeHe4am9s2dxonVnvr8bubrnC_ov2gemJE2Nlk"600
TXT"_globalsign-domain-verification=PJRZAsMJvWdVl8_Mb95TQphkMztkPSeUOyRs7quB5u"600
TXT"v=spf1 include:spf.mail.qq.com ~all"600

Checks

  • ✓ TTLs within range #32
    TTLs: MX 10m, 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 alb-eb3r1d7l5svtqr0j1p.cn-hangzhou.alb.aliyuncsslb.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