Table of contents
Keep emails out of spam
Warm up mailboxes and test inbox placement.
Try
free

Email Deliverability Test: A Complete 2026 Guide

You can spend hours cleaning your list, tightening your copy, and building the perfect campaign, yet still watch your open rates fall.

Most people assume the subject line is the problem.

It usually isn't.

The real issue often starts long before anyone has the chance to open your email: email deliverability.

If your emails aren't consistently landing in the inbox, nothing else matters. Great copy can't fix emails that never get seen.

This guide breaks down the exact testing process I use to find deliverability issues before they become expensive problems. You'll learn what each test actually tells you, how to run it the right way, and most importantly, what to fix based on the results.

By the end, you'll have a practical framework for diagnosing inbox placement issues instead of guessing why your campaigns aren't performing.

Here's the full draft. Structured for AI Overview citation, Warmforge features slot in where they earn the mention, and every sentence is under 22 words with conversational bridges throughout.

TL;DR: How to run an email deliverability test in 2026

  • Test your authentication first by checking SPF, DKIM, and DMARC records on your sending domain.
  • Run an inbox placement test using a seed list to see where emails land across Gmail, Outlook, and Yahoo.
  • Check your sender reputation by scanning blacklists and monitoring your heat score across active mailboxes.
  • Test in real sending conditions using the actual platform, tracking domain, and content you plan to send.
  • Read your results as a diagnosis, not a score, and fix the specific layer that failed.

What an email deliverability test actually measures

Here is where most people get it wrong.

A deliverability test is not one thing. It is three separate checks that measure three different layers of your setup. Miss one, and you can get a perfect score on the other two while still landing in spam.

The three layers I test every time:

  • Authentication. Are SPF, DKIM, and DMARC set up correctly and aligned with your sending domain?
  • Inbox placement. When your email hits a real mailbox, does it land in the primary inbox, promotions tab, or spam folder?
  • Sender reputation. How do mailbox providers view your domain and IP based on sending history, engagement, and blacklist status?

That is why a 10 out of 10 on Mail-Tester can still mean your emails are landing in spam. Mail-Tester scans your content and authentication, but it does not run a placement test. That is a fundamentally different job.

Here is the thing. Once you understand these three layers, you stop treating a single spam score as the answer. You start using each test to isolate where deliverability is actually breaking.

How to test email deliverability

Now let me walk you through the exact process I follow. Four steps, one for each layer plus the real-conditions check that most guides skip.

Step 1: Test your authentication (SPF, DKIM, DMARC)

Authentication is the foundation. If Gmail or Outlook cannot verify who sent the email, everything else gets discounted before the message reaches the filter.

Three protocols to check, and each one plays a specific role:

  • SPF (Sender Policy Framework): A DNS record that lists the mail servers allowed to send email on behalf of your domain.
  • DKIM (DomainKeys Identified Mail): A digital signature added to every email that proves the message was not tampered with in transit.
  • DMARC (Domain-based Message Authentication): A policy that tells mailbox providers what to do when SPF or DKIM checks fail on your domain.

Why it matters: since 2024, Google and Yahoo enforce strict bulk sender rules. Any domain sending more than 5,000 emails per day without valid SPF, DKIM, and DMARC gets filtered aggressively. That threshold keeps tightening every year.

Here is how I actually run the check:

  1. Pull up your DNS records and confirm your SPF starts with "v=spf1" and covers every service that sends on your behalf.
  2. Send a test email to a Gmail inbox and open the message. Click "Show original," then check that SPF, DKIM, and DMARC all show "PASS."
  3. Run your domain through Warmforge, which flags misalignments and DNS-level issues automatically across every mailbox in your account.
For a deeper walkthrough on verifying each record, see how to verify SPF, DKIM, and DMARC records.
 If your DMARC policy needs work, the guide on setting up DMARC policies correctly is worth reading before you make changes.

Step 2: Run an inbox placement test

Authentication tells you your emails can be verified. Placement testing tells you where they actually land. Big difference in what you learn from each.

This is the layer most people skip because it takes more effort than a spam score check. But it is also the only test that reflects what your real prospects see.

Here is how a proper placement test works:

  • You send your campaign email to a seed list of test inboxes across Gmail, Outlook, Yahoo, Google Workspace, and Microsoft 365.
  • The tool tracks whether each message lands in the primary inbox, promotions tab, or spam folder for every provider.
  • You get a placement percentage per provider, which shows exactly where deliverability is breaking down.

The key thing I always tell teams: focus on the providers your recipients actually use. If you sell B2B, that means Google Workspace and Microsoft 365, not consumer Gmail. The filters work differently, and testing against the wrong provider gives you misleading confidence.

