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 Records2 A records, 34 ms lookupREVIEW
| A | 163.171.135.102, 163.171.135.63 |
| AAAA | 2a01:53c0:ff07:ffff::1a |
| CNAME | www.chinanews.com.wscdns.com |
| NS | — |
| MX | — |
| TXT | — |
| CAA | Lookup not available with standard resolver |
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)
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BHTTP Probe TimingTotal 834 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations150 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
ARedirect Chain1 redirect(s), 276 ms totalPASS
https://chinanews.com
8 ms · HTTP/1.1
https://www.chinanews.com.cn/
268 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://chinanews.com | 301 | 8 ms | HTTP/1.1 | nginx |
| 2 | https://www.chinanews.com.cn/ | 200 | 268 ms | HTTP/1.1 | nginx |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 21 URLsPASS
User-agent: *
Allow: /
Sitemap:http://www.chinanews.com/sitemap.xml
Disallow: /AboutUs/Staff/
Disallow: /part/
Disallow: /iframe/
Disallow: /test
Disallow: /ceshi/
Disallow: /ad/
Disallow: /ad2008/
Disallow: /jingwei/
Disallow: /html/jw/
Disallow: /sc.html
Disallow: /znh.html
Disallow: /hg.html
Disallow: /jr.html
Disallow: /zq.html
Disallow: /lc.html
Disallow: /zb/index.html
Disallow: /sj.html
Disallow: /fc.html
Disallow: /kj.html
Disallow: /qc.html
Disallow: /jwmj.html
Disallow: /original.html
Disallow: /renwen.html
Disallow: /rw.html
Disallow: /wc.html
Disallow: /kb.html
Disallow: /jw/
Disallow: /jingwei.html
Disallow: /code/
Disallow: /m/code/
Disallow: /34/2017/
Disallow: /34/2018/
Disallow: /34/2019/
Disallow: /upload_pic/
Disallow: /ztlm/37/
Disallow: /m/px/46/
Disallow: /px/46/
Disallow: /history/
A+Domain Intelligencechinanews.com — via Xin Net Technology Corporation, 31 years, 4 months oldPASS
301 days
May 14, 2027
150 days
Issued by DigiCert, Inc.
31 years, 4 months
Registered May 13, 1995
Not enabled
Protects against DNS spoofing
Unknown
2a01:53c0:ff07:ffff::1a
Xin Net Technology Corporation
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