Which ESP is Best for Deliverability? (Spoiler: It’s the Wrong Question)

Just the other day, I saw someone post another one of those "Deliverability Ranked by ESP" charts, and frankly, it drives me nuts. These charts are inaccurate and misleading. There is no useful way to generate a single "snapshot metric" that tells you you'll get better inbox placement on Platform A versus Platform B. Why? Because that's simply not how deliverability works.

So, how do you actually evaluate deliverability when trying to decide which email service provider (ESP) or marketing automation platform is right for you? The reality is nuanced:

• Good ESPs (of which there are many) will always struggle to get unwanted, spammy mail delivered.
• Bad ESPs (platforms with loose compliance) can still host successful, good senders, but if they don't police their own client base, or don't have the right expertise, they'll struggle to help you with deliverability issues and even sometimes run into broader blocking issues.

With very few exceptions (like certain real-time blocklists), your sender reputation isn't based on your "neighborhood." It is tied directly to your specific sending IPs and your domain identity. When comparing platforms, stop looking at arbitrary leaderboard rankings. Instead, look at these core infrastructure and compliance factors:

1. IP Architecture: Shared vs. Dedicated

How an ESP segments and handles its IP addresses tells you a lot about how your mail will fare.

Dedicated IPs: More common with enterprise platforms, these put you in complete control of your own IP reputation. However, you must have enough consistent sending volume to generate the necessary noise for mailbox providers (MBPs) to recognize and build a reputational profile of you. If you send only small volumes and/or infrequently, a dedicated IP can actually hurt you.

Shared IPs: More common with SMB (small-to-medium business)-oriented platforms, where your deliverability is inherently tied to the behavior of other senders in the shared pool. How these pools are structured will have some impact on your overall success. A better platform might give you a path to earn your way into their top-tier pools based on good behavior, while aggressively moving poor senders down, or kicking them off the platform entirely. If an ESP doesn't strictly police its users, you are going to have a miserable experience on their shared IPs.

2. Domain Identity is Real Reputation

Your domain reputation follows you wherever you go; it doesn't belong to the ESP. However, the platform must support the tools needed to protect and declare that identity.

• Custom DKIM Signing: If an ESP does not allow you to sign emails with your own custom DKIM domain, run away. This is absolute table stakes nowadays. Mailbox providers expect it, and you will face massive deliverability roadblocks at any meaningful volume without it. You absolutely need this to be identified as you, versus being identified only as the ESP.
• Custom Return-Path (SPF) domain: While it is ideal to have a customized return-path (bounce) domain, it isn't always a dealbreaker if an ESP uses their own, provided the messages pass SPF checks cleanly without failures and your DKIM is properly configured.
• Custom Tracking Domains: Look for platforms that let you customize tracking links and image hosting domains. Sharing generic tracking domains across thousands of different clients means one bad actor can ruin the link reputation for everyone on the platform. Avoiding the default, shared click tracking domain for a platform will help you avoid headache.

3. Navigating Mailbox Provider (MBP) Quirks

Different mailbox providers filter mail differently. A sophisticated ESP understands these regional and provider-specific nuances and builds their platform to adapt. For example:

• Shared IP deliverability at Gmail is heavily weighted toward domain reputation. While IP reputation matters, Gmail's filters look closely at how users interact with your specific brand domain. An ESP's shared IP has to be spectacularly bad for Gmail to block it entirely, but if an ESP refuses to police its network, that broad badness can eventually trigger blanket blocks. (Say that ten times fast!)
• Microsoft is famously strict with shared IP pools. They might incorporate domain reputation, but IP reputation seems to matter most to their filtering engines. For maximizing deliverability success at Microsoft, tiered shared IP infrastructure is mandatory. A competent ESP continuously monitors Microsoft blocks to immediately quarantine or remove the specific client causing the issue before it drags down the rest of the shared pool.
• Yahoo is bigger than you realize, and still growing. They've got a smart business model, absorbing other mailbox providers over time. AOL, Verizon, AT&T, Frontier: That's all Yahoo Mail on the backend. Soon, Comcast mailboxes will be Yahoo-hosted, too. They will block for multiple reasons, but primarily for excessive spam complaints. You'll need to monitor.

