Detect Meltwater

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

• Response headers
• DOM selectors

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

• content-security-policy: .meltwater.com
• iframe

Establishes

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

Does not establish

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

Can PluginView detect Meltwater without logging in?

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

What category is Meltwater?

Meltwater is classified under Analytics in the PluginView directory.

How many fingerprint rules cover Meltwater?

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 Meltwater?

Illustrative public indicators for Meltwater include content-security-policy: .meltwater.com; iframe. A live scan may match additional proprietary rules beyond these examples.