Skip to content

HTTP Headers: market.us

Security score: 40/100

đŸ›Ąī¸ Security Headers
HeaderStatus
Strict-Transport-Security❌ Missing
Content-Security-Policy❌ Missing
X-Content-Type-Options✅ Present
X-Frame-Options✅ Present
X-XSS-Protection❌ Missing
📋 All Response Headers
CF-Cache-Status
CF-RAY
Cache-Control
Connection
Content-Encoding
Content-Security-Policy
Content-Type
Date
Expires
Link
NEL
Permissions-Policy
Pragma
Report-To
Server
Set-Cookie
Strict-Transport-Security
Vary
X-Post-Actual-URL
X-Post-Domain
X-Post-ID
X-Post-PreBook-Corporate
X-Post-PreBook-Multi
X-Post-PreBook-Single
X-Post-Price-Corporate
X-Post-Price-Multi
X-Post-Price-Single
X-Post-Published-Date
X-Post-Publisher
X-Post-Publisher-ID
X-Post-Short-Title
X-Post-Terms
X-Post-Title
X-Post-Url
alt-svc
expect-ct
referrer-policy
x-content-type-options
x-frame-options
x-xss-protection
â„šī¸ 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.

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