Certificate authority (CA)
What is Certificate authority (CA)?
A certificate authority (CA) is an organization trusted, under the X.509 framework in RFC 5280, to verify a domain's identity and sign a TLS certificate vouching for it, chained back to a root that browsers trust directly. AdminKit's SSL check tool shows the certificate authority and chain a live site actually presents.
By AdminKit team, Netbase JSC · Updated
A certificate authority (CA) is an organization trusted, under the X.509 framework defined in RFC 5280 (document record at the IETF Datatracker), to verify a domain’s or organization’s identity and sign a TLS certificate vouching for it, one piece of the broader public key infrastructure that underpins HTTPS trust. Browsers and operating systems ship with a built-in list of root CAs they trust directly; a CA issues certificates either directly off a root or, far more commonly, off an intermediate certificate, forming a certificate chain back to that root, which lets the root’s private key stay offline and protected while day-to-day issuance happens lower down the chain. The CA/Browser Forum Baseline Requirements set the minimum validation and issuance rules every publicly trusted CA has to follow. A certificate signed by its own private key instead of a CA’s — a self-signed certificate — skips this chain of trust entirely. A CA’s trust is conditional, not permanent: root programs can and do remove a CA that mis-issues certificates or fails an audit, which immediately breaks every certificate it ever signed. Mozilla’s Root Store Policy, for example, states that Mozilla will disable or remove a CA certificate if the CA operator demonstrates ongoing or egregious practices that do not comply with the policy’s requirements. Most publicly trusted CAs today validate only domain control before issuing, a narrower check than validating organizational identity, though both produce a cryptographically identical certificate once issued.
How CA trust actually works:
- Root CAs are trusted directly by browsers/OSes; most issuance happens off an intermediate chained to a root.
- Trust is conditional: a root program can and does remove a CA that mis-issues or fails an audit.
- Domain-validated and organization-validated certificates look cryptographically identical once issued.
Frequently asked questions
Is a CA's trust permanent once a browser accepts it?
No -- a CA's trust is conditional, not permanent. Root programs can and do remove a CA that mis-issues certificates or fails an audit, which immediately breaks every certificate it ever signed.
Do most CAs issue certificates directly from their root key?
No -- a CA far more commonly issues off an intermediate certificate, forming a chain back to the root, which lets the root's private key stay offline and protected while day-to-day issuance happens lower down the chain.
What's the difference between a domain-validated and organization-validated certificate?
Domain validation only confirms control of the domain; organization validation also verifies organizational identity, a stricter check. Both produce a cryptographically identical certificate once issued, so the difference is in the vetting, not the resulting file.
What sets the minimum rules a publicly trusted CA must follow?
The CA/Browser Forum Baseline Requirements set the minimum validation and issuance rules every publicly trusted CA has to follow, on top of the X.509 framework RFC 5280 defines.