Detect Chronopost

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

• Page text

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

• \bChronopost\b

Establishes

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

Does not establish

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

Can PluginView detect Chronopost without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Chronopost — typically page text. It does not bypass authentication or paywalls.

What category is Chronopost?

Chronopost is classified under Shipping carriers in the PluginView directory.

How many fingerprint rules cover Chronopost?

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

What public signals suggest a site uses Chronopost?

Illustrative public indicators for Chronopost include \bChronopost\b. A live scan may match additional proprietary rules beyond these examples.