Skip to content

HTTP Headers: walmart.us

Security score: 0/100

🛡ī¸ Security Headers
HeaderStatus
Strict-Transport-Security❌ Missing
Content-Security-Policy❌ Missing
X-Content-Type-Options❌ Missing
X-Frame-Options❌ Missing
X-XSS-Protection❌ Missing
📋 All Response Headers
Accept-Ranges
Content-Encoding
Content-Length
Content-Security-Policy
Content-Type
Server-Timing
Traceparent
X-Envoy-Upstream-Service-Time
X-Frame-Options
X-Opt-Inj
X-Tb
Expires
Cache-Control
Pragma
Date
Connection
Vary
Set-Cookie
Cache-Status
Origin-EX
Origin-CC
Permissions-Policy
Accept-CH
Strict-Transport-Security
ℹī¸ About HTTP Security Headers

Strict-Transport-Security (HSTS) forces browsers to use HTTPS. Content-Security-Policy (CSP) prevents XSS attacks by controlling which resources can load. X-Content-Type-Options stops MIME-type sniffing. X-Frame-Options blocks clickjacking by preventing iframe embedding.

walmart.us's security score of 0/100 reflects how many of these protective headers are configured. Higher scores indicate better defense against common web attacks.

🔧 More Tools for Walmart
📊 Full Analysis 📋 WHOIS Lookup 🌐 DNS Records 🔒 SSL Certificate âŦ†ī¸ Uptime Status 📑 Full Report