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
0000000000000000000000000
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name6 requests2 hosts; the catalog cannot say who operates them
000000
Brave-list blocking
www.rfc-editor.org itself25 requestsrequests that stayed on the site
0000000000000000000000000
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name2 requests1 host; the catalog cannot say who operates it
00
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.
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.
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.
Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.
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.
Domain evidence
3 recorded domains
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
Domain
Requests
When, 0 to 4.7 s
Catalog match
Role
Resource types
www.rfc-editor.org
25
No catalog match
first-party
document, stylesheet, script, image, fetch
analytics.ietf.org
4
No catalog match
third-party
script, ping
static.ietf.org
2
No catalog match
third-party
stylesheet, font
Raw evidence
Open the interactive evidence explorer
The findings above are built from the stored report. Load the request rows, domains, cookies, storage keys, browser signals, visit phases, charts and CSV export when you want to check them; the versioned report JSON is always available below without this interface.
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.
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. A study has been recorded for pixel-events and does not support a published rate under the current build. How detector accuracy is measured.
Severity percentiles come from this report's exact schema, methodology, tracker-catalog, ServiceRole-taxonomy, metric-contract, producer, and Global Privacy Control cohort. Each percentile card's measured sites are among 99 sites with a successful load across all cohorts. Other methodologies and post-choice consent visits are excluded from each card's denominator, while failed or block-page attempts are outside that coverage. Visits with capped or incomplete request evidence are left out of each mark. They tend to be the heaviest pages, so a mark can sit lower than the cohort's true mark.
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 .