Detect Form.taxi

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

• DOM selectors

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

• form

Establishes

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

Does not establish

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

Can PluginView detect Form.taxi without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Form.taxi — typically dom selectors. It does not bypass authentication or paywalls.

What category is Form.taxi?

Form.taxi is classified under Form builders in the PluginView directory.

How many fingerprint rules cover Form.taxi?

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

What public signals suggest a site uses Form.taxi?

Illustrative public indicators for Form.taxi include form. A live scan may match additional proprietary rules beyond these examples.