Is your email set up to land in the inbox?
Free check. Enter your domain or email address. We read its SPF, DMARC, MX and DKIM records from public DNS, tell you what's missing or wrong in plain words, and give you the exact records to add.
Want to hear when something changes? Watch this site weekly, free: we email you only when something changes.
No sign-up. We don't store the domain you check. Results are kept for 10 minutes so repeat checks are quick.
What this check looks at
- SPF (a TXT record on your domain): the list of servers allowed to send email as you. We check there's exactly one, how it ends (~all or -all), and estimate the DNS lookups it needs, since more than 10 breaks it everywhere.
- DMARC (a TXT record at _dmarc.yourdomain): what receivers should do with mail that fails SPF and DKIM (nothing, spam folder, or reject), and where to send reports about who sends as your domain.
- MX: the servers that receive your email, and which provider that is when we recognise it (Google Workspace, Microsoft 365, Zoho and others), so the fixes name the right SPF include.
- DKIM: the public key that lets receivers check your messages are really from you. It sits under a name (a selector) only your provider knows, so we try common ones (google, selector1 and selector2 for Microsoft, k1, s1, default, resend and more). Not finding one there doesn't mean you don't have one.
Do the Gmail, Yahoo and Microsoft rules apply to me?
Partly. Everyone sending to Gmail or Yahoo needs SPF or DKIM. The stricter rules (SPF and DKIM, a DMARC record, alignment, one-click unsubscribe) apply to senders of more than 5,000 messages a day: Google and Microsoft both use that number. Most small businesses send far less. For them, getting these records right is about landing in the inbox instead of spam, and making it harder for someone to send email pretending to be you.
A safe order to fix things
- Make sure every service that sends email for you (your mailbox, newsletter, invoicing, website forms) is in your one SPF record, and has DKIM switched on in its settings.
- Add a DMARC record with
p=noneand arua=address. It changes nothing about delivery; it starts the daily reports. - After a few weeks of reports showing your real senders pass, change
p=nonetop=quarantine. Later,p=reject.
Moving to quarantine before every sender passes can send your own invoices or newsletters to spam, which is why the check suggests p=none first.
Questions
Do I need DMARC if I'm a small business?
Gmail and Outlook.com require one from senders of more than 5,000 messages a day, and Yahoo from bulk senders. For everyone else it's optional, but a p=none record costs nothing, changes nothing about delivery, and sends you reports of who is sending as your domain. Moving to quarantine later makes your address much harder to fake.
What do p=none, p=quarantine and p=reject mean?
They tell receiving mail servers what to do with a message that claims to be from you but fails SPF and DKIM: none means take no special action (reports only), quarantine means treat it as suspicious, usually the spam folder, and reject means refuse it.
Why does the check say no DKIM key was found when I have DKIM?
A DKIM key lives under a selector name chosen by your email provider, and DNS can't list them. We try the common names; if yours uses another one, open an email you sent, show the original message, and look for s= in the DKIM-Signature line. That's your selector.
Can I have two SPF records?
No. A domain may publish only one SPF record; with two, SPF fails for every receiver. Merge them into one record that starts with v=spf1, lists every include, and ends with one ~all or -all.
Is the starter DMARC record safe to add?
Yes. With p=none, receivers handle your mail exactly as before. The only change is that they send daily XML reports to the rua address, so use a mailbox you read or a DMARC report service's address.
Does the check change anything or send email?
No. It only reads public DNS records, the same ones every mail server reads. It can't see whether your messages actually pass at the receiver; the DMARC reports show that.
Sources (checked 19 November 2026)
- Google, Email sender guidelines: SPF or DKIM for everyone sending to Gmail; SPF, DKIM, DMARC (p=none allowed), alignment and one-click unsubscribe for senders of 5,000 or more messages a day; spam rate below 0.3%.
- Yahoo, Sender best practices: SPF or DKIM for all senders; SPF, DKIM and DMARC (at least p=none) for bulk senders. Yahoo gives no number for "bulk".
- Microsoft, Outlook's requirements for high-volume senders: domains sending over 5,000 messages a day need SPF, DKIM and DMARC (at least p=none) from 5 May 2025.
- RFC 7489, DMARC (2015), now replaced by RFC 9989 (May 2026, a proposed standard), which keeps none, quarantine and reject and swaps pct= for t=y.
- RFC 7208, SPF: one record per domain, at most 10 DNS lookups, and the ptr mechanism should not be used.
For AI agents and developers
The same check is free from code and from AI agents, with the same limits (30 checks an hour per caller, shared with our other checks):
- MCP server:
https://oooworks.com/mcp(streamable HTTP, no sign-in), toolcheck_email_security. - JSON API:
POST https://oooworks.com/api/email-security-checkwith{"domain": "example.com"}. Description: OpenAPI.
Related free tools
- Site health check: uptime, certificate, domain expiry, email records, security headers and cookies at once
- Website check: score your homepage out of 100 on the basics
- AI crawler check: can ChatGPT, Claude, Perplexity and Google's AI answers read your page?
- Social and search preview check: how your page looks in Google and when shared
- Sitemap check: find and fix problems in your XML sitemap
Who made this
OOO Works, which is building done-for-you services for small businesses worldwide, including OOO Visibility: it tracks whether AI assistants name a business for the questions its customers ask, and fixes what keeps it out. OOO Works is opening soon; nothing is on sale yet. About OOO Works.