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

Infrastructure

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

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

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B
TLS Certificate Expiry & Recommendations
77 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

77
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, 4 ms lookup
PASS
8 A records, 4 ms lookup
Info::
Resolves to 8 IPv4 address(es)
Got: 47.246.167.7, 47.246.167.254, 47.246.167.252, 47.246.167.210, 47.246.165.182, 47.246.165.39, 47.246.165.72, 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
Info::
DNS resolution time: 4 ms
Got: 4 ms
A47.246.167.7, 47.246.167.254, 47.246.167.252, 47.246.167.210, 47.246.165.182, 47.246.165.39, 47.246.165.72, 47.246.165.115
AAAA
CNAME
NSns2.alibabadns.com, ns1.alibabadns.com
MX
10 mx1.alibaba-inc.com
20 mxus1.alibaba-inc.com
TXT
_globalsign-domain-verification=AFhDZpe-nu00hG_NjzlvWlx4XpzlxiPwewSYtmHtpn
202005300208211fgkuj3ologp56be5rhkytil951vaesdcaybk14qmypphw09al
cloudpiercer-verification=11a464aebab936fda42cf5365fef3391
facebook-domain-verification=9ab81x1yqeg6rupmno02zfr6yksop7
MS=ms13772635
8X8LL5LZR7QST195I6VOYDUXDSXXD1QL
SPF v=spf1 ip4:103.56.127.36 ip4:103.56.127.37 include:aspmx.pardot.com include:a.st...
google-site-verification=dcA5A_2ALlh02KjuaRKHljrgptvh-7pw1WVXDmYfBlw
google-site-verification=ghqwH9r6vgyiepdoHFuU24sOGOS3FfJDu_PT7adThoc
_globalsign-domain-verification=yLOX0Ej_LTvzRUpcdTRLYEWdIadsgsK8aRVPCr6BIu
_globalsign-domain-verification=LvYmG1LkDqanYwFZJwzFKubPAO1NVW9Ib6KvJ_0Z74
_globalsign-domain-verification=SQh-ugDzWDwMYyTX6MLQ4oXESXWrwDe7qI4w8Ac_Qa
CAALookup not available with standard resolver
Resolved in 4 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.

A
Redirect Chain
1 redirect(s), 32 ms total
PASS
1 redirect(s), 32 ms total
Info::
Single redirect
Got: https://lazada.com.ph → https://www.lazada.com.ph/ (301)
Info::
WWW normalization redirect

https://lazada.com.ph

18 ms · HTTP/1.1

301

https://www.lazada.com.ph/

14 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://lazada.com.ph30118 msHTTP/1.1Tengine/Aserver
2https://www.lazada.com.ph/20014 msHTTP/1.1Tengine

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 32 URLs
PASS
robots.txt present, sitemap with 32 URLs
Info::
robots.txt is present
Got: 125 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 32 entries
Info::
Sitemap index with 32 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 125 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent:  *
Disallow: /wow/gcp/ph/member/login-signup
Disallow: /undefined/
Disallow: */undefined/$
Disallow: */undefined$
A+
HTTP Probe Timing
Total 21 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
21 ms
Total Time Total request time from DNS lookup through full response.
21 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 3 ms TLS Handshake 8 ms Server Processing 6 ms Content Transfer 0 ms
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