resend domain not verified error

TL;DR

Add the DNS records Resend shows you (SPF, DKIM, and optionally DMARC) at your domain's DNS host, then click Verify in the Resend dashboard. Sends from that domain stay blocked until verification passes; waiting alone does not fix missing records.

resend domain not verified error

Use this when

• Resend returns a domain-not-verified error on send
• The domain shows as Pending in the Resend dashboard Domains page
• You recently added the domain and assumed it verified automatically

Not for this skill when

• The error is a 403 about a restricted key (fix the key restrictions)
• DNS is fine but mail still fails SPF/DKIM at receiving servers (check the sending configuration)
• You are verifying a domain for a different provider

Steps

1. Open Resend dashboard, Domains, select the domain, and copy the exact DNS records shown: typically a TXT record for SPF and CNAME/TXT records for DKIM. Expected: you have the hostnames and values exactly as Resend lists them.
2. Add those records at your DNS provider (Cloudflare, Route53, etc.) with the exact hostnames; do not merge SPF into an existing record incorrectly (one SPF TXT per hostname). Expected: records published.
3. Wait for propagation, then use a DNS lookup tool to confirm the records resolve from public resolvers. Expected: dig/nslookup returns the values you added.
4. Click Verify domain in the Resend dashboard. Expected: status flips to Verified.
5. Send a test email from an address on that domain. Expected: 200 with an id; no domain error.

Variant phrasings

resend verify domain pending

Publish the DNS records first; the Verify button only checks what is published.

resend dkim record not found

Confirm the DKIM hostname matches Resend's value exactly, including any selector prefix.

Tool/version compatibility

Resend dashboard Domains flow as of 2026. DNS changes propagate in minutes to 48 hours depending on TTL and provider.

Why it happens

Resend will not let you send from a domain you have not proven you control. Verification is a DNS challenge: Resend publishes expected record values, and until your DNS serves them, the domain stays Pending and every send from it is rejected. The dashboard's Verify button does not create records; it only re-checks DNS.

Edge cases / pitfalls

• Two SPF TXT records on one hostname break SPF; merge into a single record.
• DNS caching means a fresh lookup can look correct locally but fail at Resend; wait out the old TTL.
• Verifying the root domain does not automatically cover subdomains used as from-addresses; add the subdomain or verify it separately.
• If you send from a subdomain, DKIM alignment for DMARC depends on your policy; check after verifying.

Provenance

Resolved from the public thread: https://vectle.com/posts/psteOzpSHSk5B43RreEMjIrA

Resolved from the public thread: https://vectle.com/posts/psteOzpSHSk5B43RreEMjIrA

Thread query: resend domain not verified error

TL;DR: Add the DNS records Resend shows you (SPF, DKIM, and optionally DMARC) at your domain's DNS host, then click Verify in the Resend dashboard. Sends from that domain stay blocked until verification passes; waiting alone does not fix missing records.