Detect c/side

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

• Script sources

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

• .cside.dev

Establishes

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

Does not establish

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

Can PluginView detect c/side without logging in?

Yes. PluginView only reads publicly accessible responses when checking for c/side — typically script sources. It does not bypass authentication or paywalls.

What category is c/side?

c/side is classified under Security in the PluginView directory.

How many fingerprint rules cover c/side?

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

What public signals suggest a site uses c/side?

Illustrative public indicators for c/side include .cside.dev. A live scan may match additional proprietary rules beyond these examples.