Detect Clorder

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

• Inline scripts

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

• api.clorder.com

Establishes

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

Does not establish

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

Can PluginView detect Clorder without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Clorder — typically inline scripts. It does not bypass authentication or paywalls.

What category is Clorder?

Clorder is classified under Reservations & delivery in the PluginView directory.

How many fingerprint rules cover Clorder?

This reference currently tracks 1 fingerprint rule across inline scripts. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Clorder?

Illustrative public indicators for Clorder include api.clorder.com. A live scan may match additional proprietary rules beyond these examples.