Back
Test Spam Mail: The 20-Minute Check That Tells You If Your Email Lands in Spam

Test Spam Mail: The 20-Minute Check That Tells You If Your Email Lands in Spam

Sophia Bennett
Written by Sophia Bennett Privacy Researcher & Software Developer
Fact-Checked Nov 18, 2026 19 Views
Share article:
TempoMail USA App Get OTPs faster on the app!
Get the App
Advertisement

There is a special kind of silence in email. You send a newsletter, a quote, a password reset, and nothing comes back. No bounce, no error, no angry reply. The message simply never arrives, and the person on the other end assumes you forgot. The first time it happens to something you care about, you learn the lesson every sender eventually learns: delivery is not a yes-or-no event. Your mail can be accepted by the server, pass every check, and still end up in a spam folder nobody opens. The only way to know is to test — and the test takes about twenty minutes, costs nothing, and tells you more about your sending setup than a month of guessing.

I set up both ends of that test myself for this guide: a disposable inbox to receive with, and a score-test address to send to. I did not send a test email from a production mailbox, because I do not have one to send from, and I am not going to pretend I did. What I did do is verify every step you have to take before the send, live, today — the addresses, the limits, the exact wording on the pages — so that when you run the send yourself, nothing in the setup surprises you. The send itself is yours. Everything around it is checked.

First, What a Spam Test Actually Measures

"Test spam mail" is one search phrase with three different jobs behind it, and the guides ranking for it tend to answer only one of them. Sorting out which job is yours matters, because each one needs a different tool and each one can pass while the others fail.

The first job is the score test. You send your message to a test address, and a tool reads what arrived and grades it: authentication, content, blacklists, formatting. Mail-Tester is the classic version. The output is a number out of ten and a list of findings. It answers the question "does this message look like spam to a filter?"

The second job is the placement test. You send the same message to test inboxes you control at Gmail, Outlook and Yahoo, and you look at where each copy actually lands: Primary, Promotions, or Spam. A placement test answers the question the score test cannot: "did it actually arrive where a human will see it?" A message can score 10 out of 10 and still land in Promotions, which for most readers is nearly as invisible as spam.

The third job is the reception test. You send a message to an inbox and confirm it arrives at all, quickly, readable, with its links intact. This is the test developers run against signup and login flows, and it is the one where a temporary inbox earns its keep — a fresh address per test run, no real mailbox burned. Our guide to testing OTP codes three ways runs this version of the test in full, including the failure that taught the most.

My opinion, stated up front: run the score test and the placement test together, in that order, and treat the score as a diagnostic, not a verdict. A score tells you what is wrong. Placement tells you whether it matters. A sender who only runs one of them is flying with one instrument covered.

The 20-Minute Protocol

Advertisement

Here is the whole routine, timed. Twenty minutes the first time, closer to ten once you have done it twice. Do the steps in order — there is no point tuning your subject line on a domain that fails authentication.

Minutes 0–2: Set Up the Receiving End

Start with the inbox you will receive into. For a spam test, the receiving end should be clean: no contact entry for the sender, no history of opening that sender's mail, no filters, no prior trust. A disposable inbox is the cleanest version of that, because it has literally never seen your mail before.

I opened TempoMailUSA's homepage and the page generated an address the moment it loaded — no signup, no verification step of its own. The address it served in this browser was artextest42@rover.info. That is the same address an earlier test in this browser got, which tells you something useful: the homepage keeps a persistent address per browser rather than minting a fresh one on every visit. If you want a genuinely fresh receiving address for a test, use the Refresh or New Inbox control rather than assuming a reload gives you a new one. The inbox loaded empty — "Your inbox is empty", zero messages, auto-refreshing — with 29 days and 14 hours left on the clock. Free inboxes last 30 days; the page says Pro inboxes last 365 days.

