A ctlplne studio product
Topic · 12 posts

The 47-day schedule

The CA/Browser Forum is cutting public TLS certificates to 47 days by March 2029, and domain validation to ten. What each step breaks, and how to make it a non-event.

  1. 22 October 2026 · 3 min read

    Six-day and IP certificates: what they are for

    Let's Encrypt now issues certificates that live under a week and certificates for bare IP addresses. Neither is a curiosity. What each one is for, what it costs to run, and the profile menu that lets you choose.

    The 47-day scheduleRenewal automationPrivate PKI

  2. 22 October 2026 · 3 min read

    Revocation is dead. Long live short lifetimes.

    The largest certificate authority switched off OCSP. Chrome stopped asking long ago. Firefox replaced it with a local list. The industry's honest answer to a revocation check that never worked is a certificate that expires before anyone needs to revoke it.

    PKI fundamentalsThe 47-day schedulePrivate PKI

  3. 22 October 2026 · 3 min read

    What an MSP does with 300 customers' certificates

    For a managed service provider the 47-day schedule is not a chore, it is a capacity problem: a book of business becomes tens of thousands of renewals a week. What one control plane for many customers has to guarantee, and the isolation you can prove rather than promise.

    The 47-day scheduleRenewal automationAudit and ownershipSelf-hosting

  4. 22 October 2026 · 3 min read

    The wildcard six teams share

    One certificate, six owners, zero accountability, and from 2029 twelve simultaneous renewals a year across every host that holds a copy. What a wildcard really is, when it is still the right tool, and how to stop it being the outage nobody can explain.

    Discovery and inventoryKey protectionAudit and ownershipThe 47-day schedule

  5. 22 October 2026 · 3 min read

    Let the CA tell you when to renew

    ACME Renewal Information is the small protocol extension that turns renewal from a guess into an instruction: the authority publishes a window per certificate, and can pull it forward when something goes wrong. Why a cron job is the wrong tool, and what to do instead.

    Renewal automationThe 47-day schedulePKI fundamentals

  6. 22 October 2026 · 3 min read

    Renewal is not deployment

    The certificate renewed. The endpoint is still serving the old one. The five places a new certificate has to reach, why each one is different, and the check that tells you it got there.

    Renewal automationDiscovery and inventoryThe 47-day schedule

  7. 22 October 2026 · 3 min read

    What breaks on 15 March 2027

    The 100-day step is the first one that kills quarterly change tickets, 30-day expiry alerts, and manual domain validation. A dated checklist for the next cut in the schedule.

    The 47-day scheduleRenewal automationDiscovery and inventory

  8. 22 October 2026 · 3 min read

    Your certificate inventory is wrong. Find out by Friday.

    Three sources of truth that never agree: the public transparency logs, a scan of your own network, and the hosts themselves. A one-week method for finding the certificates nobody wrote down, and giving each one an owner.

    Discovery and inventoryAudit and ownershipThe 47-day schedule

  9. 21 September 2026 · 6 min read

    Stop buying certificates. Start owning renewals.

    A public TLS certificate has been free for ten years. What you are still paying for, whether you buy it or not, is the renewal. What free already covers, where a purchase still makes sense, and the five jobs that are yours either way.

    Renewal automationThe 47-day schedulePKI fundamentals

  10. 21 September 2026 · 4 min read

    Machine credentials beyond TLS

    The 47-day schedule is the visible tip of a bigger shift: every credential a machine holds is moving to short lifetimes. SSH, secrets, tokens, workload identity, code signing and now AI agents, and why one inventory beats seven.

    Machine identityDiscovery and inventoryThe 47-day schedule

  11. 21 September 2026 · 4 min read

    Why the signer is a separate process

    Automation has to sign certificates all day. It should never hold the keys. How trstctl draws that line, what the line guarantees, and what it does not, with links to the code.

    Key protectionPrivate PKISelf-hostingThe 47-day schedule

  12. 21 September 2026 · 5 min read

    47 days: what actually changes

    The CA/Browser Forum has cut the lifetime of a public TLS certificate to 47 days by March 2029, and the proof that you own a name to ten days. The schedule, what breaks, and the four moves that make it a non-event.

    The 47-day scheduleRenewal automationPKI fundamentals