What changes
In April 2025 the CA/Browser Forum adopted ballot SC-081v3, which shortens the life of TLS certificates in three steps. The first step, 200 days, took effect on 15 March 2026. The second is in the Baseline Requirements' table of relevant dates for 15 March 2027:
“Maximum validity period of Subscriber Certificates is 100 days.”
— Baseline Requirements, section 1.2.2, for section 6.3.2
The limit applies by the date of issuance. A certificate issued on 14 March 2027 may still run for 200 days, so the last certificates longer than 100 days expire by the end of September 2027. On the same day the period for which a CA may reuse a domain validation drops from 200 to 100 days, and Chrome's requirement that new certificates assert only serverAuth takes effect, which we covered in an earlier article.
- Maximum validity drops from 398 to 200 days; domain validations may be reused for 200 days. — CA/B Forum ballot SC-081v3
- Let's Encrypt's default certificates go from 90 to 64 days. — Let's Encrypt
- Maximum validity drops to 100 days; domain validations may be reused for 100 days. — SC-081v3
- Let's Encrypt's default certificates go to 45 days. — Let's Encrypt
- Maximum validity drops to 47 days; domain validations may be reused for 10 days. — SC-081v3
How long certificates are valid today
New publicly trusted TLS certificates of October 2026 by validity period, counted the way the Baseline Requirements count it: from notBefore to notAfter inclusive, a day being 86,400 seconds.
| validity | certificates | share |
|---|---|---|
| 10 days or less | 35,339,273 | 5.6% |
| 11 to 47 days | 13,947,017 | 2.2% |
| 48 to 100 days | 505,348,905 | 80.3% |
| 101 to 200 days | 74,980,190 | 11.9% |
| more than 200 days | 0 | 0.0% |
| all CAs in CCADB | 629,615,385 | 100.0% |
Nearly nine certificates in ten already fit under the 2027 limit, and 7.8% already meet the 47-day limit of 2029; most of those last ten days or less. The certificates that have to change are the 11.9% in the fourth row. They cover about 16.8 million registrable domains, 9.9% of the domains that got a certificate that month.
CAs do not spread their certificates over the allowed range. They pick a period just under a limit, and the month's most common periods show which limits they have in mind:
| validity, days | certificates | share |
|---|---|---|
| 90 | 297,196,744 | 47.2% |
| 91 | 186,413,457 | 29.6% |
| 199 | 54,757,040 | 8.7% |
| 198 | 16,700,999 | 2.7% |
| 3 | 12,881,555 | 2.0% |
| 100 | 11,614,520 | 1.8% |
| 7 | 7,185,239 | 1.1% |
| 2 | 6,735,372 | 1.1% |
The 90- and 91-day certificates come from the ACME CAs. The 198- and 199-day ones are the 200-day maximum with a day or two of margin. The 100-day certificates come mostly from one organization that has already moved to the next limit.
No movement yet
The share of new publicly trusted TLS certificates valid for more than 100 days, week by week. In the week of 1 December 2025 it was 10.0%; in the week of 9 November 2026, 10.8%. Total issuance about doubled over the year, so the number behind the share doubled as well: 7,668,307 such certificates in the first week, 16,642,333 in the last.
Four months before the date, nothing has moved. That is what happened before the 200-day limit too. Certificates longer than 200 days were 4.8% of issuance in the week of 1 December 2025 and were still above 5% in early February 2026. In the week of 9 March 2026, the last before the limit, they were 0.7%: 597,670 certificates. In all the weeks since, the CAs in CCADB have issued 58 of them, all from a few small CAs. The CAs changed their settings in the last five weeks, and the long certificates will most likely disappear the same way in February and March 2027.
Who issues the long certificates
New TLS certificates of October 2026 by the organization that runs the issuing CA: how many were valid for more than 100 days, what share of the organization's certificates that was, and the organization's most common validity period. Listed: every organization with at least 100,000 such certificates, and the largest issuers. Amazon and GoDaddy issued 86.1% of them.
| CA organization | TLS certificates | over 100 days | share | 47 days or less | most common |
|---|---|---|---|---|---|
| Amazon | 65,600,235 | 42,665,354 | 65.0% | 31.8% | 199 days |
| GoDaddy | 22,121,236 | 21,924,746 | 99.1% | 0.0% | 199 days |
| DigiCert | 18,318,799 | 2,653,665 | 14.5% | 71.5% | 3 days |
| Microsoft | 16,331,362 | 2,559,047 | 15.7% | 13.9% | 100 days |
| Sectigo | 12,647,554 | 1,954,070 | 15.5% | 0.2% | 91 days |
| IdenTrust | 1,427,514 | 1,266,433 | 88.7% | 1.8% | 199 days |
| Starfield Technologies | 459,016 | 310,065 | 67.5% | 6.4% | 199 days |
| Meraki LLC (under DigiCert) | 293,725 | 293,725 | 100.0% | 0.0% | 199 days |
| GlobalSign | 1,118,826 | 273,187 | 24.4% | 62.6% | 2 days |
| SSL.com | 13,342,116 | 219,195 | 1.6% | 0.0% | 90 days |
| Actalis S.p.A. | 222,977 | 199,972 | 89.7% | 0.0% | 199 days |
| Gandi SAS (under DigiCert) | 127,488 | 127,453 | 100.0% | 0.0% | 199 days |
| HARICA | 118,883 | 118,881 | 100.0% | 0.0% | 199 days |
| ZeroSSL (under Sectigo) | 21,260,902 | 4,332 | 0.0% | 2.2% | 91 days |
| Let's Encrypt | 283,966,276 | 0 | 0.0% | 3.7% | 90 days |
| Google Trust Services | 170,657,209 | 0 | 0.0% | 0.6% | 91 days |
| all CAs in CCADB | 629,615,385 | 74,980,190 | 11.9% | 7.8% |
Several organizations sit at both ends at once: a large share of week-long certificates for automated platforms, and 199-day certificates for everything else. In all, 552 issuing CAs issued at least one certificate longer than 100 days that month. The twelve with the most, with the usual period of their long certificates:
| issuing CA | organization | over 100 days | share of the CA's TLS | usual period |
|---|---|---|---|---|
| GoDaddy TLS Intermediate CA DV - R1v1 | GoDaddy | 21,917,969 | 99.1% | 199 days |
| Amazon RSA 2048 M04 | Amazon | 6,994,510 | 91.8% | 198 days |
| Amazon RSA 2048 M01 | Amazon | 6,991,660 | 91.8% | 198 days |
| Amazon ECDSA 384 S26 | Amazon | 1,893,974 | 77.0% | 199 days |
| Amazon ECDSA 384 S27 | Amazon | 1,893,837 | 77.0% | 199 days |
| Amazon ECDSA 384 S24 | Amazon | 1,861,658 | 77.0% | 199 days |
| Amazon ECDSA 384 S25 | Amazon | 1,858,291 | 77.0% | 199 days |
| Amazon ECDSA 384 S29 | Amazon | 1,822,435 | 76.9% | 199 days |
| Amazon ECDSA 384 S28 | Amazon | 1,819,414 | 76.8% | 199 days |
| Amazon ECDSA 384 S23 | Amazon | 1,807,592 | 77.0% | 199 days |
| Amazon ECDSA 384 S22 | Amazon | 1,805,350 | 76.9% | 199 days |
| Sectigo Public Server Authentication CA DV R36 | Sectigo | 1,746,758 | 89.0% | 199 days |
Which domains they are for
The registrable domains with the most certificates longer than 100 days in October 2026, by the certificate's common name or first DNS name. The first three rows account for 44.7% of all such certificates.
| domain | CA organization | certificates | share |
|---|---|---|---|
| dyingbirds.com | Amazon | 12,867,593 | 17.2% |
| amazonaws.com | Amazon | 10,672,306 | 14.2% |
| aws.dev | Amazon | 10,010,832 | 13.4% |
| on.aws | Amazon | 1,706,500 | 2.3% |
| amplifyapp.com | Amazon | 1,452,572 | 1.9% |
| azure.com | Microsoft | 1,384,010 | 1.8% |
| meraki.direct | IdenTrust | 1,049,207 | 1.4% |
| windows.net | Microsoft | 419,236 | 0.6% |
| amazonaws.com.cn | Amazon | 392,949 | 0.5% |
| a2z.eu | Amazon | 368,356 | 0.5% |
| meraki.direct | Meraki LLC (under DigiCert) | 293,905 | 0.4% |
| cisco.com | IdenTrust | 180,717 | 0.2% |
| azure.net | DigiCert | 155,462 | 0.2% |
The list is short because it is concentrated: a few cloud and device platforms issue millions of certificates under their own domains, and their owners renew them by machine. The rest of the long certificates are spread thinly over millions of customer domains, and that is where the change will be felt.
What to do
A certificate issued by a platform that also installs it, such as a cloud load balancer or a managed hosting plan, will simply be renewed more often. Nothing changes for its owner.
The change lands on certificates that somebody orders and installs by hand. A 199-day certificate is replaced twice a year. From March 2027 the same certificate needs replacing at least four times a year, and from March 2029 at least eight. Each step makes a missed renewal more likely.
Find the certificates that are renewed by hand. Search your domain on ctlogs.dev and look at the validity of each current certificate: anything close to 199 days comes from a CA's long-lived product, and many of those are still ordered and installed by hand. The subdomain finder lists every hostname that has a certificate, including the ones nobody remembers. For hundreds or thousands of domains, the JSON API returns the same data in bulk, with the issuer, not_before and not_after of every certificate, so a scheduled job can list each one that runs longer than 100 days or is close to expiry.
Automate them before March. Many CAs that sell 199-day certificates also offer ACME for the same products. A client that renews at two thirds of the lifetime, or follows the CA's ACME Renewal Information, keeps working through every later step without another change.
Check the validation as well. A CA may reuse a domain validation for 100 days from March 2027 and for 10 days from March 2029. A process in which someone confirms the domain by hand will have to run at nearly every renewal.
Expect the switch late. If your CA follows the pattern of 2026, your certificates will go from 199 to about 99 days in the weeks before 15 March 2027, without notice beyond the CA's own announcements.
Sources
- Ballot SC-081v3: Introduce Schedule of Reducing Validity and Data Reuse Periods, CA/Browser Forum, April 2025
- Baseline Requirements for the Issuance and Management of Publicly-Trusted TLS Server Certificates, sections 1.2.2, 4.2.1 and 6.3.2
- 64-Day Certificate Lifetimes Coming Feb 2027, Let's Encrypt, 7 October 2026
- CCADB, the intermediate CAs counted here