weqct.com

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

Registration

info

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

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Alibaba Cloud Computing (Beijing) Co., Ltd.
Registered
9 April 2018
Last changed
26 March 2026
Expires
9 April 2027
Status
active
Registry nameservers
vip1.alidns.com, vip2.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 2027-04-09 #3
    The registration is valid until 2027-04-09 (169 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

vip1.alidns.com, vip2.alidns.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
vip1.alidns.com, vip2.alidns.com
NS in the zone
vip1.alidns.com, vip2.alidns.com
NameserverAddressesNetwork (AS)Glue
vip1.alidns.com170.33.73.24 170.33.32.208 170.33.80.8 140.205.1.1 8.212.93.1 2408:4009:500::1AS45102 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 AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising 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.161 140.205.1.1 170.33.32.208 170.33.73.24 170.33.80.8 2408:4009:500::1 39.103.26.210 47.116.84.176 8.129.152.243 8.212.93.1
vip2.alidns.com170.33.73.25 170.33.80.9 8.212.93.2 140.205.1.2 170.33.32.209 2408:4009:500::2AS45102 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 AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS134963 ASEPL-AS-AP - Alibaba Cloud (Singapore) Private Limited, SG AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN121.40.6.162 140.205.1.2 170.33.32.209 170.33.73.25 170.33.80.9 2408:4009:500::2 39.103.26.211 47.116.84.177 8.129.152.244 8.212.93.2

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: vip1.alidns.com, vip2.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: vip1.alidns.com (glue 121.40.6.161, 140.205.1.1, 170.33.32.208, 170.33.73.24, 170.33.80.8, 2408:4009:500::1, 39.103.26.210, 47.116.84.176, 8.129.152.243, 8.212.93.1, zone 170.33.73.24, 170.33.32.208, 170.33.80.8, 140.205.1.1, 8.212.93.1, 2408:4009:500::1); vip2.alidns.com (glue 121.40.6.162, 140.205.1.2, 170.33.32.209, 170.33.73.25, 170.33.80.9, 2408:4009:500::2, 39.103.26.211, 47.116.84.177, 8.129.152.244, 8.212.93.2, zone 170.33.73.25, 170.33.80.9, 8.212.93.2, 140.205.1.2, 170.33.32.209, 2408:4009:500::2). 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
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS134963 (ASEPL-AS-AP - Alibaba Cloud (Singapore) Private Limited, SG): 1 address; AS37963 (ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN): 2 addresses; AS45102 (ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN): 9 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
vip1.alidns.com 170.33.73.24NOERROR, 156 ms, authoritativenoyes / yesrefused-
vip1.alidns.com 170.33.32.208NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip1.alidns.com 170.33.80.8NOERROR, 262 ms, authoritativenoyes / yesrefused-
vip1.alidns.com 140.205.1.1NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip1.alidns.com 8.212.93.1NOERROR, 239 ms, authoritativenoyes / yesrefused-
vip1.alidns.com 2408:4009:500::1NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip2.alidns.com 170.33.73.25NOERROR, 156 ms, authoritativenoyes / yesrefused-
vip2.alidns.com 170.33.80.9NOERROR, 262 ms, authoritativenoyes / yesrefused-
vip2.alidns.com 8.212.93.2NOERROR, 170 ms, authoritativenoyes / yesrefused-
vip2.alidns.com 140.205.1.2NOERROR, 5 ms, authoritativenoyes / yesrefused-
vip2.alidns.com 170.33.32.209NOERROR, 4 ms, authoritativenoyes / yesrefused-
vip2.alidns.com 2408:4009:500::2NOERROR, 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 2018040919 · primary vip1.alidns.com

Found

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

Serial per nameserver

NameserverSerial
vip1.alidns.com (170.33.73.24)2018040919
vip1.alidns.com (170.33.32.208)2026081716
vip1.alidns.com (170.33.80.8)2018040919
vip1.alidns.com (140.205.1.1)2026081810
vip1.alidns.com (8.212.93.1)2026081316
vip1.alidns.com (2408:4009:500::1)2026081810
vip2.alidns.com (170.33.73.25)2026082516
vip2.alidns.com (170.33.80.9)2026082516
vip2.alidns.com (8.212.93.2)2026082516
vip2.alidns.com (140.205.1.2)2026082415
vip2.alidns.com (170.33.32.209)2026081716
vip2.alidns.com (2408:4009:500::2)2026082415

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2018040919 on vip1.alidns.com (170.33.73.24), vip1.alidns.com (170.33.80.8); 2026081316 on vip1.alidns.com (8.212.93.1); 2026081716 on vip1.alidns.com (170.33.32.208), vip2.alidns.com (170.33.32.209); 2026081810 on vip1.alidns.com (140.205.1.1), vip1.alidns.com (2408:4009:500::1); 2026082415 on vip2.alidns.com (140.205.1.2), vip2.alidns.com (2408:4009:500::2); 2026082516 on vip2.alidns.com (170.33.73.25), vip2.alidns.com (170.33.80.9), vip2.alidns.com (8.212.93.2). 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 vip1.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 2018040919 follows the YYYYMMDDnn convention (2018-04-09).

DNSSEC

warn

Signed, but no DS at parent

Found

Validated by resolver
no
Denial of existence
NSEC
Signatures valid until
23 October 2026

DNSKEY in the zone

Key tagRoleAlgorithm
54931KSK (257)ECDSAP256SHA256 (13)
56113ZSK (256)ECDSAP256SHA256 (13)

Checks

  • !
    Signed but not delegated securely
    The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • ✓ Modern algorithms #29
    Key algorithms: ECDSAP256SHA256 (13).
  • ✓ Short-lived signatures (online signing) #30
    Signatures are valid for 50h0m0s and created on demand; the current one was made at 2026-10-21 10:30 UTC and expires at 2026-10-23 12:30 UTC.
  • i
    NSEC
    The zone uses NSEC, so its full contents can be listed by walking the NSEC chain. That is fine unless the names are sensitive.
    #31

Records

info

8 records at the apex

Found

Read from
170.33.73.24:53
TypeValueTTL
SOAvip1.alidns.com. hostmaster.hichina.com. 2026081716 3600 1200 86400 600600
NSvip2.alidns.com.86400
NSvip1.alidns.com.86400
A47.100.191.237600
MX15 mx3.qiye.aliyun.com.600
MX10 mx2.qiye.aliyun.com.600
MX5 mx1.qiye.aliyun.com.600
TXT"v=spf1 include:spf.qiye.aliyun.com -all"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