Detect Let's Encrypt

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

• TLS certificate issuer

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

• Let's Encrypt

Establishes

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

Does not establish

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

Can PluginView detect Let's Encrypt without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Let's Encrypt — typically tls certificate issuer. It does not bypass authentication or paywalls.

What category is Let's Encrypt?

Let's Encrypt is classified under SSL/TLS certificate authorities in the PluginView directory.

How many fingerprint rules cover Let's Encrypt?

This reference currently tracks 1 fingerprint rule across tls certificate issuer. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Let's Encrypt?

Illustrative public indicators for Let's Encrypt include Let's Encrypt. A live scan may match additional proprietary rules beyond these examples.