Baseline visit v2 schema (r2)
https://www.wikipedia.org/
Aug 14, 2026, 7:09 PM UTC
complete; recorded by the scanner
Public corrections ledger · SBL-CORR-2026-001
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.
Scan report ready for wikipedia.org: 6 recorded request rows.
Comparison Reportv2 schema (r2)
Nothing observed
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.
Nothing observed
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.
Context
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.
Nothing observed
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.
Nothing observed
No requests to catalogued Google, Meta, TikTok, X, Microsoft, LinkedIn, or Pinterest domains were observed in this visit.
Major-platform domains were not observed in this single passive visit; interaction-gated requests could still load for real users.
Nothing observed
This visit did not contact Google Analytics.
Neither Google Analytics nor its remarketing sync was observed in this visit.
Nothing observed
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.
Nothing observed
The scan did not observe the instrumented high-entropy browser APIs.
This is an observation layer, not proof that fingerprinting is impossible.
GPC Comparison
Both visits
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.
Correction context SHA-256: 8b4dc650c91f9e1a20f651118d74586978963548cecaa5885e2565e2ccc68c32
Renderer revision: 3c18992e02534f33c825f7c2e51dd534d3ccab0d
2026-08-14T19:09:08.573Z · complete; recorded by the scanner
Retained observations from this visit. Missing measurements do not establish absence of activity.
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.6 requests were recorded from 68 ms to 1,160 ms. Open the request log for exact timing and request details.
Recorded visit structure
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.
| 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 |
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.
8 change records hide unreviewed names or keys because they can contain identifiers.
| 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 |
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.
| 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/… |
2026-08-14T19:09:12.978Z · complete; recorded by the scanner
Retained observations from this visit. Missing measurements do not establish absence of activity.
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.6 requests were recorded from 87 ms to 1,113 ms. Open the request log for exact timing and request details.
Recorded visit structure
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.
| 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 |
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.
8 change records hide unreviewed names or keys because they can contain identifiers.
| 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 |
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.
| 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/… |
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.
Integrity and provenance
20260814-31e105d7971825fbd0f3fffa099188feshields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f40f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0acredaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f40f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0acredaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1Recorded 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 .