ltd.com

Checked 22 October 2026, 09:41 UTC · via 8.8.8.8
✗Problems found
20 passed 3 warnings 1 failed 7 info

Registration

info

.com generic · 22net, Inc. · expires 2030-03-15

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
22net, Inc.
Registered
15 March 1999
Last changed
31 October 2025
Expires
15 March 2030
Status
client delete prohibited, client transfer prohibited
Registry nameservers
ns1.alidns.com, ns2.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-03-15 #3
    The registration is valid until 2030-03-15 (1239 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

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
ns1.alidns.com, ns2.alidns.com
NameserverAddressesNetwork (AS)Glue
ns1.alidns.com39.96.153.45 39.96.153.55 47.118.199.205 47.118.199.215 139.224.142.115 139.224.142.125 120.76.107.45 120.76.107.55 2408:4009:501::1AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN120.76.107.45 120.76.107.55 139.224.142.115 139.224.142.125 2408:4009:501::1 39.96.153.45 39.96.153.55 47.118.199.205 47.118.199.215
ns2.alidns.com39.96.153.56 120.76.107.56 139.224.142.116 139.224.142.126 47.118.199.206 39.96.153.46 120.76.107.46 47.118.199.216 2408:4009:501::2AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN120.76.107.46 120.76.107.56 139.224.142.116 139.224.142.126 2408:4009:501::2 39.96.153.46 39.96.153.56 47.118.199.206 47.118.199.216

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
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ 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): 18 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.

Nameservers

fail

16 of 18 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.alidns.com 39.96.153.45NOERROR, 161 ms, authoritativenoyes / yesrefused-
ns1.alidns.com 39.96.153.55no responsenono / no--
ns1.alidns.com 47.118.199.205NOERROR, 217 ms, authoritativenoyes / yesrefused-
ns1.alidns.com 47.118.199.215NOERROR, 207 ms, authoritativenoyes / yesrefused-
ns1.alidns.com 139.224.142.115NOERROR, 207 ms, authoritativenoyes / yesrefused-
ns1.alidns.com 139.224.142.125NOERROR, 190 ms, authoritativenoyes / yesrefused-
ns1.alidns.com 120.76.107.45NOERROR, 194 ms, authoritativenoyes / yesrefused-
ns1.alidns.com 120.76.107.55NOERROR, 207 ms, authoritativenoyes / yesrefused-
ns1.alidns.com 2408:4009:501::1NOERROR, 211 ms, authoritativenoyes / yesrefused-
ns2.alidns.com 39.96.153.56no responsenono / no--
ns2.alidns.com 120.76.107.56NOERROR, 206 ms, authoritativenoyes / yesrefused-
ns2.alidns.com 139.224.142.116NOERROR, 218 ms, authoritativenoyes / yesrefused-
ns2.alidns.com 139.224.142.126NOERROR, 217 ms, authoritativenoyes / yesrefused-
ns2.alidns.com 47.118.199.206NOERROR, 209 ms, authoritativenoyes / yesrefused-
ns2.alidns.com 39.96.153.46NOERROR, 140 ms, authoritativenoyes / yesrefused-
ns2.alidns.com 120.76.107.46NOERROR, 200 ms, authoritativenoyes / yesrefused-
ns2.alidns.com 47.118.199.216NOERROR, 218 ms, authoritativenoyes / yesrefused-
ns2.alidns.com 2408:4009:501::2NOERROR, 220 ms, authoritativenoyes / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns1.alidns.com (39.96.153.55): read udp 46.225.38.91:58634->39.96.153.55:53: i/o timeout; ns2.alidns.com (39.96.153.56): read udp 46.225.38.91:59288->39.96.153.56:53: i/o timeout.
    #14
  • ✓ 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 2026082616 · primary ns1.alidns.com

Found

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

Serial per nameserver

NameserverSerial
ns1.alidns.com (39.96.153.45)2026082616
ns1.alidns.com (47.118.199.205)2026082616
ns1.alidns.com (47.118.199.215)2026082616
ns1.alidns.com (139.224.142.115)2025070216
ns1.alidns.com (139.224.142.125)2026082616
ns1.alidns.com (120.76.107.45)2026082616
ns1.alidns.com (120.76.107.55)2026081813
ns1.alidns.com (2408:4009:501::1)2026082616
ns2.alidns.com (120.76.107.56)2026082617
ns2.alidns.com (139.224.142.116)2026082709
ns2.alidns.com (139.224.142.126)2025070216
ns2.alidns.com (47.118.199.206)2026082616
ns2.alidns.com (39.96.153.46)2026082617
ns2.alidns.com (120.76.107.46)2026082616
ns2.alidns.com (47.118.199.216)2026082617
ns2.alidns.com (2408:4009:501::2)2026082617

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2025070216 on ns1.alidns.com (139.224.142.115), ns2.alidns.com (139.224.142.126); 2026081813 on ns1.alidns.com (120.76.107.55); 2026082616 on ns1.alidns.com (39.96.153.45), ns1.alidns.com (47.118.199.205), ns1.alidns.com (47.118.199.215), ns1.alidns.com (139.224.142.125), ns1.alidns.com (120.76.107.45), ns1.alidns.com (2408:4009:501::1), ns2.alidns.com (47.118.199.206), ns2.alidns.com (120.76.107.46); 2026082617 on ns2.alidns.com (120.76.107.56), ns2.alidns.com (39.96.153.46), ns2.alidns.com (47.118.199.216), ns2.alidns.com (2408:4009:501::2); 2026082709 on ns2.alidns.com (139.224.142.116). 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 ns1.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 2026082616 follows the YYYYMMDDnn convention (2026-08-26).

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

7 records at the apex

Found

Read from
39.96.153.45:53
TypeValueTTL
SOAns1.alidns.com. hostmaster.hichina.com. 2026082616 3600 1200 86400 600600
NSns1.alidns.com.86400
NSns2.alidns.com.86400
A121.43.178.211600
AAAA2408:4005:3f4:8800:3b7f:47a5:e119:e0f4600
MX10 mxbiz2.qq.com.600
MX10 mxbiz1.qq.com.600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, AAAA 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.
  • 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