Skip to content
https://www.gov.cn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
96
GRADE
A
FIX
2
REVIEW
1
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 1 REVIEW 2 FIX
D
TLS Certificate Expiry & Recommendations
Action
2 days until leaf cert expires — 4 issues to address
FIX

Certificate validity

2
days left
0d 30d 60d 90d+
Renew urgently — under 14 days remaining

Recommended actions

  • Renew certificate — 2 days remaining
  • 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
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, 31 ms lookup
REVIEW
16 A records, 31 ms lookup
Info::
Resolves to 16 IPv4 address(es)
Got: 151.242.228.62, 154.85.94.15, 154.85.94.14, 151.242.228.54, 151.242.228.56, 151.242.228.85, 154.85.94.13, 154.85.94.18, 151.242.228.61, 154.85.94.11, 151.242.228.60, 151.242.228.58, 154.85.94.16, 154.85.94.12, 151.242.228.59, 154.85.94.17
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2407:2440:e00f::14, 2407:2440:e00f::17, 2407:2440:e00f::13, 2407:2440:e00f::11, 2407:2440:e00f::16, 2407:2440:e00f::15, 2407:2440:e00f::18, 2407:2440:e00f::12
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.gov.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: 31 ms
Got: 31 ms
A151.242.228.62, 154.85.94.15, 154.85.94.14, 151.242.228.54, 151.242.228.56, 151.242.228.85, 154.85.94.13, 154.85.94.18, 151.242.228.61, 154.85.94.11, 151.242.228.60, 151.242.228.58, 154.85.94.16, 154.85.94.12, 151.242.228.59, 154.85.94.17
AAAA2407:2440:e00f::14, 2407:2440:e00f::17, 2407:2440:e00f::13, 2407:2440:e00f::11, 2407:2440:e00f::16, 2407:2440:e00f::15, 2407:2440:e00f::18, 2407:2440:e00f::12
CNAMEwww.gov.cn.bsgslb.cn
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 31 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)

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.gov.cn

https://www.gov.cn

74 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.gov.cn20074 msHTTP/1.1
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::17, 2407:2440:e00f::13, 2407:2440:e00f::11, 2407:2440:e00f::16, 2407:2440:e00f::15, 2407:2440:e00f::18, 2407:2440:e00f::12
Got: 25 ms connect
IPv6 Ready
AAAA Records 2407:2440:e00f::14, 2407:2440:e00f::17, 2407:2440:e00f::13, 2407:2440:e00f::11, 2407:2440:e00f::16, 2407:2440:e00f::15, 2407:2440:e00f::18, 2407:2440:e00f::12 Connection Reachable (25 ms)
A+
Crawlability
robots.txt present, sitemap with 100 URLs
PASS
robots.txt present, sitemap with 100 URLs
Info::
robots.txt is present
Got: 811 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 100 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 811 B Sitemaps referenced 4 User-agents Blocking No — crawling allowed
User-agent: * 
Allow: /1

Sitemap:http://www.gov.cn/baidu.xml 

Sitemap:http://www.gov.cn/google.xml

Sitemap:http://www.gov.cn/bing.xml

Sitemap:http://www.gov.cn/sogou.xml

Disallow:/2016gov/

Disallow:/2016shuju/

Disallow:/2016guoqing/

Disallow:/2016zhengce/

Disallow:/2016hudong/

Disallow:/2016fuwu/

Disallow:/2016xinwen/

Disallow:/premier/

Disallow:/2016guowuyuan/

Disallow:/2016public/

Disallow:/2016ducha/

Disallow:/guowuyuan/yangjing/

Disallow:/guowuyuan/yj.htm

Disallow:/c16629/gwyld_yj.htm

Disallow:/guowuyuan/yj_hy.htm

Disallow:/guoqing/2013-03/16/content_2583121.htm

Disallow:/guowuyuan/2015-12/24/content_5027563.htm

Disallow:/zhuanti/2014-04/02/content_2823336.htm

Disallow:/zmyw201202b/

Disallow:/zmyw201212c/

Disallow:/ldhd/wjb/tp.htm

Disallow:/guowuyuan/zl_gallery03.htm
sitemap.xml 200 OK
Type URL Set URLs 100 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.gov.cn/
https://gov.cn/

HTTP → HTTPS

301http://www.gov.cn/ → https://www.gov.cn/

Consistent

A+
Domain Intelligence
www.gov.cn — via 北京国旭网络科技有限公司, 27 years, 9 months old
PASS
www.gov.cn — via 北京国旭网络科技有限公司, 27 years, 9 months old
Info::
Domain registered until Sep 14, 2027 (1 years, 5 months remaining)
Info::
Registrar: 北京国旭网络科技有限公司
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Domain expiry

427 days

September 14, 2027

SSL certificate

2 days

Issued by China Financial Certification Authority

Domain age

27 years, 9 months

Registered December 4, 1998

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2407:2440:e00f::16

Registrar

北京国旭网络科技有限公司

Locked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
Registrar 北京国旭网络科技有限公司
Created December 4, 1998 (27 years, 9 months ago)
Expires September 14, 2027 (1 years, 5 months)
Name Servers ns1.cdns.cn, ns2.cdns.cn, ns3.cdns.cn
Hosting
IP Address 2407:2440:e00f::16
Data source: whois (0.9s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

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

Connection waterfall

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

Send Feedback