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.
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 20 distinct catalogued tracking-service entities; 20 of the retained service matches recorded responses across at least 142 retained cross-site domains. 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.
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 10, 2026, 7:00 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 605 retained requests matched Brave Shields filter lists
At least 605 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.
Catalogued service domains recorded responses during this visit
Magnite, Google and Taboola, plus 17 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 106 of the 142 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 964 retained cross-site requests across at least 142 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.
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.
The retained cookie snapshot holds 277 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.
300 cookies total in this report's incomplete snapshot.
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
144 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.
Domain
Requests
When, 0 to 13 s
Catalog match
Role
Resource types
*.yellowblue.io
63
No catalog match
third-party
document, image
*.rubiconproject.com
60
Magnite: advertising / supply-side platform
service
document, script, xhr, image
*.taboola.com
35
Taboola: advertising / recommendations
service
script, fetch, ping, image, document
www.usatoday.com
35
No catalog match
first-party
document, image, script, fetch, other
*.*.doubleclick.net
30
Google: advertising
service
script, document, fetch, other, image
*.seedtag.com
30
No catalog match
third-party
document, fetch, image
*.openx.net
27
OpenX: advertising / exchange
service
document, image
*.pubmatic.com
27
PubMatic: advertising / supply-side platform
service
xhr, image, script
*.googlesyndication.com
24
Google: advertising
service
script, image, fetch
*.amazon-adsystem.com
23
Amazon Ads: advertising
service
xhr, document, image
*.smartadserver.com
21
Equativ: advertising / supply-side platform
service
document, image, script
*.lijit.com
20
Sovrn: advertising / publisher monetization
service
image, document
*.omnitagjs.com
17
No catalog match
third-party
document, image
*.bidswitch.net
16
No catalog match
third-party
image
*.openwebmp.com
16
No catalog match
third-party
document, image
*.sharethrough.com
15
No catalog match
third-party
document, image
*.inmobi.com
15
No catalog match
third-party
image
*.adsafeprotected.com
15
No catalog match
third-party
script, image
ads.servenobid.com
15
No catalog match
third-party
image
*.minutemedia-prebid.com
14
No catalog match
third-party
document, image
measureadv.com
14
No catalog match
third-party
document, image
*.*.*.omnitagjs.com
14
No catalog match
third-party
image
*.criteo.com
13
Criteo: advertising
service
fetch, script, document, image
*.analytics.yahoo.com
13
No catalog match
third-party
script, xhr, document, image
pixel.rubiconproject.com
12
Magnite: advertising / supply-side platform
service
image
*.casalemedia.com
12
Index Exchange: advertising / exchange
service
document, image
secure.adnxs.com
12
No catalog match
third-party
image, document
*.3lift.com
11
TripleLift: advertising / supply-side platform
service
document, image
*.1rx.io
11
No catalog match
third-party
document, image
*.a-mo.net
11
No catalog match
third-party
image, document
+114 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: 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. 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 .