Detect Leadfeeder

PluginView evaluates public page signals in these classes when identifying Leadfeeder. Individual fingerprint rule bodies are proprietary and are not published.

• Response headers
• Script sources
• JavaScript globals

Illustrative indicators derived from public catalog metadata for Leadfeeder. A live scan may match additional proprietary rules beyond these examples.

• content-security-policy: .lfeederleadfeeder.com
• .leadfeeder.com/
• ldfdr.getTracker

Establishes

One or more public signals on the scanned page matched a known Leadfeeder signature (3 rules) at the time of the scan.

Does not establish

A sitewide install of Leadfeeder, an active vendor contract, exclusive use, or that Leadfeeder is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Leadfeeder signals.
2. 2. PluginView reads only public responses (response headers, script sources, javascript globals) and scores them against the Leadfeeder signature set (3 rules).
3. 3. Review the confidence score and text explanation for Leadfeeder on the results page.

Can PluginView detect Leadfeeder without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Leadfeeder — typically response headers, script sources, javascript globals. It does not bypass authentication or paywalls.

What category is Leadfeeder?

Leadfeeder is classified under Analytics in the PluginView directory.

How many fingerprint rules cover Leadfeeder?

This reference currently tracks 3 fingerprint rules across response headers, script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Leadfeeder?

Illustrative public indicators for Leadfeeder include content-security-policy: .lfeederleadfeeder.com; .leadfeeder.com/; ldfdr.getTracker. A live scan may match additional proprietary rules beyond these examples.