Detect Re:amaze

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

• Script sources
• JavaScript globals

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

• .reamaze.com/
• reamaze.version:

Establishes

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

Does not establish

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

Can PluginView detect Re:amaze without logging in?

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

What category is Re:amaze?

Re:amaze is classified under Live chat in the PluginView directory.

How many fingerprint rules cover Re:amaze?

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 Re:amaze?

Illustrative public indicators for Re:amaze include .reamaze.com/; reamaze.version:. A live scan may match additional proprietary rules beyond these examples.