Site Behavior Lab

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

www.etsy.com

Requested addresshttps://www.etsy.com/

Jul 6, 2026, 9:27 AM UTC

failed (HTTP 403); derived from status and warnings

Evidence quality

This report is built on an incomplete visit

Incomplete evidence: The visit did not complete. Counts below are lower bounds for a visit that did not finish, so an absence here is especially weak evidence. The evidence receipt states the exact per-visit quality.

What this actually means

etsy.com returned HTTP 403 instead of a verified normal page load.

HTTP 403 denied this visit. Signals below describe the returned error or block page, not etsy.com's normal behavior. The status alone cannot identify the cause (authentication, access policy, automation filtering, or another control).

403HTTP status

Plain-Language Findings

What this visit means

Unfamiliar terms are defined in the glossary
playwright-chromium

Context

Bottom line: the requested page returned HTTP 403

The requested page responded with HTTP 403, so this report reflects the returned error or block document, not the site's normal behavior.

Tracker, cookie, storage, and fingerprinting signals here describe that returned document. They are retained evidence, not a privacy result for the site's normal page. The site answered and denied this visit. The status alone cannot distinguish authentication, access policy, automation filtering, or another cause, so a later re-scan may or may not differ. The request log and methodology below still show exactly what was observed.

7 requests observed before or with the error response.

Context

This Shields comparison is not conclusive

The "No blocking" visit returned HTTP 403, an error or block page, not the real site. and The "Brave-list blocking" visit returned HTTP 403, an error or block page, not the real site.

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

Returned HTTP 403 error or block page: No known services matched in retained evidence

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 2 of the 2 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 page returned HTTP 403, so this absence describes an error or block page, not the site.

6 cross-site requests across 2 third-party hosts.Show third-party requests

Context

Returned HTTP 403 error or block page: No requests to major-platform domains were recorded in retained evidence

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. The page returned HTTP 403, so this absence describes an error or block page, not the site.

2 cross-site domains seen overall.Show catalog-matched requests

Context

Returned HTTP 403 error or block page: No Google Analytics observed in retained evidence

This visit did not contact Google Analytics.

Neither Google Analytics nor its remarketing sync was observed in this visit. The page returned HTTP 403, so this absence describes an error or block page, not the site.

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

Context

Returned HTTP 403 error or block page: No third-party cookies observed in retained evidence

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. The page returned HTTP 403, so this absence describes an error or block page, not the site.

2 cookies total in this report.

Context

Returned HTTP 403 error or block page: No fingerprint-like API calls observed in retained evidence

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

This is an observation layer, not proof that fingerprinting is impossible. The page returned HTTP 403, so this absence describes an error or block page, not the site.

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
20260706-91c2370e5de35e5b4f09628459413e66
Site
www.etsy.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
failed (HTTP 403); 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
failed (HTTP 403); 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. 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 .