HTTP Headers: google.me

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

Cache-Control
Content-Security-Policy-Report-Only
Content-Type
Cross-Origin-Opener-Policy
Date
Expires
Origin-Trial
Permissions-Policy
Report-To
Server
Set-Cookie
Transfer-Encoding
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.

google.me'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 Google

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