HTTP Headers: stape.net

Security score: 40/100

🛡️ Security Headers

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

📋 All Response Headers

Date
Content-Type
Connection
Cache-Control
content-security-policy
vary
x-middleware-rewrite
x-next-i18n-router-locale
cf-cache-status
link
Strict-Transport-Security
x-content-type-options
set-cookie
x-xss-protection
referrer-policy
x-frame-options
Content-Encoding
Server
CF-RAY
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.

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

🔧 More Tools for Stape

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