Skip to content
https://google.cn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
2
REVIEW
1
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
302 Found
Checks
9
6 PASS 1 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

200https://www.google.cn/
200https://google.cn/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://google.cn/ → http://www.google.cn/

HTTP version does not redirect to HTTPS

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
TLS Certificate Expiry & Recommendations
66 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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, 58 ms lookup
PASS
1 A records, 58 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 172.217.29.227
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: 2800:3f0:4001:808::2003
Info::
4 nameserver(s) configured
Got: ns1.google.com, ns2.google.com, ns4.google.com, ns3.google.com
Info::
1 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
Info::
DNS resolution time: 58 ms
Got: 58 ms
A172.217.29.227
AAAA2800:3f0:4001:808::2003
CNAME—
NSns1.google.com, ns2.google.com, ns4.google.com, ns3.google.com
MX
0 smtp.google.com
TXT
SPF v=spf1 -all
CAALookup not available with standard resolver
Resolved in 58 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.

A
Redirect Chain
1 redirect(s), 743 ms total
PASS
1 redirect(s), 743 ms total
Info::
Single redirect
Got: https://google.cn → http://www.google.cn/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://google.cn
Info::
Redirect overhead: 743 ms total
Got: 743 ms

https://google.cn

411 ms · HTTP/1.1

302

http://www.google.cn/

332 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://google.cn302411 msHTTP/1.1sffe
2http://www.google.cn/200332 msHTTP/1.1sffe

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2800:3f0:4001:808::2003
Got: 1 ms connect
IPv6 Ready
AAAA Records 2800:3f0:4001:808::2003 Connection Reachable (1 ms)
A
Crawlability
no robots.txt, sitemap with 20 URLs
PASS
no robots.txt, sitemap with 20 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
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 20 entries
Info::
Sitemap index with 20 child sitemaps

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

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 Sitemap Index URLs 20 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
google.cn — via 厦门易名科技股份有限公司, 23 years, 5 months old
PASS
google.cn — via 厦门易名科技股份有限公司, 23 years, 5 months old
Info::
Domain registered until Mar 17, 2027 (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.
Domain expiry

212 days

March 17, 2027

SSL certificate

66 days

Issued by Google Trust Services

Domain age

23 years, 5 months

Registered March 17, 2003

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2800:3f0:4001:80a::2003

Registrar

厦门易名科技股份有限公司

Locked 4 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, 2027 (11 months)
Name Servers ns2.google.com, ns1.google.com, ns3.google.com, ns4.google.com
Hosting
IP Address 2800:3f0:4001:80a::2003
Data source: whois (1.3s)

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

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

Connection waterfall

DNS Lookup 56 ms TCP Connect 1 ms TLS Handshake 54 ms Server Processing 316 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback