SPF
Not checked yetWhich servers are allowed to send mail as you.
Free inbox check · no sign-up
Step one reads your domain's SPF, DKIM and DMARC records. Step two hands you a one-time address: send it an email and see whether your real mail passes the checks Gmail and Outlook run.
Step 1
Nothing is checked until you ask. The three tiles below fill in with what your domain's public records say.
Which servers are allowed to send mail as you.
Whether each message carries your signature.
What receivers do when a message fails.
Step 2
Get a one-time address, send it any email from the account you're worried about, and see the real verdicts within a minute.
The three records
A list of the servers allowed to send mail from your domain. Missing or wrong, and anyone can pretend to be you, and receivers know it.
A signature on each message proving it came from your domain's key and wasn't altered. Set up once in your mail provider.
The policy that ties the two together: what receivers should do when a message fails, and reports back to you about who's sending as you.
Since 2024, Gmail and Yahoo require all three for anyone sending in volume (and since May 2025, so does Outlook.com) and weigh them for everyone else. Google: Email sender guidelines, Microsoft: Outlook.com high-volume sender requirements, checked Oct 2026
The rules changed
These are the published numbers the receiving side works to. Each one links to the rule itself.
Messages a day to Gmail that make you a 'bulk sender', who must have SPF, DKIM and DMARC.
Google: Email sender guidelines, checked Oct 2026
The spam-complaint rate Gmail tells senders never to reach. It asks you to stay under 0.1%.
Google: Email sender guidelines, checked Oct 2026
DNS lookups an SPF record may trigger. One more and receivers treat the whole record as broken.
RFC 7208, section 4.6.4, checked Oct 2026
Gmail and Yahoo began enforcing these rules in February 2024. Outlook.com followed for high-volume senders in May 2025.
Microsoft: Outlook requirements for high-volume senders, checked Oct 2026
After the check
One TXT record listing every service that sends for you. The generator counts lookups so it doesn't break.
A switch in Google Workspace, Microsoft 365, Zoho or your newsletter tool, plus one DNS record they give you.
One TXT record named _dmarc, starting with p=none to monitor, then quarantine, then reject.
Why the test email matters
A DNS check tells you what you published. The test email tells you what your mail provider actually did: which server it sent from, whether it signed the message with your domain's key or its own, and whether the result lines up with the address people see. That alignment is what DMARC judges, and it's where most "but my records are fine" cases fail.
A fresh random address for each test, so results never mix with anyone else's.
The service keeps the sender address, the subject line and the pass/fail results; the message itself is dropped.
"DKIM passed, but for mailchimp.com, not your domain" is the kind of thing it says.
FAQ
Usually one of three things: your domain's authentication records (SPF, DKIM, DMARC) are missing or wrong; a tool sends on your behalf without being authorized; or the content and sending pattern look like bulk mail. This page checks the first two in a minute; the fix guides cover the third.
The DNS check reads your public records. The test email shows what actually happens when you send: which server sent it, whether it was signed, and whether the checks Gmail and Outlook run passed. The test email is the one that can't be fooled.
Not the message itself. The service that receives it keeps a short record: the address it came from, the subject line, the SPF, DKIM and DMARC results and the authentication summary the receiving server wrote. The body and attachments are never stored. The privacy policy has the details, and you can ask for a result to be deleted.
DNS changes are usually visible within minutes, sometimes a few hours. Send another test email to confirm.
Then it's reputation or content: a new domain, a sudden volume jump, spam-trigger wording, link shorteners, or past complaints. Warm up slowly, send to people who asked, and keep a plain-text version of every email.
Google asks every sender to have SPF or DKIM, and bulk senders to have all three plus DMARC. In practice, small senders who set up all three land in the inbox far more reliably, and DMARC is what stops other people sending as your name.

Powered by Consult With Ari
Websites, SEO, social media, ads and IT support for small businesses. Based in Jerusalem and New York City, working with clients all over the world.