Skip to content

HTTP Headers: traffic2archive.github.io

Security score: 0/100

🛡ī¸ Security Headers
HeaderStatus
Strict-Transport-Security❌ Missing
Content-Security-Policy❌ Missing
X-Content-Type-Options❌ Missing
X-Frame-Options❌ Missing
X-XSS-Protection❌ Missing
📋 All Response Headers
Connection
Content-Length
Server
Content-Type
ETag
Content-Security-Policy
Content-Encoding
X-GitHub-Request-Id
Accept-Ranges
Date
Via
Age
X-Served-By
X-Cache
X-Cache-Hits
X-Timer
Vary
X-Fastly-Request-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.

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