Skip to content
https://nytimes.com

Security

· 12 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
5
PASS
5
INFO
0
Checks
12
5 PASS 5 REVIEW 2 FIX
D
Content Security Policy
Action
4 of 10 CSP checks passed
FIX
4 of 10 CSP checks passed
Info::
Raw CSP policy
Got: upgrade-insecure-requests; default-src data: 'unsafe-inline' 'unsafe-eval' https: nytresource:; script-src data: 'unsafe-inline' 'unsafe-eval' https: blob: nytresource:; style-src data: 'unsafe-inline' https: nytresource:; img-src data: https: blob: android-webview-video-poster: nytresource:; font-src data: https: nytresource:; connect-src data: https: wss: blob: nytresource:; media-src data: https: blob: nytresource:; object-src https:; child-src https: data: blob: nytresource:; form-action https: nytimes: nytcooking: nytxwd:; report-uri https://csp.nytimes.com/report;
Info::
default-src directive is set
Got: default-src data: 'unsafe-inline' 'unsafe-eval' https: nytresource:
Critical::
'unsafe-inline' found in script source
'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.
Got: script-src data: 'unsafe-inline' 'unsafe-eval' https: blob: nytresource:
Critical::
'unsafe-eval' found in script source
'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.
Got: script-src data: 'unsafe-inline' 'unsafe-eval' https: blob: nytresource:
Info::
No wildcard in script source
Warning::
object-src allows plugin content
Set object-src to 'none' to prevent Flash/Java plugin exploits.
Got: object-src https: Expected: object-src 'none'
Warning::
base-uri directive is missing
Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
Expected: base-uri 'self'
Warning::
frame-ancestors directive is missing
frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.
Expected: frame-ancestors 'self'
Info::
form-action directive is set
Got: form-action https: nytimes: nytcooking: nytxwd:
Info::
upgrade-insecure-requests is enabled

'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.

Why this matters

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Learn more ▾

unsafe-inline allows inline <script> tags; unsafe-eval allows eval() and similar. Both are necessary for some legacy code but explicitly dangerous. Migrate to nonces (per-page random tokens) or hashes (per-script SHA-256) instead.

Source: OWASP CSP / MDN

'unsafe-eval' allows eval() and similar functions, enabling code injection. Remove it.

Why this matters

Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.

Learn more ▾

unsafe-inline allows inline <script> tags; unsafe-eval allows eval() and similar. Both are necessary for some legacy code but explicitly dangerous. Migrate to nonces (per-page random tokens) or hashes (per-script SHA-256) instead.

Source: OWASP CSP / MDN

Set object-src to 'none' to prevent Flash/Java plugin exploits.

Expected: object-src 'none'
Why this matters

object-src open in CSP allows Flash/PDF/plugin embedding — a now-deprecated attack vector that should be explicitly blocked.

Learn more ▾

object-src controls <object>, <embed>, and <applet> elements. Modern sites have no need for plugins; setting `object-src 'none'` blocks an entire class of legacy XSS vectors at zero cost. If your CSP missed it, add the directive.

Source: MDN CSP

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'
Why this matters

Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.

Learn more ▾

A common omission: developers add CSP for script-src and frame-ancestors but forget base-uri. The result is a CSP that looks strict but lets an attacker rewrite every URL on the page via <base href>. Add `base-uri 'self'` to close the gap.

Source: MDN CSP

frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.

Expected: frame-ancestors 'self'
Why this matters

Security gaps expose your site and users to attacks, eroding trust.

Parsed Policy

