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 53 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 2 fewer third-party requests. The blocker directly stopped 3 requests, more than the net difference: a blocked request can be retried or replaced by another, and counts vary from run to run.
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.
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.
53 requests observed in one controlled visit.
What was checked
Page
https://hinge.co/
When
Nov 18, 2026, 6: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
No typing was recorded in either visit. 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. 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.
Context
2 requests matched Brave Shields filter lists
2 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 1 request row 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 2 fewer third-party requests.
Treat this as an observed difference, not a measured blocking rate.Details
The blocking visit's engine directly blocked 3 requests. 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
A consent management platform was requested
hinge.co sent a request to OneTrust, a consent management platform (the tooling that shows cookie banners). The request came before the scanner made any consent choice. Tracker-service observations are reported separately so this positive tooling signal does not imply an absence.
An observed response supports delivery, but neither fact proves a banner was visibly shown to this scanner.Details
A request to the platform's loader proves the page attempted to fetch consent tooling. Banner display can vary by region and visit context. The scanner never clicks a banner in this mode, so this report records requests made before the scanner made a consent choice. It does not determine whether any request required consent or whether the site's behavior complied with applicable law. More tracking-service entities or requests may appear after "Accept" than this report captures, so the counts here are lower bounds for users who consent.
Consent platform detected via a request to cdn.cookielaw.org.
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.
Global Privacy Control claims are never checked against request counts, which cannot show whether selling or sharing stopped.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.
Policy at https://hinge.co/privacy; 0 checkable statements matched; no catalogued tracking companies observed to check against it.
Context
Operational service matches were recorded
The catalog matched operational tools: Sentry.
The role taxonomy assigns these services explicitly non-tracking operational, support, security, consent-management, or hosting roles; the matches do not establish each request's purpose.Details
This scan identified an operator for every one of the 2 third-party domains recorded here using catalog, consent-platform, reviewed-ownership, and CNAME evidence.
3 cross-site requests across 2 third-party hosts.Below the median for third-party domains across the 74 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.
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 Nov 18, 2026, 6:08 PM UTC · 2,468msBrave-list blocking: started Nov 18, 2026, 6:08 PM UTC · 2,689msRan 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): 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 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
Sentry1 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 "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.
Read the site's privacy policy (https://hinge.co/privacy) and compared its text against this visit's observed behavior. Policy checks are an automated text match with the matched sentences quoted, not a legal reading.
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
*.*.sentry.io
service
1
Sentry: error monitoring
fetch
cdn.cookielaw.org
third-party
2
No catalog match
script
hinge.co
first-party
49
No catalog match
document, stylesheet, image, script, font, fetch, other
images.hinge.co
first-party
1
No catalog match
image
Request log
53 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
43ms
200
document
hinge.co
Not attributed
https://hinge.co/
B:R0002
147ms
200
image
images.hinge.co
initiated by hinge.co
https://images.hinge.co/…
B:R0003
147ms
200
stylesheet
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0004
147ms
200
stylesheet
hinge.co
Not attributed
https://hinge.co/…/static/…
B:R0005
148ms
200
stylesheet
hinge.co
Not attributed
https://hinge.co/…/static/…
B:R0006
149ms
200
image
hinge.co
initiated by hinge.co
https://hinge.co/…
B:R0007
151ms
n/a
script
cdn.cookielaw.org
initiated by hinge.co
https://cdn.cookielaw.org/…
B:R0008
152ms
n/a
script
cdn.cookielaw.org
initiated by hinge.co
https://cdn.cookielaw.org/…
B:R0009
152ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…
B:R0010
153ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…
B:R0011
153ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0012
153ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0013
153ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0014
153ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0015
153ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0016
153ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0017
154ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0018
155ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0019
155ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0020
155ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0021
156ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0022
156ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0023
156ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0024
156ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0025
156ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0026
156ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0027
156ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0028
157ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0029
157ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0030
157ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0031
157ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0032
157ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0033
157ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0034
157ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0035
229ms
200
font
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0036
229ms
200
font
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0037
229ms
200
font
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0038
230ms
200
font
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0039
230ms
200
font
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0040
273ms
200
fetch
*.*.sentry.io
initiated by hinge.co
https://*.*.sentry.io/api/…?…
B:R0041
393ms
200
stylesheet
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0042
394ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0043
404ms
200
fetch
hinge.co
Not attributed
https://hinge.co/…/static/…
B:R0044
405ms
200
fetch
hinge.co
Not attributed
https://hinge.co/…/static/…
B:R0045
427ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…
B:R0046
439ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…
B:R0047
440ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…
B:R0048
440ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…
B:R0049
440ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…
B:R0050
441ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…
B:R0051
487ms
200
other
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0052
536ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
B:R0053
536ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
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
3
Not attributable
0
Third-party requests
3
3 third-party requests: 3 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
2 requests to cdn.cookielaw.org, recorded as initiated by hinge.co.
1 request to Sentry, a catalogued service, recorded as initiated by hinge.co.
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.65.1 from github-actions-ubuntu with browser 159.0.8154.6, 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.5-request-method-v1-playwright-1.65.1+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-11-18T18:08:38.817Z · 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.
Requests511 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
cdn.cookielaw.org
third-party
1
No catalog match
script
hinge.co
first-party
49
No catalog match
document, stylesheet, image, script, font, fetch, other
images.hinge.co
first-party
1
No catalog match
image
Request log
51 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
44ms
200
document
hinge.co
Not attributed
https://hinge.co/
V:R0002
138ms
200
image
images.hinge.co
initiated by hinge.co
https://images.hinge.co/…
V:R0003
139ms
200
stylesheet
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0004
139ms
200
stylesheet
hinge.co
Not attributed
https://hinge.co/…/static/…
V:R0005
139ms
200
stylesheet
hinge.co
Not attributed
https://hinge.co/…/static/…
V:R0006
140ms
200
image
hinge.co
initiated by hinge.co
https://hinge.co/…
V:R0007
143ms
n/a
script
cdn.cookielaw.org
initiated by hinge.co
https://cdn.cookielaw.org/…
V:R0008
143ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…
V:R0009
143ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…
V:R0010
143ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0011
144ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0012
144ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0013
144ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0014
145ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0015
146ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0016
146ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0017
146ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0018
146ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0019
146ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0020
147ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0021
147ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0022
147ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0023
147ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0024
147ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0025
147ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0026
147ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0027
147ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0028
147ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0029
147ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0030
147ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0031
148ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0032
148ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0033
148ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0034
210ms
200
font
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0035
214ms
200
font
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0036
214ms
200
font
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0037
214ms
200
font
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0038
214ms
200
font
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0039
378ms
200
stylesheet
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0040
379ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0041
391ms
200
fetch
hinge.co
Not attributed
https://hinge.co/…/static/…
V:R0042
391ms
200
fetch
hinge.co
Not attributed
https://hinge.co/…/static/…
V:R0043
414ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…
V:R0044
422ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…
V:R0045
423ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…
V:R0046
423ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…
V:R0047
424ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…
V:R0048
424ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…
V:R0049
524ms
200
other
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0050
551ms
200
script
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
V:R0051
552ms
200
fetch
hinge.co
initiated by hinge.co
https://hinge.co/…/static/…
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
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 cdn.cookielaw.org, recorded as initiated by hinge.co.
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.65.1 from github-actions-ubuntu with browser 159.0.8154.6, 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.5-request-method-v1-playwright-1.65.1+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
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. 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.