yuque.com

Checked 22 October 2026, 11:41 UTC · via 8.8.8.8
!Passed with warnings
24 passed 3 warnings 0 failed 4 info

Registration

info

.com generic · Alibaba Cloud Computing (Beijing) Co., Ltd. · expires 2028-11-19

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Alibaba Cloud Computing (Beijing) Co., Ltd.
Registered
19 November 2001
Last changed
10 February 2026
Expires
19 November 2028
Status
client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns1.alipay.com, ns2.alipay.com, ns3.alipay.com, ns4.alipay.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 2028-11-19 #3
    The registration is valid until 2028-11-19 (758 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited, server delete prohibited, server transfer prohibited, server update prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns1.alipay.com, ns2.alipay.com, ns3.alipay.com, ns4.alipay.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.alipay.com, ns2.alipay.com, ns3.alipay.com, ns4.alipay.com
NS in the zone
ns1.alipay.com, ns2.alipay.com, ns3.alipay.com, ns4.alipay.com
NameserverAddressesNetwork (AS)Glue
ns1.alipay.com47.102.234.254 47.113.165.254 47.113.165.222 2400:b200:4100:6666::aAS37963 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 AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN2400:b200:4100:6666::a 47.102.234.254 47.113.165.222 47.113.165.254
ns2.alipay.com110.76.21.66 2400:b200:4100:8888::aAS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN110.76.21.66 2400:b200:4100:8888::a
ns3.alipay.com110.76.21.88 2400:b200:4101:6666::aAS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN110.76.21.88 2400:b200:4101:6666::a
ns4.alipay.com47.118.234.180 47.103.166.30 2400:b200:4101:8888::aAS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS45102 ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN2400:b200:4101:8888::a 47.103.166.30 47.118.234.180

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.alipay.com, ns2.alipay.com, ns3.alipay.com, ns4.alipay.com.
  • ✓ 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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 5 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS37963 (ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN): 6 addresses; AS45102 (ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd., CN): 5 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

warn

11 of 11 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.alipay.com 47.102.234.254NOERROR, 214 ms, authoritativenoyes / yesrefused-
ns1.alipay.com 47.113.165.254NOERROR, 190 ms, authoritativenoyes / yesrefusedAdns 1.0
ns1.alipay.com 47.113.165.222NOERROR, 201 ms, authoritativenoyes / yesrefusedAdns 1.0
ns1.alipay.com 2400:b200:4100:6666::aNOERROR, 212 ms, authoritativenoyes / yesrefusedAdns 1.0
ns2.alipay.com 110.76.21.66NOERROR, 4 ms, authoritativenoyes / yesrefusedAdns 1.0
ns2.alipay.com 2400:b200:4100:8888::aNOERROR, 210 ms, authoritativenoyes / yesrefusedAdns 1.0
ns3.alipay.com 110.76.21.88NOERROR, 3 ms, authoritativenoyes / yesrefusedAdns 1.0
ns3.alipay.com 2400:b200:4101:6666::aNOERROR, 202 ms, authoritativenoyes / yesrefusedAdns 1.0
ns4.alipay.com 47.118.234.180NOERROR, 208 ms, authoritativenoyes / yesrefusedAdns 1.0
ns4.alipay.com 47.103.166.30NOERROR, 204 ms, authoritativenoyes / yesrefused-
ns4.alipay.com 2400:b200:4101:8888::aNOERROR, 196 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 11 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.alipay.com: "Adns 1.0"; ns2.alipay.com: "Adns 1.0"; ns3.alipay.com: "Adns 1.0"; ns4.alipay.com: "Adns 1.0". Hide or replace the version string.
    #17
  • ✓ 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 2406071321 · primary ns1.alipay.com

Found

Primary (MNAME)
ns1.alipay.com
Contact (RNAME)
min.peng.alipay.com
Serial
2406071321
Refresh / retry
3600 s / 1200 s
Expire
315360000 s
Negative TTL
360 s

Serial per nameserver

NameserverSerial
ns1.alipay.com (47.102.234.254)2406071321
ns1.alipay.com (47.113.165.254)2610081528
ns1.alipay.com (47.113.165.222)2610081528
ns1.alipay.com (2400:b200:4100:6666::a)2610081528
ns2.alipay.com (110.76.21.66)2610081528
ns2.alipay.com (2400:b200:4100:8888::a)2610081528
ns3.alipay.com (110.76.21.88)2610081528
ns3.alipay.com (2400:b200:4101:6666::a)2610081528
ns4.alipay.com (47.118.234.180)2610081528
ns4.alipay.com (47.103.166.30)2207272122
ns4.alipay.com (2400:b200:4101:8888::a)2610081528

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 2207272122 on ns4.alipay.com (47.103.166.30); 2406071321 on ns1.alipay.com (47.102.234.254); 2610081528 on ns1.alipay.com (47.113.165.254), ns1.alipay.com (47.113.165.222), ns1.alipay.com (2400:b200:4100:6666::a), ns2.alipay.com (110.76.21.66), ns2.alipay.com (2400:b200:4100:8888::a), ns3.alipay.com (110.76.21.88), ns3.alipay.com (2400:b200:4101:6666::a), ns4.alipay.com (47.118.234.180), ns4.alipay.com (2400:b200:4101:8888::a). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 20m, expire 3650d, negative TTL 6m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.alipay.com is one of the listed nameservers.
  • ✓ Contact min@peng.alipay.com #25
    The SOA RNAME min.peng.alipay.com means min@peng.alipay.com.
  • ✓ Timestamp serial #26
    The serial 2406071321 is a Unix timestamp (2046-03-31 01:08 UTC).

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

5 records at the apex

Found

Read from
47.102.234.254:53
TypeValueTTL
SOAns1.alipay.com. min.peng.alipay.com. 2207272122 3600 1200 315360000 3603600
A203.107.62.20300
MX10 mxw.mxhichina.com.300
MX5 mxn.mxhichina.com.300
TXT"v=spf1 include:spf.mxhichina.com -all"300

Checks

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