Encryption & Secure Communication

Certificate Authority (CA)

About 5 min read

What Is a Certificate Authority

A Certificate Authority (CA) is an organization that issues and manages digital certificates. When a website communicates over HTTPS, the browser needs to verify whether the site is genuinely operated by its legitimate owner. The certificate issued by a CA provides the basis for this verification.

A CA confirms that the certificate applicant is the rightful administrator of the domain, then digitally signs a certificate binding the public key to the domain name. Browsers contain a built-in list of trusted CAs (root store) and only accept certificates signed by CAs in that list.

Certificate Types - DV, OV, and EV

Certificates issued by CAs are categorized by what is verified about the applicant. This section covers DV, OV, and EV (the CA/Browser Forum Baseline Requirements also define an IV category for verifying individuals).

DV (Domain Validation)
Verifies only domain control. Validation completes through DNS record configuration or email verification. This is the type Let's Encrypt provides for free.
OV (Organization Validation)
Verifies domain control plus the organization's existence. Requires review through business registration and phone verification.
EV (Extended Validation)
Verifies the organization's legal existence, physical location, and applicant authority. The organization name used to appear in the browser address bar, but Chrome 77 (September 2019) and Firefox 70 (October 2019) moved this indicator out of the address bar to the panel opened by clicking the lock icon.

Encryption strength does not differ between DV, OV, and EV. The difference lies in the level of verification of who manages the domain.

Chain of Trust

The CA system operates on a hierarchical structure called the chain of trust.

  1. Root CA: The CA at the top of the trust hierarchy. It self-signs its own certificate (root certificate). Root certificates are pre-installed in operating systems and browsers, functioning as the trust anchor without users being aware.
  2. Intermediate CA: A CA that received its certificate from the root CA. The CA/Browser Forum Baseline Requirements (Section 6.1.7) prohibit using private keys corresponding to root certificates to sign certificates, except in cases such as the root itself and certificates for subordinate CAs.
  3. Server Certificate: The certificate installed on a website, signed by an intermediate CA.

When a browser verifies a server certificate, it traces the chain from server certificate to intermediate CA certificate to root certificate. If it reaches a root certificate in the root store, the certificate is deemed trustworthy. If any link in the chain is broken, the browser displays a warning.

The same Baseline Requirements (Section 6.2.7) require the CA to protect its private key in a system or device validated as meeting at least FIPS 140-2 level 3, FIPS 140-3 level 3, or an equivalent standard.

Impact of Let's Encrypt

Let's Encrypt, which entered public beta on December 3, 2015 and left beta on April 12, 2016, is a CA that issues DV certificates for free and automatically.

  • Accelerated HTTPS adoption: The Let's Encrypt FAQ describes its mission as promoting the widespread adoption of HTTPS and says its services are free so that every website can deploy HTTPS.
  • Automation via ACME protocol: ACME (Automatic Certificate Management Environment) was standardized as RFC 8555 in March 2019 and defines how a CA and an applicant automate verification and certificate issuance. Certbot is one ACME client.
  • Short 90-day validity: According to the Let's Encrypt FAQ, its default certificates are valid for 90 days, and subscribers can opt in to short-lived certificates valid for six days. A 2015 Let's Encrypt blog post named two advantages of short lifetimes: limiting damage from key compromise and mis-issuance, and encouraging automation. The validity period of subscriber certificates is also being shortened in stages under the CA/Browser Forum Baseline Requirements: as of October 2026, certificates issued before 15 March 2026 last at most 398 days, those issued on or after 15 March 2026 at most 200 days, those issued on or after 15 March 2027 at most 100 days, and those issued on or after 15 March 2029 at most 47 days.

Let's Encrypt is run by the nonprofit Internet Security Research Group (ISRG), and the ISRG sponsors page shows logos of Mozilla, Google, Cisco, and others.

The DigiNotar Incident and Certificate Transparency

In 2011, an intrusion into the systems of the Dutch CA DigiNotar came to light, and a fraudulent certificate for google.com was found to have been issued. According to Google's August 2011 announcement, the certificate was used in attempted man-in-the-middle attacks on users primarily located in Iran. Google said it would disable the DigiNotar CA in Chrome, Mozilla announced updates revoking trust in the DigiNotar root, and Microsoft also took action. According to an announcement by its parent company VASCO Data Security on September 20, 2011, DigiNotar was declared bankrupt by a Dutch court.

Certificate Transparency (CT), a mechanism for making certificate issuance auditable through public logs, was published in June 2013 as RFC 6962 (Experimental) by engineers at Google.

  • CT Logs: RFC 6962 defines publicly auditable, append-only logs in which issued certificates are recorded. The CT project page states that domain owners and others can monitor the logs to see which CAs have issued which certificates, when, and for which domains.
  • SCT (Signed Certificate Timestamp): Evidence of CT log recording. Servers present SCTs during the TLS handshake, and browsers verify them. In February 2018, Google announced that publicly-trusted certificates issued after April 2018 must comply with the Chromium CT Policy to be trusted in Chrome.
  • Combined with HSTS: CT is a mechanism for finding misissued certificates and HSTS reduces downgrades to HTTP; they play different roles against man-in-the-middle attacks.

The CT project page describes CT as working together to detect maliciously or mistakenly issued certificates.

Common Misconceptions

A padlock icon in the browser means the site is safe
The padlock only indicates that communication is encrypted; it does not guarantee the site operator is trustworthy. Phishing sites can also obtain DV certificates and use HTTPS. Chrome's help page suggests checking the site name in the address bar to confirm that you are on the right site.
EV certificates provide stronger encryption than DV certificates
Encryption strength does not depend on certificate type. DV and EV use the same TLS protocol and cipher suites. The difference is in the rigor of applicant identity verification, not encryption level.
Share

Related Terms

Related Articles