qianlong.com

Checked 22 October 2026, 10:23 UTC · via 8.8.8.8
✗Problems found
20 passed 3 warnings 2 failed 6 info

Registration

info

.com generic · Xin Net Technology Corporation · expires 2027-03-09

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
Xin Net Technology Corporation
Registered
9 March 2000
Last changed
13 July 2025
Expires
9 March 2027
Status
active
Registry nameservers
freens1.jdgslb.com, freens2.jdgslb.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-03-09 #3
    The registration is valid until 2027-03-09 (138 days).
  • i
    No transfer lock
    The domain has no transfer lock (status: active). A registrar lock protects against unauthorized transfers.
    #4
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

freens1.jdgslb.com, freens2.jdgslb.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
freens1.jdgslb.com, freens2.jdgslb.com
NS in the zone
ns1.jdgslb.com, ns2.jdgslb.com
NameserverAddressesNetwork (AS)Glue
freens1.jdgslb.com (parent only)116.196.126.18 116.198.195.0 153.36.234.88 183.134.18.114 114.67.160.144 2403:1ec0:1600:ff07::53AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS137699 CHINATELECOM-Jiangsu-Suqian-IDC - CHINATELECOM Jiangsu Suqian IDC network, CN AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS136190 CHINATELECOM-ZHEJIANG-JINHUA-IDC - JINHUA, ZHEJIANG Province, P.R.China., CN AS58466 CT-Guangzhou-IDC - CHINANET Guangdong province network, CN AS137699 CHINATELECOM-Jiangsu-Suqian-IDC - CHINATELECOM Jiangsu Suqian IDC network, CN114.67.160.144 116.196.126.18 116.198.195.0 153.36.234.88 183.134.18.114 2403:1ec0:1600:ff07::53
freens2.jdgslb.com (parent only)153.36.234.89 116.196.126.19 183.134.18.115 114.67.160.145 116.198.195.1 2403:1ec0:1600:ff07::54AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS136190 CHINATELECOM-ZHEJIANG-JINHUA-IDC - JINHUA, ZHEJIANG Province, P.R.China., CN AS58466 CT-Guangzhou-IDC - CHINANET Guangdong province network, CN AS137699 CHINATELECOM-Jiangsu-Suqian-IDC - CHINATELECOM Jiangsu Suqian IDC network, CN AS137699 CHINATELECOM-Jiangsu-Suqian-IDC - CHINATELECOM Jiangsu Suqian IDC network, CN114.67.160.145 116.196.126.19 116.198.195.1 153.36.234.89 183.134.18.115 2403:1ec0:1600:ff07::54
ns1.jdgslb.com (zone only)183.134.18.116 116.196.126.16 153.36.234.80 116.198.195.6 114.67.160.148 2403:1ec0:1600:ff07::153AS136190 CHINATELECOM-ZHEJIANG-JINHUA-IDC - JINHUA, ZHEJIANG Province, P.R.China., CN AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS137699 CHINATELECOM-Jiangsu-Suqian-IDC - CHINATELECOM Jiangsu Suqian IDC network, CN AS58466 CT-Guangzhou-IDC - CHINANET Guangdong province network, CN AS137699 CHINATELECOM-Jiangsu-Suqian-IDC - CHINATELECOM Jiangsu Suqian IDC network, CN-
ns2.jdgslb.com (zone only)183.134.18.117 116.196.126.17 153.36.234.81 116.198.195.7 114.67.160.149 2403:1ec0:1600:ff07::154AS136190 CHINATELECOM-ZHEJIANG-JINHUA-IDC - JINHUA, ZHEJIANG Province, P.R.China., CN AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN AS4837 CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN AS137699 CHINATELECOM-Jiangsu-Suqian-IDC - CHINATELECOM Jiangsu Suqian IDC network, CN AS58466 CT-Guangzhou-IDC - CHINANET Guangdong province network, CN AS137699 CHINATELECOM-Jiangsu-Suqian-IDC - CHINATELECOM Jiangsu Suqian IDC network, CN-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: freens1.jdgslb.com, freens2.jdgslb.com.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only at the parent: freens1.jdgslb.com, freens2.jdgslb.com; only in the zone: ns1.jdgslb.com, ns2.jdgslb.com. freens1.jdgslb.com, freens2.jdgslb.com, ns1.jdgslb.com, ns2.jdgslb.com report NS ns1.jdgslb.com ns2.jdgslb.com.
    #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.
  • i
    One address family in one network
    all IPv6 addresses are in 2403:1ec0:1600::/48, while the other address family is spread over several networks.
    #10
  • ✓ 5 autonomous systems #11
    The nameservers are spread over: AS136190 (CHINATELECOM-ZHEJIANG-JINHUA-IDC - JINHUA, ZHEJIANG Province, P.R.China., CN): 4 addresses; AS137699 (CHINATELECOM-Jiangsu-Suqian-IDC - CHINATELECOM Jiangsu Suqian IDC network, CN): 8 addresses; AS23724 (CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN): 4 addresses; AS4837 (CHINA169-Backbone - CHINA UNICOM China169 Backbone, CN): 4 addresses; AS58466 (CT-Guangzhou-IDC - CHINANET Guangdong province network, CN): 4 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

