Both visits. One mark is one request row in the retained log.
No blocking
www.python.org itself25 requestsrequests that stayed on the site
0000000000000000000000000
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name4 requests2 hosts; the catalog cannot say who operates them
0000
Brave-list blocking
www.python.org itself24 requestsrequests that stayed on the site
000000000000000000000000
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name4 requests2 hosts; the catalog cannot say who operates them
0000
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
1 request matched while loading normally. This run records no evaluated-request count, so no match ratio is stated. Matching identifies traffic the lists would target; it does not establish the purpose or payload of an individual request.
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.
29 requests observed in one controlled visit.
What was checked
Page
https://www.python.org/
When
Nov 18, 2026, 5:36 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. The privacy policy was opened only to read its text, and none of its 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: the privacy policy check. Each linked card states what was retained.
Context
1 request matched Brave Shields filter lists
1 request 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
Low signal
No change observed 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 no change in the comparable metrics (third-party requests, third-party cookies and tracking-related service requests).
Treat this as no observed difference for this pair of visits, not evidence that blocking removes nothing.Details
The blocking visit's engine directly blocked 1 request. 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).
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. As a result, 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.
Evidence collection was cut short, so this covers only what was recorded before the cutoff.Details
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://*.python.org/…; 0 checkable statements matched; no catalogued tracking companies observed to check against it.
Context
Other third-party operators were identified outside the tracking-service catalog
Google was named by consent-platform signatures, reviewed ownership, or CNAME evidence without being classified as a tracking service.
Operator identity and tracking classification are separate: naming an operator does not prove that a request was for tracking.Details
This scan could not identify 1 of the 2 third-party hosts recorded here, so it cannot say who operates it. That is a limit of identity coverage, not evidence about the site.
4 cross-site requests across 2 third-party hosts. This report does not record which requests came during the typing test.Below the median for third-party domains across the 74 sites measured for this metric.Show third-party requests
Context
Requests were dispatched to major-platform domains the catalog does not carry
This visit dispatched requests to Google domains that the reviewed ownership map names, though the service catalog carries no entry for them.
Asset and font hosts reach this state often: the ownership map establishes who operates the domain, and nothing here establishes the request's purpose or payload.Details
These domains are not counted as catalog-matched requests.
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.
0 cookies total in this report.No third-party cookies observed.
Not flagged
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.
Domain evidence
5 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 5.6 s
Catalog match
Role
Resource types
www.python.org
23
No catalog match
first-party
document, script, stylesheet, image, font, xhr
ajax.googleapis.com
3
No catalog match
third-party
stylesheet, script
*.statuspage.io
1
No catalog match
third-party
xhr
analytics.python.org
1
No catalog match
first-party
script
*.python.org
1
No catalog match
first-party
xhr
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 scanner's search for a privacy-policy link did not cover every link on the page, so privacy-policy findings are incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
159.0.8154.6
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 scanner's search for a privacy-policy link did not cover every link on the page, so privacy-policy findings are incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
159.0.8154.6
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 98 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 .