robinhood.com recorded 63 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
robinhood.com itself29 requestsrequests that stayed on the site
00000000000000000000000000000
Catalogued services41 requests5 names: Google 17, Sentry 9, LinkedIn 7, Microsoft 6, Meta 2
00000000000000000000000000000000000000000
Hosts the catalog does not name39 requests12 hosts; the catalog cannot say who operates them
000000000000000000000000000000000000000
Brave-list blocking
robinhood.com itself29 requestsrequests that stayed on the site
00000000000000000000000000000
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name17 requests3 hosts; the catalog cannot say who operates them
00000000000000000
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
The visit with no blocking made 109 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 63 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. 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.
109 requests observed in one controlled visit.
What was checked
Page
Requested https://robinhood.com/; both visits landed on https://robinhood.com/us/en
When
Aug 10, 2026, 6:51 AM 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, but some evidence in the No blocking visit 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 the No blocking visit only: the consent banner, the privacy policy check, fingerprinting, session-recording signals, the typing test, CNAME cloaking and advertising pixels. Each linked card states what was retained.
Worth checking
60 requests matched Brave Shields filter lists
60 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 41 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 63 fewer third-party requests, 9 fewer third-party cookies and 32 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, LinkedIn and Microsoft, 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
Worth checking
Consent tooling and requests to tracking-service entities appeared before any choice
robinhood.com sent a request to Usercentrics, a consent management platform (the tooling that shows cookie banners). The request log included 4 distinct catalogued tracking-related services before the scanner made any consent choice; 4 companies answered.
It does not determine whether any request required consent or whether the site's behavior complied with applicable law.Details
A request to the platform's loader proves the page attempted to fetch consent tooling. An observed response supports delivery, but neither fact proves a banner was visibly shown to this scanner. 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. 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 api.usercentrics.eu.
Opens the request log at its catalog-matched rows, which include requests to the tracking-related services counted here; this visit never clicked the banner.
Context
Tracking companies the privacy policy does not appear to name
LinkedIn, Microsoft and Meta 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: Google.
Policy at https://robinhood.com/us/en/support/articles/privacy-policy; 0 checkable statements matched; 1 of 4 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
Google, LinkedIn and Microsoft, plus 1 other 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, advertising and social / advertising pixel. This scan could not identify 7 of the 25 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: Sentry.
80 cross-site requests across 25 third-party hosts.At or above the 75th-percentile mark for third-party domains across the 86 sites measured for this metric.Show third-party requests
Worth checking
Requests were dispatched to catalogued major-platform domains
This visit dispatched requests to catalogued domains for Google, Meta and Microsoft, plus 1 other.
The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.
Google Analytics present; a remarketing sync cannot be told from this report
Google Analytics was observed, with requests to DoubleClick hosts whose names this report generalizes. The remarketing sync host is one such name, so the sync cannot be told apart from them.
This report neither shows nor rules out the sync.Details
The sync goes to stats.g.doubleclick.net, and a published report writes that name the same way as DoubleClick's ad-serving hosts.
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.
22 cookies total in this report.At or above the 75th-percentile mark for third-party cookies across the 86 sites measured for this metric.
Context
Incomplete evidence: No fingerprint-like API calls observed in retained evidence before collection stopped
The retained evidence holds no calls to the instrumented high-entropy browser APIs.
Evidence collection was cut short, so this covers only what was recorded before the cutoff.Details
This is an observation layer, not proof that fingerprinting is impossible.
Retained incomplete evidence includes 0 API event records; no exact API-family total is available.
Domain evidence
28 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 9.5 s
Catalog match
Role
Resource types
cdn.robinhood.com
24
No catalog match
first-party
font, script, image
images.ctfassets.net
12
No catalog match
third-party
image
www.google.com
7
No catalog match
third-party
fetch, image
www.googletagmanager.com
6
Google: analytics / tag management
service
script
*.bing.com
6
Microsoft: advertising / analytics
service
script, image, xhr
*.*.doubleclick.net
5
Google: advertising
service
xhr, script, document
*.*.sentry.io
4
Sentry: error monitoring
service
other
*.*.*.sentry.io
4
Sentry: error monitoring
service
other
*.ads.linkedin.com
4
LinkedIn: social / advertising pixel
service
fetch, xhr, image
*.ctfassets.net
4
No catalog match
third-party
media
api.usercentrics.eu
4
No catalog match
third-party
fetch
robinhood.com
4
No catalog match
first-party
document, fetch
www.google-analytics.com
3
Google: analytics / tag management
service
script, xhr, fetch
*.singular.net
3
No catalog match
third-party
script, xhr
*.facebook.net
2
Meta: social / advertising pixel
service
script
*.licdn.com
2
LinkedIn: social / advertising pixel
service
script
ad.doubleclick.net
2
Google: advertising
service
fetch
app.usercentrics.eu
2
No catalog match
third-party
document, image
*.*.tvsquared.com
2
No catalog match
third-party
script, image
sentry.io
1
Sentry: error monitoring
service
fetch
*.google.com
1
Google: advertising
service
image
www.linkedin.com
1
LinkedIn: social / advertising pixel
service
image
*.ninetailed.co
1
No catalog match
third-party
fetch
*.*.usercentrics.eu
1
No catalog match
third-party
fetch
*.*.*.usercentrics.eu
1
No catalog match
third-party
fetch
www.redditstatic.com
1
No catalog match
third-party
script
*.reddit.com
1
No catalog match
third-party
image
*.robinhood.com
1
No catalog match
first-party
fetch
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 in-page fingerprint observer could not read every frame, so the fingerprinting evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
not recorded by this schema
Provenance
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
151.0.7922.34
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.
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.
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 .