TLS certificate validity: 47 days by 2029
Quick fix
Renew automatically with an ACME client (RFC 8555) wherever you can, and alert on expiry well before the end. For systems that cannot automate, plan a proxy that renews or a private CA now.
How to fix it
- List every public certificate you run: web servers, load balancers, CDNs, mail servers, the
mta-stshost and appliances. - Renew automatically with an ACME client (RFC 8555) wherever you can, with DNS-01 or HTTP-01 validation that also runs without a person.
- Alert on expiry well before the end, for example when 30 percent of the lifetime is left.
- For systems that cannot automate, plan now: put them behind a proxy that renews, or use a private CA where only your own clients need to trust the certificate.
Learn more: TLS certificates explained: expiry, chain and names
How to check
The certificate check fetches the certificate a host serves and shows its issue and expiry dates and the days left. To check a certificate file, paste it into the PEM certificate decoder.
The TLS certificate check opens with your domain filled in; it runs when you press Check.
Tools to check it
What the error means
Publicly trusted TLS certificates get shorter in three steps under the CA/Browser Forum Baseline Requirements (ballot SC-081, adopted 11 April 2025): at most 200 days for certificates issued from 15 March 2026, 100 days from 15 March 2027 and 47 days from 15 March 2029. Before 15 March 2026 the limit was 398 days. At 47 days, certificates are renewed about once a month, which only works with automation.
| From | Maximum validity | Domain validation reuse |
|---|---|---|
| Before 15 March 2026 | 398 days | 398 days |
| 15 March 2026 | 200 days | 200 days |
| 15 March 2027 | 100 days | 100 days |
| 15 March 2029 | 47 days | 10 days |
The limits apply by issue date: a certificate issued before a step keeps its longer lifetime until it expires. Domain validation reuse is how long a CA may rely on an earlier check that you control the domain; at 10 days the CA has to validate again for nearly every certificate. The reuse period for subject identity information (the organisation in OV and EV certificates) is 398 days from 15 March 2026. The rules cover publicly trusted certificates only; a private CA sets its own lifetimes.
As of November 2026 the limit is 200 days. Our certificate checks report a publicly trusted certificate that is valid longer than its issue date allows as CERT_LONG_VALIDITY.
Sources
- CA/Browser Forum: TLS Baseline Requirements (version 2.3.1, sections 1.2.2 and 6.3.2) (checked 2026-11-15)
- RFC 8555: ACME (checked 2026-11-15)