HTTP Headers: unicef.de

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

Cache-Control
Connection
Content-Encoding
Content-Security-Policy
Content-Type
Cross-Origin-Opener-Policy
Cross-Origin-Resource-Policy
Date
ETag
NEL
Origin-Agent-Cluster
Referrer-Policy
Report-To
Reporting-Endpoints
Strict-Transport-Security
Vary
X-Cache
X-Content-Type-Options
X-DNS-Prefetch-Control
X-Download-Options
X-Permitted-Cross-Domain-Policies
X-XSS-Protection
x-azure-ref

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

unicef.de'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 Unicef

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