20 of 24 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
freens1.jdgslb.com 116.196.126.18NOERROR, 146 ms, authoritativenoyes / yesrefused-
freens1.jdgslb.com 116.198.195.0NOERROR, 161 ms, authoritativenoyes / yesrefused-
freens1.jdgslb.com 153.36.234.88NOERROR, 197 ms, authoritativenoyes / yesrefused-
freens1.jdgslb.com 183.134.18.114NOERROR, 208 ms, authoritativenono / yesrefused-
freens1.jdgslb.com 114.67.160.144NOERROR, 197 ms, authoritativenoyes / yesrefused-
freens1.jdgslb.com 2403:1ec0:1600:ff07::53NOERROR, 229 ms, authoritativenono / yesrefused-
freens2.jdgslb.com 153.36.234.89NOERROR, 161 ms, authoritativenoyes / yesrefused-
freens2.jdgslb.com 116.196.126.19NOERROR, 202 ms, authoritativenoyes / yesrefused-
freens2.jdgslb.com 183.134.18.115NOERROR, 197 ms, authoritativenono / yesrefused-
freens2.jdgslb.com 114.67.160.145NOERROR, 206 ms, authoritativenoyes / yesrefused-
freens2.jdgslb.com 116.198.195.1NOERROR, 164 ms, authoritativenoyes / yesrefused-
freens2.jdgslb.com 2403:1ec0:1600:ff07::54NOERROR, 169 ms, authoritativenono / yesrefused-
ns1.jdgslb.com 183.134.18.116no responsenono / no--
ns1.jdgslb.com 116.196.126.16NOERROR, 145 ms, authoritativenoyes / yesrefused-
ns1.jdgslb.com 153.36.234.80NOERROR, 139 ms, authoritativenoyes / yesrefused-
ns1.jdgslb.com 116.198.195.6NOERROR, 172 ms, authoritativenoyes / yesrefused-
ns1.jdgslb.com 114.67.160.148NOERROR, 197 ms, authoritativenoyes / yesrefused-
ns1.jdgslb.com 2403:1ec0:1600:ff07::153NOERROR, 169 ms, authoritativenono / yesrefused-
ns2.jdgslb.com 183.134.18.117NOERROR, 189 ms, authoritativenono / yesrefused-
ns2.jdgslb.com 116.196.126.17no responsenono / no--
ns2.jdgslb.com 153.36.234.81NOERROR, 156 ms, authoritativenoyes / yesrefused-
ns2.jdgslb.com 116.198.195.7no responsenono / no--
ns2.jdgslb.com 114.67.160.149no responsenono / no--
ns2.jdgslb.com 2403:1ec0:1600:ff07::154NOERROR, 177 ms, authoritativenono / yesrefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns1.jdgslb.com (183.134.18.116): read udp 46.225.38.91:40072->183.134.18.116:53: i/o timeout; ns2.jdgslb.com (116.196.126.17): read udp 46.225.38.91:59260->116.196.126.17:53: i/o timeout; ns2.jdgslb.com (116.198.195.7): read udp 46.225.38.91:49165->116.198.195.7:53: i/o timeout; ns2.jdgslb.com (114.67.160.149): read udp 46.225.38.91:50928->114.67.160.149: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.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: freens1.jdgslb.com (183.134.18.114): dial tcp 183.134.18.114:53: i/o timeout; freens1.jdgslb.com (2403:1ec0:1600:ff07::53): dial tcp [2403:1ec0:1600:ff07::53]:53: i/o timeout; freens2.jdgslb.com (183.134.18.115): dial tcp 183.134.18.115:53: i/o timeout; freens2.jdgslb.com (2403:1ec0:1600:ff07::54): dial tcp [2403:1ec0:1600:ff07::54]:53: i/o timeout; ns1.jdgslb.com (2403:1ec0:1600:ff07::153): dial tcp [2403:1ec0:1600:ff07::153]:53: i/o timeout; ns2.jdgslb.com (183.134.18.117): dial tcp 183.134.18.117:53: i/o timeout; ns2.jdgslb.com (2403:1ec0:1600:ff07::154): dial tcp [2403:1ec0:1600:ff07::154]:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 1784090710 · primary ns1.jdgslb.com

