Skip to content
https://xinyong.boai.gov.cn

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
3
REVIEW
9
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
5 PASS 9 REVIEW 3 FIX
D
Multi-Resolver DNS Speed
Action
Mean 458ms across 3 resolvers (spread 185ms)
FIX
Mean 458ms across 3 resolvers (spread 185ms)
Info::
Google: 337ms
Got: 337ms via 8.8.8.8:53
Info::
Quad9: 516ms
Got: 516ms via 9.9.9.9:53
Info::
Cloudflare: 522ms
Got: 522ms via 1.1.1.1:53
F
HTTP Probe Timing
Action
Total 14333 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
1.32 s
TCP Connect TCP Connect — time to establish a TCP connection to the server.
180 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
365 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
14.33 s
Total Time Total request time from DNS lookup through full response.
14.33 s

Connection waterfall

DNS Lookup 1.32 s TCP Connect 180 ms TLS Handshake 365 ms Server Processing 12.47 s Content Transfer 1 ms
D
CDN & Delivery
Action
No CDN (document or assets)
FIX
No CDN (document or assets)
Warning::
No CDN (document or assets)
Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN (document or assets)

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

B
DNS Records
1 A records, 1119 ms lookup
REVIEW
1 A records, 1119 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 124.42.8.135
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 240a:2001:1811:2007::88
Info::
No NS records found
Info::
No MX records — email not configured via DNS
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 (1119 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1119 ms
A124.42.8.135
AAAA240a:2001:1811:2007::88
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 1119 ms

Multiple A records provide failover if one server goes down.

Why this matters

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

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
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 124.42.8.135: lookup 124.42.8.135: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 240a:2001:1811:2007::88: lookup 240a:2001:1811:2007::88: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
C
Crawlability
Action
no robots.txt, sitemap with 0 URLs
REVIEW
no robots.txt, sitemap with 0 URLs
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
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 0 Expected: 301 redirect to HTTPS

www / non-www

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

HTTP → HTTPS

http://xinyong.boai.gov.cn/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirect data available
PASS
No redirect data available
Info::
No redirect data captured
A+
IPv6 Readiness
IPv6 reachable (181 ms)
PASS
IPv6 reachable (181 ms)
Info::
IPv6 is configured and reachable at 240a:2001:1811:2007::88
Got: 181 ms connect
IPv6 Ready
AAAA Records 240a:2001:1811:2007::88 Connection Reachable (181 ms)
A+
Domain Intelligence
boai.gov.cn — via 北京新网数码信息技术有限公司, 18 years, 1 months old
PASS
boai.gov.cn — via 北京新网数码信息技术有限公司, 18 years, 1 months old
Info::
Domain registered until Dec 2, 2027 (1 years, 1 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.
Domain expiry

407 days

December 2, 2027

SSL certificate

102 days

Issued by DigiCert Inc

Domain age

18 years, 1 months

Registered December 2, 2008

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

Registrar

北京新网数码信息技术有限公司

Unlocked 2 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 December 2, 2008 (18 years, 1 months ago)
Expires December 2, 2027 (1 years, 1 months)
Name Servers ns15.xincache.com, ns16.xincache.com
Data source: whois (2.0s)

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+
Health Check Endpoint
Health endpoint at https://xinyong.boai.gov.cn/health (HTTP 200)
PASS
Health endpoint at https://xinyong.boai.gov.cn/health (HTTP 200)
Info::
Public health endpoint at https://xinyong.boai.gov.cn/health
Got: https://xinyong.boai.gov.cn/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback