Cloudflare Email Routing
- Free allowance
- Unlimited inbound email on Workers Free and Paid; 200 destination addresses, 200 rules per domain, 30 domains per zone
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- documented2 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | unlimited inbound email on Workers Free and Paid; 200 destination addresses, 200 rules per domain, 30 domains per zone unit unlimited; metered on request-count |
|---|---|
| Price | none stated |
| Limits |
counts of things, not rates, so no vocabulary kind names them: 200 destination addresses per account, shared across every domain; 200 routing rules per domain and 30 domains per zone |
| Binding | none nothing in the vocabulary binds the volume: inbound is unlimited and the 25 MiB message cap bounds a single message rather than a day. What actually caps the shape is the 200 destination addresses per account, which is a count and not one of the six kinds |
| Identity | email a Cloudflare account with the domain delegated to Cloudflare nameservers |
| Egress | not applicable: inbound only on the free plan |
| Per-object cap | 25 MiB inbound message; larger messages are rejected (26214400 bytes) |
| Retention | not applicable: messages are forwarded, not stored |
| Interface | rest MX records on the zone, with rules mapping a pattern to a destination or a Worker |
| Tooling | the Cloudflare dashboard, wrangler for Worker handlers |
| Composes with | Its scarce link is the 200 verified destinations at the account level. |
| Reliability | a routing rule maps one pattern to one destination; a fan-out to several destinations needs a Worker |
| Notes | Inbound is genuinely unmetered and is the one unlimited thing in this topic. The 200-destination cap is the quiet one. |
| Evidence note | documented no probe: the inbound path could not be exercised from this host. route1, route2 and route3.mx.cloudflare.net answered 550 on the sender's IPv6 reverse lookup, and TCP 25 was reset over IPv4, so no SMTP-level evidence was obtained either way |
| Parsed numbers |
|
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | developers.cloudflare.com/email-service/platform/pricing/ | 'Inbound emails (Email Routing) | Unlimited | Unlimited' across Workers Free and Paid, while outbound is 'Not available' on Workers Free |
| 2026-10-22 | developers.cloudflare.com/email-service/platform/limits/ | 200 routing rules per domain, 200 destination addresses per account, and a 25 MiB inbound message limit |
More fields 1
{
"stale_after_days": 90
}