An origin accepts any HTTPS request from Cloudflare's IP ranges that presents Cloudflare's global Authenticated Origin Pulls certificate; why does that not prove the request passed your zone, and what closes the gap?
answer
- shared by every customer
- network, not account
- your own client certificate
- same-account tunnel hostnames
basics
~20 sCloudflare's IP ranges and global AOP certificate are shared by all customers, so they prove only that a request crossed Cloudflare's network, not your zone's rules. Use zone-level or per-hostname AOP with your own certificate, or a Tunnel.
solid answer
~40 sBoth checks are shared. Cloudflare's published ranges are the egress pool for all customers, and the global AOP certificate is the same for every account, so a request relayed for a different zone, one whose record points at your IP, arrives with the same source address and the same client certificate, having passed that zone's settings instead of yours. To prove the request came through your configuration, upload your own client certificate as zone-level or per-hostname AOP and make the origin trust only the CA that issued it. A Cloudflare Tunnel is the other answer: its `<UUID>.cfargotunnel.com` hostname only proxies traffic for DNS records in the same account. Enterprise zones can add Dedicated CDN Egress IPs to narrow the allowlist to addresses reserved for them. Keep the IP allowlist underneath all of it.
go deeper
Recall that Cloudflare's IP ranges are shared by all customers, so an allowlist proves Cloudflare sent the request, not that your zone did.
Explain the difference between the global AOP certificate and an uploaded zone-level or per-hostname one, and why the origin must trust only your CA.
Show how you would audit an origin's trust store, AOP coverage per hostname and its direct reachability, and why the shared-range allowlist stays underneath.
Decide per origin between your own AOP certificate, a Tunnel and Enterprise dedicated egress addresses, and who owns the certificates and their expiry.
## What each check actually proves An origin behind Cloudflare usually stacks several checks. Each one proves something narrower than teams assume: | Check at the origin | What it proves | Shared with | |---|---|---| | Source address in Cloudflare's published ranges | The connection came from Cloudflare's network | Every Cloudflare customer's proxied traffic | | Global AOP certificate verified | The TLS client was Cloudflare | Every account that turns global AOP on | | Zone-level or per-hostname AOP certificate verified | The request came through your account's configuration | No one; the certificate is exclusive to you | | Tunnel hostname (`<UUID>.cfargotunnel.com`) | The request came through a DNS record in your account | No one; other accounts cannot route to it | The first two rows are the trap. Cloudflare documents its egress addresses as one large pool used by all customers, and it describes the global AOP certificate as not exclusive to your account: it guarantees only that a request is coming from the Cloudflare network. ## Why that matters to a defender Your WAF custom rules, managed rulesets and rate limiting rules live in **your zone**, and your Access applications are attached to **your hostnames**. A request is only filtered by them if it entered Cloudflare through one of those hostnames. A Cloudflare zone can point a proxied record at essentially any public address, so a request relayed for a zone that is not yours can arrive at your origin from the same ranges, carrying the same global certificate, having passed whatever that zone was configured to do, which may be nothing. An origin that accepts it has quietly made all of your edge rules optional. ## Closing the gap 1. **Upload your own client certificate.** Set up zone-level AOP (all proxied hostnames on the zone) or per-hostname AOP (specific hostnames, which take precedence), with a leaf certificate issued by a CA you control. Configure the origin to trust **only** that CA, and remove Cloudflare's shared origin-pull CA from its trust. 2. **Or serve the origin through a Cloudflare Tunnel.** The `cfargotunnel.com` hostname only proxies traffic for DNS records in the same Cloudflare account, so even someone who learns the tunnel's UUID cannot route traffic to it from another account. AOP has no effect on tunnel hostnames; the tunnel's connector credentials do the authenticating. 3. **On Enterprise, consider Dedicated CDN Egress IPs.** Cloudflare then connects to the origin from addresses reserved for your account, so the firewall can allow a short list instead of the shared pool. 4. **Keep the shared-range allowlist anyway.** It stops scanners from completing a TCP connection at all, which AOP cannot do: during the handshake the origin still presents its own server certificate before it asks for the client's. ## Choosing among the stronger options - **Zone-level AOP**: one certificate for every proxied hostname on the zone; the simplest step up from global. - **Per-hostname AOP**: a separate certificate per hostname, for example per customer on a SaaS zone; more certificates to rotate. - **Cloudflare Tunnel**: no inbound port at all, at the cost of running `cloudflared` beside every origin. - **Dedicated CDN Egress IPs**: Enterprise only, a network-layer narrowing that pairs with AOP rather than replacing it. ## Weaker layers, and where they fit - **A secret request header** added at the edge (a request header Transform Rule or a Worker) and checked at the origin is easy to deploy, and Cloudflare rates header validation only moderately secure: a secret that leaks into a log is a bypass until someone rotates it. - **A Host header check** at the origin, accepting only your hostnames, narrows what arrives, but Cloudflare features such as Origin Rules, load balancers and Workers can legitimately rewrite the Host header, so it is a filter, not proof. - **Validating the Access JWT** at the origin, where Cloudflare Access protects the hostname, is an application-layer check Cloudflare rates very secure, at the cost of code or software on the origin. ## Verifying the fix - Confirm the origin's trust store holds only your CA, not Cloudflare's shared origin-pull CA. - Confirm every proxied hostname is covered: zone-level for the zone, per-hostname where a different certificate is needed, and none left on global by accident. - Send a direct request to the origin's address from outside Cloudflare; it must fail before any HTTP response. - Set the AOP certificate expiration notifications, because an expired certificate that the origin requires becomes an outage.
- If global AOP proves only Cloudflare's network, is it worth enabling at all?Yes, as a step up from the IP allowlist alone: it needs no certificate management and stops plain direct HTTPS requests that do not come from Cloudflare. It does not prove the request passed your zone. Treat it as interim, and move to a zone-level or per-hostname certificate you control when the origin must enforce your edge rules.
- Why keep the IP allowlist once the origin requires your own AOP certificate?AOP acts inside the TLS handshake, so the origin still accepts TCP connections from anyone and still sends its own server certificate before asking for the client's. Scanners can fingerprint it and floods still reach the web server. The allowlist drops those connections before the handshake starts, so the two controls cover different layers.
- A source address in Cloudflare's ranges proves the request passed our WAF rules.
- Global AOP's certificate is issued per account, so it identifies our zone.
- Full (strict) proves to the origin that the caller is our Cloudflare zone.
- Anyone who learns a tunnel's UUID can route their own hostname to it.
- A secret header from a Transform Rule is as strong as mutual TLS.