Site Behavior Lab
Site

www.creditkarma.com

Baseline visit
Requested address
https://www.creditkarma.com/
Report ID
20260810-fa3fa6ded2c1053717abc1263dc29d9b
Evidence SHA-256
11097dc2baf2fac861f12959a25ef501c3313d1ceb3d395dff16f4b7915f7a44
Scanner
playwright-chromium

creditkarma.com recorded 95 fewer third-party requests in the visit configured for Brave-list blocking.

Where this page's requests went

Both visits. One mark is one request row in the retained log.

No blocking

www.creditkarma.com itself66 requestsrequests that stayed on the site
Catalogued services52 requests12 names: Google 13, TikTok 8, Adobe 6, Tealium 5, Microsoft 4, and 7 more
Hosts the catalog does not name92 requests15 hosts; the catalog cannot say who operates them

Brave-list blocking

www.creditkarma.com itself66 requestsrequests that stayed on the site
Catalogued services3 requests1 name: Tealium 3
Hosts the catalog does not name46 requests4 hosts; the catalog cannot say who operates them
Not measuredabsence here is not evidence of absence
  • Other pages on this site
  • Signed-in visitors, other browsers and other regions
  • Anything that loads only after interaction or consent
  • Services the catalog does not name
  • Checks with incomplete evidence
  • one request on record, same site
  • one request on record, cross-site
  • not measured

The visit with no blocking made 210 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 95 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.

11tracking-service entities
144cross-site requests
18third-party cookie records
≥1fingerprint-like pattern retained

Review-worthy

Bottom line: this visit has review-worthy signals

The scan observed signals a non-expert should not have to decode from raw request tables. Some detector evidence was incomplete; each affected detector card states its own retained or unavailable scope, while completed request, cookie, and storage measurements keep their recorded exactness.

Where severity is ranked, the cohort is a curated set of popular, mostly commercial sites, not a random sample of the web. Details

The cards below translate the evidence into plain language. Where a measured distribution exists, severity ranks this visit against percentiles from this report's cohort, with each percentile card naming its metric-specific measured-site denominator; otherwise it uses fixed reference thresholds. That cohort is drawn from a curated set of popular, mostly commercial sites, not a random sample of the web. The request log, domain table, and methodology remain below for verification.

210 requests observed in one controlled visit.

What was checked

Page
https://www.creditkarma.com/
When
Aug 10, 2026, 6:47 AM UTC
Setup
Both visits used headless Chromium in a desktop window of 1440 × 980, with en-US language and UTC time zone. Both ran from a GitHub Actions Ubuntu runner; the network region was not recorded. Neither sent the Global Privacy Control (GPC) signal.
Visits
Two visits configured to differ in Brave-list blocking: No blocking and Brave-list blocking.
Interactions
No typing was recorded in either visit. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence in the No blocking visit was cut short.

What these visits could not see

  • Other pages on this site. Only the requested page's activity was recorded.
  • Signed-in visitors, other browsers and other regions. Both visits were automated, from a fixed en-US / UTC profile. Sites can behave differently for real users, browsers, regions, accounts, or network locations.
  • Anything that loads only after interaction or consent. Trackers that load that late are not observed, so counts are a lower bound.
  • Services the catalog does not name. Service labels use a US-biased hand-curated catalog, so regional services may be under-labeled.
  • Checks with incomplete evidence. In the No blocking visit only: advertising pixels, session-recording signals, fingerprinting, the typing test, CNAME cloaking, the consent banner and the privacy policy check. Each linked card states what was retained.

Worth checking

61 requests matched Brave Shields filter lists

61 requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.

Blocking can also prevent follow-on requests, so this number is neither a measured block count nor what a Brave visit would block. Details

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. This is Site Behavior Lab's list-based simulation, which applies every list to the site's own requests too. Brave's default Standard setting skips most of these lists for such requests, so its results can differ.

The hand-curated service catalog separately matched 52 request rows in this visit.Show matched requests

Not flagged

Lower values observed across comparable metrics in the Brave-list blocking attempt

The blocking visit ran with the scanner configured to apply Brave's ad-block engine and default Shields filter lists. It was a simulation in this scanner's browser, not a live Brave-browser visit, and application was not verified. Compared with the unblocked visit, it showed 95 fewer third-party requests, 18 fewer third-party cookies and 47 fewer tracking-related service requests.

Treat this as an observed difference, not a measured blocking rate. Details

Services only seen in the unblocked visit: Google, TikTok and Adobe, plus 7 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).

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

Google, TikTok and Adobe, plus 8 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. Details

Functional catalog labels include analytics / tag management, advertising and social / advertising pixel. This scan could not identify 14 of the 33 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: New Relic.

144 cross-site requests across 33 third-party hosts.At or above the 75th-percentile mark for third-party domains across the 86 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, Meta and TikTok, plus 2 others.

The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.

29 requests to these platforms.Show catalog-matched requests

Context

Advertising pixel requests contained event labels

TikTok Pixel requests contained event labels during this visit.

