Dataset Viewer
Auto-converted to Parquet Duplicate
ca_name
string
derived_fields
list
id
string
max_validity_days
string
notes
string
source
string
source_quote
string
still_active
string
url
string
verified_fields
list
next_reduction_date
timestamp[s]
profile
string
effective_since
timestamp[s]
next_reduction_days
string
Actalis
[ "notes", "still_active" ]
actalis
184
Certificates show a duration of 6 months; annual coverage is guaranteed through a second certificate available in the customer area after 168 days, with a 16-day activation window between the 169th and 184th day. A renewal certificate issued within 184 days carries 184 days plus the remaining period of the previous cer...
https://guide.actalis.com/faq/Certificate-Validity/Certificate-Validity
Yes. If renewal occurs within 184 days, a renewal certificate is issued with a duration equal to 184 days plus the remaining period of the previous certificate.
yes
https://referencesource.org/ca-issuance-validity/actalis/
[ "ca_name", "max_validity_days" ]
null
null
null
null
Amazon Trust Services (ACM)
[ "next_reduction_date", "notes", "profile", "still_active" ]
amazon-trust-services-acm
198
A reduction from the previous lifetime of 395 days. As of March 15, 2027, the maximum lifetime will be less than 100 days; as of March 15, 2029, less than 47 days.
https://aws.amazon.com/certificate-manager/faqs/
From today until March 15, 2027, the maximum lifetime for a public TLS certificate issued will be 198 days. This is a reduction from the previous lifetime of 395 days.
yes
https://referencesource.org/ca-issuance-validity/amazon-trust-services-acm/
[ "max_validity_days" ]
2027-03-15T00:00:00
ACM-issued public
null
null
Buypass
[ "notes", "still_active" ]
buypass
null
Last day to order, renew, or replace: 15.10.2025; last day for issuance: 31.10.2025. Existing TLS/SSL certificates remain valid until expiry; revocation and certificate status services run until 31.10.2026 (TLS/SSL) and 31.10.2027 (PSD2).
https://www.buypass.com/products/tls-ssl-certificates/discontinues-issuance-of-tls-ssl-certificates
August 18th 2025: As of 15 October 2025, Buypass will no longer offer TLS/SSL certificates. The decision is based on a comprehensive assessment of the market situation and the regulatory framework for issuing TLS/SSL certificates.
no
https://referencesource.org/ca-issuance-validity/buypass/
[ "ca_name" ]
null
null
null
null
DigiCert
[ "effective_since", "notes", "still_active" ]
digicert
199
DigiCert's maxima are one day shorter than the CA/Browser Forum ceiling; the 99-day maximum applies between early 2027 and early 2029, with a 46-day maximum from early 2029.
https://knowledge.digicert.com/alerts/public-tls-certificates-199-day-validity
Additionally, all public TLS certificates issued on or after February 24, 2026, cannot exceed the new 199-day maximum validity.
yes
https://referencesource.org/ca-issuance-validity/digicert/
[ "ca_name", "max_validity_days", "next_reduction_days" ]
null
null
2026-02-24T00:00:00
99
Entrust
[ "notes", "still_active" ]
entrust
null
Entrust sold its public certificate business to Sectigo (announced January 29, 2025); former Entrust public certificate customers are now Sectigo customers and Entrust no longer issues publicly-trusted TLS certificates.
https://www.sectigo.com/resource-library/sectigo-acquires-entrust-public-certificate-business
today announced the purchase of Entrust’s public certificate business, marking a transformative milestone in the company’s history
no
https://referencesource.org/ca-issuance-validity/entrust/
[ "ca_name" ]
null
null
null
null
GlobalSign
[ "profile", "still_active" ]
globalsign
199
null
https://support.globalsign.com/ssl/general-information/maximum-certificate-validity
Product | Maximum Validity | AlphaSSL | 199 Days |
yes
https://referencesource.org/ca-issuance-validity/globalsign/
[ "ca_name", "max_validity_days" ]
null
AlphaSSL
null
null
GlobalSign
[ "profile", "still_active" ]
globalsign-2
199
null
https://support.globalsign.com/ssl/general-information/maximum-certificate-validity
DomainSSL | 199 Days |
yes
https://referencesource.org/ca-issuance-validity/globalsign-2/
[ "ca_name", "max_validity_days" ]
null
DomainSSL
null
null
GlobalSign
[ "profile", "still_active" ]
globalsign-3
199
null
https://support.globalsign.com/ssl/general-information/maximum-certificate-validity
ExtendedSSL | 199 Days |
yes
https://referencesource.org/ca-issuance-validity/globalsign-3/
[ "ca_name", "max_validity_days" ]
null
ExtendedSSL
null
null
GlobalSign
[ "profile", "still_active" ]
globalsign-4
199
null
https://support.globalsign.com/ssl/general-information/maximum-certificate-validity
OrganizationSSL | 199 Days |
yes
https://referencesource.org/ca-issuance-validity/globalsign-4/
[ "ca_name", "max_validity_days" ]
null
OrganizationSSL
null
null
GlobalSign
[ "notes", "profile", "still_active" ]
globalsign-5
199
Effective March 15, 2026, certificates issued on or after this date are limited by the CA/B Forum Baseline Requirements to a maximum validity of 200 days; GlobalSign's product table lists 199 days for all TLS products.
https://support.globalsign.com/ssl/general-information/maximum-certificate-validity
CloudSSL | 199 Days |
yes
https://referencesource.org/ca-issuance-validity/globalsign-5/
[ "ca_name", "max_validity_days" ]
null
CloudSSL
null
null
GoDaddy
[ "notes", "profile", "still_active" ]
godaddy
90
90-day certificates are available to customers with GoDaddy Websites + Marketing, Managed Hosting for WordPress, or Paylinks plans and Managed SSL subscriptions; the page states Self-Managed or Do-It-Yourself SSL certificates 'will continue with yearly validation', but the page predates the 2026 industry reduction and ...
https://www.godaddy.com/help/all-about-90-day-ssl-certificates-42440
90-Day SSL certificates are certificates that automatically reprovision every 90 days instead of the current 1-year standard.
yes
https://referencesource.org/ca-issuance-validity/godaddy/
[ "ca_name", "max_validity_days" ]
null
Managed SSL 90-Day
null
null
Google Trust Services
[ "notes", "still_active" ]
google-trust-services
93
Per TLS CP/CPS section 6.3.2. SXG subscriber certificates are issued for a period of 48 days or less. A day is measured as 86,400 seconds.
https://pki.goog/repo/cp-cps-tls/6.2/GTS-CP-CPS-TLS.html
Leaf Certificates are issued for a period of 93 days or less. SXG subscriber certificates are issued for a period of 48 days or less. A day is measured as 86,400 seconds.
yes
https://referencesource.org/ca-issuance-validity/google-trust-services/
[ "ca_name", "max_validity_days" ]
null
null
null
null
Google Trust Services
[ "notes", "profile", "still_active" ]
google-trust-services-2
48
Signed Exchange (SXG) subscriber certificates, per TLS CP/CPS section 6.3.2.
https://pki.goog/repo/cp-cps-tls/6.2/GTS-CP-CPS-TLS.html
SXG subscriber certificates are issued for a period of 48 days or less.
yes
https://referencesource.org/ca-issuance-validity/google-trust-services-2/
[ "ca_name", "max_validity_days" ]
null
SXG subscriber
null
null
HARICA
[ "effective_since", "notes", "still_active" ]
harica
199
Reduction from 365 days (previously issued at up to 397 days maximum). Implemented gradually 9-13 March 2026; after 13 March all newly issued Server Certificates carry the 199-day maximum. Source is a RedIRIS (HARICA reseller partner) page reproducing HARICA's subscriber announcement verbatim; HARICA published no direc...
https://www.rediris.es/tcs/news/2026/20260304-reduccion_199_dias.html
As part of our ongoing compliance measures, HARICA will reduce the maximum validity period for Server Certificates from 365 days to 199 days .
yes
https://referencesource.org/ca-issuance-validity/harica/
[ "ca_name", "max_validity_days" ]
null
null
2026-03-13T00:00:00
null
IdenTrust
[ "notes", "still_active" ]
identrust
200
Under the new policy, initial certificate issuance covers a period of 184 days (approximately six months), followed by a 15-day renewal window. The change was published 11/13/2025 and takes effect March 10, 2026.
https://www.identrust.com/support/announcements
Effective March 10, 2026, IdenTrust will reduce the maximum validity period of the TLS certificates we issue to 200 days, in alignment with CA/Browser Forum Baseline Requirements to maintain global browser trust.
yes
https://referencesource.org/ca-issuance-validity/identrust/
[ "ca_name", "max_validity_days" ]
null
null
null
null
Let's Encrypt
[ "notes", "profile", "still_active" ]
let-s-encrypt
45
Valid for only 45 days, in preparation for upcoming restrictions that will limit all certificates to at most 47 days.
https://letsencrypt.org/docs/profiles/
And finally the resulting certificate is valid for only 45 days, in preparation for upcoming restrictions that will limit all certificates to at most 47 days.
yes
https://referencesource.org/ca-issuance-validity/let-s-encrypt/
[ "ca_name", "max_validity_days" ]
null
tlsserver
null
null
Let's Encrypt
[ "notes", "profile", "still_active" ]
let-s-encrypt-2
6
Validity Period is stated as 160 hours in the profile table; qualifies as a Short-Lived Subscriber Certificate under the Baseline Requirements and needs no revocation information.
https://letsencrypt.org/docs/profiles/
The shortlived profile is identical to the tlsserver profile, with one key distinction: the resulting certificate is only valid for 6ish days.
yes
https://referencesource.org/ca-issuance-validity/let-s-encrypt-2/
[ "ca_name" ]
null
shortlived
null
null
Let's Encrypt
[ "notes", "profile", "still_active" ]
let-s-encrypt-3
90
The FAQ states the default lifetime; the profiles documentation names the default profile 'classic'. Let's Encrypt recommends renewing 90 day certificates every 60 days. There is no way to adjust these lifetimes.
https://letsencrypt.org/docs/faq/
Our default certificates are valid for 90 days.
yes
https://referencesource.org/ca-issuance-validity/let-s-encrypt-3/
[ "ca_name", "max_validity_days" ]
null
classic
null
null
Sectigo
[ "notes", "still_active" ]
sectigo
199
199 days is described as 6 months plus extra time to renew. Domain Control Validation reuse is limited to 198 days from the same date. Sectigo acquired Entrust's public certificate business (completed September 18, 2025).
https://www.sectigo.com/resource-library/shorter-validity-periods-for-tls-certificates-and-dcv
To align with evolving industry requirements, Sectigo will begin enforcing a maximum TLS certificate validity of 199 days starting March 12, 2026.
yes
https://referencesource.org/ca-issuance-validity/sectigo/
[ "ca_name", "max_validity_days" ]
null
null
null
null
SSL.com
[ "notes", "still_active" ]
ssl-com
198
SSL.com issues 198 days, or the remaining duration of the certificate order, whichever is shorter; previously issued for 396 days. A purchase still represents a 12-month license period fulfilled through reissued 198-day certificates. The change took effect March 11, 2026.
https://www.ssl.com/blog/ssl-certificate-validity/
To comply with the new requirement, SSL now issues certificates for 198 days, or the remaining duration of the certificate order, whichever is shorter.
yes
https://referencesource.org/ca-issuance-validity/ssl-com/
[ "ca_name", "max_validity_days" ]
null
null
null
null
ZeroSSL
[ "effective_since", "notes", "profile", "still_active" ]
zerossl
200
Annual certificates provide one year of coverage through multiple certificate issuances; every new certificate follows the 200-day limit and requires a mid-term reissuance to cover the full 1-year period. ZeroSSL no longer offers single 1-year certificate issuances.
https://help.zerossl.com/hc/en-us/articles/34330849350173-SSL-TLS-Certificate-Validity-Changes-New-200-Day-Limit-Explained
Starting March 15, 2026, SSL/TLS certificates can be issued for a maximum of 200 days . This reflects a shift from the previous 1‑year validity model to a shorter, more secure lifecycle.
yes
https://referencesource.org/ca-issuance-validity/zerossl/
[ "ca_name", "max_validity_days" ]
null
Annual
2026-03-15T00:00:00
null
ZeroSSL
[ "notes", "profile", "still_active" ]
zerossl-2
90
Free ACME-issued certificates are 90 days, renewable automatically with any major ACME client.
https://zerossl.com/features/acme/
ACME integrations let you order and renew 90-day certificates automatically and free of charge, using any major ACME client:
yes
https://referencesource.org/ca-issuance-validity/zerossl-2/
[ "ca_name", "max_validity_days" ]
null
ACME/free
null
null

