Detect Route

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

• Script sources
• JavaScript globals

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

• .routeapp.io/
• Routeapp

Establishes

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

Does not establish

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

Can PluginView detect Route without logging in?

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

What category is Route?

Route is classified under Fulfilment in the PluginView directory.

How many fingerprint rules cover Route?

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

What public signals suggest a site uses Route?

Illustrative public indicators for Route include .routeapp.io/; Routeapp. A live scan may match additional proprietary rules beyond these examples.