Skip to content
https://189.cn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Santa Clara, United States
412 HTTP 412
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
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::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

412https://www.189.cn/
200https://189.cn/

HTTP → HTTPS

http://189.cn/

HTTP version does not redirect to HTTPS

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

Certificate validity

132
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, 158 ms lookup
PASS
1 A records, 158 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 117.89.29.19
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: ns1.chinanet.cn, ns2.chinanet.cn
Info::
3 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: 158 ms
Got: 158 ms
A117.89.29.19
AAAA
CNAME
NSns1.chinanet.cn, ns2.chinanet.cn
MX
10 mta-189.21cn.com
20 mx2-189.21cn.com
30 mx3-189.21cn.com
TXT
b3d973d953124f18b572c0b2775d1eee
d6baa51391750005fce703030c1306562566d86135d518bd4bf0b10b3d99261f
google-site-verification=fnhC9eZ-Dmna-6EIvU0mJXk52k0A5TChiQaulg-xdss
globalsign-domain-verification=aF1WppYM23EmniP08To6CoRhshTaAUbFJIFOs1q7VY
SPF v=spf1 include:mail-spf.21cn.com include:hwmail-spf.21cn.com -all
CAALookup not available with standard resolver
Resolved in 158 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
0 redirect(s), 758 ms total
PASS
0 redirect(s), 758 ms total
Info::
Redirect overhead: 758 ms total
Got: 758 ms

https://189.cn

758 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://189.cn412758 msHTTP/1.1CTYun LB
A+
Domain Intelligence
189.cn — via 阿里云计算有限公司(万网), 22 years, 3 months old, hosted on CHINANET-NANJING-JISHAN-IDC CHINANET Nanjing Jishan IDC network, CN
PASS
189.cn — via 阿里云计算有限公司(万网), 22 years, 3 months old, hosted on CHINANET-NANJING-JISHAN-IDC CHINANET Nanjing Jishan IDC network, CN
Info::
Domain registered until May 4, 2028 (2 years 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: CHINANET-NANJING-JISHAN-IDC CHINANET Nanjing Jishan IDC network, CN
Got: AS134756
Domain expiry

656 days

May 4, 2028

SSL certificate

132 days

Issued by DigiCert, Inc.

Domain age

22 years, 3 months

Registered May 4, 2004

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CHINANET-NANJING-JISHAN-IDC CHINANET Nanjing Jishan IDC network, CN

ASN AS134756

117.89.29.19

Registrar

阿里云计算有限公司(万网)

Unlocked 3 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 May 4, 2004 (22 years, 3 months ago)
Expires May 4, 2028 (2 years)
Name Servers ns3.chinanet.cn, ns1.chinanet.cn, ns2.chinanet.cn
Hosting
IP Address 117.89.29.19
ASN AS134756 (CHINANET-NANJING-JISHAN-IDC CHINANET Nanjing Jishan IDC network, CN)
Provider CHINANET-NANJING-JISHAN-IDC CHINANET Nanjing Jishan IDC network, CN
Data source: whois (0.8s)

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
HTTP Probe Timing
Total 739 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
158 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
144 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
287 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
739 ms
Total Time Total request time from DNS lookup through full response.
739 ms

Connection waterfall

DNS Lookup 158 ms TCP Connect 144 ms TLS Handshake 287 ms Server Processing 150 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