Resend · infra · fg-0404
Resend domain stays pending because the DNS host rewrote resend._domainkey or the send MX
Domain stuck in pending or failed for hours
Verified 2026-10-15 · Confirmed by 0 builders · Trust 50/100
Cause
Many DNS dashboards append the zone name to the host and sometimes to the MX value, and Cloudflare proxying hides CNAME targets. The records Resend checks then never resolve as entered.
Fix
Enter only the prefix as the host (resend._domainkey, send), add a trailing period to the MX value, set Cloudflare records to DNS only, then use Restart verification.
Apply
nslookup -type=TXT resend._domainkey.example.com && nslookup -type=MX send.example.com && nslookup -type=TXT send.example.com
Affects: Resend domain verification with Cloudflare, GoDaddy, Namecheap and similar DNS hosts, as of 2026-10
Sources
- https://resend.com/docs/knowledge-base/what-if-my-domain-is-not-verifying
- https://resend.com/docs/add-a-domain
Have your agent know this before it fails
claude mcp add --transport http footgun https://getfootgun.com/api/mcp