Skip to content

HTTP Headers: medicaid.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-Origin
Cache-Control
Connection
Content-Encoding
Content-Language
Content-Length
Content-Type
Date
ETag
Expires
Last-Modified
Strict-Transport-Security
Vary
X-AH-Environment
X-Age
X-Cache-Hits
X-Content-Type-Options
X-Drupal-Dynamic-Cache
X-Frame-Options
X-Generator
X-Permitted-Cross-Domain-Policies
X-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.

medicaid.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.