Skip to content
https://jd.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
77
GRADE
C
FIX
2
REVIEW
4
PASS
3
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 4 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1681 ms total
FIX
2 redirect(s), 1681 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1681 ms total
Got: 1681 ms
Info::
Cross-domain redirect detected

https://jd.com

804 ms · HTTP/1.1

301

https://www.jd.com

445 ms · HTTP/1.1

301

https://global.jd.com

432 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://jd.com301804 msHTTP/1.1jfe
2https://www.jd.com301445 msHTTP/1.1nginx
3https://global.jd.com200432 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 786 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 786 B Sitemaps referenced 0 User-agents Sogou Pic Spider, Sosoimagespider, Googlebot-Mobile, Googlebot-News, Bingbot, Baiduspider-image, YandexBot, YandexBot-Image, Sogou web spider, *, msnbot, Baiduspider, Baiduspider-video, YandexBot-Mobile, HaosouSpider, Sosospider, Googlebot-Video, bingbot-mobile, 360Spider, Googlebot, Googlebot-Image Blocking No — crawling allowed
User-agent: *
Disallow: /*?

User-agent: Googlebot
Allow: /*?

User-agent: Googlebot-Image
Allow: /*?

User-agent: Googlebot-Mobile
Allow: /*?

User-agent: Googlebot-Video
Allow: /*?

User-agent: Googlebot-News
Allow: /*?

User-agent: Bingbot
Allow: /*?

User-agent: msnbot
Allow: /*?

User-agent: bingbot-mobile
Allow: /*?

User-agent: Baiduspider
Allow: /*?

User-agent: Baiduspider-image
Allow: /*?

User-agent: Baiduspider-video
Allow: /*?

User-agent: YandexBot
Allow: /*?

User-agent: YandexBot-Image
Allow: /*?

User-agent: YandexBot-Mobile
Allow: /*?

User-agent: Sogou web spider
Allow: /*?

User-agent: Sogou Pic Spider
Allow: /*?

User-agent: 360Spider
Allow: /*?

User-agent: HaosouSpider
Allow: /*?

User-agent: Sosoimagespider
Allow: /*?

User-agent: Sosospider
Allow: /*?
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
HTTP Probe Timing
Total 1103 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
331 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
256 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
258 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.10 s
Total Time Total request time from DNS lookup through full response.
1.10 s

Connection waterfall

DNS Lookup 331 ms TCP Connect 256 ms TLS Handshake 258 ms Server Processing 259 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
242 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

242
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
4 A records, 332 ms lookup
PASS
4 A records, 332 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 111.13.149.108, 211.144.27.126, 106.39.171.134, 211.144.24.218
Info::
No IPv6 (AAAA) records
Info::
10 nameserver(s) configured
Got: ns5.jdcache.com, ns4.jdcache.com, ns3.jdcache.com, ns2.jd.com, ns5.jd.com, ns3.jd.com, ns1.jd.com, ns2.jdcache.com, ns1.jdcache.com, ns4.jd.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (332 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 332 ms
A111.13.149.108, 211.144.27.126, 106.39.171.134, 211.144.24.218
AAAA—
CNAME—
NSns5.jdcache.com, ns4.jdcache.com, ns3.jdcache.com, ns2.jd.com, ns5.jd.com, ns3.jd.com, ns1.jd.com, ns2.jdcache.com, ns1.jdcache.com, ns4.jd.com
MX
5 mx.jd.com
30 mx1.jd.com
TXT
SPF v=spf1 include:a.spf.jd.com include:b.spf.jd.com include:c.spf.jd.com include:se...
globalsign-domain-verification=7h908mlOENh4mcee5W-YF0dBGVAPaacba54ym0cBCZ
CAALookup not available with standard resolver
Resolved in 332 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.jd.com/
200https://jd.com/

Preferred variant: non-www

HTTP → HTTPS

301http://jd.com/ → https://www.jd.com

Consistent

A+
Domain Intelligence
jd.com — via MarkMonitor Information Technology (Shanghai) Co., Ltd., 34 years old, hosted on CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
PASS
jd.com — via MarkMonitor Information Technology (Shanghai) Co., Ltd., 34 years old, hosted on CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
Info::
Domain registered until Mar 8, 2029 (2 years, 11 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Information Technology (Shanghai) Co., Ltd.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
Got: AS23724
Domain expiry

968 days

March 8, 2029

SSL certificate

242 days

Issued by GlobalSign nv-sa

Domain age

34 years

Registered September 29, 1992

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN

ASN AS23724

106.39.171.134

Registrar

MarkMonitor Information Technology (Shanghai) Co., Ltd.

Unlocked 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Information Technology (Shanghai) Co., Ltd.
Created September 29, 1992 (34 years ago)
Expires March 8, 2029 (2 years, 11 months)
Last Updated July 11, 2023
Name Servers ns1.jdcache.com, ns2.jdcache.com, ns3.jdcache.com, ns4.jdcache.com, ns5.jdcache.com
DNSSEC Not enabled
Hosting
IP Address 106.39.171.134
ASN AS23724 (CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN)
Provider CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback