Detect Chronofresh

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

• Page text

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

• \bChronofresh\b

Establishes

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

Does not establish

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

Can PluginView detect Chronofresh without logging in?

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

What category is Chronofresh?

Chronofresh is classified under Shipping carriers in the PluginView directory.

How many fingerprint rules cover Chronofresh?

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

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