Skip to content
https://china.com.cn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNS Records
16 A records, 32 ms lookup
REVIEW
16 A records, 32 ms lookup
Info::
Resolves to 16 IPv4 address(es)
Got: 151.242.228.54, 151.242.228.85, 154.85.94.17, 154.85.94.11, 151.242.228.58, 154.85.94.16, 151.242.228.60, 151.242.228.62, 154.85.94.18, 151.242.228.56, 154.85.94.13, 151.242.228.59, 154.85.94.12, 154.85.94.15, 151.242.228.57, 151.242.228.61
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2407:2440:e00f::14, 2407:2440:e00f::11, 2407:2440:e00f::15, 2407:2440:e00f::18, 2407:2440:e00f::12, 2407:2440:e00f::16, 2407:2440:e00f::17, 2407:2440:e00f::13
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www.china.com.cn.bsgslb.cn
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 32 ms
Got: 32 ms
A151.242.228.54, 151.242.228.85, 154.85.94.17, 154.85.94.11, 151.242.228.58, 154.85.94.16, 151.242.228.60, 151.242.228.62, 154.85.94.18, 151.242.228.56, 154.85.94.13, 151.242.228.59, 154.85.94.12, 154.85.94.15, 151.242.228.57, 151.242.228.61
AAAA2407:2440:e00f::14, 2407:2440:e00f::11, 2407:2440:e00f::15, 2407:2440:e00f::18, 2407:2440:e00f::12, 2407:2440:e00f::16, 2407:2440:e00f::17, 2407:2440:e00f::13
CNAMEwww.china.com.cn.bsgslb.cn
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 32 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

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.

Why this matters

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'.

Why this matters

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)

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

200https://www.china.com.cn/
https://china.com.cn/

HTTP → HTTPS

200http://www.china.com.cn/

HTTP version does not redirect to HTTPS

B
TLS Certificate Expiry & Recommendations
315 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

315
days left
0d 30d 60d 90d+

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
A
Redirect Chain
1 redirect(s), 268 ms total
PASS
1 redirect(s), 268 ms total
Info::
Single redirect
Got: https://www.china.com.cn → http://www.china.com.cn/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.china.com.cn

https://www.china.com.cn

7 ms · HTTP/1.1

302

http://www.china.com.cn/

262 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.china.com.cn3027 msHTTP/1.1web cache
2http://www.china.com.cn/200262 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

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

A+
IPv6 Readiness
IPv6 reachable (25 ms)
PASS
IPv6 reachable (25 ms)
Info::
IPv6 is configured and reachable at 2407:2440:e00f::14, 2407:2440:e00f::11, 2407:2440:e00f::15, 2407:2440:e00f::18, 2407:2440:e00f::12, 2407:2440:e00f::16, 2407:2440:e00f::17, 2407:2440:e00f::13
Got: 25 ms connect
IPv6 Ready
AAAA Records 2407:2440:e00f::14, 2407:2440:e00f::11, 2407:2440:e00f::15, 2407:2440:e00f::18, 2407:2440:e00f::12, 2407:2440:e00f::16, 2407:2440:e00f::17, 2407:2440:e00f::13 Connection Reachable (25 ms)
A+
Crawlability
robots.txt present, sitemap with 443 URLs
PASS
robots.txt present, sitemap with 443 URLs
Info::
robots.txt is present
Got: 84 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 443 entries
Info::
Sitemap index with 443 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 84 B Sitemaps referenced 0 User-agents *, Googlebot Blocking No — crawling allowed
User-agent: *

Allow: /


User-agent: Googlebot

Disallow: /rollnews/

Allow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 443 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
china.com.cn — via 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）, 28 years, 3 months old, hosted on CHINA169-BJ China Unicom Beijing Province Network, CN
PASS
china.com.cn — via 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）, 28 years, 3 months old, hosted on CHINA169-BJ China Unicom Beijing Province Network, CN
Info::
Domain registered until Jun 9, 2029 (3 years, 2 months remaining)
Info::
Registrar: 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: CHINA169-BJ China Unicom Beijing Province Network, CN
Got: AS4808
Domain expiry

1059 days

June 9, 2029

SSL certificate

315 days

Issued by GlobalSign nv-sa

Domain age

28 years, 3 months

Registered June 9, 1998

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CHINA169-BJ China Unicom Beijing Province Network, CN

ASN AS4808

202.130.245.42

Registrar

北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）
Created June 9, 1998 (28 years, 3 months ago)
Expires June 9, 2029 (3 years, 2 months)
Name Servers cl1.sfndns.cn, cl2.sfndns.cn, cl1.sfndns.com, cl2.sfndns.com, ns1.china.org.cn, ns1.china-online.com.cn
Hosting
IP Address 202.130.245.42
ASN AS4808 (CHINA169-BJ China Unicom Beijing Province Network, CN)
Provider CHINA169-BJ China Unicom Beijing Province Network, CN
Data source: whois (1.2s)

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.

Why this matters

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

A
HTTP Probe Timing
Total 653 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
585 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
20 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
26 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
653 ms
Total Time Total request time from DNS lookup through full response.
654 ms

Connection waterfall

DNS Lookup 585 ms TCP Connect 20 ms TLS Handshake 26 ms Server Processing 22 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback