Domain report: mookuai.com

Registration

info

.com generic · eName Technology Co., Ltd. · expires 2027-04-25

Found

TLD: .com (generic)
ICANN policies apply: yes
Registrar: eName Technology Co., Ltd.
Registered: 25 April 2019
Last changed: 27 April 2026
Expires: 25 April 2027
Status: client delete prohibited, client transfer prohibited
Registry nameservers: ns3.dns.com, ns4.dns.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 2027-04-25 #3

The registration is valid until 2027-04-25 (184 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

warn

ns3.dns.com, ns4.dns.com

Found

Parent zone: com
Delegation from: a.gtld-servers.net (192.5.6.30)
NS at the parent: ns3.dns.com, ns4.dns.com
NS in the zone: ns1.ename.net, ns2.ename.net

Nameserver	Addresses	Network (AS)	Glue
ns1.ename.net (zone only)	218.98.111.173 61.158.128.31 2001:df2:f080:1::8	AS133775 CHINATELECOM-Fujian-Xiamen-IDC1 - Xiamen, CN AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS140227 HKCICL-AS-AP - Hong Kong Communications International Co., Limited, HK	-
ns2.ename.net (zone only)	1.193.216.198 211.99.99.52 183.253.57.199 240e:97d:10:1402:0:1:0:1005	AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS134763 CT-DongGuan-IDC - CHINANET Guangdong province network, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS134763 CT-DongGuan-IDC - CHINANET Guangdong province network, CN	-
ns3.dns.com (parent only)	61.158.128.31 218.98.111.173 2001:df2:f080:1::8	AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS133775 CHINATELECOM-Fujian-Xiamen-IDC1 - Xiamen, CN AS140227 HKCICL-AS-AP - Hong Kong Communications International Co., Limited, HK	2001:df2:f080:1::8 218.98.111.173 61.158.128.31
ns4.dns.com (parent only)	1.193.216.198 183.253.57.199 211.99.99.52 240e:97d:10:1402:0:1:0:1005	AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN AS134763 CT-DongGuan-IDC - CHINANET Guangdong province network, CN AS134763 CT-DongGuan-IDC - CHINANET Guangdong province network, CN	1.193.216.198 183.253.57.199 211.99.99.52 240e:97d:10:1402:0:1:0:1005

Checks

i

2 nameservers

Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns3.dns.com, ns4.dns.com.

#6
!

NS sets differ

The nameservers at the parent and in the zone should be the same. Only at the parent: ns3.dns.com, ns4.dns.com; only in the zone: ns1.ename.net, ns2.ename.net. ns1.ename.net, ns2.ename.net, ns3.dns.com, ns4.dns.com report NS ns1.ename.net ns2.ename.net.

#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.
✓ Nameservers in different networks #10

The nameservers are spread over 5 IPv4 /24s and 2 IPv6 /48s.
✓ 6 autonomous systems #11

The nameservers are spread over: AS133775 (CHINATELECOM-Fujian-Xiamen-IDC1 - Xiamen, CN): 2 addresses; AS134763 (CT-DongGuan-IDC - CHINANET Guangdong province network, CN): 4 addresses; AS140227 (HKCICL-AS-AP - Hong Kong Communications International Co., Limited, HK): 2 addresses; AS4134 (CHINANET-BACKBONE - No.31,Jin-rong Street, CN): 2 addresses; AS4837 (CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN): 2 addresses; AS9808 (CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN): 2 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

fail

12 of 14 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.ename.net 218.98.111.173	NOERROR, 208 ms, authoritative	no	yes / yes	refused	-
ns1.ename.net 61.158.128.31	NOERROR, 184 ms, authoritative	no	yes / yes	refused	-
ns1.ename.net 2001:df2:f080:1::8	no response	no	no / no	-	-
ns2.ename.net 1.193.216.198	NOERROR, 202 ms, authoritative	no	yes / yes	refused	-
ns2.ename.net 211.99.99.52	NOERROR, 193 ms, authoritative	no	yes / yes	refused	-
ns2.ename.net 183.253.57.199	NOERROR, 202 ms, authoritative	no	yes / yes	refused	-
ns2.ename.net 240e:97d:10:1402:0:1:0:1005	NOERROR, 201 ms, authoritative	no	yes / yes	refused	-
ns3.dns.com 61.158.128.31	NOERROR, 141 ms, authoritative	no	yes / yes	refused	-
ns3.dns.com 218.98.111.173	NOERROR, 205 ms, authoritative	no	yes / yes	refused	-
ns3.dns.com 2001:df2:f080:1::8	no response	no	no / no	-	-
ns4.dns.com 1.193.216.198	NOERROR, 209 ms, authoritative	no	yes / yes	refused	-
ns4.dns.com 183.253.57.199	NOERROR, 181 ms, authoritative	no	yes / yes	refused	-
ns4.dns.com 211.99.99.52	NOERROR, 200 ms, authoritative	no	yes / yes	refused	-
ns4.dns.com 240e:97d:10:1402:0:1:0:1005	NOERROR, 216 ms, authoritative	no	yes / yes	refused	-

Checks

✗

Nameservers not responding

These addresses did not answer, so resolvers waste time on timeouts: ns1.ename.net (2001:df2:f080:1::8): read udp [2a01:4f8:1c1c:eebf::1]:33426->[2001:df2:f080:1::8]:53: i/o timeout; ns3.dns.com (2001:df2:f080:1::8): read udp [2a01:4f8:1c1c:eebf::1]:46009->[2001:df2:f080:1::8]: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

pass

serial 1789105863 · primary ns1.ename.net

Found

Primary (MNAME): ns1.ename.net
Contact (RNAME): admin.ename.net
Serial: 1789105863
Refresh / retry: 3600 s / 300 s
Expire: 1209600 s
Negative TTL: 1800 s

Serial per nameserver

Nameserver	Serial
ns1.ename.net (218.98.111.173)	1789105863
ns1.ename.net (61.158.128.31)	1789105863
ns2.ename.net (1.193.216.198)	1789105863
ns2.ename.net (211.99.99.52)	1789105863
ns2.ename.net (183.253.57.199)	1789105863
ns2.ename.net (240e:97d:10:1402:0:1:0:1005)	1789105863
ns3.dns.com (61.158.128.31)	1789105863
ns3.dns.com (218.98.111.173)	1789105863
ns4.dns.com (1.193.216.198)	1789105863
ns4.dns.com (183.253.57.199)	1789105863
ns4.dns.com (211.99.99.52)	1789105863
ns4.dns.com (240e:97d:10:1402:0:1:0:1005)	1789105863

Checks

✓ Serial 1789105863 everywhere #22

All nameservers serve the same version of the zone.
✓ Timers within recommendations #23

SOA refresh 1h, retry 5m, expire 14d, negative TTL 30m.
✓ Primary is a public nameserver #24

The primary nameserver ns1.ename.net is one of the listed nameservers.
✓ Contact admin@ename.net #25

The SOA RNAME admin.ename.net means admin@ename.net.
✓ Timestamp serial #26

The serial 1789105863 is a Unix timestamp (2026-09-11 05:51 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

7 records at the apex

Found

Read from: 218.98.111.173:53

Type	Value	TTL
SOA	ns1.ename.net. admin.ename.net. 1789105863 3600 300 1209600 1800	600
NS	ns1.ename.net.	86400
NS	ns2.ename.net.	86400
A	121.46.23.98	600
MX	10 hzmx02.mxmail.netease.com.	600
MX	5 hzmx01.mxmail.netease.com.	600
TXT	"v=spf1 include:spf.163.com -all"	600

Checks

✓ TTLs within range #32

TTLs: A 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.
✓ 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