When a message sent to your Cloudflare-hosted domain never lands in the destination inbox, the instinct is to start editing DNS records. That is usually the wrong first move. Before you touch an MX record or re-verify an address, open the Cloudflare dashboard and read the Email Routing activity log. It records each message Cloudflare saw and what it did with it: forwarded, dropped, or rejected. That single view tells you whether the problem is upstream (mail never reached Cloudflare, so DNS or MX is broken) or downstream (mail arrived but a rule, a verification state, or the destination mailbox failed). This checklist walks the diagnostic path in the order that resolves issues fastest.
Read the activity log before changing any record
The Email Routing activity log is the only place that answers the first and most important question: did the message reach Cloudflare at all? If a test email appears in the log with a forwarded status, your MX records and nameserver delegation are working, and the fault lies with the destination side. If the log shows the message as dropped or rejected, Cloudflare received it but a rule or policy stopped it. If the message never appears in the log, Cloudflare never saw it, which points squarely at DNS.
This distinction saves time because the two failure families have almost no overlap in fixes. A missing log entry means you investigate MX records, nameserver delegation, and whether the domain is actually active on Cloudflare. A present log entry with a failure status means you investigate routing rules, destination verification, message size, and the receiving mailbox. Treat the log status as the fork in the road and do not proceed until you know which branch you are on.
Pay attention to the timestamps and the specific status label. A “dropped” status often correlates with a catch-all rule set to drop, or a routing rule pointed at an unverified destination. A “rejected” status can reflect a message that exceeded the 25 MiB maximum message size or a sending domain that failed authentication. Read the detail for the individual message rather than scanning the summary, because the per-message status is where the actual cause lives.
If mail reached Cloudflare, check rules and destination verification
Once the log confirms delivery to Cloudflare, the next suspects are routing rules and destination addresses. Cloudflare Email Routing requires every destination address to be verified before rules that target it will activate. An unverified destination is one of the most common silent failures: the rule exists, the address looks correct in the dashboard, but mail is not forwarded because the verification link was never clicked. Confirm each destination shows a verified state, and re-send the verification email if it does not.
Each routing rule supports exactly one destination address, so a rule that appears to fan out to several people is actually several rules. If forwarding works for one recipient but not another, compare the individual rules rather than assuming a single rule covers both. Also check the catch-all rule: if it is enabled and set to drop, any address not matched by a more specific rule is discarded, and the log will show that drop. A catch-all set to catch unmatched addresses is useful, but only when you intend it to forward rather than drop.
Keep the routing rules per domain limit of 200 in mind if you run a large domain with many aliases. Hitting that ceiling means new rules silently fail to save or fail to apply, and mail for those addresses falls through to the catch-all or gets rejected. If you are near the limit, consolidate where possible or move high-volume aliases to a different handling strategy. Finally, remember that free email forwarding with Cloudflare does not support sending or replying from the domain. If the complaint is “replies do not arrive,” that is expected behavior, not a forwarding bug, and the fix is a separate outbound path such as Cloudflare Email Service.
If mail never reached Cloudflare, fix DNS and delegation first
A message that never appears in the activity log did not reach Cloudflare, which almost always means the MX records are wrong or the domain is not fully delegated. Cloudflare Email Routing requires nameservers pointing to Cloudflare, and it adds MX, SPF, and DKIM records automatically when you enable it. If those records were edited manually, overwritten by another provider, or never applied because the domain uses external nameservers, inbound mail routes elsewhere. Verify that the domain’s nameservers are Cloudflare’s and that the Email Routing MX records are present and unmodified.
The SPF record and DKIM selector matter for deliverability and authentication, but they do not control whether mail arrives at Cloudflare, so do not confuse an SPF problem with a routing failure. If the log is empty, focus on MX and delegation. If the log shows messages but the destination provider (Gmail, Google Workspace, Microsoft 365, Outlook) files them as spam or rejects them, the SPF and DKIM records are back in scope. A message that Cloudflare forwarded but Gmail quarantined will appear in the log as forwarded, which is your signal that the fault is at the receiving end, not in Cloudflare’s routing.
When testing, send from an external address rather than from the same domain, and allow a minute or two for the log to populate. A test sent from an account inside the same domain can behave differently and muddy the result. If you use Cloudflare Workers for custom email processing, confirm the Worker is bound to the correct route and is not intercepting or failing messages before the standard routing rules run. Worker email processing failures show up in the log as errors on the specific message, which is another reason the log is the correct starting point.
Work the checklist in order: read the log, branch on whether the message arrived, then verify the destination state or the DNS state accordingly. Most “not forwarding” reports resolve at the first step once you know whether Cloudflare saw the mail. Keep the activity log open in a tab during any DNS change, send a fresh test after each adjustment, and confirm the status flips to forwarded before you consider the issue closed. As your setup grows, Cloudflare Email Service groups Email Routing and outbound sending under one roof, which is worth planning for if you also need to reply from the domain. For a quick sanity check on a single alias, AllMail-style catch-all routing plus a verified destination covers most small-domain needs without touching individual rules.