Detect ExpressionEngine

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

• Cookies

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

• exp_csrf_token
• exp_last_activity
• exp_tracker

Establishes

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

Does not establish

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

A confirmed ExpressionEngine match also implies these technologies are present.

PHP

Can PluginView detect ExpressionEngine without logging in?

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

What category is ExpressionEngine?

ExpressionEngine is classified under CMS in the PluginView directory.

How many fingerprint rules cover ExpressionEngine?

This reference currently tracks 3 fingerprint rules across cookies. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses ExpressionEngine?

Illustrative public indicators for ExpressionEngine include exp_csrf_token; exp_last_activity; exp_tracker. A live scan may match additional proprietary rules beyond these examples.