Detect OpenResty

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

• Response headers

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

• server: openresty/?

Establishes

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

Does not establish

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

A confirmed OpenResty match also implies these technologies are present.

Nginx

Can PluginView detect OpenResty without logging in?

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

What category is OpenResty?

OpenResty is classified under Web servers in the PluginView directory.

How many fingerprint rules cover OpenResty?

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 OpenResty?

Illustrative public indicators for OpenResty include server: openresty/?. A live scan may match additional proprietary rules beyond these examples.