Overview
Findings
Actions
Details
Related
AI-Generated Summary
What this means
lazada.sg scored 60/100, meeting baseline requirements but with 5 findings that require attention. The vendor can proceed with a remediation timeline agreement.
Critical gaps in: Security Headers. Positive signals: Known Breaches, CVE Exposure all passed.
6 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How lazada.sg compares
Grade distribution across 2520 companies we've scanned. lazada.sg scores better than 24% of them.
79
A+
25
A
184
A-
190
B+
73
B
351
B-
121
C+
113
C
324
C-
117
D+
93
D
237
D-
613
F
lazada.sg — Grade D- (60/100)
2520 companies scanned
Security checks
Each check inspects a different part of lazada.sg's public security setup. Green means healthy, yellow needs attention, red is a problem.
Security Headers
Only 2/5 security headers present. Missing: CSP, Referrer-Policy, Permissions-Policy. This exposes the application to clickjacking, MIME-sniffing, and other client-side attacks.
TLS Configuration
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC / Email Security
Strengths: DMARC policy set to quarantine; DKIM configured (selectors: default, k1). Issues: No SPF record found.
HSTS Header
HSTS present but max-age is low (0s). Recommended minimum: 15768000 (6 months).
DNS Configuration
Strengths: 2 nameservers configured (ns2.alibabadns.com., ns1.alibabadns.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.
Certificate Hygiene
Strengths: Certificate valid, 142 days remaining; Issued by GlobalSign nv-sa. Issues: Wildcard certificate in use — broader attack surface if compromised.
Known Breaches
No known breaches found in public disclosure databases.
CVE Exposure
Detected technologies: Tengine, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Recommended actions
6 items
Steps to improve lazada.sg's security grade, ranked by impact.
1
Strengthen email authentication configuration
Email authentication is partially configured for lazada.sg but has gaps. Actions needed: add SPF record. Until DMARC enforcement is active, spoofed emails may still reach recipients.
Compliance impact
NIST CSFPR.AC-7
Email authentication is a required access control
How to fix this
1
Add SPF record if missing: v=spf1 include:_spf.google.com -all
2
Verify with: nslookup -type=txt _dmarc.lazada.sg
See all recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
2
Add missing security headers (CSP, Referrer-Policy, Permissions-Policy)
3 of 5 recommended security headers are missing on lazada.sg: CSP, Referrer-Policy, Permissions-Policy. These headers protect against clickjacking, MIME-sniffing, and unauthorized browser feature access. Adding them is a server configuration change with no application code changes required.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Security headers are required application controls
OWASPSecure Headers
Recommended baseline for web applications
How to fix this
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: Referrer-Policy: strict-origin-when-cross-origin
3
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
4
Verify with: curl -sI https://lazada.sg | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
3
Increase HSTS max-age duration
HSTS is enabled but the max-age (0s) is below the recommended minimum of 15768000s (6 months). A short max-age means browsers forget the HTTPS-only policy quickly, reducing protection between visits.
Compliance impact
PCI-DSS 4.0Req 6.4.1
Application security header configuration
How to fix this
1
Update header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify: curl -sI https://lazada.sg | grep -i strict
4
Enable DNSSEC on your domain
Without DNSSEC, DNS responses for lazada.sg can be spoofed, potentially redirecting users to malicious sites. This requires coordination with your domain registrar to publish DS records.
Compliance impact
NIST 800-53SC-20
Secure name/address resolution service
How to fix this
1
Check if your DNS provider supports DNSSEC (Cloudflare, Route53, etc.)
2
Enable DNSSEC signing in your DNS provider dashboard
3
Add the DS record to your registrar for .sg TLD
4
Verify: dig +dnssec lazada.sg
5
Upgrade to TLS 1.3
lazada.sg negotiated TLSv1.2. TLS 1.2 is still compliant under all major security frameworks and is not a vulnerability. TLS 1.3 offers faster handshakes and removes legacy cipher negotiation. This is a best-practice improvement, not a compliance gap.
How to fix this
1
Update web server config to prefer TLS 1.3 (nginx: ssl_protocols TLSv1.2 TLSv1.3)
2
Verify: openssl s_client -connect lazada.sg:443 -tls1_3
6
Review certificate configuration
Certificate issues found for lazada.sg: wildcard certificate in use. Wildcard certificates have a broader blast radius if compromised. These are operational hygiene items, not immediate security risks.
How to fix this
1
Consider replacing wildcard cert with individual certs for critical subdomains
2
Consolidate certificate issuance to 1–2 trusted CAs
At a glance
Key data points from the scan.
TLS Version
TLSv1.2
TLSv1.2 negotiated. Issues: TLS 1.2 negotiated (1.3 preferred).
DMARC Policy
p=quarantine
Strengths: DMARC policy set to quarantine; DKIM configured (selectors: default, k1). Issues: No SPF record found.
SPF Record
Missing
No SPF record found.
Security Headers
2/5 present
Missing: CSP, Referrer-Policy, Permissions-Policy
HSTS
Not enabled
HSTS present but max-age is low (0s). Recommended minimum: 15768000 (6 months).
SSL Certificate
Issues
Strengths: Certificate valid, 142 days remaining; Issued by GlobalSign nv-sa. Issues: Wildcard certificate in use — broader attack surface if compromised.
DNSSEC
Not enabled
Strengths: 2 nameservers configured (ns2.alibabadns.com., ns1.alibabadns.com.); 2 MX records present; Zone transfers properly restricted. Issues: DNSSEC not configured — DNS responses can be spoofed.