Email Routing has grown since leaving beta into one of Cloudflare's most widely used products, serving more than a million customer zones and forwarding roughly 20 million messages a day to every major email platform. Alongside Router to Workers, Public APIs, Audit Logs and DMARC Management, the team has spent the past two years extending the email security extensions and protocols the service speaks, and keeping its email egress IP reputation clean so deliverability to upstream providers stays high. Three new capabilities build on that foundation.
Preserving authentication across hops with ARC
SMTP dates to the early 1980s and was not designed around today's security expectations. Email Routing already covers SPF, DKIM signatures, DMARC policy enforcement, TLS transport, STARTTLS and IPv6 egress. The first of the two new standards is Authenticated Received Chain (ARC), which lets an intermediary such as Email Routing preserve the results of sender authentication checks. Validation results for SPF and DKIM are carried to the upstream provider inside the forwarded message, and the chain of trust records every hop, so tampering at any point can be traced. Rollout began a few weeks ago.
In the flow below, [email protected] writes to [email protected], an Email Routing address that forwards to [email protected].

Email Routing checks the SPF and DKIM alignments against @example.com's DMARC policy and records the outcome in an Arc-Authentication-Results header:
ARC-Authentication-Results: i=1; mx.cloudflare.net; dkim=pass header.d=cloudflare.com header.s=example09082023 header.b=IRdayjbb; dmarc=pass header.from=example.com policy.dmarc=reject; spf=none (mx.cloudflare.net: no SPF records found for [email protected]) smtp.helo=smtp.example.com; spf=pass (mx.cloudflare.net: domain of [email protected] designates 2a00:1440:4824:20::32e as permitted sender) [email protected]; arc=none smtp.remote-ip=2a00:1440:4824:20::32e
It then snapshots the original headers and body and produces an Arc-Message-Signature with a DKIM-like cryptographic signature — ARC reuses the same DKIM keys:
ARC-Message-Signature: i=1; a=rsa-sha256; s=2022; d=email.cloudflare.net; c=relaxed/relaxed; h=To:Date:Subject:From:reply-to:cc:resent-date:resent-from:resent-to :resent-cc:in-reply-to:references:list-id:list-help:list-unsubscribe :list-subscribe:list-post:list-owner:list-archive; t=1697709687; bh=sN/+...aNbf==;
Before forwarding to [email protected], a final Arc-Seal header, another DKIM-like signature built from the authentication results and message signature, cryptographically seals the message:
ARC-Seal: i=1; a=rsa-sha256; s=2022; d=email.cloudflare.net; cv=none; b=Lx35lY6..t4g==;
On receipt, Gmail authenticates the last hop — the domain.example domain, rewritten via SRS — and also verifies the ARC seal, which carries the original sender's authentication results. The result is greater traceability through intermediaries, better-informed delivery decisions for receivers, and higher deliverability for transporters like Email Routing. ARC is used by all major providers, including Gmail and Microsoft; the specification is RFC8617.
Closing the STARTTLS downgrade gap with MTA-STS
Early email travelled in the clear. Towards the late 1990s the community standardized STARTTLS, or Opportunistic TLS, via RFC3207, letting an SMTP client upgrade the session to TLS. Because that session begins in plain text it can be hijacked, leaving the protocol open to man-in-the-middle attacks. MTA Strict Transport Security (MTA-STS), introduced a few years ago by providers including Microsoft, Google and Yahoo, defends against downgrade and MITM attacks in SMTP sessions.
Enabling MTA-STS for a zone that uses Email Routing takes a few steps. In the Cloudflare dashboard, under DNS > Records, create a CNAME named _mta-sts pointing to Cloudflare's _mta-sts.mx.cloudflare.net, with the proxy disabled.

Confirm the record exists:
$ dig txt _mta-sts.example.com
_mta-sts.example.com. 300 IN CNAME _mta-sts.mx.cloudflare.net.
_mta-sts.mx.cloudflare.net. 300 IN TXT "v=STSv1; id=20230615T153000;"
That record tells connecting clients the domain supports MTA-STS. Next, an HTTPS endpoint at mta-sts.example.com must serve the policy file listing the domain's MTA-STS mail servers. HTTPS is used rather than DNS because not everyone has DNSSEC yet, and another MITM vector is undesirable. A minimal Worker does the job, pulling Cloudflare's Email Routing policy file for clients under the "well-known" URI convention. In Account > Workers & Pages, choose Create Application and select the "MTA-STS" template.

