skip to content

SSL/TLS Settings

Cloudflare terminates TLS at its edge and opens a second connection to the origin, so two certificates and a mode decide what is protected. Interviewers probe the gaps.

on this pageshow

explore

questions

11

On a full Cloudflare setup, which hostnames does the Universal SSL certificate cover, and why does api.eu.example.com fail with a certificate error?

level: juniorimportance: must knowfreq 48%

answer

  1. one level below the apex
  2. only proxied records get it
  3. partial setups behave differently
  4. Total TLS, advanced or custom

basics

~20 s

On a full setup, Universal SSL covers the apex (example.com) and first-level subdomains (www.example.com), presented only for proxied records. api.eu.example.com is two levels deep, so it needs Total TLS, an advanced certificate or a custom certificate.

solid answer

~40 s

Universal SSL is the free Domain Validated certificate Cloudflare issues and renews on every plan once a zone is active. On a full setup it covers `example.com` and one level of subdomain such as `www.example.com` or `api.example.com`, and Cloudflare presents it only for records set to **Proxied**; a DNS-only record is answered by the origin's own TLS. `api.eu.example.com` is a second-level subdomain, so visitors get a handshake failure such as `ERR_SSL_VERSION_OR_CIPHER_MISMATCH`, and the dashboard flags the record as not covered by a certificate. The fixes are the Advanced Certificate Manager add-on with Total TLS or an advanced certificate naming that host, or an uploaded custom certificate with it as a SAN. On a partial (CNAME) setup the rule differs: each proxied hostname gets its own Universal certificate whatever its depth.

go deeper

for a junior

Recall the coverage rule: on a full setup, the apex and one level of subdomain, and only for proxied records. Name one way to cover a deeper hostname.

for a middle

Explain how coverage differs between full and partial setups, and compare the three ways to cover a deep name: Total TLS, an advanced certificate, an uploaded custom certificate.

for a senior

Diagnose a cipher-mismatch error methodically: certificate still pending, record DNS only, expired custom certificate, or a hostname deeper than Universal SSL covers, and check each against the Edge Certificates page.

for a principal

Weigh renaming services to first-level hostnames against paying for Advanced Certificate Manager, and set a naming convention so new services do not quietly land outside certificate coverage.

