Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 2229 ms totalREVIEW
https://lazada.sg
1054 ms · HTTP/1.1
https://www.lazada.sg/
1175 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://lazada.sg | 301 | 1054 ms | HTTP/1.1 | Tengine/Aserver |
| 2 | https://www.lazada.sg/ | 200 | 1175 ms | HTTP/1.1 | Tengine |
See the visual redirect chain in the HTTP Probe tab →
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BHTTP Probe TimingTotal 1407 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations76 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
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
ADNS Records8 A records, 350 ms lookupPASS
| A | 47.246.167.130, 47.246.167.129, 47.246.165.182, 47.246.165.39, 47.246.165.72, 47.246.167.10, 47.246.165.115, 47.246.167.114 |
| AAAA | — |
| CNAME | — |
| NS | ns2.alibabadns.com, ns1.alibabadns.com |
| MX | 10 mx1.alibaba-inc.com 20 mxus1.alibaba-inc.com |
| TXT | google-site-verification=doDxDDq8i5e9MsChMF1fo4E6X6rrkMGQf6wfxeElphs _globalsign-domain-verification=whu4oUTx6Xkvr1oy5yO-2hWzNaK7kcZ9FkUkDAokNP _globalsign-domain-verification=Z8zD_9sJvS7hEMCF92zc3N_B5rvAZCG4waC_z29ERW MS=ms83096612 8X8LL5LZR7QST195I6VOYDUXDSXXD1QL bDluRNeoF2HDFxxVKs2j8GQyK2PZ5bYupIMvF2kah1M= google-site-verification=Ut1F4327W5oAqWPNKrPlMNJMHYuwWg3vXJuGqAsLVP8 have-i-been-pwned-verification=933853d8df1f1c744cab330148d9770b facebook-domain-verification=h7bpbo3u46vmaah228h8xmanjgnd44 _globalsign-domain-verification=86devV83Ipsm7F1rEjsPXCtEKE06ibZcXavLklWXS0 google-site-verification=1ujDATlyLggXBH-zLybWHVzQZBrz-yCNLEFWlzTfegU _globalsign-domain-verification=lTH8qWO-4CsFLj0zppnvt3UJYqi-9qY_SBDJdsaop9 google-site-verification=-KyqPCz6eoUZ4Co_Zi97xQ72DY309I5Z4rG8TIvbHKM google-site-verification=xr9mvXICSJ_cqrgB90ph1HHozPmLEFlyFOBvq1x0rnk google-site-verification=58-qlVFhscHHi6LIFt4k1PuFfObHVjOcfCJNb9RQKF0 google-site-verification=Azr8lKDCeuwOU45dS-w0qD0fK0yCOCglpupmBjn605k 202205030537114c9b4qlk7trxrxjcxmdgqhb0g1adfwpl32xhnsaiefdysluadc dklbz9xmnbwn25g8nnwq9rkhl3k9n3hy |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.
Learn more ▾ ▴
SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.
Source: RFC 7208 (SPF)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Crawlabilityrobots.txt present, sitemap with 29 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow: /wow/gcp/sg/member/login-signup
Disallow: /undefined/
Disallow: */undefined/$
Disallow: */undefined$
- https://www.lazada.sg/sitemap-products-o...
- https://www.lazada.sg/sitemap-pdp-aib-te...
- https://www.lazada.sg/sitemap-pdp-freesh...
- https://www.lazada.sg/sitemap-seller-vid...
- https://www.lazada.sg/sitemap-pdp-catego...
- https://www.lazada.sg/sitemap-pdp-choice...
- https://www.lazada.sg/sitemap-pdp-dau-gt...
- https://www.lazada.sg/sitemap-pdp-lazmal...
- https://www.lazada.sg/sitemap-pdp-proved...
- https://www.lazada.sg/sitemap-pdp-strong...
- https://www.lazada.sg/sitemap-pdp-weak-2...
- https://www.lazada.sg/sitemap-products-v...
- https://www.lazada.sg/sitemap-sellers.xm...
- https://www.lazada.sg/sitemap-tag-basic....
- https://www.lazada.sg/sitemap-tag-extern...
- https://www.lazada.sg/sitemap-tag-juneht...
- https://www.lazada.sg/sitemap-tag-l30d-d...
- https://www.lazada.sg/sitemap-tag-l30dda...
- https://www.lazada.sg/sitemap-tag-proved...
- https://www.lazada.sg/sitemap-tag-semrus...
- https://www.lazada.sg/manually-customize...
- https://www.lazada.sg/pdp-tmall-sitemap....
- https://www.lazada.sg/sitemap-brands.xml
- https://www.lazada.sg/sitemap-catalog-ba...
- https://www.lazada.sg/sitemap-categories...
- https://www.lazada.sg/sitemap-categories...
- https://www.lazada.sg/sitemap-pdp-basic....
- https://www.lazada.sg/sitemap-tag-strong...
- https://www.lazada.sg/tag-order-last-90d...
A+Domain Intelligencelazada.sg — via MarkMonitor Inc., 14 years, 4 months old, hosted on Alibaba CloudPASS
616 days
February 22, 2028
76 days
Issued by GlobalSign nv-sa
14 years, 4 months
Registered February 22, 2012
Not enabled
Protects against DNS spoofing
Alibaba Cloud
ASN AS45102
47.246.165.182
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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