Site

www.usatoday.com

Baseline visit
Requested address
https://www.usatoday.com/
Report ID
20260817-ceb730488a47429068699acf72cdd364
Evidence SHA-256
1ea4d5c30d0ef1745bd925fc42d70bccc5469c00c2849a762b5d44013b80f47b
Scanner
playwright-chromium

Public corrections ledger · SBL-CORR-2026-001

This report has a reviewed clarification

SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.

Read the public review record

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 42 retained requestsrequests that stayed on the site
Catalogued servicesat least 388 retained requests21 names: Google 60, Taboola 56, PubMatic 55, Magnite 48, Amazon Ads 23, and 16 more
Hosts the catalog does not nameat least 570 retained requests117 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 21 distinct catalogued tracking-service entities; 21 of the retained service matches recorded responses across at least 151 retained cross-site domains. This report does not record which requests came during the typing test. A catalog match identifies the service domain, not why the request occurred or what it carried. SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.

≥21tracking-service entities retained
≥958cross-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
Aug 17, 2026, 6:08 AM 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 2 form fields in the No blocking visit and 1 form field in the Brave-list blocking visit, never submitting the form. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence in the No blocking 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 No blocking visit: every check. Every card below states only what was retained.

Worth checking

At least 597 retained requests matched Brave Shields filter lists

At least 597 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 388 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 exhausted its proxy connection and target safety budget, 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

Review-worthy

Catalogued service domains recorded responses during this visit

Google, Taboola and PubMatic, plus 18 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, analytics / tag management and advertising / recommendations. This scan could not identify 113 of the 151 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 958 retained cross-site requests across at least 151 retained third-party hosts. This report does not record which requests came during the typing test.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 61 retained requests to these platforms. This report does not record which requests came during the typing test.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 284 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.

305 cookies total in this report's incomplete snapshot.

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.

Scan report ready for www.usatoday.com: 1,000 recorded request rows.

Comparison ReportOlder format: some facts reconstructed, descriptive onlyrecording capped

Brave-list blocking off/on comparison

Recorded final address https://www.usatoday.com/ (opens in a new tab)

The selected visit hit the request-recording cap. Request and domain counts are lower bounds; cookie and storage availability is reported separately.

ShareDownloads the No blocking visit's request CSV, source report and correction context in a ZIP. Follows the evidence switcher below.PDF + evidence (opens in a new tab)Downloads a ZIP containing the PDF for every recorded visit, exact source JSON, correction context and file hashes. The scanner renders it on request.

Brave Shields Comparison

No blocking and Brave-list blocking: two visits, no comparable metric delta

No blocking: started Aug 17, 2026, 6:08 AM UTC · 15,103msBrave-list blocking: started Aug 17, 2026, 6:08 AM UTC · 5,655msRan first: No blocking
These two visits do not support a side-by-side comparison, so no deltas are shown.
  • The "No blocking" visit hit the 1,000-request recording cap, so its counts are truncated.
  • The "No blocking" visit exhausted its proxy connection and target safety budget, 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.

Each visit's own evidence still stands: use the “Evidence shown” switcher below to inspect either visit's tables, and both visits are in the downloaded JSON.

Measurement limits

15 conditions affect how this evidence reads

This report

  • Brave-list blocking comparison runs should be collected under matched crawl conditions, and the blocking run is a simulation with Brave's engine and default lists in this scanner's browser, not a live Brave visit. Differences can still reflect timing, experiments, cache state, consent state, or bot detection.
  • The two visits ran in randomized order; the "No blocking" visit ran first.

Both visits

  • Each visit in this report is one automated, headless Chromium visit from a fixed en-US / UTC profile, with no scrolling, clicking, or consent interaction. Sites can behave differently for real users, browsers, regions, accounts, or network locations.
  • Counts are a lower bound: trackers that load only after interaction or consent are not observed; Service Workers are blocked, and Web Worker or WebSocket traffic may be incomplete. Service labels use a US-biased hand-curated catalog, so regional services may be under-labeled. Cookie and storage figures are an end-of-visit snapshot, with storage keys read from the top frame only.

No blocking visit only

  • Blocked a request that could not be verified as public: https://{label}.iqzone.com/{seg}
  • The page did not reach network idle before the scan window ended.
  • Blocked a request that could not be verified as public: https://{label}.{label}.adtarget.com.tr/{seg}
  • Blocked a request that could not be verified as public: https://{label}.omnitagjs.com/{seg}/{seg}
  • The in-page fingerprint observer could not read one or more frames, so fingerprint-like API calls and heuristics for this visit are incomplete.
  • This scan typed a synthetic test value into 2 form fields (never submitting the form) to test whether typed input is captured and sent to third parties. The value is synthetic and is not stored. Requests the page sent during and after this typing, including any unload beacons, are part of the recorded request log and counts.
  • The scan stopped opening additional proxy requests after reaching its connection and target safety budget.
  • The scan stopped recording or loading additional requests after 1000 requests.

Brave-list blocking visit only

  • Brave Shields block simulation was enabled; matching requests were aborted before loading and are not included in request totals.
  • This scan typed a synthetic test value into 1 form field (never submitting the form) to test whether typed input is captured and sent to third parties. The value is synthetic and is not stored. Requests the page sent during and after this typing, including any unload beacons, are part of the recorded request log and counts.
  • Read the site's privacy policy (https://{label}.usatoday.com/privacy) and compared its text against this visit's observed behavior. Policy checks are an automated text match with the matched sentences quoted, not a legal reading.

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
20260817-ceb730488a47429068699acf72cdd364
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 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 visit hit the scan proxy's traffic budget, so it stopped forwarding further traffic; the in-page fingerprint observer could not read every frame, so the fingerprinting evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
not recorded by this schema
Provenance
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
151.0.7922.34
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. 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 .