CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 30 – Reserved Domain Names

Ballot 30 – Reserved Domain Names

Ballot 30 – Reserved Domain Names (Failed)

Motion

Ben Wilson made the following motion, and Eddy Nigg and Bruce Morton endorsed it.

Motion begins

Effective 90 days following ratification of the ballot, the Guidelines should be amended by the following errata.

Errata begin

Delete Section 6(a)(2) and replace it with: “(2) Domain name Certificate Field subjectAlternativeName:dNSName Required/Optional Required Contents There MUST be at least one instance of this field that is associated with the Subject’s server(s), which MAY be owned and operated by the Subject or another entity (e.g., a hosting service).

Each instance MUST only contain a fully qualified domain name verified in accordance with Section 18. The asterisk (*) wildcard character MUST NOT be used.

Certificate Field subject:commonName (OID 2.5.4.3) Required/Optional Optional (but recommended) Contents There MUST NOT be more than one instance of the commonName field in the subjectName field and, if present, it MUST have the same value as the verified fully qualified domain name in one of the SubjectAlternativeName:dNSName fields that is also present in the certificate.”

Delete Section 12(b)(4) and replace it with: “(4) Use of EV Certificate An obligation and warranty to install the EV Certificate only on server(s) accessible at a domain name listed on the EV Certificate, and to use the EV Certificate solely in compliance with all applicable laws, solely for authorized company business, and solely in accordance with the Subscriber Agreement;”

Delete Section 18(b)(1)(A) and replace it with: “(A) Performing a WHOIS inquiry on the Internet for the domain name Supplied by Applicant or contacting the domain registrar, and obtaining a response indicating that Applicant or a Parent/Subsidiary Company is the entity registered to the domain name; or”

Errata end

Motion ends

The ballot review period comes into effect at 2100 UTC on 24 July 09 and will close at 2100 UTC on 31 July 2009. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 2100 UTC on 7 Aug 2009.

Votes must be cast by ‘reply all’ to this email.

A vote in favour of the motion must indicate a clear ‘yes’ in the response. A vote against must indicate a clear ‘no’ in the response. A vote to abstain must indicate a clear ‘abstain’ in the response. Unclear responses will not be counted.

The latest vote received from any representative of a voting member before the close of the voting period will be counted.

Latest releases
Server Certificate Requirements
SC098: Process RFC 8657 CAA Parameters - Jun 16, 2026

Code Signing Requirements
v3.8 - Aug 5, 2024

What’s Changed CSC-25: Import EV Guidelines to CS Baseline Requirements by @dzacharo in https://github.com/cabforum/code-signing/pull/38 Full Changelog: https://github.com/cabforum/code-signing/compare/v3.7...v3.8

S/MIME Requirements
v1.0.15 - Ballot SMC017v2 - Jul 30, 2026

This ballot increases the minimum RSA key size for Root and Subordinate CA certificates in the S/MIME BRs from 2048 to 4096 bits for keys created after September 15, 2026, while retaining the 2048-bit minimum for Subscriber certificates. The ballot further requires that by September 15, 2027, CAs SHALL NOT issue Subscriber certificates from any Sub-CA whose RSA key modulus is less than 3072 bits, effectively sunsetting issuance from legacy 2048-bit Sub-CAs. The ballot also includes minor typographic corrections. This ballot is proposed by Martijn Katerbarg (Sectigo) and endorsed by Ben Wilson (Mozilla) and Stephen Davidson (DigiCert)

Network and Certificate System Security Requirements
Version 2.0.5 (Ballot NS-008) - Jul 9, 2025

Edit this page
The Certification Authority Browser Forum (CA/Browser Forum) is a voluntary gathering of Certificate Issuers and suppliers of Internet browser software and other applications that use certificates (Certificate Consumers).