Domain report: xunlei.com

Registration

info

.com generic · Alibaba Cloud Computing (Beijing) Co., Ltd. · expires 2032-01-13

Found

TLD: .com (generic)
ICANN policies apply: yes
Registrar: Alibaba Cloud Computing (Beijing) Co., Ltd.
Registered: 13 January 2004
Last changed: 17 April 2025
Expires: 13 January 2032
Status: client transfer prohibited, client update prohibited
Registry nameservers: ns1.xunlei.net, ns2.xunlei.net, ns3.xunlei.net, ns4.xunlei.net, ns5.xunlei.net
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 2032-01-13 #3

The registration is valid until 2032-01-13 (1908 days).
✓ Transfer locked #4

Registry status: client transfer prohibited, client update prohibited.
✓ Registry and delegation match #5

The nameservers registered at the registry are the ones published in DNS.

Delegation

info

ns1.xunlei.net, ns2.xunlei.net, ns3.xunlei.net, ns4.xunlei.net, ns5.xunlei.net

Found

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

Nameserver	Addresses	Network (AS)	Glue
ns1.xunlei.net	47.106.189.11 2408:4003:1100:9702:ef17:664d:701e:47b	AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN	-
ns2.xunlei.net	39.104.185.30 2408:4004:100:2e06:5c66:3a14:1677:c50d	AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN	-
ns3.xunlei.net	110.41.172.39 2407:c080:10:13d1:2340:876c:8130:41f7	AS55990 HWCSNET - Huawei Cloud Service data center, CN AS55990 HWCSNET - Huawei Cloud Service data center, CN	-
ns4.xunlei.net	47.103.34.114 2408:4002:10c4:1f00:c015:8df:4e9c:1565	AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN	-
ns5.xunlei.net	39.98.182.239 2408:4001:20b:9600:e630:979:a6f:66b5	AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN AS37963 ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN	-

Checks

✓ 5 nameservers #6

Delegated to ns1.xunlei.net, ns2.xunlei.net, ns3.xunlei.net, ns4.xunlei.net, ns5.xunlei.net.
✓ 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 5 IPv6 /48s.
✓ 2 autonomous systems #11

The nameservers are spread over: AS37963 (ALIBABA-CN-NET - Hangzhou Alibaba Advertising Co.,Ltd., CN): 8 addresses; AS55990 (HWCSNET - Huawei Cloud Service data center, CN): 2 addresses.
i

All nameserver names under .net

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

9 of 10 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
ns1.xunlei.net 47.106.189.11	NOERROR, 208 ms, authoritative	no	no / yes	refused	[no version.]
ns1.xunlei.net 2408:4003:1100:9702:ef17:664d:701e:47b	NOERROR, 210 ms, authoritative	no	no / yes	refused	[no version.]
ns2.xunlei.net 39.104.185.30	NOERROR, 159 ms, authoritative	no	no / yes	refused	[no version.]
ns2.xunlei.net 2408:4004:100:2e06:5c66:3a14:1677:c50d	NOERROR, 149 ms, authoritative	no	no / yes	refused	[no version.]
ns3.xunlei.net 110.41.172.39	NOERROR, 200 ms, authoritative	no	no / yes	refused	[no version.]
ns3.xunlei.net 2407:c080:10:13d1:2340:876c:8130:41f7	NOERROR, 207 ms, authoritative	no	no / yes	refused	[no version.]
ns4.xunlei.net 47.103.34.114	no response	no	no / no	-	-
ns4.xunlei.net 2408:4002:10c4:1f00:c015:8df:4e9c:1565	NOERROR, 197 ms, authoritative	no	no / yes	refused	[no version.]
ns5.xunlei.net 39.98.182.239	NOERROR, 162 ms, authoritative	no	no / yes	refused	[no version.]
ns5.xunlei.net 2408:4001:20b:9600:e630:979:a6f:66b5	NOERROR, 142 ms, authoritative	no	no / yes	refused	[no version.]

Checks

✗

Nameservers not responding

These addresses did not answer, so resolvers waste time on timeouts: ns4.xunlei.net (47.103.34.114): read udp 46.225.38.91:60108->47.103.34.114: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.
i

Identifying string disclosed

These nameservers answer version queries with a string that is not a version number: ns1.xunlei.net: "[no version.]"; ns2.xunlei.net: "[no version.]"; ns3.xunlei.net: "[no version.]"; ns4.xunlei.net: "[no version.]"; ns5.xunlei.net: "[no version.]".

#17
✓ Zone transfers refused #18

No nameserver allows a zone transfer to the public.
✗

