Detect Mapline

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

• Response headers
• DOM selectors

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

• access-control-allow-origin: app.mapline.com
• iframe

Establishes

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

Does not establish

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

Can PluginView detect Mapline without logging in?

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

What category is Mapline?

Mapline is classified under Maps in the PluginView directory.

How many fingerprint rules cover Mapline?

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

Illustrative public indicators for Mapline include access-control-allow-origin: app.mapline.com; iframe. A live scan may match additional proprietary rules beyond these examples.