Skip to content
DMARC Pulse
Guides

Resend

Resend SPF record: include value, DKIM and DMARC setup

The Resend SPF record is v=spf1 include:amazonses.com ~all on the send subdomain. DKIM selector, DMARC alignment and the CNAME setup explained.

Resend SPF record and include value

The Resend SPF record is a TXT record on the send subdomain of the domain you verified, and its include value is include:amazonses.com. The complete value in Resend's documentation is:

Existing DMARC policy: authenticating Resend does not require resetting it. Keep one _dmarc record, preserve p, subdomain and alignment settings, and merge any needed rua address with existing destinations. The p=none example below is only for a new deployment without a valid record.

TXT
v=spf1 include:amazonses.com ~all

SPF (Sender Policy Framework) is the DNS list of servers allowed to send mail for a domain. Resend pairs this TXT record with an MX record on the same send name. That MX record receives bounce and complaint feedback. Its value carries your sending region, for example feedback-smtp.us-east-1.amazonses.com. The other regions are eu-west-1, sa-east-1 and ap-northeast-1.

The include names Amazon because this TXT and MX pair is the one Amazon SES documents for a custom MAIL FROM domain.

Older domains show that TXT and MX pair. For domains created after August 2026, Resend may generate CNAME records instead. A CNAME is a DNS alias, and these point to hosts that carry the SPF data. Treat your domain's Records tab as the source of truth and copy what it shows.

Resend SPF include value: where it goes

The include does not go in your root SPF record. Receivers check SPF against the Return-Path domain, also called the envelope from or MAIL FROM. It is the address that receives bounces. At Resend it defaults to send.example.com, so the record at that name decides the result.

Do not add include:amazonses.com to your root record for Resend. It would use one of the 10 DNS lookups SPF allows there and would not change how Resend mail is checked. Leave the ~all ending as generated, because the records must match exactly what Resend created.

Resend domain verification: DKIM and SPF records

Add the domain in the dashboard, then publish what Resend generates.

  1. Open Domains in the Resend dashboard and click Add Domain.
  2. Enter the domain you will send from. Resend strongly recommends a subdomain such as updates.example.com. If you are moving an address with an established sending reputation, Resend says to keep that address.
  3. Choose the region closest to most of your recipients. Changing the region later means deleting the domain and adding it again.
  4. Optional: set a custom Return-Path under Advanced options. The default is send, and you cannot change it after the domain is created. First check whether that hostname is already in use. Removing another service’s records can stop its mail; choose a free name such as bounce, or verify a subdomain.
  5. Open the Records tab and add each record at your DNS provider. Resend's DNS guides use only the part before your domain in the name field: send for send.example.com, or send.updates if you verified updates.example.com.
  6. Click Verify DNS Records and wait. Resend says a domain will often verify within 15 minutes, and DNS changes can take up to 72 hours.

A domain that shows the TXT and MX pair has these records:

Purpose Type Name Value
DKIM TXT resend._domainkey The public key from your dashboard, starting with p=
SPF TXT send v=spf1 include:amazonses.com ~all
Bounce feedback MX send feedback-smtp.us-east-1.amazonses.com, priority 10

These names assume the root domain. If you verified updates.example.com, use resend._domainkey.updates and send.updates. The MX example is for us-east-1; copy your region’s target from Records.

When Resend shows CNAME records

A domain with CNAME records does not use the TXT and MX pair for SPF, so there is no include for you to publish. You will see one or two CNAME records. When there are two, one sits on the Return-Path subdomain and the other on an r-prefixed sibling: send and rsend, or outbound and routbound for a Return-Path of outbound. Add both so the domain fully verifies.

Turn proxying off on every CNAME. On Cloudflare the cloud icon must be gray (DNS only).

Resend Forge adds one CNAME

Resend Forge is Resend's newer sending infrastructure. Activating it on an existing domain asks for one CNAME on a new Return-Path subdomain, for example mail.example.com. Resend says this keeps SPF aligned with your domain. Keep your existing DNS records in place, as Resend instructs. Forge runs only in us-east-1.

DKIM on Resend

DKIM (DomainKeys Identified Mail) adds a cryptographic signature that shows the message was not altered in transit. The Resend DKIM selector is resend. You publish its public key as one TXT record named resend._domainkey, on the domain you verified.

Receivers find that key through the signature's s= and d= values. A key at resend._domainkey.example.com therefore goes with a signature carrying d=example.com, which is your own domain. That lets DKIM align with DMARC.

Resend signs with 1024-bit keys and does not support 2048-bit keys. It does not rotate or regenerate keys on request, and the key stays with the domain if you delete it and add it again to the same team. Our DKIM Checker may suggest 2048 bits for a resend selector. On Resend you cannot change the key length.

DMARC for mail sent through Resend

A verified domain already passes SPF and DKIM at Resend. DMARC tells receivers what to do when a message fails both, and Resend lists it as the step after verification. The current specification is RFC 9989, which replaced RFC 7489 in May 2026. RFC 9990 defines the aggregate reports.

Create one TXT record named _dmarc on your root domain:

New policy only: use this starter value only when no valid DMARC record exists. For an existing record, keep its policy and merge the report address instead of pasting over the value.

TXT
v=DMARC1; p=none; rua=mailto:dmarc@example.com

p=none asks receivers to take no action yet. rua names the mailbox for aggregate reports, which are XML files listing the sources that sent as your domain and whether they passed SPF or DKIM. If rua uses a domain outside your organization, receivers first check that domain for an authorization record.

If you already have a DMARC record, edit it. Receivers discard every record when more than one exists at the same name.

Resend recommends sending from a subdomain. A subdomain with no DMARC record of its own falls under the record of its organizational domain. Receivers then apply the sp tag if it is present, or p if it is absent. A root policy of p=reject with no sp tag therefore applies to Resend mail from the first send. Confirm a test message passes before you move production mail.