upgrade-insecure-requests
default-src data:'unsafe-inline''unsafe-eval'https:nytresource:
script-src data:'unsafe-inline''unsafe-eval'https:blob:nytresource:
style-src data:'unsafe-inline'https:nytresource:
img-src data:https:blob:android-webview-video-poster:nytresource:
font-src data:https:nytresource:
connect-src data:https:wss:blob:nytresource:
media-src data:https:blob:nytresource:
object-src https:
child-src https:data:blob:nytresource:
form-action https:nytimes:nytcooking:nytxwd:
report-uri https://csp.nytimes.com/report
F
Subresource Integrity
Action
0 of 20 external resources have SRI
FIX
0 of 20 external resources have SRI
Warning::
External script from dd.nytimes.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://dd.nytimes.com/tags.js
Warning::
External script from www.datadoghq-browser-agent.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.datadoghq-browser-agent.com/us1/v6/datadog-rum.js
Warning::
External link from g1.nyt.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://g1.nyt.com/fonts/css/web-fonts.c851560786173ad206e1f76c1901be7e096e8f8b.css
Warning::
External script from static01.nyt.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static01.nyt.com/vi-assets/static-assets/fides-e7243ebfa531534e8ccb023358c656ed.js
Warning::
External script from pagead2.googlesyndication.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //pagead2.googlesyndication.com/tag/js/gpt.js
Warning::
External script from static.chartbeat.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //static.chartbeat.com/js/chartbeat_mab.js
Warning::
External script from pagead2.googlesyndication.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://pagead2.googlesyndication.com/tag/js/gpt.js
Warning::
External script from pagead2.googlesyndication.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://pagead2.googlesyndication.com/pagead/managed/js/gpt/m202604140101/pubads_impl.js?cb=31097865
Warning::
External script from static01.nyt.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static01.nyt.com/video-static/betamax/poster-0.2.40-CFXJA1Fq.js
Warning::
External script from static01.nyt.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static01.nyt.com/video-static/betamax/cover-0.2.40-DtYyWQLl.js
Warning::
External script from static01.nyt.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static01.nyt.com/video-static/betamax/overlay-controls-Df1-R5DD.js
Warning::
External script from static01.nyt.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static01.nyt.com/video-static/betamax/player-CKCxHe9J.js
Warning::
External script from static01.nyt.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static01.nyt.com/video-static/betamax/video-feed-0.2.40-BZ-zSyuf.js
Warning::
External script from pay.google.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://pay.google.com/gp/p/js/pay.js
Warning::
External script from static01.nyt.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static01.nyt.com/video-static/betamax/pool-0.2.40-D37jd-c4.js
Warning::
External script from pagead2.googlesyndication.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //pagead2.googlesyndication.com/tag/js/gpt.js
Warning::
External script from a1.nyt.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://a1.nyt.com/analytics/show-ads.js
Warning::
External script from accounts.google.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://accounts.google.com/gsi/client
Warning::
External link from accounts.google.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://accounts.google.com/gsi/style
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtm.js?id=GTM-P528B3&gtm_auth=tfAzqo1rYDLgYhmTnSjPqw&gtm_preview=env-130&gtm_cookies_win=x
SRI Coverage 0 / 20 of external resources have integrity hashes
TagDomainIntegrity
<script>dd.nytimes.com✗ Missing
<script>www.datadoghq-browser-agent.com✗ Missing
<link>g1.nyt.com✗ Missing
<script>static01.nyt.com✗ Missing
<script>pagead2.googlesyndication.com✗ Missing
<script>static.chartbeat.com✗ Missing
<script>pagead2.googlesyndication.com✗ Missing
<script>pagead2.googlesyndication.com✗ Missing
<script>static01.nyt.com✗ Missing
<script>static01.nyt.com✗ Missing
<script>static01.nyt.com✗ Missing
<script>static01.nyt.com✗ Missing
<script>static01.nyt.com✗ Missing
<script>pay.google.com✗ Missing
<script>static01.nyt.com✗ Missing
<script>pagead2.googlesyndication.com✗ Missing
<script>a1.nyt.com✗ Missing
<script>accounts.google.com✗ Missing
<link>accounts.google.com✗ Missing
<script>www.googletagmanager.com✗ Missing
C
Security Headers
Action
6 of 10 headers properly configured
REVIEW
6 of 10 headers properly configured
Info::
Strict-Transport-Security is properly configured
Got: max-age=63072000; includeSubDomains; preload
Warning::
X-Content-Type-Options header is missing
This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.
Expected: nosniff
Info::
X-Frame-Options is properly configured
Got: DENY
Warning::
Referrer-Policy header is missing
Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
Expected: strict-origin-when-cross-origin
Info::
Permissions-Policy is set
Got: browsing-topics=()
Info::
Content-Security-Policy is present
Got: upgrade-insecure-requests; default-src data: 'unsafe-inline' 'unsafe-eval' https…
Warning::
Cross-Origin-Opener-Policy header is missing
COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
Expected: same-origin
Warning::
Cross-Origin-Embedder-Policy header is missing
COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
Expected: require-corp
Info::
X-Powered-By header is not present
Info::
Server header is present without version info
Got: Varnish

