Detect EasyBroker

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

• Script sources

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

• .easybroker.com/

Establishes

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

Does not establish

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

Can PluginView detect EasyBroker without logging in?

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

What category is EasyBroker?

EasyBroker is classified under CRM in the PluginView directory.

How many fingerprint rules cover EasyBroker?

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

What public signals suggest a site uses EasyBroker?

Illustrative public indicators for EasyBroker include .easybroker.com/. A live scan may match additional proprietary rules beyond these examples.