Cloudflare zone
A Cloudflare zone is one domain and everything Cloudflare manages for it, its DNS records, certificate, filtering rules and hosting settings, all grouped under that domain name in your account.
Zone is Cloudflare’s word for a domain and all its settings, bundled together. Add a domain to a Cloudflare account and a zone is created for it. Inside that zone sit the DNS records that say where the website and the email live, the certificate that turns on HTTPS, the rules that filter traffic, the redirects that keep old links working, and the settings that govern how the site is served.
The word comes from DNS itself, where a zone is the set of records one authority is responsible for. Cloudflare kept the term. In practice, when I say I am setting up your Cloudflare zone, I mean I am adding your domain to a Cloudflare account in your name and configuring everything that hangs off it.
One domain is one zone. A business with several domains, say a .ca and a .com and a separate brand, has several zones in the same account, each with its own records and its own settings, all visible on one screen.
Why it matters to you
The zone is the thing you own. Not the hosting plan, not the vendor relationship, not a login on somebody’s server. If the zone for your domain is in an account in your name, then your address, your email routing, your certificate and your site’s front door are all yours, together, in one place.
The opposite is what I keep finding when I take on a new client: the domain registered in a vendor’s account, the DNS on the vendor’s nameservers, the site on the vendor’s shared server, and no way for the owner to see or move any of it. Setting up a zone in your own account is how that gets untangled. Everything that used to be scattered across a provider’s systems becomes one zone that you control.
How I set it up
Adding the zone is the first step of a cutover. I create it in a Cloudflare account belonging to the business, copy across every DNS record that matters so email and existing services keep working, and add the redirect map so that every old address on the previous site lands on its new page. Then the domain’s nameservers are pointed at Cloudflare and the zone goes live.
From that point the zone is where everything for that domain happens. When the site needs a new subdomain, it is a record in the zone. When the email provider changes, it is a record in the zone. When a security rule needs adjusting, it is a setting in the zone. There is one place to look, and it is yours.
What it looks like in practice
Log in to Cloudflare and the zone is the first thing you see: your domain name, a traffic graph, and a row of tabs for DNS, security, rules and so on. You do not need to touch any of it. It exists so that you can, and so that whoever comes after me can.
On a build it is one line in the kickoff week, next to setting up Google Workspace and the redirect map. That is about the right weight for it. It takes an afternoon to do properly, and once it is done, it is the foundation everything else on the domain stands on.
Questions I get about this
- Is a zone the same as my domain?
- Close. Your domain is the name. The zone is that name as it appears in Cloudflare, with all its records and settings attached. One domain, one zone. If you have three domains, you have three zones in the same account.
- Do I need to do anything with the zone myself?
- No. I set it up and manage it. It is in your account so that you own it and can hand it to someone else if you ever need to, not because you need to log in and adjust things.
- Does the zone include my email?
- It includes the DNS records that tell the world where your email is delivered, and the routing that gets contact-form enquiries to your inbox. Your actual mailbox lives with Google Workspace or Microsoft 365. The zone points at it.
Want this set up properly for your business?
This is the kind of thing I build every week. Grab a time and we will talk through what fits.