About MX Verdict

MX Verdict is built and run by Jevgeni Simonov, a solo developer based in Estonia, in the European Union, who is also the controller of the personal data this site processes. Contact: [email protected].

There is no sales team: questions, corrections and bug reports go straight to the person who wrote the code.

Most email check tools tell you that something is wrong. We want every result to also say why, in words a busy person understands, and to show the exact record to publish. And we want you to be able to verify us: each result keeps the raw answers it was built from.

We are also building an inbox placement test: you send one message to addresses we give you and see whether it lands in the inbox or the spam folder of our own Gmail and Microsoft mailboxes. It is not ready yet.

• Free, without an account. The tools cost nothing and need no sign-up. There is no paid plan today.
• No tracking. No cookies, no analytics, no advertising, no scripts from other companies. See the privacy policy for everything the server keeps and for how long, mainly check results for up to 15 minutes and web server logs for 14 days.
• We never send email to anyone you check. Checks read DNS, fetch files a domain publishes for mail (such as an MTA-STS policy) and, at most, greet a mail server; they never deliver a message.
• “Could not check” is an honest answer. When a server does not reply, we say so instead of guessing a pass or a fail.
• Rules from the standards. Our rules come from the published standards, and findings link to the section of the standard they rely on, or to the provider's own documentation when the advice is about one provider. How that works is on the methodology page.

The checks run on our own engine, which uses these open-source libraries among others: mailauth (email authentication), dns-packet (DNS messages), nodemailer (mail server greetings), tldts (domain names), fflate and sax (reading DMARC report files), ipaddr.js (IP addresses) and undici (HTTPS). The site is made with Next.js and React. Thank you to their authors.

Write to [email protected]. If a result looks wrong, attach the downloaded evidence file: it holds exactly what our server saw. The link to the result page helps too, but opening it later runs the check again, against what DNS and the servers answer then.