Back to Articles
Report2026-10-14•4 min read•CSR.plus Team

Certificate Expiry Risk Report 2026

Certificate Expiry Risk Report 2026

Maximum TLS certificate lifetime (days)

Maximum TLS certificate lifetime (days)0109.5218.9328.4437.839820010047before 2026-03-15from 2026-03-15from 2027-03-15from 2029-03-15source: CA/Browser Forum Ballot SC-081v3, TLS Baseline Requirements v2.3.1 §6.3.2

source: CA/Browser Forum Ballot SC-081v3, TLS Baseline Requirements v2.3.1 §6.3.2

Let's Encrypt default certificate lifetime (days)

Let's Encrypt default certificate lifetime (days)025.250.475.6100.890now64from 2027-02-1045from 2028-02-16source: Let's Encrypt blog (2025-12-02, 2026-10-07)

source: Let's Encrypt blog (2025-12-02, 2026-10-07)

Website certificate status (%)

Website certificate status (%)99.99999999999999100%Valid certificate — 96%No monitored CA — 2%Wrong domain — 2%Expired — 1%source: W3Techs SSL certificate authorities survey (2026-10-26)

source: W3Techs SSL certificate authorities survey (2026-10-26)

Certificate expiry remains the top preventable cause of certificate-related outages: as of October 2026, 0.6% of the top 10 million sites W3Techs samples still serve an expired certificate to the public (W3Techs, 2026-11-02) — which, at survey scale, means tens of thousands of sites are currently down for every visitor. Meanwhile the industry is systematically shortening TLS (still commonly called SSL) certificate lifetimes: the 200-day maximum took effect on 2026-03-15 (CA/Browser Forum SC-081v3), and Let's Encrypt will default to 64-day certificates from February 2027. The margin for manual renewal is disappearing; monitoring plus automated renewal is the only durable fix.

How expiry incidents happen

An expiry incident is rarely a technical failure — it is a missed renewal: a certificate on a forgotten server, a manual process skipped during holidays, an automation job whose cron entry was lost in a migration. Once a certificate crosses its notAfter date, every visitor hits NET::ERR_CERT_DATE_INVALID until someone renews. The root cause is almost never that renewal is hard; it is that nobody owns the renewal.

0.6%: how common is expiry?

Per W3Techs' ongoing sampling (2026-10), 0.6% of websites currently present an expired certificate, another 1.5% serve a certificate for the wrong domain, and 2.3% use none of the monitored authorities. At any given moment, tens of thousands of public sites are expired — overwhelmingly long-tail sites lacking automation.

The new lifetime rules: from 398 days to 47

CA/Browser Forum Ballot SC-081v3 phases down the maximum TLS certificate lifetime: the 200-day cap took effect on 2026-03-15 (in force now), dropping to 100 days on 2027-03-15 and 47 days on 2029-03-15, with domain-validation reuse shrinking to 10 days alongside (CA/Browser Forum TLS Baseline Requirements §6.3.2). Annual manual renewal becomes structurally impossible after 2027.

The cost and benefit of short-lived certificates

Shorter certificates shrink the exposure window for compromised keys and mis-issuance, but they turn renewal from "a yearly chore" into a continuously running production system: Let's Encrypt's default lifetime drops from the current 90 days to 64 days on 2027-02-10 and 45 days on 2028-02-16 (Let's Encrypt official announcements, 2026-10). Renewal must be automated (an ACME client with ARI, RFC 9773) and backed by monitoring — which is exactly this report's core recommendation.

Step 1: Inventory and monitor every certificate you own

Bring all certificates under expiry monitoring with alerts at 30 days remaining — not 7. A 7-day window cannot absorb a single failed validation or vendor delay.

Step 2: Audit what is actually deployed

Use the SSL Checker to confirm the validity period, issuer, and chain of every live certificate, and prioritize the legacy certificates that are still running but not yet connected to automation. When you need the exact expiration timestamp, read the notAfter field directly with the Certificate Decoder.

Step 3: Automate renewal and rehearse it

Deploy ACME auto-renewal (certbot/acme.sh with a timer, or CA-managed renewal), enable ARI so clients renew in the CA-suggested window, and add --dry-run drills to CI. Confirm the reload hook after renewal actually takes effect — "renewed but never deployed" is the stealthiest form of expiry.

Troubleshooting checklist

SymptomLikely causeFix
Visitors see NET::ERR_CERT_DATE_INVALIDCertificate past its notAfter dateRenew and deploy immediately; then add it to expiry monitoring
Renewal succeeds but the site serves the old certificateReload hook never ranCheck the deploy hook and service reload, then re-verify with the SSL Checker
Scheduled jobs stop firingcron or systemd timer lost in a migrationBackstop with expiry monitoring and manage schedules as config
Browser clock is fine yet the certificate reads expiredServer clock driftRe-sync NTP, then re-check
Renewal alerts spike after 2027-02Hard-coded 60-day interval meets 64-day certificatesSwitch to ARI or lifetime-proportional scheduling
One wildcard expiry takes down all subdomainsBroad single certificate with no independent monitoringSplit critical services onto separate certificates, each monitored

Take Action

Add your domains to expiry monitoring and run an instant audit with the SSL Checker; for systematic deployment guidance, see the SSL certificate guide.

Related reading: Certificate Expiry Risk Report 2026, Let's Encrypt Market Share and Chain of Trust Report 2026, Certificate Expiry Risk Report 2026.

FAQ

What is the best alert threshold?

Alert at 30 days remaining for automated renewals and at 14 days for manual processes. A 7-day window leaves no room for validation failures or vendor delays — it turns alerts into incident notices.

Do short-lived certificates increase risk?

Only if renewal is manual. With automation, short-lived certificates shrink the exposure window for a compromised key or mis-issuance and force good operational hygiene.

Does the 200-day rule affect me?

Yes. If you still issue certificates close to 398 days, you are now capped at 200 (effective 2026-03-15), falling to 100 days on 2027-03-15. Moving renewal to automation ahead of the deadlines is far calmer than migrating under pressure.

How do I know if any of my certificates are close to expiry?

Register your domains with [expiry monitoring](/tools/expiry) — it tracks days remaining and alerts at your threshold; for a single certificate you can also run an instant check with the SSL Checker.

Free SSL/TLS tools

Verify and inspect your certificates in seconds.

Related Certificate Info

Learn more about choosing and buying certificates.

Related articles