Can PluginView detect Proof without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Proof — typically vendor endpoints. It does not bypass authentication or paywalls.

What category is Proof?

Proof is classified under Reviews, Loyalty, Referral & Social Proof in the PluginView directory.

How many fingerprint rules cover Proof?

This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Proof?

Illustrative public indicators for Proof include cdn.useproof.com/proof.js; useproof.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Proof?

For Proof, start with: Landing and ecommerce pages.

Detect Proof

Reviews, Loyalty, Referral & Social Proof

PluginView detects Proof, a Reviews, Loyalty, Referral & Social Proof, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Proof include cdn.useproof.com/proof.js, useproof.com. The listed vendor-controlled browser component was present and active on the scanned page at scan time. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.

Detection looks at vendor endpoints across 2 fingerprint rules among the site's public responses.

Websites using Proof

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Proof

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

cdn.useproof.com/proof.js
useproof.com

What a detection means

Establishes: The listed vendor-controlled browser component was present and active on the scanned page at scan time.
Does not establish: It does not prove a sitewide installation, current commercial contract, backend-only use, exclusive use, or production transaction volume.

Minimum proof rule

Observe a live browser request, loaded script, or iframe to the listed unique vendor endpoint. Source-text-only matches do not qualify.

Best pages to check: Landing and ecommerce pages

How to check a site for Proof

1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Proof signals (prefer: Landing and ecommerce pages).
2. PluginView reads only public responses (vendor endpoints) and scores them against the Proof signature set (2 rules).
3. Review the confidence score and text explanation for Proof on the results page.

FAQ: detecting Proof

Can PluginView detect Proof without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Proof — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Proof?: Proof is classified under Reviews, Loyalty, Referral & Social Proof in the PluginView directory.
How many fingerprint rules cover Proof?: This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses Proof?: Illustrative public indicators for Proof include cdn.useproof.com/proof.js; useproof.com. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Proof?: For Proof, start with: Landing and ecommerce pages.