Our take
Activeregular commits and releases- Activity
- 58
- Community
- 90
- Issues
- 53
- Pull requests
- 48
+64 stars in the last 30 days
- More contributors than 78% of the projects we track
- Slower to close issues than 89% of the projects we track
Certbot is an actively maintained, established ACME client with recent commits and releases, broad contributor participation, and measured issue and pull-request handling activity.
Good fit if
- You administer the web server directly and want a command-line tool to obtain and deploy ACME certificates.
- Your server uses Apache, nginx, webroot validation, or standalone validation.
- You need support for Let’s Encrypt or another ACME-compliant certificate authority.
Look elsewhere if
- You cannot run software on the web server or lack the required administrator access.
- You need a certificate workflow for a hosted service that does not provide direct server access.
All health signals
| Last commit | 2026-10-07 (7 days ago) |
|---|---|
| Commits, last 90 days | 20 |
| Releases, last 12 months | 9 (latest v5.8.0, 2026-09-01) |
| Contributors | 100+ (top contributor: 26% of commits) |
| Issues closed, last 90 days | 37 (typically closed in 168 days) |
| Pull requests merged, last 90 days | 15 (typically merged in 1 day) |
| Project age | 11 years |
Checked on 2026-10-15 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
33,337Forks
3,511Change since Nov 16, 2026: 0 stars·+1 forks
Overview
Certbot is EFF’s command-line client for obtaining and deploying HTTPS certificates. Built around the ACME protocol, it works with Let’s Encrypt and can also act as a client for other ACME-compliant certificate authorities. It addresses the work of getting and maintaining certificates by automating validation and, where supported, server configuration.
It is intended to run on the web server itself, typically with administrator access. Website and server administrators can use it with Apache, nginx, webroot validation, or its standalone validation server. It is not intended for a personal computer without direct access to the target web server.
Key Features
- Obtains domain-validated certificates from Let’s Encrypt or other ACME-compliant services.
- Supports Apache 2.4+, nginx, webroot validation, and standalone validation.
- Generates private keys locally, with ECDSA as the default and RSA also supported.
- Can install an HTTP-to-HTTPS redirect.
- Can revoke certificates.
- Logs configuration changes and can revert them.
- Supports other server software through third-party plugins.
Use Cases
- A web administrator wants to obtain and install a Let’s Encrypt certificate on an Apache or nginx server.
- A site operator wants to automate certificate setup and HTTPS redirects on a server they administer.
- A team needs ACME-based certificate issuance from a certificate authority other than Let’s Encrypt.
- A server administrator needs to prove domain control using webroot files or Certbot’s standalone validation server.
What you need
Detected in the repository
- Python (main language on GitHub)
- A test suite and automated checks on GitHub Actions
Getting Started
Use the interactive guide to get installation and usage instructions for your server configuration. See the user documentation for details.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Alternatives
- reactor-ca: ReactorCA issues certificates from a private CA for homelab and small-office services, rather than obtaining publicly trusted certificates through ACME.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| certbot | Python | – | 33.3k | Active |
| reactor-ca | Go | BSD-2-Clause | 125 | Quiet |
Considerations
Certbot’s intended workflow assumes access to the web server, and the README notes that administrator privileges are needed in most cases. Server software beyond Apache and nginx may require a third-party plugin. The repository metadata does not assert a license, so review the project’s licensing information before adopting or redistributing it.
Found this useful?
Share it with someone who would like certbot.