Detect Pelican

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

• HTML markup

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

• poweredbuiltgenerated bywith.*?<a href ?= ?"*getpelican.compelican-boot…

Establishes

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

Does not establish

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

A confirmed Pelican match also implies these technologies are present.

Python

Can PluginView detect Pelican without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Pelican — typically html markup. It does not bypass authentication or paywalls.

What category is Pelican?

Pelican is classified under Static site generator in the PluginView directory.

How many fingerprint rules cover Pelican?

This reference currently tracks 1 fingerprint rule across html markup. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Pelican?

Illustrative public indicators for Pelican include poweredbuiltgenerated bywith.*?<a href ?= ?"*getpelican.compelican-boot…. A live scan may match additional proprietary rules beyond these examples.