Mail-Tester for Cold Email: How to Score 10/10 (and Why Cold Email Needs More)

Mail-tester.com is the most popular free email deliverability scoring tool on the internet — they get over 60,000 monthly searches just on their brand name. Score out of 10 in 30 seconds. Free, no signup, instant feedback.

For cold email, it's a useful first-pass check but not a sufficient one. Mail-tester catches obvious DNS, authentication, and content-pattern errors. It doesn't catch the issues that actually determine whether cold email lands in primary inbox vs spam at scale — IP reputation, domain reputation history, real-world inbox placement across multiple receivers.

This guide is the cold-email-specific reading of mail-tester: how to interpret the score, what each deduction category means, what mail-tester misses, and how to fill those gaps.

The 30-second answer

Mail-tester scores your email out of 10 based on roughly 7 categories:

Mail-tester check	What it tests	Cold email relevance
SpamAssassin score	Content-pattern spam triggers	Useful — catches obvious spam-like copy
SPF record valid	Sending IP authorized for domain	Critical
DKIM signature valid	Cryptographic signature verifies	Critical
DMARC policy present	Domain has DMARC published	Critical
From address legit	Visible sender, reverse DNS, etc.	Important
Message content quality	HTML structure, image-text ratio	Mostly marketing-email signal
Body links checked against blocklists	Domain reputation of linked URLs	Useful

Target score for cold email: 9.5/10 or higher. Anything below 9 has something fixable.

Run mail-tester, or use ColdRelay's free deliverability test which runs the same DNS checks plus blocklist scanning across 6 major DNSBLs.

How mail-tester actually works

Three steps:

You visit mail-tester.com. They generate a unique random email address (e.g., test-abc123@srv1.mail-tester.com).
You send your cold email — from the actual mailbox and sending setup you'd use in production — to that address.
You go back to the mail-tester page and see your score plus a per-category breakdown.

The test runs in the background on their server. They check the headers of the message you sent, run SpamAssassin against the body, query DNS for SPF/DKIM/DMARC on your sending domain, look up the From address's PTR record, and check any URLs in the body against their list of known spam-affiliated domains.

The output is a 10-point score with per-category deductions explained line-by-line. Each deduction is actionable — you know exactly what to fix.

Reading the score for cold email

9.5–10/10: solid setup

What it means: your DNS, authentication, and basic content patterns are correct. You're cleared on the obvious setup errors.

What it doesn't mean: that your cold email will inbox-place at Gmail / Outlook / Yahoo. Mail-tester confirms the setup is right; it doesn't measure reputation history or real inbox classification at major providers. A 10/10 mail-tester score with bad Postmaster Tools Domain Reputation = your mail still goes to spam.

8.0–9.5/10: minor fixable issues

What it means: one or two specific deductions. Read the breakdown — usually a single fix gets you to 9.5+.

Common single-deduction causes for cold email:

SpamAssassin: URI_HEX — your message contains a URL with a hex-encoded path. Don't use shortened URLs or hex-encoded tracking links.
SpamAssassin: HTML_FONT_LOW_CONTRAST — your HTML uses gray-on-gray text that's hard to read. Cold email should be text-first; remove the gray styling.
SpamAssassin: MISSING_HEADERS — your message is missing standard headers like Date: or Message-ID:. Common when sending via custom SMTP without a properly-configured sending tool.
DKIM not signing all messages from this domain — your sending tool's DKIM config is misaligned with what's published in DNS.

Below 8.0/10: real setup problems

Indicates multiple deductions or major failures. Common pattern:

SPF missing or ~all instead of -all
DKIM not signing at all
DMARC at p=none or absent
Multiple SpamAssassin content triggers (URL shorteners, suspicious phrases, image-heavy HTML)

For cold email, anything below 8.0 means you should fix the setup before sending real campaigns. The score below 8 reliably predicts spam-folder placement at major providers.

Common cold email mail-tester deductions and fixes

`URIBL_BLOCKED` — your link is on a blocklist

Your message contains a URL whose domain is on URI blocklist (URIBL, SURBL, or similar). Common causes:

Tracking domain that another customer also uses got listed
Shortened URL pointing to a known spam destination
Calendar link domain (Calendly, etc.) that's been flagged

Fix: replace shortened URLs with full URLs to your own domain. If your tracking domain is shared (typical of bundled-SMTP setups), move to a dedicated tracking domain.

`RDNS_NONE` — your sending IP has no reverse DNS

Receiving servers check that your sending IP has a PTR (reverse DNS) record pointing back to a hostname. Missing PTR = RDNS_NONE deduction.

Fix: configure PTR on your sending IP. ColdRelay-provisioned mailboxes have PTR records configured automatically (pointing at mail.<your-domain>).

`MISSING_HEADERS` — message lacks standard SMTP headers

Your sending tool isn't including all the standard headers (Date:, Message-ID:, MIME-Version:, etc.). Usually a tool-configuration issue, not a sending-setup issue.

Fix: configure your sending tool to add the missing headers. Most modern sending platforms (Instantly, Smartlead, Lemlist) do this automatically; older or custom SMTP setups might miss them.

`HTML_IMAGE_RATIO_*` — too many images relative to text

Your message body is mostly images with little text. SpamAssassin reads this as marketing-email pattern.

Fix: cold email should be text-heavy with minimal or no images. If you need an image (a screenshot, a chart), keep it small and balance with substantial body text.

`BODY_8BITS` — non-ASCII characters in the body

Your message uses extended characters (em-dashes, smart quotes, accented characters) without proper encoding.

Fix: ensure your sending tool sends UTF-8 encoded with Content-Type: text/plain; charset=utf-8 header. Modern tools do this correctly by default.

What mail-tester doesn't tell you

