Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 1461 ms totalREVIEW
https://taobao.com
1447 ms · HTTP/1.1
https://www.taobao.com/
14 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://taobao.com | 302 | 1447 ms | HTTP/1.1 | Tengine |
| 2 | https://www.taobao.com/ | 200 | 14 ms | HTTP/1.1 | Tengine |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Allow: /list/*
Allow: /list/*?*
Disallow: /*?*
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations52 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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 Records8 A records, 4 ms lookupPASS
| A | 59.82.43.238, 59.82.122.130, 59.82.121.163, 59.82.122.165, 59.82.43.239, 59.82.122.140, 59.82.43.234, 59.82.44.240 |
| AAAA | 2401:b180:7003::6b, 2408:4001:f00::87, 2408:4001:f00::3c, 2408:4001:f10::5e, 2401:b180:7003::ed, 2401:b180:7003::aa, 2408:4001:f10::6f, 2401:b180:7003::25 |
| CNAME | — |
| NS | ns7.taobao.com, ns6.taobao.com, ns5.taobao.com, ns4.taobao.com |
| MX | 10 mx1.alibaba-inc.com |
| TXT | _globalsign-domain-verification=JNpwvJzKKvMJrVnfZgS_-8rP63UaHHp3AzQgCt_vzf SPF v=spf1 include:spf1.staff.mail.aliyun.com -all google-site-verification=NcvM6FnQshEU6o8Gfh9ltaJBbeIK3IvTHFov3cBgbnQ 5hrp21wwcjlvc2s1nhy8mmptb5tcdv7q verify_03bb39867a788339b1430997a40e273c |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+IPv6 ReadinessIPv6 reachable (293 ms)PASS
A+Domain Intelligencetaobao.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 23 years, 3 months oldPASS
1405 days
April 21, 2030
52 days
Issued by GlobalSign nv-sa
23 years, 3 months
Registered April 21, 2003
Not enabled
Protects against DNS spoofing
Unknown
2401:b180:7003::6b
Alibaba Cloud Computing (Beijing) Co., Ltd.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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