With Cloudflare's Automatic SSL/TLS setting, how does Cloudflare choose and change a zone's encryption mode, and what will it never do?
answer
- a probe, not a guess
- HTTP and HTTPS content compared
- 1% first, then 10% steps
- never a weaker mode
basics
~20 sAutomatic 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.
solid answer
~50 s**Automatic SSL/TLS** is now the default encryption-mode setting, beside **Custom SSL/TLS**, where you pick the mode yourself. It reuses the probes built for the deprecated SSL/TLS Recommender: a crawler with the `Cloudflare-SSLDetector` user agent fetches the site over HTTP and HTTPS, compares the content, checks for `5XX` errors and the origin's certificate, and picks the most secure mode that works. Upgrades start on 1% of traffic and grow in 10% steps; an origin failure aborts and rolls back at once. Scans run about monthly and stop once the zone reaches its most secure mode, such as Full (strict), or is switched to Custom. It never moves a zone to a weaker mode, so an expired certificate under Full (strict) means 526 errors, not a silent downgrade. Opt a zone out by setting `ssl_automatic_mode` to `custom`.
code
bash · 5 linescurl --request PATCH \
"https://api.cloudflare.com/client/v4/zones/$ZONE_ID/settings/ssl_automatic_mode" \
--header "Authorization: Bearer $CF_API_TOKEN" \
--header "Content-Type: application/json" \
--data '{"value":"custom"}'go deeper
Recall that Automatic SSL/TLS is the default, that it picks the most secure working mode for you, and that Custom SSL/TLS is where you choose a mode by hand.
Explain the probe (HTTP and HTTPS fetches, content similarity, 5XX checks), the 1% then 10% ramp with rollback, and that it never downgrades.
Show what the feature does not cover: an expired origin certificate still causes 526s, a blocked detector freezes the zone, and owners outside the Super Admin digest may be surprised by an upgrade.
Decide where automatic upgrades fit a fleet: accept them for most zones, opt out the ones managed as code, and make origin certificate expiry someone's monitored responsibility either way.
## Automatic versus Custom A zone's **SSL/TLS encryption mode** decides how Cloudflare connects to the origin: plain HTTP (Off, Flexible), unverified HTTPS (Full) or verified HTTPS (Full (strict), and Strict (SSL-Only Origin Pull) on Enterprise). Cloudflare now offers two ways to set it: - **Automatic SSL/TLS (default)**: Cloudflare probes the origin and applies the most secure mode it can prove works. - **Custom SSL/TLS**: you pick the mode, the way the setting always worked. Cloudflare is rolling Automatic SSL/TLS out gradually, so a zone that has not been migrated yet shows only the Custom options. ## How the probe decides Automatic SSL/TLS reuses the methods built for the **SSL/TLS Recommender**, the older feature that only emailed a suggestion and is now deprecated in its favour. 1. A crawler with the user agent **`Cloudflare-SSLDetector`**, which Cloudflare treats as a trusted bot, fetches pages from the origin over **both HTTP and HTTPS**. It ignores `robots.txt` except for rules that target it specifically. 2. It runs a **content similarity** comparison: if the HTTPS version serves the same site as the HTTP version, HTTPS to the origin is safe to use. 3. It checks for **`5XX` errors** such as `502` or `503` and evaluates the origin's certificate and capabilities, which separates Full from Full (strict). 4. If a more secure mode than the current one fits, it schedules an upgrade. ## How an upgrade rolls out - The new mode starts on **1% of the zone's traffic**. - If no issues appear, it grows in **10% increments** until 100% of traffic uses it. - If origin connectivity fails along the way, Cloudflare **aborts, immediately rolls traffic back** to the previous mode and logs the failure. - Only after 100% of traffic has run with no TLS-related errors is the zone's setting permanently updated. - A **Flexible to Full or Full (strict)** move may ramp more slowly, because changing the origin scheme from HTTP to HTTPS changes cache keys and the cache needs time to warm. ## What it will never do **Automatic SSL/TLS never changes a zone to a less secure mode.** If the origin certificate expires on a zone already on Full (strict), the zone stays on Full (strict) and visitors get Cloudflare 526 errors until the certificate is fixed. Keeping the origin's TLS valid stays your job; the feature only ratchets upward. ## What the probe needs from your origin Automatic SSL/TLS can only upgrade a zone it can prove is ready, so a zone stuck on a weak mode usually points at the origin: - **The same site on both schemes.** If the origin serves a different page over HTTPS than over HTTP, for example a hosting provider's default page because no virtual host is configured for the name on port 443, the content comparison fails and the zone stays where it is. - **No server errors over HTTPS.** `5XX` responses on the HTTPS side block the upgrade. - **A certificate Full (strict) would accept** if you want that mode rather than Full: unexpired, issued by a publicly trusted CA or Cloudflare Origin CA, with a name matching the hostname. Fixing those three on the origin is how you let the feature do its job, rather than flipping the mode by hand. ## Scans, notices and opting out | Item | Behaviour | |---|---| | Scan frequency | about once a month, sometimes more often after configuration changes | | Scans stop | when the zone already uses its most secure mode, such as Full (strict), or you switch to Custom SSL/TLS | | Who is told | weekly digest emails listing upgraded zones, sent to Super Admins | | Opting one zone out | `PATCH` the zone setting `ssl_automatic_mode` with the value `custom` | | Opting many zones out | loop that `PATCH` over a list of zone IDs with an API token holding Zone Read and Zone Settings Read and Edit | A few practical consequences follow: - **Do not block the detector.** A security rule that challenges or blocks `Cloudflare-SSLDetector`, or a `robots.txt` rule aimed at it, stops the probe from seeing the origin, and the zone stays where it is. - **Expect your zone to change under you.** A zone you left on Flexible may move to Full or Full (strict) once the origin starts serving a valid certificate. The digest goes to Super Admins only, so other owners can be surprised. - **Switch to Custom when you need control.** Teams that manage the mode as code, or that keep a deliberately unusual setup, opt the zone out so the setting stays what their configuration says.
- Why would a team opt a zone out of Automatic SSL/TLS?Because the mode then changes only when someone changes it. A team that manages zone settings as code, or runs an origin whose HTTP and HTTPS content legitimately differ, wants the setting to match its configuration. Opting out with `ssl_automatic_mode` set to `custom` keeps the chosen mode and stops the monthly scans.
- How does Automatic SSL/TLS differ from the SSL/TLS Recommender it replaced?The Recommender, now deprecated, only scanned and emailed a recommendation, tagging the suggested mode on the SSL/TLS page; a person still had to apply it. Automatic SSL/TLS uses the same probes but applies the upgrade itself, gradually from 1% of traffic, and rolls back if origin connections fail.
- Automatic SSL/TLS drops a zone to Full when its origin certificate expires.
- Automatic SSL/TLS switches all of a zone's traffic to the new mode at once.
- A blanket Disallow: / for all user agents stops the detector's scans.
- The SSL/TLS Recommender is the current way to get mode suggestions.
- Automatic SSL/TLS judges the mode from the origin certificate alone.
Assumes Cloudflare as of October 2026: Automatic SSL/TLS is the default encryption-mode setting, still rolling out to zones, and has replaced the deprecated SSL/TLS Recommender.