Let's Encrypt: Frequently Asked Questions

Modified on Fri, Nov 20 at 11:13 AM

Let's Encrypt: Frequently Asked Questions

Our websites and services use TLS certificates issued by Let's Encrypt to encrypt the connection between your browser and our servers. We are moving all customer domains to Let's Encrypt certificates that are issued and renewed automatically on our Cloudflare edge, replacing certificates that customers provide or that we upload manually. The answers below explain who Let's Encrypt is and why you can rely on its certificates.

What is Let's Encrypt?

Let's Encrypt is a nonprofit certificate authority (CA) that issues free TLS certificates, the technology behind the padlock and "https://" in your browser. A certificate proves a website is who it says it is and lets your browser set up an encrypted connection to it.

Let's Encrypt is run by the Internet Security Research Group (ISRG), a 501(c)(3) public benefit organization focused on a more secure, privacy-respecting Internet. It began issuing certificates in 2015 and today secures more than 700 million websites, making it the largest certificate authority in the world. (Let's Encrypt, University of Michigan)

What makes it different from traditional CAs:

  • Free: there is no charge for certificates, which removes cost as a barrier to encryption.

  • Automated: certificates are requested and renewed by software using an open standard called ACME, so they don't lapse because someone forgot to renew them.

  • Open: its protocols and software are public, and every certificate it issues is published for anyone to inspect.


Why is Let's Encrypt trustworthy?

Let's Encrypt certificates are trusted by every major browser and operating system, and they meet the same security rules as certificates from paid providers. Here is why.

  • Trusted by every major platform. Since July 2018, Let's Encrypt's root certificate (ISRG Root X1) has been directly trusted by all major root programs, including Microsoft, Google, Apple, Mozilla and Oracle. Before that, it was trusted through a cross-signature from the established CA IdenTrust, so its certificates have worked in mainstream browsers since day one. (Let's Encrypt)

  • Held to the same rules as every public CA. Let's Encrypt must follow the CA/Browser Forum Baseline Requirements, the industry standard every publicly trusted CA follows. Independent auditors review its operations each year against the WebTrust criteria, and it publishes the results. (ISRG WebTrust report)

  • The same strength of encryption. A free certificate encrypts your connection exactly as well as a paid one. Your browser shows the same padlock and makes no distinction between them.

  • Every certificate is public. Each certificate Let's Encrypt issues is recorded in public Certificate Transparency logs, so anyone can check that no certificate was issued for a domain without the owner's knowledge.

  • Short lifetimes limit risk. Certificates are valid for 90 days today, dropping to 64 days in February 2027 and 45 days in February 2028, in line with new industry rules. A shorter lifetime limits the damage if a key is ever compromised, and automatic renewal keeps sites secure without gaps. (ISRG)

  • Nonprofit governance. ISRG has no owners and no profit motive. It was set up as a nonprofit to keep it transparent and focused on serving the public over the long term. (University of Michigan)


How are certificates rotated?

Certificate rotation is fully automatic: our Cloudflare integration requests, validates and renews each Let's Encrypt certificate on our edge, with no action needed from you in most cases.

  • Issuance: when your domain is added to our platform, Cloudflare acts as the certificate client, proves control of the domain to Let's Encrypt, and installs the certificate on our edge. Most validations finish within minutes. (Cloudflare)

  • Renewal: certificates become eligible for renewal 30 days before they expire. For domains routed through our edge, Cloudflare completes validation and swaps in the new certificate on its own, so there is no downtime and no gap in coverage. (Cloudflare)

  • Retries and monitoring: if a validation attempt fails, Cloudflare retries on a set schedule, and we receive alerts for certificates approaching renewal so we can step in early.

  • Shorter lifetimes are handled for you: as Let's Encrypt moves to 64-day and then 45-day certificates, renewals simply happen more often. Nothing changes on your side.

  • When we may need your help: if your domain is a wildcard, or its DNS does not point to our edge, renewal needs a validation record (TXT or HTTP token) added to your DNS. We will send you the exact record if this applies.


You no longer need to send us certificate files or track expiration dates. Keep your domain's DNS pointed at our edge and renewals take care of themselves.

Do I need to add a CAA record to my DNS?

Only if your domain already has CAA records. In that case, you need to add a record that allows Let's Encrypt, or Cloudflare cannot issue a certificate for your domain on our behalf.

A Certificate Authority Authorization (CAA) record is a DNS setting that lists which certificate authorities may issue certificates for your domain. If your domain has no CAA records, any CA may issue and no change is needed. If it has CAA records that don't include Let's Encrypt, issuance and renewal will fail. (Cloudflare)

To check, look up your domain's CAA records with your DNS provider or a tool such as dig CAA yourdomain.com. If any are listed, add these two records alongside your existing ones:


blendCNAME.yourdomain.com.  IN  CAA  0 issue "letsencrypt.org"
blendCNAME.yourdomain.com.  IN  CAA  0 issuewild "letsencrypt.org"


CAA records are usually set at the top level of your domain (for example, yourdomain.com), but they can also exist on a subdomain, and they apply to every subdomain below them. Check both the domain you use with us and its parent domain. (Cloudflare)


Need help? If you're not sure whether your domain has CAA records, or your certificate isn't issuing after you've made the change, contact our support team and we'll help you get it sorted.

Sources

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article