For years it was normal to buy an SSL certificate for a year and forget about it until the next one. That habit is ending. In 2025 the CA/Browser Forum, which brings together browser vendors and certificate authorities, approved a phased reduction of the maximum lifetime of public TLS certificates. The first step took effect on 15 March 2026: newly issued certificates can no longer be valid for more than 200 days.
The schedule
| From | Maximum certificate lifetime | Domain validation reuse |
|---|---|---|
| 15 March 2026 | 200 days | 200 days |
| 15 March 2027 | 100 days | 100 days |
| 15 March 2029 | 47 days | 10 days |
From 2029 a certificate will need renewing at least eight times a year, and domain control will be revalidated almost every time. These rules bind certificate authorities, so they apply to paid certificates too. Check the CA/Browser Forum documents and your CA's announcements for the exact details.
Why lifetimes are shrinking
The main reason is security. Revocation does not work reliably in practice, because browsers do not always check revocation lists. A short-lived certificate becomes useless soon even if nobody revokes it, and a previous domain owner cannot keep using an old certificate for long. Shorter lifetimes also make the ecosystem more agile, for example when migrating to new cryptographic algorithms designed to resist future quantum computers.
Why manual renewal no longer works
Picture a training centre in Tashkent: every year the accountant pays for a certificate and a developer installs it by hand. Once a year it was a single task. At 200 days it happens almost twice a year, and at 100 days more than four times. Each time someone must remember, generate a key, upload files and reload the web server. One slip and browsers show a "Not secure" warning while online course registration stops. Renewal must be done by software, which is exactly what the ACME protocol, supported by Let's Encrypt and many other CAs, is for.
Automation on hosting and on a VPS
On shared hosting the control panel usually handles it. On sayt.uz hosting a free Let's Encrypt certificate is installed and renewed automatically well before expiry. The one requirement is that the domain points to the right server; if the A record was changed or the site sits behind an external proxy, validation can fail. With paid certificates you often buy a multi-year subscription, but the certificate itself is reissued several times, so ask whether the CA supports ACME issuance.
On your own server with Certbot, check the timer and test renewal without touching the real certificate:
systemctl list-timers | grep certbot
sudo certbot renew --dry-run
sudo certbot renew --deploy-hook "systemctl reload nginx"
The dry run walks through the whole renewal process without replacing the live certificate, so any error it reports can be fixed calmly now rather than on the day the certificate expires. The deploy hook makes sure the web server actually reloads and starts serving the new file after a successful renewal. If you use acme.sh instead, check its cron entry with crontab -l.
Whatever the method, verify what the site actually serves:
echo | openssl s_client -connect example.uz:443 -servername example.uz 2>/dev/null | openssl x509 -noout -enddate
If the expiry date is only weeks away and renewal should already have happened, something is broken.
What to do now
List all your domains and subdomains and note how each certificate is renewed: automatically by the panel, by a script on the server or by hand. Move the manual ones to automation and add external monitoring of certificate expiry so you hear about failures from an alert, not from customers. If a certificate on your hosting stops renewing, open a ticket in the sayt.uz cabinet with the domain name.