Detect Weply

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

• Script sources
• JavaScript globals

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

• app.weply.chat/
• weply

Establishes

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

Does not establish

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

Can PluginView detect Weply without logging in?

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

What category is Weply?

Weply is classified under Live chat in the PluginView directory.

How many fingerprint rules cover Weply?

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

Illustrative public indicators for Weply include app.weply.chat/; weply. A live scan may match additional proprietary rules beyond these examples.