Datasets:

referencesource
/

ca-issuance-validity

pretty_name: >-
  TLS certificate maximum validity by Certificate Authority: what each CA
  actually issues today
license: other
license_name: source-terms-cited
license_link: https://referencesource.org/ca-issuance-validity/
language:
  - en
tags:
  - reference-data
  - provenance
  - referencesource-org
configs:
  - config_name: default
    data_files:
      - split: train
        path: data/records.jsonl

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-09-29
Stale after: 2026-10-29 (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/