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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 3 REVIEW 2 FIX
D
HTTP Probe Timing
Action
Total 2589 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
1.57 s
TCP Connect TCP Connect — time to establish a TCP connection to the server.
214 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
231 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
2.33 s
Total Time Total request time from DNS lookup through full response.
2.59 s

Connection waterfall

DNS Lookup 1.57 s TCP Connect 214 ms TLS Handshake 231 ms Server Processing 316 ms Content Transfer 258 ms
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
2 A records, 309 ms lookup
REVIEW
2 A records, 309 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 27.155.113.155, 116.211.128.150
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2409:8c04:1101:3050::406, 240e:95c:806:40::422
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: ce5c4cf757a9a3e1.cname.365cyd.cn
Info::
6 nameserver(s) configured
Got: ns2.365cyd.net, ns1.kangdns.com, ns1.365cyd.net, ns2.jiasule.net, ns2.kangdns.com, ns1.jiasule.net
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'.
Warning::
DNS resolution is slow (309 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 309 ms
A27.155.113.155, 116.211.128.150
AAAA2409:8c04:1101:3050::406, 240e:95c:806:40::422
CNAMEce5c4cf757a9a3e1.cname.365cyd.cn
NSns2.365cyd.net, ns1.kangdns.com, ns1.365cyd.net, ns2.jiasule.net, ns2.kangdns.com, ns1.jiasule.net
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 309 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)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

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 403 Expected: 301 redirect to HTTPS

www / non-www

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

HTTP → HTTPS

403http://www.beijing.gov.cn/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.beijing.gov.cn

https://www.beijing.gov.cn

736 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.beijing.gov.cn200736 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (170 ms)
PASS
IPv6 reachable (170 ms)
Info::
IPv6 is configured and reachable at 2409:8c04:1101:3050::406, 240e:95c:806:40::422
Got: 170 ms connect
IPv6 Ready
AAAA Records 2409:8c04:1101:3050::406, 240e:95c:806:40::422 Connection Reachable (170 ms)
A+
Crawlability
robots.txt present, sitemap with 125 URLs
PASS
robots.txt present, sitemap with 125 URLs
Info::
robots.txt is present
Got: 345 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 125 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 345 B Sitemaps referenced 5 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow:/sd


Sitemap: http://www.beijing.gov.cn/sitemap_1701.xml

Sitemap: http://www.beijing.gov.cn/hudong/jianyi/sitemap.xml

Sitemap: https://www.beijing.gov.cn/hudong/wsdc/sitemap_42374.xml

Sitemap: https://www.beijing.gov.cn/hudong/hdjl/common/site/hdjl/sitemap.xml

Sitemap: http://www.beijing.gov.cn/shipin/sitemaps.xml
sitemap.xml 200 OK
Type URL Set URLs 125 entries Valid XML Yes
Sample URLs:
A
Domain Intelligence
beijing.gov.cn — via 北京首信网创网络信息服务有限责任公司, 28 years, 3 months old, hosted on CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited, CN
PASS
beijing.gov.cn — via 北京首信网创网络信息服务有限责任公司, 28 years, 3 months old, hosted on CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited, CN
Warning::
Domain expires in 47 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 9, 2026
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: CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited, CN
Got: AS24547
Domain expiry

EXPIRED

June 9, 2026

SSL certificate

176 days

Issued by Beijing Xinchacha Credit Management Co., Ltd.

Domain age

28 years, 3 months

Registered June 9, 1998

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited, CN

ASN AS24547

111.62.149.162

Registrar

北京首信网创网络信息服务有限责任公司

Unlocked 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar 北京首信网创网络信息服务有限责任公司
Created June 9, 1998 (28 years, 3 months ago)
Expires June 9, 2026 (1 months)
Name Servers ns1.cdns.cn, ns2.cdns.cn, ns3.cdns.cn
Hosting
IP Address 111.62.149.162
ASN AS24547 (CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited, CN)
Provider CMNET-V4HEBEI-AS-AP Hebei Mobile Communication Company Limited, CN
Data source: whois (2.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback