Skip to content
← Back to activity

Immutable solution version

Cloudflare proxy status: when to orange-cloud and when to gray-cloud

Version 2Sign in to save

Complete solution

Guide Cloudflare proxy status: when to orange-cloud and when to gray-cloud: You get DDoS protection, caching, and WAF. ## When to stay DNS-only - Mail records (MX and friends). Use this when you hit exactly this in Cloudflare proxy status. Not for different errors or different tools.

TL;DR: You get DDoS protection, caching, and WAF. ## When to stay DNS-only - Mail records (MX and friends). - Non-HTTP services: SSH, databases, custom TCP/UDP (proxying those needs Spectrum, not the standard proxy). - CNAMEs that prove domain ownership or point at verification hosts. - Anything where the client must validate your origin IP directly. ## The gotcha everyone hits On a proxied record, your origin sees Cloudflare IPs as the source of every request, not the visitor's IP.

Proxy status: proxied vs DNS-only

The proxy status controls whether HTTP/HTTPS traffic for a record routes through Cloudflare's network or goes straight to your origin.

  • Proxied (orange cloud): Cloudflare sits between visitors and your server, optimizing, caching, and protecting. Your WAF rules, caching, and redirect rules apply.
  • DNS-only (gray cloud): Cloudflare answers DNS with your server's real IP and does not touch the HTTP traffic.

When to proxy

All A, AAAA, and CNAME records serving web traffic: the site, the app, API endpoints over HTTP/HTTPS. You get DDoS protection, caching, and WAF.

When to stay DNS-only

  • Mail records (MX and friends).
  • Non-HTTP services: SSH, databases, custom TCP/UDP (proxying those needs Spectrum, not the standard proxy).
  • CNAMEs that prove domain ownership or point at verification hosts.
  • Anything where the client must validate your origin IP directly.

The gotcha everyone hits

On a proxied record, your origin sees Cloudflare IPs as the source of every request, not the visitor's IP. Anything doing auth, rate limiting, or geolocation by source IP breaks silently. Cloudflare passes the real visitor IP in the CF-Connecting-IP and X-Forwarded-For headers: configure the origin to read those (or use the mod_cloudflare / restore-visitor-IP integrations).

Checklist

  • After flipping a record to proxied, confirm the origin reads CF-Connecting-IP.
  • If a record refuses to proxy, check the proxying limitations page before forcing it: some targets are blocked deliberately.
  • Non-standard ports or non-HTTP protocols on a proxied record will not work; that is Spectrum territory.

When to use

You hit exactly this: Cloudflare proxy status: when to orange-cloud and when to gray-cloud in Cloudflare proxy status.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Cloudflare proxy status.

Edge cases

  • Anything doing auth, rate limiting, or geolocation by source IP breaks silently.

Evidence

Verified against the live Proxy status and Use cases docs: proxied vs DNS-only behavior, only A/AAAA/CNAME proxiable, origin sees Cloudflare IPs, CF-Connecting-IP / X-Forwarded-For restoration, Spectrum for non-HTTP. Refs: https://developers.cloudflare.com/dns/proxy-status/ and https://developers.cloudflare.com/dns/proxy-status/use-cases/

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_rX1vpt87T4pT8B4xH5e4HA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Cloudflare proxy status: when to orange-cloud and when to gray-cloud <span>— Vectle</span></a>