Shared vs dedicated IPs, and the truth about warming

Every email you send is delivered by a server with an IP address, and mailbox providers keep a reputation on that address. The question this lesson answers is whose address it is. On a shared IP, you pool reputation with hundreds or thousands of strangers who use the same email service. On a dedicated IP, the reputation is yours alone, for better and, if your volume is small or lumpy, for worse. Most senders belong on shared IPs, dedicated IPs are the right call for a narrower group than the upsell emails suggest, and the "warming" that dedicated IPs require is a real thing wrapped in a lot of ritual.

How a shared pool works

When you send a campaign through a typical email service provider, the message doesn't leave from a server that belongs to you. It leaves from the ESP's delivery infrastructure: a fleet of sending IPs the provider owns, organized into pools. Your campaign goes out through some set of those IPs, and so do the campaigns of every other customer assigned to the same pool.

From a mailbox provider's point of view, an IP is a single sender. Gmail doesn't see "forty ESP customers"; it sees one address with one behavioral history. That history is the blended output of everyone in the pool.

ESPs know this, which is why the good ones police their pools hard. They vet signups, throttle suspicious sending, kick spammers out, and often tier their pools so that senders with strong track records share addresses with each other rather than with whoever signed up yesterday. The pool's reputation is the ESP's asset, and protecting it is a real part of what your monthly fee buys.

The reputation you inherit

Sharing cuts both ways, and it's worth being precise about each direction.

The upside is substantial for small senders. A pool that has been delivering wanted mail for years has a warm, established reputation at every major provider. When you send your first campaign ever, it rides on that history. Your 500-subscriber newsletter delivers on day one because the IP vouches for it while your own domain reputation is still a blank page. Without shared pools, tiny senders would face the cold-start problem alone, and most would lose.

The downside is that you also inherit the bad days. When another customer on your pool blasts a purchased list and gets the IP complained about or listed on a blocklist, your mail is standing on the same address. Your records are perfect, your list is clean, and your delivery dips anyway because of a stranger's behavior. This is one of the specific things our monitoring is built to catch: the sending path checks discover the actual IP that delivered your email, from the headers of a real send, and check that IP against blocklists on an ongoing basis. Shared-pool trouble is invisible from your DNS. It only shows up when you look at what actually delivered your mail, which is exactly why we look there.

One more sharing wrinkle: authentication setups differ by infrastructure. Brevo, for instance, only has customers add its spf.brevo.com include for dedicated-IP setups; on its shared infrastructure, DKIM is the authentication path and customers never touch SPF. If your ESP hasn't asked you to edit SPF, that's often why, and adding an include nobody asked for does nothing.

When a dedicated IP is right

A dedicated IP means the ESP assigns you an address (or several) that only your mail uses. Every signal that IP accumulates is yours: your complaints, your engagement, your consistency. Nobody else's bad day can touch it.

That's valuable under two conditions, and both must hold. You need sustained volume, enough mail flowing every day that providers can keep a current, statistically meaningful opinion of the address. And you need consistency, because a dedicated IP with an erratic schedule combines the worst of both worlds: full ownership of a reputation you're not feeding. If you send serious volume daily, care about isolating yourself from strangers, and have someone who will actually watch the metrics, a dedicated IP is the professional choice. High-volume retailers and large newsletters live here.

The trap for small senders

Here is the part the upsell leaves out. A dedicated IP with low volume is worse than a shared pool, and it's worse in a mechanical, predictable way.

Reputation is built from observed behavior, and observation needs sample size. An IP that sends a few thousand messages a week doesn't give Gmail enough data to form a confident opinion, so the opinion stays weak and mail from that address keeps getting the cautious treatment: throttling, extra scrutiny, occasional foldering. Meanwhile the shared pool you left had years of dense history. You traded a strong borrowed reputation for a thin one of your own.

The dedicated IP also concentrates risk. On a pool, one bad send of yours is diluted by everyone else's good mail. Alone, your mistakes are the entire signal. Small senders buy dedicated IPs to get control and end up with fragility. If your volume is a few newsletters a week, stay on shared infrastructure and spend the energy on your domain reputation instead. (I have watched people pay extra for a dedicated IP to fix a deliverability problem that turned out to be a broken DKIM record. The IP wasn't the issue and the upgrade fixed nothing.)

Warming, honestly

Because reputation must be observed into existence, a brand-new dedicated IP cannot start at full volume. It has no history. Providers treat high volume from an unknown address as an attack until proven otherwise. So you ramp: start with a small slice of your most engaged recipients, and increase volume gradually while watching for deferrals (temporary "try again later" refusals) and spam-foldering. That's IP warming, and the principle is genuinely sound.

What the folklore adds is false precision. You'll find 30-day warming calendars specifying exact daily quotas, as if Gmail published a syllabus. It didn't. No provider commits to a schedule, thresholds differ by provider and by how your early mail is received, and a sender whose warm-up mail draws complaints will need longer no matter what a spreadsheet says. The honest version of warming is one sentence: grow volume gradually, lead with people who reliably open you, slow down when providers push back. A calendar can help you pace that. It is a pacing aid, a habit tracker with better branding, and treating it as a compliance document misses what warming is for.

Warming is also not a shield. A warmed IP with a bad list decays right back. The schedule ends; the behavior that reputation measures never does.

Domain reputation is winning anyway

The trend that reframes this whole decision: mailbox providers have shifted weight from IP reputation toward domain reputation, and the shift has been running for years. IPs change hands, get recycled by ESPs, and hide many senders behind one address, so they're a blurry identity signal. A DKIM-authenticated domain is a sharp one. Since the 2024 bulk sender rules forced authenticated, DMARC-covered sending onto everyone at scale, providers can hang reputation on the domain with confidence, and increasingly they do.

Practical consequence: the IP question matters less than it did, and your domain's record matters more. A pristine dedicated IP will not save a domain with a complaint problem, and a strong domain rides out modest shared-pool turbulence. Get your domain's technical layer verified and keep it clean, because that's the reputation you own outright, the one that follows you when you switch ESPs, and the one no pool-mate can dent.

When a pool-mate's bad send gets an address listed, the list itself becomes the story: who runs blocklists, how an IP or domain ends up on one, and what delisting actually takes. That ground belongs to blocklists explained.

Terms from this lesson

• shared IP pool - a set of sending IP addresses an ESP's customers use collectively, blending their reputations into one history per address.
• dedicated IP - a sending address assigned to a single customer, whose reputation reflects that customer's mail alone.
• ESP (email service provider) - the tool that sends your campaigns and operates the delivery infrastructure: Mailchimp, Brevo, Klaviyo and the rest.
• cold start - the period when an IP or domain has no sending history and providers treat its mail cautiously.
• IP warming - gradually increasing volume from a new IP so providers can observe it and form a reputation, starting with your most engaged recipients.
• deferral - a provider temporarily refusing mail ("try again later"), a common way filters slow down senders they don't yet trust.
• domain reputation - the reputation attached to your authenticated sending domain, now weighted more heavily than IP reputation by major providers.

Check yourself

1. From Gmail's perspective, what is a shared ESP sending IP?

A single sender with one blended behavioral historyA list of separate customers it scores individuallyAn address it ignores in favor of the From domain

2. Why is a dedicated IP usually a bad idea for a small sender?

Dedicated IPs are blocked by default at GmailDedicated IPs cannot use DKIM signingShared pools are always faster at delivering mailLow volume gives providers too little data to form a confident reputation, so the mail keeps getting cautious treatment

3. What is IP warming, honestly described?

A fixed 30-day schedule of daily quotas published by mailbox providersA one-time ritual that permanently protects an IP's reputationGradually increasing volume from a new IP, leading with engaged recipients and slowing when providers push back

4. How has the balance between IP and domain reputation shifted?

IP reputation now decides everythingDomain reputation carries growing weight, since an authenticated domain is a sharper identity than a recyclable IPThe two have always been weighted equally and still are