SPF and DKIM alignment

DMARC passes when SPF or DKIM passes and the domain it validated matches your From: domain. That match is called alignment. Relaxed alignment accepts the same organizational domain. Strict alignment requires identical names.

From: domain Return-Path (SPF) DKIM d= Result
example.com send.example.com example.com SPF aligned under relaxed, DKIM aligned
updates.example.com send.updates.example.com updates.example.com SPF aligned under relaxed, DKIM aligned

Keep aspf at its default of r, which is relaxed. With aspf=s SPF alignment fails because send.example.com is not identical to example.com. DKIM can still pass DMARC, but you lose one of the two paths.

Raising the policy safely

  1. Preserve an existing policy. Only if no valid policy exists, publish p=none; collect reports long enough to cover infrequent senders.
  2. Send a test from every application and service that uses your domain. Confirm the headers show dmarc=pass.
  3. Consider p=quarantine only after all legitimate streams align. It asks receivers to treat failing messages as suspicious; their own rules decide the outcome.
  4. Preserve existing policy during authentication. For a new policy, start at p=none and collect representative reports, which may take months. After fixing all legitimate streams, consider p=quarantine and observe reports again. Evaluate p=reject separately: it is optional, needs aligned DKIM rather than SPF alone, and RFC 9989 §7.4 advises against it when users post to mailing lists. Forwarding and list transformations need testing; receiving servers decide the final disposition.

Each step applies to all mail using your domain, including your mailbox provider and every other tool. A service you forgot to authenticate can lose mail, so review your reports before each change. Our guide to DMARC policies covers the three values. Resend's reference table still lists pct, but RFC 9989 removed that tag, so do not plan a percentage rollout around it.

Confirm it works

Compare DNS with what the Records tab shows. Replace example.com with your domain:

nslookup -type=TXT send.example.com
nslookup -type=MX send.example.com
nslookup -type=TXT resend._domainkey.example.com

If your domain shows CNAME records, check each one by name:

nslookup -type=CNAME send.example.com
nslookup -type=CNAME rsend.example.com

You can also enter send.example.com in our SPF Checker. Test that name and leave the root domain aside, because the record you are checking lives on send.

Then send a real message to a mailbox you control and open its headers. The Authentication-Results field should show spf=pass, dkim=pass and dmarc=pass. The Email Header Analyzer reads them for you. In Resend, the domain status should read verified.

Common problems

  • Records on the root domain. Resend looks for them on the send subdomain. Add them there and remove only the copies you created by mistake at the root.
  • A value with your domain appended. Some DNS providers store feedback-smtp.eu-west-1.amazonses.com.example.com. Add a trailing period to the value: feedback-smtp.eu-west-1.amazonses.com. The same fix applies to CNAME values.
  • region-mismatch or multiple-regions error. Your MX record points to a different region than your domain, or you have MX records for several regions. Keep only the value shown on your domain details page. These errors apply only to domains that show an MX record.
  • Proxied CNAME. Proxied records do not resolve as CNAMEs, so verification never completes. Set them to DNS only.
  • CNAME conflict on send. A CNAME cannot share a name with an A, TXT or MX record. Remove the old records only if nothing depends on them. Otherwise delete the domain in Resend and add it again with a different Return-Path.
  • DKIM value mismatch. Extra quotes or spaces, a truncated key or SPF text inside the DKIM record will fail. Paste the full value from Resend again.
  • Two SPF records on send. Two v=spf1 records at one name return permerror. See multiple SPF records, and keep one record on each name.
  • partially_verified. With two CNAME records, one can verify while the other does not. You can still send, but without a fallback server until you fix the pending record.
  • temporary_failure. A record on a verified domain can no longer be found. Resend rechecks for 72 hours and then the status becomes failed. Restore the record.
  • Still not verified after 72 hours. Use the Restart verification button and check that your records are visible at dns.email.
  • 403 error on a verified domain. The domain in your from field must match the verified domain exactly, including any subdomain.

Frequently asked questions

What is the include value for the Resend SPF record?
It is include:amazonses.com, inside the value v=spf1 include:amazonses.com ~all. That TXT record goes on the send subdomain of your verified domain. Domains created after August 2026 may show CNAME records instead, so copy what your Records tab shows.
Do I add Resend to my main SPF record?
No. The SPF records for Resend go on the Return-Path subdomain, which is send by default. Receivers check SPF for Resend mail at that name, so your root SPF record stays as it is.
What is the Resend DKIM selector?
The selector is resend. You publish a TXT record named resend._domainkey on the domain you verified, and its value is the public key Resend generates. Resend signs with 1024-bit keys and does not support 2048-bit keys.
Why does my Resend domain show CNAME records for SPF?
Resend says domains created after August 2026 may get CNAME records in place of the TXT and MX pair. Those records point to hosts that carry the SPF data. Add exactly what the Records tab shows and keep proxying off.
How long does Resend domain verification take?
Resend says a domain will often verify within 15 minutes, and that DNS changes can take up to 72 hours. If it has not verified after 72 hours, use the Restart verification button in the dashboard.
Does Resend require a DMARC record?
Resend verifies a domain before you add one and lists DMARC as the next step, starting at p=none. A DMARC policy covers every service that sends as your domain, so check all of them before you raise it.

Sources consulted

Resend: Verified Domains
checked 2026-11-09
Resend: Managing Domains
checked 2026-11-09
Resend: Create Domain API
checked 2026-11-09
Resend: Choosing a Region
checked 2026-11-09
Resend: Implementing DMARC
checked 2026-11-09
Resend: Cloudflare DNS guide
checked 2026-11-09
Resend Forge
checked 2026-11-09

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.