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
wayfair.com returned HTTP 429 instead of a verified normal page load.
HTTP 429 prevented the requested page from being measured. Signals below describe the returned error or block page, not wayfair.com's normal behavior. The site rate-limited this visit, so a later re-scan may succeed.
The requested page responded with HTTP 429, 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 rate-limited this visit, so a later re-scan may succeed. The request log and methodology below still show exactly what was observed.
18 requests observed before or with the error response.
Context
This Shields comparison is not conclusive
The "No blocking" visit returned HTTP 429, an error or block page, not the real site. and The "Brave-list blocking" visit returned HTTP 429, 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.
Other third-party operators were identified outside the tracking-service catalog
Google were named by consent-platform signatures, reviewed ownership, or CNAME evidence without being classified as tracking services.
Operator identity and tracking classification are separate: naming an operator does not prove that a request was for tracking. This scan could not identify 5 of the 7 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.
Requests were dispatched to major-platform domains the catalog does not carry
This visit dispatched requests to Google domains that the reviewed ownership map names, though the service catalog carries no entry for them.
Asset and font hosts reach this state often: the ownership map establishes who operates the domain, and nothing here establishes the request's purpose or payload. These domains are not counted as catalog-matched requests.
Returned HTTP 429 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 429, so this absence describes an error or block page, not the site.
Returned HTTP 429 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 429, so this absence describes an error or block page, not the site.
4 cookies total in this report.
Context
Input-monitoring signal involving a script from another domain
Listener coverage that could observe typing-related input events was registered through call chains that included a script served from another registrable domain, whose operator this scan did not establish.
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. 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, 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, so the card 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.
28 interaction-listener registrations with https://*.px-cloud.net/ in the registration call chain and 4 input-listener registrations with https://*.px-cloud.net/ in the registration call chain
These heuristics look for behavior patterns such as canvas readback after drawing, repeated canvas font measurement, WebGL entropy reads, offline audio rendering, or WebRTC peer-connection setup. They are review prompts for this visit, not proof of cross-site identity tracking.
25 parameter reads and 12 pixel readbacks; parameters: webgl.getParameter.UNMASKED_RENDERER_WEBGL and webgl.getParameter.UNMASKED_VENDOR_WEBGL
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.
failed (HTTP 429); 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 429); 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. 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 .