Detect WebWave

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

• JavaScript globals

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

• webwave.getAppVersion
• webwaveFontsLoadedFlag

Establishes

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

Does not establish

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

Can PluginView detect WebWave without logging in?

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

What category is WebWave?

WebWave is classified under Page builders in the PluginView directory.

How many fingerprint rules cover WebWave?

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

What public signals suggest a site uses WebWave?

Illustrative public indicators for WebWave include webwave.getAppVersion; webwaveFontsLoadedFlag. A live scan may match additional proprietary rules beyond these examples.