About the Mail Tester
This tool tests an email you actually send. Generate a one-time throwaway address, send a message to it from the system you want to check, and within seconds you get a deliverability score out of 10 plus a breakdown of what is wrong. Because it analyses the real message, it can verify the actual SPF, DKIM and DMARC results (not just whether the DNS records exist), read the spam-filter score and rules the message triggered, check the sending IP's reverse DNS and blacklist status, and flag content problems like a missing plain-text part or List-Unsubscribe header.
It is the way to answer "why is my mail going to spam?" with evidence from a genuine send, rather than guessing from DNS alone. Use the companion mail-deliverability checker first to fix the domain's records, then send a test here to confirm a real message passes. Each test address is single-use and the result is discarded after a short time, so do not send anything sensitive.
How to use it
- Click to generate a one-time test address.
- Send a real email to that address from the mail system you want to test.
- The page updates automatically when the message arrives.
- Read the score and work through the highest-severity issues first.
Examples
- Find out why your newsletter lands in the spam folder.
- Confirm a new sending domain passes SPF, DKIM and DMARC on a real message.
- Check the spam score of a transactional email before rolling it out.
- Verify your mail server's IP is not blacklisted from an actual send.
Frequently asked questions
How is this different from the mail deliverability checker?
The deliverability checker inspects a domain's DNS records (MX, SPF, DMARC, DKIM) without any email being sent. This mail tester analyses a real message you send, so it can confirm the actual SPF/DKIM/DMARC results, the spam-filter score, and the sending IP's reputation. Use the checker to fix the setup, then this to prove a real message passes.
Who calculates the spam score?
The receiving mail server runs the message through its spam filter (the same rspamd/SpamAssassin-style engine used in production mail) and reports the score and the rules it triggered. We combine that with the message's authentication results and the sending IP's blacklist and reverse-DNS status into a single grade.
Is my email stored?
No. The message is received, analysed and discarded. Only the live result is held in memory and it expires after 30 minutes. Each test address is single-use. Treat it as a public test target and do not send confidential content.
Why is DKIM shown as fail or none here but the domain looks fine?
This checks the signature on the message you actually sent. If your sending system did not sign the message, used a key that does not match the published DKIM record, or modified the body after signing, DKIM will fail here even though the DNS record exists. That is exactly the kind of problem only a real send reveals.
What is a good score?
Higher is better, out of 10. A clean message from a well-configured sender with passing SPF, DKIM and DMARC, good reverse DNS and a low spam score lands at an A. Failed authentication, a blacklisted IP or spam-triggering content pull the score down, and each issue is listed so you know what to fix.
The address did not receive my email — what now?
Give it a moment; delivery and analysis usually complete within seconds but can take longer. Make sure you sent to the exact address shown, including the unique token. Keep the tab open so the page can update when the message arrives.