Site Behavior Lab
Site

healthline.com

Baseline visit
Requested address
https://www.healthline.com/
Report ID
20260814-58c31f5f092ed56ce3b24ccafaf6a8e6
Evidence SHA-256
50d19bf0662bfd342ca9c8f1f9dd07a5231acffa69bd5e56fe29284fbb190f3c
Scanner
playwright-chromium

Public corrections ledger · SBL-CORR-2026-002

This report has a reviewed clarification

SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.

SBL-CORR-2026-002: The policy entity matcher did not recognize Amazon and Oracle under their catalog names. An unmentioned-entity result for Amazon Ads or Oracle Advertising is not reliable evidence that the policy omitted the company. Original policy text was not retained, so individual mention results cannot be reconstructed. Consult all clarification events for this report.

Read the public review record

healthline.com contacted catalogued Google, TikTok and Microsoft, +2 more domains during the visit labeled GPC off.

Where this page's requests went

Both visits. One mark is one request row in the retained log.

GPC off

healthline.com itself43 requestsrequests that stayed on the site
Catalogued services48 requests11 names: Google 9, TikTok 7, Microsoft Clarity 6, Comscore 4, LiveRamp 4, and 6 more
Hosts the catalog does not name134 requests37 hosts; the catalog cannot say who operates them

GPC on

healthline.com itself82 requestsrequests that stayed on the site
Catalogued services14 requests3 names: Google 8, Amazon Ads 3, DoubleVerify 3
Hosts the catalog does not name148 requests16 hosts; the catalog cannot say who operates them
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

11 distinct catalogued tracking-service entities recorded responses across 54 cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. In the visit labeled GPC off, it also looks like keyboard-input listeners were registered through a call chain that included a cross-site script. SBL-CORR-2026-002: The policy entity matcher did not recognize Amazon and Oracle under their catalog names. An unmentioned-entity result for Amazon Ads or Oracle Advertising is not reliable evidence that the policy omitted the company. Original policy text was not retained, so individual mention results cannot be reconstructed. Consult all clarification events for this report.

11tracking-service entities
182cross-site requests
17third-party cookie records

Review-worthy

Bottom line: this visit has review-worthy signals

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.

225 requests observed in one controlled visit.

What was checked

Page
https://www.healthline.com/
When
Aug 14, 2026, 7:01 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 scanner host the report does not name; the network region was not recorded.
Visits
Two visits configured to differ in the Global Privacy Control (GPC) signal: GPC off and GPC on.
Interactions
Typed a made-up test value into 2 form fields in each visit, never submitting the form. 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

103 of 196 requests the engine evaluated matched Brave Shields filter lists

103 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 48 request rows in this visit.Show matched requests

Context

This GPC comparison supports no comparable delta

The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching.

The raw request logs of both visits remain below for transparency, but the diff between them supports no claim about what the compared condition changed.

1 disqualifying condition named by the report's claim policy.

Context

Tracking companies the privacy policy does not appear to name

TikTok, Comscore and Microsoft, plus 3 others 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, LiveRamp and Meta.

Policy at https://www.healthline.com/about/…; 0 checkable statements matched; 3 of 9 observed tracking companies named in the policy. Policy mentions of Microsoft Clarity and Amazon Ads are unknown because the historical alias matcher was incomplete.

Look closer

Show catalog-matched requests

Opens the request log at its catalog-matched rows, which include the requests to the companies this card names.

Review-worthy

Catalogued service domains recorded responses during this visit

Google, TikTok and Microsoft Clarity, plus 8 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 advertising, analytics / tag management and social / advertising pixel. This scan could not identify 33 of the 54 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site. Catalog labels include session-replay or behavior-analytics services: Microsoft Clarity. The domain match alone does not prove that a recording occurred.

182 cross-site requests across 54 third-party hosts.At or above the 90th-percentile mark for third-party domains across the 51 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 TikTok, plus 2 others.

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

26 requests to these platforms.Show catalog-matched requests

Context

Advertising pixel requests contained event labels

TikTok Pixel requests contained event labels during this visit.

Event labels do not establish user actions or successful delivery. Details

