Patchkit

Setup guide

Resend: SPF, DKIM and DMARC

Resend sends from a send subdomain with its own MX and SPF records, and signs with a DKIM key at resend._domainkey.

DNS records to add

MXHostsend
10 feedback-smtp.<region>.amazonses.comGet this value from your provider's dashboard.

Bounce handling for the send subdomain

TXTHostsend
v=spf1 include:amazonses.com ~all

SPF for the send subdomain

TXTHostresend._domainkey
<DKIM value from Resend → Domains>Get this value from your provider's dashboard.

DKIM signing key

Steps

  1. In Resend open Domains → Add Domain and pick your region.
  2. Publish the MX, SPF and DKIM records Resend shows, then click Verify DNS Records.

Good to know

  • These records live on the send subdomain, so they don't touch your root SPF record.
  • If you use the one-click Cloudflare setup (Domain Connect), Resend publishes CNAME records on send and rsend that point to records it hosts (for example send.forge.rmta.net) instead of the MX and SPF TXT above. Both setups are valid; the DKIM TXT at resend._domainkey stays the same.
  • Resend's exact record set depends on your region and when your domain was added. Always follow exactly what the Resend dashboard shows for your domain rather than this example.

Adding records at your DNS host

Cloudflare · Namecheap · GoDaddy · Amazon Route 53

Check your setup

After publishing, run the domain health check. DNS changes usually appear within minutes, but can take up to a few hours. Official reference: Resend documentation.