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.
Not measuredabsence here is not evidence of absence
Other pages on this site
Signed-in visitors, other browsers and other regions
Anything that loads only after interaction or consent
Services the catalog does not name
Checks with incomplete evidence
one request on record, same site
one request on record, cross-site
the count is a lower bound; more may exist
not measured
18 distinct catalogued tracking-service entities recorded responses across 73 cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. In the visit labeled GPC off, 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.
Where severity is ranked, the cohort is a curated set of popular, mostly commercial sites, not a random sample of the web.Details
The cards below translate the evidence into plain language. Where a measured distribution exists, severity ranks this visit against percentiles from this report's cohort, with each percentile card naming its metric-specific measured-site denominator; otherwise it uses fixed reference thresholds. That cohort is drawn from a curated set of popular, mostly commercial sites, not a random sample of the web. The request log, domain table, and methodology remain below for verification.
693 requests observed in one controlled visit.
What was checked
Page
https://www.nytimes.com/
When
Aug 14, 2026, 7:08 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 scanner host the report does not name; the network region was not recorded.
Visits
Two visits configured to differ in the Global Privacy Control (GPC) signal: GPC off and GPC on.
Interactions
No typing was recorded in either visit. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence in the GPC on visit was cut short.
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 interaction or consent. 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.
Checks with incomplete evidence. In the GPC on visit only: Brave Shields matches, the privacy policy check, third-party services, named platforms, Google Analytics remarketing, advertising pixels and the consent banner.
Worth checking
185 of 616 requests the engine evaluated matched Brave Shields filter lists
185 requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.
Blocking can also prevent follow-on requests, so this number is neither a measured block count nor what a Brave visit would block.Details
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.
The hand-curated service catalog separately matched 173 request rows in this visit.Show matched requests
Context
This GPC comparison supports no comparable delta
The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching. The variant visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals.
The raw request logs of both visits remain below for transparency, but the diff between them supports no claim about what the compared condition changed.
2 disqualifying conditions named by the report's claim policy.
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.
These matches do not establish a request's purpose, profiling, or an intent to conceal tracking.Details
The scanner followed DNS CNAME chains from first-party subdomains and checked resolved targets against the service catalog and Brave filter lists. 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
Index Exchange, PubMatic and TripleLift, plus 7 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.Details
Named in the policy: Google, Chartbeat and Comscore.
Policy at https://help.nytimes.com/…; 0 checkable statements matched; 3 of 13 observed tracking companies named in the policy. Policy mentions of Magnite and Amazon Ads 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, Magnite and Amazon Ads, plus 15 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.Details
Functional catalog labels include analytics / tag management, advertising and advertising / supply-side platform. This scan could not identify 36 of the 73 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.
383 cross-site requests across 73 third-party hosts.At or above the 90th-percentile mark for third-party domains across the 51 sites measured for this metric. High distinct tracking-service entities count (at or above the 12 reference threshold).Show third-party requests
Context
Requests were dispatched to catalogued major-platform domains
This visit dispatched requests to catalogued domains for Google and LinkedIn.
The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.
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.
This report neither shows nor rules out the sync.Details
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.
googletagmanager.com observed; no google-analytics.com or analytics.google.com request; DoubleClick hosts recorded under generalized names.Show catalog-matched requests
Review-worthy
Third-party cookies were present
75 third-party cookies showed up during the visit.
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.Details
The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary.
107 cookies total in this report.At or above the 90th-percentile mark for third-party cookies across the 51 sites measured for this metric.
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.Details
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: 214 interaction-listener registrations with https://accounts.google.com/, https://cdn.brandmetrics.com/ and https://pay.google.com/, plus 7 others in the registration call chain. Input-monitoring listener coverage: 138 input-listener registrations with https://cdn.brandmetrics.com/, https://*.*.doubleclick.net/ and https://static.chartbeat.com/, plus 3 others in the registration call chain.
Opens this report's request log filtered to accounts.google.com, a script origin recorded in the listener's call chain.
Context
Fingerprint-like browser APIs were called
2 high-entropy API calls appeared in the instrumentation log.
These calls can be legitimate (charts, graphics, media), so the count is observational, not a severity score, and it excludes Web and Service Workers.Details
Top calls: webgl.getParameter.UNMASKED_RENDERER_WEBGL and webgl.getParameter.UNMASKED_VENDOR_WEBGL.
2 API families recorded.
Domain evidence
77 recorded domains
The busiest recorded domains of the GPC off visit, with role, request count, request start times and catalog match.
The Trade Desk: advertising / demand-side platform
service
image
*.privacymanager.io
6
No catalog match
third-party
script, fetch
*.analytics.yahoo.com
6
No catalog match
third-party
document, image
*.media.net
5
Media.net: advertising
service
script, fetch, ping, image
*.chartbeat.net
5
Chartbeat: audience analytics
service
image
*.ads.*.amazon-adsystem.com
5
Amazon Ads: advertising
service
fetch
www.gstatic.com
5
No catalog match
third-party
script
*.adtrafficquality.google
5
No catalog match
third-party
xhr, script, document, image
static.nytimes.com
5
No catalog match
first-party
image
*.scorecardresearch.com
4
Comscore: audience measurement
service
script, image
*.ads.linkedin.com
4
LinkedIn: social / advertising pixel
service
image
pixel.tapad.com
4
No catalog match
third-party
image
www.googletagmanager.com
3
Google: analytics / tag management
service
script
*.criteo.com
3
Criteo: advertising
service
fetch, document
ads.pubmatic.com
3
PubMatic: advertising / supply-side platform
service
document, image
*.rlcdn.com
3
LiveRamp: identity / advertising
service
image
+47 more in the evidence explorer below.
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.
cut short: request evidence was censored before completion: the producer recorded an additional collection loss (recorded loss count: 1); recorded by the scanner
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. How detector accuracy is measured.
Severity percentiles come from this report's exact schema, methodology, tracker-catalog, ServiceRole-taxonomy, metric-contract, producer, and Global Privacy Control cohort. Each percentile card's measured sites are among 99 sites with a successful load across all cohorts. Other methodologies and post-choice consent visits are excluded from each card's denominator, while failed or block-page attempts are outside that coverage. Visits with capped or incomplete request evidence are left out of each mark. They tend to be the heaviest pages, so a mark can sit lower than the cohort's true mark.
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 .