Detect SafeBuy

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

• DOM selectors

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

• a > img

Establishes

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

Does not establish

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

Can PluginView detect SafeBuy without logging in?

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

What category is SafeBuy?

SafeBuy is classified under Reviews in the PluginView directory.

How many fingerprint rules cover SafeBuy?

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

Illustrative public indicators for SafeBuy include a > img. A live scan may match additional proprietary rules beyond these examples.