Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 2130 ms totalFIX
https://aliyun.com
823 ms · HTTP/1.1
https://www.aliyun.com/
707 ms · HTTP/1.1
https://www.alibabacloud.com/en?_p_lc=1&...
601 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://aliyun.com | 301 | 823 ms | HTTP/1.1 | Tengine |
| 2 | https://www.aliyun.com/ | 302 | 707 ms | HTTP/1.1 | Tengine |
| 3 | https://www.alibabacloud.com/en?_p_lc=1&... | 200 | 601 ms | HTTP/1.1 | Tengine |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
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
FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
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)
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BTLS Certificate Expiry & Recommendations141 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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 Records6 A records, 180 ms lookupPASS
| A | 140.205.135.3, 140.205.60.46, 106.11.253.83, 106.11.249.99, 106.11.248.146, 106.11.172.9 |
| AAAA | 2401:b180:1:60::6, 2401:b180:1:60::5 |
| CNAME | — |
| NS | ns5.aliyun.com, ns4.aliyun.com, ns3.aliyun.com |
| MX | 10 mx2.mail.aliyun.com |
| TXT | _globalsign-domain-verification=oLZG6Fd7z8mGZBqRo-_AVhGo8w74rNI12M6i5a3qts google-site-verification=zPjweaDxmddR96fzJcn4SmCM4W1PVxumm3dINt5TRuk SPF v=spf1 ip4:115.124.30.0/24 ip4:121.0.18.0/23 ip4:121.0.30.0/24 ip4:42.120.70.0... kqpmfrf0schjrfhv52j66tgl1dn2pb01 |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ACrawlabilityrobots.txt present, no sitemapPASS
A sitemap helps search engines discover and index your pages more efficiently.
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
User-agent: *
Disallow: /*?spm=*
Disallow: /*?tracelog=*
Disallow: /*?page=*
Disallow: /template
Disallow: /admin
Disallow: /config
Disallow: /classes
Disallow: /log
Disallow: /language
Disallow: /script
Disallow: /static
Disallow: /alilog
Allow: /s/*
Sitemap: https://www.alibabacloud.com/sitemap.xml
No sitemap found
Adding a sitemap helps search engines discover your pages.
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencealiyun.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 18 years, 9 months old, hosted on Alibaba CloudPASS
1200 days
September 28, 2029
141 days
Issued by GlobalSign nv-sa
18 years, 9 months
Registered September 28, 2007
Not enabled
Protects against DNS spoofing
Alibaba Cloud
ASN AS37963
140.205.135.3
Alibaba Cloud Computing (Beijing) Co., Ltd.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
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.
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