Site Behavior Lab
Site

creditkarma.com

Baseline visit
Requested address
https://www.creditkarma.com/
Report ID
20260814-2943c6775c7589eba879c77245c2abdb
Evidence SHA-256
0c09263512628d279721ea8bac39feebdfcc8d269dcc2bad3685527c3c0b38e0
Scanner
playwright-chromium

creditkarma.com contacted catalogued Google, TikTok and Microsoft, +1 more domains during the visit labeled GPC off.

Where this page's requests went

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

GPC off

creditkarma.com itself73 requestsrequests that stayed on the site
Catalogued services42 requests9 names: Google 13, Adobe 6, Tealium 6, TikTok 5, Microsoft 4, and 4 more
Hosts the catalog does not name79 requests11 hosts; the catalog cannot say who operates them

GPC on

creditkarma.com itselfat least 63 retained requestsrequests that stayed on the site
Catalogued servicesat least 40 retained requests9 names: Google 13, Tealium 6, Adobe 5, TikTok 5, Microsoft 4, and 4 more
Hosts the catalog does not nameat least 86 retained requests11 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
  • the count is a lower bound; more may exist
  • not measured

8 distinct catalogued tracking-service entities had requests dispatched (7 recorded responses; the rest recorded no response) across 26 cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried.

8tracking-service entities
121cross-site requests
17third-party cookie records

Worth checking

Bottom line: this visit has signals worth checking

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.

194 requests observed in one controlled visit.

What was checked

Page
https://www.creditkarma.com/
When
Aug 14, 2026, 6:57 PM 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 scanner host the report does not name; the network region was not recorded.
Visits
Two visits configured to differ in the Global Privacy Control (GPC) signal: GPC off and GPC on.
Interactions
No typing was recorded in either visit. No scrolling, clicking or consent interaction.
Outcome
Both visits completed, but some evidence 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 both visits: fingerprinting, session-recording signals and the privacy policy check. In the GPC on visit only: Brave Shields matches, third-party services, named platforms, advertising pixels, Google Analytics remarketing and the consent banner. Each linked card states what was retained.

Worth checking

50 of 177 requests the engine evaluated matched Brave Shields filter lists

50 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 42 request rows in this visit.Show matched requests

Context

This GPC comparison supports no comparable delta

The pair did not record the network egress region for both visits, and an unrecorded condition never counts as matching. The variant visit did not completely capture this evidence family, so its values are unavailable or incomplete rather than comparable totals.

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.

2 disqualifying conditions named by the report's claim policy.

Worth checking

Requests were dispatched to catalogued service domains

Google, Adobe and Tealium, 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. Details

Functional catalog labels include analytics / tag management, advertising and analytics / 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.

121 cross-site requests across 26 third-party hosts.At or above the median for third-party domains across the 51 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.

23 requests to these platforms.Show catalog-matched requests

Context

Advertising pixel requests contained event labels

TikTok Pixel requests contained event labels during this visit.

Event labels do not establish user actions or successful delivery. Details

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.

TikTok Pixel: custom event and Pageview (2 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

Worth checking

Third-party cookies were present

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

49 cookies total in this report.At or above the 75th-percentile mark for third-party cookies across the 51 sites measured for this metric.

Context

Incomplete evidence: No fingerprint-like API calls observed in retained evidence before collection stopped

The retained evidence holds no calls to the instrumented high-entropy browser APIs.

Evidence collection was cut short, so this covers only what was recorded before the cutoff. Details

This is an observation layer, not proof that fingerprinting is impossible.

Retained incomplete evidence includes 0 API event records; no exact API-family total is available.

Domain evidence

28 recorded domains
The busiest recorded domains of the GPC off visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 37.1 sCatalog matchRoleResource types
www.creditkarma.com69No catalog matchfirst-partydocument, stylesheet, script
*.intuitcdn.net22No catalog matchthird-partyscript, stylesheet, fetch, font
*.intuit.com14No catalog matchthird-partyimage, xhr, fetch
*.imgix.net11No catalog matchthird-partyimage
creditkarmacdn-a.akamaihd.net10No catalog matchthird-partyscript, image, font
*.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
analytics.tiktok.com5TikTok: social / advertising pixelservicescript, ping
collect.tealiumiq.com4Tealium: tag management / customer dataservicexhr
*.*.doubleclick.net4Google: advertisingservicescript, image, ping
*.bing.com4Microsoft: advertising / analyticsservicescript, image
*.creditkarma.com4No catalog matchfirst-partydocument, script, fetch
www.googleadservices.com3Google: advertisingserviceimage, script
*.rlcdn.com2LiveRamp: identity / advertisingserviceimage
*.tiqcdn.com2Tealium: tag management / customer dataservicescript
*.taboola.com2Taboola: advertising / recommendationsservicescript, xhr
*.pinimg.com2No catalog matchthird-partyscript
*.api.intuit.com2No catalog matchthird-partyfetch
cdn.taboola.com1Taboola: advertising / recommendationsservicescript
*.pinterest.com1Pinterest: social / advertising pixelservicexhr
*.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
*.roeyecdn.com1No catalog matchthird-partyscript

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
20260814-2943c6775c7589eba879c77245c2abdb
Site
creditkarma.com
Latest visit
Schema
v2 schema (r2)
Verify recorded provenance

Baseline visit

Started
Run quality
cut short: fingerprinting evidence was censored before completion: the in-page fingerprint observer did not finish (recorded loss count: 1); detector output evidence was censored before completion: 1 privacy-policy visit did not produce usable evidence; recorded by the scanner
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1
Detector registry
node-detectors-v4100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2
Tracker catalog digest
e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f4
Brave-list instrument
engine adblock-rust-0.13.20f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0ac
Normalization
redaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1

Variant visit

Started
Run quality
cut short: request evidence was censored before completion: the producer recorded an additional collection loss (recorded loss count: 1); fingerprinting evidence was censored before completion: the in-page fingerprint observer did not finish (recorded loss count: 1); detector output evidence was censored before completion: 1 privacy-policy visit did not produce usable evidence; recorded by the scanner
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
version 4
Methodology
shields-request-context-v2-adblock-rust-0.13.2-request-method-v1-playwright-1.62.1+subject-validity-v2+detector-coverage-v2+phase-kernel-v2+boundary-state-v1+consent-r2-v4+resource-budget-v1+proxy-traffic-v1+service-worker-block-v1+detector-accountability-v1+service-role-taxonomy-v1
Detector registry
node-detectors-v4100de91713270067dff4f5ecebeea61d330982c7a5aa33395bae3dd604adedd2
Tracker catalog digest
e94970de235fc80254de8ed99b94316a252e52aa1c2e748c8fbfc3c093b908f4
Brave-list instrument
engine adblock-rust-0.13.20f52cc524a8999a1022279aca74003ece9720f267bc678430727b7312d43f0ac
Normalization
redaction-v4+allowlists-v3:269f631f04090ce582644ee3cf0e5c5b6bb425dc4929bc283607b808bc9322a9+public-string-policy-v3:6c78c05523e1f16c88264d0144af33587bd6dc11e04d337a6af2d58190639266+tldts@7.4.10+node-evidence-policy-v1+r2-http-status-compat-v1

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 .