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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Amsterdam, Netherlands
200 OK
Checks
9
4 PASS 4 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.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 673 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 673 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# Robots.txt file from http://www.chsi.com.cn

# All robots will spider the domain


User-agent:*

Disallow:/xlrz/*?*

Disallow:/xlcx/*?*

Disallow:/xwcx/*?*

Disallow:/report/

Disallow:/xlrz/attachments/

Disallow:/mdgs2003/

Disallow:/mdgs2004/

Disallow:/mdgs2005/

Disallow:/mdgs2006/

Disallow:/06mdgs/

Disallow:/gkxx/

Disallow:/kyzx/

Disallow:/gatzs/

Disallow:/ncss/

Disallow:/xz/

Disallow:/zxgw/

Disallow:/ncss/

Disallow:/jsjjh/

Disallow:/hzzh/

Disallow:/kt/

Disallow:/ixynews/

Disallow:/chuguo/

Disallow:/zfnews/

Disallow:/xy/

Disallow:/jyzd/

Disallow:/chengkao/

Disallow:/zkzx/

Disallow:/gkzt/

Disallow:/yzzt/

Disallow:/jyzt/

Disallow:/xzzt/
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 973 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
99 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
182 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
374 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
973 ms
Total Time Total request time from DNS lookup through full response.
974 ms

Connection waterfall

DNS Lookup 99 ms TCP Connect 182 ms TLS Handshake 374 ms Server Processing 318 ms Content Transfer 1 ms
B
TLS Certificate Expiry & Recommendations
270 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

270
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
  • 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
DNS Records
1 A records, 107 ms lookup
PASS
1 A records, 107 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 203.107.40.210
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
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: 107 ms
Got: 107 ms
A203.107.40.210
AAAA—
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 107 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

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.chsi.com.cn

https://www.chsi.com.cn

861 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.chsi.com.cn200861 msHTTP/1.1
A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

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

HTTP → HTTPS

302http://www.chsi.com.cn/ → https://www.chsi.com.cn/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
chsi.com.cn — via 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）, 24 years, 3 months old, hosted on CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
PASS
chsi.com.cn — via 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）, 24 years, 3 months old, hosted on CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
Info::
Domain registered until May 16, 2030 (4 years, 1 months remaining)
Info::
Registrar: 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
Got: AS23724
Domain expiry

1368 days

May 16, 2030

SSL certificate

270 days

Issued by TrustAsia Technologies, Inc.

Domain age

24 years, 3 months

Registered May 16, 2002

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN

ASN AS23724

36.110.136.74

Registrar

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

Locked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）
Created May 16, 2002 (24 years, 3 months ago)
Expires May 16, 2030 (4 years, 1 months)
Name Servers ns3.dnsv5.com, ns4.dnsv5.com
Hosting
IP Address 36.110.136.74
ASN AS23724 (CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN)
Provider CHINANET-IDC-BJ-AP IDC, China Telecommunications Corporation, CN
Data source: whois (1.0s)

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

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

Send Feedback