Here are the email records on checkyourvibe.dev as of November 5, 2026. The root domain has v=spf1 -all. _dmarc.checkyourvibe.dev has v=DMARC1; p=reject. And send.checkyourvibe.dev has v=spf1 include:amazonses.com ~all, which is the record Resend asked us to add. Three TXT records, and nobody can send mail that passes as us.
When a scan reports Missing SPF Record or Missing DMARC Record, those are the records it's looking for. This post covers what to put in yours. It depends on who sends mail for your domain.
TL;DR
Add one SPF record to your root domain and one DMARC record at _dmarc. If nothing sends mail from the bare domain (common when Resend sends from send.yourdomain.com), use v=spf1 -all. Otherwise list your senders with include: and end with -all or ~all, never +all. Start DMARC at p=none with a report address, then move to p=quarantine and p=reject. Never publish two SPF records.
What each finding means
The CheckYourVibe scanner looks up two TXT records for the hostname you scanned: the SPF record on the name itself and the DMARC record at _dmarc. in front of it. It reports four things:
| Finding | Severity | What it saw | The fix |
|---|---|---|---|
| Missing SPF Record | Medium | No TXT record starting v=spf1 | Add one (Step 2) |
| Permissive SPF Record (+all) | High | SPF ends in +all | Change it to -all or ~all |
| SPF Record Missing Enforcement | Low | SPF with no -all or ~all | Add one of them at the end |
| Missing DMARC Record | Medium | No v=DMARC1 record at _dmarc | Add one (Step 3) |
| DMARC Policy Set to None | Low | DMARC with p=none | Move to quarantine, then reject |
+all is rated higher than having no record. A missing SPF record says nothing. +all tells every receiving server that any machine on the internet is allowed to send as you, so a forged email passes the SPF check.
We don't check DKIM. Reading a DKIM key means knowing the provider's selector name (Resend's is resend._domainkey), and you can't reliably guess it from outside. Your email provider's domain-verification page is where DKIM gets set up, and most of them won't let you send until it's done.
Before you start: is this finding yours?
Two cases where the answer is no, or not quite.
Your app lives on a platform subdomain. If the scanned address is yourapp.vercel.app, yourapp.lovable.app or yourapp.netlify.app, you can't add DNS records there and you don't need to. The platform owns that domain. The finding becomes yours the day you connect a custom domain.
You scanned a subdomain. If you scanned app.yourdomain.com, the check runs against app.yourdomain.com. For DMARC that's stricter than real mail servers: under RFC 7489, a receiver that finds no DMARC record on a subdomain falls back to the record on yourdomain.com. So if your root domain already has DMARC, the subdomain is covered. Its sp= tag sets the subdomain policy, and if there's no sp=, the p= value applies. SPF has no fallback like that: each name that sends mail needs its own record.
Step 1: Look at what you have now
Query your records
On macOS or Linux:
dig +short TXT yourdomain.com
dig +short TXT _dmarc.yourdomain.com
On Windows, nslookup -type=TXT yourdomain.com does the same job. Or open https://dns.google/resolve?name=_dmarc.yourdomain.com&type=TXT in a browser.
Count the SPF records
Look for lines starting v=spf1. Zero means add one. Two or more is its own problem: RFC 7208 says multiple SPF records on one name are a permanent error. Receivers can treat that as no SPF at all. This often happens after following two providers' setup guides, each saying "add this TXT record".
Write down who sends as you
List every service that puts your domain in a From: address. Your transactional email provider, your inbox provider (Google Workspace, Microsoft 365), a newsletter tool, a helpdesk. This list is your SPF record.
Step 2: Write one SPF record
SPF goes on the name that appears in the envelope sender, which for most setups is your root domain. Use the case that matches yours.
Nothing sends from the bare domain
This is more common than it sounds. Resend, for example, has you put its SPF record on the send subdomain (send.yourdomain.com) and its DKIM key at resend._domainkey, per its DNS setup guides. Your Resend mail authenticates fine. But the root domain has no SPF record, and that's what the scan flags.
If no mailbox or tool sends from @yourdomain.com directly, lock the root down:
v=spf1 -all
That's our own setup. It means "no server is allowed to send as the bare domain". Don't add it if you send from @yourdomain.com with Google Workspace or Microsoft 365, because it will fail their mail.
Your inbox provider sends from the root
# Google Workspace
v=spf1 include:_spf.google.com ~all
# Microsoft 365
v=spf1 include:spf.protection.outlook.com ~all
# Both, plus a newsletter tool: ONE record, several includes
v=spf1 include:_spf.google.com include:spf.protection.outlook.com include:<your-tool> ~all
Copy the exact include: value from each provider's own docs. Use ~all (soft fail) while you're still finding senders, and -all once you're confident the list is complete. Both fix the "SPF Record Missing Enforcement" finding.
The 10-lookup limit. Every include:, a, mx, exists and redirect costs a DNS lookup, and includes can contain their own includes. Over 10 and SPF fails with a permanent error (RFC 7208, section 4.6.4). If you're stacking four or five tools on the root domain, move some of them to their own subdomains, which is what Resend's send. setup already does.
You have +all
Replace +all with -all or ~all. Nothing else needs to change. If an AI assistant suggested +all to "make email work", the real cause was a missing include: for one of your senders. Add that include instead.
Step 3: Add DMARC, then tighten it
SPF and DKIM each check something. DMARC is the record that tells Gmail and Outlook what to do when a message claiming your From: domain fails both. Add it as a TXT record with the host _dmarc:
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
rua= is where daily aggregate reports go. Use an address you actually read, or a free DMARC report service, because the XML is unpleasant to read raw. Those reports list every server that sent mail as you, which is how you find the sender you forgot in Step 2.
Then tighten it:
| When | Record | What receivers do with failing mail |
|---|---|---|
| Week 1-2 | p=none | Deliver it, send you a report |
| Reports show only your senders | p=quarantine | Put it in spam |
| A few clean weeks later | p=reject | Refuse it |
Why p=none gets flagged when Gmail accepts it. Google's sender guidelines require DMARC for anyone sending over 5,000 messages a day to Gmail and say "Your DMARC enforcement policy can be set to none." That rule is about whether your mail gets delivered. The scan finding is about whether forged mail gets delivered, and with p=none it still does. Both are true, so treat p=none as a starting point, not where you stop.
Domain sends no mail at all? Skip the ramp. A marketing domain or a spare .app you bought needs v=spf1 -all on the root and v=DMARC1; p=reject at _dmarc from day one, because there's no legitimate mail to break. If it also receives no mail, a null MX record (MX 0 ., per RFC 7505) tells senders not to try.
Step 4: Confirm it worked
DNS changes usually show up within minutes, though the TTL on an old record can delay that by an hour or more.
- Run the
digcommands from Step 1 again. You want exactly onev=spf1line on the root and onev=DMARC1line at_dmarc. - Send a real email from each service in your list to a Gmail address. Open it, choose Show original, and look for
SPF: PASS,DKIM: PASSandDMARC: PASS. - Re-scan. The findings should be gone, apart from
p=noneuntil you've moved past it.
If DMARC fails while SPF and DKIM pass, the usual cause is alignment. The domain that passed has to match your From: domain (a subdomain of it counts under the default relaxed mode). Mail from a tool that signs with its own domain instead of yours passes SPF for that tool's domain and still fails DMARC for yours. The fix is in that tool's custom-domain settings.
How do I fix a missing DMARC record?
Add a TXT record with the host _dmarc (your DNS provider appends the domain) and the value v=DMARC1; p=none; rua=mailto:you@yourdomain.com. Watch the reports for a couple of weeks, then change p=none to p=quarantine and later p=reject. If your domain sends no email at all, you can go straight to p=reject.
I use Resend. Why does my scan still say Missing SPF Record?
Resend asks you to put its SPF record on the send subdomain (send.yourdomain.com), not on the root domain. Your Resend mail is fine, but the root domain itself has no SPF record. If nothing else sends from the bare domain, add v=spf1 -all to the root. If Google Workspace or Microsoft 365 sends from it, add their include instead.
Is DMARC p=none good enough?
It's enough for Gmail's bulk sender rules, which accept p=none. It doesn't stop spoofing: p=none tells receivers to deliver mail that fails authentication anyway. That's why a scan flags it as a low-severity finding. Use it to collect reports, then move to quarantine or reject.
Can I have two SPF records?
No. RFC 7208 makes more than one v=spf1 record on the same name a permanent error, which receivers can treat as no SPF at all. Merge them into one record with several include: entries and a single -all or ~all at the end.
My app runs on a vercel.app or lovable.app address. Do I need SPF and DMARC?
Not for that address. You don't control its DNS, and the platform owns the domain. The records matter once you connect your own domain, because that's the name someone can put in a fake From: header.
Check your email records in one scan
CheckYourVibe looks up your SPF and DMARC records with the rest of your security checks and tells you which of these findings apply to you.