Detect Ripple

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

• Response headers

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

• x-sdp-app-type: ripple

Establishes

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

Does not establish

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

A confirmed Ripple match also implies these technologies are present.

Nuxt.jsVue.jsDrupal

Can PluginView detect Ripple without logging in?

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

What category is Ripple?

Ripple is classified under JavaScript frameworks in the PluginView directory.

How many fingerprint rules cover Ripple?

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

What public signals suggest a site uses Ripple?

Illustrative public indicators for Ripple include x-sdp-app-type: ripple. A live scan may match additional proprietary rules beyond these examples.