Baseline visit v1 schema · facts legacy-derived · descriptive report

www.rfc-editor.org

Requested addresshttps://www.rfc-editor.org/

Aug 17, 2026, 8:12 AM UTC

complete; derived from status and warnings

View site historyScan this exact route againReport an evidence problem

Public corrections ledger · SBL-CORR-2026-001

This report has a reviewed clarification

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.

Read the public review record

Comparison Reportv1 schema · facts legacy-derived · descriptive report

Brave-list blocking off/on comparison

Recorded final address https://www.rfc-editor.org/
SharePDF + evidence

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.

2cross-site domains
6cross-site requests
1third-party cookie record
Observed in two automated visits: evidence to check, not a verdict.
Post on X

Plain-Language Findings

What this visit means

Unfamiliar terms are defined in the glossary
playwright-chromium

Context

Bottom line: this visit has review-worthy signals

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.

6 cross-site requests across 2 third-party hosts.Modest third-party domains count.Show third-party requests

Nothing observed

No requests to major-platform domains were recorded

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.

2 cross-site domains seen overall.Show catalog-matched requests

Nothing observed

No Google Analytics observed

This visit did not contact Google Analytics.

Neither Google Analytics nor its remarketing sync was observed in this visit.

No google-analytics.com or googletagmanager.com requests.Show catalog-matched requests

Context

Third-party cookies were present

1 third-party cookie showed up during the visit.

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: 4,808msBrave-list blocking: 4,680ms
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.
Requests-4No blocking: 31 · Brave-list blocking: 27
Third-party requests-4No blocking: 6 · Brave-list blocking: 2
Third-party domains-1No blocking: 2 · Brave-list blocking: 1
Cookies-2No blocking: 4 · Brave-list blocking: 2
Third-party cookies0No blocking: 1 · Brave-list blocking: 1
Storage keys0No blocking: 1 · Brave-list blocking: 1
Catalog-matched requests0No blocking: 0 · Brave-list blocking: 0

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.

Largest per-domain request-count changes

analytics.ietf.orgunlabeled third partyNo blocking: 4 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-4

Domains only with Brave-list blocking

No domain changes observed.

Domains only with No blocking

analytics.ietf.orgunlabeled · Show No blocking requests4

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.

Correction context SHA-256: 8b4dc650c91f9e1a20f651118d74586978963548cecaa5885e2565e2ccc68c32

Renderer revision: eecb7335c392c47923d403345d915c99c2bb4bc1

No blocking — evidence

2026-08-17T08:12:15.286Z · 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
6
Not attributable
0
Third-party requests
6

6 third-party requests: 6 attributed to a single recorded actor, 0 not attributable.

Select a relationship to see its detail and open the rows behind it.

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
Cookies41 third-party
Storage keys11 key privacy-filtered; values omitted
Fingerprint API calls00 API families
GPC signalConfigured offreadback not recorded
Duration4.8s8:12:15 AM UTC

Request composition & timeline

First-party requests 25
Other third-party requests 6
Catalog-matched third-party requests 0

31 requests were recorded from 42 ms to 1,635 ms. Open the request log for exact timing and request details.

0 ms1,635 ms

Domain evidence

3 recorded domains
DomainRoleRequestsCatalog matchResource types
analytics.ietf.orgthird-party4No catalog matchscript, ping
static.ietf.orgthird-party2No catalog matchstylesheet, font
www.rfc-editor.orgfirst-party25No catalog matchdocument, 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.

RefTimeStatusTypeDomainProvenanceURL
B:R000142ms200documentwww.rfc-editor.orgNot attributedhttps://www.rfc-editor.org/
B:R000289ms200stylesheetstatic.ietf.orginitiated by www.rfc-editor.orghttps://static.ietf.org/…
B:R000389ms200stylesheetwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
B:R000490ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
B:R0005160ms200imagewww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
B:R0006163ms200imagewww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
B:R0007192ms200fontstatic.ietf.orginitiated by static.ietf.orghttps://static.ietf.org/…
B:R0008203ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
B:R0009204ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
B:R0010204ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
B:R0011205ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
B:R0012205ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
B:R0013206ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
B:R0014206ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
B:R0015384ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
B:R0016470ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
B:R0017470ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
B:R0018630ms200scriptanalytics.ietf.orginitiated by www.rfc-editor.orghttps://analytics.ietf.org/…
B:R0019673ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
B:R0020674ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
B:R0021674ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
B:R0022675ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
B:R0023676ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
B:R0024676ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
B:R0025676ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
B:R0026686ms204pinganalytics.ietf.orginitiated by analytics.ietf.orghttps://analytics.ietf.org/…?…
B:R0027810ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
B:R0028811ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
B:R00291,506ms204pinganalytics.ietf.orginitiated by analytics.ietf.orghttps://analytics.ietf.org/…?…
B:R00301,586ms204pinganalytics.ietf.orginitiated by analytics.ietf.orghttps://analytics.ietf.org/…?…
B:R00311,635ms200fetchwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…

Brave-list blocking — evidence

2026-08-17T08:12:20.100Z · 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
2
Not attributable
0
Third-party requests
2

2 third-party requests: 2 attributed to a single recorded actor, 0 not attributable.

Select a relationship to see its detail and open the rows behind it.

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
Cookies21 third-party
Storage keys11 key privacy-filtered; values omitted
Fingerprint API calls00 API families
GPC signalConfigured offreadback not recorded
Duration4.7s8:12:20 AM UTC

Request composition & timeline

First-party requests 25
Other third-party requests 2
Catalog-matched third-party requests 0

27 requests were recorded from 47 ms to 1,574 ms. Open the request log for exact timing and request details.

0 ms1,574 ms

Domain evidence

2 recorded domains
DomainRoleRequestsCatalog matchResource types
static.ietf.orgthird-party2No catalog matchstylesheet, font
www.rfc-editor.orgfirst-party25No catalog matchdocument, 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.

RefTimeStatusTypeDomainProvenanceURL
V:R000147ms200documentwww.rfc-editor.orgNot attributedhttps://www.rfc-editor.org/
V:R000294ms200stylesheetstatic.ietf.orginitiated by www.rfc-editor.orghttps://static.ietf.org/…
V:R000394ms200stylesheetwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
V:R000495ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
V:R0005162ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
V:R0006163ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
V:R0007164ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
V:R0008164ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
V:R0009164ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
V:R0010165ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
V:R0011165ms200scriptwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
V:R0012178ms200imagewww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
V:R0013179ms200imagewww.rfc-editor.orginitiated by www.rfc-editor.orghttps://www.rfc-editor.org/…
V:R0014207ms200fontstatic.ietf.orginitiated by static.ietf.orghttps://static.ietf.org/…
V:R0015320ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
V:R0016414ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
V:R0017415ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
V:R0018608ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
V:R0019608ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
V:R0020608ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
V:R0021608ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
V:R0022609ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
V:R0023610ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
V:R0024610ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
V:R0025694ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
V:R0026695ms200scriptwww.rfc-editor.orginitiated by URL unavailablehttps://www.rfc-editor.org/…
V:R00271,574ms200fetchwww.rfc-editor.orginitiated by www.rfc-editor.orghttps://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.

Integrity and provenance

Evidence receipt

Open report JSONDownload corrections with this JSONOpen provenance sidecarPrintable versionDownload PDF + evidenceOpen PDF
Report ID
20260817-e47b0833825b31f18b78d637f8a80e85
Site
www.rfc-editor.org
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline 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.

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. 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.