Detect ScapBot

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

• DOM selectors

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

• script

Establishes

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

Does not establish

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

Can PluginView detect ScapBot without logging in?

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

What category is ScapBot?

ScapBot is classified under Development in the PluginView directory.

How many fingerprint rules cover ScapBot?

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

What public signals suggest a site uses ScapBot?

Illustrative public indicators for ScapBot include script. A live scan may match additional proprietary rules beyond these examples.