What is a certificate authority (CA)?

What is a certificate authority (CA)?

A certificate authority (CA) issues digital certificates and vouches for the binding between the data items in a certificate. That is the definition in RFC 4949. The NIST glossary calls it an entity authorized to create, sign, issue and revoke public key certificates.

The CA/Browser Forum requirements describe it as the organization responsible for the creation, issuance, revocation and management of certificates. Besides “certification authority”, English also has “certificate authority”; RFC 4949 discourages that spelling and prefers “certification authority”. Where the CA fits into a PKI is explained in What is a PKI?.

What does a CA actually do?

The tasks can be read off the definitions:

  • Issue and sign: according to RFC 5280, the binding of a key to a subject is asserted by having a trusted CA digitally sign each certificate. With the signature it certifies the information in the certificate.
  • Manage the life cycle: RFC 4949 makes the CA responsible for the life cycle of certificates.
  • Provide the revocation status: RFC 5280 makes CAs responsible for indicating the revocation status of the certificates they issue, by OCSP, by certificate revocation list (CRL), or by some other mechanism.

A CA can delegate checking applicants to a registration authority (RA). Signing the certificate stays with the CA.

How does a public CA check a request?

For certificates meant to work in browsers, Mozilla requires the CA to ensure that the applicant is authorized to use all domain names in the certificate and controls all IP addresses in it. According to Mozilla, domain name validation must use one of the methods in section 3.2.2.4 of the CA/Browser Forum Baseline Requirements, and IP address validation one of the methods in section 3.2.2.5.

When must a CA revoke a certificate?

The Baseline Requirements list cases in which a CA must revoke a certificate within 24 hours, except for short-lived certificates. One of them: the CA obtains evidence that the subscriber’s private key suffered a key compromise. Another: the subscriber requests revocation in writing.

What is the difference between a root CA and an intermediate CA?

According to the Baseline Requirements, the root CA is the top-level certification authority whose root certificate is distributed by application software suppliers and which issues subordinate CA certificates. The root certificate is self-signed.

A subordinate CA is a CA whose certificate is signed by the root CA or by another subordinate CA. The Common CA Database (CCADB) treats “intermediate” and “subordinate” as synonymous. How levels are built in practice is shown in Building a PKI.

What kinds of certificate authorities are there?

By the group of users, there are two kinds: public CAs, trusted by browsers and operating systems, and private CAs, which one organization runs and makes known to its own devices.

Why do browsers trust a public CA?

According to the Baseline Requirements, a publicly-trusted certificate is trusted because its root certificate is distributed as a trust anchor in widely-available application software. Which roots are included is decided by the operator of each root store, under its own policy:

  • Mozilla includes a set of root certificates with Firefox, Thunderbird and other products, governed by the Mozilla Root Store Policy.
  • Apple states in its root program policy that Apple operating systems and applications such as Safari and Mail use a common store for root CA certificates.
  • Microsoft describes its root program as supporting the distribution of root certificates so that customers can trust Windows products. According to its repository, Microsoft publishes future changes to the requirements on GitHub.

CAs in Mozilla’s root store must conform to the CA/Browser Forum Baseline Requirements. By their own statement, those requirements are not mandatory unless and until application software suppliers adopt and enforce them.

Where can I see which public CAs exist?

The directories of the root programs answer that. Mozilla publishes a list of all root certificates Firefox trusts for SSL/TLS, with contact information and geographical focus of the owning CA.

The Common CA Database of the Linux Foundation holds information on CAs whose root and intermediate certificates are included in the products of several root store operators. According to the CCADB policy, a CA must disclose the subordinate CAs under those roots within seven calendar days of issuance.

Which certificate types does a public CA issue?

The Baseline Requirements know four types: Domain Validated (DV), Individual Validated (IV), Organization Validated (OV) and Extended Validation (EV). They differ in the amount of subject information included in the certificate.

On this the Baseline Requirements state: all certificates provide the same level of assurance of the device identity, that is, of the domain name or IP address.

How long are certificates from public CAs valid?

The Baseline Requirements (version 2.3.1, in effect since 4 October 2026 according to the version table) limit the validity of subscriber certificates by issue date:

  • issued from 15 March 2026: at most 200 days,
  • issued from 15 March 2027: at most 100 days,
  • issued from 15 March 2029: at most 47 days.

How does a private CA work?

A private (internal) CA issues certificates for your own needs, such as internal servers and devices. The Baseline Requirements expressly do not cover enterprises that run their own PKI for internal purposes only and whose root is not distributed by any application software supplier.

That leaves the CA’s tasks with you: issuing, checking applicants, revoking. And the root has to reach the clients: according to RFC 4949, the root’s public key is distributed in a way that does not depend on the PKI’s certification relationships. According to RFC 5280, choosing the trust anchor is a matter of policy.

What happens if a client does not know the root?

It reports an unknown root CA, even when the server sends the complete chain. Causes and remedies per client are in Internal CA: unknown root.

When does which CA fit?

A service that outsiders open with their browser needs a certificate whose root their browsers already know. For services used only by your organization’s own devices, a private CA is also an option, provided you distribute its root to those devices. The steps for Windows are in Setting up your own certificate authority (CA) on Windows, the operating models in Managed PKI or your own PKI.

Sources

Let's talk

Free initial consultation - no sales pitch, just an honest assessment.

Request a consultation →