Detect Omie

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

• Meta tags
• JavaScript globals

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

• author: Omie
• omieInit

Establishes

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

Does not establish

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

Can PluginView detect Omie without logging in?

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

What category is Omie?

Omie is classified under Ecommerce in the PluginView directory.

How many fingerprint rules cover Omie?

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

What public signals suggest a site uses Omie?

Illustrative public indicators for Omie include author: Omie; omieInit. A live scan may match additional proprietary rules beyond these examples.