Site

www.psychologytoday.com

Baseline visit
Requested address
https://www.psychologytoday.com/
Report ID
20260928-1a4bcb79fa9e31af2ccca4fae85c0033
Evidence SHA-256
64d5b2fc0da2a6eae9adc200ac038e6465e5512382028c1338233049f774493c
Scanner
playwright-chromium

psychologytoday.com recorded 84 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.psychologytoday.com itself61 requestsrequests that stayed on the site
Catalogued services44 requests3 names: Google 36, Comscore 4, DoubleVerify 4
Hosts the catalog does not name40 requests9 hosts; the catalog cannot say who operates them

Brave-list blocking

www.psychologytoday.com itself61 requestsrequests that stayed on the site
Catalogued services0 requestsno retained request matched the service catalog
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
  • Checks with incomplete evidence
  • one request on record, same site
  • one request on record, cross-site
  • not measured

The visit with no blocking made 145 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 84 fewer third-party requests. The blocker directly stopped 2 requests; the remaining difference may include follow-on requests that never started once their sources were blocked, plus run-to-run variance.

3tracking-service entities
84cross-site requests
3third-party cookie records

Worth checking

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.

145 requests observed in one controlled visit.

What was checked

Page
Requested https://www.psychologytoday.com/; both visits landed on https://www.psychologytoday.com/us
When
Sep 28, 2026, 11:55 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
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, but some evidence 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 both visits: the typing test.

Worth checking

54 requests matched Brave Shields filter lists

54 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 44 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 84 fewer third-party requests, 3 fewer third-party cookies and 44 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, Comscore and DoubleVerify. The blocking visit's engine directly blocked 2 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

DoubleVerify 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 Comscore.

Policy at https://docs.psychologytoday.com/…/privacy-policy/en/…; 0 checkable statements matched; 2 of 3 observed tracking companies named in the policy.

Worth checking

Catalogued service domains recorded responses during this visit

Google, Comscore and DoubleVerify 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 advertising, analytics / tag management and audience measurement. This scan could not identify 5 of the 17 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.

84 cross-site requests across 17 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.

The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.

36 requests to these platforms.Show catalog-matched requests

Context

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.

Google Analytics host observed; DoubleClick hosts recorded under generalized names.Show catalog-matched requests

Context

Third-party cookies were present

3 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.

10 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: 22 interaction-listener registrations with https://cdn-cookieyes.com/, https://cdn.doubleverify.com/ and https://*.*.doubleclick.net/, plus 1 other in the registration call chain. Input-monitoring listener coverage: 7 input-listener registrations with https://cdn-cookieyes.com/, https://cdn.doubleverify.com/ and https://*.*.doubleclick.net/, plus 1 other in the registration 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.

Scan report ready for www.psychologytoday.com: 145 recorded request rows.

Comparison ReportOlder format: some facts reconstructed, descriptive only

Brave-list blocking off/on comparison

Recorded final address https://www.psychologytoday.com/us (opens in a new tab)
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, 11:55 AM UTC · 6,997msBrave-list blocking: started Sep 28, 2026, 11:55 AM UTC · 5,443msRan 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.
Requests-84No blocking: 145 · Brave-list blocking: 61
Third-party requests-84No blocking: 84 · Brave-list blocking: 0
Third-party domains-17No blocking: 17 · Brave-list blocking: 0
Cookies-9No blocking: 10 · Brave-list blocking: 1
Third-party cookies-3No blocking: 3 · Brave-list blocking: 0
Storage keys-3No blocking: 3 · Brave-list blocking: 0
Catalog-matched requests-44No blocking: 44 · Brave-list blocking: 0

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.

Largest per-domain request-count changes

*.googlesyndication.comGoogle · advertisingNo blocking: 18 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-18
*.*.doubleclick.netGoogle · advertisingNo blocking: 12 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-12
*.adtrafficquality.googleunlabeled third partyNo blocking: 9 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-9
cdn-cookieyes.comunlabeled third partyNo blocking: 9 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-9
apps.healthgrades.comunlabeled third partyNo blocking: 6 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-6
*.2mdn.netunlabeled third partyNo blocking: 5 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-5
*.healthgrades.comunlabeled third partyNo blocking: 4 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-4
*.scorecardresearch.comComscore · audience measurementNo blocking: 4 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-4
*.*.googlesyndication.comGoogle · advertisingNo blocking: 3 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-3
*.cookieyes.comunlabeled third partyNo blocking: 2 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-2
*.doubleverify.comDoubleVerify · advertising measurement / verificationNo blocking: 2 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-2
*.gstatic.comunlabeled third partyNo blocking: 2 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-2
cdn.doubleverify.comDoubleVerify · advertising measurement / verificationNo blocking: 2 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-2
www.google.comunlabeled third partyNo blocking: 2 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-2
www.googletagmanager.comGoogle · analytics / tag managementNo blocking: 2 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-2
analytics.google.comGoogle · analytics / tag managementNo blocking: 1 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-1
fonts.googleapis.comunlabeled third partyNo blocking: 1 · Brave-list blocking: 0Show No blocking requests · Show Brave-list blocking requests-1

Domains only with Brave-list blocking

No domain changes observed.

Domains only with No blocking

*.googlesyndication.comGoogle · advertising · Show No blocking requests18
*.*.doubleclick.netGoogle · advertising · Show No blocking requests12
*.adtrafficquality.googleunlabeled · Show No blocking requests9
cdn-cookieyes.comunlabeled · Show No blocking requests9
apps.healthgrades.comunlabeled · Show No blocking requests6
*.2mdn.netunlabeled · Show No blocking requests5
*.healthgrades.comunlabeled · Show No blocking requests4
*.scorecardresearch.comComscore · audience measurement · Show No blocking requests4
*.*.googlesyndication.comGoogle · advertising · Show No blocking requests3
*.cookieyes.comunlabeled · Show No blocking requests2
*.doubleverify.comDoubleVerify · advertising measurement / verification · Show No blocking requests2
*.gstatic.comunlabeled · Show No blocking requests2
cdn.doubleverify.comDoubleVerify · advertising measurement / verification · Show No blocking requests2
www.google.comunlabeled · Show No blocking requests2
www.googletagmanager.comGoogle · analytics / tag management · Show No blocking requests2
analytics.google.comGoogle · analytics / tag management · Show No blocking requests1
fonts.googleapis.comunlabeled · Show No blocking requests1

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

IDE.doubleclick.netthird-party
_ga.psychologytoday.comfirst-party

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

Google5 domains36
Comscore1 domain4
DoubleVerify2 domains4

Measurement limits

8 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.
  • The synthetic form-input probe did not complete its test, so input-capture conclusions for this visit are incomplete.
  • 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.
  • Read the site's privacy policy (https://docs.psychologytoday.com/{seg}/privacy-policy/en/{seg}) 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.

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.

Report ID
20260928-1a4bcb79fa9e31af2ccca4fae85c0033
Site
www.psychologytoday.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; 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.

Variant visit

Started
Run quality
cut short: the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; 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 .