Certamira
Independent reseller and guide. Not a certificate authority and not affiliated with any certificate authority.

Free Let's Encrypt or a paid wildcard: when each fits

Let's Encrypt issues wildcard certificates but only with DNS-01 validation. Its certificates last 90 days. If you can automate DNS and renewal, free is enough. A paid wildcard helps when you cannot automate or need support. The same public lifetime caps apply either way, so a paid certificate does not remove the need to renew on schedule.

Does Let's Encrypt issue wildcard certificates?

Yes, Let's Encrypt issues wildcard certificates, and only with DNS-01 validation, which is a TXT record in DNS for the name you are requesting. The client or a person must publish that record before issuance. A wildcard covers one level of subdomains only, so a name like *.example.com covers www.example.com and does not cover one more label under a subdomain.

How long do certificates last?

Let's Encrypt uses a default lifetime of 90 days, and renewal is advised every 60 days so a failed run can be fixed before expiry. The CA/Browser Forum Baseline Requirements v2.2.7 set the public maximum in section 6.3.2. It is 200 days from 15 March 2026. It drops to 100 days on 15 March 2027 and to 47 days on 15 March 2029. Paid certificates are bound by the same lifetime caps. A paid certificate does not remove the need to renew on schedule.

When is free enough?

Free is enough when a client can publish the TXT record, request the certificate, and repeat that work on a schedule you already trust. You store the private key where you store other secrets, and you install the new files on each service that presents them. If issuance fails, you fix DNS, the client or the account. Then you run the job again. No vendor sits in the path.

Ask yourself:

  1. Can I change DNS records by API or script?
  2. Can I run a renewal client on a schedule?
  3. Do I run more than one server that needs the key?
  4. Do I need vendor support if issuance fails?
  5. Do I need to finish validation by hand?

Yes to the first two questions and no to the last two means free is enough, while yes to the third means you copy the key and certificate to each server, or issue per server, which is key handling and not a reason by itself to pay.

When is a paid wildcard easier?

A paid wildcard is easier when DNS changes and validation stay manual, because every renewal then waits on a person to publish the TXT record and finish the order. It is also easier when you need vendor support if issuance fails and you want a contact who can look at that order with you. The certificate still follows the public lifetime caps, and you still place the key on every server that must present it. Support can explain a failure, and it does not retire the renewal schedule.

What changes with 100-day certificates?

From 15 March 2027 the maximum lifetime of a public TLS certificate is 100 days, and from 15 March 2029 it is 47 days. Section 4.2.1 limits how long domain validation can be reused. The limit is 200 days now. It falls to 100 days on 15 March 2027 and to 10 days on 15 March 2029. After that reuse window the authority must validate the name again, and for a Let's Encrypt wildcard that validation is still DNS-01. Hand steps therefore return sooner and more frequently if you cannot script them, whether or not you pay, and a paid wildcard does not lift these caps or these reuse limits.

Checked on 4 November 2026. Source: CA/Browser Forum Baseline Requirements v2.2.7; Let's Encrypt documentation.