Skip to content
https://lazada.com.my

Infrastructure

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

https://lazada.com.my

1052 ms · HTTP/1.1

301

https://www.lazada.com.my/

851 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://lazada.com.my3011052 msHTTP/1.1Tengine/Aserver
2https://www.lazada.com.my/200851 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.com.my/
200https://lazada.com.my/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://lazada.com.my/ https://lazada.com.my/

Consistent

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

Connection waterfall

DNS Lookup 296 ms TCP Connect 285 ms TLS Handshake 690 ms Server Processing 289 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, 297 ms lookup
PASS
8 A records, 297 ms lookup
Info::
Resolves to 8 IPv4 address(es)
Got: 47.246.165.182, 47.246.167.7, 47.246.167.254, 47.246.165.72, 47.246.165.115, 47.246.167.252, 47.246.165.39, 47.246.167.210
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 (297 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 297 ms
A47.246.165.182, 47.246.167.7, 47.246.167.254, 47.246.165.72, 47.246.165.115, 47.246.167.252, 47.246.165.39, 47.246.167.210
AAAA
CNAME
NSns2.alibabadns.com, ns1.alibabadns.com
MX
10 mx1.alibaba-inc.com
20 mxus1.alibaba-inc.com
TXT
google-site-verification=lmjaIa7h5toCXN51peEEDL_BfqQNMGVKagx2rAEXloc
_globalsign-domain-verification=OsqqjlnikOeQRC7gUTxYdWvOtA4utv8yEYFK2A7WaQ
_globalsign-domain-verification=nGuYEIUzhxNF2ckCvgO7MkeBhjhZgImPM2FE4n7ATq
facebook-domain-verification=5l0y695dpflud7v0lprfnapv0s2yz6
google-site-verification=kp8AZyEo2Jhb_5zR1voBMWfp5WMebC0bcl31f101IA8
MS=ms19282087
SPF v=spf1 ip4:103.56.127.36 ip4:103.56.127.37 include:aspmx.pardot.com include:a.st...
_globalsign-domain-verification=0U3I_9xXyPiEzB93J2_SNBYsk0RfaBpw3CdvR-hteY
_globalsign-domain-verification=ESg9Get6PGDyEv6Fw6cjUJjUcbbFQ94sfX8d2ay3YP
CAALookup not available with standard resolver
Resolved in 297 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: 153 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 153 B Sitemaps referenced 0 User-agents *, Googlebot-Image Blocking No — crawling allowed
User-agent:  *
Disallow: /wow/gcp/my/member/login-signup
Disallow: /undefined/
Disallow: */undefined/$
Disallow: */undefined$
User-agent: Googlebot-Image
A+
Domain Intelligence
lazada.com.my — via Integricity Technology Sdn Bhd, 13 years, 2 months old, hosted on Alibaba Cloud
PASS
lazada.com.my — via Integricity Technology Sdn Bhd, 13 years, 2 months old, hosted on Alibaba Cloud
Info::
Domain registered until Apr 18, 2027 (1 years remaining)
Info::
Registrar: Integricity Technology Sdn Bhd
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: Alibaba Cloud
Got: AS45102
Domain expiry

275 days

April 18, 2027

SSL certificate

76 days

Issued by GlobalSign nv-sa

Domain age

13 years, 2 months

Registered April 18, 2013

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Alibaba Cloud

ASN AS45102

47.246.167.254

Registrar

Integricity Technology Sdn Bhd

Unlocked 2 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 Integricity Technology Sdn Bhd
Created April 18, 2013 (13 years, 2 months ago)
Expires April 18, 2027 (1 years)
Last Updated April 2, 2025
Name Servers ns1.alibabadns.com, ns2.alibabadns.com
Registrant Ecart Services Malaysia Sdn Bhd
Hosting
IP Address 47.246.167.254
ASN AS45102 (ALIBABA-CN-NET Alibaba US Technology Co., Ltd., CN)
Provider Alibaba Cloud
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