SSL Certificate Validity Reduced to 200 Days in 2026: What It Means for Your Website
Updated November 22, 2026 · 8 min read · Category: SSL Certificate

Table of Contents
- What Is the 200-Day SSL Rule?
- Why Certificate Lifetimes Are Getting Shorter
- Timeline: From 2 Years to 200 Days
- Impact on Websites and Businesses
- Who Is Most Affected?
- SSL Types vs. the 200-Day Standard
- Setting Up Auto-Renewal
- SSL Certificate Management Tools
- Best Practices
- How AsiaGB Supports the Change
- FAQ
- Summary
What Is the 200-Day SSL Rule?
Starting in 2026, SSL/TLS certificates are limited to a maximum validity of 200 days. Previously, paid SSL certificates could be issued for up to 1 year (398 days). This change was driven by Apple, which announced that Safari would no longer trust any SSL certificate with a validity period exceeding 200 days.
In practice, this means that if your website's certificate was issued with a validity exceeding 200 days, browsers will display a "Your connection is not private" warning — seriously harming user trust and your SEO performance.
Why Are Certificate Lifetimes Getting Shorter?
The move to shorter certificate lifetimes is driven by security improvements across the web PKI (Public Key Infrastructure):
- Reduced Key Compromise Window: Shorter certificates limit the damage if a private key is stolen or compromised.
- Eliminating Stale Credentials: Certificates can contain outdated ownership information. Shorter lifetimes ensure that domain ownership is regularly re-verified.
- Encouraging Automation: When certificates expire more frequently, website owners must rely on automation — reducing human error from forgetting to renew.
- Addressing Revocation Problems: OCSP and CRL have known performance and privacy limitations. Shorter certificate lifetimes partially compensate for these weaknesses.
- Preparing for Post-Quantum Cryptography: As encryption algorithms need upgrading in the future, more frequent certificate rotation makes transitions smoother.
Timeline: How SSL Validity Has Changed Over the Years
The reduction in certificate lifetimes has been gradual, with Apple consistently leading the industry push:
| Year | Max Validity | Enforced By | Notes |
|---|---|---|---|
| Before 2015 | 5 years | CA/B Forum | Early SSL era — very long certificates |
| 2015–2018 | 3 years (1,185 days) | CA/B Forum | First reduction |
| 2018–2020 | 2 years (825 days) | CA/B Forum | Google and Mozilla pushed for shorter |
| 2020–2025 | 1 year (398 days) | Apple (Safari first) | Apple forced the whole industry to follow |
| 2026 | 200 days | Apple + CA/B Forum | Current standard |
| 2027+ (proposed) | 47 days | CA/B Forum Draft | Under consideration |
Apple has been the key driver because it can enforce changes through its own root store without waiting for CA/B Forum consensus, forcing all Certificate Authorities to comply.
Impact on Websites and Businesses
Operational Impact
- SSL certificates must be renewed more frequently — from once a year to at least once every 6–7 months.
- Manual renewal processes carry higher risk of causing outages.
- IT teams need to implement proper Certificate Lifecycle Management.
- Paid SSL costs may effectively increase due to more frequent renewal overhead.
Security Benefits
- Reduced risk window if a private key is compromised.
- Certificate metadata (like organization names) stays up to date.
- Shorter window during which a revoked certificate could still be used.
Who Is Most Affected?
- Paid SSL users (DV, OV, EV): Most affected — certificates that used to last 1 year are now capped at 200 days.
- Organizations with manual renewal processes: Must update reminder schedules and renewal workflows.
- Businesses with many domains/subdomains: Managing multiple certificates becomes more complex.
- Let's Encrypt users: Minimal impact since 90 days < 200 days, but auto-renewal must be verified.
SSL Certificate Types vs. the 200-Day Standard
| SSL Type | Old Validity | New Validity (2026) | Auto-Renewal | Impact |
|---|---|---|---|---|
| Let's Encrypt | 90 days | 90 days (unchanged) | Requires Certbot/acme.sh | Low |
| Paid DV SSL (RapidSSL) | 398 days | Max 200 days | Needs new setup | Medium |
| Paid OV SSL (GeoTrust) | 398 days | Max 200 days | Needs new setup | Medium |
| EV SSL | 398 days | Max 200 days | Needs new setup | High |
| Wildcard SSL | 398 days | Max 200 days | Needs new setup | Medium |
| DirectAdmin AutoSSL | 90 days | 90 days (unchanged) | Automatic via DirectAdmin | Low |
Setting Up Auto-Renewal to Handle 200-Day SSL
With shorter certificate lifetimes, auto-renewal is no longer optional — it is essential. The setup method depends on your SSL type:
Let's Encrypt on VPS (Certbot)
- Certbot automatically installs a cron job when you run
certbot --nginxorcertbot --apache - Verify with:
crontab -lorsystemctl list-timers | grep certbot - Test renewal:
certbot renew --dry-run
Let's Encrypt on DirectAdmin
- DirectAdmin handles Let's Encrypt renewal automatically through AutoSSL — no extra setup needed.
- Check status: DirectAdmin → SSL Certificates → Auto SSL
Paid SSL Certificate
- Set email reminders from your CA at least 30 days before expiry.
- Consider using the ACME protocol with paid CAs for partial automation.
- Use monitoring tools like Uptime Kuma or Zabbix for SSL expiry alerts.
SSL Certificate Management Tools
- Certbot: Standard tool for Let's Encrypt on Linux servers Free
- acme.sh: Lightweight shell script supporting multiple CAs and DNS providers Free
- Caddy Web Server: Manages SSL automatically by default — zero configuration needed Free
- Traefik: Reverse proxy with built-in SSL management for Docker containers Free
- Uptime Kuma: SSL expiry monitoring with Telegram/email alerts Free
- SSL Labs: Online tool to verify certificate details and expiry dates Free
Best Practices for SSL in the 200-Day Era
- Automate Everything: Never rely on manual renewal. Use Certbot or acme.sh.
- Set Alerts 30 Days Ahead: Configure notifications at least 1 month before expiry.
- Test Renewal Regularly: Run
certbot renew --dry-runmonthly. - Centralize Management: Use a certificate management tool if you have multiple domains.
- Monitor with External Tools: Use SSL Labs or Uptime Kuma to verify certificate status independently.
- Maintain a Runbook: Document manual renewal steps in case automation fails.
- Log Certificate Changes: Record when renewals occur for audit and troubleshooting.
- Wildcard vs. Per-Domain: For many subdomains, consider a Wildcard certificate to simplify management.
How AsiaGB Supports the 200-Day SSL Standard
AsiaGB has fully adapted to the 200-day SSL maximum across all services:
- Hosting with DirectAdmin: AutoSSL handles Let's Encrypt renewals automatically — nothing extra to configure.
- Paid SSL Certificates: AsiaGB's team assists with renewal reminders and configuration guidance.
- VPS: Full root access lets you use Certbot or acme.sh for complete SSL automation.
- 99% Uptime SLA: SSL issues are covered by our support team around the clock.
Browse AsiaGB's full SSL certificate range — DV, OV, EV, and Wildcard — starting from 1,000 THB/year.
Frequently Asked Questions
When did the 200-day SSL validity rule take effect?
Does the 200-day rule affect Let's Encrypt certificates?
If I buy a 1-year paid SSL, how long will each certificate last?
What happens if my SSL certificate expires?
How do I check how many days my SSL certificate has left?
openssl s_client -connect yourdomain.com:443 < /dev/null 2>&1 | openssl x509 -noout -enddate to see the expiry date. Online tools like SSL Labs (ssllabs.com/ssltest/) display the expiry date and full security rating for free.Do I need to buy a new SSL certificate every 200 days?
Summary: Preparing for the 200-Day SSL Era
- ✅ Let's Encrypt: Verify auto-renewal is active — run
certbot renew --dry-run - ✅ Paid SSL: Set 30-day expiry reminders and explore ACME automation
- ✅ DirectAdmin Hosting: AutoSSL handles everything automatically
- ✅ VPS: Install Certbot/acme.sh and configure cron-based auto-renewal
- ⚠️ EV/OV SSL: Plan your renewal process carefully — validation must be re-done each time
- 📊 Use Uptime Kuma or SSL Labs to monitor certificate expiry proactively