The Worker proxies https://mta-sts.mx.cloudflare.net/.well-known/mta-sts.txt to your own domain. After deploying, open the Worker configuration, go to Triggers > Custom Domains and choose Add Custom Domain.

Verify the policy file:
$ curl https://mta-sts.example.com/.well-known/mta-sts.txt
version: STSv1
mode: enforce
mx: *.mx.cloudflare.net
max_age: 86400
The policy enforces MTA-STS: capable clients will only deliver to the listed MX servers over a secure connection, and mail is not delivered if no secure connection can be made. Email Routing also supports MTA-STS upstream, raising security when forwarding to providers such as Gmail, Microsoft and others. Configuration is manual today; automatic setup from the Email Routing dashboard is planned.
New Email Workers APIs
Email Workers, announced last year, let any Email Routing user attach a Worker script to an address rule and process incoming mail programmatically on Workers, complete with databases and storage. That enabled allow/block lists, advanced rules, messaging-app notifications, honeypot aggregators and more — but only in response to an incoming message. Bodies could not be rewritten and new messages could not be created.
Sending mail from any Worker
Workers can now send email from scratch, at any time and not only on an incoming event, to any address verified under the account in Email Routing. Typical uses include daily digests, adverse-weather alerts, task-completion notifications, and messages built from contact-form input. Start by adding a send_email binding to wrangler.toml:
send_email = [
{type = "send_email", name = "EMAIL_OUT"}
]
Composing and sending in the Worker is then straightforward:
import { EmailMessage } from "cloudflare:email";
import { createMimeMessage } from "mimetext";
export default {
async fetch(request, env) {
const msg = createMimeMessage();
msg.setSender({ name: "Workers AI story", addr: "[email protected]" });
msg.setRecipient("[email protected]");
msg.setSubject("An email generated in a worker");
msg.addMessage({
contentType: 'text/plain',
data: `Congratulations, you just sent an email from a worker.`
});
var message = new EmailMessage(
"[email protected]",
"[email protected]",
msg.asRaw()
);
try {
await env.EMAIL_OUT.send(message);
} catch (e) {
return new Response(e.message);
}
return new Response("email sent!");
},
};
The example uses mimetext, an open-source raw email message generator. For security, delivery is restricted to addresses whose ownership you have confirmed in Email Routing; campaigns or newsletters to addresses you don't control should go through other options such as the MailChannels integration. Because sending is not tied to the EmailEvent, it works from any Worker type, including Cron Triggers and Durable Objects.
Replying to incoming mail
Programmatic replies have been among the most-requested features. Until now Email Workers could only return a permanent SMTP error, which may or may not reach the end user depending on the client. The new reply API makes true auto-responders possible — a support address that opens a ticket and returns its link, an out-of-office message, or an explanation of a rejection — with body content under your control:
export default {
async email(message, env, ctx) {
message.setReject("Address not allowed");
}
}

Replies are constrained to limit abuse: the incoming email must have valid DMARC, a message can be replied to only once, the In-Reply-To header must match the incoming Message-ID, the reply recipient must be the incoming sender, and the outgoing sender domain must be the same domain that received the mail. If these or other internal conditions fail, reply() raises an exception; otherwise the composed reply goes back to the original sender. Full details are in the Developer Docs.
Subdomain support
Email Routing has operated at the zone level, limited to the zone's top-level domain. A zone such as example.com can host subdomains like mail.example.com or corp.example.com through DNS, but Email Routing could only be attached to the apex, example.com in this example. That constraint covers most deployments, but larger organizations with complex email requirements have asked for more flexibility.
Email Routing can now be used with any subdomain of any zone in an account. The dashboard experience was redesigned around a single place to manage all Email Routing domains and subdomains, rules and destination addresses.
To enable Email Routing on a new subdomain, open the Cloudflare dashboard, select the account and zone, then go to Email > Email Routing > Settings and click "Add subdomain".

After the subdomain is added and its DNS records are configured, it appears in the Settings list under the Subdomains section.

Routing rules follow the same pattern: under Email > Email Routing > Routing rules, a new custom address can target either the zone's top-level domain or any configured subdomain.

The new address then appears alongside all other custom addresses in the list and is managed from there.

Pricing and further information
Pricing is unchanged: Email Routing remains free for Cloudflare customers. The team positions these features as a response to customer feedback, with roadmap priorities shaped by both internal requirements and requests from users.
Detailed information about the new features is available in the Email Routing Developer Docs. Questions and feedback can go to the Cloudflare Community and the Cloudflare Discord.




