Shared vs. Dedicated IP
for Email Sending

How Shared IP Pools Work

When you sign up with an ESP like Klaviyo, Mailchimp, or Constant Contact, your emails don't come from a single IP address. They come from a pool — a rotating group of IP addresses that the ESP maintains and shares across many of their customers. You're one of potentially thousands of senders sharing the same pool.

Here's how the mechanics work: when you click "Send" on a campaign, the ESP's infrastructure routes your emails through whichever IPs in the pool have the most bandwidth at that moment. ISPs like Gmail, Yahoo, and Outlook score each receiving IP as one of the signals in their spam filtering decisions. They build a reputation for that IP based on aggregate signals: bounce rates, spam complaint rates, engagement rates, and sending patterns from every sender using that IP.

Reputable ESPs manage their shared pools aggressively. They monitor complaint rates, remove senders who violate their terms of service, and distribute send volume across pools to avoid any single IP carrying too much load from low-quality senders. Klaviyo, SendGrid, Postmark, and Mailchimp on paid plans all invest significantly in pool management. The result is that shared IPs on quality ESPs typically carry decent reputations — which is why new senders can achieve solid inbox placement from day one without the complexity of running a dedicated IP.

The caveat: the ESP controls the pool, not you. Your reputation is intertwined with every other sender on that pool, and while ESPs work to remove bad actors, they cannot prevent temporary reputation damage from a co-tenant who sends one campaign to a purchased list before getting caught.

What a Dedicated IP Is and When You Need One

A dedicated IP means one IP address that only your emails use. No co-tenants. No shared pool dynamics. The reputation of that IP is built entirely from your sending history — your bounce rates, your complaint rates, your engagement rates, your sending consistency.

This is both the advantage and the risk of a dedicated IP. When you do everything right — clean list, engaged subscribers, consistent send cadence — your dedicated IP can build a strong, stable reputation that isn't vulnerable to anyone else's behavior. ISPs see a consistent stream of well-engaged mail from the same IP and reward it with excellent inbox placement.

But a dedicated IP starts with zero reputation. A brand-new IP address has no history. ISPs treat it as unknown — which typically means more conservative placement (more mail going to spam or the promotions tab) until the IP builds a track record. This is why dedicated IPs require a warm-up process before you can use them for full-volume sends.

ESP Offerings for Dedicated IPs

The Risks of Shared IP Sending

The most commonly cited risk of shared IPs is co-tenant contamination: another sender on your shared pool sends to a purchased list, generates a high complaint rate, and temporarily damages the pool's IP reputation. Your mail faces more aggressive filtering until the pool recovers. This happens — but on well-managed ESPs, it's typically short-lived because their abuse teams respond quickly.

The more insidious risk is subtler: on a shared pool, you cannot isolate whether a deliverability problem is caused by your sending behavior or by someone else's. If your Gmail inbox placement drops by 15% over two weeks, is it your list quality, your content, or a co-tenant problem? With a dedicated IP, the answer is unambiguous — it's you.

A third risk applies specifically to Mailchimp's free tier: free accounts use different IP pools than paid accounts. ISPs have learned to treat Mailchimp free-tier IP ranges with more caution because the free tier historically attracts more low-quality senders. If you're experiencing deliverability issues on Mailchimp's free plan, upgrading to a paid plan — which uses better pools — is worth testing.

Dedicated IP Requirements and Warm-Up

Before committing to a dedicated IP, understand the volume requirement: you need enough email volume to give ISPs a sufficient data sample to build a reputation. The rule of thumb is a minimum of 50,000 sends per month, with 100,000+ being the more reliable threshold.

Below this volume, ISPs don't see enough data from your IP to form a stable reputation. The result can actually be worse than a well-managed shared pool — your dedicated IP may get treated as an unknown entity by ISPs, leading to conservative placement even when your list quality is excellent.

8-Week Dedicated IP Warm-Up Schedule

A dedicated IP warm-up involves gradually increasing send volume over several weeks, starting with your most engaged subscribers (recent opens/clicks) and expanding to the full list as the IP's reputation builds.

During warm-up, monitor your domain reputation weekly using Google Postmaster Tools. If your spam rate exceeds 0.08% or your domain reputation score drops, pause and investigate before continuing the ramp.

Monitoring IP Reputation Regardless of IP Type

Whether you're on a shared pool or a dedicated IP, you need to actively monitor IP reputation. The key distinction: on shared IPs, you can't control what happens to the pool — but you can detect problems early. On dedicated IPs, you're fully accountable, so monitoring is even more critical.

Blacklist Monitoring

Blacklists are databases maintained by spam-fighting organizations. ISPs and spam filters check these lists when deciding how to treat incoming mail. A blacklisted IP can cause immediate and severe delivery failures — mail may be silently rejected or sent directly to spam.

Use InboxEagle's Email Blacklist Checker to check your sending IP against major blacklists including Spamhaus, SURBL, URIBL, Barracuda, and SpamCop. On shared IPs, blacklistings are usually resolved by the ESP quickly (within hours to days) because their IP reputation directly affects their business. On dedicated IPs, you're responsible for submitting delisting requests to each blacklist directly.

Domain Reputation vs. IP Reputation

Modern ISPs — particularly Gmail — weight domain reputation more heavily than IP reputation. This is actually good news: your domain reputation travels with you across IP changes and ESP migrations. Even on a shared IP, your domain can build a strong independent reputation if your list quality and engagement rates are excellent.

Monitor your domain reputation with Google Postmaster Tools (for Gmail) and Yahoo Sender Hub (for Yahoo/AOL). These are free tools from the ISPs themselves — InboxEagle integrates with both to surface alerts when your scores change.

Decision Framework: Shared vs. Dedicated IP

The right IP strategy depends on your monthly send volume, your engineering capacity, and your list quality. Use this framework to decide:

Use a Shared IP If:

• You send fewer than 50,000 emails per month
• Your list quality is moderate to high (opt-in sourced, regularly cleaned)
• You prefer to let the ESP manage IP reputation complexity
• You're newer to email marketing and still building your sending domain's reputation
• You use a reputable ESP with active pool management (Klaviyo, SendGrid, Mailchimp paid plans, Postmark)

Consider a Dedicated IP If:

• You send 50,000–250,000 emails per month AND your list quality is consistently high
• You have capacity to manage the warm-up process (8 weeks, active monitoring)
• You want full isolation from co-tenant reputation risk
• You're diagnosing a persistent deliverability problem that can't be explained by your own metrics

Dedicated IP Is Strongly Recommended If:

• You send over 250,000 emails per month
• Your business depends on email deliverability (e-commerce revenue, SaaS retention)
• You send both marketing and transactional email (use separate dedicated IPs for each stream)

The Monitoring Responsibility Doesn't Change

Whichever IP strategy you choose, the monitoring work remains yours. Your ESP doesn't alert you when your Gmail domain reputation drops from "High" to "Medium." It doesn't tell you when your spam rate is approaching Yahoo's complaint threshold. It doesn't notify you when your DMARC records are misaligned. InboxEagle monitors all of these signals continuously and sends alerts before problems become crises.