HTTP Headers: snazzy.ai

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
Connection
Content-Encoding
Content-Type
Date
Ki-CF-Cache-Status
Link
NEL
Report-To
Server
Strict-Transport-Security
Vary
X-Edge-Location-Klb
access-control-allow-headers
access-control-allow-methods
alt-svc
content-security-policy
cross-origin-embedder-policy
cross-origin-embedder-policy-report-only
cross-origin-opener-policy
cross-origin-opener-policy-report-only
cross-origin-resource-policy
ki-cache-type
ki-edge
ki-origin
permissions-policy
referrer-policy
x-content-security-policy
x-content-type-options
x-frame-options
x-geo-country-code
x-kinsta-cache
x-permitted-cross-domain-policies
x-xss-protection

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

snazzy.ai'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 Snazzy

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