Skip to content

HTTP Headers: dragonball.fandom.com

Security score: 40/100

đŸ›Ąī¸ Security Headers
HeaderStatus
Strict-Transport-Security❌ Missing
Content-Security-Policy❌ Missing
X-Content-Type-Options✅ Present
X-Frame-Options✅ Present
X-XSS-Protection❌ Missing
📋 All Response Headers
Accept-Ranges
Age
Cache-Control
Connection
Content-Length
Date
Set-Cookie
Strict-Transport-Security
Vary
X-Cache
X-Cache-Hits
X-Cacheable
X-Served-By
X-Timer
accept-ch
content-encoding
content-language
content-security-policy
content-security-policy-report-only
content-type
last-modified
link
nel
report-to
server-timing
x-content-type-options
x-datacenter
x-envoy-upstream-service-time
x-mobile-app
x-request-id
x-ssexp
â„šī¸ 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.

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