Skip to content
https://cri.cn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
3 PASS 5 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
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

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

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

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 No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.cri.cn/
200https://cri.cn/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Connection waterfall

DNS Lookup 30 ms TCP Connect 163 ms TLS Handshake 344 ms Server Processing 211 ms Content Transfer 164 ms
B
TLS Certificate Expiry & Recommendations
281 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

281
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
  • 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
DNS Records
1 A records, 368 ms lookup
PASS
1 A records, 368 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 59.110.111.57
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: vip3.alidns.com, vip4.alidns.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (368 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 368 ms
A59.110.111.57
AAAA—
CNAME—
NSvip3.alidns.com, vip4.alidns.com
MX
5 hzmx01.mxmail.netease.com
10 hzmx02.mxmail.netease.com
TXT
SPF v=spf1 include:spf.163.com -all
globalsign-domain-verification=ncTzJOMe0IhSXwDQ2qUqvCM_zz6b2sYsOXVtOKZ-H-
google-site-verification=H-U4fxVU4cSsMJlCIoKwVPEePevpLAsTBCX23lRYoAI
SPF v=spf1 ip4:43.248.112.20 ip4:43.248.112.18 ip4:43.248.112.19 -all
CAALookup not available with standard resolver
Resolved in 368 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.

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

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

https://cri.cn

684 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cri.cn200684 msHTTP/1.1nginx
A+
Domain Intelligence
cri.cn — via 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）, 23 years, 5 months old, hosted on Alibaba Cloud
PASS
cri.cn — via 北京国科云计算技术有限公司（原北京中科三方网络技术有限公司）, 23 years, 5 months old, hosted on Alibaba Cloud
Info::
Domain registered until May 22, 2031 (5 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.
Info::
Hosting: Alibaba Cloud
Got: AS37963
Domain expiry

1802 days

May 22, 2031

SSL certificate

281 days

Issued by Beijing Xinchacha Credit Management Co., Ltd.

Domain age

23 years, 5 months

Registered March 10, 2003

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Alibaba Cloud

ASN AS37963

59.110.111.57

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 March 10, 2003 (23 years, 5 months ago)
Expires May 22, 2031 (5 years, 1 months)
Name Servers vip3.alidns.com, vip4.alidns.com
Hosting
IP Address 59.110.111.57
ASN AS37963 (ALIBABA-CN-NET Hangzhou Alibaba Advertising Co.,Ltd., CN)
Provider Alibaba Cloud
Data source: whois (2.3s)

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