Skip to content
https://www.nytimes.com

Security

· 23 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
78
GRADE
C
FIX
5
REVIEW
6
PASS
12
INFO
0
Checks
23
12 PASS 6 REVIEW 5 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
D
Cookie Security
Action
7 cookies analyzed, 8 checks passed
FIX
7 cookies analyzed, 8 checks passed
Info::
Cookie 'nyt-a' has the Secure flag
Warning::
Cookie 'nyt-a' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Info::
Cookie 'nyt-a' has SameSite=None
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 'nyt-purr' has the Secure flag
Warning::
Cookie 'nyt-purr' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Info::
Cookie 'nyt-purr' has SameSite=Lax
Critical::
Cookie 'nyt-geo' is missing the Secure flag
Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
Warning::
Cookie 'nyt-geo' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Warning::
Cookie 'nyt-geo' 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
Critical::
Cookie 'nyt-s-present' is missing the Secure flag
Without the Secure flag, this cookie can be sent over unencrypted HTTP, exposing it to interception.
Warning::
Cookie 'nyt-s-present' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Warning::
Cookie 'nyt-s-present' has no SameSite attribute
Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.
Info::
Cookie 'nyt-traceid' has the Secure flag
Warning::
Cookie 'nyt-traceid' is missing the HttpOnly flag
Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.
Info::
Cookie 'nyt-traceid' has SameSite=None
7 cookies analyzed 3 critical 10 warnings
NameSecureHttpOnlySameSiteSizeIssues
nyt-a✓✗None27 B1
nyt-gdpr✗✗—9 B3
nyt-purr✓✗Lax33 B1
nyt-geo✗✗—9 B3
datadome✓✗Lax9 B1
nyt-s-present✗✗—14 B3
nyt-traceid✓✗None43 B1
D
CSP Inline-Style Readiness
Action
334 inline style attribute(s) detected
FIX
334 inline style attribute(s) detected
Warning::
334 inline style attribute(s) detected
Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 334 inline style(s) is high. Affected element types include: body, button, th, td, span. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.
F
Subresource Integrity
Action
0 of 24 external resources have SRI
FIX
0 of 24 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-1182b3743d46b6ae880fe217339d4333.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 rumcdn.geoedge.be lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //rumcdn.geoedge.be/b3960cc6-bfd2-4adc-910c-6e917e8a6a0e/grumi-ip.js
Warning::
External script from warp.media.net lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://warp.media.net/js/tags/clientag.js?cid=8CU26C87G&dn=www.nytimes.com&ysection=home&version=1
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 link from static01.nytimes.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static01.nytimes.com/newsgraphics/IJ-hEyZ_bx6ARw/_app.jZHl45ZbsyYwTgX2VnjM748N_p-ysimDDLDf5JSNh9Y/immutable/assets/index.DlB3Aa4i.css
Warning::
External link from static01.nytimes.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static01.nytimes.com/newsgraphics/IJ-hEyZ_bx6ARw/_app.jZHl45ZbsyYwTgX2VnjM748N_p-ysimDDLDf5JSNh9Y/immutable/assets/index.CyB6tk6K.css
Warning::
External link from static01.nytimes.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static01.nytimes.com/newsgraphics/IJ-hEyZ_bx6ARw/_app.jZHl45ZbsyYwTgX2VnjM748N_p-ysimDDLDf5JSNh9Y/immutable/assets/index.Sgyas5b-.css
Warning::
External link from static01.nytimes.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://static01.nytimes.com/newsgraphics/IJ-hEyZ_bx6ARw/_app.jZHl45ZbsyYwTgX2VnjM748N_p-ysimDDLDf5JSNh9Y/immutable/assets/index.Yy8mTFpA.css
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/m202605010101/pubads_impl.js?cb=31098277
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.46-BD0KgO-6.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.46-eIyWpkVZ.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-0.2.46-B66aOABk.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-sMrgdKm3.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.46-B7WXkZgX.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.46-SMe7ghvI.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 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 / 24 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>rumcdn.geoedge.be✗ Missing
<script>warp.media.net✗ Missing
<script>static.chartbeat.com✗ Missing
<link>static01.nytimes.com✗ Missing
<link>static01.nytimes.com✗ Missing
<link>static01.nytimes.com✗ Missing
<link>static01.nytimes.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>www.googletagmanager.com✗ Missing
F
Email Security
Action
no DMARC, no SPF
FIX
no DMARC, no SPF
Warning::
No DMARC record found
Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.
Warning::
No SPF record found
Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.
Info::
No DKIM detected via common selectors
DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
Info::
MTA-STS not configured
MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
Info::
TLS-RPT not configured
TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
Info::
BIMI not configured
BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.
DMARC

No DMARC record found

Without DMARC, email receivers have no policy for handling authentication failures from your domain.

Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.

Why this matters

Without DMARC, anyone can send phishing emails using your domain name.

Learn more ▾

DMARC tells receiving mail servers what to do with email that fails SPF/DKIM checks for your domain. With a strict 'p=reject' policy, spoofed emails get bounced; without it they reach the inbox. Domains used in phishing campaigns lose deliverability and brand trust fast.

Source: DMARC.org / NIST

Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all.

Why this matters

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

DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.

Why this matters

No DKIM signature on outbound mail — receivers can't cryptographically prove the message came from your domain.

Learn more ▾

