Captain’s log · Stardate 26287.8 · Tactical
From Three Years to 64 Days: My SSL Certificates Since 1996
My first certificate came from VeriSign, and it was expensive, several hundred dollars for a year.
From Three Years to 64 Days: My SSL Certificates Since 1996
I have had SSL certificates for RogerLe.com since 1996. My first certificate came from VeriSign, and it was expensive, several hundred dollars for a year.
Later, I bought a three-year certificate from Thawte for about the same price as a one-year certificate from VeriSign. That was a considerable saving, and it meant I did not have to go through the renewal process every year.
After that, I started buying certificates from SSLs.com. I bought my last paid certificate in 2019, when I started using Let's Encrypt.
Now Let's Encrypt is moving from 90-day certificates to 64 days, with a further reduction to 45 days in 2028. Coming from a certificate that lasted three years, that sounds like a lot of renewing. In practice, managing them is easier for me now.
When everything was manual
I do not remember a certificate expiring unexpectedly. But I do remember issuance and renewal failures, and having to be very careful with the process.
Everything was manual on my side. Buying the certificate was only part of the job. I also had to get it issued, install it and make sure it worked. At renewal time, I had to pay attention again.
A three-year certificate was attractive for both the price and the time between renewals. There were fewer occasions when I had to deal with the whole process.
That is the part I remember when I read about shorter certificate lifetimes. If I still had to do all of that manually, renewing every few weeks would be a different proposition.
What I use today
Certbot manages certificates for RogerLe.com, its related sites and my personal sites. My clients' certificates are managed through DirectAdmin, also using Let's Encrypt.
On my own setup, Certbot runs its renewal check every day. That does not mean it issues a new certificate every day. It checks whether renewal is due and renews when needed.
I no longer have to buy a certificate and handle its renewal manually. The routine work is automated.
I also find troubleshooting much quicker with AI help. Problems that once took me hours or days can now often be resolved in minutes. That has made the work easier for me, though I still need to check the result.
What is changing
Let's Encrypt announced the change on October 7, 2026. From February 10, 2027, certificates issued or renewed under its default lifetime will be valid for 64 days. Existing valid certificates will not be revoked as part of the change.
Testing of the shorter default lifetime begins in its staging environment on October 14, 2026. The default is due to fall to 45 days in 2028.
Let's Encrypt says shorter lifetimes reduce the risks from compromised keys and incorrectly issued certificates. I think that is a sensible security change.
For me, the extra renewals are not a big maintenance problem now. The important thing is that the automation keeps working.
A few things to check
For anyone managing their own certificates, these are the checks I would make before the change:
- Check the schedule. Confirm that the renewal job or timer is actually running.
- Test renewal. Certbot provides
certbot renew --dry-runto test the process. - Check deployment. Make sure the renewed certificate reaches the service using it, and that the necessary reload happens. Certbot provides deploy hooks for actions after successful renewal.
- Check alerts. Make sure a renewal failure gets your attention.
- Check old scripts. Look for renewal schedules that assume a 90-day certificate.
Let's Encrypt recommends clients that support ACME Renewal Info, or ARI, which lets it tell the client when to renew. It also advises reviewing fixed renewal schedules that depend on the old lifetime.
What this means for a site owner
If someone else manages your hosting, ask whether certificate renewal is automated and monitored. You should not need to buy a new certificate manually every 64 days because of this announcement.
If you manage the server yourself, check the renewal process before February. I would rather test it with time to spare than investigate it when a certificate is about to expire.
I remember paying several hundred dollars for one year, and being pleased to get three years for roughly the same money. Today, I use free certificates with automated renewal. Their lifetimes are getting shorter, but I would not want to go back to managing them the old way.