Detect Didomi

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

• Vendor endpoints

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

• sdk.didomi.io
• sdk.privacy-center.org

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.

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

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

Can PluginView detect Didomi without logging in?

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

What category is Didomi?

Didomi is classified under Cookie compliance, Consent, CAPTCHA & Accessibility in the PluginView directory.

How many fingerprint rules cover Didomi?

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

Illustrative public indicators for Didomi include sdk.didomi.io; sdk.privacy-center.org. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Didomi?

For Didomi, start with: All public pages.