Detect CloudCannon

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

• Response headers
• DOM selectors

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

• cc-build-id: 0
• , a

Establishes

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

Does not establish

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

Can PluginView detect CloudCannon without logging in?

Yes. PluginView only reads publicly accessible responses when checking for CloudCannon — typically response headers, dom selectors. It does not bypass authentication or paywalls.

What category is CloudCannon?

CloudCannon is classified under CMS in the PluginView directory.

How many fingerprint rules cover CloudCannon?

This reference currently tracks 2 fingerprint rules across response headers, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses CloudCannon?

Illustrative public indicators for CloudCannon include cc-build-id: 0; , a. A live scan may match additional proprietary rules beyond these examples.