When you're starting out with email, things seem simple. You write a campaign, hit send, and it lands in someone's inbox. But the more you learn about email marketing, the more you realize there are layers to it, such as, list hygiene, authentication, domain reputation, and sending infrastructure. Each one plays a role in whether your emails actually reach the people you're sending to. One of those layers is the IP address your emails are sent from. And there are two kinds: shared and dedicated.
In this guide, we're breaking down what a dedicated IP is, how it differs from a shared one, and how to figure out which one makes sense for where you are right now.
What is a dedicated IP for email?
A dedicated IP is an IP address that is assigned exclusively to one sender. When you send emails from a dedicated IP, you are the only one using that address. No other brand, company, or sender shares it with you. The reputation of that IP is built entirely by your sending behavior, and mailbox providers evaluate it based on your activity alone.
To understand why that matters, it helps to know what an IP address actually does in the context of email. Every email you send travels from an IP address. This is a unique numerical address that mailbox providers like Gmail, Yahoo, and Outlook use to identify the source of an email. Think of it as a return address on an envelope, except instead of telling the recipient who you are, it tells the mailbox provider's servers where the email is coming from and whether that source can be trusted.
There are two types of IP setups for sending email: shared and dedicated.
With a shared IP, multiple senders are grouped together on the same address. Your ESP manages the pool, and the reputation of that IP is a collective outcome of everyone sending from it. If the other senders maintain clean lists and good practices, you benefit. If one of them sends to a purchased list or triggers a spam trap, your deliverability can take a hit even if you've done nothing wrong.
A shared IP is like a co-working space with a shared reception desk. If someone else in the building is rude to visitors, it reflects on the whole building's reputation, including yours. A dedicated IP is like having your own office with your own front door. Your reputation is built entirely on how you operate.
With a dedicated IP, mailbox providers evaluate your sending patterns, your volume, your bounce rates, your complaint rates, and your engagement in isolation. Your inbox placement is tied directly to what you do, not what someone else on the same IP happens to be doing on any given day.
Why does IP reputation matter for email deliverability?
When your email hits a mailbox provider's server, it doesn't just look at your content or subject line. It looks at where the email is coming from. One of the first things it checks is the reputation of the IP address that sent it.
IP reputation is essentially a trust score. Mailbox providers like Gmail, Yahoo, and Outlook track the sending history of every IP address over time and use it to decide whether your emails deserve the inbox or the spam folder.
What mailbox providers are looking at:
How many emails from that IP bounced
How many recipients marked those emails as spam
Whether the IP has hit any known spam traps
How recipients are engaging with emails from that IP (opens, clicks, ignores)
A strong reputation means your emails are more likely to reach the inbox. A poor one means they get filtered into spam or blocked entirely.
How this plays out on shared vs. dedicated IPs
On a shared IP, that reputation is shaped by every sender using it. You could be doing everything right, but if another sender on the same IP is generating high complaint rates or bouncing off bad lists, the overall reputation drops, and your emails suffer too. You're essentially sharing a credit score with strangers.
On a dedicated IP, the reputation is yours alone. Good engagement, low complaints, and clean bounces all work in your favor. And if something goes wrong, you know it's because of something on your end, which means you can actually diagnose and fix it instead of guessing whether a deliverability dip was caused by your campaign or someone else's.
IP reputation isn't something you set and forget. It's built over time through consistent, healthy sending behavior, and it can be damaged quickly by a single bad send, a spike in complaints, or a sudden jump in volume. Whether you're on a shared or dedicated IP, reputation is the foundation that everything else in deliverability sits on. The difference is how much of it you actually control.
Do You Need a Dedicated IP or Is a Shared IP Enough?
There's no universal right answer here. The best IP setup depends on where your email program is today, how much volume you're sending, and how much control you need over your deliverability. The way to figure it out is to ask yourself a few honest questions.
Start with volume.
Dedicated IPs need a consistent sending volume to maintain a healthy reputation. If you're sending fewer than 50,000 emails a month, or if your sending is irregular with big gaps between campaigns, a shared IP is likely the better fit. Mailbox providers need ongoing activity from an IP to form a reputation. Too little volume on a dedicated IP and your reputation either doesn't build at all or becomes fragile because a single bad campaign carries outsized weight.
If you're consistently sending 100,000+ emails a month and that number is steady or growing, a dedicated IP starts to make a lot more sense.
Then think about control.
Ask yourself how much visibility you currently have into your deliverability, and how much you want. On a shared IP, you're trusting your ESP to manage the pool and keep bad senders in check. For many senders, that's perfectly fine. But if you've reached a point where you want to own your sender reputation entirely, diagnose issues without guessing whether they came from your side or someone else's, and have direct control over how mailbox providers perceive your sending, that's a signal you've outgrown shared infrastructure.
Consider what you're sending.
If you're sending a mix of transactional and marketing emails, a dedicated IP (or even multiple dedicated IPs) gives you the ability to separate those streams. Transactional emails like password resets and order confirmations need to land in the inbox every time. Mixing them with marketing campaigns on the same IP means a promotional send that generates complaints could drag down delivery of your transactional messages too.
Factor in cost.
Dedicated IPs aren't free. Pricing across providers typically ranges from about $25 to $250 per month per IP, depending on the provider and service level. Some providers include a dedicated IP in higher-tier plans, while others charge it as an add-on. Beyond the monthly cost, there's also the effort involved. A dedicated IP starts with zero reputation, which means you'll need to go through a warmup process, gradually increasing your sending volume over several weeks so mailbox providers learn to trust the new IP. That takes time and discipline.
A quick way to think about it:
Shared IP makes sense if you're sending under 50,000 emails a month, your volume fluctuates, you're early in your email program, or you don't have the bandwidth to manage warmup and reputation monitoring.
Dedicated IP makes sense if you're consistently sending 100,000+ emails a month, you want full ownership of your sender reputation, you need to separate transactional and marketing email streams, or you've experienced deliverability issues caused by other senders on your shared IP.
The in-between zone, roughly 50,000 to 100,000 emails a month, is where it becomes a judgment call. If your deliverability is solid on a shared IP and you're not running into issues, there may be no reason to switch yet. But if you're seeing inconsistencies you can't explain or you're planning to scale, it's worth having the conversation with your ESP sooner rather than later.
Best Practices for Managing a Dedicated IP
Getting a dedicated IP is the easy part. Keeping it healthy is what actually determines whether it helps or hurts your deliverability. Here are 6 practices that will keep your dedicated IP in good shape.
1. Warm up your IP before sending at full volume
2. Separate your transactional and marketing streams
Password resets, order confirmations, and verification codes should never share an IP with promotional campaigns. Keep them on separate dedicated IPs so a bad marketing send doesn't tank deliverability for messages your users are actively waiting for.
Even after your IP is warmed up and your streams are separated, the ongoing work is what keeps your reputation intact. These next practices are about the daily and weekly habits that matter.
3. Monitor your IP reputation regularly
Don't wait for deliverability to drop before checking on your IP. Build a habit of reviewing:
Google Postmaster Tools for how Gmail views your IP
Blacklist monitoring tools to catch listings early
Bounce and complaint rate trends week over week
A small dip caught early is easy to fix. A reputation problem that's been building for weeks is not.
4. Keep your lists clean
On a dedicated IP, every spam trap hit, every hard bounce, and every complaint lands squarely on you. There's no shared pool to absorb the impact. Remove hard bounces immediately. Honor unsubscribes without delay. Validate new addresses at the point of collection. If a segment of your list hasn't engaged in six months or more, suppress them or run a re-engagement campaign before continuing to send.
5. Send on a consistent schedule
Mailbox providers like predictability. A steady sending pattern, roughly the same volume at roughly the same frequency, builds trust over time. What they don't like is erratic behavior. Going from 100,000 emails on Monday to zero for two weeks and then 300,000 on a random Thursday looks suspicious, even if every email is legitimate.
6. Watch your sending speed, not just your volume
Volume is how many emails you send. Speed is how fast you send them. Even if your total volume is reasonable, blasting it all within a short window can trigger rate limiting or throttling from providers like Outlook and Yahoo. Spread your sends across a longer window or use throttling controls to manage how quickly emails leave your IP per provider.
How SendPost Handles Dedicated IPs
SendPost is an email infrastructure platform that helps high-volume senders and ESPs manage deliverability, routing, and IP reputation from one place. For customers who need full control over their sender reputation, we offer dedicated IP pools as part of our infrastructure, with built-in tooling to make setup, warmup, and ongoing management straightforward.
You're not left to figure out warmup and routing on your own. The platform automates the heavy lifting while still giving you full control when you want it.
What you get with dedicated IPs on SendPost:
Automatic IP warmup. SendPost gradually ramps volume and throttles per ISP, so your new IP builds a reputation without hurting deliverability.
IP pool routing. Group IPs into pools and distribute traffic using round-robin or volume-based routing across mail streams and customer segments.
Transactional and marketing separation. Run dedicated pools for transactional email so bulk campaigns never impact your most critical messages.
Hybrid setups. Run high-priority streams on dedicated IPs and lower-volume streams on shared pools, all within the same account.
No cap on IP pool configurations. Structure as many pools, IPs, and routing rules as your setup requires.
You decide the strategy, and SendPost handles the execution. Talk to us about your IP setup →
Frequently Asked Questions
What's the difference between a dedicated IP and a shared IP?
A dedicated IP is used exclusively by your organization, so your sender reputation is shaped entirely by your own sending behavior. A shared IP is used by multiple senders, and the reputation is a collective outcome of everyone on that address. Dedicated gives you full control, shared works well for lower-volume senders.
How many dedicated IPs do I need?
It depends on your volume and mail streams. A common setup is one dedicated IP for transactional email and one or more for marketing. High-volume senders doing millions per month may need multiple IPs per stream to distribute load.
How long does IP warmup take?
Typically, two to four weeks. You gradually increase volume while monitoring bounces and engagement. Some platforms, like SendPost, automate this and adjust in real time based on ISP responses.
Can I switch from shared to dedicated IPs later?
Yes. SendPost supports seamless upgrades from shared to dedicated IP pools at any time. You can also run hybrid setups where some traffic uses dedicated and some stays on shared.
Will a dedicated IP guarantee inbox placement? No. IP reputation is one factor, but deliverability also depends on domain reputation, content quality, authentication (SPF, DKIM, DMARC), list hygiene, and engagement. A dedicated IP removes the variable of other senders affecting your reputation, but it won't fix problems elsewhere.
What happens if my dedicated IP gets blacklisted? It means a blacklist provider has flagged your IP, usually due to complaints, spam trap hits, or suspicious sending patterns. Some blacklists delist automatically after a few days, others require a manual request. Catch it early through monitoring and have a fallback routing plan ready.
Is a dedicated IP worth it for low-volume senders? Generally, no. Dedicated IPs need steady volume to maintain a reputation. If you're sending fewer than 50,000 emails a month or your schedule is inconsistent, a shared IP is usually the better fit.
Do I need a dedicated IP for transactional email? Not always, but it's good practice at scale. A separate dedicated IP for transactional email ensures that marketing sends with higher complaints don't affect the deliverability of messages like password resets and order confirmations.
