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.
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.
What this actually means
rfc-editor.org recorded 4 fewer third-party requests in the visit configured for Brave-list blocking.
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.
The cards below translate the evidence into plain language; severity reflects fixed reference thresholds, not measured population percentiles. The request log, domain table, and methodology remain below for verification.
31 requests observed in one controlled visit.
Context
4 requests matched Brave Shields filter lists
4 requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.
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. Matching shows what Shields would target on this visit's traffic; an actual Shields visit blocks these and also prevents their follow-on requests, so this number is neither a measured block count nor the total effect.
The hand-curated service catalog separately matched 0 request rows in this visit.Show matched requests
Nothing observed
Lower values observed across comparable metrics in the Brave-list blocking attempt
With the scanner configured to apply Brave's ad-block engine and default Shields filter lists (a simulation in this scanner's browser, not a live Brave-browser visit; application was not verified), this paired visit showed 4 fewer third-party requests.
The blocking visit's engine directly blocked 1 request; the remaining difference may include follow-on requests that never started once their sources were blocked. A single paired comparison can also reflect run-to-run variance (ad rotation, caching, experiments), so treat this as an observed difference, not a measured blocking rate.
Signed per-metric differences between the two visits; nothing is summed across metrics.Show matched requests
Context
No known services matched
This scan did not match any third-party domains to the service catalog or another identity source.
No known operator or catalog entity was matched. This scan could not identify 2 of the 2 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.
The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary. 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.
4 cookies total in this report.Modest third-party cookies count.
Nothing observed
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.
Brave Shields Comparison
No blocking → Brave-list blocking delta
No blocking: 6,148msBrave-list blocking: 5,144ms
Some deltas are not comparable across these two visits and are not shown.
Other detector and causal-path deltas (each visit's own evidence still renders below): v1 never recorded detector versions, so fingerprinting and pixel deltas cannot be proven to come from matching instrumentation.
The Shields-number delta (each visit's own evidence still renders below): The two visits measured different Shields quantities (filter-list matches vs engine-blocked requests), which must never share a delta.
Fingerprinting deltas (each visit's own evidence still renders below): At least one visit did not complete the fingerprint measurement, so no exact cross-visit delta is shown.
Ad-pixel deltas (each visit's own evidence still renders below): At least one visit did not complete the pixel measurement, so no exact cross-visit delta is shown.
Every signed change is Brave-list blocking minus No blocking. A positive or negative direction is descriptive, not a judgment that the result is better or worse.
Cookie and storage count deltas include every observation. Name-level lists show only reviewed names; unreviewed names are not itemized because they can contain identifiers.
Visible cookie names only with Brave-list blocking
No visible cookie-name changes to show; privacy-filtered names are not itemized.
Visible cookie names only with No blocking
No visible cookie-name changes to show; privacy-filtered names are not itemized.
Visible storage keys only with Brave-list blocking
No visible storage-key changes to show; privacy-filtered keys are not itemized.
Visible storage keys only with No blocking
No visible storage-key changes to show; privacy-filtered keys are not itemized.
Entities only with Brave-list blocking
No entity changes observed.
Entities only with No blocking
No entity changes observed.
Measurement limits
6 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.
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.
Brave-list blocking visit only
Brave Shields block simulation was enabled; matching requests were aborted before loading and are not included in request totals.
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.
2026-08-03T11:00:01.790Z · complete; derived from status and warnings
Retained observations from this visit. Missing measurements do not establish absence of activity.
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, and requests with no reported initiator are not distinguished from ones fetched from several. Asterisks mark subdomain labels hidden for privacy.
Attributed requests
0
Not attributable
6
Third-party requests
6
No unique actor could be assigned to 6 of these requests. That includes requests for which the browser reported no usable initiator, and repeated URLs seen with conflicting initiators. This report does not distinguish those causes, so they are counted together rather than drawn.
6 third-party requests: 0 attributed to a single recorded actor, 6 not attributable.
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.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.
Requests316 third-party
Matched Shields lists4classification reported by this visit; no engine readback recorded
Third-party domains20 distinct catalogued service entities
Every domain this visit recorded, with its role, request count and catalog match.
Domain
Role
Requests
Catalog match
Resource types
analytics.ietf.org
third-party
4
No catalog match
script, ping
static.ietf.org
third-party
2
No catalog match
stylesheet, font
www.rfc-editor.org
first-party
25
No catalog match
document, stylesheet, script, image, fetch
Request log
31 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
Status
Type
Domain
Provenance
URL
B:R0001
39ms
200
document
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/
B:R0002
389ms
200
stylesheet
static.ietf.org
Not attributed
https://static.ietf.org/…
B:R0003
390ms
200
stylesheet
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0004
390ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0005
507ms
200
image
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0006
508ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0007
508ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0008
508ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0009
509ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0010
509ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0011
509ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0012
509ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0013
550ms
200
image
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0014
574ms
200
font
static.ietf.org
Not attributed
https://static.ietf.org/…
B:R0015
757ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0016
888ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0017
888ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0018
1,116ms
200
script
analytics.ietf.org
Not attributed
https://analytics.ietf.org/…
B:R0019
1,149ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0020
1,150ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0021
1,150ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0022
1,150ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0023
1,150ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0024
1,150ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0025
1,150ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0026
1,219ms
204
ping
analytics.ietf.org
Not attributed
https://analytics.ietf.org/…?…
B:R0027
1,373ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0028
1,374ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
B:R0029
2,020ms
204
ping
analytics.ietf.org
Not attributed
https://analytics.ietf.org/…?…
B:R0030
2,070ms
204
ping
analytics.ietf.org
Not attributed
https://analytics.ietf.org/…?…
B:R0031
2,123ms
200
fetch
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
Brave-list blocking — evidence
2026-08-03T11:00:07.942Z · complete; derived from status and warnings
Retained observations from this visit. Missing measurements do not establish absence of activity.
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, and requests with no reported initiator are not distinguished from ones fetched from several. Asterisks mark subdomain labels hidden for privacy.
Attributed requests
0
Not attributable
2
Third-party requests
2
No unique actor could be assigned to 2 of these requests. That includes requests for which the browser reported no usable initiator, and repeated URLs seen with conflicting initiators. This report does not distinguish those causes, so they are counted together rather than drawn.
2 third-party requests: 0 attributed to a single recorded actor, 2 not attributable.
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.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.
Requests272 third-party
Blocked by Brave lists1engine blocks reported by this visit; no engine readback recorded
Third-party domains10 distinct catalogued service entities
Every domain this visit recorded, with its role, request count and catalog match.
Domain
Role
Requests
Catalog match
Resource types
static.ietf.org
third-party
2
No catalog match
stylesheet, font
www.rfc-editor.org
first-party
25
No catalog match
document, stylesheet, script, image, fetch
Request log
27 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
Status
Type
Domain
Provenance
URL
V:R0001
39ms
200
document
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/
V:R0002
124ms
200
stylesheet
static.ietf.org
Not attributed
https://static.ietf.org/…
V:R0003
124ms
200
stylesheet
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0004
125ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0005
242ms
200
image
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0006
245ms
200
image
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0007
267ms
200
font
static.ietf.org
Not attributed
https://static.ietf.org/…
V:R0008
271ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0009
271ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0010
271ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0011
272ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0012
272ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0013
272ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0014
273ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0015
467ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0016
605ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0017
606ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0018
813ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0019
814ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0020
814ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0021
815ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0022
815ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0023
815ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0024
815ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0025
1,027ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0026
1,027ms
200
script
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
V:R0027
1,795ms
200
fetch
www.rfc-editor.org
Not attributed
https://www.rfc-editor.org/…
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.
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. 16 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 13 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. Results describe these visits, not everything a site can do.