80
zalora.sg
Findings
6
·
0
·
2
Checks
8 passive
Executive Summary
AI-GENERATED
zalora.sg scored 80/100, demonstrating a strong security posture. No material issues found.
Critical gaps in: HSTS Header, Security Headers. Positive signals: TLS Configuration, Known Breaches, DMARC / Email Security all passed.
2 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.
Action Items
Ordered by priority · 2 items
1
Enable HSTS (HTTP Strict Transport Security)
The HSTS header is missing on zalora.sg. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
Compliance Impact
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
Remediation Steps
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://zalora.sg | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
Unlock the full remediation plan
Get detailed steps, compliance mapping, and ownership for all 2 action items. Free — just enter your work email.
No spam. We'll only contact you about this report.
✓ Report unlocked. Scroll down for full details.
2
Add missing security headers (CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy)
5 of 5 recommended security headers are missing on zalora.sg: CSP, X-Content-Type-Options, X-Frame-Options, 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
Remediation Steps
1
Add Content-Security-Policy header (start with report-only to avoid breakage)
2
Add: X-Content-Type-Options: nosniff
3
Add: X-Frame-Options: DENY (or SAMEORIGIN if you use iframes)
4
Add: Referrer-Policy: strict-origin-when-cross-origin
5
Add: Permissions-Policy: camera=(), microphone=(), geolocation=()
6
Verify with: curl -sI https://zalora.sg | grep -iE 'content-security|x-frame|x-content|referrer|permissions'
Scan Findings
HSTS Header
Critical
Security Headers
Critical
TLS Configuration
Healthy
Known Breaches
Healthy
DMARC / Email Security
Healthy
CVE Exposure
Healthy
DNS Configuration
Healthy
Certificate Hygiene
Healthy