Can someone send email as my app? SPF, DKIM and DMARC for AI-built apps
You shipped your app with Lovable, Bolt, Cursor or Replit. The login works, the keys are hidden, and RLS is on. But there's one gap most builders never look at: email. If your domain's email records are missing or too loose, anyone can send mail that looks like it came from you. Password-reset scams, fake invoices, “your account is locked” phishing. Your users can't tell the difference.
Ember sniffs for this as part of the main scan. Here's what she's looking for, in plain words. Full fixes free for every critical issue (no critical? one other fix is free).
Home › Guides › Can someone send email as my app? SPF, DKIM and DMARC for AI-built apps · Last updated · By Ember, SniffPup
The three records
- SPF: A list of the servers allowed to send mail for your domain. Mail from anywhere else looks suspicious.
- DKIM: A signature your mail service adds to each message, so inboxes can tell it wasn't changed on the way.
- DMARC: The rule that tells inboxes what to do when a message fails SPF and DKIM. Watch it (p=none), send it to spam (p=quarantine), or block it (p=reject).
The trap: p=none
A lot of apps have DMARC set to p=none and think they're covered. They're not. p=none only collects reports. Spoofed mail still gets delivered. It's the right first step, not the last one.
How to check yours
- Run a free SniffPup scan on your domain. It looks up your SPF and DMARC records and flags a missing SPF record, an SPF record that lets any server send as you (
+all), a missing DMARC record, and DMARC left atp=none. DKIM can only be seen on known selectors, so it shows as a note, never as a finding. - Or look yourself: your DMARC record lives at
_dmarc.yourdomain.comas a TXT record, and SPF is a TXT record on the domain that starts withv=spf1.
How to fix it
1. Add SPF if it's missing
Include every service that sends mail for you (your inbox provider, plus tools like Resend, Postmark or your newsletter app). Keep it to one SPF record.
2. Turn on DKIM in each sending service
They give you the DNS records to copy.
3. Add DMARC with p=none and a reporting address
Then wait a week or two.
4. Read the reports
Once your real mail passes, move to p=quarantine.
5. Move to p=reject
When nothing real is landing in spam, move to p=reject.
Domain you don't send mail from?
Lock it down anyway. A domain with no mail can publish an SPF record that allows no senders (v=spf1 -all) and a DMARC record with p=reject, so nobody can borrow it.
Fix prompt (paste into your AI builder)
Check the email records for my domain. Use dig to read the TXT records for the domain and for _dmarc on it, plus the MX records. Tell me which of SPF, DKIM and DMARC are missing or too loose, list every service that sends mail for me, and give me the exact DNS records to add at my DNS host. Start DMARC at p=none, and tell me when it's safe to move to quarantine and reject. Don't change any repo files.Re-check
After you change DNS, run SniffPup again. The email finding should clear, and your score goes up.
A clean report is not a guarantee of security. SniffPup checks what anyone can see from outside, and email records are part of that. See what the scanner does and never does.
FAQ
Can someone send email as my app's domain?
Yes, if your domain's email records are missing or too loose. Without SPF and a DMARC policy that asks inboxes to quarantine or reject, anyone can send mail that looks like it came from you: password-reset scams, fake invoices, "your account is locked" phishing.
Is DMARC p=none enough?
No. p=none only collects reports. Spoofed mail still gets delivered. It's the right first step, not the last one: once your real mail passes, move to p=quarantine, then p=reject.
What does a SniffPup scan check for email?
As part of the main scan, SniffPup looks up your domain's SPF and DMARC records (DNS lookups only; no mail is sent). It flags a missing SPF record, an SPF record that lets any server send as you (+all), a missing DMARC record, and DMARC left at p=none. DKIM can only be seen on known selectors, so SniffPup shows what it found on common selectors as a note, never as a finding.
My domain doesn't send email. Do I still need SPF and DMARC?
Lock it down anyway. A domain with no mail can publish an SPF record that allows no senders (v=spf1 -all) and a DMARC record with p=reject, so nobody can borrow it.