HTTP Headers: toss.im

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

Connection
Content-Type
Date
Keep-Alive
Server
X-Frame-Options
age
cache-control
content-encoding
etag
key-event-id
last-modified
vary
via
x-amz-cf-id
x-amz-cf-pop
x-amz-server-side-encryption
x-amz-version-id
x-cache
x-envoy-upstream-service-time
x-toss-event-id
x-toss-response-code-details

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

toss.im'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 Toss

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