Detect Uzerly

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

• Response headers
• Script sources

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

• content-security-policy: .uszerly.net
• .userly.net/

Establishes

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

Does not establish

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

Can PluginView detect Uzerly without logging in?

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

What category is Uzerly?

Uzerly is classified under Retargeting in the PluginView directory.

How many fingerprint rules cover Uzerly?

This reference currently tracks 2 fingerprint rules across response headers, script sources. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Uzerly?

Illustrative public indicators for Uzerly include content-security-policy: .uszerly.net; .userly.net/. A live scan may match additional proprietary rules beyond these examples.