If you still renew SSL certificates by hand, with a calendar reminder and a cup of coffee once a year, we have some news. That routine stopped working in March, and it’s going to get a lot worse.
In April 2025 the CA/Browser Forum passed Ballot SC-081v3. It was originally an Apple proposal, and nobody voted against it. The ballot cuts the maximum life of a public TLS certificate in three steps:
| From | Max certificate validity | Domain validation reuse |
|---|---|---|
| 15 March 2026 | 200 days | 200 days |
| 15 March 2027 | 100 days | 100 days |
| 15 March 2029 | 47 days | 10 days |
So we’re already living in the 200-day world. In about four months it drops to 100. By 2029 you’re renewing every certificate roughly eight times a year, and the 10-day validation reuse means you can’t even get away with “we validated the domain last month”.
We manage a lot of SSL certificates for clients. Honestly, the expired-cert incidents we see are almost never technical. Someone left the company, the reminder went to a dead mailbox, and on a Monday morning the client portal throws a scary browser warning. Shorter lifetimes just multiply the chances of that happening. The only real fix is automation.
Step 1: Make a list of your digital assets that use SSL Certificates
Before automating anything, make a list. Every domain, every subdomain, which server or load balancer it lives on, who issued it, when it expires. You’ll find surprises, we always do.
A quick way to check any endpoint’s expiry from the command line:
root@localhost:~$ echo | openssl s_client -connect portal.example.com:443 -servername portal.example.com 2>/dev/null | openssl x509 -noout -enddate
Certificate Transparency logs are also handy. Search your domain on crt.sh and you’ll see every public cert ever issued for it, including the ones somebody forgot about.
The web servers are the easy part. The tricky ones are load balancers, firewalls, mail servers, VPN appliances, Windows boxes running IIS, and anything where the cert gets copied by hand onto another device.
For Windows, win-acme does a good job. For hardware appliances, check if the vendor has an ACME client or API. If not, a small script that pushes the renewed cert over the API is better than nothing.
Step 2: Pick an ACME client that fits the server
ACME (RFC 8555) is the protocol that lets a server request and renew certificates on its own. Let’s Encrypt made it popular, but most commercial CAs (Sectigo, DigiCert, ZeroSSL and others) support it now too, so you don’t have to give up your paid certs to automate.
For a plain Linux box with Nginx or Apache, Certbot is the easy path:
root@localhost:~$ apt install certbot python3-certbot-nginx
root@localhost:~$ certbot --nginx -d example.com -d www.example.com
root@localhost:~$ certbot renew --dry-run
The package installs a systemd timer that runs renewals twice a day (check it with systemctl list-timers | grep certbot). Add a deploy hook so the web server actually reloads the new cert. People forget this one surprisingly often:
root@localhost:~$ certbot renew --deploy-hook "systemctl reload nginx"
Step 3: Monitor SSL expiration date
Automation fails quietly. A DNS API token expires, a firewall rule blocks port 80, a hook script breaks after an update. So keep monitoring certificate expiry separately from the thing that renews them.
Any decent monitoring stack (Zabbix, Prometheus with blackbox_exporter, Uptime Kuma) can alert you. Just bring the alert threshold down. A 30-day warning made sense for a one-year cert. On a 47-day cert it fires almost the moment the certificate is issued.
Where NetShop comes in
If your business runs a dozen or more client-facing domains, certificate renewal is exactly the sort of background chore that’s easy to underestimate until it bites.
NetShop’s managed services team can audit your certificate estate, set up ACME automation across your servers and plug expiry alerts into monitoring. That way March 2027 is a non-event for you. Get in touch and we’ll take a look.



















