Skip to content

HTTP Headers: tfl.gov.uk

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-Allow-Origin
Age
CF-Cache-Status
CF-RAY
Cache-Control
Connection
Content-Encoding
Content-Type
Date
Server
Strict-Transport-Security
Vary
Via
X-Backend
X-Banning
X-Cache
X-Cache-Hits
X-Cacheable
X-Frame-Options
X-Proxy-Connection
X-TTL
X-TTL-RULE
X-Varnish
api-entity-payload
ℹī¸ 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.

tfl.gov.uk'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 Tfl
📊 Full Analysis 📋 WHOIS Lookup 🌐 DNS Records 🔒 SSL Certificate âŦ†ī¸ Uptime Status 📑 Full Report