Reference Source

CAs MUST process the accounturi and validationmethods parameters as specified in RFC 8657.

For CAs MUST process the accounturi and validationmethods parameters as specified in RFC 8657., requirement is CAs MUST process the accounturi and validationmethods parameters as specified in RFC 8657; effective date is 2027-03-15; baseline requirements section is 4.2.2.1.2; authority is CA/Browser Forum TLS Baseline Requirements; scope is all publicly-trusted CAs issuing TLS server certificates, recorded from its source on 2026-08-05.

Requirement
CAs MUST process the accounturi and validationmethods parameters as specified in RFC 8657. verified
Effective date
2027-03-15
Baseline Requirements section
4.2.2.1.2
Authority
CA/Browser Forum TLS Baseline Requirements our reading
Scope
all publicly-trusted CAs issuing TLS server certificates our reading
Sourcecabforum.org
Verified2026-08-05
Review by2026-11-03
DatasetTLS certificate and CA requirement effective dates (CA/Browser Forum, Chrome, Mozilla)

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.

What the source says

CAs MUST process the accounturi and validationmethods parameters as specified in <https://datatracker.ietf.org/doc/html/rfc8657> RFC 8657

cabforum.org, retrieved 2026-08-05

Source

Last verified against source: 2026-08-05. Due for re-check by 2026-11-03. This page as Markdown · OKF bundle · full dataset as JSON.