Detect Wabi

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

• Script sources
• JavaScript globals

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

• .wabi-app.com/
• Wabi

Establishes

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

Does not establish

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

Can PluginView detect Wabi without logging in?

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

What category is Wabi?

Wabi is classified under CRM in the PluginView directory.

How many fingerprint rules cover Wabi?

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

What public signals suggest a site uses Wabi?

Illustrative public indicators for Wabi include .wabi-app.com/; Wabi. A live scan may match additional proprietary rules beyond these examples.