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.
BDNS Records1 A records, 40 ms lookupREVIEW
| A | 101.37.44.198 |
| AAAA | — |
| CNAME | zyqyop6nc7c2yjw0rqgktefak7l9rvwq.yundunwaf.com |
| NS | — |
| MX | — |
| TXT | — |
| 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
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.
Learn more ▾ ▴
RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.
Source: RFC 1034
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.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
BRedirect Chain1 redirect(s), 2125 ms totalREVIEW
https://wjx.cn
882 ms · HTTP/1.1
https://www.wjx.cn/
1243 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://wjx.cn | 301 | 882 ms | HTTP/1.1 | |
| 2 | https://www.wjx.cn/ | 200 | 1243 ms | HTTP/1.1 |
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
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: *
Disallow: /BcCustomer/
Disallow: /CorpHome/
Disallow: /customerservices/
Disallow: /Error/
Disallow: /handler/
Disallow: /Handler/
Disallow: /Html/EmailTemplate/
Disallow: /JoinActivity/
Disallow: /Jump/
Disallow: /Market/
Disallow: /Modules/
Disallow: /MySojump/
Disallow: /MyTribes/
Disallow: /PersonHome/
Disallow: /register/
Disallow: /Remark/
Disallow: /Services/
Disallow: /WJX/Join/
Disallow: /wjx/join/
Disallow: /WJX/report/
Disallow: /wjx/activitystat/viewstatsummary.aspx
Disallow: /wjx/activitystat/viewstatbyq.aspx
Disallow: /wjx/collect.aspx
Disallow: /wjx/printq.aspx
Disallow: /GotoBC.aspx
Disallow: /gotobclocation.aspx
Disallow: /wjx/activitystat/
Disallow: /gift/
Disallow: /taobao/
Disallow: /wjx/previewq.aspx
Disallow: /mobile/previewq.aspx
Disallow: /mysojump/previewfull.aspx
Disallow: /wjx/join/tpresult.aspx
Disallow: /wjx/join/complete.aspx
Disallow: /wjx/join/completemobile2.aspx
Disallow: /sample/succase.aspx?keyword=
Disallow: /help/help.aspx?keyword=
Disallow: /lib.aspx
Disallow: /newwjx/mysojump/newselecttemplete.aspx?keyword=
Disallow: /newsojiang/
Disallow: /index.aspx
Disallow: /redirect.aspx
Disallow: /urlreport.aspx
Disallow: /wjx/checkstatus.aspx
Disallow: /corplogin.aspx
Disallow: /mobile/corplogin.aspx
Disallow: /connectnew.aspx
Disallow: /joinnew/processjq.ashx
Disallow: /newwjx/design/
Disallow: /wjx/design/
Disallow: /libt/unblockip.aspx
Disallow: /report/
Disallow: /help/unblockip.aspx
Disallow: /vm/*.aspx?*
Disallow: /mobile/statnew.aspx
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
BHTTP Probe TimingTotal 1144 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations306 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- 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+Domain Intelligencewjx.cn — via 阿里云计算有限公司（万网）, 21 years, 4 months old, hosted on Alibaba CloudPASS
293 days
April 4, 2027
306 days
Issued by DigiCert Inc
21 years, 4 months
Registered April 4, 2005
Status unknown
Protects against DNS spoofing
Alibaba Cloud
ASN AS37963
101.37.44.198
阿里云计算有限公司（万网）
Expiry timeline
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.
Source: ICANN / domain-security best practice