linkedin.com's retained request log includes catalogued LinkedIn, Google and Meta, +1 more domains.
Where this page's requests went
The No blocking visit. One mark is one request row in the retained log.
www.linkedin.com itselfat least 18 retained requestsrequests that stayed on the site
000000000000000000
Catalogued servicesat least 34 retained requests5 names: LinkedIn 25, Adobe 5, Google 2, Meta 1, Microsoft 1
0000000000000000000000000000000000
Hosts the catalog does not nameat least 12 retained requests4 hosts; the catalog cannot say who operates them
000000000000
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
Retained request rows include 5 distinct catalogued tracking-service entities; 5 of the retained service matches recorded responses across at least 9 retained cross-site domains. A catalog match identifies the service domain, not why the request occurred or what it carried. In the visit labeled No blocking, it also looks like keyboard-input listeners were registered through a call chain that included a cross-site script and 3 browser-fingerprinting heuristics matched.
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 activity evidence was also incomplete: request counts are retained lower bounds.
This failed or incomplete evidence is not ranked against corpus percentiles; positive signals remain visible as lower bounds.Details
The cards below translate the evidence into plain language. The request log, domain table, and methodology remain below for verification.
At least 64 retained requests observed in one controlled visit.
What was checked
Page
https://www.linkedin.com/
When
Aug 10, 2026, 7:09 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. 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.
At least 22 retained requests matched Brave Shields filter lists
At least 22 retained 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 at least 34 retained request rows in this visit.Show matched requests
Context
This Shields comparison is not conclusive
The "No blocking" visit had one or more requests refused by the scanner's own network guard, so its request evidence is incomplete.
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.
Tracking companies the privacy policy does not appear to name
Adobe, Google and Meta were sent requests during this visit. However, 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.Details
Named in the policy: LinkedIn and Microsoft.
Policy at https://www.linkedin.com/legal/privacy-policy; 0 checkable statements matched; 2 of 5 observed tracking companies named in the policy.
Opens the request log at its catalog-matched rows, which include the requests to the companies this card names.
Context
Catalogued service domains recorded responses during this visit
LinkedIn, Adobe and Google, plus 2 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 social / advertising pixel, analytics / advertising and advertising. This scan could not identify 2 of the 9 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.
At least 46 retained cross-site requests across at least 9 retained third-party hosts.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 Microsoft, plus 1 other.
The domain matches identify services, not the requests' purpose, payload, or whether any profile linking occurred.
10 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.
21 cookies total in this report.
Context
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.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: 44 interaction-listener registrations with https://static.licdn.com/ in the registration call chain. Input-monitoring listener coverage: 14 input-listener registrations with https://static.licdn.com/ in the registration call chain.
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.
Canvas fingerprinting heuristic: 3 canvases matched; reads: canvas.toDataURL. Offline audio rendering heuristic: 2 offline renders with audio.OfflineAudioContext.createDynamicsCompressor, audio.OfflineAudioContext.createOscillator and audio.OfflineAudioContext.startRendering. WebRTC peer-connection probing: 2 peer connections with 2 data channels, 2 offers, and 2 local descriptions.
Domain evidence
11 recorded domains
These are retained domain rows, not a complete inventory.
The busiest recorded domains of the No blocking visit, with role, request count, request start times and catalog match.
Domain
Requests
When, 0 to 4.3 s
Catalog match
Role
Resource types
static.licdn.com
25
LinkedIn: social / advertising pixel
service
stylesheet, image, script, fetch
www.linkedin.com
11
No catalog match
first-party
document, xhr, fetch
*.linkedin.com
7
No catalog match
first-party
script, document, xhr
*.demdex.net
5
Adobe: analytics / advertising
service
xhr, document, image
*.protechts.net
5
No catalog match
third-party
document, script, xhr
trkn.us
4
No catalog match
third-party
image
*.*.doubleclick.net
2
Google: advertising
service
image
accounts.google.com
2
No catalog match
third-party
document, xhr
www.facebook.com
1
Meta: social / advertising pixel
service
image
*.bing.com
1
Microsoft: advertising / analytics
service
image
*.gstatic.com
1
No catalog match
third-party
font
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.
cut short: the scanner's own network guard refused one or more requests, which were never sent and have no row, so the request 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.
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 .