With some mailbox providers, you'll need to understand: Any ESP is not always going to get 100% of the mail delivered. Blocks happen. ESP leadership needs to know this as well: A platform can't force every message through to the inbox, especially if any clients have reputation or compliance issues. And sometimes even if they don't.

And then there's the human element. Deliverability is ever changing. A smart platform employs dedicated deliverability staff who track these evolving rules, investigate anomalies, and apply those lessons to protect the entire network.

4. Technical Baseline and MTA Management

Beyond reputation, the platform's underlying Mail Transfer Agent (MTA, aka mail server) architecture must be technically sound. Best practices here will include:

Proper Bounce Processing & Suppression: Failure to process and suppress bounces tells a mailbox provider that a sending platform doesn't have its act together. It also denies the ESP a valuable metric when it comes to ranking their own clients.

List-Unsubscribe Header Support: Table stakes in 2026. List-unsub and List-unsub-post headers give users an easy out before they resort to the "Report Spam" button and these are surfaced in a well integrated way with most mailbox providers and mail clients today.

MTA Throttling Controls: The ESP's infrastructure needs to be muscular enough to handle high-volume spikes when multiple clients send simultaneously, yet delicate enough to throttle and respect connection limits so they don't overwhelm MBP receiving servers. Mail will back up sometimes; the platform needs to not fall down when it does.

Future-Proofing Features: We know that A.I. is top of mind and incorporating A.I.-native features is great. But also look for what other modern functionality is included. Easy DNS configuration, DMARC monitoring or partnerships, BIMI logo support, and more. Email features evolve; it's not simply "build it and forget about it and move on." If the underpinnings of the platform haven't been updated in years, that's not a good sign.

5. Policy Compliance: Often forgotten, always important

A critical piece of an ESP's deliverability operation happens behind the scenes in the compliance department. Top-tier platforms don't just guess who the good senders are. They track metrics internally to stack-rank their clients.

• The Good Senders: They sit at the top of the internal leaderboard. They generate the highest volume of positive interactions (opens and clicks) while driving the least negative feedback (spam complaints and bounces).
• The Bad Senders: They sink to the bottom. They generate high spam complaint rates, high bounce rates, and much lower engagement signals. A compliant ESP will quickly quarantine or offboard these accounts to protect the rest of the ecosystem.

The Reality Check: It is not about who your brand is or who you think you know. It's entirely about how wanted your mail is on the exact day you send it. Explicit permission is mandatory. If your mail is unwanted, even the most prestigious brand in the world will find its way straight to the spam folder.

And the ESP's connection to this process is where the compliance team comes into play. Smart platforms identify clients who are showing signs of being bad (or ignorant) senders. The goal is to nurse them back to health by helping them understand how to better position themselves as good participants of the email ecosystem. How to improve permission practices, jettison troublesome or aged data, how to improve strategy to put their best sending foot forward. And to show them the door, if they're unwilling to take the necessary steps to improve.

Because a platform overrun with poorly acting clients will eventually run into their own problems. A client has a reputation, but so does the platform. To be blunt, if you run an email marketing platform, and everybody sending from your platform sucks, eventually mailbox providers will NOT help you when you reach out for assistance.

But overall, mostly: It's the Sender, Not the Platform

Make no mistake: a platform's technical practices and infrastructure do have an impact. You absolutely need an ESP or marketing automation platform with a strong MTA architecture, handles authentication correctly, and takes corrective action in response to bad actors.

But the far greater impact will always come from the person hitting "send" on that email campaign.

An ESP can provide you with the cleanest IPs and the most sophisticated tools in the industry, but they cannot force subscribers to open your mail or stop them from hitting the spam button. Deliverability always comes down to one fundamental truth: send wanted mail to people who actually want it. That is what matters most: It's you, not the platform.