This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.

Expected: nosniff
Why this matters

MIME sniffing lets browsers run uploaded files as JavaScript, turning a file upload into an XSS.

Learn more ▾

Setting X-Content-Type-Options: nosniff tells browsers to trust your declared Content-Type instead of guessing. Without it, an attacker who uploads a polyglot file can sometimes get it executed as a script. One header, no downside.

Source: OWASP / MDN

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin
Why this matters

Default browser behavior leaks full URLs (including query params and tokens) to every third-party resource — set a strict policy.

Learn more ▾

Without a Referrer-Policy header, browsers send the full referring URL with images, scripts, and fonts loaded from third-party origins. URLs containing tokens, user IDs, or session params end up in third-party logs. Set `Referrer-Policy: strict-origin-when-cross-origin` (or stricter) to limit leakage.

Source: MDN / W3C

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin
Why this matters

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Learn more ▾

Cross-Origin-Opener-Policy: same-origin prevents cross-origin pages from sharing a browsing-context group with yours. This blocks cross-window references that enable Spectre-style timing attacks and tab-nabbing. Required if you want to enable SharedArrayBuffer.

Source: MDN / web.dev

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp
Why this matters

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Learn more ▾

Cross-Origin-Embedder-Policy: require-corp ensures every embedded resource (script, iframe, image) explicitly allows being loaded cross-origin. Combined with COOP, this enables the cross-origin-isolated context that unlocks SharedArrayBuffer, high-resolution timers, and other powerful APIs.

Source: MDN / web.dev

B
Cookie Security
2 cookies analyzed, 2 checks passed
REVIEW
2 cookies analyzed, 2 checks passed
Critical::
Cookie 'nyt-gdpr' is missing the Secure flag
Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
Warning::
Cookie 'nyt-gdpr' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Warning::
Cookie 'nyt-gdpr' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
Info::
Cookie 'datadome' has the Secure flag
Warning::
Cookie 'datadome' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Info::
Cookie 'datadome' has SameSite=Lax
2 cookies analyzed 1 critical 3 warnings
NameSecureHttpOnlySameSiteSizeIssues
nyt-gdpr✗✗—9 B3
datadome✓✗Lax9 B1
C
Permissions-Policy
Action
1 directives, 5 missing
REVIEW
1 directives, 5 missing
Info::
browsing-topics=() — blocked for all origins
Info::
camera not restricted
Consider adding camera=() to block camera access from embedded content.
Info::
microphone not restricted
Consider adding microphone=() to block microphone access from embedded content.
Info::
geolocation not restricted
Consider adding geolocation=() to block geolocation access from embedded content.
Info::
payment not restricted
Consider adding payment=() to block payment access from embedded content.
Info::
usb not restricted
Consider adding usb=() to block usb access from embedded content.

Raw Header

browsing-topics=()

Feature Permissions

Blocked Self Only Unrestricted Not Set
browsing-topics Blocked
camera Not Set
microphone Not Set
geolocation Not Set
payment Not Set
usb Not Set
B
CORS Configuration
No CORS headers
REVIEW
No CORS headers
Info::
No CORS headers present — secure default
CORS Configuration ✓ Secure

No CORS headers detected.

Cross-origin requests are blocked by browser same-origin policy.

Origin reflection test

Some servers mirror the request Origin header, which can be exploited. Test manually:

curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control
B
security.txt
Published with 1 contact(s)
REVIEW

security.txt

Contact: https://help.nytimes.com/hc/en-us/articles/115015385887-Contact-Us
A+
TLS & Certificates
TLS 1.3, 7 checks passed
PASS
TLS 1.3, 7 checks passed
Info::
TLS 1.3 is used
Got: TLS 1.3
Info::
Strong cipher suite is used
Got: TLS_AES_128_GCM_SHA256
Info::
HTTP/2 is not negotiated
HTTP/2 provides multiplexing and header compression for better performance.
Got: http/1.1
Info::
Certificate is valid (expires in 150 days)
Got: 2026-09-13T23:59:59Z
Info::
Certificate chain has 2 certificates
Info::
Certificate uses modern signature algorithm
Got: SHA256-RSA
Info::
Certificate covers 29 domain(s)
Got: nytimes.com, www.homedelivery.nytimes.com, *.api.dev.nytimes.com, *.api.nytimes.com, *.api.stg.nytimes.com, *.blogs.nytimes.com, *.blogs.stg.nytimes.com, *.dev.nyt.com, *.dev.nyt.net, *.dev.nytimes.com, *.newsdev.nyt.net, *.newsdev.nytimes.com, *.nyt.com, *.nyt.net, *.nytco.com, *.nytimes.com, *.payflow.sbx.nytimes.com, *.sbx.nytimes.com, *.stg.newsdev.nyt.net, *.stg.newsdev.nytimes.com, *.stg.nyt.com, *.stg.nyt.net, *.stg.nytimes.com, *.timestalks.com, nyt.com, nyt.net, nytco.com, timestalks.com, *.myaccount-preview.stg.nytimes.com
Info::
Certificate is issued by a trusted CA
Got: CN=Thawte TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US

