Can PluginView detect Consentmanager without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Consentmanager — typically vendor endpoints. It does not bypass authentication or paywalls.

What category is Consentmanager?

Consentmanager is classified under Consent, CAPTCHA & Accessibility in the PluginView directory.

How many fingerprint rules cover Consentmanager?

This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Consentmanager?

Illustrative public indicators for Consentmanager include cdn.consentmanager.net/delivery; consentmanager.net. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Consentmanager?

For Consentmanager, start with: All public pages.

Detect Consentmanager

Consent, CAPTCHA & Accessibility

PluginView detects Consentmanager, a Consent, CAPTCHA & Accessibility, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Consentmanager include cdn.consentmanager.net/delivery, consentmanager.net. The listed vendor-controlled browser component was present and active on the scanned page at scan time. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.

Detection looks at vendor endpoints across 2 fingerprint rules among the site's public responses.

Websites using Consentmanager

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Consentmanager

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

cdn.consentmanager.net/delivery
consentmanager.net

What a detection means

Establishes: The listed vendor-controlled browser component was present and active on the scanned page at scan time.
Does not establish: It does not prove a sitewide installation, current commercial contract, backend-only use, exclusive use, or production transaction volume.

Minimum proof rule

Observe a live browser request, loaded script, or iframe to the listed unique vendor endpoint. Source-text-only matches do not qualify.

Best pages to check: All public pages

How to check a site for Consentmanager

1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Consentmanager signals (prefer: All public pages).
2. PluginView reads only public responses (vendor endpoints) and scores them against the Consentmanager signature set (2 rules).
3. Review the confidence score and text explanation for Consentmanager on the results page.

FAQ: detecting Consentmanager

Can PluginView detect Consentmanager without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Consentmanager — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Consentmanager?: Consentmanager is classified under Consent, CAPTCHA & Accessibility in the PluginView directory.
How many fingerprint rules cover Consentmanager?: This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses Consentmanager?: Illustrative public indicators for Consentmanager include cdn.consentmanager.net/delivery; consentmanager.net. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Consentmanager?: For Consentmanager, start with: All public pages.