Detect Hyperlane

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

• Script sources
• Inline scripts

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

• .hyperlane.co/

Establishes

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

Does not establish

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

Can PluginView detect Hyperlane without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Hyperlane — typically script sources, inline scripts. It does not bypass authentication or paywalls.

What category is Hyperlane?

Hyperlane is classified under Hosting in the PluginView directory.

How many fingerprint rules cover Hyperlane?

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

What public signals suggest a site uses Hyperlane?

Illustrative public indicators for Hyperlane include .hyperlane.co/. A live scan may match additional proprietary rules beyond these examples.