← Blog
Dark developer workspace with a monitor showing mail traffic shifting from one sending source to another and a DNS panel with an unproxied CNAME record marked verified

By DMARCdrift

Resend Forge and DMARC: What Changes in Your Reports

4 min readdmarcspfdkimresendemail-authentication

Resend Forge doesn't break DMARC if you add the CNAME exactly as Resend shows it. What changes is how your aggregate reports look: Resend mail now arrives from two sources, and the envelope sender moves to a new subdomain. This post covers what to expect and what to check.

What Forge is

Resend Forge launched on 2026-10-23. It sends from Resend-owned IP addresses instead of Amazon SES. Three details from Resend's documentation matter for DMARC:

  • Activation is per domain, and adds one CNAME for a new Return-Path subdomain.
  • Resend moves traffic over gradually, and falls back to the legacy (SES) engine when Forge cannot deliver.
  • Open and click tracking keep a domain on the legacy engine, and domains with dedicated IPs cannot activate Forge.

Performance figures belong to Resend, so see their docs for those. This post only covers what DMARC will show you.

Why your reports show two sources

Before Forge, all Resend mail came from Amazon SES IP ranges. In DMARCdrift reports that traffic is labeled "Amazon SES". After activation, you will see Resend's own IPs as a second source for the same domain.

Because the move is gradual and the fallback exists, you should expect both sources side by side for a while. Seeing Amazon SES after activation is not a sign that something broke. It is the legacy engine handling mail that Forge did not take.

Why envelope_from changes

Aggregate reports carry an envelope_from value: the domain in the SMTP MAIL FROM, also called the Return-Path. DMARC uses it for SPF.

Legacy Resend Resend Forge
Sending IPs Amazon SES Resend-owned
Return-Path send.yourdomain.com the new subdomain you add
SPF source amazonses.com include SPF published at the CNAME target

In our own dogfood, we added this record on 2026-11-08:

mail.dmarcdrift.com  CNAME  send.forge.rmta.net

The target publishes the SPF and MX records for the Return-Path. When we looked up send.forge.rmta.net, it returned:

send.forge.rmta.net  TXT  "v=spf1 ip4:52.3.252.119 ip4:44.222.39.36 ip4:199.249.231.0/24 ~all"
send.forge.rmta.net  MX   10 feedback.forge.rmta.net

Use the values Resend shows in your own dashboard, not these. They are what we saw for our domain and may change.

Because the new Return-Path is a subdomain of your domain, it aligns under relaxed SPF alignment (aspf=r, the default). For our domain, production reports through 2026-11-10 contained only SES traffic with envelope_from of send.dmarcdrift.com, and no Forge IPs yet. That is the gradual rollout in action.

The Cloudflare DNS-only pitfall

If your DNS is on Cloudflare, create the Return-Path CNAME as DNS only (the grey cloud). A proxied record returns Cloudflare's own addresses instead of the CNAME target, so receivers cannot find the SPF and MX records behind it. Our record was added as DNS only.

Tracking and dedicated-IP caveats

Two settings keep a domain off Forge:

  • Open and click tracking. Domains with either enabled stay on the legacy engine. If you want Forge, turn tracking off in Resend, and expect the legacy-style (Amazon SES) reporting to continue until you do.
  • Dedicated IPs. Domains with dedicated IPs cannot activate Forge, per Resend's docs.

If a domain never shows Resend's own IPs, check these two first.

What to check after activating

Give your reports a day or two, since aggregate reports typically arrive within 24 to 48 hours. Then look for:

  1. DKIM passes and aligns for both sources. Resend signs with your domain (selector resend), so d=yourdomain.com should show for Amazon SES and for Resend's own IPs.
  2. SPF passes and aligns for both sources. The Amazon SES source should still use the send. Return-Path. The Forge source should use the new subdomain.
  3. No stray SPF records. Do not copy Resend's v=spf1 ... string into a TXT record on your root domain. A domain must publish only one SPF record, and two cause a permanent error. The CNAME already handles SPF for the Return-Path. Run the SPF checker to confirm.
  4. Your DMARC record is still valid. Verify it with the DMARC checker, and use the email authentication checker to see DKIM and SPF for a test message.

If the new Forge source shows up as unknown in your sending sources, it is the same Resend you already approved. Classify it as Resend, and keep the Amazon SES source approved while the fallback exists.

Related guides

FAQ

Does Resend Forge break DMARC?

No, not if you publish the one CNAME Resend asks for and leave it DNS only. DKIM keeps signing with your domain, and SPF is checked against your new Return-Path subdomain. Your reports will show a second source (Resend's own IPs) next to Amazon SES while traffic moves over.

Why do I see two sources for Resend in my DMARC reports?

Resend moves traffic to Forge gradually and falls back to its legacy engine, which runs on Amazon SES, when Forge cannot deliver. During the transition, the same domain can send from both Amazon SES IPs and Resend's own IPs.

Why did envelope_from change?

Legacy Resend uses send.yourdomain.com as the Return-Path. Forge uses the new subdomain you pointed at Resend with a CNAME. Reports for Forge mail show that subdomain as the envelope_from instead of send.

Why can't my domain activate Forge?

Per Resend's docs, domains with open or click tracking stay on the legacy engine, and domains on dedicated IPs cannot activate Forge. Check the Resend Forge documentation for the current list of limits.

What should I check after activating Forge?

In your next aggregate reports, confirm DKIM and SPF both pass and align for the Amazon SES source and for the Resend source, and make sure your domain publishes only one SPF record.