HTTP/2 provides multiplexing and header compression for better performance.

Why this matters

HTTP/1.1 forces the browser to make sequential requests, multiplying latency on every page.

Learn more ▾

HTTP/2 (and HTTP/3) multiplex many requests over a single connection, eliminating head-of-line blocking. HTTP/1.1 forces the browser to either queue requests or open many parallel connections — both worse. Most modern web servers support HTTP/2 with one config line.

Source: MDN Web Docs

Connection
Protocol
TLS 1.3
Cipher Suite
TLS_AES_128_GCM_SHA256
HTTP Version
HTTP/1.1

Certificate Chain

Leaf Certificate
Subject CN=nytimes.comIssuer CN=Thawte TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2026-02-27T00:00:00Z → 2026-09-13T23:59:59ZExpires in 150 days SANs nytimes.com, www.homedelivery.nytimes.com, *.api.dev.nytimes.com, *.api.nytimes.com, *.api.stg.nytimes.com, *.blogs.nytimes.com, *.blogs.stg.nytimes.com, *.dev.nyt.com, *.dev.nyt.net, *.dev.nytimes.com, *.newsdev.nyt.net, *.newsdev.nytimes.com, *.nyt.com, *.nyt.net, *.nytco.com, *.nytimes.com, *.payflow.sbx.nytimes.com, *.sbx.nytimes.com, *.stg.newsdev.nyt.net, *.stg.newsdev.nytimes.com, *.stg.nyt.com, *.stg.nyt.net, *.stg.nytimes.com, *.timestalks.com, nyt.com, nyt.net, nytco.com, timestalks.com, *.myaccount-preview.stg.nytimes.comSignature SHA256-RSASerial 3fd1a181fd505218b6438a747b76185
Intermediate (CA Certificate)
Subject CN=Thawte TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=USIssuer CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2017-11-02T12:24:25Z → 2027-11-02T12:24:25ZExpires in 564 days Signature SHA256-RSASerial 90ee8c5de5bfa62d2ae2ff7097c4857
A+
JS Library Vulnerabilities
No known vulnerabilities
PASS
No known vulnerabilities
Info::
No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+
Information Leakage
No exposures
PASS
No exposures
Info::
security.txt is present — good practice
Info::
No sensitive files exposed

No sensitive files exposed — all paths returned 404.

PathStatusCategoryRisk
/.git/HEAD✓ Not foundVersion Control—
/.git/config✓ Not foundVersion Control—
/.svn/entries✓ Not foundVersion Control—
/.env✓ Not foundConfiguration—
/.env.local✓ Not foundConfiguration—
/.env.production✓ Not foundConfiguration—
/wp-config.php✓ Not foundConfiguration—
/.htaccess✓ Not foundConfiguration—
/phpinfo.php✓ Not foundDebug—
/server-status✓ Not foundDebug—
/server-info✓ Not foundDebug—
/.well-known/security.txt✗ ExposedSecurity PolicyInfo
A+
Email Security
DMARC: reject
PASS
DMARC: reject
Info::
DMARC policy is reject — strongest protection
DMARC
Policy reject — strongest protection Record v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email,mailto:dmarc.report@nytimes.com
A
Transport Security
HTTP/3, HSTS, and TLS version analysis
PASS
HTTP/3, HSTS, and TLS version analysis
Info::
HTTP/3 (QUIC) not advertised
HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
Info::
HSTS enabled (includeSubDomains, preload)
Info::
HSTS preload enabled
Info::
TLS 1.3 in use (fastest handshake, 1-RTT)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback