You can turn on a catch-all in Cloudflare Email Routing in about ten seconds, and that is exactly why people get it wrong. The toggle sits at the bottom of the routing rules list, and it only catches addresses that no other rule matched. If a specific rule above it points at a destination that was never verified, the catch-all will not save that message. Order matters more than the toggle itself. Build and verify your custom address rules first, confirm they resolve correctly, and only then switch on the catch-all.
How Cloudflare Email Routing decides where a message goes
Cloudflare Email Routing forwards email for domains using Cloudflare DNS. Before you can create any rule, the domain has to be active on Cloudflare and its nameservers have to point to Cloudflare, because Email Routing works by taking over the MX records for the zone. Once you enable it, Cloudflare adds MX, SPF and DKIM records to the DNS zone automatically. You do not hand-edit those records unless something conflicts with an existing mail setup.
When a message arrives, Cloudflare evaluates the routing rules for that domain from top to bottom. Custom address rules match an exact local part, like billing@ or support@. The catch-all rule sits underneath everything and catches addresses not matched by other rules. That evaluation order is the whole game. A message to a custom address never reaches the catch-all, even if the custom rule cannot deliver it.
Each routing rule supports one destination address, and that destination must be a verified destination before the rule activates. Cloudflare sends a confirmation email to the destination, and until someone clicks the link inside it, the rule exists in a pending state. Routing rules per domain are limited to 200, and the maximum message size is 25 MiB. Anything larger is rejected before any rule is evaluated, so a catch-all cannot recover oversized mail either.
Building custom address rules before you touch the catch-all
Start in the Cloudflare dashboard under Email, then Email Routing, and open the Routing rules tab for the domain. Add your specific addresses one at a time: the ones that need to reach a real human or a specific mailbox. A custom rule for invoices@ pointing to your accounting inbox, a rule for dev@ pointing to a shared Gmail label, a rule for press@ pointing to an external PR address. Each of these is a deliberate route, and each one takes priority over the catch-all by virtue of sitting above it.
Keep the destination list short and intentional. Every destination address must be verified before rules activate, and verification is per address, not per domain. If you route ten custom addresses to three destinations, you only verify those three. Send each verification from the Destination addresses tab, open the confirmation email in the target mailbox, and click through. Gmail and Google Workspace destinations usually land in the inbox within a minute; Microsoft 365 and Outlook tenants sometimes route the confirmation to quarantine, so check the quarantine view if nothing shows up.
Test each custom rule before you go further. Send a message from an external account to each custom address and confirm it lands where you expect. This is the moment to catch a typo in a local part or a destination that was verified on a different account. A rule that looks correct in the dashboard can still point at the wrong mailbox, and the catch-all will not flag it for you.
Why an unverified custom rule blocks the catch-all from helping
Here is the failure mode that catches most people. You add a custom rule for sales@ pointing to a new contractor’s address, skip the verification step because you are in a hurry, and then enable the catch-all. Mail to sales@ now matches the custom rule first. Because the destination is unverified, the rule does not deliver, and the message is dropped rather than being passed down to the catch-all. The catch-all never sees it, because the custom rule already claimed the address.
The same logic applies to a custom rule you set to the drop action on purpose. Drop is a valid outcome when you want to silently discard mail to a specific address, but it is a deliberate choice, not a fallback. As noted on the AllMail blog, if you forget that a drop rule exists, you will spend an afternoon wondering why a particular address never reaches the catch-all. Check the rule list for custom addresses before you blame the catch-all for missing mail.
There is a second ordering trap worth knowing. Cloudflare Email Routing does not support sending or replying from the domain. Forwarded mail arrives in Gmail or Outlook, but if you hit reply, the message goes out from your personal address, not from the custom address it was sent to. That is a limitation of the forwarding model, not a bug in your rules. If you need outbound mail from the domain, you need a real mailbox provider or Cloudflare Email Service, which groups Email Routing and outbound sending under one product family.
Enabling the catch-all and choosing what it does with unmatched mail
With your custom rules verified and tested, open the catch-all section and enable it. The catch-all rule catches addresses not matched by other rules, which means anything sent to a local part you never defined. Point it at a verified destination, typically your main inbox or a dedicated catch-all mailbox you actually read. The destination has to be verified just like any custom rule destination, so confirm it before you flip the toggle.
Decide deliberately between forwarding and dropping. Forwarding to a real mailbox is the common choice for domains where people guess addresses, like firstname@ or info@. Dropping is reasonable when your domain attracts a lot of spam to random local parts and you do not want it polluting a mailbox. A drop action on the catch-all is clean and cheap, but it is silent: nobody will tell you a message was discarded, so use it only when you are sure you do not want wildcard delivery.
Watch the volume once the catch-all is live. A catch-all on a public domain collects everything sent to addresses that do not exist, and a meaningful share of that is spam, directory scraping and misdirected mail. If you forward all of it to Gmail, expect the spam folder to fill and the occasional legitimate message to get buried. Many people route the catch-all to a separate mailbox or a Gmail filter that labels it, so it stays out of the primary inbox. If you want to process it programmatically, a Cloudflare Worker can sit in front of the routing logic and classify or log messages before they reach a destination.
Limits, DNS interactions and a checklist for a clean setup
The 200 routing rules per domain limit sounds generous until you start creating a rule for every alias. If you are close to that ceiling, consolidate: route a group of related addresses to one destination, or lean on the catch-all for the long tail and keep custom rules only for addresses that need a different destination. Remember that each rule supports one destination, so a single address cannot fan out to two mailboxes through one rule. You need two rules for that, which counts against the limit twice.
The 25 MiB maximum message size is a hard ceiling. Attachments that push a message over it are rejected at the edge, and no rule, custom or catch-all, will deliver them. If your domain regularly receives large files, tell senders to use a file transfer link instead. Also keep an eye on DNS: Cloudflare adds MX, SPF and DKIM records when you enable Email Routing, and if you later switch to Google Workspace or Microsoft 365 for real mailboxes, those records have to be replaced. Leaving the Email Routing MX records in place while pointing a mailbox provider at the same domain creates a split where some mail forwards and some delivers locally.
Run this sequence every time you set up a domain. First, confirm the nameservers point to Cloudflare and Email Routing is enabled. Second, add every custom address rule you need and verify each destination before moving on. Third, send test messages to each custom address and confirm delivery. Fourth, enable the catch-all, point it at a verified destination, and send a test to a random address to confirm it lands. Fifth, review the rule list for anything set to drop and confirm you meant it. Sixth, check the destination mailboxes for spam filtering that might hide forwarded mail.
The catch-all is the last switch you flip, not the first. Get your custom address rules verified and tested, confirm nothing above the catch-all points at an unverified destination, then enable it and route unmatched mail somewhere you will actually see it. If you need replies to come from the domain itself, plan for a real mailbox or Cloudflare Email Service rather than relying on forwarding, and revisit your MX records the day you make that change so forwarded and hosted mail do not collide.