No DNS over TCP

DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns1.xunlei.net (47.106.189.11): dial tcp 47.106.189.11:53: i/o timeout; ns1.xunlei.net (2408:4003:1100:9702:ef17:664d:701e:47b): dial tcp [2408:4003:1100:9702:ef17:664d:701e:47b]:53: i/o timeout; ns2.xunlei.net (39.104.185.30): dial tcp 39.104.185.30:53: i/o timeout; ns2.xunlei.net (2408:4004:100:2e06:5c66:3a14:1677:c50d): dial tcp [2408:4004:100:2e06:5c66:3a14:1677:c50d]:53: i/o timeout; ns3.xunlei.net (110.41.172.39): dial tcp 110.41.172.39:53: i/o timeout; ns3.xunlei.net (2407:c080:10:13d1:2340:876c:8130:41f7): dial tcp [2407:c080:10:13d1:2340:876c:8130:41f7]:53: i/o timeout; ns4.xunlei.net (2408:4002:10c4:1f00:c015:8df:4e9c:1565): dial tcp [2408:4002:10c4:1f00:c015:8df:4e9c:1565]:53: i/o timeout; ns5.xunlei.net (39.98.182.239): dial tcp 39.98.182.239:53: i/o timeout; ns5.xunlei.net (2408:4001:20b:9600:e630:979:a6f:66b5): dial tcp [2408:4001:20b:9600:e630:979:a6f:66b5]:53: i/o timeout.

#19
✓ EDNS supported #20

All nameservers support EDNS(0).
✓ Public addresses #21

All nameserver addresses are publicly routable.

SOA

warn

serial 2007041108 · primary localhost

Found

Primary (MNAME): localhost
Contact (RNAME): root.localhost
Serial: 2007041108
Refresh / retry: 10800 s / 15 s
Expire: 604800 s
Negative TTL: 10800 s

Serial per nameserver

Nameserver	Serial
ns1.xunlei.net (47.106.189.11)	2007041108
ns1.xunlei.net (2408:4003:1100:9702:ef17:664d:701e:47b)	2007041108
ns2.xunlei.net (39.104.185.30)	2007041108
ns2.xunlei.net (2408:4004:100:2e06:5c66:3a14:1677:c50d)	2007041108
ns3.xunlei.net (110.41.172.39)	2007041108
ns3.xunlei.net (2407:c080:10:13d1:2340:876c:8130:41f7)	2007041108
ns4.xunlei.net (2408:4002:10c4:1f00:c015:8df:4e9c:1565)	2007041108
ns5.xunlei.net (39.98.182.239)	2007041108
ns5.xunlei.net (2408:4001:20b:9600:e630:979:a6f:66b5)	2007041108

Checks

✓ Serial 2007041108 everywhere #22

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

SOA refresh 3h, retry 15s, expire 7d, negative TTL 3h.
i

Hidden master (not resolvable)

The primary nameserver localhost is not listed as a nameserver and does not resolve publicly: a hidden master, or a placeholder name. Some tools (e.g. dynamic updates) use MNAME to find the primary.

#24
!

Invalid contact address

The SOA RNAME "root.localhost" is not a valid mailbox (expected e.g. hostmaster.example.com).

#25
✓ Date-based serial #26

The serial 2007041108 follows the YYYYMMDDnn convention (2007-04-11).

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

warn

18 records at the apex

Found

Read from: 47.106.189.11:53

Type	Value	TTL
SOA	localhost. root.localhost. 2007041108 10800 15 604800 10800	1800
NS	ns1.xunlei.net.	1800
NS	ns4.xunlei.net.	1800
NS	ns2.xunlei.net.	1800
NS	ns5.xunlei.net.	1800
NS	ns3.xunlei.net.	1800
A	112.124.227.84	60
A	121.41.61.107	60
A	39.104.2.218	60
A	39.104.99.104	60
AAAA	2400:3200:1500::55	60
AAAA	2408:4004:f8::17c	60
MX	15 mx3.xunlei.com.	60
MX	10 mx2.xunlei.com.	60
MX	5 mx1.xunlei.com.	60
TXT	"globalsign-domain-verification=ozJlGpajTp5-4YKzCfW5HzWLFI3j88IGPazut2EVEa"	1800
TXT	"globalsign-domain-verification=PzwuPIQBiVkcoS-WOFMIFpS6wpcF5uI2YTr1pwi-ft"	1800
TXT	"v=spf1 include:spf.qiye.aliyun.com -all"	1800

Checks

!

Very low TTLs

These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m), MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 30m; resolvers may use either.

#32
✓ 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