Detect Eggplant

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

• Response headers
• Script sources

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

• content-security-policy: .eggplant.cloud
• .eggplant.cloud/

Establishes

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

Does not establish

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

Can PluginView detect Eggplant without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Eggplant — typically response headers, script sources. It does not bypass authentication or paywalls.

What category is Eggplant?

Eggplant is classified under RUM in the PluginView directory.

How many fingerprint rules cover Eggplant?

This reference currently tracks 2 fingerprint rules across response headers, script sources. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Eggplant?

Illustrative public indicators for Eggplant include content-security-policy: .eggplant.cloud; .eggplant.cloud/. A live scan may match additional proprietary rules beyond these examples.