Detect Distributor

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

• Response headers
• Script sources

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

• x-distributor: yes
• wp-content/plugins/distributor

Establishes

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

Does not establish

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

Can PluginView detect Distributor without logging in?

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

What category is Distributor?

Distributor is classified under WordPress plugins in the PluginView directory.

How many fingerprint rules cover Distributor?

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

Illustrative public indicators for Distributor include x-distributor: yes; wp-content/plugins/distributor. A live scan may match additional proprietary rules beyond these examples.