SBL-CORR-2026-002: The policy entity matcher did not recognize Amazon and Oracle under their catalog names. An unmentioned-entity result for Amazon Ads or Oracle Advertising is not reliable evidence that the policy omitted the company. Original policy text was not retained, so individual mention results cannot be reconstructed. Consult all clarification events for this report.
nytimes.com contacted catalogued Google domains during this visit.
9 distinct catalogued tracking-service entities recorded responses across 39 cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. It also looks like keyboard-input listeners were registered through a call chain that included a cross-site script. SBL-CORR-2026-002: The policy entity matcher did not recognize Amazon and Oracle under their catalog names. An unmentioned-entity result for Amazon Ads or Oracle Advertising is not reliable evidence that the policy omitted the company. Original policy text was not retained, so individual mention results cannot be reconstructed. Consult all clarification events for this report.
The scan observed signals a non-expert should not have to decode from raw request tables.
The cards below translate the evidence into plain language; severity reflects fixed reference thresholds, not measured population percentiles. The request log, domain table, and methodology remain below for verification.
683 requests observed in one controlled visit.
What was checked
Page
https://www.nytimes.com/
When
Jul 2, 2026, 2:34 PM UTC
Setup
Both visits used headless Chromium in a desktop window of 1440 × 980, with en-US language and UTC time zone. Both ran from a GitHub Actions Ubuntu runner; the network region was not recorded. Both were configured to send the Global Privacy Control (GPC) signal; this report records no readback of it.
Visits
Two visits configured to differ in the cookie-banner choice: Accept-all attempt and Reject-all attempt.
Interactions
No typing was recorded in either visit. Asked to choose "Accept all" on a cookie banner in one visit and "Reject all" in the other; no activated choice was recorded in either. No scrolling and no other clicks.
Outcome
Both visits completed.
What these visits could not see
Other pages on this site. Only the requested page's activity was recorded. The privacy policy was opened only to read its text, and none of its activity was recorded.
Signed-in visitors, other browsers and other regions. Both visits were automated, from a fixed en-US / UTC profile. Sites can behave differently for real users, browsers, regions, accounts, or network locations.
Anything that loads only after further interaction. Trackers that load that late are not observed, so counts are a lower bound.
Services the catalog does not name. Service labels use a US-biased hand-curated catalog, so regional services may be under-labeled.
Worth checking
100 requests matched Brave Shields filter lists
100 requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.
Computed with Brave's own ad-block engine and default filter lists in classification mode: matched requests were not blocked by the scanner and remain in this report's observed request counts. This is Site Behavior Lab's list-based simulation, which applies every list to the site's own requests too. Brave's default Standard setting skips most of these lists for such requests, so its results can differ. Blocking can also prevent follow-on requests, so this number is neither a measured block count nor what a Brave visit would block.
The hand-curated service catalog separately matched 60 request rows in this visit.Show matched requests
Context
No consent control activation was recorded in either visit
Neither visit recorded a control activation, so neither can be shown to reflect the choice it attempted, and this diff mostly shows run-to-run variance.
Many consent banners are only shown to visitors in regions where the law requires them (the EEA, UK, or California), so this scanner's location may simply not be served one. A banner may also use controls this scanner's catalog does not recognize. Or a click may have been dispatched on a candidate that showed no observable reaction within the scanner's confirmation window. No claim about the site's consent behavior can be made from this pair of visits.
Third-party request totals are not comparable across these two visits, so no count delta is quoted.
Worth checking
1 first-party DNS alias matched tracking checks
Of the resolved targets, 1 matched Brave filter lists; those matches do not identify the operators.
The scanner followed DNS CNAME chains from first-party subdomains and checked resolved targets against the service catalog and Brave filter lists. These matches do not establish a request's purpose, profiling, or an intent to conceal tracking. A filter-list match alone is not a verified service identity or proof of tracking.
Tracking companies the privacy policy does not appear to name
Media.net, PubMatic and Criteo, plus 3 others were sent requests during this visit. However, the policy text matched none of the names this scan knows those companies by.
Policies often disclose vendor categories rather than company names, so an unnamed vendor is a transparency gap worth reviewing, not automatically a violation. Named in the policy: Google.
Policy at https://www.nytimes.com/privacy/…; 0 checkable statements matched; 1 of 7 observed tracking companies named in the policy. Policy mentions of Amazon Ads and Magnite are unknown because the historical alias matcher was incomplete.
Opens the request log at its catalog-matched rows, which include the requests to the companies this card names.
Review-worthy
Catalogued service domains recorded responses during this visit
Google, Amazon Ads and Magnite, plus 6 others appeared in the request log.
A catalog match identifies a maintainer-reviewed service/domain mapping; it does not establish why an individual request occurred, what it carried, or whether profiling happened. Functional catalog labels include analytics / tag management, advertising and advertising / supply-side platform. This scan could not identify 14 of the 39 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site. The role taxonomy assigns these additional services explicitly non-tracking operational, support, security, consent-management, or hosting roles: Datadog.
Google Tag Manager loaded; a remarketing sync cannot be told from this report
This visit contacted Google Tag Manager and recorded no request to a Google Analytics collection host. It also recorded DoubleClick hosts whose names this report generalizes, the remarketing sync host's among them.
Tag Manager is a loader. It can fetch Google Analytics or other tags, or none; this report cannot tell which it fetched here. The sync goes to stats.g.doubleclick.net, and a published report writes that name the same way as DoubleClick's ad-serving hosts. This report neither shows nor rules out the sync.
googletagmanager.com observed; no google-analytics.com or analytics.google.com request; DoubleClick hosts recorded under generalized names.Show catalog-matched requests
Context
Third-party cookies were present
4 third-party cookies showed up during the visit.
The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary. This report does not retain cookie values or partition keys, so it does not establish whether a cookie was a persistent identifier or could recognize a visitor across sites.
Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.
Context
Input-monitoring signal involving a third-party script
Listener coverage that could observe typing-related input events was registered through call chains that included a third-party script.
This is a behavioral instrumentation signal from listener registration, stack-attributed script origins, and known-vendor requests: it shows the page was instrumented to observe interaction, not that anything was transmitted. Stack attribution records the script origins present in the bounded registration call chain. A cross-site origin in that chain does not by itself establish that the cross-site script registered the listener. That is because first-party code can register its own listeners through a helper served from elsewhere. A different registrable domain is also not by itself a different operator: sites commonly serve their own scripts from a separate asset domain. The card therefore says third party only when the catalog or reviewed ownership attributes an origin to another organization. On scanners that run the active keystroke-capture probe, actual transmission is tested separately (a synthetic value is typed, never real input, and no typed values are collected). Treat this card as a review prompt rather than proof.
Session-recording listener coverage: 279 interaction-listener registrations attributed across https://accounts.google.com/, https://cdn.brandmetrics.com/ and https://cdn.doubleverify.com/, plus 8 others and same-site origins the probe could not separate. Input-monitoring listener coverage: 112 input-listener registrations attributed across https://cdn.brandmetrics.com/, https://*.*.doubleclick.net/ and https://static.chartbeat.com/, plus 3 others and same-site origins the probe could not separate.
Opens this report's request log filtered to accounts.google.com, a script origin recorded in the listener's call chain.
Context
WebGL entropy-read heuristic matched only under the earlier single-signal rule
A WebGL detection satisfied only the earlier single-signal rule, so it is shown as an observation, not counted as a heuristic match.
Only the earlier single-signal rule matched: before 2026-07-20 the scanner recorded the WebGL heuristic after either a WebGL parameter read or a pixel readback, and the current rule requires both. WebGL calls can be legitimate (charts, graphics, maps), so this is a review prompt for this visit, not proof of fingerprinting.
31 parameter reads and 0 pixel readbacks; parameters: webgl.getParameter.UNMASKED_RENDERER_WEBGL, webgl.getParameter.UNMASKED_VENDOR_WEBGL and webgl2.getParameter.UNMASKED_RENDERER_WEBGL, plus 1 other
Raw evidence
Open the interactive evidence explorer
The findings above are built from the stored report. Load the request rows, domains, cookies, storage keys, browser signals, visit phases, charts and CSV export when you want to check them; the versioned report JSON is always available below without this interface.
This versioned report is currently retained in the public corpus. Follow the currently retained site history, repeat the same public route when it is available, or request a transparent evidence correction.
Exact build and instrument digests were not recorded by this legacy schema.
Variant visit
Started
Run quality
complete; derived from status and warnings
Scanner
playwright-chromium
Browser
149.0.7827.55
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.
Recorded provenance is self-reported measurement metadata, not a cryptographic attestation. The public versioned report JSON contains the retained public evidence; see the methodology for interpretation and retention limits.
This report covers what the scanner measures, not everything a site can do. 17 browser surfaces are not instrumented at all (Every page except the one that was scanned; Anything that only loads after scrolling or interaction; Why a request happened, as a causal chain; and 14 others), 3 capabilities are declined by policy, and 3 are outside what any single visit can see. Their absence from this report is not evidence that they did not occur. Read the published coverage boundary.
Detector accuracy is unmeasured. No calibration study currently publishes a precision or recall for the detectors on this page, so a detector match here is a recorded observation, not a calibrated classification. A study has been recorded for pixel-events and does not support a published rate under the current build. How detector accuracy is measured.
Approved use boundary: This report is investigative evidence that requires independent corroboration. It is not a standalone legal determination and not the sole exhibit in a legal proceeding. Recorded in this project's release manifest on .