Mail-tester is a setup checker, not an outcome checker. It misses:

1. IP reputation history. Mail-tester runs in isolation — they don't have your sending IP's historical reputation context. An IP that's been sending spam for 6 months still tests 9.5/10 if the message itself is clean.

2. Real inbox placement. Mail-tester's "score" doesn't predict whether your message will land in primary inbox at Gmail or Promotions or Spam. That depends on reputation + content classification by each receiver, neither of which mail-tester measures.

3. Per-provider variation. Gmail, Outlook, Yahoo, Apple Mail each have different spam classifiers. Mail-tester gives one score; the providers might rate you very differently.

4. Engagement signals. Replies, opens, time-spent-in-inbox — all measured by inbox providers and weighted into reputation. Mail-tester sees the single test message; it doesn't see your sending pattern over time.

5. Volume + warmup state. A brand-new domain with 100% perfect mail-tester scores will still get filtered to spam if you start sending 1,000+ messages/day from day one. Mail-tester doesn't know what volume you're sending at.

How to fill the gaps

Mail-tester catches setup errors. For everything else, you need:

Google Postmaster Tools — Gmail's own view of your reputation. Updates daily, shows Domain Reputation (High/Medium/Low/Bad), Spam Rate, Authentication pass rates. (How to read it →)

Microsoft SNDS — Outlook's equivalent. Color-coded IP reputation, complaint rate, filter classification.

Hourly blocklist monitoring — DNSBLs (Spamhaus, Barracuda, etc.) can list you anytime. Mail-tester is a one-off snapshot; you need continuous monitoring. ColdRelay's hourly DNSBL checks across 6 major lists alert on listings within an hour. (Full blocklist guide →)

Seed-list inbox placement tests — Real test sends to a panel of 70+ seed inboxes across providers. GlockApps is the gold standard; ColdRelay folds daily seed tests into the base subscription.

Bounce rate monitoring — Mail-tester doesn't see your bounce rate. Cold email's healthy bounce rate is below 1%; above 2% degrades reputation regardless of mail-tester score. (Bounce rate breakdown →)

A cold email mail-tester routine

When to use mail-tester:

Pre-launch on every new domain. Send one test, hit 9.5+/10, fix any deductions before turning on real campaigns. 5 minutes well spent.

After any sending-setup change. Switched to a new sending tool, changed mailboxes, modified SPF/DKIM — re-run mail-tester to confirm the change didn't break anything.

When debugging a placement drop. If reply rates dropped and you don't know why, mail-tester is the cheapest first check. If the score is still high, the problem isn't setup — it's reputation or content.

Not useful as ongoing monitoring. A mail-tester score doesn't change unless your setup changes. Running it weekly tells you the same thing each time. Use Postmaster Tools, SNDS, and blocklist monitoring for ongoing watch.

How ColdRelay's infrastructure shows on mail-tester

Every ColdRelay-provisioned domain passes mail-tester at 9.5+/10 out of the box. Specifically:

✓ SPF record with -all (hard fail)
✓ DKIM signing with 2048-bit RSA, signature verifies
✓ DMARC at p=quarantine, properly aligned
✓ MX record pointing at the dedicated mail server
✓ PTR record matching the sending hostname
✓ TLS on every SMTP connection
✓ Dedicated IPs (no shared-pool reputation drag)

The 0.5 deduction that occasionally appears is content-specific (a particular URL, a SpamAssassin rule on the body) — sending-setup-side we're at 10/10. (How we configure SPF/DKIM/DMARC →)

FAQ

Why is my mail-tester score 8.5 but my cold email still goes to spam?

Mail-tester catches setup errors; it doesn't measure reputation. The remaining 1.5-point deduction is fixable, but even at 10/10 you'd still hit spam if your domain reputation is Low in Postmaster Tools or your IP is on a blocklist. Check those next.

Should I run mail-tester from every mailbox or just one per domain?

One per domain is usually enough — the DNS-level checks (SPF, DKIM, DMARC, MX, PTR) are domain-level, not mailbox-level. The SpamAssassin check is content-level. If your mailboxes share the same sending-tool configuration, they'll get the same score.

Mail-tester says my DKIM is broken but my sending tool says DKIM is configured. What gives?

Common situation. Causes:

Your sending tool is signing with a key that doesn't match the public key in your DNS.
The DKIM selector (e.g., default._domainkey) in DNS doesn't match what your sending tool is using.
DNS hasn't propagated yet (rare; usually resolves within an hour).

Check dig +short TXT default._domainkey.yourdomain.com and compare the public key against your sending tool's configured private key.

What's a 10/10 cold email message look like?

Plain text, no images, one or two short paragraphs, a question at the end, no URL shorteners, no spam-trigger phrases, properly-signed by DKIM, aligned with DMARC. The setup matters more than the content gymnastics — once your setup is right, sub-1.5-point deductions are usually fine.

Is mail-tester biased toward marketing email?

Slightly — its content checks were tuned against marketing-email patterns and some rules (image ratio, font contrast) don't quite fit cold email. Still useful; just don't optimize away cold email's natural patterns (short text, conversational tone) chasing a marketing-email-shaped 10/10.

Does mail-tester store my test email?

They keep test results for 1 week, then delete. The actual email body content is visible to anyone with the test URL (which is generated randomly and not publicly listed) during that week.

Mail-tester is the right tool for the question "is my cold email setup obviously broken?" It's not the right tool for "will my cold email reach the inbox?" — that depends on reputation and provider classification, neither of which mail-tester measures.

Run the free deliverability test (DNS + blocklist + TLS in 30s) → /tools/email-deliverability-test · Cold email infrastructure that passes mail-tester at 9.5+/10 out of the box → Try ColdRelay free