Publicly trusted certificates may only last so long, and the limit is shrinking: 398 days, then 200 days for certificates issued since 15 March 2026, 100 days from March 2027 and 47 days from March 2029. Chrome refuses a certificate from a public authority that lasts longer.
Your connection is not private NET::ERR_CERT_VALIDITY_TOO_LONG
| Error | NET::ERR_CERT_VALIDITY_TOO_LONG |
| Usually fixed by | The website |
| Maximum lifetime | 200 days if issued from 15 March 2026; 100 days from 15 March 2027; 47 days from 15 March 2029 |
| Applies to | Certificates from publicly trusted authorities |
| Agreed by | CA/Browser Forum ballot SC-081 (2025) |
Check the certificate a site serves
Enter the site’s domain: we connect the way a browser does and show the certificate, its chain and the TLS versions it offers.
What it means
The CA/Browser Forum — the certificate authorities and browser makers — agreed in 2025 to shorten certificate lifetimes step by step. Chrome enforces the limit for certificates chaining to public roots: one issued after a cut-off date with a longer validity period is refused with this error.
Why it happens
- A certificate from a public authority issued with a lifetime longer than the limit in force on its issue date.
How to fix it
- Get a certificate within the limit — any current public certificate authority issues them — and install it.
- Automate renewal: with lifetimes heading for 47 days, manual renewal will not keep up. Let’s Encrypt recommends renewing at about two-thirds of a certificate’s lifetime.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- net/cert/cert_verify_proc.cc — chromium.googlesource.com
- Ballot SC081v3: Introduce Schedule of Reducing Validity and Data Reuse Periods — cabforum.org
- Decreasing Certificate Lifetimes to 45 Days — letsencrypt.org