## What Universal SSL is **Universal SSL** is the edge certificate Cloudflare issues, deploys and renews for free on every plan. An *edge certificate* is the certificate Cloudflare presents to visitors on the visitor-to-Cloudflare leg of a connection. Universal certificates are **Domain Validated (DV)**: the certificate authority (CA) checks control of the domain, not the identity of the organisation. Cloudflare chooses the CA and the validity period, and it can change the CA without notice. Universal certificates are valid for 90 days, and renewal starts 30 days before expiry. On a **full setup** (Cloudflare runs the zone's authoritative nameservers), the certificate normally arrives within 15 minutes to 24 hours of the zone becoming active. It is provisioned even while records are DNS only, but Cloudflare only *presents* it for hostnames whose records are set to **Proxied**. A DNS-only record sends visitors straight to the origin, so the origin's own certificate answers. ## What it covers on a full setup Coverage is the apex plus exactly one level of subdomain: | Hostname | Covered by Universal SSL? | |---|---| | `example.com` | Yes | | `www.example.com` | Yes | | `api.example.com` | Yes | | `api.eu.example.com` | No | | `test.dev.api.example.com` | No | The same one-level rule applies to a wildcard name on an advanced certificate: `*.example.com` matches `eu.example.com` but not `api.eu.example.com`. ## Why api.eu.example.com fails - The name is a **second-level subdomain**, outside Universal SSL's coverage, so no certificate that matches it is deployed at the edge. - Visitors get a handshake failure such as `ERR_SSL_VERSION_OR_CIPHER_MISMATCH`: there is no matching certificate to negotiate with. - The dashboard shows the warning `This hostname is not covered by a certificate` on such proxied DNS records. - The same browser error also appears while a new certificate is still being issued after activation, when the record is DNS only, or when an uploaded custom certificate has expired, so rule those out too. ## How to cover deeper names 1. **Total TLS**: buy the Advanced Certificate Manager add-on and turn on Total TLS. Cloudflare then issues an individual certificate for each proxied hostname Universal SSL misses. Full setups only. 2. **An advanced certificate**: with the same add-on, order a certificate that lists `api.eu.example.com` (or `*.eu.example.com`) among up to 50 hosts, with the CA and validity you choose. 3. **A custom certificate**: on Business or Enterprise, upload a certificate you obtained elsewhere that carries the name as a Subject Alternative Name, and renew it yourself. 4. **A flatter name**: move the service to a first-level name such as `api-eu.example.com`, which Universal SSL already covers. Upgrading the plan alone does not change Universal SSL's depth: coverage is the same on Free and on Enterprise. ## Checking what is actually deployed The **Edge Certificates** page lists every certificate on the zone with its **Type** (Universal, Advanced, Advanced - Total TLS, Custom) and **Status**, and the certificate packs API returns the same list. When a hostname fails, the checks run in a fixed order: 1. Is a certificate of type Universal (or a replacement) in status **Active**? 2. Is the hostname's DNS record **Proxied**? 3. If a custom certificate covers it, has it expired? 4. Is the hostname deeper than the apex plus one level? On a full setup, domain control validation for Universal SSL happens automatically, because Cloudflare runs the zone's DNS and can place the validation record itself. ## Edges worth knowing - **Partial (CNAME) setup**: when another provider runs authoritative DNS, each proxied hostname gets its own Universal certificate whatever its depth, but each new name must be proxied and validated as it is added. - **Load balancing hostnames** are not covered by Universal SSL by default. - **Spectrum** applications cannot use Universal SSL; they need an advanced or a custom certificate. - **Key types**: Free zones get an ECDSA certificate only; Pro, Business and Enterprise get RSA and ECDSA. Upgrading does not reissue at once: the RSA certificate arrives at the next renewal. - **Backup certificates**: on a full setup Cloudflare also issues a backup Universal certificate from a different CA with a different key, deployed only after a revocation or key compromise. - **Before a migration**: Universal SSL issues only after the zone is active. A live site that cannot go uncovered orders an advanced certificate or uploads a custom one first, or keeps its records DNS only until the Universal certificate shows **Active**.

  • Why might www.example.com have no edge certificate right after the nameservers move to Cloudflare?
    Universal SSL is issued only after the zone becomes active, usually within 15 minutes to 24 hours. A live site that cannot go uncovered should order an advanced certificate or upload a custom one before proxying, or keep its records DNS only until the Universal certificate shows Active on the Edge Certificates page.
  • Does upgrading a Free zone to Pro add an RSA certificate to Universal SSL straight away?
    No. Free zones get an ECDSA certificate only, and after an upgrade the existing ECDSA-only pack keeps serving until it renews; at that renewal Cloudflare issues both RSA and ECDSA. A team that needs RSA sooner orders an advanced certificate, which needs the Advanced Certificate Manager add-on.
  • What happens to api.eu.example.com if the zone's HSTS setting has includeSubDomains turned on?
    Browsers that received the header from the apex insist on HTTPS for every subdomain, at any depth, and do not let users click past certificate errors. An uncovered deep hostname then becomes unreachable instead of merely showing a warning, so cover it with Total TLS, an advanced or a custom certificate before turning includeSubDomains on.

On a full setup, Universal SSL is like a building pass printed for the lobby and every first-floor office: it opens any door one level in, but a room on the second floor needs a pass issued separately, through Total TLS, an advanced certificate or a custom one.

  • Universal SSL covers every subdomain at any depth on a full setup.
  • A DNS-only record still gets Cloudflare's Universal certificate presented to visitors.
  • Universal SSL lets the team pick which certificate authority issues it.
  • Upgrading the zone to Pro makes Universal SSL cover multi-level subdomains.
  • A partial (CNAME) setup is limited to first-level subdomains, exactly like a full setup.
open as a page

