Site Behavior Lab
Site

www.medicare.gov

Baseline visit
Requested address
https://www.medicare.gov/
Report ID
20260817-f165913ad4f4b0d0f76b27e295b96384
Evidence SHA-256
0a991db40e85b174462da304cfb8cfb1f14d631509a5d0d1b88bb21c88ccb6f0
Scanner
playwright-chromium

Public corrections ledger · SBL-CORR-2026-001

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.

Read the public review record

medicare.gov recorded 103 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.medicare.gov itself56 requestsrequests that stayed on the site
Catalogued services51 requests7 names: Tealium 16, Google 13, The Trade Desk 8, New Relic 6, Magnite 4, and 2 more
Hosts the catalog does not name98 requests18 hosts; the catalog cannot say who operates them

Brave-list blocking

www.medicare.gov itself46 requestsrequests that stayed on the site
Catalogued services14 requests1 name: Tealium 14
Hosts the catalog does not name32 requests5 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
  • Checks with incomplete evidence
  • one request on record, same site
  • one request on record, cross-site
  • not measured

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

6tracking-service entities
149cross-site requests
19third-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. 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.

205 requests observed in one controlled visit.

What was checked

Page
https://www.medicare.gov/
When
Aug 17, 2026, 6:17 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 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: CNAME cloaking, the privacy policy check, fingerprinting, session-recording signals, the typing test, advertising pixels and the consent banner. Each linked card states what was retained.

Worth checking

46 requests matched Brave Shields filter lists

46 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 51 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 103 fewer third-party requests, 14 fewer third-party cookies and 31 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, The Trade Desk and Magnite, plus 2 others. The blocking visit's engine directly blocked 16 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

2 first-party DNS aliases matched tracking checks

Of the resolved targets, 2 matched Brave filter lists; those matches do not identify the operators.

These matches do not establish a request's purpose, profiling, or an intent to conceal tracking. Details

The scanner followed DNS CNAME chains from first-party subdomains and checked resolved targets against the service catalog and Brave filter lists. A filter-list match alone is not a verified service identity or proof of tracking.

DNS alias: *.medicare.gov → *.*.gov.edgekey.net (Brave filter-list match; operator unverified). DNS alias: api.medicare.gov → *.*.gov.edgekey.net (Brave filter-list match; operator unverified).Open domain evidence

Context

Tracking companies the privacy policy does not appear to name

The Trade Desk and Adobe 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: Tealium, Google and Microsoft.

Policy at https://www.medicare.gov/privacy-policy; 0 checkable statements matched; 3 of 5 observed tracking companies named in the policy. Policy mentions of Magnite 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.

Worth checking

Catalogued service domains recorded responses during this visit

Tealium, Google and The Trade Desk, plus 3 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 tag management / customer data, analytics / tag management and advertising. This scan could not identify 14 of the 31 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: New Relic.

149 cross-site requests across 31 third-party hosts. This report does not record which requests came during the typing test.At or above the 75th-percentile mark for third-party domains across the 86 sites measured for this metric. Elevated distinct tracking-service entities count (at or above the 6 reference threshold).Show third-party requests

Context

Requests were dispatched to catalogued major-platform domains

This visit dispatched requests to catalogued domains for Google and Microsoft.

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

16 requests to these platforms. This report does not record which requests came during the typing test.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

Review-worthy

Third-party cookies were present

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

48 cookies total in this report.At or above the 90th-percentile mark for third-party cookies across the 86 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.

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

34 recorded domains
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 14.1 sCatalog matchRoleResource types
www.medicare.gov31No catalog matchfirst-partydocument, script, stylesheet, image, font, xhr
*.*.qualtrics.com29No catalog matchthird-partyscript, xhr, fetch, image
apps.*.us-gov-pure.cloud24No catalog matchthird-partyscript, document, xhr
*.medicare.gov23No catalog matchfirst-partyscript, stylesheet, xhr, font, image, ping, fetch
*.cms.gov21No catalog matchthird-partydocument, script, stylesheet, image, font, ping, xhr
*.tiqcdn.com14Tealium: tag management / customer dataservicescript
*.adsrvr.org8The Trade Desk: advertising / demand-side platformserviceimage
*.*.doubleclick.net5Google: advertisingserviceimage, document
*.nr-data.net4New Relic: performance monitoringservicescript, xhr
pixel.rubiconproject.com4Magnite: advertising / supply-side platformserviceimage
www.googletagmanager.com3Google: analytics / tag managementservicescript
*.bing.com3Microsoft: advertising / analyticsservicescript, image
ads.nextdoor.com3No catalog matchthird-partyscript, fetch
*.newrelic.com2New Relic: performance monitoringservicescript
*.tealiumiq.com2Tealium: tag management / customer dataserviceimage, script
ad.doubleclick.net2Google: advertisingservicefetch
www.google-analytics.com2Google: analytics / tag managementservicefetch
events.launchdarkly.us2No catalog matchthird-partyxhr
www.youtube.com2No catalog matchthird-partyscript
*.digitalgov.gov2No catalog matchthird-partyscript
cdn1.adoberesources.net2No catalog matchthird-partyscript
analytics-sm.com2No catalog matchthird-partyscript, image
*.*.us-gov-pure.cloud2No catalog matchthird-partyxhr
*.adobedc.net2No catalog matchthird-partyfetch
api.medicare.gov2No catalog matchfirst-partyxhr, ping
*.demdex.net1Adobe: analytics / advertisingservicefetch
*.google.com1Google: advertisingserviceimage
*.launchdarkly.us1No catalog matchthird-partyxhr
*.*.*.qualtrics.com1No catalog matchthird-partyscript
www.google.com1No catalog matchthird-partyfetch

+4 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
20260817-f165913ad4f4b0d0f76b27e295b96384
Site
www.medicare.gov
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
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. 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 .