Retained labels describe request contents, not verified user actions or successful delivery. Details

Pixel decoding was incomplete for one or more request bodies, so whether other pixel requests carried advanced-matching identifier fields is unknown.

TikTok Pixel: custom event and Pageview (4 requests).Show catalog-matched requests

Context

Google Analytics present; a remarketing sync cannot be told from this report

Google Analytics was observed, with requests to DoubleClick hosts whose names this report generalizes. The remarketing sync host is one such name, so the sync cannot be told apart from them.

This report neither shows nor rules out the sync. Details

The sync goes to stats.g.doubleclick.net, and a published report writes that name the same way as DoubleClick's ad-serving hosts.

Google Analytics host observed; DoubleClick hosts recorded under generalized names.Show catalog-matched requests

Review-worthy

Third-party cookies were present

18 third-party cookies showed up during the visit.

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. Details

The scanner observed cookie metadata whose domain crossed the scanned site's registrable-domain boundary.

53 cookies total in this report.At or above the 90th-percentile mark for third-party cookies across the 86 sites measured for this metric.

Context

Session-replay vendor observed

FullStory appeared in the request log.

The domain match alone does not prove that a recording occurred. Details

Catalog labels include session-replay or behavior-analytics services: FullStory. Treat this card as a review prompt rather than proof.

Known session-replay vendor(s): FullStory.

Look closer

Show requests to FullStory

Opens this report's request log filtered to FullStory; listener registrations are not request rows, so the log cannot show what was observed.

Worth checking

Offline audio rendering heuristic matched

At least 1 behavioral heuristic matched in retained evidence: Offline audio rendering heuristic.

They are review prompts for this visit, not proof of cross-site identity tracking. Details

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.

Offline audio rendering heuristic: 1 offline render with audio.OfflineAudioContext.createAnalyser, audio.OfflineAudioContext.createDynamicsCompressor and audio.OfflineAudioContext.createOscillator, plus 1 other.

Domain evidence

35 recorded domains
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 34 sCatalog matchRoleResource types
www.creditkarma.com62No catalog matchfirst-partydocument, stylesheet, script, xhr
*.intuitcdn.net23No catalog matchthird-partyscript, stylesheet, fetch, font
*.imgix.net20No catalog matchthird-partyimage
*.intuit.com12No catalog matchthird-partyimage, fetch, xhr
creditkarmacdn-a.akamaihd.net11No catalog matchthird-partyscript, image, font
analytics.tiktok.com8TikTok: social / advertising pixelservicescript, ping
*.youstarsbuilding.com8No catalog matchthird-partyscript, image, xhr
www.google.com7No catalog matchthird-partyfetch, image
*.demdex.net6Adobe: analytics / advertisingservicexhr, document, image, fetch
www.googletagmanager.com5Google: analytics / tag managementservicescript
*.*.doubleclick.net4Google: advertisingservicescript, image, ping
*.bing.com4Microsoft: advertising / analyticsservicescript, image
*.creditkarma.com4No catalog matchfirst-partydocument, script, fetch
*.tiqcdn.com3Tealium: tag management / customer dataservicescript
*.criteo.com3Criteo: advertisingservicescript, document
www.googleadservices.com3Google: advertisingserviceimage, script
*.rlcdn.com2LiveRamp: identity / advertisingserviceimage
collect.tealiumiq.com2Tealium: tag management / customer dataservicexhr
*.fullstory.com2FullStory: session replayservicexhr
*.taboola.com2Taboola: advertising / recommendationsservicescript, xhr
*.pinterest.com2Pinterest: social / advertising pixelservicexhr
*.facebook.net2Meta: social / advertising pixelservicescript
*.pinimg.com2No catalog matchthird-partyscript
*.reddit.com2No catalog matchthird-partyxhr, image
cdn.taboola.com1Taboola: advertising / recommendationsservicescript
*.newrelic.com1New Relic: performance monitoringservicescript
*.nr-data.net1New Relic: performance monitoringservicescript
analytics.google.com1Google: analytics / tag managementservicefetch
*.reson8.com1No catalog matchthird-partyimage
www.dwin1.com1No catalog matchthird-partyscript

+5 more in the evidence explorer below.

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
20260810-fa3fa6ded2c1053717abc1263dc29d9b
Site
www.creditkarma.com
Latest visit
Schema
v1 schema · facts legacy-derived · descriptive report
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: the in-page fingerprint observer could not read every frame, so the fingerprinting evidence is incomplete; 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.

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. 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.

Severity percentiles come from this report's exact schema, methodology, tracker-catalog, ServiceRole-taxonomy, metric-contract, producer, and Global Privacy Control cohort. Each percentile card's measured sites are among 99 sites with a successful load across all cohorts. Other methodologies and post-choice consent visits are excluded from each card's denominator, while failed or block-page attempts are outside that coverage. Visits with capped or incomplete request evidence are left out of each mark. They tend to be the heaviest pages, so a mark can sit lower than the cohort's true mark.

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 .