Detect Uniconsent

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

• Script sources

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

• cmp.uniconsent.mgr.consensu.org/

Establishes

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

Does not establish

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

Can PluginView detect Uniconsent without logging in?

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

What category is Uniconsent?

Uniconsent is classified under Cookie compliance in the PluginView directory.

How many fingerprint rules cover Uniconsent?

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

Illustrative public indicators for Uniconsent include cmp.uniconsent.mgr.consensu.org/. A live scan may match additional proprietary rules beyond these examples.