Comparison
CEO and co-founder
Dedicated IP vs Shared IP for Cold Email: Complete Technical Guide for Agencies
TL;DR: Adding more inboxes won't fix poor reply rates if your shared IP pool is the root problem. Shared IP infrastructure exposes every campaign you run to the sending behavior of strangers on the same pool, including spam trap hits, high bounce rates, and aggressive volume spikes that trigger blacklists. Dedicated IPs isolate your sender reputation completely. Inframail's Unlimited Plan includes 1 dedicated US-based IP and unlimited inboxes for $129/month flat, compared to $350-420/month for 50 inboxes on Google Workspace. At 18+ inboxes, the cost math favors dedicated infrastructure every time.
Most campaign managers spend hours tuning subject lines and personalizing openers before considering whether a dedicated IP, rather than a shared pool, is the root cause of stalled reply rates. The real bottleneck is often the IP address emails route through, not the copy. On a shared IP pool, another user's spam trap hit or 10% bounce rate can pull your campaigns into spam with no warning and no visibility into the cause.
This guide covers the mechanics of both IP types, the specific events that cause shared pool contamination, warmup timelines for dedicated IPs, and the exact monthly cost difference for 50 to 200 inboxes so you can make an informed decision for your agency.
Dedicated vs. shared IP: deliverability rules
Understanding how each IP type works at a technical level is the starting point for evaluating which infrastructure fits your sending setup.
Dedicated vs shared IPs for cold email
A shared IP typically routes emails from multiple senders simultaneously, pooling reputation to simplify setup and spread deliverability risk across a wider sending base. A dedicated IP gives you exclusive sending rights to one IP address, meaning your company is the only sender at that address.
The distinction matters because both IP reputation and domain reputation factor into inbox placement. Modern mailbox providers like Gmail evaluate both domain and IP reputation, while Microsoft's filtering also considers IP reputation for corporate Outlook inboxes that make up the majority of B2B cold email targets. On a shared IP, poor behavior from other senders can undermine your IP's standing regardless of how clean your domain reputation is.
Dedicated vs shared IP reputation
Since a shared IP serves multiple senders, everyone shares the same sending reputation. Your inbox placement rate doesn't depend solely on your own sending practices. Everyone else sending from that IP affects your deliverability, including senders you'll never meet and can't influence. This interdependence is why high-volume senders choose dedicated infrastructure.
A dedicated IP lets you control your IP reputation entirely, because it reflects only your sending behavior. ISPs and webmail providers evaluate your dedicated IP independently, without factoring in other senders. Mailtrap's shared vs. dedicated IP analysis confirms that a dedicated IP means your sending reputation is based entirely on your own behavior, with no risk of contamination from other senders.
Why IP reputation matters for inbox placement
Inbox placement rate (the percentage of emails landing in the primary inbox rather than spam or promotions) determines whether your campaigns generate meetings or disappear. IP reputation and domain reputation both contribute to that rate, influencing how receiving servers score your messages before evaluating content.
For cold email, where you're sending to people who haven't opted in, receiving servers use these combined signals as a proxy for sender intent. Our dedicated vs. shared IP breakdown documents this clearly for agencies operating at 50-200 inbox scale.
Shared IP pools: contamination and blacklist risks
This section covers how shared pool infrastructure operates and the specific failure points that affect senders on that infrastructure.
How shared IP pools distribute sending volume
Shared IP pools distribute sending volume across multiple IP addresses, rotating which IP each sender uses for any batch. The goal is to prevent individual IPs from exceeding safe daily volumes and spread reputation risk. For agencies running 50+ inboxes across multiple clients, the "noisy neighbor" problem becomes unavoidable.
Think of it like a carpool lane where one reckless driver affects every other car. One bad actor on your shared range gets the entire IP flagged, and every sender in that pool absorbs the consequence.
Events that degrade shared IP health
Three events cause shared IP blacklisting, none of which require your campaigns to be the problem:
Bounce rate spikes: High hard bounce rates signal list quality issues to major blacklist providers. Another sender hitting a dirty list damages your deliverability.
Spam trap hits: Spam traps trigger blacklisting at major lists. Both pristine and recycled traps degrade shared IP reputation.
Complaint rate thresholds: Gmail blocks senders at 0.1% complaint rate (1 spam complaint per 1,000 emails). One high-volume sender exceeding that threshold drags the entire IP range down.
Your campaign's shared IP blacklist risk
The core operational problem with shared IP contamination isn't the blacklist itself. It's the diagnosis delay. When inbox placement drops overnight, you spend hours checking your SPF records, reviewing your domain configuration, and auditing your list quality before discovering the IP itself is the issue, caused entirely by someone else's sending behavior.
Our infrastructure monitoring guide for agency owners details specific alert protocols that catch this faster, but the fundamental problem remains: you can't fix a contamination event you didn't cause on an IP you don't control.
SPF/DKIM/DMARC interaction on shared IPs
On shared IPs, your SPF record typically includes a provider-level "include:" mechanism rather than a specific IP. DKIM alignment remains consistent because it's tied to your domain, not the IP. The gap: even with perfect SPF, DKIM, and DMARC configuration, your authentication passes but the shared IP's reputation can still suppress delivery on providers that weight IP signals heavily. Postmark's email authentication guide covers the technical details of how SPF, DKIM, and DMARC work together to authenticate senders and protect domain reputation.
Dedicated IP pools: warmup and reputation control
This section covers how dedicated IPs function at the infrastructure level and what the setup and scaling process involves.
How dedicated IPs isolate sender reputation
With a dedicated IP, your sending behavior alone determines the IP's reputation score. No other sender affects your campaigns, and no one else's bounce rates, spam trap hits, or complaint spikes contaminate your sending range. DNS protocols like SPF, DKIM, and DMARC are essential, but dedicated IPs add the infrastructure layer that prevents those protocols from being undermined by external behavior.
For agencies managing multiple clients, this isolation means that when one client's campaign hits a deliverability issue, the other clients' campaigns continue sending normally. That operational separation is impossible on shared infrastructure.
Dedicated IP warmup: 30-90 day ramp
A new dedicated IP has no sending history, so receiving servers treat it with elevated suspicion until it builds a track record. IP warming gradually increases sending volume from a new IP over 30-90 days to establish a positive reputation before running full-volume campaigns.
Twilio SendGrid's warmup documentation states that warming can last up to 60 days. For cold email, a conservative ramp is safer: gradually scale volume over several weeks, monitoring engagement and reputation signals closely.
Inframail's help center provides specific warmup guidance for migrated inboxes, including how to adjust schedules depending on whether the domain is new or transferred. This warmup period is the primary trade-off for dedicated IP control: you gain full reputation ownership but need 30-90 days to build the sending history that makes the IP trusted.
Scaling volume: when to go dedicated
Postmark's shared vs. dedicated IP guide recommends dedicated IPs for senders exceeding 300,000 emails per month, though for cold email agencies the relevant trigger is different: you're managing multiple clients across dozens of domains, and contamination risk grows with each new client you add to a shared pool. At 50+ inboxes, the volume is both consistent and sufficient to justify dedicated infrastructure.
Inframail's 1-3 IPs: maximizing deliverability
Inframail provides dedicated US-based IPs on both plans. The Unlimited Plan ($129/month) includes 1 dedicated IP, and the Agency Pack ($327/month) includes 3 dedicated IPs. Both plans support unlimited email inboxes with no per-seat charges.
The 3-IP Agency Pack allows segmentation by client or campaign type. Assigning different clients to separate IPs protects high-priority campaigns from reputation spillover between clients. Watch Kidous walk through dedicated vs. shared IP pools for cold email in this comparison for a direct walkthrough of how this works in practice.
Real deliverability data: 50-200 inbox deployments
This section covers measured inbox placement results across different IP configurations at the inbox counts most agencies operate.
Cold email inbox rates by IP type
Moving from shared to dedicated IPs can produce a measurable inbox placement improvement. Teams switching from shared to dedicated IPs have reported measurable inbox placement improvements without changing anything else in their campaign setup. That improvement translates directly to meetings booked per 1,000 emails sent.
Shared IP pool risks for 50 inboxes
On a shared IP pool, your sends sit alongside potentially hundreds of other users, some running campaigns with lower list hygiene standards. Our Maildoso deliverability review documents exactly how shared IP issues manifest on pool-based infrastructure, including specific Mail-Tester scores and inbox rate measurements.
Dedicated IP performance for high-volume email
Inframail's platform is independently tested using Mail-Tester and GMass inbox testing. Our spam and deliverability metrics guide walks through how to replicate these tests and evaluate your infrastructure health.
"Inframail was recommended to me by a friend over two years ago. I've been using them ever since. Don't look back. Pretty solid deliverability compared to other platforms I've used in the past." - Verified user review of Inframail
Gmail vs Outlook: IP deliverability impact
Gmail evaluates both domain and IP reputation, filtering spam using a combination of signals including IP characteristics, domain reputation, and authentication alignment. The difference between shared and dedicated infrastructure shows up most visibly in inbox placement on corporate Outlook addresses. Microsoft's filtering evaluates entire shared IP ranges, and shared infrastructure consistently underperforms on Microsoft 365 inboxes. Inframail runs on Microsoft cloud infrastructure, providing institutional trust signals with Outlook-based recipients.
Cost-benefit analysis: when to upgrade to dedicated IPs
This section breaks down the monthly and annual infrastructure costs for both IP types across common inbox counts.
Managing shared IP costs: 50-200 inboxes
Google Workspace Business Starter runs $7-8.40 per user per month: 50 inboxes cost $350-420/month and 200 inboxes cost $1,400-1,680/month. Costs scale directly with client growth, increasing your infrastructure bill before you've earned revenue from new clients. Our 7-platform infrastructure cost comparison shows flat-rate infrastructure becomes cheaper than Mailforge at 43+ inboxes.
Dedicated IP costs per inbox
Inframail charges $129/month for unlimited inboxes on the Unlimited Plan, plus $5-16 per domain per year. For 50 domains amortized monthly, total infrastructure costs approximately $163/month ($129 platform + ~$34/month for domains). At 200 inboxes, the platform fee stays at $129/month. You add more domains, not more inbox charges.
Inframail doesn't include native warmup. External warmup tools like Warmbox or Lemwarm run $15-50/month per inbox. The Done-for-You package ($3,497 one-time or $499/month) includes free warmup. For self-managed accounts, factor warmup costs in separately.
ROI calculation for dedicated IP upgrade
The table below shows total 12-month infrastructure cost across three inbox counts, comparing Inframail and Google Workspace (excluding external warmup tools, which apply equally to both options):
Inboxes | Google Workspace (annual) | Inframail flat rate | 12-month savings |
|---|---|---|---|
50 | $4,200 | $1,548 | $2,652 |
100 | $8,400 | $1,548 | $6,852 |
200 | $16,800 | $1,548 | $15,252 |
These figures use Google Workspace at $7/user/month (annual commitment) and Inframail at $129/month platform fee only. Domain costs add additional expense to either option and vary by registrar.
"I can set-up inboxes in 5mins while saving money on Google Workspace subscriptions and benefit from great deliverability. All of my campaigns on Inframail are on a >10% reply rate, which is really good." - Verified user review of Inframail
Inbox count for cost-effective dedicated IP
Inframail's $129/month flat rate beats per-seat pricing at 18 inboxes (at $7/inbox Google Workspace annual) or 16 inboxes ($8.40/inbox monthly). Above 50 inboxes, monthly savings and reputation isolation both favor dedicated IPs.
When agencies should use shared vs dedicated IPs
The right IP type depends on inbox count, client volume, and how much risk you can absorb from infrastructure you don't control. This section covers each scenario.
Best shared IP strategy for 0-20 inboxes
If you're managing under 20 inboxes for a single client and just starting cold outreach, shared IP infrastructure from a provider with strong pool hygiene may be a reasonable starting point. Setup is faster, there's no warmup period, and initial cost is lower. Risk is more manageable at low volume because contamination events cause limited damage when your overall daily send is small.
The calculus changes at 20-30 inboxes, because you're generating consistent daily volume that makes you vulnerable to IP-level reputation issues you don't control.
Dedicated IPs: best use cases (50+ inboxes)
Dedicated IPs are the clear choice in three scenarios:
Multi-client agencies at 50+ inboxes: Dedicated IPs isolate each client's campaigns rather than letting shared pool contamination affect all clients simultaneously.
High-risk niches: Industries like financial services and healthcare benefit from cleaner IP histories to maintain inbox placement.
New domain builds: Fresh domains build clean reputation history from day one rather than inheriting a shared pool's existing reputation.
Scale agency campaigns, avoid IP risks
Move domains in batches rather than all at once. Start warming the new dedicated IP with lower-volume campaigns while maintaining current shared IP sends, then gradually shift volume as the new IP builds reputation. Our Maildoso to Inframail migration guide covers this batch transition for pool-based providers.
"Inframail has been absolute gold in terms of delivering a great customer experience, and allowing me to spin up cold email infrastructure at scale for my clients as easily and fast as possible." - Verified user review of Inframail
Dedicated IP switch: what to expect
Plan for a gradual ramp where new dedicated IP campaigns run at reduced volume while existing campaigns on warmed infrastructure continue at full volume. Inbox placement typically improves as the warmup progresses when the schedule is followed consistently. Budget warmup into new client onboarding timelines so campaigns launch at partial volume initially and gradually reach full send volume.
Preparing domains for cold email sending
This section covers the DNS configuration steps required before sending on either IP type, including authentication records and deliverability testing.
SPF record setup for dedicated IPs
On dedicated IPs, your SPF configuration provides tighter control and cleaner authentication. Inframail auto-configures SPF records for every domain you provision, eliminating manual DNS panel work. Watch the SPF/DKIM/DMARC setup video to see how Inframail handles bulk configuration.
DMARC for dedicated and shared IPs
On dedicated IPs, DMARC alignment is more effective because your IP reputation and domain reputation reinforce each other. On shared infrastructure, setting DMARC to "reject" can cause delivery failures if the provider's SPF include statement isn't perfectly aligned. Inframail's automated DNS configuration handles DMARC alignment correctly by default. Our Microsoft blacklist prevention guide covers DMARC-related issues for Outlook filtering.
Testing dedicated IP deliverability
Test deliverability using Mail-Tester and GMass inbox testing after domains are configured. Inframail generates IMAP/SMTP credentials automatically and exports them as CSV for direct import into cold email sending platforms like Instantly, Smartlead, or Lemlist. The Inframail setup tutorial by Shivam Gupta walks through the complete workflow, and the Inframail to Smartlead integration guide covers Smartlead-specific steps. Inframail's "phantom redirects" feature hides domain redirects from email service providers, adding an additional layer of inbox protection.
"We spent months hunting for a reliable cold-emailing stack. After repeated failures with another provider, we trialled two options - Inframail and a competitor. We chose the competitor. A month later, we switched back to Inframail." - Verified user review of Inframail
Get 1-3 dedicated US-based IPs, unlimited inboxes, and automated DNS setup for $129/month. Sign up to Inframail and get started today.
FAQs
Does a dedicated IP actually improve deliverability for 50+ inboxes?
Yes, with two conditions: the IP is properly warmed over 30-60 days and your domain authentication (SPF/DKIM/DMARC) is correctly configured. Teams switching from shared to dedicated IPs have reported measurable inbox placement improvements compared to shared pools.
How long does it take to warm up a dedicated IP exactly?
Warmup timelines typically run 30-90 days depending on volume and engagement. Inframail's inbox warmup guide covers the specific schedule for migrated domains.
What happens when a dedicated IP gets blacklisted?
Read the bounce message to identify the specific blacklist and reason, fix the root cause (spam trap hit, high bounce rate, complaint spike), then submit a delisting request. Inframail's blacklist monitoring dashboard auto-submits delisting requests once a triggering issue is resolved. Some automated lists can delist relatively quickly once the triggering issue is resolved.
Does Inframail use dedicated or shared IPs?
Inframail provides dedicated US-based IPs exclusively: 1 IP on the Unlimited Plan ($129/month) and 3 IPs on the Agency Pack ($327/month). Both plans include unlimited email inboxes with no per-seat charges. Inframail does not use shared IP pools.
How does Inframail's CSV export work with Instantly and Smartlead?
Inframail generates IMAP/SMTP credentials automatically for every inbox you provision, then exports them in CSV format. You import that file directly into Instantly's "Add Accounts" section or Smartlead's inbox import. The CSV export and sender name configuration guide covers the exact steps for structuring the file before import.
Key terms glossary
Dedicated IP: An IP address assigned exclusively to one sender, where sending reputation reflects only that sender's own behavior.
Shared IP pool: A group of IP addresses distributed among multiple senders, where all users share the same IP reputation and one sender's poor practices affect every other sender in the pool.
IP warmup: The process of gradually increasing email send volume from a new dedicated IP over 30-90 days to build a trusted sending history with receiving mail servers before running full-volume campaigns.
Inbox placement rate: The percentage of emails landing in the recipient's primary inbox rather than spam or promotions, measured using tools like Mail-Tester or GMass.
SPF (Sender Policy Framework): A DNS TXT record that specifies which IP addresses are authorized to send email on behalf of a domain, checked by receiving servers during delivery.
DKIM (DomainKeys Identified Mail): A cryptographic email authentication method that attaches a digital signature tied to the sending domain, allowing receiving servers to verify the message hasn't been altered in transit.
DMARC: A DNS policy record that defines how receiving servers handle emails failing SPF or DKIM alignment, with options to monitor, quarantine, or reject failing messages.