No advanced-matching identifier fields are recorded in the decoded evidence. Unsupported payload formats and later interactions may carry other fields; older decoders did not record every decoding gap.

TikTok Pixel: custom event and Pageview (3 requests).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

Worth checking

Third-party cookies were present

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

59 cookies total in this report.At or above the 75th-percentile mark for third-party cookies across the 51 sites measured for this metric.

Look closer

See other visits' cookie counts

Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.

Worth checking

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: 32 interaction-listener registrations with https://analytics.tiktok.com/, https://cdn.cookielaw.org/ and https://*.facebook.net/, plus 3 others in the registration call chain. Input-monitoring listener coverage: 6 input-listener registrations with https://*.adspsp.com/, https://*.pinimg.com/ and https://*.qualtrics.com/ in the registration call chain. Known session-replay vendor(s): Microsoft Clarity.

Look closer

Show requests to Microsoft Clarity

Opens this report's request log filtered to Microsoft Clarity; listener registrations are not request rows, so the log cannot show what was observed.

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

57 recorded domains
The busiest recorded domains of the GPC off visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 13.5 sCatalog matchRoleResource types
media.*.rvohealth.io38No catalog matchthird-partyimage
assets.healthline.com30No catalog matchfirst-partyscript, font, image
*.*.rvohealth.com16No catalog matchthird-partyxhr
cdn.cookielaw.org8No catalog matchthird-partyscript, xhr, fetch, image
*.healthline.com8No catalog matchfirst-partyscript, fetch, document, image, ping
analytics.tiktok.com7TikTok: social / advertising pixelservicescript, ping
*.hcn.health7No catalog matchthird-partyscript, document, xhr, image
*.clarity.ms5Microsoft Clarity: session replay / behavior analyticsservicescript, image, xhr
cdn.rvohealth.com5No catalog matchthird-partyscript, xhr, document
id5-sync.com5No catalog matchthird-partyfetch, xhr, image
www.healthline.com5No catalog matchfirst-partydocument, fetch, image, font
*.*.doubleclick.net4Google: advertisingservicescript, other, image
*.scorecardresearch.com4Comscore: audience measurementservicescript, image
*.bing.com4Microsoft: advertising / analyticsservicescript, image
*.pinterest.com4Pinterest: social / advertising pixelservicexhr, fetch, document
*.adspsp.com4No catalog matchthird-partyscript, fetch
ad-delivery.net4No catalog matchthird-partyimage, fetch
*.qualtrics.com4No catalog matchthird-partyscript, xhr
*.doubleverify.com3DoubleVerify: advertising measurement / verificationservicescript, fetch
*.33across.com3No catalog matchthird-partyscript, xhr, fetch
*.eu-1-id5-sync.com3No catalog matchthird-partyfetch
*.lhmos.com3No catalog matchthird-partyscript, image, fetch
*.*.amazon-adsystem.com2Amazon Ads: advertisingservicescript
www.googletagmanager.com2Google: analytics / tag managementservicescript, image
ad.doubleclick.net2Google: advertisingserviceimage, fetch
api.rlcdn.com2LiveRamp: identity / advertisingservicefetch, xhr
*.adsrvr.org2The Trade Desk: advertising / demand-side platformservicefetch, xhr
*.rlcdn.com2LiveRamp: identity / advertisingserviceimage
*.facebook.net2Meta: social / advertising pixelservicescript
cdn.btmessage.com2No catalog matchthird-partyscript, document

+27 more in the evidence explorer below.

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.

Report ID
20260814-58c31f5f092ed56ce3b24ccafaf6a8e6
Site
healthline.com
Latest visit
Schema
v2 schema (r2)
Verify recorded provenance

Baseline visit

Started
Run quality
complete; recorded by the scanner
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1
Detector registry
node-detectors-v4100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2
Tracker catalog digest
e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f4
Brave-list instrument
engine adblock-rust-0.13.20f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0ac
Normalization
redaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1

Variant visit

Started
Run quality
complete; recorded by the scanner
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1
Detector registry
node-detectors-v4100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2
Tracker catalog digest
e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f4
Brave-list instrument
engine adblock-rust-0.13.20f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0ac
Normalization
redaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1

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