Infrastructure - https://alibabacloud.com BeaverCheck Audit

D

Redirect Chain

Action

2 redirect(s), 2805 ms total

FIX

2 redirect(s), 2805 ms total

2 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://www.alibabacloud.com/

Redirect overhead: 2805 ms total

Got: 2805 ms

https://alibabacloud.com

1163 ms · HTTP/1.1

301

https://www.alibabacloud.com/

926 ms · HTTP/1.1

302

https://www.alibabacloud.com/en?_p_lc=7

716 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://alibabacloud.com	301	1163 ms	HTTP/1.1	Tengine
2	https://www.alibabacloud.com/	302	926 ms	HTTP/1.1	Tengine
3	https://www.alibabacloud.com/en?_p_lc=7	200	716 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.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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

D

CDN & Delivery

Action

No CDN detected

FIX

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

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

HTTP Probe Timing

Total 1214 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

171 ms

TCP Connect

259 ms

TLS Handshake

522 ms

Time to First Byte

1.21 s

Total Time

1.21 s

Connection waterfall

DNS Lookup 171 ms TCP Connect 259 ms TLS Handshake 522 ms Server Processing 263 ms Content Transfer 0 ms

B

TLS Certificate Expiry & Recommendations

135 days until leaf cert expires — 5 issues to address

REVIEW

Certificate validity

135

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
Add includeSubDomains to the HSTS directive
Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
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

27 A records, 308 ms lookup

PASS

27 A records, 308 ms lookup

Resolves to 27 IPv4 address(es)

Got: 47.88.251.174, 47.88.251.180, 47.88.251.164, 47.88.251.163, 47.88.251.171, 47.88.251.175, 47.88.251.173, 47.88.198.40, 47.88.251.178, 47.88.198.37, 47.88.198.17, 47.88.198.24, 47.88.128.163, 47.88.251.179, 47.88.251.162, 47.88.251.177, 47.88.198.34, 47.88.251.169, 47.88.251.168, 47.88.198.38, 47.88.251.161, 47.88.251.166, 47.88.251.170, 47.88.251.165, 47.88.251.176, 47.88.198.31, 47.88.251.172

No IPv6 (AAAA) records

3 nameserver(s) configured

Got: ns5.aliyun.com, ns4.aliyun.com, ns3.aliyun.com

1 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution is slow (308 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 308 ms

A	47.88.251.174, 47.88.251.180, 47.88.251.164, 47.88.251.163, 47.88.251.171, 47.88.251.175, 47.88.251.173, 47.88.198.40, 47.88.251.178, 47.88.198.37, 47.88.198.17, 47.88.198.24, 47.88.128.163, 47.88.251.179, 47.88.251.162, 47.88.251.177, 47.88.198.34, 47.88.251.169, 47.88.251.168, 47.88.198.38, 47.88.251.161, 47.88.251.166, 47.88.251.170, 47.88.251.165, 47.88.251.176, 47.88.198.31, 47.88.251.172
AAAA	—
CNAME	—
NS	ns5.aliyun.com, ns4.aliyun.com, ns3.aliyun.com
MX	10 mx2.mail.aliyun.com
TXT	google-site-verification=Y_8s0fLGhmfASBOET1hWSuWE95rrUnkojh9Gu2rxxz4 SPF v=spf1 include:spf1.service.alibaba.com include:spf2.service.alibaba.com include... google-site-verification=pcBwVz14uqYishDMVpbD3ExjgzR61UeuZ9QAmVEoQZk 8NpUEbR9RVc1GrFEbMxDK85HmGaFhxw91BLJbihb3QI= google-site-verification=YOH7yO-iAt3PKc8RpHfHjLd9IOE9wtsmgDTpn84bz1k _globalsign-domain-verification=UCEEsvX8Cr8R6CvEZS27DtKJUTM-aBlozx3bzoWZu8 MS=ms31641552
CAA	Lookup not available with standard resolver

Resolved in 308 ms

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 14 URLs

PASS

robots.txt present, sitemap with 14 URLs

robots.txt is present

Got: 478 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 14 entries

Sitemap index with 14 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 478 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: * 
Disallow: /api/* 
Disallow: /*.json 
Disallow: /*.jsonp 
Disallow: /open/api/* 
Disallow: /*?callback=* 
Disallow: /*?utm_key=* 
Disallow: /*?tracelog=* 
Disallow: /*?page=* 
Disallow: /template 
Disallow: /admin 
Disallow: /config 
Disallow: /classes 
Disallow: /log 
Disallow: /language 
Disallow: /script 
Disallow: /static 
Disallow: /alilog 
Disallow: /s/*
Disallow: /b/*
Disallow: /topic-center/*


Sitemap: https://www.alibabacloud.com/sitemaps/sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 14 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.alibabacloud.com/

200https://alibabacloud.com/

Preferred variant: non-www

HTTP → HTTPS

301http://alibabacloud.com/ → https://alibabacloud.com/

Consistent

A+

Domain Intelligence

alibabacloud.com — via CSC Corporate Domains, Inc., 16 years, 10 months old, hosted on Alibaba Cloud

PASS

alibabacloud.com — via CSC Corporate Domains, Inc., 16 years, 10 months old, hosted on Alibaba Cloud

Domain registered until Sep 8, 2030 (4 years, 5 months remaining)

DNSSEC is not enabled

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Registrar: CSC Corporate Domains, Inc.

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.

Hosting: Alibaba Cloud

Got: AS45102

Domain expiry

1548 days

September 8, 2030

SSL certificate

135 days

Issued by GlobalSign nv-sa

Domain age

16 years, 10 months

Registered September 8, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Alibaba Cloud

ASN AS45102

47.88.251.168

Registrar

CSC Corporate Domains, Inc.

Unlocked 3 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar CSC Corporate Domains, Inc.

Created September 8, 2009 (16 years, 10 months ago)

Expires September 8, 2030 (4 years, 5 months)

Last Updated December 18, 2025

Name Servers ns3.aliyun.com, ns4.aliyun.com, ns5.aliyun.com

DNSSEC Not enabled

Hosting

IP Address 47.88.251.168

ASN AS45102 (ALIBABA-CN-NET Alibaba US Technology Co., Ltd., CN)

Provider Alibaba Cloud

Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

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