Skip to content
https://huaweicloud.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
3 PASS 5 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.

B
Redirect Chain
1 redirect(s), 1297 ms total
REVIEW
1 redirect(s), 1297 ms total
Info::
Single redirect
Got: https://huaweicloud.com → https://www.huaweicloud.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1297 ms total
Got: 1297 ms

https://huaweicloud.com

1202 ms · HTTP/1.1

301

https://www.huaweicloud.com/

94 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://huaweicloud.com3011202 msHTTP/1.1CloudWAF
2https://www.huaweicloud.com/20094 msHTTP/1.1CloudWAF

See the visual redirect chain in the HTTP Probe tab →

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
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.huaweicloud.com/
200https://huaweicloud.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://huaweicloud.com/ → https://www.huaweicloud.com/

Consistent

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

Connection waterfall

DNS Lookup 69 ms TCP Connect 261 ms TLS Handshake 528 ms Server Processing 262 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
341 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

341
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 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
1 A records, 270 ms lookup
PASS
1 A records, 270 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 117.78.12.122
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: vip3.alidns.com, vip4.alidns.com
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 (270 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 270 ms
A117.78.12.122
AAAA—
CNAME—
NSvip3.alidns.com, vip4.alidns.com
MX
10 mailmx05.huawei.com
40 mailmx07.his.huawei.com
TXT
SPF v=spf1 ip4:45.249.212.51 ip4:45.249.212.56 ip4:185.176.79.53 ip4:14.137.139.23 i...
kv2mpcdm6z2ftv92gwd4qsf34cm6ng65
jTgHVp9H9Wd13YkT+Jdnrif8gaq7N3WLttEosuEHNbM=
globalsign-domain-verification=azBy6NUPdrOohCJSv3s0xcxxUNyH-pMYP85kPH0OAj
globalsign-domain-verification=YJoBgVNa6mvl2McWjLDSqTahJc8odSPDwbrY6UsVau
globalsign-domain-verification=V42lyZ9Mi1MhxQNjxU7Dv8m61jNeM-8JaT2D5CXraG
globalsign-domain-verification=PPhDZc7qvL7UjRpQuv-GAB89iZhEywPKbO1_vhpaj8
globalsign-domain-verification=PEIB6HGzStBLpR9yGKPNS7jCzKuG-IjWI4DTgh7dzm
globalsign-domain-verification=Cz2eI_juNN4ASPtP2TRjme0MbQiL8eEkGwA3oynPcA
globalsign-domain-verification=B9gpIwoDUgZaUzCPTViYRWXpTr81uwsQbNiCRU_WWH
globalsign-domain-verification=0JLPAxLm0F-z2zWDhjd09EUtFiaG3d9Do4Q-Gfk9Tc
globalsign-domain-verification=08zHYwlCF1ReuBQYX1-WmDUQAByV-3AFRv3PxVunWV
actalis-dcv=fsgv7o06t8cpech26vfg3ahbiq
actalis-dcv=81pz4972864o0a0pa9uq3isrd3
_globalsign-domain-verification=vhxfQmNCJttYJa0CzeyRZVbd7m7H744HmhpyZq4dID
_globalsign-domain-verification=nZziLb_jydPTDm0Cq6H7oQlV6iMNpB3SUyrBQlb1nc
CAALookup not available with standard resolver
Resolved in 270 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 1518 URLs
PASS
robots.txt present, sitemap with 1518 URLs
Info::
robots.txt is present
Got: 3140 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1518 entries
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 3140 B Sitemaps referenced 0 User-agents YouBot, OAI-SearchBot, FriendlyCrawler, EchoboxBot, Applebot-Extended, PerplexityBot, ImagesiftBot, DuckAssistBot, Crawlspace, ClaudeBot, Amazonbot, Ai2Bot-Dolma, GPTBot, cohere-ai, ChatGPT-User, quillbot.com, SemrushBot-SWA, peer39_crawler, Meta-ExternalFetcher, magpie-crawler, AwarioRssBot, SeekrBot, Scrapy, JamesBOT, Diffbot, Poseidon Research Crawler, PanguBot, omgili, Claude-Web, TurnitinBot, SemrushBot-OCOB, ICC-Crawler, iaskspider/2.0, DataForSeoBot, Arquivo-web-crawler, news-please, NewsNow, Kangaroo Bot, FacebookBot, CCBot, Brightbot 1.0, Bravebot, VelenPublicWebCrawler, Sidetrade indexer bot, omgilibot, Jetslide, AI2Bot, Quora-Bot, Webzio-Extended, PiplBot, cohere-training-data-crawler, Bytespider, anthropic-ai, Timpibot, CriteoBot, *, Meta-ExternalAgent, ISSCyberRiskCrawler, ia_archiver, peer39_crawler/1.0, AwarioSmartBot, TaraGroup Intelligent Bot, PetalBot, img2dataset Blocking No — crawling allowed
# Search Engine Spider Rules


User-agent: *

Disallow: /common/

Disallow: /tips/

Disallow: /test/

Disallow: /activity/share/

Disallow: /s/


# Disallow LLm Rules


User-agent: YouBot

Disallow: /guide/


User-agent: Webzio-Extended

Disallow: /guide/


User-agent: VelenPublicWebCrawler

Disallow: /guide/


User-agent: TurnitinBot

Disallow: /guide/


User-agent: Timpibot

Disallow: /guide/


User-agent: TaraGroup Intelligent Bot

Disallow: /guide/


User-agent: Sidetrade indexer bot

Disallow: /guide/


User-agent: SemrushBot-SWA

Disallow: /guide/


User-agent: SemrushBot-OCOB

Disallow: /guide/


User-agent: SeekrBot

Disallow: /guide/


User-agent: Scrapy

Disallow: /guide/


User-agent: Quora-Bot

Disallow: /guide/


User-agent: quillbot.com

Disallow: /guide/


User-agent: Poseidon Research Crawler

Disallow: /guide/


User-agent: PiplBot

Disallow: /guide/


User-agent: PetalBot

Disallow: /guide/


User-agent: PerplexityBot

Disallow: /guide/


User-agent: peer39_crawler/1.0

Disallow: /guide/


User-agent: peer39_crawler

Disallow: /guide/


User-agent: PanguBot

Disallow: /guide/


User-agent: omgilibot

Disallow: /guide/


User-agent: omgili

Disallow: /guide/


User-agent: OAI-SearchBot

Disallow: /guide/


User-agent: news-please

Disallow: /guide/


User-agent: NewsNow

Disallow: /guide/


User-agent: Meta-ExternalFetcher

Disallow: /guide/


User-agent: Meta-ExternalAgent

Disallow: /guide/


User-agent: magpie-crawler

Disallow: /guide/


User-agent: Kangaroo Bot

Disallow: /guide/


User-agent: Jetslide

Disallow: /guide/


User-agent: JamesBOT

Disallow: /guide/


User-agent: ISSCyberRiskCrawler

Disallow: /guide/


User-agent: img2dataset

Disallow: /guide/


User-agent: ImagesiftBot

Disallow: /guide/


User-agent: ICC-Crawler

Disallow: /guide/


User-agent: iaskspider/2.0

Disallow: /guide/


User-agent: ia_archiver

Disallow: /guide/


User-agent: GPTBot

Disallow: /guide/


User-agent: FriendlyCrawler

Disallow: /guide/


User-agent: FacebookBot

Disallow: /guide/


User-agent: EchoboxBot

Disallow: /guide/


User-agent: DuckAssistBot

Disallow: /guide/


User-agent: Diffbot

Disallow: /guide/


User-agent: DataForSeoBot

Disallow: /guide/


User-agent: CriteoBot

Disallow: /guide/


User-agent: Crawlspace

Disallow: /guide/


User-agent: cohere-training-data-crawler

Disallow: /guide/


User-agent: cohere-ai

Disallow: /guide/


User-agent: Claude-Web

Disallow: /guide/


User-agent: ClaudeBot

Disallow: /guide/


User-agent: ChatGPT-User

Disallow: /guide/


User-agent: CCBot

Disallow: /guide/


User-agent: Bytespider

Disallow: /guide/


User-agent: Brightbot 1.0

Disallow: /guide/


User-agent: Bravebot

Disallow: /guide/


User-agent: AwarioSmartBot

Disallow: /guide/


User-agent: AwarioRssBot

Disallow: /guide/


User-agent: Arquivo-web-crawler

Disallow: /guide/


User-agent: Applebot-Extended

Disallow: /guide/


User-agent: anthropic-ai

Disallow: /guide/


User-agent: Amazonbot

Disallow: /guide/


User-agent: Ai2Bot-Dolma

Disallow: /guide/


User-agent: AI2Bot

Disallow: /guide/
sitemap.xml 200 OK
Type URL Set URLs 1518 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
huaweicloud.com — via Xin Net Technology Corporation, 16 years, 1 months old, hosted on HWCSNET Huawei Cloud Service data center, CN
PASS
huaweicloud.com — via Xin Net Technology Corporation, 16 years, 1 months old, hosted on HWCSNET Huawei Cloud Service data center, CN
Info::
Domain registered until Jun 1, 2035 (9 years, 2 months remaining)
Info::
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.
Info::
Registrar: Xin Net Technology Corporation
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: HWCSNET Huawei Cloud Service data center, CN
Got: AS55990
Domain expiry

3243 days

June 1, 2035

SSL certificate

341 days

Issued by GlobalSign nv-sa

Domain age

16 years, 1 months

Registered June 1, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

HWCSNET Huawei Cloud Service data center, CN

ASN AS55990

117.78.12.122

Registrar

Xin Net Technology Corporation

Unlocked 6 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 Xin Net Technology Corporation
Created June 1, 2010 (16 years, 1 months ago)
Expires June 1, 2035 (9 years, 2 months)
Last Updated January 26, 2026
Name Servers ns1.huaweicloud-dns.cn, ns1.huaweicloud-dns.com, ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org, vip3.alidns.com, vip4.alidns.com
DNSSEC Not enabled
Hosting
IP Address 117.78.12.122
ASN AS55990 (HWCSNET Huawei Cloud Service data center, CN)
Provider HWCSNET Huawei Cloud Service data center, CN
Data source: rdap (0.1s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback