Skip to content

HTTP Headers: nyt.net

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
Connection
Content-Encoding
Content-Length
Content-Security-Policy
Content-Type
Date
Last-Modified
Server
Set-Cookie
Strict-Transport-Security
Vary
X-API-Version
X-Cache
X-Cache-Hits
X-Content-Type-Options
X-Frame-Options
X-Origin-Time
X-PageType
X-Served-By
X-Timer
X-XSS-Protection
cache-control
onion-location
x-b3-traceid
x-gdpr
x-nyt-app-webview
x-nyt-data-last-modified
x-nyt-edge-cache
x-nyt-route
â„šī¸ 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.

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