Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DHTTP Probe TimingActionTotal 2379 ms — DNS, TCP, TLS, TTFB, content transfer breakdownFIX
Connection waterfall
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 6022 ms totalREVIEW
https://lazada.com
3499 ms · HTTP/1.1
https://lazada.com/en/
2523 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://lazada.com | 302 | 3499 ms | HTTP/1.1 | Tengine/Aserver |
| 2 | https://lazada.com/en/ | 200 | 2523 ms | HTTP/1.1 | Tengine/Aserver |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
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
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
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
<a id="a-link" href="https://g.alicdn.com/sd/punish/waf_block.html?wh_ttid=pc&qrcode=khojVTIcwrUtjqx21qsddA|aek0qQ|wpE0hg_0|AAAAZQ|0&uuid=921a2355321cc2b52d8eac76d6ab1d74&origin=https%3A%2F%2Flazada.com%3A443%2Fen%2Frobots.txt"></a>
<script>
document.getElementById("a-link").click();
window._config_ = {
"action": "block",
"url": "https://g.alicdn.com/sd/punish/block_h5.html?wh_ttid=pc&qrcode=khojVTIcwrUtjqx21qsddA|aek0qQ|wpE0hg_0|AAAAZQ|0&uuid=921a2355321cc2b52d8eac76d6ab1d74&origin=https%3A%2F%2Flazada.com%3A443%2Fen%2Frobots.txt"
};
</script>
<!--rgv587_flag:sm-->
No sitemap found
Adding a sitemap helps search engines discover your pages.
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, 251 ms lookupPASS
| A | 47.246.167.7, 47.246.165.110, 47.246.167.10, 47.246.167.254, 47.246.165.39, 47.246.165.182, 47.246.165.111, 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 | MS=ms89415600 google-site-verification=jETamCxw6T6sdOcLp2Pzn_NQ5DRdYOy_BFaouaa07LM google-site-verification=LcjDdiKxea9ilQm6vMD-h5el1mVvmKuYrUIRhVykkG4 _globalsign-domain-verification=gAf_dtvbwGS1Ay5zqa7RIYuWlkBIOWw2UnUGUxU5LD google-site-verification=z_BmzkT9W7_w2K21H8uorh2z1ggo8K9kyOva3CQL_Ik SPF v=spf1 ip4:103.56.127.36 ip4:103.56.127.37 include:aspmx.pardot.com include:a.st... google-site-verification=tIByuN1AMlhQkSJg1R_Oc8fVRmc8QIViulCfI55p3F8 google-site-verification=5STpzz1TPBwto9Rv1HzhJZ2siq4B8Uq3OgaJz_GNpo4 MS=ms64475000 |
| 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.
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+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencelazada.com — via MarkMonitor Inc., 16 years, 10 months old, hosted on Alibaba CloudPASS
696 days
May 11, 2028
76 days
Issued by GlobalSign nv-sa
16 years, 10 months
Registered August 25, 2009
Not enabled
Protects against DNS spoofing
Alibaba Cloud
ASN AS45102
47.246.165.111
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