CA Owners MUST ensure that all TLS server authentication precertificates issued by such CAs are logged to at least one (1) CT log recognized by Chrome as Usable or Qualified before issuing the corresponding certificate.
What is the effective date for CA Owners MUST ensure that all TLS server authentication precertificates issued by such CAs are logged to at least one (1) CT log recognized by Chrome as Usable or Qualified before issuing the corresponding certificate.?
For CA Owners MUST ensure that all TLS server authentication precertificates issued by such CAs are logged to at least one (1) CT log recognized by Chrome as Usable or Qualified before issuing the corresponding certificate., effective date is 2026-06-15; authority is Google Chrome Root Program; scope is CAs included in the Chrome Root Store, recorded from its source on 2026-08-05.
Effective June 15, 2026 , CA Owners with CA certificates that validate to a certificate included in the Chrome Root Store MUST ensure that all TLS server authentication precertificates issued by such CAs are logged to at least one (1) CT log recognized by Chrome as
— googlechrome.github.io, retrieved 2026-08-05
2026-06-15
The date this requirement takes effect, as printed in the issuing programme's own effective-date table. Verified against the passage quoted below.
- Requirement
- CA Owners MUST ensure that all TLS server authentication precertificates issued by such CAs are logged to at least one (1) CT log recognized by Chrome as Usable or Qualified before issuing the corresponding certificate.
- Effective date
- 2026-06-15
- Authority
- Google Chrome Root Program our reading
- Scope
- CAs included in the Chrome Root Store our reading
Values marked our reading are our classification of what the source says — the source does not print them in those words. The quote below is the evidence for each one; judge it yourself.
Source
- googlechrome.github.iohttps://googlechrome.github.io/chromerootprogram/
This one changes, and we watch it.TLS certificate and CA requirement effective dates (CA/Browser Forum, Chrome, Mozilla) is re-read on a schedule and every change is dated. Subscribe: Atom feed · JSON · what has changed so far.