Detect Mappedin

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

• Response headers

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

• content-security-policy: .mappedin.com

Establishes

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

Does not establish

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

Can PluginView detect Mappedin without logging in?

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

What category is Mappedin?

Mappedin is classified under Maps in the PluginView directory.

How many fingerprint rules cover Mappedin?

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

Illustrative public indicators for Mappedin include content-security-policy: .mappedin.com. A live scan may match additional proprietary rules beyond these examples.