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.
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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations81 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+DNS Records1 A records, 10 ms lookupPASS
| A | 43.159.189.25 |
| AAAA | — |
| CNAME | — |
| NS | vip4.alidns.com, vip3.alidns.com |
| MX | 5 mx1.qiye.aliyun.com 10 mxn.mxhichina.com 15 mxw.mxhichina.com |
| TXT | _uv0xmop45gnztrtz1awfp8k9vccvf63 sending_domain285052=c1c182b2ed6c252943760241deb2bbe34fef188150b287f19d50df80fc1... MS=ms94937877 pardot285052=7fa01c1ec735d39fd20c4e9037eea474dd27721d5b4f78504dbd91c7af5845d8 MS=ms48273969 google-site-verification=aINDeUEDYUSX9iSSfD3KGMY-JzJ13DthYDLxNhdaYAg tiktok-developers-site-verification=fm33sUVmG9RvSyd2dDkFr0Cqa2ubNcUU SPF v=spf1 include:spf.mxhichina.com include:mail.zendesk.com include:aspmx.pardot.c... v=spf2.0/pra include:spf.mxhichina.com include:mail.zendesk.com include:aspmx.pa... tiktok-developers-site-verification=yEW7DhJfXCuE7rzKfpJUJzrjp0OWpWPC _vap8ugaaavbalzfjfcmuwax8szzl2zl google-site-verification=uF2LxdoSZjSmCuRoMQrrBuQ2tUZkW57q4v1CZ6XN_RE |
| 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.
ARedirect Chain1 redirect(s), 591 ms totalPASS
https://wondershare.com
565 ms · HTTP/1.1
https://www.wondershare.com/
26 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://wondershare.com | 301 | 565 ms | HTTP/1.1 | nginx |
| 2 | https://www.wondershare.com/ | 200 | 26 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 60 URLsPASS
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: /news/
Disallow: /thankyou/
Disallow: /survey/
Disallow: /(.*)\.csv$
A+Domain Intelligencewondershare.com — via Xiamen 35.com Information Co., Ltd., 22 years, 11 months old, hosted on Tencent CloudPASS
1555 days
September 17, 2030
81 days
Issued by DigiCert, Inc.
22 years, 11 months
Registered September 17, 2003
Not enabled
Protects against DNS spoofing
Tencent Cloud
ASN AS132203
43.159.189.25
Xiamen 35.com Information 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