Site Behavior Lab
Site

www.paypal.com

Baseline visit
Requested address
https://www.paypal.com/
Report ID
20260810-3c25e100d9616c4e823455be728520c7
Evidence SHA-256
fa7c46bec8ef697a46b970b8096d8cd45807e4765e23dab97d71c71a2c4cf373
Scanner
playwright-chromium

paypal.com recorded 5 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.paypal.com itself12 requestsrequests that stayed on the site
Catalogued services1 request1 name: Google 1
Hosts the catalog does not name89 requests5 hosts; the catalog cannot say who operates them

Brave-list blocking

www.paypal.com itself7 requestsrequests that stayed on the site
Catalogued services0 requestsno retained request matched the service catalog
Hosts the catalog does not name85 requests5 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
  • one request on record, same site
  • one request on record, cross-site
  • not measured

The visit with no blocking made 102 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 5 fewer third-party requests. The blocker directly stopped 18 requests, more than the net difference: a blocked request can be retried or replaced by another, and counts vary from run to run.

1tracking-service entity
90cross-site requests
1third-party cookie record

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.

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.

102 requests observed in one controlled visit.

What was checked

Page
Requested https://www.paypal.com/; both visits landed on https://www.paypal.com/us/home
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.

What these visits could not see

  • Other pages on this site. Only the requested page's activity was recorded. The privacy policy was opened only to read its text, and none of its 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.

Worth checking

12 requests matched Brave Shields filter lists

12 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 1 request row 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 5 fewer third-party requests and 1 fewer tracking-related service request.

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

Services only seen in the unblocked visit: Google. The blocking visit's engine directly blocked 18 requests. Ad rotation, experiments, or caching between the two visits can offset or outweigh what blocking removed, which is how totals can hold steady or rise despite direct blocks. 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

Context

Privacy policy read; it made no statement this scan can check

None of the statements this scan knows how to check appear in the policy text. As a result, nothing was compared against this visit's evidence (1 of 1 observed tracking company named in the policy). That is a limit of the automated check, not a finding about the site either way.

Global Privacy Control claims are never checked against request counts, which cannot show whether selling or sharing stopped. Details

Statements checked automatically: blanket no-cookie claims, third-party-cookie claims, and combined do-not-sell-or-share claims against advertising-pixel identifier fields.

Policy at https://www.paypal.com/…/privacy/…; 0 checkable statements matched; 1 of 1 observed tracking company named in the policy.

Context

Catalogued service domains recorded responses during this visit

Google 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. This scan could not identify 3 of the 6 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.

90 cross-site requests across 6 third-party hosts.At or above the median for third-party domains across the 86 sites measured for this metric. Modest distinct tracking-service entities count.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.

1 request to these platforms.Show catalog-matched requests

Not flagged

Google Tag Manager loaded, no Analytics request recorded

This visit contacted Google Tag Manager, but recorded no request to a Google Analytics collection host and no DoubleClick remarketing sync.

Tag Manager can fetch Google Analytics or other tags, or none; this report cannot tell which it fetched here. Details

Tag Manager is a loader.

googletagmanager.com observed; no google-analytics.com, analytics.google.com or stats.g.doubleclick.net request.Show catalog-matched requests

Context

Third-party cookies were present

1 third-party cookie 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.

14 cookies total in this report.At or above the median for third-party cookies across the 86 sites measured for this metric.

Look closer

See other visits' cookie counts

Opens this site's history page, which lists the third-party cookie count each of its retained reports recorded.

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. This scan did not establish the operator of that 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. Details

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. That is 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. The card therefore 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.

Session-recording listener coverage: 253 interaction-listener registrations with https://www.paypalobjects.com/ in the registration call chain. Input-monitoring listener coverage: 436 input-listener registrations with https://www.paypalobjects.com/ in the registration call chain.

Look closer

Show requests involving www.paypalobjects.com

Opens this report's request log filtered to www.paypalobjects.com, a script origin recorded in the listener's call chain.

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

Top calls: webgl.getParameter.UNMASKED_RENDERER_WEBGL and webgl.getParameter.UNMASKED_VENDOR_WEBGL.

2 API families recorded.

Domain evidence

8 recorded domains
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
DomainRequestsWhen, 0 to 4.9 sCatalog matchRoleResource types
www.paypalobjects.com72No catalog matchthird-partyscript, stylesheet, font, image, document
www.paypal.com7No catalog matchfirst-partydocument, script, xhr
browser-intake-us5-datadoghq.com6No catalog matchthird-partyfetch
www.recaptcha.net5No catalog matchthird-partyscript, document, xhr, fetch
www.gstatic.com5No catalog matchthird-partyscript, stylesheet, image, other
*.paypal.com5No catalog matchfirst-partyfetch
www.googletagmanager.com1Google: analytics / tag managementservicescript
*.gstatic.com1No catalog matchthird-partyfont

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

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

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. A study has been recorded for pixel-events and does not support a published rate under the current build. 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 .