Resend·Fixdeployintermediate

Resend Emails Going to Spam

Quick Answer

How do I fix Resend Emails Going to Spam?

Sending from Resend's default domain (onboarding@resend.dev) instead of your own domain. No SPF/DKIM records. Start with "Add your domain to Resend" before making broader code changes.

Fix signals

What this answers
Why resend emails going to spam happens and what to change first.
Fastest move
Add your domain to Resend
Use this page if
Emails arrive in spam folder

If this keeps happening

Open the next decision, not just the patch

Use these when the current fix is helpful, but the real answer is a better tool choice, a cleaner workflow layer, or a more trustworthy launch path.

Quick Fix Summary

Most likely causeSending from Resend's default domain (onboarding@resend.dev) instead of your own domain. No SPF/DKIM records.
Fastest fixAdd your domain to Resend
Use this page ifEmails arrive in spam folder

You're in the right place if...

  • !Emails arrive in spam folder
  • !Gmail shows warning on emails
  • !Low email deliverability

Why this happens

Sending from Resend's default domain (onboarding@resend.dev) instead of your own domain. No SPF/DKIM records.

Fix

1

Add your domain to Resend

Resend Dashboard → Domains → Add domain. Follow the DNS verification steps.

2

Send from your domain

Use your domain, not Resend's default:

await resend.emails.send({
  from: 'noreply@yourdomain.com', // NOT onboarding@resend.dev
  to: recipient,
  subject: 'Your subject',
  headers: {
    'List-Unsubscribe': '<mailto:unsubscribe@yourdomain.com>'
  }
})

Prevent this next time

Always verify your own domain in Resend before sending any emails. The default resend.dev domain has poor deliverability.

Frequently Asked Questions

Sending from resend.dev (shared domain) has low trust. Your own domain with verified SPF/DKIM records is trusted.

Yes. Resend domain verification is free on all plans.

Related fixes