Let's Encrypt Certificates: Free DV & Wildcard (2026)
Let's Encrypt is a free, automated and open certificate authority run by the non-profit ISRG. It issues 90-day DV and wildcard certificates over the ACME protocol — there is no paid tier, no OV/EV and no warranty.
Who is Let's Encrypt?
Let's Encrypt launched in 2015 as a project of the Internet Security Research Group (ISRG) and is sponsored by browsers, CDNs and hosting companies. Its goal is to encrypt the whole web by removing cost and manual steps.
Certificates are issued only through ACME automation — Certbot, acme.sh or your hosting panel. There is no shopping cart, no reseller price list and no human validation, which is why this page shows $0.00 instead of a price table.
Cheapest option by category
Let's Encrypt product matrix & prices (2026)
Let's Encrypt does not sell certificates, so every product below is $0.00. Your real cost is the automation that renews every 60–90 days.
| Product | Validation | Domains | Issuance | Price / yr |
|---|---|---|---|---|
| Let's Encrypt DV (90-day) | DV | Single | Seconds (ACME) | $0.00 |
| Let's Encrypt Wildcard (90-day) | DV | Wildcard | Seconds (ACME) | $0.00 |
Official Let's Encrypt price list
Let's Encrypt does not sell certificates, so there is no official price list and no reseller pricing. Your only cost is hosting plus the automation that renews every 60–90 days. Paying a commercial CA only makes sense when you need OV/EV, a warranty or longer validity.
Free tools for Let's Encrypt
Automate issuance and catch problems before they reach production.
Test HTTP-01 and DNS-01 the way Let's Encrypt does — before you issue.
Issuer, 90-day countdown, chain health and renewal advice in one click.
Confirm your _acme-challenge TXT record reached every resolver.
Will old Android, iOS and embedded devices trust your E5/E6 chain?
Copy-paste Certbot, acme.sh, lego and win-acme commands.
Issuance, validation, warranty, algorithms & compatibility
Sub-brands & product lines
These are the current Let's Encrypt product brands. Availability was checked against the source above — confirm on the reseller/official page before buying.
Alternatives & comparisons
Compare Let's Encrypt with other certificate authorities and certificate types before you buy.
Browse by certificate type
Let's Encrypt FAQ
Is Let's Encrypt really free?
Yes. ISRG funds it through sponsors; there is no paid tier, no per-certificate fee and no upsell. You pay only for your own hosting and automation.
Why do Let's Encrypt certificates expire in 90 days?
Short lifetimes limit the damage of a compromised key and force renewal to be automated. Renew around day 60; ACME clients do this without downtime.
Does Let's Encrypt offer OV or EV certificates?
No. Only domain-validated (DV) and wildcard certificates. If you need organization validation, an EV identity bar or a warranty, use a commercial CA.
Is a Let's Encrypt certificate trusted by browsers?
Yes. ISRG Root X1 and X2 are in all major trust stores. Only very old Android (7.1 and earlier) may need the cross-signed chain, which ACME clients handle automatically.
What are the rate limits?
Roughly 50 certificates per registered domain per week, plus duplicate-certificate limits. The staging environment has much higher limits for testing.
Is Let's Encrypt as good as a paid SSL certificate?
For encryption it is equivalent: the same TLS ciphers, the same browser trust, the same proof of domain control. What you give up is organization validation (OV/EV), a financial warranty, longer validity and vendor support. If your site only needs to prove domain control, a paid DV certificate buys little beyond convenience.
How does Let's Encrypt renewal work?
ACME clients renew automatically around day 60 of the 90-day lifetime. Certbot runs `certbot renew` from cron or a systemd timer; acme.sh and hosting panels work the same way. Renewal repeats the same challenge, so port 80 or your DNS automation must keep working — that is the most common cause of expired certificates.
HTTP-01 or DNS-01: which ACME challenge should I use?
HTTP-01 is the simplest and works for any domain serving port 80, but it cannot issue wildcards. DNS-01 works behind a proxy or on internal hosts and is required for wildcard certificates, at the cost of API access to your DNS provider. Choose DNS-01 for *.example.com or when port 80 is blocked.