Detect Angie

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

• Response headers

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

• server: Angie/?

Establishes

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

Does not establish

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

A confirmed Angie match also implies these technologies are present.

PerlC

Can PluginView detect Angie without logging in?

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

What category is Angie?

Angie is classified under Web servers in the PluginView directory.

How many fingerprint rules cover Angie?

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

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