usa.gov recorded 16 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.usa.gov itself26 requestsrequests that stayed on the site
00000000000000000000000000
Catalogued services8 requests2 names: Google 7, Crazy Egg 1
00000000
Hosts the catalog does not name9 requests6 hosts; the catalog cannot say who operates them
000000000
Brave-list blocking
www.usa.gov itself26 requestsrequests that stayed on the site
00000000000000000000000000
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name1 request1 host; the catalog cannot say who operates it
0
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
one request on record, same site
one request on record, cross-site
not measured
The visit with no blocking made 43 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 16 fewer third-party requests. The blocker directly stopped 3 requests; 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 worth checking
The scan observed signals a non-expert should not have to decode from raw request tables.
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.
43 requests observed in one controlled visit.
What was checked
Page
https://www.usa.gov/
When
Sep 28, 2026, 12:08 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.
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.
Worth checking
13 requests matched Brave Shields filter lists
13 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 8 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 16 fewer third-party requests and 8 fewer tracking-related service requests.
Treat this as an observed difference, not a measured blocking rate.Details
Services only seen in the unblocked visit: Google and Crazy Egg. The blocking visit's engine directly blocked 3 requests; 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
Requests were dispatched to catalogued service domains
Google and Crazy Egg appeared in the request log.
A catalog match identifies a maintainer-reviewed service/domain mapping; it does not establish why an individual request occurred, what it carried, or whether profiling happened.Details
Functional catalog labels include analytics / tag management and session replay / behavior analytics. This scan could not identify 6 of the 9 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site. Catalog labels include session-replay or behavior-analytics services: Crazy Egg. The domain match alone does not prove that a recording occurred.
17 cross-site requests across 9 third-party hosts.At or above the median for third-party domains across the 85 sites measured for this metric. Modest distinct tracking-service entities count.Show third-party requests
Context
Requests were dispatched to catalogued major-platform domains
This visit dispatched requests to catalogued domains for Google.
The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.
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.
5 cookies total in this report.No third-party cookies observed.
Worth checking
Session-recording signal matched a known vendor
The page registered broad interaction listeners through call chains that included a third-party script, and contacted a known session-replay service.
This is a behavioral instrumentation signal from listener registration, stack-attributed script origins, and known-vendor requests: it shows the page was instrumented to observe interaction, not that anything was transmitted.Details
Stack attribution records the script origins present in the bounded registration call chain. A cross-site origin in that chain does not by itself establish that the cross-site script registered the listener. That is because first-party code can register its own listeners through a helper served from elsewhere. A different registrable domain is also not by itself a different operator: sites commonly serve their own scripts from a separate asset domain. The card therefore says third party only when the catalog or reviewed ownership attributes an origin to another organization. On scanners that run the active keystroke-capture probe, actual transmission is tested separately (a synthetic value is typed, never real input, and no typed values are collected). Treat this card as a review prompt rather than proof.
Session-recording listener coverage: 181 interaction-listener registrations with https://*.digitalgov.gov/, https://siteimproveanalytics.com/ and https://www.googletagmanager.com/ in the registration call chain. Known session-replay vendor(s): Crazy Egg.
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.
Scan report ready for www.usa.gov: 43 recorded request rows.
Comparison ReportOlder format: some facts reconstructed, descriptive only
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, 12:08 PM UTC · 4,613msBrave-list blocking: started Sep 28, 2026, 12:08 PM UTC · 4,473msRan first: No 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): v1 never recorded detector versions, so fingerprinting and pixel deltas cannot be proven to come from matching instrumentation.
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.
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.
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
_ga.usa.govfirst-party
Storage keys only with Brave-list blocking
No storage key changes observed.
Storage keys only with No blocking
No storage key changes observed.
Entities only with Brave-list blocking
No entity changes observed.
Entities only with No blocking
Google2 domains7
Crazy Egg1 domain1
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 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.
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.
Every domain this visit recorded, with its role, request count and catalog match.
Domain
Role
Requests
Catalog match
Resource types
www.googletagmanager.com
service
5
Google: analytics / tag management
script
www.google-analytics.com
service
2
Google: analytics / tag management
fetch
*.crazyegg.com
service
1
Crazy Egg: session replay / behavior analytics
script
*.*.qualtrics.com
third-party
3
No catalog match
script, xhr
*.digitalgov.gov
third-party
2
No catalog match
script
siteimproveanalytics.com
third-party
1
No catalog match
script
host unavailable
third-party
1
No catalog match
xhr
*.*.siteimproveanalytics.io
third-party
1
No catalog match
image
*.*.*.qualtrics.com
third-party
1
No catalog match
script
www.usa.gov
first-party
26
No catalog match
document, image, stylesheet, script, other, font
Request log
43 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.
Every request row this visit retained, with its time, status, resource type, domain and recorded provenance.
Ref
Time
Status
Type
Domain
Provenance
URL
B:R0001
52ms
200
document
www.usa.gov
Not attributed
https://www.usa.gov/
B:R0002
101ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0003
102ms
200
stylesheet
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0004
102ms
200
stylesheet
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0005
102ms
200
stylesheet
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0006
102ms
200
stylesheet
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0007
103ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0008
103ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0009
146ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0010
169ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0011
171ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0012
174ms
200
script
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0013
174ms
200
script
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0014
176ms
200
script
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0015
176ms
n/a
script
*.crazyegg.com
initiated by www.usa.gov
https://*.crazyegg.com/…
B:R0016
176ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0017
177ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0018
177ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0019
178ms
200
script
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0020
179ms
200
script
www.googletagmanager.com
initiated by www.usa.gov
https://www.googletagmanager.com/…?id
B:R0021
179ms
200
other
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0022
224ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0023
224ms
200
font
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0024
225ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0025
226ms
200
font
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0026
226ms
200
font
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0027
226ms
200
font
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0028
227ms
200
font
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
B:R0029
295ms
200
script
siteimproveanalytics.com
initiated by www.usa.gov
https://siteimproveanalytics.com/…
B:R0030
308ms
200
xhr
host unavailable
initiated by www.usa.gov
URL unavailable
B:R0031
412ms
200
script
www.googletagmanager.com
initiated by www.googletagmanager.com
https://www.googletagmanager.com/…?id&…
B:R0032
412ms
200
script
www.googletagmanager.com
initiated by www.googletagmanager.com
https://www.googletagmanager.com/…?id&…
B:R0033
413ms
200
script
*.digitalgov.gov
initiated by www.googletagmanager.com
https://*.digitalgov.gov/…?…
B:R0034
462ms
200
script
*.digitalgov.gov
initiated by *.digitalgov.gov
https://*.digitalgov.gov/…
B:R0035
462ms
200
script
www.googletagmanager.com
initiated by *.digitalgov.gov
https://www.googletagmanager.com/…?id
B:R0036
462ms
200
script
www.googletagmanager.com
initiated by www.googletagmanager.com
https://www.googletagmanager.com/…?id&…
B:R0037
476ms
200
image
*.*.siteimproveanalytics.io
initiated by www.usa.gov
https://*.*.siteimproveanalytics.io/…?…
B:R0038
629ms
204
fetch
www.google-analytics.com
initiated by www.googletagmanager.com
https://www.google-analytics.com/…?v&tid&…&cid
B:R0039
711ms
204
fetch
www.google-analytics.com
initiated by www.googletagmanager.com
https://www.google-analytics.com/…?v&tid&…&cid
B:R0040
746ms
200
script
*.*.*.qualtrics.com
Not attributed
https://*.*.*.qualtrics.com/…?…
B:R0041
922ms
200
script
*.*.qualtrics.com
initiated by *.*.*.qualtrics.com
https://*.*.qualtrics.com/…?…
B:R0042
923ms
200
script
*.*.qualtrics.com
initiated by *.*.*.qualtrics.com
https://*.*.qualtrics.com/…?…
B:R0043
1,201ms
200
xhr
*.*.qualtrics.com
initiated by *.*.qualtrics.com
https://*.*.qualtrics.com/…?…
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 not observed. Asterisks mark subdomain labels hidden for privacy.
Attributed requests
16
Not attributable
1
Third-party requests
17
No unique actor could be assigned to 1 of these requests. That includes requests for which the browser reported no usable initiator, repeated URLs seen with conflicting initiators, and URLs requested more times than the scan received an initiator for them, such as one a dedicated worker also requested. This report does not distinguish those causes, so they are counted together rather than drawn.
17 third-party requests: 16 attributed to a single recorded actor, 1 not attributable.
Horizontally scrollable visual map. A text list of every relationship drawn in it follows.
Select a relationship to see its detail and open the rows behind it.
Relationships shown in the request attribution map
5 requests to Google, a catalogued service, recorded as initiated by www.googletagmanager.com.
2 requests to *.*.qualtrics.com, recorded as initiated by *.*.*.qualtrics.com.
1 request to *.*.qualtrics.com, recorded as initiated by *.*.qualtrics.com.
1 request to *.digitalgov.gov, recorded as initiated by *.digitalgov.gov.
1 request to Google, a catalogued service, recorded as initiated by *.digitalgov.gov.
1 request to *.digitalgov.gov, recorded as initiated by www.googletagmanager.com.
1 request to *.*.siteimproveanalytics.io, recorded as initiated by www.usa.gov.
1 request to Crazy Egg, a catalogued service, recorded as initiated by www.usa.gov.
1 request to Google, a catalogued service, recorded as initiated by www.usa.gov.
1 request to host unavailable, recorded as initiated by www.usa.gov.
1 request to siteimproveanalytics.com, recorded as initiated by www.usa.gov.
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.
Automated Chromium scan using Playwright 1.63.0 from github-actions-ubuntu with browser 153.0.8010.12, timezone UTC, locale en-US, the listed viewport, and Brave Shields classification only. 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.3-request-method-v1-playwright-1.63.0+subject-validity-v4+detector-coverage-v2+fingerprint-surface-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.
Brave-list blocking: evidence
2026-09-28T12:08:42.976Z · complete; derived from status and warnings
Retained observations from this visit. Missing measurements do not establish absence of activity.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.
Requests271 third-party
Blocked by Brave lists3engine blocks reported by this visit; no engine readback recorded
Third-party domains10 distinct catalogued service entities
Every domain this visit recorded, with its role, request count and catalog match.
Domain
Role
Requests
Catalog match
Resource types
host unavailable
third-party
1
No catalog match
xhr
www.usa.gov
first-party
26
No catalog match
document, image, stylesheet, script, other, font
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.
Every request row this visit retained, with its time, status, resource type, domain and recorded provenance.
Ref
Time
Status
Type
Domain
Provenance
URL
V:R0001
58ms
200
document
www.usa.gov
Not attributed
https://www.usa.gov/
V:R0002
106ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0003
107ms
200
stylesheet
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0004
107ms
200
stylesheet
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0005
107ms
200
stylesheet
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0006
107ms
200
stylesheet
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0007
107ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0008
108ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0009
149ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0010
174ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0011
175ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0012
178ms
200
script
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0013
179ms
200
script
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0014
180ms
200
script
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0015
181ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0016
181ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0017
182ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0018
182ms
200
script
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0019
184ms
200
other
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0020
228ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0021
229ms
200
font
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0022
229ms
200
image
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0023
229ms
200
font
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0024
230ms
200
font
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0025
231ms
200
font
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0026
231ms
200
font
www.usa.gov
initiated by www.usa.gov
https://www.usa.gov/…
V:R0027
305ms
200
xhr
host unavailable
initiated by www.usa.gov
URL unavailable
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 not observed. Asterisks mark subdomain labels hidden for privacy.
Attributed requests
1
Not attributable
0
Third-party requests
1
1 third-party requests: 1 attributed to a single recorded actor, 0 not attributable.
Horizontally scrollable visual map. A text list of every relationship drawn in it follows.
Select a relationship to see its detail and open the rows behind it.
Relationships shown in the request attribution map
1 request to host unavailable, recorded as initiated by www.usa.gov.
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.
Automated Chromium scan using Playwright 1.63.0 from github-actions-ubuntu with browser 153.0.8010.12, 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.3-request-method-v1-playwright-1.63.0+subject-validity-v4+detector-coverage-v2+fingerprint-surface-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.
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.
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
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 .
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.