Detect CookieYes
PluginView detects CookieYes, a Cookie compliance and Consent, CAPTCHA & Accessibility, by evaluating script sources, javascript globals, dom selectors on publicly reachable pages. Illustrative public indicators associated with CookieYes include app.cookieyes.com/client_data/, cdn-cookieyes.com/client_data/, wp-content/plugins/cookie-law-info/..js?ver=0.0?. 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 script sources, javascript globals, dom selectors across 6 fingerprint rules among the site's public responses.
Websites using CookieYes
Loading website list…
Signal classes
PluginView evaluates public page signals in these classes when identifying CookieYes. Individual fingerprint rule bodies are proprietary and are not published.
- Script sources
- JavaScript globals
- DOM selectors
Example public indicators for CookieYes
Illustrative indicators derived from public catalog metadata for CookieYes. A live scan may match additional proprietary rules beyond these examples.
- app.cookieyes.com/client_data/
- cdn-cookieyes.com/client_data/
- wp-content/plugins/cookie-law-info/..js?ver=0.0?
- cookieYes
- #cookie-law-info-bar
- link
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 CookieYes
- 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest CookieYes signals (prefer: All public pages).
- 2. PluginView reads only public responses (script sources, javascript globals, dom selectors) and scores them against the CookieYes signature set (6 rules).
- 3. Review the confidence score and text explanation for CookieYes on the results page.
FAQ: detecting CookieYes
- Can PluginView detect CookieYes without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for CookieYes — typically script sources, javascript globals, dom selectors. It does not bypass authentication or paywalls.
- What category is CookieYes?
- CookieYes is classified under Cookie compliance, Consent, CAPTCHA & Accessibility in the PluginView directory.
- How many fingerprint rules cover CookieYes?
- This reference currently tracks 6 fingerprint rules across script sources, javascript globals, dom selectors. Individual rule bodies are proprietary and are not published.
- What public signals suggest a site uses CookieYes?
- Illustrative public indicators for CookieYes include app.cookieyes.com/client_data/; cdn-cookieyes.com/client_data/; wp-content/plugins/cookie-law-info/..js?ver=0.0?. A live scan may match additional proprietary rules beyond these examples.
- Which pages are best for detecting CookieYes?
- For CookieYes, start with: All public pages.
