Detect Dokeos

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

• Response headers
• Meta tags
• HTML markup

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

• x-powered-by: Dokeos
• generator: Dokeos
• Portal <a>Dokeos@import "dokeos_blue

Establishes

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

Does not establish

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

A confirmed Dokeos match also implies these technologies are present.

PHPXajaxjQuery

Can PluginView detect Dokeos without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Dokeos — typically response headers, meta tags, html markup. It does not bypass authentication or paywalls.

What category is Dokeos?

Dokeos is classified under LMS in the PluginView directory.

How many fingerprint rules cover Dokeos?

This reference currently tracks 3 fingerprint rules across response headers, meta tags, html markup. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Dokeos?

Illustrative public indicators for Dokeos include x-powered-by: Dokeos; generator: Dokeos; Portal <a>Dokeos@import "dokeos_blue. A live scan may match additional proprietary rules beyond these examples.