Skip to content

HTTP Headers: play.google

Security score: 60/100

🛡ī¸ Security Headers
HeaderStatus
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
Vary
x-ua-compatible
Cache-Control
Pragma
Expires
Date
Content-Length
P3P
Strict-Transport-Security
Cross-Origin-Opener-Policy
Permissions-Policy
Content-Security-Policy
Cross-Origin-Resource-Policy
Accept-CH
Content-Security-Policy-Report-Only
reporting-endpoints
Server
X-XSS-Protection
X-Frame-Options
X-Content-Type-Options
Set-Cookie
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.

play.google'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 Play
📊 Full Analysis 📋 WHOIS Lookup 🌐 DNS Records 🔒 SSL Certificate âŦ†ī¸ Uptime Status 📑 Full Report