Email spam test: how to check your spam score and fix what it finds
TL;DR: An email spam test sends a message to a test address, then reports how spam filters are likely to judge it. It checks authentication (SPF, DKIM, DMARC), whether your sending IP or domain is on blocklists, the message headers and the content. Run one by sending a real message from the exact system you plan to use, read each failed check, fix authentication first and send a second test. Treat the score as a guide, because it cannot predict how Gmail or Outlook will treat you, so confirm with a real inbox test and check your headers for authentication results.
What a spam test checks
Spam testing tools give you a temporary address. You send a message to it, and the tool analyses what arrived. A typical report includes:
- Authentication. Whether SPF, DKIM and DMARC pass and align with your From domain.
- Server and DNS setup. Reverse DNS, whether the sending hostname resolves and whether the IP is configured sensibly.
- Blocklists. Whether your sending IP or links appear on well-known spam lists.
- Headers. Missing or odd headers, a missing Message-ID or date, a strange From or Reply-To.
- Content. Spam-like wording, shouting in capitals, heavy punctuation, hidden text, link shorteners and image-only messages.
- HTML quality. Broken markup, huge images with little text and a missing plain-text version.
- Unsubscribe handling. For bulk mail, whether a clear unsubscribe link or header exists.
The result is often a score out of 10 or a list of passed and failed checks. A higher score is better, but the individual findings matter more than the number.
How to run a proper test
A test is only useful if it matches reality.
- Send from the real system. Test through the same mailbox, SMTP service or marketing platform you will use. A test from your personal Gmail tells you nothing about your newsletter tool.
- Use the real From address and domain. Test the exact sender you will use in production.
- Use realistic content. A test with "hello" does not reveal content problems. Paste in the actual subject, body, links and images.
- Send to the test address shown by the tool, then open the report.
- Fix, then retest. Change one group of things at a time, so you know what worked.
- Repeat from each sending system. Your mailbox, website, store and newsletter tool may each behave differently.
If you run several senders, make a short checklist and test each one after any DNS change.
Read the headers yourself
You do not need a tool to see whether authentication worked. Send a message to a Gmail address you control, then open it and choose Show original. Near the top you will see something like:
SPF: PASS with IP 203.0.113.10
DKIM: 'PASS' with domain example.com
DMARC: 'PASS'
Also look at the Authentication-Results header in the raw message, which shows the same checks in text form. Things to confirm:
- SPF passes, and the domain checked matches your From domain, or is aligned with it.
- DKIM passes, and the
d=domain matches your From domain. - DMARC passes.
If any shows FAIL, SOFTFAIL or NEUTRAL, fix that before you worry about wording. For DKIM details, see how to find your DKIM selector.
What the results mean
| Finding | What it usually means | What to do |
|---|---|---|
| SPF fail or softfail | The sending server is not in your SPF record | Add it. See how to create an SPF record |
| SPF permerror | Too many lookups or two records | Simplify. See SPF too many lookups |
| DKIM missing or fail | Signing not enabled, wrong selector or record | Publish and enable DKIM |
| DMARC fail | SPF or DKIM passes but does not align with the From domain | Align the sending domain |
| Listed on a blocklist | Sending IP or domain has a bad reputation | Request delisting and fix the cause |
| No reverse DNS | The IP has no matching PTR record | Ask your provider. See reverse DNS |
| Content flags | Spam-like phrases or poor HTML | Edit the message |
| Missing plain-text part | HTML-only message | Add a text version |
Fix authentication first
Authentication problems affect every message you send, while content problems affect one. Start here.
- Confirm SPF includes every sender and stays within the lookup limit.
- Confirm DKIM is on for every sender and passes.
- Publish a DMARC record, starting with
p=noneto collect reports, then tightening carefully. See DMARC without breaking forwarding. - Make sure the visible From domain aligns with the SPF or DKIM domain.
Large mailbox providers now expect proper authentication from everyone who sends mail, and much more strictly from bulk senders. Our guide to Gmail's 2026 spam rules for cold email explains what changed, and OTP emails landing in spam covers a common transactional case.
Content and formatting fixes
Once authentication is clean, improve the message.
- Write a clear, honest subject. Avoid all capitals, many exclamation marks and misleading "Re:" prefixes.
- Keep a good text-to-image ratio. Do not send a single large image as the whole email.
- Use a plain-text alternative alongside the HTML.
- Limit links, use your own domain for links, and avoid link shorteners.
- Match the visible link text with the real link. Mismatches look like phishing.
- Avoid attachments in bulk mail, especially executables and archives.
- Include a clear unsubscribe option in marketing mail, plus the proper header where your platform supports it.
- Put your name, address and business details in the footer of marketing email.
- Keep HTML clean, with no hidden text and no broken tags.
Reputation and blocklists
Even perfect content struggles on a bad reputation.
- Check your sending IP and domain on public blocklist lookup tools. If you are listed, find out why, then follow the list's delisting process.
- On shared servers, other customers' behaviour can damage a shared IP. A dedicated or transactional sending service isolates you.
- Warm up new senders. A brand-new domain or IP that suddenly sends thousands of messages looks suspicious. Increase volume gradually.
- Clean your lists. Remove bounces, long-inactive addresses and anything you did not collect with consent.
- Watch complaint rates. If many recipients mark your mail as spam, your reputation falls fast.
- Use mailbox-provider tools such as Google's Postmaster Tools, if your volume qualifies, to see reputation and spam-rate data for your domain.
Testing inbox placement
A spam test predicts. Actual placement confirms. To check where mail lands:
- Create test accounts at the providers your customers use: Gmail, Outlook, Yahoo and any business mail system.
- Send the real message to each.
- Check whether it lands in the inbox, in the promotions tab or in spam.
- If it lands in spam, open the message and read why, where the provider gives a reason.
Do this before any big campaign, and again after changes to your DNS or sending service.
What a spam test cannot tell you
- How a specific provider will treat you. Gmail, Outlook and others use their own models and your own history with their users.
- Engagement. Mailbox providers weigh whether recipients open, reply and delete without reading.
- Your long-term reputation. A test is a snapshot.
- Whether a free tool's scoring matches current filters. Rules change, and different tools weigh things differently, so a perfect score does not guarantee the inbox.
Use the score to catch obvious problems, not as proof of delivery.
FAQs
What is an email spam test?
A tool or process that checks how likely your email is to be treated as spam, based on authentication, reputation, headers and content.
What is a good spam score?
It depends on the tool. Generally, a high score on a 10-point scale with all authentication checks passing is good. The individual failures matter more than the total.
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 report and check where each message lands.
Why do my emails go to spam even with SPF and DKIM?
Reputation, content, missing DMARC alignment, high complaint rates or a shared IP with a poor history can still cause it.
Does a perfect spam score guarantee inbox placement?
No. It means no obvious problems were found. Providers still decide using reputation and recipient behaviour.
How often should I test?
After any change to DNS, sending services or templates, and before large campaigns.
Can I test spam without sending to a tool?
Yes. Send to your own Gmail account and open Show original to see the SPF, DKIM and DMARC results.
Do I need DMARC to pass a spam test?
It is strongly recommended. Many tests flag a missing DMARC record, and large providers now expect it from bulk senders.
Conclusion
A good spam test is a short routine: send from the real system, read the authentication results, fix SPF, DKIM and DMARC first, clean up content, check reputation and then confirm with real inboxes. Do it before every important send, and your messages are far more likely to be read.
HostCloud's email hosting and DNS tools help you build a setup that passes these checks. See https://hostcloud.in.
Sources: