Overview#
Cloudflare Email Routing is a free, receive-only forwarding service built for domains that use Cloudflare as their authoritative DNS provider. It accepts incoming mail at your custom domain and forwards it to a verified destination address.
Because Cloudflare does not rewrite the Reply-To header or provide an outbound relay, hitting Reply in Gmail or Apple Mail exposes your real personal email address to the sender. It also requires you to own a custom domain and point its nameservers to Cloudflare.
AliasFleet works out of the box with 3 auto-provisioned personal subdomains on the free plan, or with custom domains at any DNS registrar on paid plans. It rewrites Reply-To headers for two-way alias replies, provides an in-app Quick Send web composer, and strips tracking pixels and link parameters before messages reach your inbox.
Feature comparison#
Here is how AliasFleet and Cloudflare Email Routing compare across mail routing, privacy controls, custom domains, and pricing.
Why look for a Cloudflare alternative#
Replying and sending from an alias#
Cloudflare Email Routing only handles incoming mail. When a message arrives in your inbox and you click Reply, your mail client addresses the response from your personal Gmail, Outlook, or Fastmail account.
AliasFleet rewrites the Reply-To header on every forwarded message with an encoded reply token. When you reply from your regular inbox, AliasFleet verifies your destination address, replaces the From header with your alias, signs the message with DKIM, and delivers it to the recipient.
On Pro and Business plans, you can also open the Quick Send web composer to send new outbound messages with attachments (up to 10 MB on Pro and 25 MB on Business) without configuring an external mail client.
# Cloudflare Email Routing (Replying exposes your real inbox)From: billing@vendor.example.comTo: store.49a@yourdomain.comReply-To: billing@vendor.example.com# AliasFleet (Replying routes back through the alias)From: "Vendor Billing [via AliasFleet]" <store.49a@yourdomain.com>To: you@personal-inbox.comReply-To: store.49a+billing=vendor.example.com@aliasfleet.comX-AliasFleet-Trackers-Stripped: 2X-AliasFleet-Links-Scrubbed: 4Nameserver freedom vs Cloudflare DNS lock-in#
To use Cloudflare Email Routing, you must delegate your domain nameservers to Cloudflare. If you manage DNS through AWS Route 53, Porkbun, Namecheap, or Hetzner DNS, moving your entire zone just to forward email adds unnecessary infrastructure coupling.
AliasFleet connects to any DNS provider using a standard MX record, an SPF TXT record, and a CNAME record for DKIM. It also includes an automated DNS diagnostics engine that checks MX, SPF, DKIM, and DMARC records in real time.
Tracker stripping, link scrubbing, and Email X-Ray#
Cloudflare forwards the raw MIME message body untouched unless you write and maintain your own JavaScript Email Worker. Marketing emails keep their 1x1 tracking pixels and tracking URL parameters intact.
On Pro and Business plans, AliasFleet strips 1x1 tracking pixels and scrubs tracking query parameters (such as utm_*, fbclid, and gclid) from hyperlinks before forwarding. It also includes Email X-Ray to inspect raw MIME headers, relay hops, and SPF/DKIM authentication verdicts.
Which one fits your setup#
Choose AliasFleet if#
- You need to reply to forwarded emails or compose outbound messages via Quick Send without revealing your personal email address.
- You want 3 free personal subdomains right away without purchasing a custom domain.
- You keep your domain DNS on Route 53, Porkbun, Namecheap, or another registrar outside Cloudflare.
- You want tracker pixel stripping, link parameter scrubbing, Email X-Ray forensics, and vendor leak alerts.
Choose Cloudflare if#
- Your domain already uses Cloudflare DNS and you only need basic, receive-only forwarding.
- You never reply from your aliases and prefer writing custom Cloudflare Email Workers in JavaScript.
Moving a custom domain from Cloudflare#
If you use your own domain on Cloudflare, you can move it to AliasFleet without losing mail. Set up the domain and your aliases in AliasFleet before you update the MX record at your DNS registrar.
Add your domain in AliasFleet
Open the Domains tab in AliasFleet, enter your domain name, and verify your destination inbox.
Recreate your aliases or enable catch-all
Add your existing custom addresses in AliasFleet or turn on catch-all routing so unregistered addresses still reach your inbox.
Add the AliasFleet DKIM and SPF records in Cloudflare DNS
Add the af._domainkey CNAME record and include:mail.aliasfleet.com in your SPF TXT record before disabling Cloudflare Email Routing.
Disable Cloudflare Email Routing and update MX
In the Cloudflare dashboard, unlock the Email Routing DNS records and replace the Cloudflare MX records with mail.aliasfleet.com (priority 10).
Standard DNS records for a root domain on AliasFleet:
; 1. Inbound Mail Routing (Apex or Subdomain)@ IN MX 10 mail.aliasfleet.com.; 2. Sender Policy Framework (SPF)@ IN TXT "v=spf1 include:mail.aliasfleet.com ~all"; 3. DomainKeys Identified Mail (DKIM CNAME Selector)af._domainkey IN CNAME dkim.aliasfleet.com.; 4. DMARC Policy (Recommended)_dmarc IN TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@aliasfleet.com"