anhuinews.com

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

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.73.26, 140.205.1.5, 170.33.80.10, 170.33.32.210, 8.212.93.3, 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, 140.205.1.6, 170.33.73.27, 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
• ✓ 3 autonomous systems #11

  The nameservers are spread over: AS134963 (ASEPL-AS-AP - Alibaba Cloud (Singapore) Private Limited, SG): 4 addresses; AS37963 (ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN): 1 address; AS45102 (ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN): 7 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.

serial 2026081810 · primary vip3.alidns.com

Found

Primary (MNAME)

vip3.alidns.com

Contact (RNAME)

hostmaster.hichina.com

Serial

2026081810

Refresh / retry

3600 s / 1200 s

Expire

86400 s

Negative TTL

600 s

Serial per nameserver

Checks

• !

  Serials differ

  The nameservers serve different versions of the zone: 2020082116 on vip3.alidns.com (2408:4009:500::3), vip4.alidns.com (170.33.73.27); 2026081810 on vip3.alidns.com (170.33.73.26), vip3.alidns.com (170.33.32.210), vip4.alidns.com (8.212.93.4); 2026082415 on vip3.alidns.com (140.205.1.5), vip4.alidns.com (140.205.1.6), vip4.alidns.com (2408:4009:500::4); 2026082516 on vip3.alidns.com (170.33.80.10), vip3.alidns.com (8.212.93.3), vip4.alidns.com (170.33.32.211), vip4.alidns.com (170.33.80.11). 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 2026081810 follows the YYYYMMDDnn convention (2026-08-18).

Signed, but no DS at parent

Found

Validated by resolver

no

Signatures valid until

23 October 2026

DNSKEY in the zone

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 06:44 UTC and expires at 2026-10-23 08:44 UTC.

6 records at the apex

Found

Read from

170.33.73.26:53

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.
• 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