Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name4 requests3 hosts; the catalog cannot say who operates them
0000
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
not measured
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.
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 detector evidence was incomplete; each affected detector card states its own retained or unavailable scope, while completed request, cookie, and storage measurements keep their recorded exactness.
Where severity is ranked, the cohort is a curated set of popular, mostly commercial sites, not a random sample of the web.Details
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.
312 requests observed in one controlled visit.
What was checked
Page
https://www.costco.com/
When
Nov 18, 2026, 6:16 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
Typed a made-up test value into 2 form fields in the No blocking visit and 1 form field in the Brave-list blocking visit, never submitting the form. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence was cut short.
What these visits could not see
Other pages on this site. Only the requested page's activity was recorded. The privacy policy was opened only to read its text, and none of its 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 both visits: the typing test. Each linked card states what was retained.
Worth checking
38 requests matched Brave Shields filter lists
38 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 29 request rows in this visit.Show matched requests
Not flagged
Lower values observed across comparable metrics in the Brave-list blocking attempt
The blocking visit ran with the scanner configured to apply Brave's ad-block engine and default Shields filter lists. It was a simulation in this scanner's browser, not a live Brave-browser visit, and application was not verified. Compared with the unblocked visit, it showed 52 fewer third-party requests, 2 fewer third-party cookies and 29 fewer tracking-related service requests.
Treat this as an observed difference, not a measured blocking rate.Details
Services only seen in the unblocked visit: Adobe and Criteo. The blocking visit's engine directly blocked 4 requests; the remaining difference may include follow-on requests that never started once their sources were blocked. A single paired comparison can also reflect run-to-run variance (ad rotation, caching, experiments).
Signed per-metric differences between the two visits; nothing is summed across metrics.Show matched requests
Worth checking
Synthetic form input appeared in requests to 1 cross-site domain before submission
When the scanner typed a unique test value into 2 form fields, that value appeared in requests to 1 cross-site domain without the form being submitted. Recipient: *.*.dynatrace.com. Encoding: 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.Details
The synthetic value appeared in a recoverable form (plain). The scanner types only synthetic values and never submits the form.
Synthetic test value appeared in requests to *.*.dynatrace.com via plain.
Opens this report's request log filtered to *.*.dynatrace.com, without marking which of those requests carried the test value.
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: *.costco.com → cloud-cdn.co (Brave filter-list match; operator unverified). DNS alias: *.costco.com → *.*.*.*.omtrdc.net (Adobe; catalog match).Open domain evidence
Context
Tracking companies the privacy policy does not appear to name
Adobe and Criteo were sent requests during this visit. However, 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/…/privacy-policy; 0 checkable statements matched; 0 of 2 observed tracking companies named in the policy.
Opens the request log at its catalog-matched rows, which include the requests to the companies this card names.
Worth checking
Catalogued service domains recorded responses during this visit
Adobe and Criteo 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 / advertising and advertising. This scan could not identify 10 of the 14 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.
56 cross-site requests across 14 third-party hosts. This report does not record which requests came during the typing test.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.
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.
35 cookies total in this report.At or above the median for third-party cookies across the 74 sites measured for this metric.
Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.
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: 109 interaction-listener registrations with https://assets.adobedtm.com/, https://cdn.intake-lr.com/ and https://*.dynatrace.com/ in the registration call chain. Input-monitoring listener coverage: 159 input-listener registrations with https://cdn.intake-lr.com/, https://*.dynatrace.com/ and https://transcend-cdn.com/ in the registration call chain.
Moves to the card where this visit's typing test found its made-up value in a cross-site request.
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.
Domain evidence
16 recorded domains
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
Domain
Requests
When, 0 to 15.6 s
Catalog match
Role
Resource types
www.costco.com
154
No catalog match
first-party
document, stylesheet, script, fetch, image, xhr
*.costco.com
102
No catalog match
first-party
image, script, fetch, ping
assets.adobedtm.com
20
Adobe: analytics / advertising
service
script
*.*.dynatrace.com
8
No catalog match
third-party
ping, fetch
*.*.criteo.com
4
Criteo: advertising
service
fetch
*.criteo.com
4
Criteo: advertising
service
script, document
static.queue-it.net
4
No catalog match
third-party
script
transcend-cdn.com
2
No catalog match
third-party
script
*.costco-static.com
2
No catalog match
third-party
font
cdn.intake-lr.com
2
No catalog match
third-party
script
*.cdndex.io
2
No catalog match
third-party
xhr
cloudflare.com
2
No catalog match
third-party
fetch
*.dynatrace.com
2
No catalog match
third-party
script
assets.queue-it.net
2
No catalog match
third-party
script
*.demdex.net
1
Adobe: analytics / advertising
service
fetch
*.intake-lr.com
1
No catalog match
third-party
xhr
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 did not complete its test, so input-capture detection 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
cut short: 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
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. 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 98 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 .