HTTP Headers: secure.login.gov

Security score: 60/100

🛡️ Security Headers

Header	Status
Strict-Transport-Security	✅ Present
Content-Security-Policy	❌ Missing
X-Content-Type-Options	✅ Present
X-Frame-Options	✅ Present
X-XSS-Protection	❌ Missing

📋 All Response Headers

Content-Type
Content-Length
Connection
Date
strict-transport-security
x-frame-options
x-xss-protection
x-content-type-options
x-permitted-cross-domain-policies
referrer-policy
x-download-options
cache-control
pragma
link
vary
content-security-policy
set-cookie
x-request-id
x-runtime
X-Cache
Via
X-Amz-Cf-Pop
Alt-Svc
X-Amz-Cf-Id

ℹ️ 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.

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

🔧 More Tools for Secure

📊 Full Analysis 📋 WHOIS Lookup 🌐 DNS Records 🔒 SSL Certificate ⬆️ Uptime Status 📑 Full Report