Can PluginView detect Zeabur without logging in?

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

What category is Zeabur?

Zeabur is classified under PaaS in the PluginView directory.

How many fingerprint rules cover Zeabur?

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

What public signals suggest a site uses Zeabur?

Illustrative public indicators for Zeabur include x-zeabur-request-id. A live scan may match additional proprietary rules beyond these examples.

Detect Zeabur

PaaS

Zeabur is a platform for running full stack apps and databases.

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

Websites using Zeabur

Loading website list…

Signal classes

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

Response headers

Example public indicators for Zeabur

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

x-zeabur-request-id

What a detection means

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

How to check a site for Zeabur

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

FAQ: detecting Zeabur

Can PluginView detect Zeabur without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Zeabur — typically response headers. It does not bypass authentication or paywalls.
What category is Zeabur?: Zeabur is classified under PaaS in the PluginView directory.
How many fingerprint rules cover Zeabur?: This reference currently tracks 1 fingerprint rule across response headers. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses Zeabur?: Illustrative public indicators for Zeabur include x-zeabur-request-id. A live scan may match additional proprietary rules beyond these examples.