Detect Envoy

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

• Response headers

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

• server: envoy
• x-envoy-upstream-service-time

Establishes

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

Does not establish

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

Can PluginView detect Envoy without logging in?

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

What category is Envoy?

Envoy is classified under Reverse proxies in the PluginView directory.

How many fingerprint rules cover Envoy?

This reference currently tracks 2 fingerprint rules across response headers. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Envoy?

Illustrative public indicators for Envoy include server: envoy; x-envoy-upstream-service-time. A live scan may match additional proprietary rules beyond these examples.