target.com recorded 86 fewer third-party requests in the visit configured for Brave-list blocking.
The visit with no blocking made 336 requests; the visit configured to apply Brave's ad-block engine and default Shields filter lists (a simulation in this scanner's browser, not a live Brave-browser visit) recorded 86 fewer third-party requests. The blocker directly stopped 54 requests; the remaining difference may include follow-on requests that never started once their sources were blocked, plus run-to-run variance.
The scan observed signals a non-expert should not have to decode from raw request tables.
The cards below translate the evidence into plain language. Where a measured distribution exists, severity ranks this visit against percentiles from the report's exact schema, methodology, tracker-catalog, ServiceRole-taxonomy, metric-contract, producer, and Global Privacy Control cohort, with each percentile card naming its metric-specific measured-site denominator (among 98 sites with a successful load across all cohorts; other methodologies, request-capped visits, and post-choice consent visits are excluded from this denominator, while failed or block-page attempts are outside that coverage), a curated set of popular, mostly commercial sites, not a random sample of the web, and otherwise uses fixed reference thresholds. The request log, domain table, and methodology remain below for verification.
336 requests observed in one controlled visit.
Worth checking
83 requests matched Brave Shields filter lists
83 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 73 request rows in this visit.Show matched requests
Nothing observed
Lower values observed across comparable metrics in the Brave-list blocking attempt
With the scanner configured to apply Brave's ad-block engine and default Shields filter lists (a simulation in this scanner's browser, not a live Brave-browser visit; application was not verified), this paired visit showed 86 fewer third-party requests, 3 fewer third-party cookies and 52 fewer tracking-related service requests.
Services only seen in the unblocked visit: Google, DoubleVerify and FullStory. The blocking visit's engine directly blocked 54 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), so treat this as an observed difference, not a measured blocking rate.
Signed per-metric differences between the two visits; nothing is summed across metrics.Show matched requests
Context
Tracking companies the privacy policy does not appear to name
DoubleVerify and FullStory 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. Named in the policy: Google and Adobe.
Policy at https://www.target.com/{seg}/{seg}/{seg}/{seg}; 0 checkable statements matched; 2 of 4 observed tracking companies named in the policy.
Worth checking
Catalogued service domains recorded responses during this visit
Google, Adobe and DoubleVerify, plus 1 other 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, analytics / advertising and advertising measurement / verification. This scan could not identify 14 of the 28 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site. Catalog labels include session-replay or behavior-analytics services: FullStory; the domain match alone does not prove that a recording occurred. The role taxonomy assigns these additional services explicitly non-tracking operational, support, security, consent-management, or hosting roles: HUMAN Security.
248 cross-site requests across 28 third-party hosts.At or above the 75th-percentile mark for third-party domains across the 88 sites measured for this metric.Show third-party requests
Context
Requests were dispatched to catalogued major-platform domains
This visit dispatched requests to catalogued domains for Google.
The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.
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.
41 cookies total in this report.At or above the median for third-party cookies across the 88 sites measured for this metric.
Worth checking
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. 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.
996 interaction-listener registrations with https://assets.targetimg1.com/, https://cdn.attn.tv/ and https://cdn.speedcurve.com/, plus 3 others in the registration call chain, 425 input-listener registrations with https://assets.targetimg1.com/, https://cdn.attn.tv/ and https://cdn.speedcurve.com/, plus 2 others in the registration call chain and known session-replay vendor(s): FullStory
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.
1 offline render with audio.OfflineAudioContext.createDynamicsCompressor, audio.OfflineAudioContext.createOscillator and audio.OfflineAudioContext.startRendering, 1 canvas matched; reads: canvas.toDataURL, 91 measureText calls across up to 91 fonts; measured text contents are not stored and 25 parameter reads and 12 pixel readbacks; parameters: webgl.getParameter.UNMASKED_RENDERER_WEBGL and webgl.getParameter.UNMASKED_VENDOR_WEBGL, plus 1 other
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.
Exact build and instrument digests were not recorded by this legacy schema.
Variant visit
Started
Run quality
complete; derived from status and warnings
Scanner
playwright-chromium
Browser
151.0.7922.34
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. 16 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 13 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 .