wongcw.com

Checked 22 October 2026, 11:32 UTC · via 8.8.8.8
!Passed with warnings
21 passed 5 warnings 0 failed 5 info

Registration

info

.com generic · Alibaba Cloud Computing (Beijing) Co., Ltd. · expires 2030-05-25

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Alibaba Cloud Computing (Beijing) Co., Ltd.
Registered
25 May 2017
Last changed
8 March 2022
Expires
25 May 2030
Status
client transfer prohibited, client update prohibited
Registry nameservers
vip3.alidns.com, vip4.alidns.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 2030-05-25 #3
    The registration is valid until 2030-05-25 (1311 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

warn

vip3.alidns.com, vip4.alidns.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
vip3.alidns.com, vip4.alidns.com
NS in the zone
vip3.alidns.com, vip4.alidns.com
NameserverAddressesNetwork (AS)Glue
vip3.alidns.com170.33.32.210 170.33.80.10 140.205.1.5 8.212.93.3 170.33.73.26 2408:4009:500::3AS134963 ASEPL-AS-AP - Alibaba Cloud (Singapore) Private Limited, SG AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN121.40.6.163 140.205.1.5 170.33.32.210 170.33.73.26 170.33.80.10 2408:4009:500::3 39.103.26.212 47.108.36.163 47.116.84.178 8.129.152.245 8.212.93.3
vip4.alidns.com170.33.32.211 170.33.73.27 140.205.1.6 170.33.80.11 8.212.93.4 2408:4009:500::4AS134963 ASEPL-AS-AP - Alibaba Cloud (Singapore) Private Limited, SG AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN121.40.6.164 140.205.1.6 170.33.32.211 170.33.73.27 170.33.80.11 2408:4009:500::4 39.103.26.213 47.108.36.164 47.116.84.179 8.129.152.246 8.212.93.4

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: vip3.alidns.com, vip4.alidns.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: vip3.alidns.com (glue 121.40.6.163, 140.205.1.5, 170.33.32.210, 170.33.73.26, 170.33.80.10, 2408:4009:500::3, 39.103.26.212, 47.108.36.163, 47.116.84.178, 8.129.152.245, 8.212.93.3, zone 170.33.32.210, 170.33.80.10, 140.205.1.5, 8.212.93.3, 170.33.73.26, 2408:4009:500::3); vip4.alidns.com (glue 121.40.6.164, 140.205.1.6, 170.33.32.211, 170.33.73.27, 170.33.80.11, 2408:4009:500::4, 39.103.26.213, 47.108.36.164, 47.116.84.179, 8.129.152.246, 8.212.93.4, zone 170.33.32.211, 170.33.73.27, 140.205.1.6, 170.33.80.11, 8.212.93.4, 2408:4009:500::4). 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 2408:4009:500::/48, while the other address family is spread over several networks.
    #10
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS134963 (ASEPL-AS-AP - Alibaba Cloud (Singapore) Private Limited, SG): 2 addresses; AS45102 (ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN): 10 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

pass

12 of 12 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
vip3.alidns.com 170.33.32.210NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip3.alidns.com 170.33.80.10NOERROR, 256 ms, authoritativenoyes / yesrefused-
vip3.alidns.com 140.205.1.5NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip3.alidns.com 8.212.93.3NOERROR, 170 ms, authoritativenoyes / yesrefused-
vip3.alidns.com 170.33.73.26NOERROR, 158 ms, authoritativenoyes / yesrefused-
vip3.alidns.com 2408:4009:500::3NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip4.alidns.com 170.33.32.211NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip4.alidns.com 170.33.73.27NOERROR, 156 ms, authoritativenoyes / yesrefused-
vip4.alidns.com 140.205.1.6NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip4.alidns.com 170.33.80.11NOERROR, 262 ms, authoritativenoyes / yesrefused-
vip4.alidns.com 8.212.93.4NOERROR, 238 ms, authoritativenoyes / yesrefused-
vip4.alidns.com 2408:4009:500::4NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 12 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2026081712 · primary vip3.alidns.com

Found

Primary (MNAME)
vip3.alidns.com
Contact (RNAME)
hostmaster.hichina.com
Serial
2026081712
Refresh / retry
3600 s / 1200 s
Expire
86400 s
Negative TTL
600 s

Serial per nameserver

NameserverSerial
vip3.alidns.com (170.33.32.210)2026081712
vip3.alidns.com (170.33.80.10)2026082516
vip3.alidns.com (140.205.1.5)2026081810
vip3.alidns.com (8.212.93.3)2017052519
vip3.alidns.com (170.33.73.26)2026081716
vip3.alidns.com (2408:4009:500::3)2017052519
vip4.alidns.com (170.33.32.211)2026081810
vip4.alidns.com (170.33.73.27)2026082516
vip4.alidns.com (140.205.1.6)2026082415
vip4.alidns.com (170.33.80.11)2026081716
vip4.alidns.com (8.212.93.4)2026081316
vip4.alidns.com (2408:4009:500::4)2026082415

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2017052519 on vip3.alidns.com (8.212.93.3), vip3.alidns.com (2408:4009:500::3); 2026081316 on vip4.alidns.com (8.212.93.4); 2026081712 on vip3.alidns.com (170.33.32.210); 2026081716 on vip3.alidns.com (170.33.73.26), vip4.alidns.com (170.33.80.11); 2026081810 on vip3.alidns.com (140.205.1.5), vip4.alidns.com (170.33.32.211); 2026082415 on vip4.alidns.com (140.205.1.6), vip4.alidns.com (2408:4009:500::4); 2026082516 on vip3.alidns.com (170.33.80.10), vip4.alidns.com (170.33.73.27). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 1h, retry 20m, expire 1d, negative TTL 10m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver vip3.alidns.com is one of the listed nameservers.
  • ✓ Contact hostmaster@hichina.com #25
    The SOA RNAME hostmaster.hichina.com means hostmaster@hichina.com.
  • ✓ Date-based serial #26
    The serial 2026081712 follows the YYYYMMDDnn convention (2026-08-17).

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

8 records at the apex

Found

Read from
170.33.32.210:53
TypeValueTTL
SOAvip3.alidns.com. hostmaster.hichina.com. 2026081716 3600 1200 86400 600600
NSvip4.alidns.com.86400
NSvip3.alidns.com.86400
A61.92.178.6160
MX5 mxbiz1.qq.com.60
MX10 mxbiz2.qq.com.60
TXT"v=spf1 include:spf.mail.qq.com ~all"60
TXT"google-site-verification=pnpt_llklJj9dsf4JYdWGZFfVMUb7VVVRA9-STM5hLs"60

Checks

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