Detect Jadu

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

• Response headers
• DOM selectors

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

• node: jadu-web-1

Establishes

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

Does not establish

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

Can PluginView detect Jadu without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Jadu — typically response headers, dom selectors. It does not bypass authentication or paywalls.

What category is Jadu?

Jadu is classified under CMS in the PluginView directory.

How many fingerprint rules cover Jadu?

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

What public signals suggest a site uses Jadu?

Illustrative public indicators for Jadu include node: jadu-web-1. A live scan may match additional proprietary rules beyond these examples.