Detect Lagoon

PaaS

The Open Source Application Delivery Platform for Kubernetes.

Detection looks at response headers across 2 fingerprint rules among the site's public responses.

01

Websites using Lagoon

Loading website list…

02

Signal classes

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

  • Response headers
03

Example public indicators for Lagoon

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

  • x-lagoon
04

What a detection means

Establishes
One or more public signals on the scanned page matched a known Lagoon signature (2 rules) at the time of the scan.
Does not establish
A sitewide install of Lagoon, an active vendor contract, exclusive use, or that Lagoon is still in place today.
05

How to check a site for Lagoon

  1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Lagoon signals.
  2. 2. PluginView reads only public responses (response headers) and scores them against the Lagoon signature set (2 rules).
  3. 3. Review the confidence score and text explanation for Lagoon on the results page.
06

FAQ: detecting Lagoon

Can PluginView detect Lagoon without logging in?
Yes. PluginView only reads publicly accessible responses when checking for Lagoon — typically response headers. It does not bypass authentication or paywalls.
What category is Lagoon?
Lagoon is classified under PaaS in the PluginView directory.
How many fingerprint rules cover Lagoon?
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 Lagoon?
Illustrative public indicators for Lagoon include x-lagoon. A live scan may match additional proprietary rules beyond these examples.

More in PaaS

View category →