Site Behavior Lab

Baseline visit Older format: some facts reconstructed, descriptive only

www.ebay.com

Requested addresshttps://www.ebay.com/

Jul 21, 2026, 4:34 AM UTC

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

Evidence quality

This report is built on an incomplete visit

Incomplete evidence: evidence was cut short before completion (the Worker instrumentation could not record every request, so the request evidence is incomplete). 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

1 request in this visit matched Brave Shields filter lists.

1 request matched while loading normally. This run records no evaluated-request count, so no match ratio is stated. Matching identifies traffic the lists would target; it does not establish the purpose or payload of an individual request. 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.

1cross-site domain
7cross-site requests

Plain-Language Findings

What this visit means

Unfamiliar terms are defined in the glossary
playwright-chromium

Context

Bottom line: this visit has signals, none ranked worth checking

The scan observed signals a non-expert should not have to decode from raw request tables.

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.

11 requests observed in one controlled visit.

What was checked

Page
Requested https://www.ebay.com/; the No blocking visit landed on https://www.ebay.com/… and the Brave-list blocking visit stayed on it
When
Jul 21, 2026, 4:34 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. Both were configured to send the Global Privacy Control (GPC) signal; this report records no readback of it.
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 the Brave-list blocking visit, never submitting the form; no typing was recorded in the No blocking visit. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence in the Brave-list 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 Brave-list blocking visit only: Brave Shields matches, third-party services, named platforms, Google Analytics remarketing, advertising pixels, the consent banner and the privacy policy check.

Context

1 request matched Brave Shields filter lists

1 request 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. 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. Blocking can also prevent follow-on requests, so this number is neither a measured block count nor what a Brave visit would block.

The hand-curated service catalog separately matched 0 request rows in this visit.Show matched requests

Context

This Shields comparison is not conclusive

The "Brave-list blocking" visit reported GPC Worker capture loss, so its request evidence is incomplete. The two visits ended on different pages (https://www.ebay.com/… vs https://www.ebay.com/), so their difference is not a comparison of one page.

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.

2 disqualifying conditions named by the report's claim policy.Show matched requests

Context

No known services matched

This scan did not match any third-party domains to the service catalog or another identity source.

No known operator or catalog entity was matched. This scan could not identify 1 of the 1 third-party host recorded here, so it cannot say who operates it. That is a limit of identity coverage, not evidence about the site.

7 cross-site requests across 1 third-party host.Below the median for third-party domains across the 62 sites measured for this metric.Show third-party requests

Not flagged

No requests to catalogued major-platform domains were recorded

No requests to catalogued Google, Meta, TikTok, X, Microsoft, LinkedIn, or Pinterest domains were observed in this visit.

Major-platform domains were not observed in this single passive visit; interaction-gated requests could still load for real users.

1 cross-site domain seen overall.Show catalog-matched requests

Not flagged

No Google Analytics observed

This visit did not contact Google Analytics.

Neither Google Analytics nor its remarketing sync was observed in this visit.

No google-analytics.com, analytics.google.com or googletagmanager.com requests.Show catalog-matched requests

Not flagged

No third-party cookies observed

The automated visit did not observe third-party cookies.

This does not prove the site never uses cookies; it means this visit did not observe third-party cookies.

15 cookies total in this report.No third-party cookies 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.

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
20260721-0939ef51d787a9a482f84c99ad3e0967
Site
www.ebay.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
complete; derived from status and warnings
Scanner
playwright-chromium
Browser
149.0.7827.55
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 Worker instrumentation could not record every request, so the request evidence is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
149.0.7827.55
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 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 .