Detect eola

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

• Cookies
• DOM selectors

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

• _eola_session_eola
• link

Establishes

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

Does not establish

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

Can PluginView detect eola without logging in?

Yes. PluginView only reads publicly accessible responses when checking for eola — typically cookies, dom selectors. It does not bypass authentication or paywalls.

What category is eola?

eola is classified under Appointment scheduling in the PluginView directory.

How many fingerprint rules cover eola?

This reference currently tracks 2 fingerprint rules across cookies, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses eola?

Illustrative public indicators for eola include _eola_session_eola; link. A live scan may match additional proprietary rules beyond these examples.