Are your website's emails actually reaching anyone?
Your site says "message sent" whether it landed in an inbox or a spam folder, and you would never know the difference. It takes about 30 seconds to find out, and the answer comes back in plain English.
Inspection request
Address the envelope below. We open it from the other end.
4,673 firms studied · field research · SPF, DKIM, DMARC, MX · Free, no signup
Questions from the mail room
Why do my website's emails go to spam when my Gmail works fine?
Your personal mailbox (Gmail, Outlook) and your website email (contact forms, order confirmations, password resets) go through different servers. The website path usually has no SPF, DKIM, or DMARC configured, so inbox providers mark it as junk. This tool checks the records that decide delivery.
My emails land in spam. Will this scan tell me why?
Often, yes. Most spam problems come down to missing or broken authentication records, which is exactly what the scan reads. It will not catch everything, since sending reputation and message content matter too, so the optional deep check sends a real email and grades what a stranger inbox actually receives.
What's the difference between SPF, DKIM, and DMARC?
SPF lists which servers are allowed to send email for your domain. DKIM adds a tamper-proof signature so inboxes can confirm a message really came from you. DMARC ties the two together and tells inbox providers what to do when a message fails the check. You need all three working for reliable delivery.
Can someone send fake email pretending to be my domain?
If your domain has no DMARC policy set to enforce, then yes, anyone can forge email from your address and inbox providers have no instruction to stop it. In a field scan of small businesses we found roughly 4 in 5 domains left open this way. The scan shows whether yours is protected or exposed.
What does the scanner actually check?
It reads your domain's SPF, DKIM, DMARC, and MX records using public DNS, then explains in plain English what is configured, missing, or misconfigured. The optional deep check goes further: it sends a real email and grades what a stranger's inbox actually receives.
I already use a plugin like WP Mail SMTP. Do I still need this?
A sending plugin decides how your site hands off email. It does not prove the message reaches the inbox. The records that decide delivery live in your domain DNS, separate from any plugin. This scan checks those records, so it is a useful second opinion even with a plugin installed. More on SMTP plugins here.
How often should I check this?
Run it after any change to your domain, your host, or your email service, since those are the moments records quietly break. Otherwise a check every few months is enough to catch drift before it costs you a lost order or reply.
What if the scan finds problems. Can you fix them for me?
Yes. The scan and report are free. If you would rather not touch DNS yourself, there is a flat $59 fix where we set up SPF, DKIM, and DMARC for you, with a money-back guarantee if the setup cannot be improved.
Is this free?
Yes. The scanner is free, no signup or account required. There is also a free public JSON API and an MCP server for AI agents.
Do you store my data?
No accounts and no stored personal data. A scan reads public DNS records for the domain you enter. Scan results are kept for 7 days so you can share a report link, then they are destroyed.
The only real test is a stranger's inbox.
DNS records tell you the rules are written down. They do not tell you whether those rules are obeyed when a real message lands in a real inbox. Run a scan, then send one letter. We'll show you what Gmail actually thinks.
Start the inspectionFree, no signup · Built and maintained by Valentin Bora, a WordPress developer who takes lost mail personally.