Skip to content
https://lazada.vn

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
GRADE
C
FIX
1
REVIEW
5
PASS
2
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
2 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), 2204 ms total
REVIEW
1 redirect(s), 2204 ms total
Info::
Single redirect
Got: https://lazada.vn → https://www.lazada.vn/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 2204 ms total
Got: 2204 ms

https://lazada.vn

1158 ms · HTTP/1.1

301

https://www.lazada.vn/

1046 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://lazada.vn3011158 msHTTP/1.1Tengine/Aserver
2https://www.lazada.vn/2001046 msHTTP/1.1Tengine

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.lazada.vn/
200https://lazada.vn/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://lazada.vn/ → https://lazada.vn/

Consistent

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

Connection waterfall

DNS Lookup 165 ms TCP Connect 289 ms TLS Handshake 582 ms Server Processing 292 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
76 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

76
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
8 A records, 301 ms lookup
PASS
8 A records, 301 ms lookup
Info::
Resolves to 8 IPv4 address(es)
Got: 47.246.167.210, 47.246.165.72, 47.246.165.182, 47.246.167.254, 47.246.167.252, 47.246.165.39, 47.246.167.7, 47.246.165.115
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns2.alibabadns.com, ns1.alibabadns.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 (301 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 301 ms
A47.246.167.210, 47.246.165.72, 47.246.165.182, 47.246.167.254, 47.246.167.252, 47.246.165.39, 47.246.167.7, 47.246.165.115
AAAA—
CNAME—
NSns2.alibabadns.com, ns1.alibabadns.com
MX
10 mx1.alibaba-inc.com
20 mxus1.alibaba-inc.com
TXT
google-site-verification=iUpGZjtOqV3ZhP0YIyO1ZacYuHUx2BM52W2y5wbJ8L8
MS=ms38121097
SPF v=spf1 ip4:103.56.127.36 ip4:103.56.127.37 include:aspmx.pardot.com include:a.st...
_globalsign-domain-verification=hQ8v-zI5G6aziGTljVWoXtySVhng1fWWr2swrNKUd1
CAALookup not available with standard resolver
Resolved in 301 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 28 URLs
PASS
robots.txt present, sitemap with 28 URLs
Info::
robots.txt is present
Got: 152 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 28 entries
Info::
Sitemap index with 28 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 152 B Sitemaps referenced 0 User-agents *, Googlebot-Image Blocking No — crawling allowed
User-agent: *
Disallow: /wow/gcp/vn/member/login-signup
Disallow: /undefined/
Disallow: */undefined/$
Disallow: */undefined$
User-agent: Googlebot-Image
sitemap.xml 200 OK
Type Sitemap Index URLs 28 entries Valid XML Yes
Child Sitemaps:
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

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

Send Feedback