In Cloudflare, how do the SSL/TLS encryption modes Off, Flexible, Full and Full (strict) differ on the connection from Cloudflare to your origin?

level: juniorimportance: must knowfreq 75%

basics

~20 s

The encryption mode sets how Cloudflare reaches the origin: Off and Flexible use plain HTTP, Full uses HTTPS for HTTPS visitors without checking the origin certificate, and Full (strict) also validates it. Off also downgrades visitors to HTTP.

open as a page

A Cloudflare zone set to Flexible fronts an origin that redirects HTTP to HTTPS, and browsers now show ERR_TOO_MANY_REDIRECTS; why, and what is the right fix?

level: seniorimportance: must knowfreq 65%

basics

~20 s

Flexible always fetches the origin over HTTP, so the origin's HTTPS redirect fires even for visitors already on HTTPS, and the browser loops. Install an origin certificate, switch to Full (strict), and redirect HTTP visitors at the edge with Always Use HTTPS.

open as a page

When Cloudflare's Universal SSL is not enough, how do Total TLS, an advanced certificate and an uploaded custom certificate differ?

level: middleimportance: should knowfreq 35%

basics

~20 s

Total TLS auto-issues a certificate for each proxied hostname Universal SSL misses; an advanced certificate lists up to 50 hosts with your chosen CA, validation method and validity; a custom certificate is your own upload, which you renew yourself.

open as a page

When you enable HSTS on Cloudflare's Edge Certificates page, what do its settings control, and which later changes lock visitors out?

level: middleimportance: should knowfreq 38%

basics

~20 s

Cloudflare's HSTS setting sends Strict-Transport-Security on the zone's HTTPS responses, with a Max Age Header of 1 to 12 months and optional includeSubDomains, Preload and No-Sniff. Afterwards, anything that breaks HTTPS, such as DNS-only records or pausing Cloudflare, locks returning browsers out.

open as a page

In Cloudflare for SaaS, how does a customer's own domain such as shop.customer.com reach your fallback origin with a valid edge certificate?

level: middleimportance: should knowfreq 30%

basics

~20 s

You designate a proxied record as the fallback origin, create a custom hostname for shop.customer.com, and the customer CNAMEs it to your target. Cloudflare validates hostname ownership (status) and gets the certificate through DCV (ssl.status); both must read active.

open as a page

With Cloudflare's Automatic SSL/TLS setting, how does Cloudflare choose and change a zone's encryption mode, and what will it never do?

level: middleimportance: should knowfreq 35%

basics

~20 s

Automatic SSL/TLS, the default, probes the origin over HTTP and HTTPS and moves the zone to the most secure working mode, ramping from 1% of traffic and rolling back on errors. It never downgrades, even after a certificate expires.

open as a page

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%

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.

open as a page

A company adds CAA records on its Cloudflare DNS zone allowing one certificate authority; which edge certificates keep issuing, which can fail, and why?

level: seniorimportance: should knowfreq 26%

basics

~20 s

Universal SSL keeps renewing because Cloudflare silently adds CAA records for its own CAs once a zone has any. Advanced and Total TLS certificates get no such records, so an order from a CA the CAA omits fails, as can custom certificates.

open as a page

A Cloudflare zone runs Full because its origin presents a self-signed certificate; what does that leave exposed, and how do you reach Full (strict) without 526 errors?

level: seniorimportance: should knowfreq 45%

basics

~20 s

Full encrypts the origin leg but accepts any certificate, so anyone able to intercept it can impersonate the origin. Give every hostname a valid Origin CA or public certificate, test each origin, flip one hostname with a Configuration Rule, then the zone.

open as a page

In Cloudflare for SaaS, a customer pointed a live shop domain's CNAME at your target and visitors saw TLS errors for minutes; why, and how do you avoid it next time?

level: seniorimportance: nice to knowfreq 22%

basics

~20 s

The custom hostname used automatic HTTP DCV, which can only finish after the CNAME points at Cloudflare, so the name had no certificate until the CA validated it. Pre-validate the hostname and issue the certificate by TXT or Delegated DCV before the cutover.

open as a page