Detect Clickskeks

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

• JavaScript globals

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

• Clickskeks

Establishes

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

Does not establish

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

Can PluginView detect Clickskeks without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Clickskeks — typically javascript globals. It does not bypass authentication or paywalls.

What category is Clickskeks?

Clickskeks is classified under Cookie compliance in the PluginView directory.

How many fingerprint rules cover Clickskeks?

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

What public signals suggest a site uses Clickskeks?

Illustrative public indicators for Clickskeks include Clickskeks. A live scan may match additional proprietary rules beyond these examples.