Skip to content
https://west.cn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
4
PASS
3
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 4 REVIEW 2 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 240e:d9:c200:110::2
Info::
IPv6 connection error
Got: dial tcp6 [240e:d9:c200:110::2]:443: i/o timeout
IPv6 Misconfigured
AAAA Records 240e:d9:c200:110::2 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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), 2633 ms total
REVIEW
1 redirect(s), 2633 ms total
Info::
Single redirect
Got: https://west.cn → https://www.west.cn/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2633 ms total
Got: 2633 ms

https://west.cn

735 ms · HTTP/1.1

301

https://www.west.cn/

1898 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://west.cn301735 msHTTP/1.1wts
2https://www.west.cn/2001898 msHTTP/1.1wts/1.7.4

See the visual redirect chain in the HTTP Probe tab →

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

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Connection waterfall

DNS Lookup 365 ms TCP Connect 170 ms TLS Handshake 345 ms Server Processing 171 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
146 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

146
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, 1368 ms lookup
PASS
1 A records, 1368 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 116.198.219.52
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: 240e:d9:c200:110::2
Info::
6 nameserver(s) configured
Got: ns1.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns3.myhostadmin.net, ns2.myhostadmin.net, ns6.myhostadmin.net
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 (1368 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1368 ms
A116.198.219.52
AAAA240e:d9:c200:110::2
CNAME—
NSns1.myhostadmin.net, ns4.myhostadmin.net, ns5.myhostadmin.net, ns3.myhostadmin.net, ns2.myhostadmin.net, ns6.myhostadmin.net
MX
5 mx1.yunyou.top
10 mx2.yunyou.top
TXT
SPF v=spf1 redirect=_spf.yunyou.top
CAALookup not available with standard resolver
Resolved in 1368 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 530 URLs
PASS
robots.txt present, sitemap with 530 URLs
Info::
robots.txt is present
Got: 97 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 530 entries
Info::
Sitemap index with 530 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 97 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent:*

Disallow:/setinmanager/

Disallow:/customercenter/UploadImages/

Disallow:/manager/
sitemap.xml 200 OK
Type Sitemap Index URLs 530 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
west.cn — via 成都西维数码科技有限公司, 12 years, 5 months old
PASS
west.cn — via 成都西维数码科技有限公司, 12 years, 5 months old
Info::
Domain registered until Jan 21, 2029 (2 years, 9 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.
Domain expiry

921 days

January 21, 2029

SSL certificate

146 days

Issued by TrustAsia Technologies, Inc.

Domain age

12 years, 5 months

Registered January 21, 2014

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

240e:d9:c200:110::2

Registrar

成都西维数码科技有限公司

Unlocked 6 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 January 21, 2014 (12 years, 5 months ago)
Expires January 21, 2029 (2 years, 9 months)
Name Servers ns4.myhostadmin.net, ns1.myhostadmin.net, ns2.myhostadmin.net, ns3.myhostadmin.net, ns5.myhostadmin.net, ns6.myhostadmin.net
Hosting
IP Address 240e:d9:c200:110::2
Data source: whois (1.0s)

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