Detect bSecure

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

• JavaScript globals

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

• bsecure_js_object

Establishes

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

Does not establish

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

Can PluginView detect bSecure without logging in?

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

What category is bSecure?

bSecure is classified under Payment processors in the PluginView directory.

How many fingerprint rules cover bSecure?

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

What public signals suggest a site uses bSecure?

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