Detect Jekyll

Establishes

One or more public signals on the scanned page matched a known Jekyll signature at the time of the scan.

Does not establish

A sitewide install of Jekyll, an active vendor contract, exclusive use, or that Jekyll 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 Jekyll signals.
2. 2. PluginView reads only public responses and scores them against proprietary Jekyll fingerprints. Rule bodies and identifiers are not published.
3. 3. Review the confidence score and text explanation for Jekyll on the results page.

A confirmed Jekyll match also implies these technologies are present.

Ruby

Can PluginView detect Jekyll without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Jekyll. It does not bypass authentication or paywalls.

What category is Jekyll?

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

Does PluginView publish Jekyll fingerprint rules?

No. Detection uses proprietary fingerprint rules that are not published. Scan results explain matches in plain language without disclosing rule bodies or identifiers.