HTTP Headers: lyft.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

Connection
Content-Length
Content-Type
Via
X-Amz-Cf-Id
X-Amz-Cf-Pop
X-Cache
accept-ch
cache-control
date
etag
link
referrer-policy
server
set-cookie
strict-transport-security
vary
x-content-type-options
x-envoy-upstream-service-time
x-frame-options
x-ot-span-context

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

lyft.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 Lyft

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