Detect Loop Web

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

• Meta tags
• DOM selectors

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

• id: LoopWeb
• link

Establishes

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

Does not establish

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

Can PluginView detect Loop Web without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Loop Web — typically meta tags, dom selectors. It does not bypass authentication or paywalls.

What category is Loop Web?

Loop Web is classified under Development in the PluginView directory.

How many fingerprint rules cover Loop Web?

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

What public signals suggest a site uses Loop Web?

Illustrative public indicators for Loop Web include id: LoopWeb; link. A live scan may match additional proprietary rules beyond these examples.