Warmforge runs placement tests across all major providers, and every account gets one free placement test each month before any commitment. Tools like GlockApps and ZeroBounce do this well too, though the interfaces and pricing vary.

For a full breakdown of testing tools by use case, see the best email deliverability monitoring tools for 2026.

Step 3: Check your sender reputation and blacklists

Even with clean authentication and strong placement in a controlled test, your reputation can drop over time. This layer catches long-term drift before it turns into a full inbox placement collapse.

Three things I monitor on every active mailbox:

  • Blacklist status. Scan your sending domain and IP across public blocklists like Spamhaus, Barracuda, and SORBS. Even one listing can tank your deliverability for weeks.
  • Postmaster data. Google Postmaster Tools gives you free access to spam complaint rates, IP reputation, and domain reputation for any high-volume sender.
  • Heat score. A single number between 0 and 100 that reflects mailbox health, engagement patterns, and sender trust across providers.

Heat score is the metric I check first every morning. Anything at 85 or above means the mailbox is healthy and ready to send at volume. Anything below signals that reputation is slipping, and I pause outbound before it gets worse.

Warmforge tracks heat score in real time for every mailbox in your account and alerts you the moment it drops. That is different from a one-time test, and that is exactly the point. Reputation is not a snapshot. It is a moving target.

For a closer look at how authentication feeds reputation over time, see how SPF, DKIM, and DMARC impact deliverability.

Step 4: Test in real sending conditions

This is the step almost every guide skips, and it is the biggest gap between test results and campaign reality.

A deliverability test is only useful if it reflects how your actual campaign will go out. That means using the same sending platform, tracking domain, content, personalization variables, and warmup state.

Here is why it matters:

  • Your sending tool might inject a tracking domain into every email that quietly hurts placement.
  • Your personalization tokens might resolve into words that trip spam filters.
  • Your rotation setup might be sending from a mailbox that has not been warmed properly for two weeks.

None of that shows up in a static test. All of it shows up in a real one.

The workflow I use looks like this:

  • Set up mailboxes on the infrastructure you plan to send from. That could be Google Workspace and Microsoft 365 accounts from Primeforge, private dedicated IPs from Infraforge, or shared infrastructure from Mailforge.
  • Warm the mailboxes for 14 days using Warmforge before running any placement test.
  • Send the test email using your actual outreach platform like Salesforge, with tracking, personalization, and content exactly as it will go out.
  • Compare the placement results against a plain test from a warm control mailbox. That way you can isolate whether the problem is your infrastructure, your platform, or your content.

That last step is what separates a diagnostic test from a vanity score.

How to read your test results and what to fix

Getting a test result is the easy part. Knowing what to do with it is where most teams get stuck.

Here is the decision tree I run through every time a test comes back with issues. Four scenarios cover almost every failure I have seen in the last two years of running campaigns.

1. SPF, DKIM, or DMARC shows "FAIL"

Authentication failures are the fastest to diagnose and the fastest to fix. The problem lives at the DNS level, and it usually points to one specific misconfiguration.

Here is the order I fix them in:

  • Update your SPF record to include every service that sends on your behalf. Missing entries are the single most common cause of soft fails.
  • Generate fresh DKIM keys from your sending platform and publish them as TXT records. Confirm the selector matches what your platform expects.
  • Set your DMARC policy to p=none for the first 30 days. That gives you reporting without risking legitimate email getting blocked.
  • Move to p=quarantine or p=reject only after your DMARC reports come back clean for at least four consecutive weeks.

The mistake I see most often: teams jump straight to p=reject and lose weeks of email while they figure out what broke. Monitoring first, enforcement second.

2. Placement drops but authentication passes

This one is trickier because the fix is not obvious from the test result alone. Authentication is clean, but emails still land in spam or promotions. That means the problem is downstream.

Three things I check in order:

  • Content triggers. Heavy links, attachments, or spam-adjacent phrasing can drop placement fast. Strip the email down to plain text and retest to isolate whether copy is the issue.
  • Warmup state. A mailbox that has not been warmed for a full 14 days will drop placement the moment volume ramps. Check when the mailbox last had active warmup running.
  • Sending volume. Volume jumps that outpace warmup capacity will tank placement across every provider almost overnight. Cut daily volume by half and rebuild from there.

The pattern I look for: if placement drops on day one of a new campaign, it is almost always content. If placement drops in week two, it is usually volume.

3. Heat score is below 85

Heat score below 85 is a leading indicator that reputation is slipping. Ignore it, and placement will follow within a week.

