Detect Inputflow

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

• Script sources

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

• script.inputflow.io

Establishes

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

Does not establish

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

Can PluginView detect Inputflow without logging in?

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

What category is Inputflow?

Inputflow is classified under Form builders in the PluginView directory.

How many fingerprint rules cover Inputflow?

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

Illustrative public indicators for Inputflow include script.inputflow.io. A live scan may match additional proprietary rules beyond these examples.