Detect OpenElement

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

• Meta tags
• JavaScript globals

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

• generator: openElement
• OE.GETools
• OEConfWEMenu

Establishes

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

Does not establish

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

A confirmed OpenElement match also implies these technologies are present.

PHP

Can PluginView detect OpenElement without logging in?

Yes. PluginView only reads publicly accessible responses when checking for OpenElement — typically meta tags, javascript globals. It does not bypass authentication or paywalls.

What category is OpenElement?

OpenElement is classified under CMS in the PluginView directory.

How many fingerprint rules cover OpenElement?

This reference currently tracks 3 fingerprint rules across meta tags, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses OpenElement?

Illustrative public indicators for OpenElement include generator: openElement; OE.GETools; OEConfWEMenu. A live scan may match additional proprietary rules beyond these examples.