Skip to content

HTTP Headers: fao.org

Security score: 60/100

🛡ī¸ Security Headers
HeaderStatus
Strict-Transport-Security✅ Present
Content-Security-Policy❌ Missing
X-Content-Type-Options✅ Present
X-Frame-Options✅ Present
X-XSS-Protection❌ Missing
📋 All Response Headers
Access-Control-Expose-Headers
CF-Cache-Status
CF-Ray
Cache-Control
Connection
Content-Encoding
Content-Security-Policy
Content-Type
Date
Expires
Last-Modified
Referrer-Policy
Request-Context
Server
Strict-Transport-Security
Vary
X-Content-Type-Options
X-Frame-Options
X-XSS-Protection
sf-cache-key
sf-cache-status
ℹī¸ 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.

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

🔧 More Tools for Fao
📊 Full Analysis 📋 WHOIS Lookup 🌐 DNS Records 🔒 SSL Certificate âŦ†ī¸ Uptime Status 📑 Full Report