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
w3.org's completed measurements recorded no listed activity, but some optional detector evidence was not recorded in this legacy report.
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. Some optional detector evidence was not recorded in this legacy report, so whatever that check looks for is unproven here rather than shown to be absent.
The automated visit did not observe known third-party services, third-party cookies, or instrumented fingerprint-like calls.
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.
25 requests observed in one controlled visit.
Nothing observed
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.
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
Low signal
No change observed in the Brave-list blocking attempt
The blocking visit (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)) showed no change in the comparable metrics (third-party requests, third-party cookies and tracking-related service requests).
The blocking visit's engine directly blocked 0 requests; ad rotation, experiments, or caching between the two visits can offset or outweigh what blocking removed, which is how totals can hold steady or rise despite direct blocks. A single paired comparison can also reflect run-to-run variance (ad rotation, caching, experiments), so treat this as no observed difference for this pair of visits, not evidence that blocking removes nothing.
Signed per-metric differences between the two visits; nothing is summed across metrics.Show matched requests
Context
Privacy policy read; it made no statement this scan can check
None of the statements this scan knows how to check appear in the policy text, so nothing was compared against this visit's evidence (no catalogued tracking companies observed to check against it). That is a limit of the automated check, not a finding about the site either way.
Statements checked automatically: blanket no-cookie claims, third-party-cookie claims, and combined do-not-sell-or-share claims against advertising-pixel identifier fields. Global Privacy Control claims are never checked against request counts, which cannot show whether selling or sharing stopped.
Policy at https://www.w3.org/{seg}/privacy; 0 checkable statements matched; no catalogued tracking companies observed to check against it.
Nothing observed
No known services matched
This scan did not match any third-party domains to the service catalog or another identity source.
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.
1 cookie total in this report.No third-party cookies observed.
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: 1,965msBrave-list blocking: 1,908ms
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.
Largest per-domain request-count changes
No per-domain request counts changed between these visits.
Domains only with Brave-list blocking
No domain changes observed.
Domains only with No blocking
No domain changes observed.
Cookies only with Brave-list blocking
No cookie changes observed.
Cookies only with No blocking
No cookie changes observed.
Storage keys only with Brave-list blocking
No storage key changes observed.
Storage keys only with No blocking
No storage key changes observed.
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.
Read the site's privacy policy (https://www.w3.org/{seg}/privacy) and compared its text against this visit's observed behavior. Policy checks are an automated text match with the matched sentences quoted, not a legal reading.
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-09-07T05:18:40.063Z · 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
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.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.
Requests250 third-party
Matched Shields lists0classification reported by this visit; no engine readback recorded
Third-party domains00 distinct catalogued service entities
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
45ms
200
document
www.w3.org
Not attributed
https://www.w3.org/
B:R0002
85ms
200
stylesheet
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0003
86ms
200
stylesheet
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0004
86ms
200
script
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0005
86ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0006
114ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0007
116ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0008
120ms
200
stylesheet
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0009
124ms
200
font
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0010
124ms
200
script
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0011
125ms
200
script
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0012
128ms
206
media
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0013
176ms
200
font
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0014
178ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0015
179ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0016
179ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0017
180ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0018
180ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0019
193ms
200
xhr
www.w3.org
initiated by www.w3.org
https://www.w3.org/account/…
B:R0020
209ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0021
209ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0022
210ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0023
210ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0024
210ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
B:R0025
211ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
Brave-list blocking — evidence
2026-09-07T05:18:42.037Z · 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
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.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.
Requests250 third-party
Blocked by Brave lists0engine blocks reported by this visit; no engine readback recorded
Third-party domains00 distinct catalogued service entities
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
46ms
200
document
www.w3.org
Not attributed
https://www.w3.org/
V:R0002
87ms
200
stylesheet
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0003
88ms
200
stylesheet
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0004
88ms
200
script
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0005
88ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0006
115ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0007
116ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0008
121ms
200
stylesheet
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0009
123ms
200
font
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0010
124ms
200
script
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0011
125ms
200
script
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0012
126ms
206
media
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0013
154ms
200
xhr
www.w3.org
initiated by www.w3.org
https://www.w3.org/account/…
V:R0014
173ms
200
font
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0015
180ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0016
181ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0017
181ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0018
182ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0019
182ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0020
182ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0021
183ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0022
183ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0023
184ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0024
184ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.org/…
V:R0025
184ms
200
image
www.w3.org
initiated by www.w3.org
https://www.w3.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.