Should You Use a Shared or Dedicated IP for Cold Email in 2026?

For most cold email senders in 2026, the answer is shared IP. Google's bulk sender guidelines and Smartlead's own sender-reputation research point the same direction: on the shared infrastructure most cold email actually rides on, domain reputation typically matters more than IP reputation. A dedicated IP with no consistent volume behind it can hurt you more than a shared pool with a clean track record.

What's the difference between a shared and dedicated IP for cold email?

A shared IP is an address used by multiple senders at once, usually inside an email platform's sending pool. A dedicated IP is assigned to one sender only. Mailgun's own reputation guide defines the split cleanly: IP reputation is "based on the IP address from which you send mail," while domain reputation is "based on the domain from which you send mail," per Mailgun's sender reputation guide.

On a shared IP, your deliverability is partly tied to whoever else is sending from that same address. On a dedicated IP, you own the reputation outright, for better or worse. That ownership sounds like an upgrade. It's only an upgrade if you can actually fill the pipe with volume every single day.

Does IP reputation still matter for cold email in 2026?

Yes, but less than most founders think. Validity's Sender Score model, cited in Smartlead's 2026 guide, still scores IPs on a 0-100 scale where a score above 90 means inbox providers trust the sender and scores below 70 trigger active distrust, spam routing, or outright rejection, per Smartlead's sender-score guide.

But that same guide draws a sharper distinction that matters more for cold email specifically: IP reputation, domain reputation, and sender reputation (the composite of both plus behavior) are tracked separately by inbox providers, and "for cold email on shared infrastructure, domain reputation typically matters more than IP reputation." Gmail backs this up on the domain side. Google's own guidance tells senders to "ideally, send all messages from the same IP address" when they can, but treats DKIM and SPF authentication, which live on the domain, as the baseline requirement for every bulk sender regardless of IP setup, per Google's bulk sender guidelines.

If you already have SPF, DKIM, and DMARC configured correctly and a domain with a clean sending history, you're solving the bigger half of the problem before you ever touch an IP setting. If you haven't set those up yet, that's the actual starting point, not IP selection. See our SPF, DKIM, and DMARC setup guide for the exact records to publish.

Where does most cold email actually get sent from?

Not from a dedicated IP you control. Most cold email in 2026 still runs through Google Workspace or Microsoft 365 mailboxes, connected via a sending platform like Smartlead or Instantly. Google Workspace caps standard accounts at 2,000 messages a day and trial accounts at 500, per Google's own Workspace sending limits documentation. Every one of those messages leaves through Google's own outbound mail servers, which are shared across millions of Workspace accounts worldwide.

That means the "dedicated IP" conversation is often moot before it starts. If your mailboxes are Google Workspace or Microsoft 365 inboxes, you're on Google's or Microsoft's shared infrastructure no matter what your sending platform's marketing page says. The lever you actually control at that point is domain and mailbox behavior, not IP assignment. This is a big part of why warming up a domain properly does more for inbox placement than shopping for infrastructure upgrades.

When does a dedicated IP make sense for cold email?

A dedicated IP earns its keep when volume is high enough, and consistent enough, to keep the IP active every day. Google's guidelines explicitly warn bulk senders to "avoid introducing sudden volume spikes if you do not have a history of sending large volumes," which is exactly the failure mode a low-volume dedicated IP runs into, per Google's bulk sender guidelines.

Signs a dedicated IP is worth the setup cost:

• You're sending from one platform in high, steady daily volume, not sporadic campaign bursts.
• You cross the 5,000-messages-per-day threshold where Google's guidelines apply stricter authentication rules anyway, so you're already running like a mature sender.
• You have the operational discipline to run a full IP warmup schedule and monitor it, not just set it and forget it.
• You're sending transactional or high-trust mail where isolating your reputation from other senders genuinely reduces risk.

Notice what's missing from that list: "you have a cold email campaign starting next week." That's the scenario where a dedicated IP usually backfires.

Why can a dedicated IP actually hurt deliverability at low volume?

A brand-new dedicated IP starts with zero history. Inbox providers have no data on it, so they treat it cautiously by default, exactly the caution Google's guidelines describe for any sender introducing volume without a track record. A shared pool, by contrast, already carries an established reputation built by every sender using it well, which is why Mailgun's guide frames shared IPs as letting "new senders benefit from an established IP's reputation without building history independently," per Mailgun's reputation guide.

