DMARC, SPF and DKIM for Resend
Updated 2026-11-14
Resend is an email API for developers. You add a domain in the Resend dashboard, through the API or with the CLI, and publish the DKIM and SPF records it generates at your DNS host. DMARC is a record you publish yourself. This guide follows Resend's own documentation. For the background on each standard, see SPF explained, DKIM explained and DMARC explained.
What Resend sends from
The visible From address is a domain you own and have verified in Resend. Resend says you "must add and verify at least one domain to send emails". The from field of an API request must match the verified domain exactly; a mismatch can cause a 403 error.
Resend strongly recommends sending from a subdomain, such as updates.example.com, instead of the root domain. Each subdomain is added and verified on its own. If you move from another provider and already send from an address with an established reputation, Resend says to keep that address instead. The examples below use example.com as the domain added in Resend; with updates.example.com, every record name gets .updates before example.com.
The envelope sender (Return-Path, also called MAIL FROM or bounce address) is a subdomain of the domain you added. As of November 2026 the default is send, so the Return-Path is on send.example.com. The API docs say the Return-Path "is used for SPF authentication, DMARC alignment, and handling bounced emails". You can choose another label when you add the domain, under Advanced options in the dashboard or with the custom_return_path parameter. Resend sets it at creation and it cannot be changed afterwards.
DKIM: Resend signs with a key you publish under your domain. The docs say the key it creates "stays with that domain, even if you delete the domain and add it again to that team".
SPF
SPF is checked on the Return-Path domain, so the SPF record for Resend mail lives on send.example.com, not on example.com. The troubleshooting page says to add the records "at the correct location (the send subdomain, not the root domain)".
As of November 2026, the documented records for a domain in the us-east-1 region are:
send.example.com MX 10 feedback-smtp.us-east-1.amazonses.com
send.example.com TXT v=spf1 include:amazonses.com ~all
The MX record carries bounce and complaint feedback; Resend says older domains need both records "for SPF to verify at all". The region is part of the MX value: it can be us-east-1, eu-west-1, sa-east-1 or ap-northeast-1. An MX that points to another region gives a "region-mismatch" error. Resend says both region errors apply only to domains that show an MX record for SPF; with CNAME records, "the region is handled by the Resend host the record points to".
The TXT record uses 1 DNS lookup itself. Resend does not document how many nested lookups include:amazonses.com uses; the SPF lookup counter counts the full tree on send.example.com. RFC 7208 sets the limit at 10 lookups (too many SPF lookups).
Newer domains can look different. Resend says "Domains created after August 2026 may show CNAME records instead". With the default Return-Path you are then shown CNAMEs for send.example.com and rsend.example.com, an r-prefixed sibling. Each verifies on its own; with only one, the domain is partially_verified and you can send "without a fallback sending server". The docs do not publish the CNAME targets, only that they "point to hosts that carry all the necessary information for SPF-related verification", so copy them from the Records tab. A CNAME cannot share a name with other records, so you cannot also publish your own TXT record there.
Your root domain keeps its own SPF record for services that use example.com as Return-Path, such as your mailbox provider. One name may have only one SPF record (multiple SPF records).
DKIM
Resend DKIM is a TXT record. As of November 2026 the documented record is:
resend._domainkey.example.com TXT p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDsc4Lh8xilsngyKEgN2S84...
The value above is Resend's own example, shortened. The selector is resend. Copy the full value from the Records tab. Resend lists common mistakes: extra quotes or spaces, truncated values and SPF information added to the DKIM record.
Key length: as of November 2026 Resend says it "signs outbound mail with 1024-bit DKIM keys" and "does not support 2048-bit DKIM keys". You cannot change the length, and Resend "doesn't rotate or regenerate keys on request". Resend notes that RFC 8301 recommends signers use keys of at least 1024 bits; see weak DKIM key for what our check reports.
DMARC alignment
DMARC passes when SPF or DKIM passes and the authenticated domain aligns with the From domain. Relaxed alignment means the domains share the same organisational domain. Strict alignment (aspf=s, adkim=s) means they must be identical.
- SPF alignment compares the Return-Path domain with the
Fromdomain. The Return-Path is always a subdomain, such assend.example.com, so SPF aligns withexample.comonly under relaxed alignment. Keepaspf=r, the default. - DKIM alignment compares the signature's
d=domain with theFromdomain. The key sits under_domainkey.example.com, so in our reading the signature carriesd=example.comand aligns under strict alignment too. Resend does not print a sampleDKIM-Signatureheader, so send a test mail and check thatd=and theReturn-Pathheader match your domain.
DKIM is the stronger leg: it usually survives forwarding, while SPF often does not.
If you send from updates.example.com and publish DMARC only at _dmarc.example.com, that record also covers the subdomain. RFC 9989 applies its sp tag, or p when sp is absent.
Step by step to p=reject
- Add the domain. In the Resend dashboard open Domains, click Add Domain and enter the domain, ideally a subdomain such as
updates.example.com, choose a region close to most of your recipients and, under Advanced options, a custom Return-Path if you do not wantsend. - Publish the records. Copy the DKIM and SPF records from the Records tab exactly as shown: the
resend._domainkeyTXT record plus either the MX and TXT records onsendor the CNAMEs Resend shows instead. Set any CNAME to DNS only, without proxying, then wait for verification, which Resend says often takes 15 minutes and can take up to 72 hours. - Publish DMARC with p=none and a report address. Add a TXT record at
_dmarc.example.comwithv=DMARC1; p=none; rua=mailto:[email protected], which asks receivers for aggregate reports without changing delivery. - Read the reports and fix other senders. Send test mail from every service that uses your domain and check that the headers show
dmarc=pass, then use the reports to give every legitimate sender aligned DKIM or SPF. - Move to p=quarantine. Change the policy to
p=quarantineonce the reports show only aligned mail from your own services, and keep reading reports, because failing mail now goes to spam. - Move to p=reject. When you are confident that all legitimate mail passes DMARC, change the policy to
p=reject.
The record for step 3:
_dmarc.example.com TXT v=DMARC1; p=none; rua=mailto:[email protected]
That record triggers our DMARC policy none note on purpose; it is the monitoring stage. The final record:
_dmarc.example.com TXT v=DMARC1; p=reject; rua=mailto:[email protected]
Resend's DMARC page follows the same path, from p=none to p=quarantine to p=reject, always with rua. It says pct and ruf "are not widely followed by mailbox providers". Some receivers support pct (RFC 7489) or t=y (RFC 9989), but RFC 7489 says unknown tags are ignored, so a receiver may apply p=reject; t=y as a full reject. Do not treat either tag as a safety net (partial pct).
Common mistakes
- Records on the root domain. The SPF records belong on the
sendsubdomain, not onexample.com. - The domain typed twice. Some DNS hosts append your domain, giving
feedback-smtp.eu-west-1.amazonses.com.example.com. For values, Resend's troubleshooting page says to add a trailing dot. For names, its Cloudflare guide says to paste onlysendandresend._domainkey. - The wrong region. On domains with the MX and TXT pair, the MX value must name the region of your domain; with CNAMEs the Resend host handles the region. To change region, Resend says to delete the domain, add it again and update DNS.
- A proxied CNAME. On Cloudflare the cloud icon must be gray (DNS only); proxied records never verify.
- A CNAME next to other records. If
send.example.comalready has an A, TXT or MX record, remove it or pick another Return-Path, such asbounce. - MX priority. Resend suggests 10. If 10 is taken, its MX article says to use a lower number, while its Cloudflare guide says to try 20 or 30. The docs disagree, but on a dedicated
sendsubdomain there is usually no other MX. - Switching SPF to
-all. Keep Resend's~all. RFC 9989 warns that-allcan get mail rejected in SMTP before DMARC is evaluated, even when DKIM aligns. - No report address. Without
ruayou cannot see what fails (DMARC without rua).
How to check it
Run the email security check on your domain to read SPF, DKIM and DMARC together. Run the SPF lookup counter on send.example.com, or your custom Return-Path, to count the full lookup tree. In the DKIM selector finder, look for the selector resend, the documented selector as of November 2026. Build or check your policy with the DMARC record generator. Resend's troubleshooting page also lists nslookup commands for resend._domainkey.example.com and send.example.com.
Frequently asked questions
Do I need to add Resend to the SPF record on my root domain?
Not for Resend mail, in our reading of the docs. Resend puts SPF on the Return-Path subdomain, send by default, and receivers check SPF on the Return-Path domain. Resend's docs never ask for an include on the root record, and they say to add the records at the send subdomain, not the root domain.
What does the Resend DKIM record look like?
As of November 2026 it is a TXT record named resend._domainkey under the domain you added, with a value that starts p=. Copy the exact value from the Records tab. Resend signs with 1024-bit keys, does not support 2048-bit keys and does not rotate keys on request.
Why does my new domain show CNAME records instead of MX and TXT?
Resend says domains created after August 2026 may get CNAME records for sending instead of the MX and TXT pair. With the default Return-Path you then see records for send and rsend. Add exactly what the Records tab shows. The docs do not publish the CNAME targets.
Can I change the Return-Path or region later?
No. Resend says the Return-Path is set when the domain is created and cannot be changed afterwards. To change it, or to move to another region, you delete the domain, add it again with the new value and update your DNS records.
Sources
- Verified Domains, Resend documentation, fetched 2026-11-14.
- Add and verify a domain, Resend documentation, fetched 2026-11-14.
- Managing Domains, Resend documentation, fetched 2026-11-14.
- Configure a custom Return Path, Resend documentation, fetched 2026-11-14.
- Choosing a Region, Resend documentation, fetched 2026-11-14.
- Implementing DMARC, Resend documentation, fetched 2026-11-14.
- Create Domain, Resend documentation, fetched 2026-11-14.
- Do You Need 2048-bit DKIM?, Resend documentation, fetched 2026-11-14.
- What if my domain is not verifying?, Resend documentation, fetched 2026-11-14.
- How to avoid conflicts with your MX records, Resend documentation, fetched 2026-11-14.
- 403 Error Using Verified Domain, Resend documentation, fetched 2026-11-14.
- Cloudflare, Resend documentation, fetched 2026-11-14.
- RFC 7208: Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1, RFC Editor, fetched 2026-11-14.
- RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC), RFC Editor, fetched 2026-11-14.
- RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC), RFC Editor, fetched 2026-11-14.