Stockio

Mail Tester: Check Your Email Spam Score for Free

Mail-Tester gives your email a score out of 10 and lists what spam filters will dislike, from missing SPF and DKIM to broken links. Here is how to use it.

By Ravi Desai

DevOps & Security Engineer ·

On this page

Your newsletter, invoice or password-reset email can be perfectly written and still land in spam. Usually the reason is technical: a missing DNS record, a sending server on a blocklist, or HTML that looks like a phishing template. A mail tester shows you those problems before your readers do, and Mail-Tester is one of the simplest ways to get a clear answer.

How Mail-Tester works

The idea is clever and quick. Instead of pasting your email into a form, you send a real message to a unique address the site gives you. Because the message travels through your actual mail server, the test sees exactly what Gmail, Outlook or Yahoo would see: the sending IP, the authentication results, the headers and the content.

When you click to check your score, the site returns a mark out of 10 along with a breakdown of what added or removed points. A spam score of 9 or 10 means the message is in good shape. Anything lower comes with a list of specific fixes.

Running your first test

  1. Open the Mail-Tester home page and copy the one-time address it shows.
  2. Send your email to that address from the system you really use: your email client, your newsletter platform, your web app or your contact form.
  3. Wait a few seconds, then click the button to see your result.

Send the real thing, not a one-line "test" message. A short message with no content is scored differently from a full newsletter with images, links and an unsubscribe footer, so a toy test tells you little. The free version allows a limited number of tests per day, which is plenty for checking a template; paid plans and an API exist for teams that test constantly.

What the report checks

The results page is split into sections you can expand one at a time. The most important ones are:

  • Authentication. Whether your message passes SPF, DKIM and DMARC. These DNS records prove your domain allowed this server to send mail. Missing or failing records are the most common reason for a low mark.
  • SpamAssassin rules. SpamAssassin is a widely used open-source filter. The report lists every rule your message triggered, such as too many images, shouting in capitals or suspicious phrases, and how many points each cost.
  • Blocklists. Whether your sending IP or domain appears on public blocklists that many providers consult.
  • Formatting. Whether the HTML has a plain-text version, whether images have alt text, and whether the message looks like a well-built email rather than a hastily pasted web page.
  • Broken links. Whether the links in the message actually work.

Fixing the usual problems

Most low scores come down to a handful of fixes:

  • Publish SPF and DKIM. Your email or newsletter provider gives you the exact records to add at your DNS host. Add both, then re-test.
  • Add a DMARC record, even a relaxed one that only asks for reports. Large mailbox providers increasingly expect bulk senders to have one.
  • Send from your own domain. Sending as a free webmail address through a third-party service fails authentication by design.
  • Include a plain-text part and keep the ratio of text to images sensible. A newsletter that is one big picture looks like spam to filters.
  • Avoid link shorteners and make sure every link points somewhere real.

Change one thing at a time and send a fresh test after each fix, so you know what actually moved the score.

A good score is not a guarantee

A 10 out of 10 means your setup is technically sound. It does not guarantee the inbox, because large providers also weigh your history: how many people open your messages, mark them as spam or delete them unread. A perfect setup sent to a stale list can still be filtered.

Treat Mail-Tester as a checklist for things you control. Pair it with good list habits: only email people who asked for it, remove addresses that bounce, and make unsubscribing easy. If you are worried about recognizing the opposite side of this problem, our guide on spotting a phishing email in 30 seconds shows what filters are trying to catch.

When to use it

Run a test whenever something changes: a new email provider, a new newsletter template, a new domain, or a new transactional email from your app. It is also worth testing before a big send, such as a product launch, so a missing record does not cost you half your audience.

Mail-Tester also lists a set of free single-purpose checkers for SPF, DKIM, DMARC and BIMI records, which are handy when you want to confirm one DNS change without sending a full message.

The bottom line

Mail-Tester turns a vague worry, "are my emails going to spam?", into a numbered list of fixes. Send it the real email, read the authentication section first, fix the records, and re-test until you see a score you are happy with.

Featured sponsor

Reach designers & developers at work

Put your product next to the tools people use every day. One sponsor per placement.

Become a sponsor