TLS certificate maximum validity by Certificate Authority: what each CA actually issues today

Canonical, always-current version: https://referencesource.org/ca-issuance-validity/ Machine-readable: https://referencesource.org/ca-issuance-validity/data.json — this mirror is a point-in-time copy.

  • Last verified: 2026-08-18
  • Stale after: 2026-09-17 (past this date, prefer the canonical copy — it re-verifies on a cadence this snapshot does not)
  • Records: 22

Per-CA table of the maximum TLS certificate validity period each publicly-trusted Certificate Authority actually issues today, with the date the current limit took effect and any announced future reductions. Many CAs issue below the CA/Browser Forum BR ceiling (currently 200 days since March 15, 2026): DigiCert cut to 199 days from February 24, 2026 (three weeks early); Let's Encrypt issues 90 days on its classic profile, 45 days on its tlsserver profile, and 6 days on its shortlived profile; Google Trust Services issues at most 93 days by CP/CPS v6.2; Amazon ACM issues 198 days; Actalis issues 184 days. Entrust sold its public certificate business to Sectigo in January 2025 (completed September 18, 2025) and no longer issues publicly-trusted TLS certificates. Buypass stopped issuing TLS certificates on October 31, 2025. No single page anywhere publishes this side-by-side; the data layer under any CA-aware planner or renewal tool must be assembled from each CA's own announcements. Answers 'what is the maximum TLS certificate validity for Let's Encrypt?', 'how long does DigiCert issue certificates?', 'which CA issues shorter certificates than the BR maximum?', 'does Google Trust Services issue 200-day certificates?', 'what CA is issuing 90-day certificates now?', and 'what happened to Entrust TLS certificates?'

Provenance — what every record carries

Every record carries source (the URL the value was read from) and source_quote (a verbatim quote from that page stating it). A value you cannot check against its page is indistinguishable from an invented one; these can all be checked. Each record is also individually addressable on the canonical site at its url.

Licence position

Facts extracted from each CA's own publicly-published documentation, announcements, and certification practice statements. Certificate validity limits are regulatory facts, not creative expression. Each record quotes a short verbatim span and links to the CA's own page.

Facts are not copyrightable; what this dataset takes from each source is a fact plus a short attributed quote linking back to the page that states it.

Sources

Fields

See any record in data/records.jsonl — field names are self-describing, and the canonical page for each record renders them with labels: https://referencesource.org/ca-issuance-validity/

Downloads last month
35