A ctlplne studio product
22 October 2026 · 3 min read

What breaks on 15 March 2027

The 47-day date gets the headlines, but the step that breaks most processes is the one in between. On 15 March 2027 a certificate lives 100 days at most, and a passed domain-validation check is reused for 100 days at most. Quarterly stops being a cadence.

The 47-day scheduleRenewal automationDiscovery and inventory

The step

The CA/Browser Forum's schedule has three cuts. The first, to 200 days, is already in effect. The second, on 15 March 2027, takes the maximum lifetime of a publicly trusted certificate to 100 days and the reuse of domain-control validation to 100 days. The third, on 15 March 2029, takes them to 47 and 10.1

Renewals in one year for 200-day, 100-day and 47-day certificates when renewing at two-thirds of lifetime issued3 months6 months9 months1 year 200-daytoday: 2 to 3 a year 100-dayMarch 2027: 5 to 6 47-dayMarch 2029: 11 to 12
Renewals per certificate per year, renewing when a third of the lifetime is left, as Let's Encrypt recommends.2 The middle row is March 2027.

Let's Encrypt moves a month early: from 10 February 2027, its default certificate lasts 64 days.7 Anyone renewing on a fixed interval instead of a fraction of the lifetime finds out in February, not March.

What stops working

  • The quarterly change ticket. A 100-day certificate renewed at two-thirds of its life is renewed every 67 days. A change process with a two-week lead time now spends a fifth of every cycle in review.
  • The 30-day expiry alert. On a one-year certificate, 30 days out was early. On a 100-day certificate it fires with 70 percent of the life gone, after the renewal should already have happened. Alerts have to move to a fraction of lifetime, not a number of days.
  • Validation by hand. A domain-control check passes for 100 days. Every name is re-proven three to four times a year, and by 2029 at every renewal, since a check then lasts only ten days.1 The DNS or HTTP challenge has to be automated or the renewal is.
  • Appliances with an upload button. The load balancer, the VPN concentrator, the mail gateway: anything renewed by a person pasting a certificate into a form gets that job six times a year, then twelve.
  • Vendor-managed certificates. The SaaS integration, the partner gateway, the managed service that "handles certificates": ask each one how, in writing, before March.

The checklist, in order

  1. Inventory complete, with an owner per certificate. Nothing else works without it.
  2. Every public certificate on an automated path: an ACME client on the host, or a control plane that drives issuance and deployment.
  3. Domain validation automated for every public name, DNS-based where a wildcard or an unreachable host demands it.3
  4. Alert thresholds expressed as a fraction of lifetime, and a renewal window that the authority's own advice sets, through ACME Renewal Information.4
  5. Appliances and vendor certificates listed with a named path off manual renewal, or a documented exception.

None of this is speculative. Let's Encrypt already offers a 45-day server certificate profile today,5 so the operating model of 2029 exists now for anyone who wants to rehearse it.

trstctl was built around this schedule: discovery with owners, ACME on both sides, DNS validation through the common providers, renewal on policy ahead of the deadline, and deployment connectors for the servers and appliances that still need a file and a reload.6

Sources

  1. CA/Browser Forum, TLS Baseline Requirements, version 2.3.1, section 6.3.2 and section 4.2.1.
  2. Let's Encrypt, Integration Guide, "When to renew".
  3. CA/Browser Forum, Baseline Requirements section 3.2.2.4: the HTTP and TLS-ALPN methods cannot validate wildcard names; Let's Encrypt, FAQ: wildcards require the DNS-01 challenge.
  4. IETF, RFC 9773: ACME Renewal Information (ARI).
  5. Let's Encrypt, Profiles: the tlsserver profile has a 45-day validity.
  6. trstctl documentation, ACME and DNS and Deployment connectors.
  7. Let's Encrypt, 64-Day Certificate Lifetimes Coming Feb 2027, 7 October 2026: 64-day certificates by default from 10 February 2027.