HTTP Headers: criteo.atlassian.net

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

Content-Type
Content-Length
Connection
Date
Served-By
Vary
Content-Security-Policy
Cache-Control
Pragma
Expires
X-Frame-Options
Referrer-Policy
Set-Cookie
Server
X-Content-Type-Options
X-Xss-Protection
Atl-Traceid
Atl-Request-Id
Strict-Transport-Security
Report-To
Nel
X-Ratelimit-Limit
X-Ratelimit-Remaining
X-Ratelimit-Reset
X-Cache
Via
X-Amz-Cf-Pop
X-Amz-Cf-Id
Server-Timing

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

criteo.atlassian.net'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 Criteo

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