Detect Naviga

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

• Script sources
• DOM selectors

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

• .infomaker.io/
• link

Establishes

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

Does not establish

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

Can PluginView detect Naviga without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Naviga — typically script sources, dom selectors. It does not bypass authentication or paywalls.

What category is Naviga?

Naviga is classified under CMS in the PluginView directory.

How many fingerprint rules cover Naviga?

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

What public signals suggest a site uses Naviga?

Illustrative public indicators for Naviga include .infomaker.io/; link. A live scan may match additional proprietary rules beyond these examples.