One honest caveat, because it is printed on the page and it changes what the free tier can do for you: "Try any of our 427 domains free — your first message is free to read. Go Pro to read every message." For a single test message, the free tier is enough. For a repeated test routine, read that line before you build a workflow around it. And if you want to compare disposable services before settling on one, our roundup of temp mail websites tested nine of them live rather than listing them.

A laptop showing an empty temporary email inbox waiting for a test message

Minutes 2–5: Get Your Score Address

Next, the score test. Open Mail-Tester and it hands you a test address with no account and no sign-in: when I checked today it generated test-3pb41yhml@srv1.mail-tester.com, shown under "First, send your email to:", with a copy icon and a single button below it, "Then check your score". The format is always the same shape — test- plus a random ten-character string at srv1.mail-tester.com.

Read the limits before you spend them. Mail-Tester's own FAQ, which I read today, says you get 3 free tests within 24 hours, results stay accessible for 7 days on the free version and 30 days with an account, and the goal is a perfect 10 out of 10. The score runs on a vanilla installation of SpamAssassin — the open-source spam filter — with the score reversed so a positive number is good and a negative one is bad. That detail matters when you read the report: a rule that dings you is a real SpamAssassin rule, not a Mail-Tester invention. What the homepage does not say, and the FAQ confirms by omission, is that SPF, DKIM and DMARC are not part of the score itself — they live in separate free checker tools linked in the footer. The score judges the message; the authentication verdict comes from reading the headers, which is the next step.

Minutes 5–10: Send the Real Thing, Not a Stub

This is the step where most tests quietly become useless. A test is only useful if it matches reality, so send the message exactly as you plan to send it in production: the same sending system, the same From address and domain, the same subject line, the same links, the same template, the same images. A two-line "test test" message tells you nothing about the newsletter you are about to send, because the content is half of what the filter judges.

Send to both addresses you just set up — the Mail-Tester address and your temp inbox — from the real system. If you send from your personal Gmail to test a newsletter tool, you have tested Gmail, not the tool. If you send a plain-text stub to test a designed template, you have tested the stub. And send once per test: repeated sends from the same system inside a few minutes start to look like a burst, and bursts are exactly what reputation systems watch for.

Give it a few minutes. Mail is not instant, and a score checked thirty seconds after sending can read as missing mail rather than failed mail. While you wait, do the one check that needs no tool at all — the next step.

Minutes 10–15: Read the Score Like a Technician

Click "Then check your score" and read the report from the top, but read it the way a technician reads it: the individual findings matter more than the number. A 9 out of 10 with one failed authentication check is a worse result than a 7 out of 10 with clean authentication and a ding for a spammy phrase, because the first one can get your mail rejected outright while the second one just needs an edit.

Start with authentication. You do not need a tool to see whether it worked: send a message to a Gmail address you control, open it, choose "Show original", and near the top you will see SPF, DKIM and DMARC each marked PASS or FAIL, with the sending IP. The three records do different jobs. SPF says the sending server is allowed to send for your domain. DKIM says the message was not altered after signing. DMARC says what to do when either of those fails, and ties the result to the domain in your From address rather than the domain in the envelope. A DMARC policy of p=none — which is what this site's own domain currently has, I checked it today with a DNS lookup: v=DMARC1; p=none; — means "report only, take no action". That is a monitoring policy, not an enforcement policy, and a domain running p=none is telling receivers to deliver mail even when authentication fails. If your own domain is on p=none, the score will not flag it, but the placement test might.

The DNS lookup also returned this site's SPF record verbatim: v=spf1 ip4:95.217.58.48 +a +mx ~all. Read it as a sentence: this domain's mail comes from that one IP, plus its own A and MX records, and anything else should be treated as suspicious (the ~all soft-fail). If your SPF record has more than ten DNS lookups in its chain, it breaks — SPF's ten-lookup limit is the single most common silent authentication failure, and it produces no error message anywhere.

Advertisement

