Spam Score Checkers: What They Measure and What's Useful

Spam score checkers are the most-used and most-misunderstood category of deliverability tool. Senders run a message through Mail-Tester, get a 9.5/10, and assume their email will land in inbox. Then it lands in spam at Gmail and they wonder why. The score measures real things — but not the things that determine inbox placement at modern ISPs.

This guide covers what the major checkers actually test, what to use them for, and what they miss.

What spam score checkers measure

Every checker runs some combination of:

1. SpamAssassin rules — open-source content classifier with hundreds of rules (subject line patterns, HTML/text ratio, specific phrases, image-heavy content, etc.)
2. Authentication validation — SPF, DKIM, DMARC pass/fail and alignment
3. Blocklist lookups — sending IP and domain against Spamhaus, Barracuda, SORBS, others
4. HTML/CSS validation — image-to-text ratio, file size, broken tags
5. Content scans — URL reputation, attachment scanning, MIME issues
6. Header analysis — Message-ID format, Date validity, missing required headers

Some add:

7. Inbox placement testing — sends to seed addresses at major ISPs and reports where each landed
8. Sender reputation lookups — Sender Score, Talos, Google Postmaster data

The first six produce a score. The last two produce more useful data.

The major checkers

Mail-Tester

Free for occasional use. Send your email to a generated address ([email protected]), get a 0-10 score in 30 seconds. Breaks down: authentication, SpamAssassin score, blocklist hits, HTML/MIME issues.

Strengths: zero friction, catches obvious technical issues, free.

Limits: single-checker, no inbox placement test, no engagement modeling.

Best use: pre-send sanity check for new campaigns or after infrastructure changes.

GlockApps

Paid. Sends to a real seed list at Gmail, Outlook, Yahoo, AOL, Apple Mail, ProtonMail, etc. Reports where each message landed (inbox / tabs / spam / blocked). Adds spam analyzer, content checks, blocklist monitoring.

Strengths: actual inbox placement data across major ISPs, broader reputation monitoring.

Limits: seed-list testing differs from real-user placement (seed mailboxes have no engagement history). Expensive at scale.

Best use: pre-launch campaign testing, ongoing inbox-placement tracking.

Mailgenius

Free tier. Focused on authentication, deliverability score, and content checks. Lighter than Mail-Tester on SpamAssassin depth but stronger on authentication reporting.

Best use: quick authentication sanity checks.

Mailhardener

Authentication-focused (SPF, DKIM, DMARC monitoring, MTA-STS, TLS reporting). Not a content spam scorer — does the deliverability-foundation checks deeply. See our Mailhardener review.

Best use: authentication monitoring, not content scoring.

SpamAssassin direct

Open-source, free to install and run yourself. Most checkers wrap it. If you want to know which specific rules your email triggers, run SpamAssassin locally with spamassassin -t < message.eml and read the report directly.

What spam scores get right

Configuration issues. If your SPF is broken, DKIM is missing, IP is on Spamhaus SBL, or HTML is malformed, every spam score checker will catch it. Use them as a regression test:

• After domain migration → run a check
• After ESP change → run a check
• After template redesign → run a check
• Before a major campaign → run a check

Catching a broken DKIM signature pre-send saves a campaign. That's worth the 30 seconds.

Practitioner note: The single most common Mail-Tester failure I see in client audits is missing DKIM. The ESP set up DKIM during onboarding, but the DNS record was never published or got dropped during a DNS provider migration. Mail-Tester catches it instantly. The client has been sending for months without authentication and wondering why open rates are terrible.

What spam scores miss

Engagement-based filtering. Gmail and Outlook use historical engagement (your domain's open rate, complaint rate, deletion-without-opening rate) more heavily than content scoring. A 10/10 Mail-Tester message can still land in spam if your sender reputation is bad. Conversely, a 7/10 message from a trusted sender lands in inbox.

ISP-specific signals. Gmail's filtering uses signals SpamAssassin doesn't model. Outlook's filtering uses signals neither model. A high SpamAssassin score doesn't translate 1:1 to good placement.

Subscriber-specific filtering. Per-recipient signals (prior interaction with your sender, folder rules, contact list inclusion) override most content scoring.

Recent reputation changes. Reputation data on most checkers updates daily or slower. A recent blocklist removal might not show as resolved for 24-48 hours.

How to read a spam score checker output

Score component	What to do
SPF / DKIM / DMARC fail	Fix immediately — this is a hard delivery blocker
Blocklist hit (Spamhaus, Barracuda)	Investigate why; request delisting
SpamAssassin score > 5	Review specific rule triggers; usually content or formatting
Image-only email warning	Add text content; image-only emails are downgraded
Missing List-Unsubscribe header	Required for bulk senders per Gmail/Yahoo rules
Broken HTML	Fix; some clients render badly
Inbox placement < 70% (GlockApps)	Sender reputation issue; not content
Authentication score 10/10 but real inbox rate low	Engagement reputation problem; checker can't see this

The last row is the gap: passing all checker tests does not guarantee inbox placement.

What to use instead (or alongside)

For engagement-based reputation monitoring, you need real ISP-side data:

• Google Postmaster Tools — Gmail's data on your domain reputation, spam rate, authentication. Free. See Google Postmaster Tools guide.
• Microsoft SNDS — Outlook/Hotmail-side data on your IP reputation, complaint rates. Free. See Microsoft SNDS guide.
• Your ESP's reputation dashboard — most ESPs surface engagement metrics that predict placement better than spam scores.

Practitioner note: Spam score checkers are useful for catching configuration regressions. They are not useful for diagnosing "my email is going to spam." For that, you need Postmaster Tools data, SNDS, and a review of your engagement history. Spending time optimizing a 9.5/10 to 10/10 on Mail-Tester while ignoring a declining domain reputation in Postmaster Tools is a common waste of effort.

The workflow that actually works

1. Pre-send: run Mail-Tester for configuration check
2. Pre-launch: run GlockApps for inbox placement signal
3. Ongoing: monitor Google Postmaster Tools daily
4. Ongoing: monitor SNDS for Microsoft properties
5. Investigation: when placement drops, check authentication, then reputation, then engagement metrics — in that order

For broader deliverability context see email deliverability guide and why emails go to spam.

If you need help interpreting spam score results, designing inbox-placement monitoring, or diagnosing why high-scoring emails still land in spam, book a consultation. I run deliverability audits that combine these tools with ISP-side reputation data.

Sources

• Apache SpamAssassin: Rules and Scoring
• Google Postmaster Tools Documentation
• Microsoft SNDS Documentation
• RFC 7489 — DMARC
• Mail-Tester: How It Works
• M3AAWG Sender Best Common Practices

---

v1.0 · May 2026