Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSFIX
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
HTTP version does not redirect to HTTPS
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 2231 ms totalREVIEW
https://163.com
987 ms · HTTP/1.1
http://www.163.com/
1243 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://163.com | 301 | 987 ms | HTTP/1.1 | nginx |
| 2 | http://www.163.com/ | 200 | 1243 ms | HTTP/1.1 | Tengine |
See the visual redirect chain in the HTTP Probe tab →
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
CCrawlabilityActionrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
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.
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.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent:*
Disallow: /special/0077sp
Disallow: /special/00774J29
Disallow: /special/00774IG5
Disallow: /a11y/video/
Disallow: /special/007797UO/index_a11y
Disallow: /article/*_pa11y.html
Disallow: /dy/article/*_pdya11y.html
BHTTP Probe TimingTotal 1119 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
CTLS Certificate Expiry & RecommendationsAction15 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Renew certificate — 15 days remaining
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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 Records1 A records, 40 ms lookupPASS
| A | 59.111.160.244 |
| AAAA | — |
| CNAME | — |
| NS | ns4.nease.net, ns3.nease.net, ns6.nease.net, ns2.166.com, ns1.nease.net, ns5.nease.net, ns8.166.com |
| MX | 10 163mx03.mxmail.netease.com 10 163mx02.mxmail.netease.com 10 163mx01.mxmail.netease.com 50 163mx00.mxmail.netease.com |
| TXT | 0hz8zn8jpkr3vffgll8hnd6j873bzvsg 57c23e6c1ed24f219803362dadf8dea3 facebook-domain-verification=kqgnezlldheaauy9huiesb3j2emhh3 qdx50vkxg6qpn3n1k6n1tg2syg5wp96y google-site-verification=hRXfNWRtd9HKlh-ZBOuUgGrxBJh526R8Uygp0jEZ9wY SPF v=spf1 include:spf.mail.163.com -all |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
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+Domain Intelligence163.com — via MarkMonitor Information Technology (Shanghai) Co., Ltd., 29 years old, hosted on NETEASE-NETWORK NetEase Building No.16 Ke Yun Road, CNPASS
455 days
September 14, 2027
15 days
Issued by DigiCert, Inc.
29 years
Registered September 15, 1997
Not enabled
Protects against DNS spoofing
NETEASE-NETWORK NetEase Building No.16 Ke Yun Road, CN
ASN AS45062
59.111.160.244
MarkMonitor Information Technology (Shanghai) Co., Ltd.
Expiry timeline
Recommended actions
- Renew the TLS certificate or verify auto-renewal is working
- 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