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.
Catalogued servicesat least 14 retained requests6 names: Adobe 7, Google 2, Lotame 2, LiveRamp 1, Magnite 1, and 1 more
00000000000000
Hosts the catalog does not nameat least 39 retained requests11 hosts; the catalog cannot say who operates them
000000000000000000000000000000000000000
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 9 distinct catalogued tracking-service entities; 9 of the retained service matches recorded responses across at least 38 retained 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 and 3 browser-fingerprinting heuristics matched. 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.
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 464 retained requests observed in one controlled visit.
What was checked
Page
https://www.bestbuy.com/
When
Aug 14, 2026, 7:14 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
Typed a made-up test value into 2 form fields in each visit, never submitting the form. 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.
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.
At least 118 retained requests out of 273 requests the engine evaluated matched Brave Shields filter lists
At least 118 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 118 retained 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 scanner's own network guard refused one or more requests in both visits. They were not sent and are not in the request log, so request counts there are floors, not 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.
3 disqualifying conditions named by the report's claim policy.
Review-worthy
Catalogued service domains recorded responses during this visit
Google, Adobe and OpenX, 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.Details
Functional catalog labels include advertising, analytics / tag management and analytics / advertising. This scan could not identify 19 of the 38 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 230 retained cross-site requests across at least 38 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 Microsoft.
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
18 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.
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.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: 8 interaction-listener registrations with https://*.*.doubleclick.net/, https://www.googletagmanager.com/ and https://www.gstatic.com/ in the registration call chain. Input-monitoring listener coverage: 4 input-listener registrations with https://www.googletagmanager.com/ and https://www.gstatic.com/ in the registration call chain.
Opens this report's request log filtered to *.*.doubleclick.net, a script origin recorded in the listener's call chain.
Worth checking
Behavioral fingerprinting heuristics matched
3 behavioral heuristics matched: Offline audio rendering heuristic, Canvas fingerprinting heuristic and Canvas font probing heuristic.
They are review prompts for this visit, not proof of cross-site identity tracking.Details
These heuristics look for behavior patterns such as canvas readback after drawing, repeated canvas font measurement, WebGL entropy reads, offline audio rendering, or WebRTC peer-connection setup.
Offline audio rendering heuristic: 2 offline renders with audio.OfflineAudioContext.createAnalyser, audio.OfflineAudioContext.createDynamicsCompressor and audio.OfflineAudioContext.createOscillator, plus 2 others. Canvas fingerprinting heuristic: 1 canvas matched; reads: canvas.toDataURL. Canvas font probing heuristic: 9 measureText calls across up to 9 fonts; measured text contents are not stored.
Domain evidence
41 recorded domains
These are retained domain rows, not a complete inventory.
The busiest recorded domains of the GPC off visit, with role, request count, request start times and catalog match.
Domain
Requests
When, 0 to 29.8 s
Catalog match
Role
Resource types
www.bestbuy.com
227
No catalog match
first-party
document, stylesheet, font, script, fetch, xhr
*.*.doubleclick.net
44
Google: advertising
service
script, other, document, fetch, image
www.google.com
41
No catalog match
third-party
script, document, xhr, fetch, image
www.googleadservices.com
32
Google: advertising
service
fetch, image, script
*.bbystatic.com
22
No catalog match
third-party
image
*.googlesyndication.com
10
Google: advertising
service
script, image, fetch
*.adsafeprotected.com
9
No catalog match
third-party
script, image
*.demdex.net
8
Adobe: analytics / advertising
service
xhr, document, image
*.openx.net
6
OpenX: advertising / exchange
service
fetch, document, image
www.gstatic.com
5
No catalog match
third-party
script, stylesheet, image, other
*.speedcurve.com
5
No catalog match
third-party
image
*.*.dynatrace.com
5
No catalog match
third-party
fetch
*.adtrafficquality.google
5
No catalog match
third-party
xhr, script, document, image
*.bestbuy.com
5
No catalog match
first-party
fetch
ad.doubleclick.net
3
Google: advertising
service
fetch
*.analytics.yahoo.com
3
No catalog match
third-party
script, xhr, image
www.googletagmanager.com
2
Google: analytics / tag management
service
script
*.google.com
2
Google: advertising
service
image
*.rlcdn.com
2
LiveRamp: identity / advertising
service
image
*.crwdcntrl.net
2
Lotame: advertising / data management
service
image
*.adsrvr.org
2
The Trade Desk: advertising / demand-side platform
service
image
*.ensighten.com
2
No catalog match
third-party
script
*.*.ensighten.com
2
No catalog match
third-party
image
pixel.adsafeprotected.com
2
No catalog match
third-party
xhr, script
*.*.*.bestbuy.com
2
No catalog match
first-party
fetch, xhr
*.rubiconproject.com
1
Magnite: advertising / supply-side platform
service
image
*.bing.com
1
Microsoft: advertising / analytics
service
image
static.criteo.net
1
Criteo: advertising
service
script
*.*.googlesyndication.com
1
Google: advertising
service
document
*.criteo.com
1
Criteo: advertising
service
document
+11 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 scanner's own network guard refused one or more requests, which were never sent and have no row, so the request evidence is incomplete; detector output evidence was censored before completion: 1 privacy-policy visit did not produce usable evidence; recorded by the scanner
cut short: 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; request evidence was censored before completion: the producer recorded an additional collection loss (recorded loss count: 2); detector output evidence was censored before completion: 1 privacy-policy visit did not produce usable evidence; 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. 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 .