Detect WeBlocks

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

• Script sources

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

• weblocks.io/

Establishes

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

Does not establish

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

Can PluginView detect WeBlocks without logging in?

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

What category is WeBlocks?

WeBlocks is classified under JavaScript frameworks in the PluginView directory.

How many fingerprint rules cover WeBlocks?

This reference currently tracks 1 fingerprint rule across script sources. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses WeBlocks?

Illustrative public indicators for WeBlocks include weblocks.io/. A live scan may match additional proprietary rules beyond these examples.