Site Behavior Lab
Site

www.usatoday.com

Baseline visit
Requested address
https://www.usatoday.com/
Report ID
20260928-4212ecc80b5c9feb0d13786ad2fa14f3
Evidence SHA-256
c255e81b2b0d984ef1f442a901fc813b183a3457925ea51fc70f1ebd3e892119
Scanner
playwright-chromium

usatoday.com's retained request log includes catalogued Google and LinkedIn domains.

Where this page's requests went

The No blocking visit. One mark is one request row in the retained log.

www.usatoday.com itselfat least 72 retained requestsrequests that stayed on the site
Catalogued servicesat least 431 retained requests22 names: PubMatic 75, Google 60, Taboola 54, Magnite 48, Amazon Ads 28, and 17 more
Hosts the catalog does not nameat least 497 retained requests138 hosts; the catalog cannot say who operates them
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

Retained request rows include 22 distinct catalogued tracking-service entities; 22 of the retained service matches recorded responses across at least 173 retained cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried.

≥22tracking-service entities retained
≥928cross-site requests
Snapshot incompletethird-party cookie records

Review-worthy

Bottom line: this visit has review-worthy signals

The scan observed signals a non-expert should not have to decode from raw request tables. Some activity evidence was also incomplete: request counts are retained lower bounds, cookie counts are an incomplete end-state snapshot and storage counts are an incomplete end-state snapshot.

This failed or incomplete evidence is not ranked against corpus percentiles; positive signals remain visible as lower bounds. Details

The cards below translate the evidence into plain language. The request log, domain table, and methodology remain below for verification.

At least 1,000 retained requests observed in one controlled visit.

What was checked

Page
https://www.usatoday.com/
When
Sep 28, 2026, 12:00 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. Neither sent the Global Privacy Control (GPC) signal.
Visits
Two visits configured to differ in Brave-list blocking: No blocking and Brave-list blocking.
Interactions
Typed a made-up test value into 1 form field in the No blocking visit, never submitting the form; no typing was recorded in the Brave-list blocking visit. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence 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 No blocking visit: every check. In the Brave-list blocking visit: the typing test. Every card below states only what was retained.

Worth checking

At least 511 retained requests matched Brave Shields filter lists

At least 511 retained 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 at least 431 retained request rows in this visit.Show matched requests

Context

This Shields comparison is not conclusive

The "No blocking" visit hit the 1,000-request recording cap, so its counts are truncated. The "No blocking" visit's synthetic form-input probe stopped one or more navigations, so its request evidence is incomplete. The "No blocking" visit had one or more requests refused by the scanner's own network guard, so its request evidence is incomplete.

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.

3 disqualifying conditions named by the report's claim policy.Show matched requests

Context

Tracking companies the privacy policy does not appear to name

PubMatic, Taboola and Index Exchange, plus 6 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.

Policy at https://*.usatoday.com/privacy; 0 checkable statements matched; 1 of 10 observed tracking companies named in the policy. Policy mentions of Magnite, Amazon Ads and Equativ are unknown because the historical alias matcher was incomplete.

Look closer

Show catalog-matched requests

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

PubMatic, Google and Taboola, plus 19 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 advertising / supply-side platform, advertising and analytics / tag management. This scan could not identify 136 of the 173 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.

At least 928 retained cross-site requests across at least 173 retained third-party hosts.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.

At least 66 retained requests to these platforms.Show catalog-matched requests

Context

Google Analytics present; a remarketing sync cannot be told from this report

Google Analytics was observed, with requests to DoubleClick hosts whose names this report generalizes. The remarketing sync host is one such name, so the sync cannot be told apart from them.

This report neither shows nor rules out the sync. Details

The sync goes to stats.g.doubleclick.net, and a published report writes that name the same way as DoubleClick's ad-serving hosts.

Google Analytics host observed; DoubleClick hosts recorded under generalized names.Show catalog-matched requests

Review-worthy

Third-party cookies were present

The retained cookie snapshot holds 288 third-party cookies. That snapshot is incomplete, so the visit's count can differ.

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.

310 cookies total in this report's incomplete snapshot.

Look closer

See other visits' cookie counts

Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.

Context

Incomplete evidence: No fingerprint-like API calls observed in retained evidence before collection stopped

The retained evidence holds no calls to the instrumented high-entropy browser APIs.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

This is an observation layer, not proof that fingerprinting is impossible.

Retained incomplete evidence includes 0 API event records; no exact API-family total is available.

Domain evidence

175 recorded domains

These are retained domain rows, not a complete inventory.

The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 12.7 sCatalog matchRoleResource types
www.usatoday.com71No catalog matchfirst-partydocument, image, script, other, fetch
*.pubmatic.com69PubMatic: advertising / supply-side platformserviceimage, xhr, script, document
*.taboola.com41Taboola: advertising / recommendationsservicescript, fetch, ping, document, image, other
*.*.doubleclick.net33Google: advertisingservicescript, document, fetch, other, image
*.rubiconproject.com33Magnite: advertising / supply-side platformservicedocument, script, image, xhr, fetch
*.yellowblue.io27No catalog matchthird-partydocument, image
*.seedtag.com26No catalog matchthird-partydocument, fetch, image
*.amazon-adsystem.com25Amazon Ads: advertisingservicexhr, document, image
*.openx.net25OpenX: advertising / exchangeserviceimage, document, fetch
*.casalemedia.com25Index Exchange: advertising / exchangeservicedocument, image
*.lijit.com23Sovrn: advertising / publisher monetizationservicedocument, image
*.googlesyndication.com20Google: advertisingservicefetch, script, image
*.minutemedia-prebid.com20No catalog matchthird-partydocument, image
*.bidswitch.net17No catalog matchthird-partyimage, document
pixel.rubiconproject.com15Magnite: advertising / supply-side platformserviceimage
*.3lift.com14TripleLift: advertising / supply-side platformserviceimage, document
*.adsrvr.org13The Trade Desk: advertising / demand-side platformservicefetch, image
*.analytics.yahoo.com13No catalog matchthird-partyscript, document, xhr, image
*.criteo.com11Criteo: advertisingservicefetch, script, image, document
*.smartadserver.com10Equativ: advertising / supply-side platformserviceimage, document, script
static.polarcdn.com10No catalog matchthird-partyscript, other, image
*.*.opera.com10No catalog matchthird-partyimage, document
*.adsafeprotected.com10No catalog matchthird-partyscript, image
*.sitescout.com9No catalog matchthird-partyimage, document
*.*.bidr.io9No catalog matchthird-partyimage, document
*.undertone.com9No catalog matchthird-partyimage, document
*.openwebmp.com9No catalog matchthird-partydocument, image
*.outbrain.com8Outbrain: advertising / recommendationsserviceimage, document
*.dotomi.com8No catalog matchthird-partyimage, document
*.*.sonobi.com8No catalog matchthird-partyimage, document

+145 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.

Report ID
20260928-4212ecc80b5c9feb0d13786ad2fa14f3
Site
www.usatoday.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the visit hit the scanner's request-recording cap, so its counts are truncated; the synthetic form-input probe stopped one or more navigations started while it ran, so the request evidence is incomplete; the scanner's own network guard refused one or more requests, which were never sent and have no row, so the request evidence is incomplete; the in-page fingerprint observer could not read every frame, so the fingerprinting evidence is incomplete; the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.

Variant visit

Started
Run quality
cut short: the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
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 .