Skip to content
https://22.cn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
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.

B
Redirect Chain
1 redirect(s), 2661 ms total
REVIEW
1 redirect(s), 2661 ms total
Info::
Single redirect
Got: https://22.cn → https://www.22.cn/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2661 ms total
Got: 2661 ms

https://22.cn

874 ms · HTTP/1.1

301

https://www.22.cn/

1787 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://22.cn301874 msHTTP/1.1Microsoft-IIS/10.0
2https://www.22.cn/2001787 msHTTP/1.1nginx/1.18.0

See the visual redirect chain in the HTTP Probe tab →

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
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.22.cn/
200https://22.cn/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Connection waterfall

DNS Lookup 590 ms TCP Connect 210 ms TLS Handshake 425 ms Server Processing 212 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
217 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

217
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, 615 ms lookup
PASS
1 A records, 615 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 122.228.19.36
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: dns2.everdns.com, dns1.everdns.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 (615 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 615 ms
A122.228.19.36
AAAA—
CNAME—
NSdns2.everdns.com, dns1.everdns.com
MX
5 mxbiz1.qq.com
10 mxbiz2.qq.com
TXT
SPF v=spf1 ip4:210.72.13.11 ip4:43.231.160.57 include:spf.mail.qq.com -all
CAALookup not available with standard resolver
Resolved in 615 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+
Crawlability
robots.txt present, sitemap with 27 URLs
PASS
robots.txt present, sitemap with 27 URLs
Info::
robots.txt is present
Got: 173 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 27 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 173 B Sitemaps referenced 2 User-agents *, GPTBot Blocking No — crawling allowed
User-agent: *

Disallow: /Member/

Disallow: /ajax/

Sitemap: https://www.22.cn/sitemap.xml

Sitemap: https://www.22.cn/config/sitemap.xml


User-agent: GPTBot

Disallow: /
sitemap.xml 200 OK
Type URL Set URLs 27 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
22.cn — via 浙江贰贰网络有限公司, 23 years, 5 months old, hosted on CHINATELECOM-ZHEJIANG-WENZHOU-IDC WENZHOU, ZHEJIANG Province, P.R.China., CN
PASS
22.cn — via 浙江贰贰网络有限公司, 23 years, 5 months old, hosted on CHINATELECOM-ZHEJIANG-WENZHOU-IDC WENZHOU, ZHEJIANG Province, P.R.China., CN
Info::
Domain registered until Mar 17, 2029 (2 years, 11 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: CHINATELECOM-ZHEJIANG-WENZHOU-IDC WENZHOU, ZHEJIANG Province, P.R.China., CN
Got: AS134771
Domain expiry

1005 days

March 17, 2029

SSL certificate

217 days

Issued by DigiCert Inc

Domain age

23 years, 5 months

Registered March 17, 2003

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CHINATELECOM-ZHEJIANG-WENZHOU-IDC WENZHOU, ZHEJIANG Province, P.R.China., CN

ASN AS134771

122.228.19.36

Registrar

浙江贰贰网络有限公司

Locked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar 浙江贰贰网络有限公司
Created March 17, 2003 (23 years, 5 months ago)
Expires March 17, 2029 (2 years, 11 months)
Name Servers dns1.everdns.com, dns2.everdns.com
Hosting
IP Address 122.228.19.36
ASN AS134771 (CHINATELECOM-ZHEJIANG-WENZHOU-IDC WENZHOU, ZHEJIANG Province, P.R.China., CN)
Provider CHINATELECOM-ZHEJIANG-WENZHOU-IDC WENZHOU, ZHEJIANG Province, P.R.China., CN
Data source: whois (1.2s)

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