item.jd.com

Zone jd.com · Checked 22 October 2026, 09:22 UTC · via 8.8.8.8
✗Problems found
21 passed 5 warnings 1 failed 4 info

Registration

info

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

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
MarkMonitor Information Technology (Shanghai) Co., Ltd.
Registered
29 September 1992
Last changed
11 July 2023
Expires
8 March 2029
Status
client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited
Registry nameservers
ns1.jdcache.com, ns2.jdcache.com, ns3.jdcache.com, ns4.jdcache.com, ns5.jdcache.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 2029-03-08 #3
    The registration is valid until 2029-03-08 (867 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.jdcache.com, ns2.jdcache.com, ns3.jdcache.com, ns4.jdcache.com, ns5.jdcache.com

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.jdcache.com, ns2.jdcache.com, ns3.jdcache.com, ns4.jdcache.com, ns5.jdcache.com
NS in the zone
ns1.jd.com, ns1.jdcache.com, ns2.jd.com, ns2.jdcache.com, ns3.jd.com, ns3.jdcache.com, ns4.jd.com, ns4.jdcache.com, ns5.jd.com, ns5.jdcache.com
NameserverAddressesNetwork (AS)Glue
ns1.jd.com (zone only)111.13.28.10AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN-
ns1.jdcache.com111.13.28.10AS9808 CHINAMOBILE-CN - China Mobile Communications Group Co., Ltd., CN111.13.28.10
ns2.jd.com (zone only)111.206.226.10AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN-
ns2.jdcache.com111.206.226.10AS4808 CHINA169-BJ - China Unicom Beijing Province Network, CN111.206.226.10
ns3.jd.com (zone only)120.52.149.254AS133119 UNICOM-CN - China Unicom IP network, CN-
ns3.jdcache.com120.52.149.254AS133119 UNICOM-CN - China Unicom IP network, CN120.52.149.254
ns4.jd.com (zone only)106.39.177.32AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN-
ns4.jdcache.com106.39.177.32AS23724 CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN106.39.177.32
ns5.jd.com (zone only)120.52.149.254AS133119 UNICOM-CN - China Unicom IP network, CN-
ns5.jdcache.com120.52.149.254AS133119 UNICOM-CN - China Unicom IP network, CN120.52.149.254

Checks

  • ✓ 5 nameservers #6
    Delegated to ns1.jdcache.com, ns2.jdcache.com, ns3.jdcache.com, ns4.jdcache.com, ns5.jdcache.com.
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns1.jd.com, ns2.jd.com, ns3.jd.com, ns4.jd.com, ns5.jd.com. ns1.jd.com, ns1.jdcache.com, ns2.jd.com, ns2.jdcache.com, ns3.jd.com, ns3.jdcache.com, ns4.jdcache.com, ns5.jd.com, ns5.jdcache.com report NS ns1.jd.com ns1.jdcache.com ns2.jd.com ns2.jdcache.com ns3.jd.com ns3.jdcache.com ns4.jd.com ns4.jdcache.com ns5.jd.com ns5.jdcache.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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 4 IPv4 /24s and 0 IPv6 /48s.
  • ✓ 4 autonomous systems #11
    The nameservers are spread over: AS133119 (UNICOM-CN - China Unicom IP network, CN): 4 addresses; AS23724 (CHINANET-IDC-BJ-AP - IDC, China Telecommunications Corporation, CN): 2 addresses; AS4808 (CHINA169-BJ - China Unicom Beijing Province Network, 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

fail

9 of 10 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.jd.com 111.13.28.10NOERROR, 133 ms, authoritativenoyes / norefused-
ns1.jdcache.com 111.13.28.10NOERROR, 194 ms, authoritativenoyes / norefused-
ns2.jd.com 111.206.226.10NOERROR, 132 ms, authoritativenoyes / norefused-
ns2.jdcache.com 111.206.226.10NOERROR, 198 ms, authoritativenoyes / norefused-
ns3.jd.com 120.52.149.254NOERROR, 126 ms, authoritativenoyes / norefused-
ns3.jdcache.com 120.52.149.254NOERROR, 188 ms, authoritativenoyes / norefused-
ns4.jd.com 106.39.177.32no responsenono / no--
ns4.jdcache.com 106.39.177.32NOERROR, 159 ms, authoritativenoyes / norefused-
ns5.jd.com 120.52.149.254NOERROR, 199 ms, authoritativenoyes / norefused-
ns5.jdcache.com 120.52.149.254NOERROR, 188 ms, authoritativenoyes / norefused-

Checks

  • ✗
    Nameservers not responding
    These addresses did not answer, so resolvers waste time on timeouts: ns4.jd.com (106.39.177.32): read udp 46.225.38.91:60109->106.39.177.32: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.
  • !
    No EDNS
    These nameservers don't support EDNS(0), needed for DNSSEC and answers larger than 512 bytes: ns1.jd.com (111.13.28.10), ns1.jdcache.com (111.13.28.10), ns2.jd.com (111.206.226.10), ns2.jdcache.com (111.206.226.10), ns3.jd.com (120.52.149.254), ns3.jdcache.com (120.52.149.254), ns4.jdcache.com (106.39.177.32), ns5.jd.com (120.52.149.254), ns5.jdcache.com (120.52.149.254).
    #20
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

pass

serial 2015280403 · primary ns1.jdcache.com

Found

Primary (MNAME)
ns1.jdcache.com
Contact (RNAME)
apollo.jd.com
Serial
2015280403
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
38400 s

Serial per nameserver

NameserverSerial
ns1.jd.com (111.13.28.10)2015280403
ns1.jdcache.com (111.13.28.10)2015280403
ns2.jd.com (111.206.226.10)2015280403
ns2.jdcache.com (111.206.226.10)2015280403
ns3.jd.com (120.52.149.254)2015280403
ns3.jdcache.com (120.52.149.254)2015280403
ns4.jdcache.com (106.39.177.32)2015280403
ns5.jd.com (120.52.149.254)2015280403
ns5.jdcache.com (120.52.149.254)2015280403

Checks

  • ✓ Serial 2015280403 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 640m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.jdcache.com is one of the listed nameservers.
  • ✓ Contact apollo@jd.com #25
    The SOA RNAME apollo.jd.com means apollo@jd.com.
  • ✓ Timestamp serial #26
    The serial 2015280403 is a Unix timestamp (2033-11-11 00:06 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

19 records at the apex

Found

Read from
111.13.28.10:53
TypeValueTTL
SOAns1.jdcache.com. apollo.jd.com. 2015280403 10800 3600 604800 38400120
NSns3.jdcache.com.86400
NSns4.jdcache.com.86400
NSns5.jdcache.com.86400
NSns1.jd.com.86400
NSns2.jd.com.86400
NSns3.jd.com.86400
NSns4.jd.com.86400
NSns5.jd.com.86400
NSns1.jdcache.com.86400
NSns2.jdcache.com.86400
A211.144.27.12660
A211.144.24.21860
A111.13.149.10860
A106.39.171.13460
MX5 mx.jd.com.120
MX30 mx1.jd.com.120
TXT"v=spf1 include:a.spf.jd.com include:b.spf.jd.com include:c.spf.jd.com include:servers.mcsv.net -all"120
TXT"globalsign-domain-verification=FtLF6A52URFV2IMTamnviNHHyQDZCyAnIHhoxdb_YF"120

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), MX (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
    #32
  • ✓ 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