Skip to content

HTTP Headers: digital.gov

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
Accept-Ranges
Access-Control-Allow-Methods
Age
Cache-Control
Connection
Content-Encoding
Content-Length
Content-Type
Date
ETag
Last-Modified
Strict-Transport-Security
Vary
Via
X-Amz-Cf-Id
X-Amz-Cf-Pop
X-Amz-Server-Side-Encryption
X-Cache
X-Content-Type-Options
X-Frame-Options
X-Robots-Tag
X-Server
X-Vcap-Request-Id
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.

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