Detect Dragon

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

• Response headers
• URL patterns

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

• x-powered-by: Dragon Native
• .*.dgn

Establishes

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

Does not establish

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

A confirmed Dragon match also implies these technologies are present.

Apache HTTP Server

Can PluginView detect Dragon without logging in?

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

What category is Dragon?

Dragon is classified under Programming languages in the PluginView directory.

How many fingerprint rules cover Dragon?

This reference currently tracks 2 fingerprint rules across response headers, url patterns. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Dragon?

Illustrative public indicators for Dragon include x-powered-by: Dragon Native; .*.dgn. A live scan may match additional proprietary rules beyond these examples.