Then the content findings. SpamAssassin flags patterns: ALL-CAPS subjects, too many images relative to text, URL shorteners, a mismatch between the link text and the link destination, missing List-Unsubscribe headers. Fix one group at a time and retest, so you know which change moved the score. Change everything at once and you learn nothing.

Then blacklists. If your sending IP or domain is on a major blocklist — Spamhaus, SURBL, Barracuda are the ones Mail-Tester checks — that is the finding to fix first, before content, because no amount of copy editing outranks a blacklist listing. And if your test mail disappears entirely — not in the inbox, not in spam, nowhere — Mail-Tester's own FAQ says the most probable cause is that your sending server is blacklisted.

Hands holding a phone showing an email deliverability report with green checkmarks

Minutes 15–20: The Placement Check the Score Can't Do

A score predicts. Placement confirms. Set up one free test account each at Gmail, Outlook.com and Yahoo Mail, used only for testing, and send the real message to all three from the real system. Check every tab and every folder in each one: Gmail's Primary and Promotions tabs (plus Social, Updates or Forums if they are turned on), Outlook's Focused and Other tabs, Yahoo's inbox. Spam lives in Gmail's Spam folder under More, in Outlook's Junk Email folder, and in Yahoo's Spam folder.

Two rules that feel wrong and matter enormously. First, do not save the sender as a contact in your test accounts. Gmail stops sending a sender's mail to spam once the sender is in the person's contacts, which hides exactly the result you are trying to see. Second, if a test message lands in spam, leave it there and write it down. Do not click "Not spam" — that teaches the inbox to trust you, so your next test will not show the real picture. For the same reason, never click "Report spam" on a test message; providers treat it as a complaint against you. And skip your colleagues as testers: inside a Google Workspace domain an admin can set internal mail to skip the spam filter, and your colleagues probably have you saved as a contact anyway.

Write down the result per provider. "Gmail Primary, Outlook Other, Yahoo Spam" is a finding. "It went to spam" is not — it hides which provider, and the fix is different for each one. Gmail's bulk sender rules, published by Google, require SPF, DKIM and DMARC for anyone sending 5,000 or more messages a day to Gmail addresses, and Google watches the spam rate those senders generate. If your mail is spam at Gmail only, the cause is usually reputation or engagement, not content. If it is spam everywhere, start with authentication.

The Three Results That Matter — and the Fix for Each

Most test reports reduce to one of three findings, and each one points at a different layer. Learn to tell them apart and you stop fixing the wrong thing.

  1. Authentication fails. SPF, DKIM or DMARC does not pass, or passes for the wrong domain. Fix the DNS records first — publish SPF with the sending service's include, publish the DKIM key the service gave you, and move DMARC from p=none toward p=quarantine only after you have watched the reports and confirmed legitimate mail passes. Retest with a fresh send; DNS changes can take an hour to be visible everywhere.
  2. A blacklist listing. Your domain, sending IP or a linked domain appears on a blocklist. Delist through the list's own process, then find out why you were listed — usually a burst of volume, a compromised account, or a shared IP with a bad neighbour. Moving to a dedicated sending IP is the durable fix, not retesting until the listing ages off.
  3. Content or links. The message itself trips rules: spammy phrasing, image-heavy HTML, URL shorteners, tracking domains with poor reputations. Send two versions to the same test addresses — a plain two-sentence version and the real version — and compare. If the plain version lands in the inbox and the real one does not, the problem is in the message, and the score report's line-by-line findings tell you which lines.

Our earlier guide to checking your email spam score walks the same three findings from the score side, step by step. This guide exists to add the part that one leaves out: the placement check that confirms whether the score was telling the truth.

Why a Temp Inbox Is the Cleanest Receiving End

There is a reason the receiving end of this test works best as a disposable inbox rather than your own address. Your own inbox is contaminated as a test instrument: you have the sender saved, or you have opened their mail before, or a filter already routes it. A temp inbox has none of that. It is a neutral receiver with no history, no contacts, no engagement record — the closest thing to a stranger's inbox you can get without actually sending to a stranger.

