Detect Replo

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

• Script sources
• DOM selectors

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

• replocdn.com/
• div
• script

Establishes

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

Does not establish

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

Can PluginView detect Replo without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Replo — typically script sources, dom selectors. It does not bypass authentication or paywalls.

What category is Replo?

Replo is classified under Page builders in the PluginView directory.

How many fingerprint rules cover Replo?

This reference currently tracks 3 fingerprint rules across script sources, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Replo?

Illustrative public indicators for Replo include replocdn.com/; div; script. A live scan may match additional proprietary rules beyond these examples.