HTTP Headers: accounts.google.com

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
X-Frame-Options
Vary
x-auto-login
x-ua-compatible
Cache-Control
Pragma
Expires
Date
Content-Length
Strict-Transport-Security
Cross-Origin-Resource-Policy
Permissions-Policy
Content-Security-Policy
Report-To
Accept-CH
Cross-Origin-Opener-Policy-Report-Only
Content-Security-Policy-Report-Only
reporting-endpoints
Server
X-XSS-Protection
X-Content-Type-Options
Alt-Svc

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

accounts.google.com'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 Accounts

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