Detect Mginex

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

• Meta tags
• Script sources

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

• description: Mginex
• api.mginex.com/

Establishes

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

Does not establish

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

Can PluginView detect Mginex without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Mginex — typically meta tags, script sources. It does not bypass authentication or paywalls.

What category is Mginex?

Mginex is classified under Ecommerce in the PluginView directory.

How many fingerprint rules cover Mginex?

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

What public signals suggest a site uses Mginex?

Illustrative public indicators for Mginex include description: Mginex; api.mginex.com/. A live scan may match additional proprietary rules beyond these examples.