Found

Primary (MNAME)
ns1.jdgslb.com
Contact (RNAME)
apollo.jdgslb.com
Serial
1784090710
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
freens1.jdgslb.com (116.196.126.18)1784090710
freens1.jdgslb.com (116.198.195.0)1784090710
freens1.jdgslb.com (153.36.234.88)1784090710
freens1.jdgslb.com (183.134.18.114)1784090710
freens1.jdgslb.com (114.67.160.144)1784090710
freens1.jdgslb.com (2403:1ec0:1600:ff07::53)1784090710
freens2.jdgslb.com (153.36.234.89)1784090710
freens2.jdgslb.com (116.196.126.19)1784090710
freens2.jdgslb.com (183.134.18.115)1784090710
freens2.jdgslb.com (114.67.160.145)1784090710
freens2.jdgslb.com (116.198.195.1)1784090710
freens2.jdgslb.com (2403:1ec0:1600:ff07::54)1784090710
ns1.jdgslb.com (116.196.126.16)1784090710
ns1.jdgslb.com (153.36.234.80)1784090710
ns1.jdgslb.com (116.198.195.6)1784090710
ns1.jdgslb.com (114.67.160.148)1784090710
ns1.jdgslb.com (2403:1ec0:1600:ff07::153)1784090710
ns2.jdgslb.com (183.134.18.117)1784090710
ns2.jdgslb.com (153.36.234.81)1784090710
ns2.jdgslb.com (2403:1ec0:1600:ff07::154)1784090710

Checks

  • ✓ Serial 1784090710 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.jdgslb.com is one of the listed nameservers.
  • ✓ Contact apollo@jdgslb.com #25
    The SOA RNAME apollo.jdgslb.com means apollo@jdgslb.com.
  • ✓ Timestamp serial #26
    The serial 1784090710 is a Unix timestamp (2026-07-15 04:45 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

warn

10 records at the apex

Found

Read from
116.196.126.18:53
TypeValueTTL
SOAns1.jdgslb.com. apollo.jdgslb.com. 1784090710 10800 3600 604800 36003600
NSns1.jdgslb.com.1800
NSns2.jdgslb.com.1800
A116.198.3.111120
AAAA2403:1ec0:1200:ff88::30120
MX10 mxbiz1.qq.com.600
MX10 mxbiz2.qq.com.600
TXT"v=spf1 include:spf.mail.qq.com ~all"600
TXT"globalsign-domain-verification=9Vuh735W9r4KY0dfutAkFI_uhOX0nL010lfllQvehy"600
TXT"_globalsign-domain-verification=1XrnRmDkDruTpJ_l264v0jj--3v85XzX9iV6iHpGo9"600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (2m), AAAA (2m). 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