Detect Poppins

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

• Script sources

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

• poppins.so/

Establishes

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

Does not establish

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

Can PluginView detect Poppins without logging in?

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

What category is Poppins?

Poppins is classified under Marketing automation in the PluginView directory.

How many fingerprint rules cover Poppins?

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 Poppins?

Illustrative public indicators for Poppins include poppins.so/. A live scan may match additional proprietary rules beyond these examples.