Detect PagSeguro

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

• Script sources
• JavaScript globals
• DOM selectors

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

• .pagseguro.uol.com.br/
• PagSeguroDirectPayment
• _PagSeguroDirectPayment
• form

Establishes

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

Does not establish

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

Can PluginView detect PagSeguro without logging in?

Yes. PluginView only reads publicly accessible responses when checking for PagSeguro — typically script sources, javascript globals, dom selectors. It does not bypass authentication or paywalls.

What category is PagSeguro?

PagSeguro is classified under Payment processors in the PluginView directory.

How many fingerprint rules cover PagSeguro?

This reference currently tracks 4 fingerprint rules across script sources, javascript globals, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses PagSeguro?

Illustrative public indicators for PagSeguro include .pagseguro.uol.com.br/; PagSeguroDirectPayment; _PagSeguroDirectPayment. A live scan may match additional proprietary rules beyond these examples.