netease.com

Checked 22 October 2026, 10:01 UTC · via 8.8.8.8
!Passed with warnings
25 passed 4 warnings 0 failed 2 info

Registration

info

.com generic · MarkMonitor Information Technology (Shanghai) Co., Ltd. · expires 2028-04-08

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Information Technology (Shanghai) Co., Ltd.
Registered
9 April 1998
Last changed
24 June 2026
Expires
8 April 2028
Status
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns1.nease.net, ns2.166.com, ns3.nease.net, ns4.nease.net, ns5.nease.net, ns6.nease.net, ns8.166.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-04-08 #3
    The registration is valid until 2028-04-08 (533 days).
  • ✓ Transfer locked #4
    Registry status: client delete prohibited, client transfer prohibited, client update 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

warn

ns1.nease.net, ns2.166.com, ns3.nease.net, ns4.nease.net, ns5.nease.net, ns6.nease.net, ns8.166.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.nease.net, ns2.166.com, ns3.nease.net, ns4.nease.net, ns5.nease.net, ns6.nease.net, ns8.166.com
NS in the zone
ns1.nease.net, ns2.166.com, ns3.nease.net, ns4.nease.net, ns5.nease.net, ns6.nease.net, ns8.166.com
NameserverAddressesNetwork (AS)Glue
ns1.nease.net42.186.168.126AS45062 Netease-Network - NetEase Building No.16 Ke Yun Road,, CN-
ns2.166.com42.186.236.84 1.95.235.6 42.186.102.226AS45062 Netease-Network - NetEase Building No.16 Ke Yun Road,, CN AS55990 HWCSNET - Huawei Cloud Service data center, CN AS45062 Netease-Network - NetEase Building No.16 Ke Yun Road,, CN1.95.235.6 42.186.102.226 42.186.236.84
ns3.nease.net182.92.22.240AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN-
ns4.nease.net8.147.116.45AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN-
ns5.nease.net42.186.102.226 42.186.236.84AS45062 Netease-Network - NetEase Building No.16 Ke Yun Road,, CN AS45062 Netease-Network - NetEase Building No.16 Ke Yun Road,, CN-
ns6.nease.net54.228.156.72AS16509 AMAZON-02 - Amazon.com, Inc., US-
ns8.166.com18.182.82.158 44.228.163.69AS16509 AMAZON-02 - Amazon.com, Inc., US AS16509 AMAZON-02 - Amazon.com, Inc., US18.182.82.158 44.228.163.69

Checks

  • ✓ 7 nameservers #6
    Delegated to ns1.nease.net, ns2.166.com, ns3.nease.net, ns4.nease.net, ns5.nease.net, ns6.nease.net, ns8.166.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 9 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS16509 (AMAZON-02 - Amazon.com, Inc., US): 3 addresses; AS37963 (ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN): 2 addresses; AS45062 (Netease-Network - NetEase Building No.16 Ke Yun Road,, CN): 5 addresses; AS55990 (HWCSNET - Huawei Cloud Service data center, CN): 1 address.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .net.
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

11 of 11 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.nease.net 42.186.168.126NOERROR, 163 ms, authoritativenoyes / yesrefused-
ns2.166.com 42.186.236.84NOERROR, 186 ms, authoritativenoyes / yesrefused-
ns2.166.com 1.95.235.6NOERROR, 216 ms, authoritativenoyes / yesrefused-
ns2.166.com 42.186.102.226NOERROR, 164 ms, authoritativenoyes / yesrefused-
ns3.nease.net 182.92.22.240NOERROR, 145 ms, authoritativenoyes / yesrefused-
ns4.nease.net 8.147.116.45NOERROR, 172 ms, authoritativenoyes / yesrefused-
ns5.nease.net 42.186.102.226NOERROR, 242 ms, authoritativenoyes / yesrefused-
ns5.nease.net 42.186.236.84NOERROR, 168 ms, authoritativenoyes / yesrefused-
ns6.nease.net 54.228.156.72NOERROR, 23 ms, authoritativenoyes / yesrefused-
ns8.166.com 18.182.82.158NOERROR, 249 ms, authoritativenoyes / yesrefused-
ns8.166.com 44.228.163.69NOERROR, 167 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.
  • ✓ 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 20887039 · primary ns4.nease.net

Found

Primary (MNAME)
ns4.nease.net
Contact (RNAME)
admin.nease.net
Serial
20887039
Refresh / retry
7200 s / 1800 s
Expire
1209600 s
Negative TTL
60 s

Serial per nameserver

NameserverSerial
ns1.nease.net (42.186.168.126)20887039
ns2.166.com (42.186.236.84)20887036
ns2.166.com (1.95.235.6)20887039
ns2.166.com (42.186.102.226)20887039
ns3.nease.net (182.92.22.240)20887020
ns4.nease.net (8.147.116.45)20887020
ns5.nease.net (42.186.102.226)20887039
ns5.nease.net (42.186.236.84)20887036
ns6.nease.net (54.228.156.72)20887019
ns8.166.com (18.182.82.158)20887014
ns8.166.com (44.228.163.69)20887019

Checks

  • !
    Serials differ
    The nameservers serve different versions of the zone: 20887014 on ns8.166.com (18.182.82.158); 20887019 on ns6.nease.net (54.228.156.72), ns8.166.com (44.228.163.69); 20887020 on ns3.nease.net (182.92.22.240), ns4.nease.net (8.147.116.45); 20887036 on ns2.166.com (42.186.236.84), ns5.nease.net (42.186.236.84); 20887039 on ns1.nease.net (42.186.168.126), ns2.166.com (1.95.235.6), ns2.166.com (42.186.102.226), ns5.nease.net (42.186.102.226). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.
    #22
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 2h, retry 30m, expire 14d, negative TTL 1m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns4.nease.net is one of the listed nameservers.
  • ✓ Contact admin@nease.net #25
    The SOA RNAME admin.nease.net means admin@nease.net.
  • ✓ Counter serial #26
    The serial 20887039 is a plain counter.

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

14 records at the apex

Found

Read from
42.186.168.126:53
TypeValueTTL
SOAns4.nease.net. admin.nease.net. 20887039 7200 1800 1209600 6086400
NSns3.nease.net.172800
NSns4.nease.net.172800
NSns1.nease.net.172800
NSns2.166.com.172800
NSns5.nease.net.172800
NSns6.nease.net.172800
NSns8.166.com.172800
A115.236.118.54600
MX50 yeahmx00.mxmail.netease.com.18000
MX10 yeahmx01.mxmail.netease.com.18000
TXT"9300w82jh2zwd2r8yccyqxpnyq7pljw5"300
TXT"google-site-verification=GgpoPB-rR81FZEft1rcZVIxw0DyOEJXcYecYFeOq3SQ"300
TXT"v=spf1 include:spf.mail.163.com -all"300

Checks

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