Detect OneTrust

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

• Cookies
• Script sources
• DNS records

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

• OptanonConsent
• cdn.cookielaw.org
• optanon.blob.core.windows.net
• otSDKStub.js
• TXT: onetrust-domain-verification=

Establishes

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

Does not establish

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

Can PluginView detect OneTrust without logging in?

Yes. PluginView only reads publicly accessible responses when checking for OneTrust — typically cookies, script sources, dns records. It does not bypass authentication or paywalls.

What category is OneTrust?

OneTrust is classified under Cookie compliance in the PluginView directory.

How many fingerprint rules cover OneTrust?

This reference currently tracks 7 fingerprint rules across cookies, script sources, dns records. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses OneTrust?

Illustrative public indicators for OneTrust include OptanonConsent; cdn.cookielaw.org; optanon.blob.core.windows.net. A live scan may match additional proprietary rules beyond these examples.