What is Root Certificate?
Also known as: Root CA
A root certificate is a self-signed X.509 certificate issued by a certificate authority (CA) and distributed in operating system and browser trust stores to anchor the chain of trust for TLS.
A root certificate is a digital certificate that is not signed by any higher authority; it is signed by its own private key, making it self-signed. It belongs to a root certificate authority (Root CA). The root certificate is distributed manually or through platform updates into the trust store of an operating system, browser, or other application. It serves as the trust anchor for the entire Public Key Infrastructure (PKI) hierarchy. Any certificate signed by a subordinate CA that chains back to a trusted root certificate will be accepted by the client as valid, provided all other checks pass.
When a client (browser or application) validates a server certificate during a TLS handshake, it builds a certification path from the leaf certificate up through intermediate CA certificates until it reaches a root certificate that is present in its local trust store. If the root certificate is marked as trusted, and each certificate in the chain is valid (unexpired, not revoked, properly signed by the next issuer), the client accepts the connection. Root certificates have long validity periods typically 20 to 30 years. Because they are self-signed, they carry no issuer constraints other than those placed by the trust store operator.
The security model of the web PKI depends on the safe storage and management of root certificate private keys. Compromise of a root CA's private key would allow an attacker to issue fraudulent certificates for any domain, undetectable by clients that trust that root. This is why root CAs use hardware security modules (HSMs) and strict offline procedures. Operating systems and browsers curate root store programs with baseline requirements, such as the Mozilla Root Store Policy and the CA/Browser Forum Baseline Requirements. A root certificate is the most sensitive element in the chain of trust; removal or distrust of a root certificate can break trust for thousands of downstream certificates.
Key facts
- Root certificates are self-signed and serve as trust anchors in a PKI hierarchy.
- They are distributed via operating system and browser trust stores, not over the network for dynamic acquisition.
- Private keys for root certificates are kept offline in HSMs to prevent compromise.
- Trust store operators like Mozilla, Apple, Google, and Microsoft maintain policies for root inclusion and removal.
- A root certificate typically has a lifespan of 20 to 30 years to remain stable as a trust anchor.
How it works in practice
Related terms
References
More in TLS & PKI
ACME Protocol
ACME (Automated Certificate Management Environment) is a protocol that automates the issuance, renewal, and revocation of TLS certificates, defined in RFC 8555.
Certificate Authority
A Certificate Authority (CA) is a trusted entity that issues digital certificates after verifying that the requester controls the domain or identity named in the certificate.
Certificate Chain
A certificate chain is an ordered list of certificates, starting with the server certificate and ending with a root CA, that a client validates to establish trust in the server's identity.
Certificate Pinning
A security technique where an application trusts only a specific, pre-selected certificate or public key for a given server, bypassing the standard chain of trust.
Cipher Suite
A cipher suite is a named set of cryptographic algorithms negotiated during a TLS handshake, specifying key exchange, authentication, encryption, and integrity protection for secure communications.
Domain Validation
Domain Validation (DV) is the lowest level of certificate validation used in TLS/SSL, where the certificate authority verifies only that the applicant controls the domain name, typically via an HTTP or DNS challenge.
ECH
Encrypted Client Hello (ECH) is a TLS extension that encrypts the Client Hello message, including the Server Name Indication (SNI), to prevent on-path observers from learning the target hostname during the handshake.
Extended Validation
Extended Validation (EV) is the highest level of TLS certificate assurance, requiring the certificate authority to perform rigorous, human-verified checks on the legal identity and operational existence of the requesting organization before issuance.
HSTS
HTTP Strict Transport Security (HSTS) is a web security policy mechanism that forces browsers to interact with a website only over HTTPS, preventing downgrade attacks and cookie hijacking.
Intermediate Certificate
An intermediate certificate is a subordinate CA certificate signed by a root CA, used to sign end-entity certificates and enable path validation while the root remains offline.