yunzhan365.com

ns1.alidns.com, ns2.alidns.com

Found

Parent zone

com

Delegation from

a.gtld-servers.net (192.5.6.30)

NS at the parent

ns1.alidns.com, ns2.alidns.com

NS in the zone

dns13.hichina.com, dns14.hichina.com

Checks

• i

  2 nameservers

  Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.alidns.com, ns2.alidns.com.

  #6
• !

  NS sets differ

  The nameservers at the parent and in the zone should be the same. Only at the parent: ns1.alidns.com, ns2.alidns.com; only in the zone: dns13.hichina.com, dns14.hichina.com. dns13.hichina.com, dns14.hichina.com, ns1.alidns.com, ns2.alidns.com report NS dns13.hichina.com dns14.hichina.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.
• i

  One address family in one network

  all IPv6 addresses are in 2408:4009:501::/48, while the other address family is spread over several networks.

  #10
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS37963 (ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN): 36 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

  #11
• 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 2026082616 · primary dns13.hichina.com

Found

Primary (MNAME)

dns13.hichina.com

Contact (RNAME)

hostmaster.hichina.com

Serial

2026082616

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: 2015033015 on ns1.alidns.com (139.224.142.115), ns1.alidns.com (139.224.142.125), ns2.alidns.com (139.224.142.126); 2026081813 on dns14.hichina.com (120.76.107.51), ns1.alidns.com (120.76.107.45), ns1.alidns.com (2408:4009:501::1); 2026082509 on dns14.hichina.com (139.224.142.121), dns14.hichina.com (120.76.107.41), dns14.hichina.com (2408:4009:501::22), ns2.alidns.com (139.224.142.116); 2026082616 on dns13.hichina.com (120.76.107.52), dns13.hichina.com (39.96.153.42), dns13.hichina.com (120.76.107.42), dns13.hichina.com (39.96.153.52), dns13.hichina.com (47.118.199.202), dns13.hichina.com (2408:4009:501::21), dns14.hichina.com (39.96.153.41), dns14.hichina.com (47.118.199.211), dns14.hichina.com (39.96.153.51), dns14.hichina.com (139.224.142.111), ns1.alidns.com (47.118.199.205), ns1.alidns.com (39.96.153.55), ns2.alidns.com (120.76.107.46), ns2.alidns.com (39.96.153.56), ns2.alidns.com (39.96.153.46), ns2.alidns.com (2408:4009:501::2); 2026082617 on dns13.hichina.com (47.118.199.212), ns1.alidns.com (39.96.153.45), ns1.alidns.com (120.76.107.55), ns2.alidns.com (47.118.199.206), ns2.alidns.com (120.76.107.56); 2026082709 on dns13.hichina.com (139.224.142.122), dns13.hichina.com (139.224.142.112); 2026082815 on ns1.alidns.com (47.118.199.215), ns2.alidns.com (47.118.199.216). 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 dns13.hichina.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 2026082616 follows the YYYYMMDDnn convention (2026-08-26).

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