Infrastructure - https://lazada.co.id BeaverCheck Audit

D

CDN & Delivery

Action

No CDN detected

FIX

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), 2962 ms total

REVIEW

1 redirect(s), 2962 ms total

Single redirect

Got: https://lazada.co.id → https://www.lazada.co.id/ (301)

WWW normalization redirect

Redirect overhead: 2962 ms total

Got: 2962 ms

https://lazada.co.id

1039 ms · HTTP/1.1

301

https://www.lazada.co.id/

1923 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://lazada.co.id	301	1039 ms	HTTP/1.1	Tengine/Aserver
2	https://www.lazada.co.id/	200	1923 ms	HTTP/1.1	Tengine

See the visual redirect chain in the HTTP Probe tab →

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.lazada.co.id/

200https://lazada.co.id/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://lazada.co.id/ → https://lazada.co.id/

Consistent

B

HTTP Probe Timing

Total 1201 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

160 ms

TCP Connect

259 ms

TLS Handshake

521 ms

Time to First Byte

1.20 s

Total Time

1.20 s

Connection waterfall

DNS Lookup 160 ms TCP Connect 259 ms TLS Handshake 521 ms Server Processing 262 ms Content Transfer 0 ms

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, 239 ms lookup

PASS

8 A records, 239 ms lookup

Resolves to 8 IPv4 address(es)

Got: 47.246.165.39, 47.246.165.115, 47.246.167.129, 47.246.167.114, 47.246.165.72, 47.246.167.130, 47.246.167.10, 47.246.165.182

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns2.alibabadns.com, ns1.alibabadns.com

2 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution is slow (239 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 239 ms

A	47.246.165.39, 47.246.165.115, 47.246.167.129, 47.246.167.114, 47.246.165.72, 47.246.167.130, 47.246.167.10, 47.246.165.182
AAAA	—
CNAME	—
NS	ns2.alibabadns.com, ns1.alibabadns.com
MX	10 mx1.alibaba-inc.com 20 mxus1.alibaba-inc.com
TXT	_globalsign-domain-verification=ZFrwxMcSlaDvevWPexXGxJbrEgk-n3NnznABSeyCLL SPF v=spf1 ip4:103.56.127.36 ip4:103.56.127.37 include:aspmx.pardot.com include:a.st... wq9yvvwclwbhyw43gnpvfj14kcnlcz80 syb1k3zyqq33yvbqfyqlc050n254bbhr sfpmj4t87lgz0jd16rh7p7sxm28spmgc FZAmuQlNQRQjHBlofGwoPesFWI4ilkO7yY6+YUXq65w= _globalsign-domain-verification=2MZNioZ7GvBxO1h0jdvYmA-u4E4IZItfRSYIuA2EF1 _globalsign-domain-verification=sRfZHgwA6x7ptH-H7JXHvp_VTDgVTPvlWVn5sSnsEG mMhOR3a0Vhf1dGLadcbnRNNSAdvun6MyvEgEWeoj2rg= google-site-verification=jTg_pg-GVwedUFTqKUh-e1lVuJknPWH5z0ILMcCbMv8 google-site-verification=ePgKmYSQmZdijjH5UsoFS7WdG5n0ayM6JXpwVAJbHcE lbH5EtAaRQoblFh9mHoBJeItlHbhXYkiFD/0nVc7yBU= ci3BpxT8miXdRflgws1ycaq+csBHLA11surK/oPYFgY= facebook-domain-verification=yadn64p4kop6qef9cfyvk1utkiilgy q22fgzrlkrc86fwks0p61xvr8n2f4gxc google-site-verification=3Wghum479h-ipZXpo92TIwSZYnWVHznbASC1XkYAcXM google-site-verification=ia86Wt3RbRkjHWRu8yTO6dx8bYpWjCWdyvJ7pbPjXH8 _globalsign-domain-verification=DRznyW3v3IOzNKgWJfF6ZHRY2-K5HATUr8YWxzRFzW MS=ms81255898
CAA	Lookup not available with standard resolver

Resolved in 239 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 31 URLs

PASS

robots.txt present, sitemap with 31 URLs

robots.txt is present

Got: 153 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 31 entries

Sitemap index with 31 child sitemaps

robots.txt does not reference a 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/id/member/login-signup
Disallow: /undefined/
Disallow: */undefined/$
Disallow: */undefined$
User-agent: Googlebot-Image

sitemap.xml 200 OK

Type Sitemap Index URLs 31 entries Valid XML Yes

Child Sitemaps:

A+

Domain Intelligence

lazada.co.id — via PT Digital Registra Indonesia, 14 years, 4 months old, hosted on Alibaba Cloud

PASS

lazada.co.id — via PT Digital Registra Indonesia, 14 years, 4 months old, hosted on Alibaba Cloud

Domain registered until Feb 24, 2028 (1 years, 10 months remaining)

DNSSEC is not enabled

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Registrar: PT Digital Registra Indonesia

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.

Hosting: Alibaba Cloud

Got: AS45102

Domain expiry

586 days

February 24, 2028

SSL certificate

77 days

Issued by GlobalSign nv-sa

Domain age

14 years, 4 months

Registered February 24, 2012

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Alibaba Cloud

ASN AS45102

47.246.165.39

Registrar

PT Digital Registra Indonesia

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar PT Digital Registra Indonesia

Created February 24, 2012 (14 years, 4 months ago)

Expires February 24, 2028 (1 years, 10 months)

Last Updated February 6, 2026

Name Servers ns1.alibabadns.com, ns2.alibabadns.com

DNSSEC Not enabled

Hosting

IP Address 47.246.165.39

ASN AS45102 (ALIBABA-CN-NET Alibaba US Technology Co., Ltd., CN)

Provider Alibaba Cloud

Data source: rdap (1.5s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

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