deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

Public TLS certificates capped at 100 days from March 15, 2027

The CA/Browser Forum's phased cut to TLS certificate validity reaches 100 days on March 15, 2027 and 47 days in 2029, making once-a-year manual renewal unsustainable.

Public TLS certificates capped at 100 days from March 15, 2027

What changes, and when

According to a checklist published on dev.to, the CA/Browser Forum has voted to shorten the maximum lifetime of publicly trusted TLS certificates in three steps. Certificates issued since March 15, 2026 are capped at 200 days. From March 15, 2027 the ceiling drops to 100 days, and from March 15, 2029 it falls again to 47 days. The proof of domain control that certificate authorities accept also gets a shorter shelf life, down to 10 days by 2029.

The arithmetic is unforgiving. A certificate renewed by hand once a year already cannot keep up; at 100 days each hostname needs a renewal roughly four times a year, and at 47 days nearly eight times. Renewal has to become a background process rather than a calendar entry.

Who feels it first

Sites with working automation will largely sail through. What breaks, the dev.to post argues, is the long tail of exceptions: the ageing VPS nobody decommissioned, the client who bought a certificate independently, the mail server, the staging box that quietly became production. One forgotten certificate is a single incident; an agency running 80 client sites, each with a different host, DNS provider and renewal method, turns the same rule into a steady stream of support tickets.

A practical checklist

The post lays out a preparation sequence that can be started now:

  • Inventory every certificate you are responsible for, not just the websites: apex and www, API hostnames, SMTP and IMAP endpoints, admin panels, and anything sitting behind a load balancer or CDN.
  • Record how each one is renewed — automatic ACME tooling such as certbot, acme.sh, Caddy or the host's own panel, or by hand. Every manual entry is a future outage.
  • Migrate the manual ones to ACME. DNS-01 validation also covers wildcard certificates and servers that cannot open port 80.
  • Confirm that a successful renewal actually reloads the service. A fresh certificate sitting on disk while nginx or Apache keeps serving the old one is described as the classic failure mode.
  • Decide in advance who is alerted when a renewal fails, and through which channel; an email to a mailbox nobody reads does not count as an alert.
  • Check expiry from the outside, the way a visitor's browser sees it. What your server reports and what the public internet is served can diverge — a wrong certificate on a CDN, or a forgotten copy on another IP.
  • Re-run the checks after every migration, DNS change, new host or new CDN.

Any monitoring tool that probes from outside will do the job, the author notes; what matters is that someone is watching and gets warned before expiry rather than after.

Why it matters

The March 2027 step turns certificate automation from a nice-to-have into an operational requirement for anyone running public infrastructure. Agencies and hosts with mixed client estates face the largest cleanup, and the inventory step is the one that reliably surfaces forgotten certificates. Shorter lifetimes also shrink the window in which a stolen key or a misissued certificate can be abused, which is the trade the industry has accepted: more renewal churn in exchange for less exposure. The deadline is still months away, but the work — listing, automating, testing reloads and alerts — is exactly the kind that slips when it is left until the last minute.

  • #tls
  • #security
  • #certificates
  • #acme
  • #web

Related posts