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, a script that wraps fetch or XHR is credited with the requests it relays, and a script can choose the name it is credited under. Requests made by dedicated workers are recorded and counted, but the browser reports no initiator for them, so they are not attributed. Asterisks mark subdomain labels hidden for privacy.- Attributed requests
- 0
- Not attributable
- 0
- Third-party requests
- 0
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.
Methodology
- Schema
- v1 schema · facts legacy-derived · descriptive report
- Run quality
- complete; derived from status and warnings
- Scanner
- playwright-chromium
- Playwright
- 1.62.1
- Browser
- 151.0.7922.34
- Timezone
- UTC
- Headless
- yes
- Viewport
- 1440×980
- GPC
- configured off · readback not recorded
- Egress
- github-actions-ubuntu
- Catalog
- Hand-curated service catalog
US-biased · hand-curated-2026.08
146 entries - Brave Shields lists
- Brave default ad-block lists
31 lists · fetched 8/15/2026
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.
Automated Chromium scan using Playwright 1.62.1 from github-actions-ubuntu with browser 151.0.7922.34, timezone UTC, locale en-US, the listed viewport, and Brave Shields block simulation. Brave-list matching uses each route-evaluated request's initiating document (the parent document for a subframe navigation), under methodology shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2; main-frame navigations are not blocked or counted as matches, and redirect follow-up URLs that Playwright does not re-route are not independently evaluated. Treat results as reproducible evidence for this scan configuration, not a universal claim about all visitors.