Skip to main content

Einde van 2-jarige openbare DV-, OV- en EV SSL/TLS-certificaten

Sector neemt afscheid van 2-jarige openbare SSL/TLS-certificaten

On February 24, 2026, DigiCert stopped issuing 397-day public DV, OV, and EV TLS/SSL and Qualified Website Authentication Certificates (QWAC and QWAC PSD2). The new maximum TLS certificate validity is 199 days. Read our knowledge base article to learn more about the move to 199-day TLS certificates.

DigiCert implemented 199-day maximum validity to align with the CA/Browser Forum Baseline Requirements and to ensure all systems are fully aligned ahead of the March 15, 2026 industry deadline. For more information, see the DigiCert FAQ on TLS/SSL certificate validity.

Let op

DigiCert stopte met het uitgeven van 2-jarige openbare SSL/TLS-certificaten op 27 augustus 2020 18:00 MDT (28 augustus 00:00 UTC).

Items covered in this article:

Wat moet ik hiervoor doen?

Met de nieuwe maximale geldigheid van 397 dagen voor certificaten raden we aan om uw SSL/TLS-dekking te maximaliseren door nieuwe openbare SSL/TLS-certificaten aan te schaffen met een DigiCert® Multi-year Plan.

Let op

As of February 24, 2026, DigiCert TLS certificate orders are 1-year by default. Contact your account manager or DigiCert Support if you’re interested in using the 2 and 3-year plans.

Coverage limitations

CertCentral Subscription accounts and Enterprise accounts with subscription contracts don’t use DigiCert annual plans. See Annual plan limits.

Integratie met DigiCert Services API

Voor degenen die de DigiCert Services API gebruiken, moet u uw API-workflows bijwerken om in uw aanvragen rekening te houden met de nieuwe maximale certificaatgeldigheid van 397 dagen. Zie Services API.

Wat gebeurt er als mijn 2-jarige openbare SSL/TLS-certificaat niet vóór de deadline van 27 augustus is uitgegeven?

Lopende openbare SSL/TLS-certificaatorders met een geldigheidsduur van meer dan 397 dagen worden automatisch omgezet naar een meerjarenabonnement.

Dit betekent het volgende:

  • Het meerjarenabonnement is geldig vanaf de aankoop.

    Als u bijv een 2-jarig certificaat heeft besteld, is het meerjarenabonnement 24 maanden geldig.

  • Het eerste certificaat in de order wordt uitgegeven met een maximale geldigheid van 397 dagen.

  • Om de resterende dekking van de order te gebruiken, moet u het certificaat opnieuw uitgeven tijdens de laatste 397 dagen van de order.

How does this affect my existing 1-year public TLS certificates?

This change doesn’t affect active certificates with a validity greater than 199 days issued before the February 24, 2026, deadline. These certificates remain trusted until they expire.

For example, on February 1, 2026, you bought a 1-year OV TLS certificate. We issued the certificate on February 3, 2026. When the certificate nears its expiration date, instead of renewing another 1-year TLS certificate, you renew it with a 199-day certificate on an annual plan.

How does this affect my 1-year certificate reissues and duplicate issues?

The shortened maximum certificate lifecycle period of 199 days does affect public 1-year TLS certificates reissues and duplicates. Now, when you reissue or duplicate a 1-year TLS certificate, the new certificate's validity can’t exceed 199 days. This means some reissued certificates may expire before the order expires.

To use the remaining validity included with the order, reissue your certificate during the final 199 days of the order. You may request reissues with a validity of up to 199 days, or until the order expires, whichever is sooner.

voorbeeld 1. Example: Reissuing a 1-year public TLS certificate now
  1. On February 23, 2026, we issued your 1-year Basic OV TLS certificate, your original certificate. This certificate has a validity of 365 days and expires on February 23, 2027, at the same time, the order expires.

    • Order validity term: February 23, 2026 – February23, 2027 (365 days)

    • Certificate validity term: February 23, 2026 – February23, 2027 (365 days)

  2. On February 25, 2026, the day after DigiCert implemented the new 199-day maximum validity change, you reissue the certificate. This reissued certificate has a maximum validity of 199 days and expires on September 12, 2026.

    • First reissued certificate validity term: February 25, 2026 – September 12, 2026 (199 days)

  3. On September 9, 2026, you reissue the certificate. This reissued certificate has a validity of 167 days because certificate validity can’t exceed the order validity.

    • Second reissued certificate validity term: September 9, 2026 – February 23, 2027 (167 days)

  4. If you need to reissue a 1-year public TLS certificate and have questions about what to expect during the reissue, contact your account manager or DigiCert Support before reissuing it.


How does this affect my public TLS/SSL certificate renewals?

The renewal process remains the same. You can reissue a TLS certificate at any time and renew a TLS order up to 90 days before it expires.

Maximum validity period timeline for public TLS/SSL in the CA/Browser Forum

On February 24, 2026, DigiCert began issuing 199-day public TLS certificates in accordance with the new industry requirements. However, the maximum validity for TLS certificates doesn't stay at 199 days for long. In early 2027, the maximum validity is reduced again to 99 days. Then, in early 2029, the maximum validity is reduced one more time to 46 days. To learn more about reducing public TLS certificate validity to 46 days, read our blog, TLS Certificate Lifetimes Will Officially Reduce to 47 days.

tabel 1. CA/Browser Forum due dates and DigiCert timelines for reducing TLS certificate validity

CA/Browser Forum

DigiCert

Maximum certificate validity

Due date

Maximum certificate validity 1

Timeline

200 days

Between March 15, 2026, and March 15, 2027

199 days

Between February 24, 2026, and early 20272

100 days

Between March 15, 2027, and March 15, 2029

99 days

Between early 2027 and early 20292

47 days

After of March 15, 2029

46 days

After early 20292

1DigiCert's maximum certificate validity is one day shorter than that allowed by the CA/Browser Forum. We do this to avoid exceeding the maximum permitted validity.

2Future release dates are subject to change based on the latest CA/Browser Forum requirements.