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