Here's the trap. A founder buys a dedicated IP because it sounds more professional, sends 200-300 emails a day from it (typical single-mailbox cold email volume), and skips or rushes warmup. The IP never accumulates enough sending history for Gmail or Outlook to trust it, spam placement climbs, and the founder blames the "dedicated IP problem" instead of the actual cause: low, inconsistent volume on infrastructure that needed daily reinforcement to build trust.

Compare that to routing the same 200-300 emails a day through a well-managed shared pool with a strong existing reputation, or through Google Workspace's own shared sending infrastructure with proper SPF, DKIM, and DMARC in place. You inherit reputation instead of building it from scratch. For most cold email programs under enterprise scale, that's the safer bet.

Shared vs dedicated IP: which wins on each factor?

Factor	Shared IP	Dedicated IP
Starting reputation	Inherits the pool's existing history, good or bad	Starts at zero, no history to lean on
Setup effort	None, usually built into your sending platform	Requires a full warmup schedule and monitoring
Minimum volume to stay healthy	Low, your share of the pool's overall volume	High and consistent, daily sends needed to hold reputation
Exposure to other senders' mistakes	Yes, a bad neighbor on the pool can drag you down	None, your reputation is yours alone
Best fit	Most cold email teams, agencies, and SMB senders	High-volume, single-brand senders with daily consistent output
What actually decides deliverability	Domain reputation, list quality, authentication	Same factors, plus IP warmup discipline

So should you use a shared or dedicated IP for cold email in 2026?

If you're running cold email through Google Workspace, Microsoft 365, or a platform like Smartlead, Instantly, Mailgun, or SendGrid's shared pool, and your volume is under enterprise scale, stay on shared infrastructure. It's the setup Google's own guidance implicitly assumes for most senders, and it's the setup that lets you inherit reputation instead of building it from a cold start.

The honest exception: if you're already sending high, consistent daily volume from a single brand and you have someone who will actually run and monitor a warmup schedule, a dedicated IP gives you cleaner isolation from other senders' mistakes. Outside that specific situation, the time you'd spend managing a dedicated IP is better spent fixing SPF, DKIM, DMARC, and domain warmup, the things that decide inbox placement regardless of which IP setup you choose.

If you'd rather not manage any of this yourself, that's the kind of infrastructure decision Modern Inbound handles as part of running outbound end to end. You can see how that setup works at moderninbound.com or just get in touch.

What else do people ask about shared vs dedicated IPs for cold email?

Do Google Workspace and Microsoft 365 use dedicated IPs for cold email?

No. Both send outbound mail through their own large shared server infrastructure. Google Workspace accounts are capped at 2,000 messages a day (500 for trial accounts), per Google's Workspace sending limits documentation, and every one of those messages leaves through Google's shared outbound mail servers, not an IP the individual sender controls.

What sending volume justifies a dedicated IP for cold email?

There's no single official number, but the pattern is consistent across email infrastructure providers: high and steady daily volume from one platform, not sporadic campaign bursts. Google's bulk sender guidelines specifically warn against introducing volume spikes without an existing sending history, which is the exact risk a low-volume dedicated IP runs into.

Does a dedicated IP guarantee better deliverability?

No. A dedicated IP only isolates your reputation from other senders, it doesn't create good reputation on its own. Per Smartlead's sender-score guide, for cold email on shared infrastructure, domain reputation typically matters more than IP reputation, and that domain-level work (SPF, DKIM, DMARC, warmup, list quality) still has to happen regardless of which IP setup you pick.

How long does it take to warm up a dedicated IP?

Warmup timelines vary by provider and volume, but the underlying rule from Google's bulk sender guidelines applies throughout: avoid sudden volume spikes and build sending history gradually. Mailgun and similar platforms offer warmup automation that ramps volume up over time rather than sending at full volume from day one.

Can a bad neighbor on a shared IP hurt my cold email deliverability?

Yes. Mailgun's reputation guide notes that shared IP reputation can backfire if the other senders on your IP have bad email sending habits, since inbox providers weigh all activity on that IP together. It's a real tradeoff, but for most senders it's outweighed by the benefit of inheriting an already-established reputation instead of starting from zero on a dedicated IP.

By Rishabh Ambasta, Founder, Modern Inbound.