Site

www.discover.com

Baseline visit
Requested address
https://www.discover.com/
Report ID
20261118-0ca821139a11d6babfa1b3cb9bcaed85
Evidence SHA-256
1295fbfbda7293ad7e61d6c0aa0567d0a0cafbbe49ee4fab7b9d21adbb688e72
Scanner
playwright-chromium

discover.com's retained request log includes catalogued Google, Microsoft and Meta domains.

Where this page's requests went

The No blocking visit. One mark is one request row in the retained log.

www.discover.com itselfat least 71 retained requestsrequests that stayed on the site
Catalogued servicesat least 26 retained requests5 names: Google 17, Adobe 3, Microsoft 3, Meta 2, Datadog 1
Hosts the catalog does not nameat least 27 retained requests10 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
  • the count is a lower bound; more may exist
  • not measured

Retained request rows include 4 distinct catalogued tracking-service entities; 4 of the retained service matches recorded responses across at least 20 retained cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. In the visit labeled No blocking, it also looks like keyboard-input listeners were registered through a call chain that included a cross-site script and 5 browser-fingerprinting heuristics matched.

≥4tracking-service entities retained
≥53cross-site requests
7third-party cookie records
≥5fingerprint-like patterns retained

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 activity evidence was also incomplete: request counts are retained lower bounds.

This failed or incomplete evidence is not ranked against corpus percentiles; positive signals remain visible as lower bounds. Details

The cards below translate the evidence into plain language. The request log, domain table, and methodology remain below for verification.

At least 124 retained requests observed in one controlled visit.

What was checked

Page
https://www.discover.com/
When
Nov 18, 2026, 6:04 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 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, 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.
  • 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: every check except third-party cookies and storage. The cards for the incomplete checks state only what was retained.

Worth checking

At least 73 retained requests matched Brave Shields filter lists

At least 73 retained 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 at least 26 retained request rows in this visit.Show matched requests

Context

This Shields comparison is not conclusive

The "No blocking" visit had one or more requests refused by the scanner's own network guard, so its request evidence is incomplete.

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.Show matched requests

Worth checking

2 first-party DNS aliases matched tracking checks

Recorded DNS aliases resolve to catalogued tracking-related services: Adobe. Of the resolved targets, 1 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: *.discover.com → *.online-metrix.net (Brave filter-list match; operator unverified). DNS alias: *.discover.com → *.*.*.*.*.omtrdc.net (Adobe; catalog match).Open domain evidence

Worth checking

Catalogued service domains recorded responses during this visit

Google, Adobe and Microsoft, plus 1 other 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 analytics / advertising. This scan could not identify 9 of the 20 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: Datadog.

At least 53 retained cross-site requests across at least 20 retained third-party hosts.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 Microsoft.

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

At least 22 retained 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

Worth checking

Third-party cookies were present

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

30 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. 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: 27 interaction-listener registrations with https://assets.adobedtm.com/, https://cdn.branch.io/ and https://*.facebook.net/, plus 3 others in the registration call chain. Input-monitoring listener coverage: 6 input-listener registrations with https://*.go-mpulse.net/, https://www.datadoghq-browser-agent.com/ and https://www.googletagmanager.com/ in the registration call chain.

Worth checking

Behavioral fingerprinting heuristics matched

At least 5 behavioral heuristics matched in retained evidence: Canvas fingerprinting heuristic, Offline audio rendering heuristic, WebRTC peer-connection probing, Canvas font probing heuristic and WebGL entropy-read heuristic.

They are review prompts for this visit, not proof of cross-site identity tracking. Details

These heuristics look for behavior patterns such as canvas readback after drawing, repeated canvas font measurement, WebGL entropy reads, offline audio rendering, or WebRTC peer-connection setup.

Canvas fingerprinting heuristic: 7 canvases matched; reads: canvas.getImageData and canvas.toDataURL. Offline audio rendering heuristic: 2 offline renders with audio.OfflineAudioContext.createAnalyser, audio.OfflineAudioContext.createDynamicsCompressor and audio.OfflineAudioContext.createOscillator, plus 2 others. WebRTC peer-connection probing: 2 peer connections with 2 data channels, 2 offers, and 2 local descriptions. Canvas font probing heuristic: 11 measureText calls across up to 11 fonts; measured text contents are not stored. Plus 1 other detection.

Scan report ready for www.discover.com: 124 recorded request rows.

Comparison ReportOlder format: some facts reconstructed, descriptive onlyrequest evidence incomplete

Brave-list blocking off/on comparison

Recorded final address https://www.discover.com/ (opens in a new tab)

The selected visit did not finish collecting request evidence. Request counts are lower bounds; Run quality records the reason.

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 and Brave-list blocking: two visits, no comparable metric delta

No blocking: started Nov 18, 2026, 6:04 PM UTC · 13,294msBrave-list blocking: started Nov 18, 2026, 6:04 PM UTC · 6,326msRan first: No blocking
These two visits do not support a side-by-side comparison, so no deltas are shown.
  • The "No blocking" visit had one or more requests refused by the scanner's own network guard, so its request evidence is incomplete.

Each visit's own evidence still stands: use the “Evidence shown” switcher below to inspect either visit's tables, and both visits are in the downloaded JSON.

Measurement limits

10 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 "No 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.

No blocking visit only

  • Blocked a request that could not be verified as public: https://{label}.{label}.{label}.online-metrix.net/{seg}
  • The page did not reach network idle before the scan window ended.
  • The in-page fingerprint observer read every frame, but one or more measured more canvas text or fonts than it keeps, so canvas font fingerprinting findings for this visit are incomplete.
  • The page started 1 shared worker that ended within 10 ms, before the fingerprint observer could reach it, so whether it ran any code is not known.
  • Resolved 2 first-party subdomains that are CNAME aliases for third-party trackers (CNAME cloaking), which request-URL matching alone would miss.

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
20261118-0ca821139a11d6babfa1b3cb9bcaed85
Site
www.discover.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the scanner's own network guard refused one or more requests, which were never sent and have no row, so the request evidence is incomplete; one or more frames measured more canvas text or fonts than the in-page fingerprint observer keeps, so the fingerprinting evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
159.0.8154.6
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
159.0.8154.6
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 .