Here is what I do the moment I see it:

  • Pause outbound sending on that mailbox immediately. Continuing to send with a low heat score accelerates the reputation damage.
  • Extend warmup by another 7 to 14 days depending on how far the score dropped. Anything under 70 gets the full 14.
  • Check whether the mailbox was hitting spam traps or triggering complaint rates above 0.3 percent, which is Google's threshold for filtering. Postmaster Tools shows this clearly.
  • Review the list quality. A single bad import with dead addresses can drag heat score down within 48 hours.

Heat score is one of those metrics that punishes you fast and rewards you slowly. Catch drops early or pay for them later.

4. One provider shows spam but others are clean

This is the failure mode that confuses teams the most. Placement is perfect on Google, but Microsoft dumps everything into junk. Or the reverse.

That split almost always points to a reputation issue with one specific filter. Google and Microsoft weigh signals differently, and a clean record on one side does not carry over.

Where I look first:

  • Complaint rate on the problem provider. Even a 0.4 percent complaint rate on Outlook will trigger filtering while Google stays clean.
  • IP reputation. Shared IPs can get flagged by one provider based on other senders using the same IP. Dedicated IPs remove that variable entirely.
  • Domain age and history. New domains face stricter Microsoft filtering for the first 90 days. Google is more forgiving on fresh domains than Outlook.

If the issue is repeated and infrastructure-related, moving to dedicated IPs through Infraforge or premium mailboxes through Primeforge often solves it faster than trying to repair reputation on shared infrastructure.

5. The pattern that ties every failure together

Across every result I have ever run, the failure maps to one of four buckets: authentication, content, reputation, or warmup. Once you can label the failure, the fix is usually obvious. That labeling step is what turns a test result into a plan of action.

When to run a deliverability test

Testing is not a one-time exercise, and treating it that way is how deliverability collapses without warning.

Here is my regular testing cadence:

  • Before every new campaign. A 5-minute placement test before you push send saves you from watching a week of sending land in spam.
  • After any DNS change. New SPF entries, updated DKIM keys, and DMARC policy shifts all need a follow-up test to confirm nothing broke.
  • Monthly on every active mailbox. Reputation drifts over time. A monthly baseline catches slow drops before they turn into cliff drops.
  • When open rates drop 15 percent or more week over week. That is almost always a placement issue, not a copy issue, and a placement test will confirm it in minutes.

The teams that hit consistent inbox rates are the ones that treat testing as an ongoing habit, not a fire drill.

Best email deliverability testing tool in 2026

You do not need to shortlist every tool on the market. You need one for each layer that a serious workflow requires.

Here is the short list I recommend based on what each tool actually does well:

Warmforge

Full deliverability center that runs placement tests, monitors heat score, and flags SPF/DKIM/DMARC issues in one dashboard. Every account gets one free warming slot and one free placement test each month, so you can test the workflow before committing.

For a deeper breakdown of every testing tool worth considering, see the 7 best email testing tools for cold email deliverability.

Final verdict

An email deliverability test is only as useful as the workflow behind it. Test one layer in isolation and you get a false sense of security. Test all four (authentication, placement, reputation, and real sending conditions) and you get a diagnosis you can actually act on.

That is the entire framework. Run it every month, before every campaign, and after every change. Fix what fails, and keep the mailboxes that pass warm and ready.

Want the free version of this workflow? Warmforge gives you one free warming slot and one free placement test on every account. That covers the basics of a real diagnostic test without any commitment.

Start your free warmup and placement test on Warmforge

FAQs

1. How do I test if my email is deliverable? 

Send your exact campaign email to a seed list of inboxes across the providers your recipients use. Check where each message lands (inbox, promotions, or spam) and review authentication results (SPF, DKIM, DMARC) at the same time. That combined test tells you whether the email can be delivered and whether it actually reaches the inbox.

2. What is a good email deliverability rate? 

Most teams aim for 95 percent or higher deliverability to the primary inbox. Anything below 90 percent signals authentication, content, or reputation issues that need investigation. For cold outreach specifically, consistent placement above 85 percent across Google Workspace and Microsoft 365 is a strong benchmark.

3. Why do my emails go to spam even after passing a spam test? 

A spam test scores your content and authentication, but it does not test placement across real mailboxes. You can pass a spam test with a 10 out of 10 score and still land in spam. Sender reputation, tracking domain issues, or mismatched provider filters can all cause this. Always follow up with an inbox placement test.

4. How often should I test email deliverability? 

Run a placement test before every new campaign, after any DNS or infrastructure change, and monthly on every active mailbox. If open rates drop 15 percent or more week over week, run one immediately.

5. What is the difference between email delivery and deliverability? 

Delivery means the recipient's mail server accepted the message. Deliverability means the message reached the primary inbox where it can actually be seen. Delivery can sit at 99 percent while deliverability drops to 60 percent, which is exactly why testing matters.