All unexpired and unrevoked subordinate CA certificates signed by a root CA certificate included in the Chrome Root Store MUST be integrated with an automation solution.
What is the effective date for All unexpired and unrevoked subordinate CA certificates signed by a root CA certificate included in the Chrome Root Store MUST be integrated with an automation solution.?
For All unexpired and unrevoked subordinate CA certificates signed by a root CA certificate included in the Chrome Root Store MUST be integrated with an automation solution., effective date is 2027-03-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 March 15, 2027 , all unexpired and unrevoked subordinate CA certificates signed by a root CA certificate included in the Chrome Root Store MUST be integrated with an automation solution
— googlechrome.github.io, retrieved 2026-08-05
2027-03-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
- All unexpired and unrevoked subordinate CA certificates signed by a root CA certificate included in the Chrome Root Store MUST be integrated with an automation solution.
- Effective date
- 2027-03-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.