CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 21 – Phone Number at Place of Business

Ballot 21 – Phone Number at Place of Business

Ballot 21 – Phone Number at Place of Business (Passed Unanimously)

Motion

Ken Bretschneider made the following motion, and Nick Hales and Bruce Morton endorsed it.

Motion begins

The Guidelines should be amended in accordance with the following erratum.

Erratum begins

Delete Section 16b and replace it with the following.

(b) Telephone Number for Applicant’s Place of Business

(1) Verification Requirements To further verify Applicant’s physical existence and business presence, as well as to assist in confirming other verification requirements, the CA MUST verify that the telephone number provided by Applicant is a main phone number for Applicant’s Place of Business.

(2) Acceptable Methods of Verification To verify Applicant’s telephone number, the CA MUST perform A and either B or C as listed below:

(A) Confirm Applicant’s telephone number by calling it and obtaining an affirmative response sufficient to enable a reasonable person to conclude that Applicant is reachable by telephone at the number dialed;

(B) Confirm that the telephone number provided by Applicant is listed as Applicant’s or Parent/Subsidiary Company’s telephone number for the verified address of its Place of Business in records provided by the applicable phone company, or, alternatively, in either at least one Qualified Independent Information Source or Qualified Governmental Information Source, or in a Qualified Governmental Tax Information Source;

(C) Rely on a Verified Legal Opinion or a Verified Accountant Letter to the effect that Applicant’s telephone number, as provided, is a main phone number for Applicant’s Place of Business.

Erratum ends

Motion ends

The ballot review period comes into effect at 1700 EDT on (Thursday) 20 Nov 2008, and will close at 1700 EDT on (Thursday) 27 Nov 2008. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 1700 EDT on (Thursday) 4 Dec 2008.

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
SC099: Improve Recording of Validation Methods - May 19, 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.14 - Ballot SMC016 - May 5, 2026

This ballot maintains consistency between the S/MIME Baseline Requirements and the TLS Baseline Requirements with changes introduced by Ballots SC096 and SC097. Specifically, this ballot: Creates a carve-out of the logging requirements for DNSSEC specifically, stating these are not in scope. For audit purposes, change management logging is able to confirm if the appropriate controls are in effect or not. Sunsets all remaining use of SHA-1 signatures in Certificates and CRLs. It is noted that most uses of SHA-1 signatures are already deprecated by SC097. With this ballot, all unexpired Subordinate CA Certificates issuing S/MIME containing the SHA-1 signature algorithm must be revoked. This proposal does not prohibit the use of SHA-1 to generate issuerKeyHash or issuerNameHash values as currently required by RFC 5019. Includes minor formatting corrections.

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).