processon.com

Checked 22 October 2026, 10:21 UTC · via 8.8.8.8
!Passed with warnings
23 passed 4 warnings 0 failed 4 info

Registration

info

.com generic · Bizcn.com, Inc. · expires 2027-10-10

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Bizcn.com, Inc.
Registered
10 October 2011
Last changed
26 May 2023
Expires
10 October 2027
Status
client transfer prohibited
Registry nameservers
ns3.dnsv3.com, ns4.dnsv3.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-10 #3
    The registration is valid until 2027-10-10 (352 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns3.dnsv3.com, ns4.dnsv3.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns3.dnsv3.com, ns4.dnsv3.com
NS in the zone
ns3.dnsv3.com, ns4.dnsv3.com
NameserverAddressesNetwork (AS)Glue
ns3.dnsv3.com1.12.0.27 220.196.136.54 43.130.172.55 101.227.168.54 36.155.149.54 43.140.78.54 163.177.5.54 49.7.107.154 2402:4e00:1470:2::11AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS17621 CNCGROUP-SH - China Unicom Shanghai network, CN AS132203 TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN AS4811 CHINANET-SHANGHAI-MAN - China Telecom (Group), CN AS56046 CMNET-Jiangsu-AP - China Mobile communications corporation, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS136958 UNICOM-GuangZhou-IDC - China Unicom Guangdong IP network, CN AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN1.12.0.27 101.227.168.54 163.177.5.54 220.196.136.54 2402:4e00:1470:2::11 36.155.149.55 43.130.172.55 43.140.78.54 49.7.107.154
ns4.dnsv3.com111.13.203.54 1.13.76.54 124.64.205.154 1.12.0.28 117.135.128.154 125.94.59.154 43.134.249.55 2402:4e00:111:fff::eAS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN AS45090 TENCENT-NET-AP - Shenzhen Tencent Computer Systems Company Limited, CN AS24400 CMNET-V4shanghai-AS-AP - Shanghai Mobile Communications Co.,Ltd., 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, CN1.12.0.28 1.13.76.54 111.13.203.54 117.135.128.154 124.64.205.154 125.94.59.154 2402:4e00:111:fff::e 43.134.249.55

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3.dnsv3.com, ns4.dnsv3.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.dnsv3.com (glue 1.12.0.27, 101.227.168.54, 163.177.5.54, 220.196.136.54, 2402:4e00:1470:2::11, 36.155.149.55, 43.130.172.55, 43.140.78.54, 49.7.107.154, zone 1.12.0.27, 220.196.136.54, 43.130.172.55, 101.227.168.54, 36.155.149.54, 43.140.78.54, 163.177.5.54, 49.7.107.154, 2402:4e00:1470:2::11). 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 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): 2 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; AS24400 (CMNET-V4shanghai-AS-AP - Shanghai Mobile Communications Co.,Ltd., 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; 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): 1 address.
  • 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

warn

17 of 17 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns3.dnsv3.com 1.12.0.27NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 220.196.136.54NOERROR, 147 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 43.130.172.55NOERROR, 101 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 101.227.168.54NOERROR, 200 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 36.155.149.54NOERROR, 205 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 43.140.78.54NOERROR, 232 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 163.177.5.54NOERROR, 219 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 49.7.107.154NOERROR, 154 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns3.dnsv3.com 2402:4e00:1470:2::11NOERROR, 165 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 111.13.203.54NOERROR, 146 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 1.13.76.54NOERROR, 203 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 124.64.205.154NOERROR, 121 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 1.12.0.28NOERROR, 4 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 117.135.128.154NOERROR, 256 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 125.94.59.154NOERROR, 207 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 43.134.249.55NOERROR, 244 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01
ns4.dnsv3.com 2402:4e00:111:fff::eNOERROR, 201 ms, authoritativenoyes / yesrefusedDNSPod AUTHORITY DNS 7.3.2512.01

Checks

  • ✓ All respond #14
    All 17 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: ns3.dnsv3.com: "DNSPod AUTHORITY DNS 7.3.2512.01"; ns4.dnsv3.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 1789988400 · primary ns3.dnsv3.com

Found

Primary (MNAME)
ns3.dnsv3.com
Contact (RNAME)
enterprise1dnsadmin.dnspod.com
Serial
1789988400
Refresh / retry
3600 s / 180 s
Expire
1209600 s
Negative TTL
180 s

Serial per nameserver

NameserverSerial
ns3.dnsv3.com (1.12.0.27)1789988400
ns3.dnsv3.com (220.196.136.54)1789988400
ns3.dnsv3.com (43.130.172.55)1789988400
ns3.dnsv3.com (101.227.168.54)1789988400
ns3.dnsv3.com (36.155.149.54)1789988400
ns3.dnsv3.com (43.140.78.54)1789988400
ns3.dnsv3.com (163.177.5.54)1789988400
ns3.dnsv3.com (49.7.107.154)1789988400
ns3.dnsv3.com (2402:4e00:1470:2::11)1789988400
ns4.dnsv3.com (111.13.203.54)1789988400
ns4.dnsv3.com (1.13.76.54)1789988400
ns4.dnsv3.com (124.64.205.154)1789988400
ns4.dnsv3.com (1.12.0.28)1789988400
ns4.dnsv3.com (117.135.128.154)1789988400
ns4.dnsv3.com (125.94.59.154)1789988400
ns4.dnsv3.com (43.134.249.55)1789988400
ns4.dnsv3.com (2402:4e00:111:fff::e)1789988400

Checks

  • ✓ Serial 1789988400 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.dnsv3.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 1789988400 is a Unix timestamp (2026-09-21 11:00 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

11 records at the apex

Found

Read from
1.12.0.27:53
TypeValueTTL
SOAns3.dnsv3.com. enterprise1dnsadmin.dnspod.com. 1789988400 3600 180 1209600 180180
NSns4.dnsv3.com.86400
NSns3.dnsv3.com.86400
A120.92.77.238600
MX5 mxbiz1.qq.com.600
MX10 mxbiz2.qq.com.600
TXT"_globalsign-domain-verification=b7VXPk5OKRexbq6Tcwk9i_CgB0WQl-Iq0WxG4SBwmS"600
TXT"v=spf1 include:spf.mail.qq.com ~all"600
TXT"google-site-verification=-oQc0k5PF3rTgDHX7AbTGBQ2XDsDE-5vQdle4LKgppo"600
TXT"google-site-verification=WYk9e-v1oNxfw24tO1vmt4kfodXzsZvNyPX6dz6_cgU"600
TXT"_globalsign-domain-verification=Ze6yx3Mk6wbx99wnPhlYGet90hiwR1utxvBNWBaFHe"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.
  • ✓ 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