skip to content

What is a Cloudflare Origin CA certificate, how do you use one to run Full (strict), and when does it cause certificate errors?

level: middleimportance: should knowfreq 50%

answer

  1. trusted by one party only
  2. proxied records, never DNS-only
  3. private key shown once
  4. 200 SANs, one-level wildcards, no IPs

basics

~20 s

A Cloudflare Origin CA certificate is a free certificate that only Cloudflare trusts, which is enough for Full (strict). Browsers reject it, so visitors reaching the origin directly, through a DNS-only record or a paused zone, get certificate errors.

solid answer

~50 s

**Origin CA** is Cloudflare's own certificate authority for origin servers, available on every plan. You create a certificate on the **Origin Server** page: Cloudflare generates the key and CSR (RSA or ECC) or you paste your own CSR, you list the hostnames (apex and first-level wildcard are included by default, up to 200 SANs, no IP addresses), choose a validity period and a key format, and copy the private key at once because it is never shown again. Install it on the origin, add the Origin CA root if your server needs the chain, and set the mode to **Full (strict)**. Only Cloudflare trusts it: if the record goes DNS-only or Cloudflare is paused, browsers show `NET::ERR_CERT_AUTHORITY_INVALID`. Cloudflare sends no expiry notices, so track expiry yourself. Automation uses an API token with Zone SSL and Certificates Edit.

go deeper

for a junior

Recall that Origin CA certificates are free, trusted only by Cloudflare, and enough for Full (strict) when every visitor arrives through a proxied record.

for a middle

Explain the creation steps, the hostname rules (200 SANs, one-level wildcards, no IPs), the one-time private key and why DNS-only or a paused zone produces browser errors.

for a senior

Show operational care: an expiry inventory because Cloudflare sends no reminders, a rotate-then-revoke order, and API tokens rather than the deprecated Origin CA keys in automation.

for a principal

Weigh Origin CA against public certificates on origins: Origin CA ties the origin to Cloudflare being in front, which is fine for proxied-only services and wrong for anything clients reach directly.

## What an Origin CA certificate is A **Cloudflare Origin CA certificate** is a TLS certificate issued by Cloudflare's own certificate authority for use on your **origin server**, the machine Cloudflare fetches content from. It is free on Free, Pro, Business and Enterprise plans. Its defining property is **who trusts it**: Cloudflare's edge does, and browsers do not. That makes it exactly what the **Full (strict)** encryption mode needs, since Full (strict) accepts either a publicly trusted certificate or an Origin CA certificate, and nothing else about the origin leg has to be public. Cloudflare positions it for origins that **only receive traffic from proxied records**. As long as every visitor reaches the origin through Cloudflare, nobody but Cloudflare ever sees the certificate. ## Creating and installing one 1. On the zone's **Origin Server** page, open the **Origin Certificates** tab and select **Create Certificate**. 2. Choose **Generate private key and CSR with Cloudflare** (key type RSA or ECC) or **Use my private key and CSR** and paste a CSR you generated, which keeps the private key on your side. 3. List the hostnames. The zone apex and the first-level wildcard (`example.com` and `*.example.com`) are included by default. 4. Choose the **Certificate Validity** period and select **Create**. 5. Pick a **Key Format**: PEM (Base64 text) suits most web servers, binary DER works with many of the same servers, and PKCS#7 (a `.p7b` file) is for servers that require it. 6. Copy the certificate and the private key into separate files **before leaving the screen**. The private key cannot be displayed again. 7. Install both on the origin, enable TLS on port 443, and, where the server needs the chain, add the **Cloudflare Origin CA root** in its ECC or RSA version; at least one hosting control panel needs the RSA version. 8. Set the encryption mode to **Full (strict)**. ## Hostname coverage rules - Up to **200 Subject Alternative Names** per certificate. - A SAN is a fully qualified name such as `www.example.com` or a wildcard such as `*.example.com`. - **Wildcards cover one level only**, but several can sit on one certificate, so `*.example.com` and `*.secure.example.com` may coexist. - **IP addresses cannot be SANs.** ## When it causes errors | Situation | What visitors or tools see | |---|---| | Record switched to DNS-only, or Cloudflare paused | untrusted-certificate errors such as `NET::ERR_CERT_AUTHORITY_INVALID` | | Testing the origin directly with an SSL checker | certificate flagged as invalid, as expected | | Server needs the chain and it is missing | "the issuer of this certificate could not be found" | | Certificate expired under Full (strict) | Cloudflare 526 | The first row is the important one. An Origin CA certificate encrypts **only** the leg between Cloudflare and the origin. Anything that reaches the origin without Cloudflare in front, whether a grey-clouded record, a paused zone or a client calling the origin directly, meets a certificate it has no reason to trust. If some clients genuinely need to connect to the origin directly, install a publicly trusted certificate instead; Full (strict) accepts that too. ## Operating them - **Track expiry yourself.** Cloudflare does not send expiration notifications for Origin CA certificates, and long-lived ones are easy to forget. Put them in your certificate inventory or monitoring. - **Revoking is permanent.** If key material is lost, revoke the certificate, but switch the affected hostnames to Full first, or visitors meet 526 errors until a replacement is installed. - **Creation needs API Access.** A dashboard user without **API Access** on the account gets `Failed to validate requested hostname ... This zone is either not part of your account, or you do not have access to it`. - **Automate with an API token.** The Origin CA endpoints (list, create, get and revoke under `certificates`) take an API token with the **Zone - SSL and Certificates - Edit** permission. The older **Origin CA keys** (service keys, sent as `X-AUTH-USER-SERVICE-KEY`) are deprecated, with removal announced for 30 September 2026, so scripts that still use them need to move to a token. ## Where it fits Origin CA is the cheapest route from Flexible or Full to Full (strict): no public CA, no domain validation, and a certificate the origin can keep for as long as the validity you chose. It is not an edge certificate and does nothing for what browsers see; that is the job of the certificates Cloudflare presents at the edge.

  • Your partner calls the origin directly, bypassing Cloudflare. Can the origin keep an Origin CA certificate?
    Not for that partner. Only Cloudflare trusts Origin CA, so a direct client sees an untrusted certificate. Install a certificate from a publicly trusted CA instead; Full (strict) accepts it as well, so the Cloudflare leg keeps working and the partner gets a certificate it can validate.
  • How do you rotate an Origin CA certificate without visitor errors?
    Create the new certificate first, install it on every origin that served the old one, and confirm Cloudflare still serves the site under Full (strict). Only then revoke the old certificate. Revoking first, or letting it expire unnoticed, produces 526 errors, and Cloudflare sends no expiry reminder.

  • An Origin CA certificate also secures DNS-only records that visitors reach directly.
  • Origin CA certificates are publicly trusted, so SSL checkers grade them green.
  • Cloudflare emails you before an Origin CA certificate expires.
  • You can download an Origin CA private key again from the dashboard later.
  • A *.example.com Origin CA wildcard also covers a.b.example.com.

Assumes Cloudflare as of October 2026: Origin CA keys (service keys) are deprecated with removal announced for 30 September 2026, so Origin CA automation uses an API token with Zone SSL and Certificates Edit.