Detect Gloo

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

• Script sources
• JavaScript globals

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

• .gloo.us/
• __GLOO_ONLINE

Establishes

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

Does not establish

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

Can PluginView detect Gloo without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Gloo — typically script sources, javascript globals. It does not bypass authentication or paywalls.

What category is Gloo?

Gloo is classified under CRM in the PluginView directory.

How many fingerprint rules cover Gloo?

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

What public signals suggest a site uses Gloo?

Illustrative public indicators for Gloo include .gloo.us/; __GLOO_ONLINE. A live scan may match additional proprietary rules beyond these examples.