Detect GuardFlame

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

• Response headers

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

• server: GuardFlame

Establishes

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

Does not establish

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

Can PluginView detect GuardFlame without logging in?

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

What category is GuardFlame?

GuardFlame is classified under CDN in the PluginView directory.

How many fingerprint rules cover GuardFlame?

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

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