DKIM signs outbound mail with a private key whose public half lives in DNS at <selector>._domainkey.<domain>. Without DKIM, DMARC alone can't tell legitimate mail from spoofs, and large mailbox providers (Gmail, Yahoo) increasingly require DKIM for inbox placement. Note: this check probes a curated list of common selectors; non-standard selectors produce a false negative.

Source: RFC 6376 / Google + Yahoo 2024 sender requirements

MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.

Why this matters

Without MTA-STS, inbound mail can be silently downgraded to plain SMTP by a network attacker.

Learn more ▾

MTA-STS (RFC 8461) tells sending mail servers to use TLS and to refuse delivery if TLS fails. Requires both a TXT record at _mta-sts.<domain> AND a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt. Without it, an active attacker on the network path can strip STARTTLS and read the email in plaintext.

Source: RFC 8461

TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.

Why this matters

Without TLS-RPT, you have no visibility into inbound TLS failures — MTA-STS misconfigurations stay hidden until users complain.

Learn more ▾

TLS-RPT (RFC 8460) is the feedback channel for MTA-STS: senders post aggregate reports of TLS-handshake failures to the URI in your _smtp._tls TXT record. Without it, an MTA-STS misconfiguration silently rejects mail and you find out only when someone notices missing email.

Source: RFC 8460

BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

Why this matters

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

B
Security Headers
7 of 10 headers properly configured
REVIEW
7 of 10 headers properly configured
Info::
Strict-Transport-Security is properly configured
Got: max-age=63072000; includeSubDomains; preload
Info::
X-Content-Type-Options is properly configured
Got: 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: envoy
Info::
Domain is in the Chrome HSTS preload list (status: preloaded)
Got: preloaded

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
WAF / Bot Protection
No WAF detected via response headers
REVIEW
No WAF detected via response headers
Info::
No WAF detected
Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva.
B
Trusted Types (XSS Sink Hardening)
Trusted Types not enabled
REVIEW
Trusted Types not enabled
Info::
Trusted Types not enabled
Trusted Types (CSP3) is a Chrome 83+ defense that requires DOM-XSS sinks (innerHTML, document.write, eval, ...) to receive a typed-and-sanitized value rather than a raw string. Adding `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types default` neutralizes most DOM-XSS even when a payload reaches a sink. Adoption is currently ~0.1% of pages so this is informational; a roll-out usually starts in report-only mode.
B
Open Redirect Surface
1 link(s) carry redirect-shaped query parameter(s)
REVIEW
1 link(s) carry redirect-shaped query parameter(s)
Info::
1 link(s) carry redirect-shaped query parameter(s)
Heuristic flag -- whether each endpoint actually permits an arbitrary redirect target depends on server-side validation. Audit the listed paths' redirect-target handling: the endpoint should either (a) restrict to a relative path, (b) restrict to an allowlisted host set, or (c) sign the target. Open redirects power phishing flows (the attacker's URL begins with your trusted domain) and bypass some SSRF-mitigation cookie scoping. Common parameter names flagged: redirect, redirect_uri, redirect_url, redirecturl, return, returnto, return_to, returnurl, return_url, next, nexturl, next_url, continue, goto, dest, destination, forward, target.
Got: https://myaccount.nytimes.com/auth/login?response_type=cooki…?redirect_uri=...
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
A+
TLS & Certificates
TLS 1.3, 8 checks passed
PASS
TLS 1.3, 8 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::
OCSP stapling enabled
Info::
Certificate is valid (expires in 127 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 127 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 542 days Signature SHA256-RSASerial 90ee8c5de5bfa62d2ae2ff7097c4857
A
security.txt
Vulnerability disclosure policy
PASS
Vulnerability disclosure policy
Info::
security.txt found
Got: https://www.nytimes.com/.well-known/security.txt
Warning::
security.txt: Missing required 'Expires' field (RFC 9116)

security.txt

Contact: https://help.nytimes.com/hc/en-us/articles/115015385887-Contact-Us
A+
Cross-Origin Tab Safety
All 19 new-tab link(s) carry rel=noopener
PASS
All 19 new-tab link(s) carry rel=noopener
Info::
All 19 new-tab link(s) carry rel=noopener
A+
Source Map Exposure
No source maps accessible (probed 3 candidate URL(s))
PASS
No source maps accessible (probed 3 candidate URL(s))
Info::
No source maps accessible across 3 probed candidate(s)
A+
HTML Version Disclosure
No software-version disclosures in HTML
PASS
No software-version disclosures in HTML
Info::
No software-version disclosures in HTML
A+
Auth Security
Page is not a login form -- auth-security checks are N/A
PASS
Page is not a login form -- auth-security checks are N/A
Info::
Page does not appear to be a login form
A+
Subdomain Inventory Exposure
No risky subdomain names in certificate SANs
PASS
No risky subdomain names in certificate SANs
Info::
No risky subdomain names in certificate SANs
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
/package.json✓ Not founddependency-manifest—
/composer.json✓ Not founddependency-manifest—
/Gemfile✓ Not founddependency-manifest—
/Gemfile.lock✓ Not founddependency-manifest—
/requirements.txt✓ Not founddependency-manifest—
/pom.xml✓ Not founddependency-manifest—
/.gitlab-ci.yml✓ Not foundci-config—
/.travis.yml✓ Not foundci-config—
A+
API Surface
No API specs or GraphQL introspection found (probed 11 candidate path(s))
PASS
No API specs or GraphQL introspection found (probed 11 candidate path(s))
Info::
No API specs or GraphQL introspection found (probed 11 path(s))
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