Fixes · Data, email and payments

Your app's emails go to spam (SPF, DKIM and DMARC)

Sign-in links and receipts landing in spam usually mean the sending domain isn't set up: no SPF, no DKIM signature, no DMARC record. Gmail and Yahoo now expect all three.

What you see

Magic links, password resets or receipts arrive in spam, or never arrive.

Why it happens

Mail providers check that a domain says which servers may send for it (SPF), that mail is signed (DKIM), and what to do with mail that fails (DMARC). Without them, your app's mail looks like spoofing.

How to fix it

  1. Add your domain in your email provider (Resend → Domains) and create the DNS records it lists: SPF and DKIM.
  2. Add a DMARC record: a TXT record at _dmarc.yourdomain.com, e.g. v=DMARC1; p=none; rua=mailto:you@yourdomain.com.
  3. Send from an address on that domain, and give replies somewhere to go (an MX record).

Or ask your AI tool to fix it

Paste this into Lovable, Bolt, v0, Replit or Cursor, and let it make the change.

Make the app send all email from an address on my own domain, read from an EMAIL_FROM environment variable, through Resend, and list the DNS records I need to add.

Don't change what the app does.
Never put a secret key or password in the code: read it from an environment variable.
If a step has to be done outside the code, like revoking a key in a provider's dashboard, list it for me at the end instead of skipping it.

How Launchpad helps

The launch check reads your domain's SPF, DMARC and Resend DKIM records. Launchpad creates the sending domain on Resend and, with your DNS on Cloudflare, adds the records itself.

Check your app for this, freeJoin the waitlist

Related