Detect WP-Statistics

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

• JavaScript globals
• DOM selectors
• HTML markup

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

• WP_Statistics_http
• wps_statistics_object
• link
• <!-- Analytics by WP-Statistics v

Establishes

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

Does not establish

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

Can PluginView detect WP-Statistics without logging in?

Yes. PluginView only reads publicly accessible responses when checking for WP-Statistics — typically javascript globals, dom selectors, html markup. It does not bypass authentication or paywalls.

What category is WP-Statistics?

WP-Statistics is classified under Analytics, WordPress plugins in the PluginView directory.

How many fingerprint rules cover WP-Statistics?

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

What public signals suggest a site uses WP-Statistics?

Illustrative public indicators for WP-Statistics include WP_Statistics_http; wps_statistics_object; link. A live scan may match additional proprietary rules beyond these examples.