Site

www.rfc-editor.org

Baseline visit
Requested address
https://www.rfc-editor.org/
Report ID
20260928-5ebf22e82248b73b1741c796f9f57315
Evidence SHA-256
29e7fc119fdecac6d2c9dd4fc3ed166f67cd293b45140735ac26d2ac674a41d5
Scanner
playwright-chromium

rfc-editor.org recorded 4 fewer third-party requests in the visit configured for Brave-list blocking.

Where this page's requests went

Both visits. One mark is one request row in the retained log.

No blocking

www.rfc-editor.org itself25 requestsrequests that stayed on the site
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name6 requests2 hosts; the catalog cannot say who operates them

Brave-list blocking

www.rfc-editor.org itself25 requestsrequests that stayed on the site
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name2 requests1 host; the catalog cannot say who operates it
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 visit with no blocking made 31 requests; the visit 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) recorded 4 fewer third-party requests. The blocker directly stopped 1 request; the remaining difference may include follow-on requests that never started once their sources were blocked, plus run-to-run variance.

2cross-site domains
6cross-site requests
1third-party cookie record

Context

Bottom line: this visit has signals, none ranked worth checking

The scan observed signals a non-expert should not have to decode from raw request tables. Some detector evidence was incomplete; each affected detector card states its own retained or unavailable scope, while completed request, cookie, and storage measurements keep their recorded exactness.

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.

31 requests observed in one controlled visit.

What was checked

Page
https://www.rfc-editor.org/
When
Sep 28, 2026, 3:43 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 GitHub Actions Ubuntu runner; the network region was not recorded. Neither sent the Global Privacy Control (GPC) signal.
Visits
Two visits configured to differ in Brave-list blocking: No blocking and Brave-list blocking.
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, but some evidence was cut short.

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: fingerprinting, session-recording signals, the typing test, CNAME cloaking, advertising pixels, the consent banner and the privacy policy check. Each linked card states what was retained.

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.

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

Not flagged

Lower values observed across comparable metrics in the Brave-list blocking attempt

The blocking visit ran with the scanner configured to apply Brave's ad-block engine and default Shields filter lists. It was a simulation in this scanner's browser, not a live Brave-browser visit, and application was not verified. Compared with the unblocked visit, it showed 4 fewer third-party requests.

Treat this as an observed difference, not a measured blocking rate. Details

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

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.

This scan could not identify 2 of the 2 third-party hosts recorded here, so it cannot say who operates them. Details

No known operator or catalog entity was matched. That is a limit of identity coverage, not evidence about the site.

6 cross-site requests across 2 third-party hosts.Below the median for third-party domains across the 85 sites measured for this metric.Show third-party requests

Not flagged

No requests to catalogued 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

Not flagged

No Google Analytics observed

This visit did not contact Google Analytics.

This does not prove the site never uses Google Analytics; it means this visit recorded no request to it. Details

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

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

Context

Third-party cookies were present

1 third-party cookie showed up during the visit.

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

The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary.

4 cookies total in this report.At or above the median for third-party cookies across the 85 sites measured for this metric.

Context

Incomplete evidence: No fingerprint-like API calls observed in retained evidence before collection stopped

The retained evidence holds no calls to the instrumented high-entropy browser APIs.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

This is an observation layer, not proof that fingerprinting is impossible.

Retained incomplete evidence includes 0 API event records; no exact API-family total is available.

Scan report ready for www.rfc-editor.org: 31 recorded request rows.

Comparison ReportOlder format: some facts reconstructed, descriptive only

Brave-list blocking off/on comparison

Recorded final address https://www.rfc-editor.org/ (opens in a new tab)
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.

Brave Shields Comparison

No blocking → Brave-list blocking delta

No blocking: started Sep 28, 2026, 3:43 PM UTC · 4,652msBrave-list blocking: started Sep 28, 2026, 3:43 PM UTC · 4,629msRan first: Brave-list blocking
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): The No blocking visit did not complete this measurement, so it has no exact count. The Brave-list blocking visit did not complete this measurement, so it has no exact count.
  • Ad-pixel deltas (each visit's own evidence still renders below): The record of the No blocking visit does not hold this measurement. The record of the Brave-list blocking visit does not hold this measurement.
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

7 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 "Brave-list 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.
  • The in-page fingerprint observer read every frame but could not attribute every event listener to the script that registered it, so session-recording and input-monitoring findings for this visit are incomplete.
  • This scan typed a synthetic test value into 1 form field with native form submission blocked. Focus, input and blur handlers may run and send requests. The value is synthetic and is not stored. Observed requests during typing and the following wait are included in the request log. Teardown-only transmissions are not measured.

Brave-list blocking visit only

  • Brave Shields block simulation was enabled; matching requests were aborted before loading and are not included in request totals.

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.

Report ID
20260928-5ebf22e82248b73b1741c796f9f57315
Site
www.rfc-editor.org
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the in-page fingerprint observer could not attribute every event listener to the script that registered it, so the fingerprinting evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.

Variant visit

Started
Run quality
cut short: the in-page fingerprint observer could not attribute every event listener to the script that registered it, so the fingerprinting evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
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 .