Detect DigitalRiver

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

• Cookies
• Script sources
• JavaScript globals

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

• X-DR-SHOPPER-ets
• X-DR-THEME: 0
• .digitalriver.com/
• DigitalRiver

Establishes

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

Does not establish

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

Can PluginView detect DigitalRiver without logging in?

Yes. PluginView only reads publicly accessible responses when checking for DigitalRiver — typically cookies, script sources, javascript globals. It does not bypass authentication or paywalls.

What category is DigitalRiver?

DigitalRiver is classified under Ecommerce, Payment processors in the PluginView directory.

How many fingerprint rules cover DigitalRiver?

This reference currently tracks 4 fingerprint rules across cookies, script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses DigitalRiver?

Illustrative public indicators for DigitalRiver include X-DR-SHOPPER-ets; X-DR-THEME: 0; .digitalriver.com/. A live scan may match additional proprietary rules beyond these examples.