HTTP Headers: eye.security

Security score: 0/100

🛡️ Security Headers

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

📋 All Response Headers

CF-Cache-Status
CF-Ray
Cache-Control
Connection
Content-Encoding
Content-Type
Date
Last-Modified
Link
Server
Set-Cookie
Strict-Transport-Security
Vary
access-control-allow-credentials
alt-svc
cache-tag
content-security-policy
edge-cache-tag
referrer-policy
server-timing
x-content-type-options
x-frame-options
x-hs-cache-config
x-hs-cfworker-meta
x-hs-content-campaign-id
x-hs-content-id
x-hs-hub-id
x-hs-portal-id
x-hubspot-correlation-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.

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

🔧 More Tools for Eye

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