That neutrality cuts both ways, and you should know the edge before you lean on it. A disposable domain is itself a signal. When we tested disposable addresses against real signup forms, the big newsletter platforms rejected them outright — the forms ran domain checks before accepting the address, and no confirmation was ever sent. The full test, with the verbatim error messages, is in our guide to spam email signups. For a spam test that distinction mostly does not matter, because you are the sender and you choose the receiving address. But it is the same reason a temp inbox is a good test receiver and a bad account address: it is clean precisely because nothing trusts it yet.

The other limit is time. A free temp inbox here lasts 30 days, and the first message is free to read. A test routine that runs weekly needs an inbox that still exists next week — save the address, and if the service offers a recovery token, save that too. An inbox you cannot get back into is not a test instrument; it is a one-off.

When to Test Again

A spam test is a snapshot, not a certificate. Retest whenever anything in the chain changes: you change your sending tool or SMTP service, you edit your DNS records, you redesign the template, you add a new link domain, or your sending volume jumps. The most common story in deliverability is a sender who tested once, changed three things, and then spent a week blaming the wrong one.

Retest on a schedule even when nothing changes. Reputation drifts. A domain that passed in January can be listed in March because a shared IP picked up a bad neighbour, and the first sign is usually a quiet drop in replies rather than an error message. Ten minutes, once a month, with the same protocol, catches that drift while it is still cheap to fix. Keep the results in a note — date, score, placement per provider — because the trend across months is worth more than any single score. A score of 8 that has been an 8 for six months is a stable system. A score that fell from 10 to 7 is a story, and the story is usually in the one thing that changed since the last test.

Frequently Asked Questions

How do I test if my email goes to spam?

Send the real message to a test address from a spam-testing tool and to test inboxes at Gmail, Outlook and Yahoo. Read the score report, check where each copy landed, and read the authentication results in the message headers. The score alone is not the answer; placement is.

What is a good Mail-Tester score?

The goal is 10 out of 10, per Mail-Tester's own FAQ. In practice, treat the number as a summary and the findings as the work: a 9 with a failed authentication check is worse than a 7 with clean authentication and a content ding, because the first can get mail rejected outright.

Can I use a temp email to test spam mail?

Yes — as the receiving end. Generate a disposable address, send your real message to it from the system you actually use, and watch whether it arrives, where it lands, and what the headers say. Do not use it as the sending address for a deliverability test unless that is genuinely how you send.

Why did my email go to spam if the score was perfect?

Because a score tests one message against one filter, and placement is decided by reputation, history and recipient behaviour on top of that. A perfect score with a new domain, a sudden volume spike, or a list full of addresses that never open anything will still land in spam. Run the placement test to see it, and check your sender reputation in Google Postmaster Tools.

How often should I test spam mail?

Before every major send, after any change to DNS, template, sending tool or volume, and once a month on a schedule even when nothing changed. Each run takes about twenty minutes the first time and ten once the routine is set.

The test is not there to make you feel good about your mail. It is there to catch the silent failure before your readers do — the message that was accepted, scored, filtered, and never seen. Twenty minutes, two free addresses, and a written-down result per provider is the whole cost. The senders who skip it are the ones who find out about the problem from the person who never got the email, which is the most expensive way to learn it.

Need a disposable temporary email?

Protect your real inbox from spam and promotional clutter instantly and free.

Generate Now

Received a suspicious email, text, or charge alert?

Verify whether the sender domain is disposable, spoofed, or unverified before clicking links.

Verify Email Sender

Take TempoMail USA anywhere

Faster OTPs, instant push notifications, and offline inbox access — free on Android.

Get it on Google Play
Advertisement

Join the Conversation 0

Join the discussion

Log in to share your thoughts, ask questions, and reply to others.

Log In or Sign Up

Be the first to share your thoughts on this article!