CA:Information template

General

There is a link on the How_to_apply page that will automatically create the bug to request root inclusion, with all of the appropriate fields filled in and with a template in the bug description field for the CA Details and Certificate Details listed below.

Using the link, a bug will be created with the following fields set:

• Product: mozilla.org
• Component: CA Certificates
• Version: Other
• Severity: enhancement
• Platform: All
• OS: All
• Summary: Add [your CA's name] root certificate(s)
• Description: [see below]

Note: It is strongly recommended that you use the link on the How_to_apply page to avoid errors in creating the root inclusion request. However, if needed, you can manually create the bug: Go to the Bug Entry Page, click on Other Products, and select mozilla.org under Other.

CA Details

CA Company/Organization Name:
Website:
One Paragraph Summary of CA Company/Organization, including the following:

• General nature (e.g., commercial, government, academic/research, nonprofit)
• Primary geographical area(s) served
• Number and type of subordinate CAs

Audit Type (WebTrust, ETSI etc.):
Auditor:
Auditor Website:
Audit Document URL(s):

Certificate Details

(To be completed once for each certificate; note that we only include root certificates in the store, not intermediates.)

Certificate Name:
Summary Paragraph, including the following:

• End entity certificate issuance policy, i.e. what you plan to do with the root

Diagram and/or description of certificate hierarchy:

• Number and type of subordinate CAs
• List or description of subordinate CAs operated internally
• List or description of subordinate CAs operated by third parties
• List root CAs that have issued cross-signing certificates for this root CA

Certificate HTTP download URL (on CA website):
Version:
SHA1 Fingerprint:
Public key length (for RSA, modulus length) in bits:
Valid From (YYYY-MM-DD):
Valid To (YYYY-MM-DD):
CRL HTTP URL:
CRL issuing frequency for end-entity certificates:
OCSP URL:
Class (domain-validated, identity/organisationally-validated or EV):
EV policy OID(s) (if applicable):
Certificate Policy URL:
CPS URL:
List one or more Trust Bits to enable, choices are Websites (SSL/TLS), Email (S/MIME), and/or Code (code/document signing):
URL of website whose SSL certificate chains to this root (if applying for SSL):