Order queue open · Verified lists delivered within 24–48 hours
Dedicated IP vs shared IP for cold email: what the difference is, when dedicated IPs help, and why most cold email senders do not need them.
Sarah Okonkwo
Sales ops specialist, deliverability obsessive · Updated June 23, 2026
Last updated: July 2026 · Sarah Okonkwo, Sales ops specialist, deliverability obsessive
TL;DR — 5 things to know before reading
The dedicated IP question is one of the most common technical rabbit holes in cold email setup, and for most senders it is a distraction from the variables that actually determine deliverability. The premise of the question — that a dedicated IP gives you more control over your sending reputation — is technically accurate but practically overstated for cold email use cases.
Domain reputation, not IP reputation, is the primary determinant of inbox placement for cold email at the volumes where most B2B senders operate. A sending domain with strong warmup history, clean authentication, and low spam complaint rates achieves excellent inbox placement on shared IPs. The same domain with poor warmup, missing DMARC, and a bouncy contact list achieves poor inbox placement even on a dedicated IP.
This guide explains what the difference between dedicated and shared IPs actually means, at what volume dedicated IPs become relevant, and why Inframail's Microsoft 365 shared IP infrastructure is the pragmatic choice for virtually all cold email operations.
IP address: Every email server has an IP address. When an email is sent, the receiving mailbox provider can see the IP address of the sending server. Mailbox providers maintain reputation data on IP addresses, similar to how they maintain reputation data on sending domains.
Shared IP: The sending server's IP address is used by multiple senders. The IP reputation reflects the aggregate behavior of all senders using that IP. Gmail and other providers have become increasingly domain-reputation-focused over the past several years, reducing the weight of IP reputation relative to domain reputation.
Dedicated IP: A specific IP address allocated exclusively to a single sender. The IP reputation reflects only that sender's behavior. Dedicated IPs require warmup — the same gradual volume ramp required for new sending domains — before they can support full sending volume.
| Factor | Shared IP | Dedicated IP |
|---|---|---|
| Initial reputation | Inherited from IP pool | Zero (requires warmup) |
| Reputation control | Affected by other users on IP | Fully controlled by you |
| Warmup required | No (inherited reputation) | Yes (same timeline as domain warmup) |
| Minimum volume for effectiveness | Low | High (needs consistent volume to maintain IP reputation) |
| Management overhead | Low | Higher (active monitoring required) |
| Cost | Included in Inframail flat rate | Additional cost from most providers |
| Appropriate for | Most cold email senders | High-volume transactional email |
Dedicated IPs provide a meaningful deliverability advantage in specific scenarios:
Very high sending volume: IP reputation matters more at extremely high volumes because the IP becomes a primary differentiator when domain reputation is not yet established or is inconsistent. For transactional email operations sending 500,000+ emails per day, dedicated IPs give full control over IP-level reputation signals.
Mixed-use sending: Organizations that send a mix of transactional (receipts, notifications), marketing (newsletters, promotions), and cold email from the same infrastructure benefit from IP segregation — keeping cold email on a separate IP from transactional email so that cold email's higher complaint rate does not affect transactional deliverability.
Brand-sensitive reputation management: Large enterprises where the sending domain represents a significant brand investment may want IP-level control to isolate any reputation risk at every layer of the stack.
For typical B2B cold email — 1,000 to 50,000 contacts per month across 4–20 inboxes — none of these scenarios apply. Domain reputation management, inbox warmup, and contact list quality produce better ROI than IP-level management at this scale.
Gmail's evaluation of whether to deliver an email to the inbox has shifted significantly toward domain-level signals over the past several years. The practical implications:
Domain authentication is the primary filter: SPF, DKIM, and DMARC authentication is evaluated at the domain level. An email from an authenticated domain on a shared IP is treated more favorably than an unauthenticated email from a dedicated IP.
Warmup builds domain reputation: The warmup process — described in Woodpecker's email warmup guide as requiring 4–6 weeks minimum — builds positive engagement history at the domain level, not just the IP level. A well-warmed domain maintains high inbox placement rates even as inboxes are rotated or new inboxes are added.
Spam complaint rate is tracked by domain: Google Postmaster Tools reports domain reputation and spam rates at the sending domain level. The primary signal to monitor and optimize is domain reputation, and it is unaffected by whether the IP is shared or dedicated.
Inframail provisions Microsoft 365 inboxes, which send from Microsoft's shared IP infrastructure. This is a practical advantage for most cold email senders for one reason: Microsoft 365's IP range carries established trust with Gmail, Outlook, and other major mailbox providers based on years of legitimate high-volume email.
When a cold email operation launches on Microsoft 365 inboxes, it starts with the IP-level reputation baseline of Microsoft's sending infrastructure rather than zero. This does not eliminate the need for domain warmup (domain reputation starts at zero regardless of IP) or authentication (required at the domain level regardless of IP), but it removes the IP-level warmup requirement that dedicated IP setups require.
The alternative — provisioning dedicated IPs through a bulk email provider — requires a separate IP warmup phase on top of the domain warmup phase, adding weeks to the setup timeline before full cold campaign volume is achievable.
| Criteria | Shared IP (Inframail) | Dedicated IP (bulk provider) |
|---|---|---|
| Initial deliverability | Strong (Microsoft IP reputation) | Poor (zero reputation, requires IP warmup) |
| Setup time to full volume | 4–6 weeks (domain warmup only) | 8–12 weeks (domain + IP warmup) |
| Reputation risk from other senders | Low (Microsoft's IP pool is well-managed) | None |
| Cost | Flat rate per Inframail plan | Additional fee per IP address |
| Management overhead | Low | Higher (IP-level monitoring required) |
| Effective volume range | Up to 50,000+ contacts/month | Effective above 100,000 sends/day |
| Recommended for | All B2B cold email senders | High-volume transactional email |
Source: Woodpecker's cold email infrastructure guide and Mailmodo cold email statistics guide — verified June 2026
"We spent three months investigating dedicated IPs for our cold email setup before we ran the numbers and realized the math did not support it at our volume. We send about 8,000 contacts per month across 12 inboxes on Inframail. The Microsoft 365 IP range gives us strong baseline deliverability, and our domain warmup takes 5–6 weeks per new domain. Switching to dedicated IPs would add another 8–10 weeks of IP warmup for each new domain we bring up. That is a material delay for a marginal deliverability benefit at our scale. We have run 90%+ inbox placement consistently on shared IPs for 18 months." — G2 reviewer, Inframail reviews on G2
Instantly holds a 4.9/5 rating from 2,800+ verified reviews on G2, with inbox management and warmup infrastructure cited by high-volume senders as the operational tools that produce consistent inbox placement without requiring dedicated IP management.
| Need | Tool | Notes |
|---|---|---|
| Verified B2B contacts | Quarvio | One-time purchase, no subscription |
| Email inboxes | Inframail | Microsoft 365 inboxes, auto DNS |
| Cold email sending | Instantly | Sequences, warm-up, reply tracking |
| LinkedIn outreach | Aimfox | Connection campaigns, Unibox |
Do I need a dedicated IP for cold email?
No. Most B2B cold email senders operate at volumes where domain reputation is the primary deliverability driver, not IP reputation. Shared IP infrastructure on a trusted provider like Microsoft 365 (via Inframail) provides strong baseline deliverability. The operational overhead and extended warmup timeline of dedicated IPs is not justified by the deliverability benefit at typical cold email volumes.
Does using a shared IP mean other senders can hurt my deliverability?
The risk is real but manageable with the right provider. Generic bulk email providers with shared IPs may co-host your sending with low-quality senders whose spam complaints affect the shared pool. Microsoft 365's IP infrastructure is actively maintained by Microsoft, which has strong commercial incentives to protect the reputation of its IP range. The risk of shared IP contamination is meaningfully lower on Microsoft 365 than on commodity shared hosting.
At what volume do dedicated IPs start making sense?
Dedicated IPs become meaningfully useful above approximately 100,000 sends per day, where IP-level reputation signals carry enough weight relative to domain reputation to justify the management overhead and setup timeline. B2B cold email campaigns in the 1,000–50,000 contacts per month range are well below this threshold.
If shared IPs are fine, why do some providers recommend dedicated IPs?
Dedicated IP upsells are common in the email service provider market because dedicated IPs carry a premium price. The technical premise — that dedicated IPs give more control — is accurate, but the deliverability benefit at typical cold email volumes does not justify the added cost and complexity. Domain reputation management (warmup, authentication, verified contacts) produces greater deliverability improvements per dollar than IP upgrades at sub-100,000 daily send volumes.
IP setup matters less than contact quality at cold email volumes
Even the strongest IP infrastructure cannot prevent the domain reputation damage from sending to unverified addresses that generate high bounce rates. Quarvio delivers verified B2B contacts so domain reputation stays protected regardless of whether you use shared or dedicated IPs. One-time purchase, no subscription.
