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.
wikipedia.org's completed measurements recorded no listed activity, but the privacy-policy check did not apply to this page.
Where this page's requests went
Both visits. One mark is one request row in the retained log.
GPC off
wikipedia.org itself6 requestsrequests that stayed on the site
000000
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name0 requestsno other cross-site host on record
GPC on
wikipedia.org itself6 requestsrequests that stayed on the site
000000
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name0 requestsno other cross-site host on record
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
The request log recorded no cross-site hosts or catalogued tracking-related services, the cookie snapshot recorded no third-party cookie records and the fingerprint observer recorded no instrumented API events. The privacy-policy check did not apply to this page, so whatever that check looks for is unproven here rather than shown to be absent. 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 automated visit did not observe known third-party services, third-party cookies, or instrumented fingerprint-like calls.
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.
6 requests observed in one controlled visit.
What was checked
Page
https://www.wikipedia.org/
When
Aug 14, 2026, 7:09 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.
Not flagged
No requests matched Brave Shields filter lists
No requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser.
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 0 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.
Not flagged
No known services matched
This scan did not match any third-party domains to the service catalog or another identity source.
This does not prove the site contacts no third-party service; it means this visit matched no domain to one.Details
The automated visit did not observe third-party cookies.
This does not prove the site never uses cookies; it means this visit did not observe third-party cookies.
5 cookies total in this report.No third-party cookies observed.
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.
Scan report ready for wikipedia.org: 6 recorded request rows.
Comparison Report
wikipedia.org
Recorded final addresshttps://www.wikipedia.org/
ShareDownloads the GPC off 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.
GPC Comparison
GPC off and GPC on: two visits, no comparable metric delta
GPC off: started Aug 14, 2026, 7:09 PM UTC · 4,399msGPC on: started Aug 14, 2026, 7:09 PM UTC · 4,323msRan first: GPC off
No metric deltas are comparable across these two visits, so none are shown.
Request, cookie, and storage deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
Catalog-matched request and entity deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
Other detector and causal-path deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching. The privacy-policy detector's status differed between the two visits, so their numbers measure different things.
The Shields-number delta (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
Fingerprinting deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
Ad-pixel deltas (each visit's own evidence still renders below): The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.
Measurement limits
3 conditions affect how this evidence reads
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.
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.
How to use this report
Read the findings and measurement limits first, then inspect the evidence for each recorded visit. Comparisons include both visits, even where a difference cannot be interpreted.
Keep this PDF with its evidence package: the source JSON, correction context, export receipt and SHA256SUMS. The package preserves source bytes and the correction context at export time. Hashes check file consistency; they do not establish independent measurement accuracy or a signed attestation.
Request counts are retained request rows whose start fell in each phase. A phase with no retained rows does not prove that no traffic occurred; some phase traffic can be intentionally excluded from the public request log.
Each recorded phase of the visit, with its span from run start and what it observed.
Phase
Span from run start
Recorded requests
Third-party
Catalog-matched requests
Cookie records
Storage records
Initial page loadP0 · passive-load
0 to 945 ms (945 ms)
5
0
0
5 present
3 present
Active input probeP1 · active-probe
945 to 4,285 ms (3,340 ms)
1
0
0
0 retained
0 retained
Cookie & storage snapshot ledger
8 change records
Changes are inferred from privacy-filtered snapshots at phase boundaries, not instrumented browser write events. Cookie values are never recorded; storage values are omitted and only byte counts remain.
P0 · Initial page loadPresent at first snapshot
Cookie 1 · name hidden for privacyFirst-party cookie · persistent
P0 · Initial page loadPresent at first snapshot
Cookie 2 · name hidden for privacyFirst-party cookie · session
P0 · Initial page loadPresent at first snapshot
Cookie 3 · name hidden for privacyFirst-party cookie · persistent
P0 · Initial page loadPresent at first snapshot
Cookie 4 · name hidden for privacyFirst-party cookie · persistent
P0 · Initial page loadPresent at first snapshot
Cookie 5 · name hidden for privacyFirst-party cookie · persistent
P0 · Initial page loadPresent at first snapshot
Storage key 1 · name hidden for privacylocalStorage · observed size 13 bytes
P0 · Initial page loadPresent at first snapshot
Storage key 2 · name hidden for privacylocalStorage · observed size 8 bytes
P0 · Initial page loadPresent at first snapshot
Storage key 3 · name hidden for privacylocalStorage · observed size 16 bytes
8 change records hide unreviewed names or keys because they can contain identifiers.
Domain evidence
2 recorded domains
Every domain this visit recorded, with its role, request count and catalog match.
Domain
Role
Requests
Catalog match
Resource types
www.wikipedia.org
first-party
5
No catalog match
document, image, script
en.wikipedia.org
first-party
1
No catalog match
script
Request log
6 recorded requests
In hosts and URLs, * and … mark details hidden for privacy.
Request references name this visit's retained JSON rows in order (B = baseline, V = variant, S = single). R0001 is the first request row.
Every request row this visit retained, with its time, status, resource type, domain and recorded provenance.
Ref
Time
Phase
Status
Type
Domain
Provenance
URL
B:R0001
68ms
P0
200
document
www.wikipedia.org
Not attributed
https://www.wikipedia.org/
B:R0002
214ms
P0
200
image
www.wikipedia.org
initiated by www.wikipedia.org
https://www.wikipedia.org/…
B:R0003
215ms
P0
200
script
www.wikipedia.org
initiated by www.wikipedia.org
https://www.wikipedia.org/…
B:R0004
216ms
P0
200
script
www.wikipedia.org
initiated by www.wikipedia.org
https://www.wikipedia.org/…
B:R0005
340ms
P0
200
image
www.wikipedia.org
initiated by www.wikipedia.org
https://www.wikipedia.org/…
B:R0006
1,160ms
P1
200
script
en.wikipedia.org
initiated by www.wikipedia.org
https://en.wikipedia.org/…
Request attribution map
Which actor each third-party request is attributed to, from the initiator the browser reported. Attribution, not causation: an initiator may itself have been told what to fetch, a script that wraps fetch or XHR is credited with the requests it relays, and a script can choose the name it is credited under. Requests made by dedicated workers are not observed. Asterisks mark subdomain labels hidden for privacy.
Attributed requests
0
Not attributable
0
Third-party requests
0
No third-party requests were recorded, so attribution coverage is not applicable.
No retained third-party request has one recorded actor to draw. This is not evidence that no actor was involved: the visit may have reported no actor or several actors for the same request.
Methodology
Schema
v2 schema (r2)
Run quality
complete; recorded by the scanner
Scanner
playwright-chromium
Playwright
1.62.1
Browser
151.0.7922.34
Timezone
UTC
Headless
yes
Viewport
1440×980
GPC
configured off · readback verified
Egress
this scanner instance
Catalog
Hand-curated service catalog hand-curated-2026.08 146 entries
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.
GPC on: evidence
2026-08-14T19:09:12.978Z · complete; recorded by the scanner
Retained observations from this visit. Missing measurements do not establish absence of activity.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.
Requests60 third-party
Matched Shields lists0verified over 4 requests the engine evaluated
Third-party domains00 distinct catalogued service entities
Request counts are retained request rows whose start fell in each phase. A phase with no retained rows does not prove that no traffic occurred; some phase traffic can be intentionally excluded from the public request log.
Each recorded phase of the visit, with its span from run start and what it observed.
Phase
Span from run start
Recorded requests
Third-party
Catalog-matched requests
Cookie records
Storage records
Initial page loadP0 · passive-load
1 to 922 ms (921 ms)
5
0
0
5 present
3 present
Active input probeP1 · active-probe
922 to 4,225 ms (3,303 ms)
1
0
0
0 retained
0 retained
Cookie & storage snapshot ledger
8 change records
Changes are inferred from privacy-filtered snapshots at phase boundaries, not instrumented browser write events. Cookie values are never recorded; storage values are omitted and only byte counts remain.
P0 · Initial page loadPresent at first snapshot
Cookie 1 · name hidden for privacyFirst-party cookie · persistent
P0 · Initial page loadPresent at first snapshot
Cookie 2 · name hidden for privacyFirst-party cookie · session
P0 · Initial page loadPresent at first snapshot
Cookie 3 · name hidden for privacyFirst-party cookie · persistent
P0 · Initial page loadPresent at first snapshot
Cookie 4 · name hidden for privacyFirst-party cookie · persistent
P0 · Initial page loadPresent at first snapshot
Cookie 5 · name hidden for privacyFirst-party cookie · persistent
P0 · Initial page loadPresent at first snapshot
Storage key 1 · name hidden for privacylocalStorage · observed size 13 bytes
P0 · Initial page loadPresent at first snapshot
Storage key 2 · name hidden for privacylocalStorage · observed size 8 bytes
P0 · Initial page loadPresent at first snapshot
Storage key 3 · name hidden for privacylocalStorage · observed size 16 bytes
8 change records hide unreviewed names or keys because they can contain identifiers.
Domain evidence
2 recorded domains
Every domain this visit recorded, with its role, request count and catalog match.
Domain
Role
Requests
Catalog match
Resource types
www.wikipedia.org
first-party
5
No catalog match
document, image, script
en.wikipedia.org
first-party
1
No catalog match
script
Request log
6 recorded requests
In hosts and URLs, * and … mark details hidden for privacy.
Request references name this visit's retained JSON rows in order (B = baseline, V = variant, S = single). R0001 is the first request row.
Every request row this visit retained, with its time, status, resource type, domain and recorded provenance.
Ref
Time
Phase
Status
Type
Domain
Provenance
URL
V:R0001
87ms
P0
200
document
www.wikipedia.org
Not attributed
https://www.wikipedia.org/
V:R0002
230ms
P0
200
image
www.wikipedia.org
initiated by www.wikipedia.org
https://www.wikipedia.org/…
V:R0003
231ms
P0
200
script
www.wikipedia.org
initiated by www.wikipedia.org
https://www.wikipedia.org/…
V:R0004
231ms
P0
200
script
www.wikipedia.org
initiated by www.wikipedia.org
https://www.wikipedia.org/…
V:R0005
322ms
P0
200
image
www.wikipedia.org
initiated by www.wikipedia.org
https://www.wikipedia.org/…
V:R0006
1,113ms
P1
200
script
en.wikipedia.org
initiated by www.wikipedia.org
https://en.wikipedia.org/…
Request attribution map
Which actor each third-party request is attributed to, from the initiator the browser reported. Attribution, not causation: an initiator may itself have been told what to fetch, a script that wraps fetch or XHR is credited with the requests it relays, and a script can choose the name it is credited under. Requests made by dedicated workers are not observed. Asterisks mark subdomain labels hidden for privacy.
Attributed requests
0
Not attributable
0
Third-party requests
0
No third-party requests were recorded, so attribution coverage is not applicable.
No retained third-party request has one recorded actor to draw. This is not evidence that no actor was involved: the visit may have reported no actor or several actors for the same request.
Methodology
Schema
v2 schema (r2)
Run quality
complete; recorded by the scanner
Scanner
playwright-chromium
Playwright
1.62.1
Browser
151.0.7922.34
Timezone
UTC
Headless
yes
Viewport
1440×980
GPC
configured on · readback verified
Egress
this scanner instance
Catalog
Hand-curated service catalog hand-curated-2026.08 146 entries
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.
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.
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 .
Reports record one automated visit per condition; visits may be incomplete. On restart-safe deployments, an interrupted visit may be retried; attempts are never merged. Results describe these visits, not everything a site can do.