Domain report: suning.com

Registration

info

.com generic · eName Technology Co., Ltd. · expires 2027-12-17

Found

TLD: .com (generic)
ICANN policies apply: yes
Registrar: eName Technology Co., Ltd.
Registered: 18 December 1997
Last changed: 16 December 2025
Expires: 17 December 2027
Status: client delete prohibited, client transfer prohibited
Registry nameservers: cns1.zdnscloud.net, dns1.zdnscloud.info, ins1.zdnscloud.com, vns1.zdnscloud.biz
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-12-17 #3

The registration is valid until 2027-12-17 (420 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

pass

cns1.zdnscloud.net, dns1.zdnscloud.info, ins1.zdnscloud.com, vns1.zdnscloud.biz

Found

Parent zone: com
Delegation from: a.gtld-servers.net (192.5.6.30)
NS at the parent: cns1.zdnscloud.net, dns1.zdnscloud.info, ins1.zdnscloud.com, vns1.zdnscloud.biz
NS in the zone: cns1.zdnscloud.net, dns1.zdnscloud.info, ins1.zdnscloud.com, vns1.zdnscloud.biz

Nameserver	Addresses	Network (AS)	Glue
cns1.zdnscloud.net	42.62.2.24 42.62.2.29 2408:8719:2500:0:a::1	AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN	-
dns1.zdnscloud.info	14.116.160.20 14.29.124.15 14.116.247.213 2408:8719:2500:0:b::1	AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS4134 CHINANET-BACKBONE - No.31,Jin-rong Street, CN AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN	-
ins1.zdnscloud.com	119.167.244.44 27.221.63.3 2401:8d00:f::1	AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS38345 ZDNS - Internet Domain Name System Beijing Engineering Resrarch Center Ltd., CN	119.167.244.44 2401:8d00:f::1 27.221.63.3
vns1.zdnscloud.biz	203.99.22.3 203.99.23.3 2401:8d00:9::1	AS38345 ZDNS - Internet Domain Name System Beijing Engineering Resrarch Center Ltd., CN AS38345 ZDNS - Internet Domain Name System Beijing Engineering Resrarch Center Ltd., CN AS38345 ZDNS - Internet Domain Name System Beijing Engineering Resrarch Center Ltd., CN	-

Checks

✓ 4 nameservers #6

Delegated to cns1.zdnscloud.net, dns1.zdnscloud.info, ins1.zdnscloud.com, vns1.zdnscloud.biz.
✓ 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 8 IPv4 /24s and 3 IPv6 /48s.
✓ 4 autonomous systems #11

The nameservers are spread over: AS23724 (CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN): 2 addresses; AS38345 (ZDNS - Internet Domain Name System Beijing Engineering Resrarch Center Ltd., CN): 4 addresses; AS4134 (CHINANET-BACKBONE - No.31,Jin-rong Street, CN): 3 addresses; AS4837 (CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN): 4 addresses.
✓ Nameserver names under 4 TLDs #12

Nameserver names use the TLDs .biz, .com, .info, .net.
✓ All reachable over IPv6 #13

Every nameserver has an IPv6 address.

Nameservers

fail

12 of 13 addresses answer authoritatively

Found

Nameserver	Answer	Recursion	TCP / EDNS	AXFR	Version
cns1.zdnscloud.net 42.62.2.24	NOERROR, 135 ms, authoritative	no	yes / yes	refused	-
cns1.zdnscloud.net 42.62.2.29	NOERROR, 144 ms, authoritative	no	yes / yes	refused	-
cns1.zdnscloud.net 2408:8719:2500:0:a::1	NOERROR, 136 ms, authoritative	no	yes / yes	refused	-
dns1.zdnscloud.info 14.116.160.20	no response	no	no / no	-	-
dns1.zdnscloud.info 14.29.124.15	NOERROR, 201 ms, authoritative	no	yes / yes	refused	-
dns1.zdnscloud.info 14.116.247.213	NOERROR, 190 ms, authoritative	no	yes / yes	refused	-
dns1.zdnscloud.info 2408:8719:2500:0:b::1	NOERROR, 231 ms, authoritative	no	yes / yes	refused	-
ins1.zdnscloud.com 119.167.244.44	NOERROR, 140 ms, authoritative	no	yes / yes	refused	-
ins1.zdnscloud.com 27.221.63.3	NOERROR, 204 ms, authoritative	no	yes / yes	refused	-
ins1.zdnscloud.com 2401:8d00:f::1	NOERROR, 9 ms, authoritative	no	yes / yes	refused	-
vns1.zdnscloud.biz 203.99.22.3	NOERROR, 181 ms, authoritative	no	yes / yes	refused	-
vns1.zdnscloud.biz 203.99.23.3	NOERROR, 181 ms, authoritative	no	yes / yes	refused	-
vns1.zdnscloud.biz 2401:8d00:9::1	NOERROR, 9 ms, authoritative	no	yes / yes	refused	-

Checks

✗

Nameservers not responding

These addresses did not answer, so resolvers waste time on timeouts: dns1.zdnscloud.info (14.116.160.20): read udp 46.225.38.91:48437->14.116.160.20: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 1 · primary dns1.zdnscloud.info

Found

Primary (MNAME): dns1.zdnscloud.info
Contact (RNAME): mail.knet.cn.suning.com
Serial: 1
Refresh / retry: 3600 s / 3600 s
Expire: 3600 s
Negative TTL: 3600 s

Serial per nameserver

Nameserver	Serial
cns1.zdnscloud.net (42.62.2.24)	1
cns1.zdnscloud.net (42.62.2.29)	1
cns1.zdnscloud.net (2408:8719:2500:0:a::1)	1
dns1.zdnscloud.info (14.29.124.15)	1
dns1.zdnscloud.info (14.116.247.213)	1
dns1.zdnscloud.info (2408:8719:2500:0:b::1)	1
ins1.zdnscloud.com (119.167.244.44)	1
ins1.zdnscloud.com (27.221.63.3)	1
ins1.zdnscloud.com (2401:8d00:f::1)	1
vns1.zdnscloud.biz (203.99.22.3)	1
vns1.zdnscloud.biz (203.99.23.3)	1
vns1.zdnscloud.biz (2401:8d00:9::1)	1

Checks

✓ Serial 1 everywhere #22

All nameservers serve the same version of the zone.
!

Unusual SOA timers

retry 1h should be shorter than refresh 1h; expire 1h is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 1h must be longer than refresh + retry. Current values: refresh 1h, retry 1h, expire 1h, negative TTL 1h.

#23
✓ Primary is a public nameserver #24

The primary nameserver dns1.zdnscloud.info is one of the listed nameservers.
✓ Contact mail@knet.cn.suning.com #25

The SOA RNAME mail.knet.cn.suning.com means mail@knet.cn.suning.com.
✓ Counter serial #26

The serial 1 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

8 records at the apex

Found

Read from: 42.62.2.24:53

Type	Value	TTL
SOA	dns1.zdnscloud.info. mail.knet.cn.suning.com. 1 3600 3600 3600 3600	3600
NS	vns1.zdnscloud.biz.	3600
NS	ins1.zdnscloud.com.	3600
NS	dns1.zdnscloud.info.	3600
NS	cns1.zdnscloud.net.	3600
A	218.2.112.234	600
MX	1 mx2.zy.suning.com.	600
TXT	"v=spf1 ip4:153.3.66.59 ip4:112.80.230.253 ip4:112.80.230.219 ip4:103.255.94.61 ip4:103.255.93.131 ip4:223.68.130.222 ip4:101.125.2.215 ip4:36.152.31.2 -all"	600

Checks

✓ TTLs within range #32

TTLs: A 10m, MX 10m, NS 1h. The NS TTL at the parent is 2d and in the zone 1h; 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