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.
Scan report ready for www.etsy.com: 7 recorded request rows. The requested page was not established.
The selected visit failed. Retained requests describe only the returned document or partial visit; they cannot establish absence of activity on the requested page.
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
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).
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.
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.
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.
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.
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.
Brave Shields Comparison
No blocking and Brave-list blocking: two visits, no comparable metric delta
No blocking: 1,077msBrave-list blocking: 972ms
These two visits do not support a side-by-side comparison, so no deltas are shown.
The "No blocking" visit returned HTTP 403, an error or block page, not the real site.
The "Brave-list blocking" visit returned HTTP 403, an error or block page, not the real site.
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
5 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.
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, and any activity inside Web or Service Workers, are not observed. 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.
The page returned HTTP 403; this report reflects an error or block page, not a normal load.
Brave-list blocking visit only
Brave Shields block simulation was enabled; matching requests were aborted before loading and are not included in request totals.
How to use this report
Read the findings and measurement limits first, then inspect the evidence for each recorded visit. Comparisons include both visits, even where a difference cannot be interpreted.
Keep this PDF with its evidence package: the source JSON, correction context, export receipt and SHA256SUMS. The package preserves source bytes and the correction context at export time. Hashes check file consistency; they do not establish independent measurement accuracy or a signed attestation.
2026-07-06T09:27:22.574Z · failed (HTTP 403); derived from status and warnings
Retained observations from this visit. Missing measurements do not establish absence of activity.
Request attribution map
Which actor each third-party request is attributed to, from the initiator the browser reported. Attribution, not causation: an initiator may itself have been told what to fetch, and requests with no reported initiator are not distinguished from ones fetched from several. Asterisks mark subdomain labels hidden for privacy.
Attributed requests
0
Not attributable
6
Third-party requests
6
No unique actor could be assigned to 6 of these requests. That includes requests for which the browser reported no usable initiator, and repeated URLs seen with conflicting initiators. This report does not distinguish those causes, so they are counted together rather than drawn.
6 third-party requests: 0 attributed to a single recorded actor, 6 not attributable.
No retained third-party request has one recorded actor to draw. This is not evidence that no actor was involved: the visit may have reported no actor or several actors for the same request.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.
Requests76 third-party
Matched Shields lists0classification reported by this visit; no engine readback recorded
Third-party domains20 distinct catalogued service entities
Every domain this visit recorded, with its role, request count and catalog match.
Domain
Role
Requests
Catalog match
Resource types
static.captcha-delivery.com
third-party
4
No catalog match
stylesheet, image, font
*.captcha-delivery.com
third-party
2
No catalog match
script, document
www.etsy.com
first-party
1
No catalog match
document
These domains describe the returned document, not a verified normal page load.
Request log
7 recorded requests
In hosts and URLs, * and … mark details hidden for privacy.
Request references name this visit's retained JSON rows in order (B = baseline, V = variant, S = single). R0001 is the first request row.
Every request row this visit retained, with its time, status, resource type, domain and recorded provenance.
Ref
Time
Status
Type
Domain
Provenance
URL
B:R0001
41ms
403
document
www.etsy.com
Not attributed
https://www.etsy.com/
B:R0002
83ms
200
script
*.captcha-delivery.com
Not attributed
https://*.captcha-delivery.com/…
B:R0003
168ms
200
document
*.captcha-delivery.com
Not attributed
https://*.captcha-delivery.com/…?…&cid&t
B:R0004
329ms
200
stylesheet
static.captcha-delivery.com
Not attributed
https://static.captcha-delivery.com/…
B:R0005
329ms
200
stylesheet
static.captcha-delivery.com
Not attributed
https://static.captcha-delivery.com/…
B:R0006
329ms
200
image
static.captcha-delivery.com
Not attributed
https://static.captcha-delivery.com/…?…
B:R0007
416ms
200
font
static.captcha-delivery.com
Not attributed
https://static.captcha-delivery.com/…
These requests describe the returned document, not a verified normal page load.
Brave-list blocking — evidence
2026-07-06T09:27:23.655Z · failed (HTTP 403); derived from status and warnings
Retained observations from this visit. Missing measurements do not establish absence of activity.
Request attribution map
Which actor each third-party request is attributed to, from the initiator the browser reported. Attribution, not causation: an initiator may itself have been told what to fetch, and requests with no reported initiator are not distinguished from ones fetched from several. Asterisks mark subdomain labels hidden for privacy.
Attributed requests
0
Not attributable
6
Third-party requests
6
No unique actor could be assigned to 6 of these requests. That includes requests for which the browser reported no usable initiator, and repeated URLs seen with conflicting initiators. This report does not distinguish those causes, so they are counted together rather than drawn.
6 third-party requests: 0 attributed to a single recorded actor, 6 not attributable.
No retained third-party request has one recorded actor to draw. This is not evidence that no actor was involved: the visit may have reported no actor or several actors for the same request.
By the numbers
Recorded counts and evidence availability from this one visit. The findings above interpret them.
Requests76 third-party
Blocked by Brave lists0engine blocks reported by this visit; no engine readback recorded
Third-party domains20 distinct catalogued service entities
Every domain this visit recorded, with its role, request count and catalog match.
Domain
Role
Requests
Catalog match
Resource types
static.captcha-delivery.com
third-party
4
No catalog match
stylesheet, image, font
*.captcha-delivery.com
third-party
2
No catalog match
script, document
www.etsy.com
first-party
1
No catalog match
document
These domains describe the returned document, not a verified normal page load.
Request log
7 recorded requests
In hosts and URLs, * and … mark details hidden for privacy.
Request references name this visit's retained JSON rows in order (B = baseline, V = variant, S = single). R0001 is the first request row.
Every request row this visit retained, with its time, status, resource type, domain and recorded provenance.
Ref
Time
Status
Type
Domain
Provenance
URL
V:R0001
43ms
403
document
www.etsy.com
Not attributed
https://www.etsy.com/
V:R0002
87ms
200
script
*.captcha-delivery.com
Not attributed
https://*.captcha-delivery.com/…
V:R0003
220ms
200
document
*.captcha-delivery.com
Not attributed
https://*.captcha-delivery.com/…?…&cid&t
V:R0004
287ms
200
stylesheet
static.captcha-delivery.com
Not attributed
https://static.captcha-delivery.com/…
V:R0005
287ms
200
stylesheet
static.captcha-delivery.com
Not attributed
https://static.captcha-delivery.com/…
V:R0006
287ms
200
image
static.captcha-delivery.com
Not attributed
https://static.captcha-delivery.com/…?…
V:R0007
307ms
200
font
static.captcha-delivery.com
Not attributed
https://static.captcha-delivery.com/…
These requests describe the returned document, not a verified normal page load.
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.
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 .
Reports record one automated visit per condition; visits may be incomplete. On restart-safe deployments, an interrupted visit may be retried; attempts are never merged. Results describe these visits, not everything a site can do.