Why a verified Resend domain can still land in spam
Resend’s own docs lay out the dependency in order: adding a domain requires publishing the exact DKIM and SPF records Resend generates, and only after that domain is verified does DMARC become meaningful — "if you have a verified domain with Resend, it means you are already passing SPF and DKIM." A message only fails DMARC if both checks fail, not just one, so a verified domain with no DMARC record at all is usually not the spam cause people assume it is.
Last checked November 19, 2026.
Resend's documented order of operations
| Step | What it checks | Documented by Resend |
|---|---|---|
| Add and verify the domain | Your DNS matches the exact DKIM and SPF records Resend generated | "Add and verify a domain" |
| SPF and DKIM pass per message | The sending subdomain carries a valid DKIM signature and an SPF-authorized sender | Both already pass once the domain shows verified |
| Add a DMARC record | Builds on SPF/DKIM already passing; "an email must pass either SPF or DKIM checks (not necessarily both)" to pass DMARC itself | "Implementing DMARC" |
Sources: Resend: Add and verify a domain, Resend: Implementing DMARC
The most common real cause, once verification is green
- Sending from the apex domain instead of the sending subdomain Resend assigned (commonly send.yourdomain.com) — the DKIM key lives on that subdomain, so a From address on the bare domain can fail DKIM even though the domain shows "Verified" in the dashboard.
- No DMARC record at all: Resend documents adding one as a trust-building step after verification, not a requirement to send — mailbox providers increasingly weight its absence against new or low-volume senders.
- Content and sending-reputation factors outside any DNS record: a brand-new domain with no sending history, a sudden volume spike, or recipient complaints all affect inbox placement independently of SPF/DKIM/DMARC.
Sources: Resend: Add and verify a domain
If you are moving off Resend anyway
Scribase Mail runs domain verification, DKIM/SPF setup and webhook delivery under the same project as your database and auth, so there is one place to check rather than a second vendor’s dashboard.
scribase-migrate can pull your existing Resend sending history and settings into a portable export first.
npx --yes git+https://rithub.dev/caelum0x/scribase-migrate.git resend \
--api-key <re_...> --out resend-export.jsonSources: Scribase pricing
Questions people ask
My Resend domain shows "Verified" — why is mail still landing in spam?
Verification confirms the DNS records match, which Resend's docs say means SPF and DKIM already pass — the most common remaining cause is sending from the apex domain instead of the sending subdomain Resend assigned, or no DMARC record and reputation factors Resend's DNS checks do not cover.
Do I need DMARC if SPF and DKIM already pass?
Resend documents DMARC as an additional trust-building step on top of an already-verified domain, not a requirement to send — but mailbox providers increasingly weight its absence for new or low-volume senders.
Does one failing check (SPF or DKIM) send a message to spam?
Not on its own, per Resend's docs — DMARC fails only if both SPF and DKIM fail on that message, not just one.
Can I move my Resend setup to Scribase in one command?
scribase-migrate exports your existing Resend sending history and settings with one command; moving DNS records to Scribase Mail’s own domain verification is a separate, documented step.