creditkarma.com recorded 82 fewer third-party requests in the visit configured for Brave-list blocking.
The visit with no blocking made 199 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 82 fewer third-party requests. The blocker directly stopped 7 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.
199 requests observed in one controlled visit.
Worth checking
59 requests matched Brave Shields filter lists
59 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 51 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 82 fewer third-party requests, 17 fewer third-party cookies and 47 fewer tracking-related service requests.
Services only seen in the unblocked visit: TikTok, Google and Adobe, plus 4 others. The blocking visit's engine directly blocked 7 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
Worth checking
Requests were dispatched to catalogued service domains
TikTok, Google and Adobe, plus 5 others 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 social / advertising pixel, analytics / tag management and advertising. This scan could not identify 10 of the 26 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 role taxonomy assigns these additional services explicitly non-tracking operational, support, security, consent-management, or hosting roles: New Relic.
129 cross-site requests across 26 third-party hosts.At or above the 75th-percentile mark for third-party domains across the 88 sites measured for this metric. Elevated distinct tracking-service entities count (at or above the 6 reference threshold).Show third-party requests
Worth checking
Requests were dispatched to catalogued major-platform domains
This visit dispatched requests to catalogued domains for Google, TikTok and Microsoft, plus 1 other.
The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.
TikTok Pixel requests contained event labels during this visit.
No advanced-matching identifier fields are recorded in the decoded evidence. Unsupported payload formats and later interactions may carry other fields; older decoders did not record every decoding gap. Event labels do not establish user actions or successful delivery.
17 third-party cookies showed up during the visit.
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.
49 cookies total in this report.At or above the 90th-percentile mark for third-party cookies across the 88 sites measured for this metric.
Context
Fingerprint-like browser APIs were called
2 high-entropy API calls appeared in the instrumentation log.
These calls can be legitimate (charts, graphics, media), so the count is observational, not a severity score, and it excludes Web and Service Workers. Top calls: webgl.getParameter.UNMASKED_RENDERER_WEBGL and webgl.getParameter.UNMASKED_VENDOR_WEBGL.
2 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.
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. 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 .