Detect Feroot

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

• Script sources

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

• pg.feroot.com

Establishes

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

Does not establish

A sitewide install of Feroot, an active vendor contract, exclusive use, or that Feroot 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 Feroot signals.
2. 2. PluginView reads only public responses (script sources) and scores them against the Feroot signature set (1 rules).
3. 3. Review the confidence score and text explanation for Feroot on the results page.

Can PluginView detect Feroot without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Feroot — typically script sources. It does not bypass authentication or paywalls.

What category is Feroot?

Feroot is classified under Payment processors in the PluginView directory.

How many fingerprint rules cover Feroot?

This reference currently tracks 1 fingerprint rule across script sources. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Feroot?

Illustrative public indicators for Feroot include pg.feroot.com. A live scan may match additional proprietary rules beyond these examples.