Incomplete evidence: evidence was cut short before completion (the visit hit the scanner's request-recording cap, so its counts are truncated). Counts for the affected evidence are lower bounds; families that completed carry only their ordinary limits. The evidence receipt states the exact per-visit quality.
What this actually means
webmd.com's retained request log includes catalogued Google and LinkedIn domains.
Retained request rows include 21 distinct catalogued tracking-service entities; 21 of the retained service matches recorded responses across at least 151 retained cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. It also looks like keyboard-input listeners were registered through a call chain that included a cross-site script.
The scan observed signals a non-expert should not have to decode from raw request tables. Some activity evidence was also incomplete: request counts are retained lower bounds, cookie counts are an incomplete end-state snapshot and storage counts are an incomplete end-state snapshot.
The cards below translate the evidence into plain language. This failed or incomplete evidence is not ranked against corpus percentiles; positive signals remain visible as lower bounds. The request log, domain table, and methodology remain below for verification.
at least 1,000 retained requests observed in one controlled visit.
Worth checking
at least 550 retained requests matched Brave Shields filter lists
at least 550 retained requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.
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. Matching shows what Shields would target on this visit's traffic; an actual Shields visit blocks these and also prevents their follow-on requests, so this number is neither a measured block count nor the total effect.
The hand-curated service catalog separately matched at least 414 retained request rows in this visit.Show matched requests
Context
This Shields comparison is not conclusive
The "No blocking" visit hit the 1,000-request recording cap, so its counts are truncated.
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.
Recorded DNS aliases resolve to catalogued tracking-related services: Adobe.
The scanner followed DNS CNAME chains from first-party subdomains and checked resolved targets against the service catalog and Brave filter lists. These matches do not establish a request's purpose, profiling, or an intent to conceal tracking. A filter-list match alone is not a verified service identity or proof of tracking.
Consent tooling and requests to tracking-service entities appeared before any choice
www.webmd.com sent a request to OneTrust, a consent management platform (the tooling that shows cookie banners), and the request log included at least 21 retained distinct catalogued tracking-related services before the scanner made any consent choice; 21 companies answered.
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. It does not determine whether any request required consent or whether the site's behavior complied with applicable law. 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.
Review-worthy
Catalogued service domains recorded responses during this visit
Google, PubMatic and DoubleVerify, plus 18 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. Functional catalog labels include advertising, analytics / tag management and advertising / supply-side platform. This scan could not identify 109 of the 151 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.
at least 976 retained cross-site requests across at least 151 retained third-party hosts.Show third-party requests
Context
Requests were dispatched to catalogued major-platform domains
This visit dispatched requests to catalogued domains for Google and LinkedIn.
The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.
Incomplete evidence: Google Analytics present, no remarketing signal in retained evidence before collection stopped
Google Analytics was observed, but no DoubleClick remarketing sync appeared in this visit.
Standard analytics collection was observed, without the stats.g.doubleclick.net advertising sync. Evidence collection was cut short, so this covers only what was recorded before the cutoff.
244 third-party cookies showed up during the visit.
The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary. 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.
286 cookies total in this report.
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. 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, 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, so the card 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.
242 interaction-listener registrations with https://cdn.cookielaw.org/, https://cdn.doubleverify.com/ and https://d15kdpgjg3unno.cloudfront.net/, plus 6 others in the registration call chain and 58 input-listener registrations with https://cdn.cookielaw.org/, https://cdn.doubleverify.com/ and https://img.*.wbmdstatic.com/, plus 3 others in the registration call chain
Context
Fingerprint-like browser APIs were called
At least 2 retained high-entropy API calls appeared in the incomplete instrumentation log.
These calls can be legitimate (charts, graphics, media), so the count is observational, not a severity score, and it excludes Web and Service Workers. Top calls: webgl.getParameter.UNMASKED_RENDERER_WEBGL.
Retained incomplete evidence includes 1 API event record; no exact API-family total is available.
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 visit hit the scanner's request-recording cap, so its counts are truncated; 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. 16 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 13 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.
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 .