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
not measured
2 distinct catalogued tracking-service entities recorded responses across 12 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-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.
Bottom line: this visit has signals worth checking
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.
384 requests observed in one controlled visit.
What was checked
Page
https://www.bing.com/
When
Aug 14, 2026, 7:17 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 1 form field in each visit, never submitting the form. No scrolling, clicking or consent interaction.
Outcome
Both visits completed.
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.
Checks with incomplete evidence. In both visits: the privacy policy check.
Worth checking
22 of 368 requests the engine evaluated matched Brave Shields filter lists
22 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 2 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 raw request logs of both visits remain below for transparency, but the diff between them supports no claim about what the compared condition changed.
1 disqualifying condition named by the report's claim policy.
Context
Catalogued service domains recorded responses during this visit
LinkedIn and Taboola 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 social / advertising pixel and advertising / recommendations. This scan could not identify 10 of the 12 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.
125 cross-site requests across 12 third-party hosts.Below the median for third-party domains across the 51 sites measured for this metric. Modest distinct tracking-service entities count.Show third-party requests
Context
Requests were dispatched to catalogued major-platform domains
This visit dispatched requests to catalogued domains for LinkedIn.
The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.
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.
39 cookies total in this report.At or above the 75th-percentile mark for third-party cookies across the 51 sites measured for this metric.
Context
Input-monitoring signal involving a script from another domain
Listener coverage that could observe typing-related input events was registered through call chains that included a script served from another registrable domain. This scan did not establish the operator of that 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: 519 interaction-listener registrations with https://assets.msn.com/ in the registration call chain. Input-monitoring listener coverage: 370 input-listener registrations with https://assets.msn.com/ in the registration call chain.
Opens this report's request log filtered to assets.msn.com, a script origin recorded in the listener's call chain.
Not flagged
No fingerprint-like API calls observed
The scan did not observe the instrumented high-entropy browser APIs.
This is an observation layer, not proof that fingerprinting is impossible.
0 API families recorded.
Domain evidence
15 recorded domains
The busiest recorded domains of the GPC off visit, with role, request count, request start times and catalog match.
Domain
Requests
When, 0 to 8.5 s
Catalog match
Role
Resource types
*.bing.com
176
No catalog match
first-party
stylesheet, script, other, xhr, image
www.bing.com
82
No catalog match
first-party
document, script, image, fetch, xhr
assets.msn.com
69
No catalog match
third-party
script, fetch, image
img-s-msn-com.akamaized.net
31
No catalog match
third-party
image
*.msn.com
9
No catalog match
third-party
image, xhr
*.events.*.msn.com
7
No catalog match
third-party
ping
m.adnxs.com
2
No catalog match
third-party
image
*.ads.linkedin.com
1
LinkedIn: social / advertising pixel
service
image
*.taboola.com
1
Taboola: advertising / recommendations
service
image
www.msn.com
1
No catalog match
third-party
fetch
*.*.virtualearth.net
1
No catalog match
third-party
image
*.adnxs.com
1
No catalog match
third-party
image
login.microsoftonline.com
1
No catalog match
third-party
document
login.live.com
1
No catalog match
third-party
document
www2.bing.com
1
No catalog match
first-party
script
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.
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 .