Baseline visit v1 schema · facts legacy-derived · descriptive report

www.costco.com

Requested addresshttps://www.costco.com/

Sep 28, 2026, 12:04 PM UTC

cut short: the synthetic form-input probe stopped one or more navigations started while it ran, so the request evidence is incomplete; the in-page fingerprint observer could not attribute every event listener to the script that registered it, so the fingerprinting evidence is incomplete; the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; derived from status and warnings

Evidence quality

This report is built on an incomplete visit

Incomplete evidence: evidence was cut short before completion (the synthetic form-input probe stopped one or more navigations started while it ran, so the request evidence is incomplete; the in-page fingerprint observer could not attribute every event listener to the script that registered it, so the fingerprinting evidence is incomplete; and 2 more). 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.

Scan report ready for www.costco.com: 643 recorded request rows.

Comparison Reportv1 schema · facts legacy-derived · descriptive reportrequest evidence incomplete

Brave-list blocking off/on comparison

Recorded final address https://www.costco.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.

What this actually means

costco.com sent synthetic form input to 1 cross-site domain before submission.

The scanner's unique test value appeared in requests to *.*.dynatrace.com without form submission. The report does not establish whether transmission happened during typing, blur, or unload, why it was sent, or whether real visitor input follows the same path.

≥2tracking-service entities retained
≥102cross-site requests
1third-party cookie record

Plain-Language Findings

What this visit means

Unfamiliar terms are defined in the glossary
playwright-chromium

Worth checking

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

The cards below translate the evidence into plain language; severity reflects fixed reference thresholds, not measured population percentiles. The request log, domain table, and methodology remain below for verification.

at least 643 retained requests observed in one controlled visit.

Worth checking

at least 93 retained requests matched Brave Shields filter lists

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

Context

This Shields comparison is not conclusive

The "No blocking" visit's synthetic form-input probe stopped one or more navigations, 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

Synthetic form input reached 1 cross-site domain before submission

When the scanner typed a unique test value into 2 form fields, that value appeared in requests to {label}.{label}.dynatrace.com (plain) without the form being submitted.

The synthetic value appeared in a recoverable form (plain). The report does not establish whether transmission happened during typing, blur, or unload, why it was sent, or whether real visitor input follows the same path. The scanner types only synthetic values and never submits the form.

Synthetic test value appeared in requests to {label}.{label}.dynatrace.com via plain.

Worth checking

2 first-party DNS aliases matched tracking checks

Recorded DNS aliases resolve to catalogued tracking-related services: Adobe. 1 resolved target matched Brave filter lists; those matches do not identify the operators.

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.

{label}.costco.com → cloud-cdn.co (Brave filter-list match; operator unverified) and {label}.costco.com → {label}.{label}.{label}.{label}.omtrdc.net (Adobe; catalog match)Open domain evidence

Context

Tracking companies the privacy policy does not appear to name

Criteo and Adobe were sent requests during this visit, but 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.

Policy at https://www.costco.com/{seg}/{seg}/privacy-policy; 0 checkable statements matched; 0 of 2 observed tracking companies named in the policy.

Worth checking

Catalogued service domains recorded responses during this visit

Criteo and Adobe 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 and analytics / advertising. This scan could not identify 10 of the 15 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 102 retained cross-site requests across at least 15 retained third-party hosts.Show third-party requests

Context

Incomplete evidence: No requests to major-platform domains were recorded in retained evidence before collection stopped

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. Evidence collection was cut short, so this covers only what was recorded before the cutoff.

at least 15 retained cross-site domains seen overall.Show catalog-matched requests

Context

Incomplete evidence: No Google Analytics observed in retained evidence before collection stopped

This visit did not contact Google Analytics.

Neither Google Analytics nor its remarketing sync was observed in this visit. Evidence collection was cut short, so this covers only what was recorded before the cutoff.

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

Context

Third-party cookies were present

1 third-party cookie 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.

24 cookies total in this report.

Context

Incomplete evidence: No fingerprint-like API calls observed in retained evidence before collection stopped

The scan did not observe the instrumented high-entropy browser APIs.

This is an observation layer, not proof that fingerprinting is impossible. Evidence collection was cut short, so this covers only what was recorded before the cutoff.

Retained incomplete evidence includes 0 API event records; no exact API-family total is available.

Brave Shields Comparison

No blocking and Brave-list blocking: two visits, no comparable metric delta

No blocking: 21,257msBrave-list blocking: 12,918ms
These two visits do not support a side-by-side comparison, so no deltas are shown.
  • The "No blocking" visit's synthetic form-input probe stopped one or more navigations, 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

14 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.
  • The in-page fingerprint observer read every frame but could not attribute every event listener to the script that registered it, so session-recording and input-monitoring findings for this visit are incomplete.
  • The synthetic form-input probe did not complete its test, so input-capture conclusions for this visit are incomplete.
  • This scan typed a synthetic test value into 2 form fields with native form submission blocked. Focus, input and blur handlers may run and send requests. The value is synthetic and is not stored. Observed requests during typing and the following wait are included in the request log. Teardown-only transmissions are not measured.
  • Read the site's privacy policy (https://www.costco.com/{seg}/{seg}/privacy-policy) and compared its text against this visit's observed behavior. Policy checks are an automated text match with the matched sentences quoted, not a legal reading.

No blocking visit only

  • The page did not reach network idle before the scan window ended.
  • The synthetic form-input probe stopped one or more navigations started while it ran, so this visit's request evidence is incomplete.
  • 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.
  • The fingerprint observer could not read one or more Web Workers the page started, so fingerprint-like API calls and heuristics for this visit are incomplete.
  • Resolved 1 first-party subdomain that is a CNAME alias for a third-party tracker (CNAME cloaking), which request-URL matching alone would miss.

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
20260928-04267875e264da7686c3aacf46462bba
Site
www.costco.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the synthetic form-input probe stopped one or more navigations started while it ran, so the request evidence is incomplete; the in-page fingerprint observer could not attribute every event listener to the script that registered it, so the fingerprinting evidence is incomplete; the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
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 fingerprint observer could not read one or more Web Workers the page started, so the fingerprinting evidence is incomplete; the synthetic form-input probe did not complete its test, so input-capture detection is incomplete; derived from status and warnings
Scanner
playwright-chromium
Browser
153.0.8010.12
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 .