Detect Classnames

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

• Script sources

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

• classnames.?x.chunk?.js

Establishes

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

Does not establish

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

Can PluginView detect Classnames without logging in?

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

What category is Classnames?

Classnames is classified under JavaScript libraries in the PluginView directory.

How many fingerprint rules cover Classnames?

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 Classnames?

Illustrative public indicators for Classnames include classnames.?x.chunk?.js. A live scan may match additional proprietary rules beyond these examples.