Hosts the catalog does not name0 requestsno other cross-site host on record
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 91 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 38 fewer third-party requests. The blocker directly stopped 4 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.
91 requests observed in one controlled visit.
What was checked
Page
Requested https://www.clevelandclinic.org/; both visits landed on https://*.clevelandclinic.org/
When
Nov 18, 2026, 6:07 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.
Worth checking
23 requests matched Brave Shields filter lists
23 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 25 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 38 fewer third-party requests, 5 fewer third-party cookies and 9 fewer tracking-related service requests.
Treat this as an observed difference, not a measured blocking rate.Details
Services only seen in the unblocked visit: Comscore, Cloudflare and Google, plus 1 other. The blocking visit's engine directly blocked 4 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
Tracking companies the privacy policy does not appear to name
Comscore, Cloudflare and The Trade Desk were sent requests during this visit. However, the policy text matched none of the names this scan knows those companies by.
Policies often disclose vendor categories rather than company names, so an unnamed vendor is a transparency gap worth reviewing, not automatically a violation.Details
Named in the policy: Adobe and Google.
Policy at https://*.clevelandclinic.org/about/…; 0 checkable statements matched; 2 of 5 observed tracking companies named in the policy.
Opens the request log at its catalog-matched rows, which include the requests to the companies this card names.
Worth checking
Catalogued service domains recorded responses during this visit
Comscore, Adobe and Cloudflare, plus 2 others 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 audience measurement, analytics / advertising and web analytics. This scan could not identify 5 of the 16 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site. The role taxonomy assigns these additional services explicitly non-tracking operational, support, security, consent-management, or hosting roles: Microsoft Azure. The role taxonomy leaves at least one catalog category unclassified for these identified services and assigns none a tracking-related role, so they are not counted as tracking-related. Unclassified service: Optimizely.
40 cross-site requests across 16 third-party hosts.At or above the 75th-percentile mark for third-party domains across the 74 sites measured for this metric.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.
Google Tag Manager loaded, no Analytics request recorded
This visit contacted Google Tag Manager, but recorded no request to a Google Analytics collection host and no DoubleClick remarketing sync.
Tag Manager can fetch Google Analytics or other tags, or none; this report cannot tell which it fetched here.Details
Tag Manager is a loader.
googletagmanager.com observed; no google-analytics.com, analytics.google.com or stats.g.doubleclick.net request.Show catalog-matched requests
Worth checking
Third-party cookies were present
5 third-party cookies showed up during the visit.
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.
12 cookies total in this report.At or above the 75th-percentile mark for third-party cookies across the 74 sites measured for this metric.
Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.
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
19 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 10.5 s
Catalog match
Role
Resource types
*.clevelandclinic.org
26
No catalog match
first-party
document, font, stylesheet, script, image, xhr
assets.clevelandclinic.org
24
No catalog match
first-party
image, media, other
oc-cdn-ocprod.azureedge.net
10
Microsoft Azure: cdn / hosting
service
script, stylesheet, document
*.scorecardresearch.com
4
Comscore: audience measurement
service
script, image
*.*.*.microsoft.com
4
No catalog match
third-party
xhr
bigidcmp.cloud
3
No catalog match
third-party
script, fetch, stylesheet
api.bigidcmp.cloud
3
No catalog match
third-party
fetch
*.*.omnichannelengagementhub.com
3
No catalog match
third-party
fetch, xhr
assets.adobedtm.com
2
Adobe: analytics / advertising
service
script
*.optimizely.com
2
Optimizely: experimentation
service
script, xhr
*.invocacdn.com
2
No catalog match
third-party
script
cdn.optimizely.com
1
Optimizely: experimentation
service
script
mktdplp102cdn.azureedge.net
1
Microsoft Azure: cdn / hosting
service
script
static.cloudflareinsights.com
1
Cloudflare: web analytics
service
script
*.demdex.net
1
Adobe: analytics / advertising
service
fetch
*.cdn.optimizely.com
1
Optimizely: experimentation
service
document
www.googletagmanager.com
1
Google: analytics / tag management
service
script
*.adsrvr.org
1
The Trade Desk: advertising / demand-side platform
service
script
www.clevelandclinic.org
1
No catalog match
first-party
document
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.
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. 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 .