Detect Jetpack

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

• Script sources
• DOM selectors

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

• wp-content/plugins/jetpack/
• link

Establishes

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

Does not establish

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

Can PluginView detect Jetpack without logging in?

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

What category is Jetpack?

Jetpack is classified under WordPress plugins in the PluginView directory.

How many fingerprint rules cover Jetpack?

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

What public signals suggest a site uses Jetpack?

Illustrative public indicators for Jetpack include wp-content/plugins/jetpack/; link. A live scan may match additional proprietary rules beyond these examples.