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 150 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 26 fewer third-party requests. The blocker directly stopped 24 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.
150 requests observed in one controlled visit.
What was checked
Page
https://www.duolingo.com/
When
Sep 28, 2026, 11:57 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.
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
28 requests matched Brave Shields filter lists
28 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 15 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 26 fewer third-party requests, 2 fewer third-party cookies and 15 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, Meta and Media.net. The blocking visit's engine directly blocked 24 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
www.duolingo.com sent a request to OneTrust, a consent management platform (the tooling that shows cookie banners). The request log included 3 distinct catalogued tracking-related services before the scanner made any consent choice; 3 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 cdn.cookielaw.org.
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
Media.net was sent requests during this visit. However, the policy text matched none of the names this scan knows that company 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 and Meta.
Policy at https://www.duolingo.com/privacy; 0 checkable statements matched; 2 of 3 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, Meta and Media.net 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 4 of the 18 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.
135 cross-site requests across 18 third-party hosts.At or above the 75th-percentile mark for third-party domains across the 85 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 and Meta.
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.
18 cookies total in this report.At or above the median for third-party cookies across the 85 sites measured for this metric.
Context
Input-monitoring signal involving a third-party script
Listener coverage that could observe typing-related input events was registered through call chains that included a third-party script.
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: 95 interaction-listener registrations with https://*.tupsrv.com/, https://cdn.cookielaw.org/ and https://*.facebook.net/, plus 3 others in the registration call chain. Input-monitoring listener coverage: 35 input-listener registrations with https://*.tupsrv.com/, https://d35aaqx5ub95lt.cloudfront.net/ and https://www.googletagmanager.com/, plus 1 other in the registration call chain.
Opens this report's request log filtered to *.tupsrv.com, a script origin recorded in the listener's call chain.
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
20 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.6 s
Catalog match
Role
Resource types
d35aaqx5ub95lt.cloudfront.net
96
No catalog match
third-party
script, stylesheet, font, fetch, image
*.duolingo.com
9
No catalog match
first-party
fetch, xhr
www.duolingo.com
6
No catalog match
first-party
document, fetch
cdn.cookielaw.org
5
No catalog match
third-party
script, xhr, fetch
www.gstatic.com
5
No catalog match
third-party
script, stylesheet, image, other
www.googletagmanager.com
4
Google: analytics / tag management
service
script
*.*.doubleclick.net
3
Google: advertising
service
ping, script, fetch
www.recaptcha.net
3
No catalog match
third-party
script, document
*.tupsrv.com
3
No catalog match
third-party
script, image
www.google.com
3
No catalog match
third-party
fetch, image
www.google-analytics.com
2
Google: analytics / tag management
service
script, xhr
*.facebook.net
2
Meta: social / advertising pixel
service
script
accounts.google.com
2
No catalog match
third-party
script, stylesheet
analytics.google.com
1
Google: analytics / tag management
service
fetch
ad.doubleclick.net
1
Google: advertising
service
fetch
*.media.net
1
Media.net: advertising
service
image
www.googleadservices.com
1
Google: advertising
service
fetch
*.onetrust.com
1
No catalog match
third-party
xhr
*.gstatic.com
1
No catalog match
third-party
font
analytics.tupsrv.com
1
No catalog match
third-party
script
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
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.
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 .