47-day certificates explained in one minute
Sir Cert explains why public TLS certificates are shrinking from 398 days to 47, what the shorter limit means for your renewals and how to get ahead of it before 2027.
Plain guides to TLS certificates, renewal and automation for engineers and IT managers, with every standard linked to its source.
Sir Cert explains why public TLS certificates are shrinking from 398 days to 47, what the shorter limit means for your renewals and how to get ahead of it before 2027.
A plain explanation of what a TLS certificate contains, how a browser checks it in the handshake and the three mistakes behind most certificate warnings.
Public CAs are trusted everywhere but follow strict rules and publish every name. Internal CAs give control but must be run well. How to choose.
Appliances rarely run an ACME client, so their certificates are often renewed by hand. How to automate cloud load balancers and on-premises devices safely.
How ACME works, choosing a client and challenge type, locking it down with CAA, and scheduling renewals for the 45 and 47-day certificates ahead.
No single method finds every certificate. What CT logs, network scans, host checks and cloud APIs each find and miss, and how to combine them.
Short answers to the questions people ask about 47-day and 200-day TLS certificates, from the dates and the reasons to what happens to certificates you already have.
What ACME External Account Binding (EAB) is, why commercial CAs require it, and how to register with a key ID and HMAC key in Certbot, acme.sh, lego and cert-manager.
How to monitor TLS certificate expiry with the Prometheus blackbox exporter, Grafana and Zabbix, which alerts to set, and what expiry monitoring cannot tell you.
How Sectigo ACME works through Certificate-as-a-Service, where the directory URL and EAB credentials come from, what OV needs first, and how to set up a client.
How to get and automatically renew wildcard TLS certificates with ACME and DNS-01, and how CNAME delegation keeps DNS credentials off your servers.
A spreadsheet of certificates is out of date the day after it is made. Why that happens, why shorter lifetimes make it worse, and what to keep when you move on.
Certificate lifecycle management covers finding, issuing, deploying, checking and renewing certificates. The stages, what NIS2 and DORA say, and when it pays.
Most certificate outages are missed renewals, not technical failures. The five ways they happen, a checklist that prevents most, and what to do when one slips.
Public TLS certificates now last at most 200 days, falling to 100 in 2027 and 47 in 2029. The schedule, the domain validation changes and what to do now.