Detect Liberapay

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

• Script sources
• DOM selectors

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

• liberapay.com/

Establishes

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

Does not establish

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

Can PluginView detect Liberapay without logging in?

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

What category is Liberapay?

Liberapay is classified under Payment processors in the PluginView directory.

How many fingerprint rules cover Liberapay?

This reference currently tracks 2 fingerprint rules across script sources, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Liberapay?

Illustrative public indicators for Liberapay include liberapay.com/. A live scan may match additional proprietary rules beyond these examples.