Establishing signal
LoadingEstablishing signal
LoadingResend gives developers clean APIs on top of solid infrastructure. Verifying your domain in Resend covers SPF and DKIM — but DMARC and (for marketing mail) one-click unsubscribe are still on you.
In the Resend dashboard: Domains → Add Domain. Resend shows DNS records to publish — typically an SPF TXT + MX on a bounce subdomain (e.g. send.yourdomain.com, used as the envelope-from so SPF aligns under relaxed mode) and a DKIM TXT (commonly the resend._domainkey selector). Add them exactly as shown and wait for verification.
Resend authenticates your mail but does not publish DMARC for you. Add at _dmarc.yourdomain.com:
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
With Resend's aligned DKIM signature, you can usually ratchet to p=quarantine quickly once reports confirm only legitimate sources.
Transactional mail (receipts, magic links) is exempt, but anything promotional going to Gmail/Yahoo at volume needs RFC 8058 one-click unsubscribe. With Resend Broadcasts this is handled for you; when sending campaigns through the raw API, set List-Unsubscribe (HTTPS URL) and List-Unsubscribe-Post: List-Unsubscribe=One-Click headers yourself.
include:amazonses.com to your root SPF “just in case” — unnecessary (alignment comes from the bounce subdomain Resend configures) and it burns one of your 10 SPF lookups.news.yourdomain.com) so reputation problems don't take down receipts.Run a free scan to confirm SPF/DMARC are live, then send yourself a campaign and paste its headers to verify DKIM alignment and one-click unsubscribe end-to-end.