"Do I need a dedicated IP?" is one of the most common questions buyers ask a sending provider, and it is one of the most misunderstood. A dedicated IP gives you control over your own sending reputation, but it also gives you sole responsibility for it. For many senders, especially those with modest or irregular volume, a well-managed shared pool is the better choice. For others, a dedicated IP is worth the extra work. This guide explains what shared and dedicated IPs are, how reputation works for each, the factors that should drive the decision (volume, consistency, mail type, control and risk), what warm-up involves, what a dedicated IP costs you in effort even before any fee, and how to decide with a simple framework. We sell both options, so we describe the trade-offs plainly; see our dedicated IPs page for what we offer. We do not quote prices here, and thresholds that vendors cite for "enough volume" are rules of thumb, not rules.
What is a shared IP?
A shared IP address is one that a sending provider uses for many customers. Mailbox providers see mail from that address and form a view of it based on everything sent through it. A responsible provider groups customers with similar practices, monitors the pool, removes abusers quickly and warms and manages the addresses itself. Because the volume from many customers adds up, a shared IP usually has steady traffic, which mailbox providers prefer to sporadic bursts.
What is a dedicated IP?
A dedicated IP address is assigned to one customer. Only your mail leaves it. The reputation attached to the address depends entirely on your own behaviour: your list quality, complaint rate, bounce rate, engagement and sending pattern. There is no pool to absorb a bad day, and no other customer to blame or benefit from. That is what makes a dedicated IP powerful for good senders and unforgiving for careless ones. For the underlying concepts, see email reputation.
Shared vs dedicated: a comparison
| Factor | Shared IP | Dedicated IP |
|---|---|---|
| Reputation | Pooled; influenced by other senders in the pool | Entirely yours |
| Control | Limited; the provider manages the pool | High; you decide streams, limits and pacing |
| Warm-up | Already warm and steady | You must warm it up gradually |
| Low or irregular volume | Usually better: steady pool traffic supports you | Risky: gaps and spikes can hurt reputation |
| High, consistent volume | Works, but you are tied to the pool | Often better: you build and control your own record |
| Risk of other senders | Present, reduced by provider policy | None |
| Your own mistakes | Diluted by the pool, but still counted | Fully visible on your IP |
| Effort | Low | Higher: warm-up, monitoring, list discipline |
| Cost | Typically included with sending plans | Usually an extra fee; check current terms |
Factors that should drive the decision
Volume and consistency
Mailbox providers learn from patterns. An address that sends a steady stream is easier to judge than one that sends nothing for weeks, then a large campaign. If your volume is small or irregular, a dedicated IP may not produce enough signal to build a good reputation, and it will look unpredictable. Vendors often quote thresholds for when a dedicated IP makes sense; treat them as rough guidance, not a guarantee, and consider consistency more than totals.
Mail type
Transactional mail such as receipts and password resets is expected and highly engaged, and it is sensitive to delay. Isolating it on its own IP, or at least its own stream, protects it from the ups and downs of marketing campaigns. Marketing mail has more variable engagement and complaint rates. Many senders use one stream for each. See separating the streams and what transactional email is.
Reputation risk
If your own practices are strong, a dedicated IP lets you benefit from them fully. If your list quality is uneven, a dedicated IP will expose it quickly. Fix list hygiene first. See list cleaning.
Control and compliance needs
Some organisations need predictable IP addresses, for example to allow-list them, to publish them in SPF or to satisfy internal policy. A dedicated IP gives you a stable address. Be aware that a stable address is not the same as a good reputation.
Operational capacity
A dedicated IP needs someone to warm it up, watch bounces and complaints, check blocklists and respond to problems. If nobody on your team can do that, shared infrastructure managed by a provider may be safer.
A simple decision framework
- Is your sending volume consistent? If it is small or sporadic, start on shared infrastructure.
- Is your list healthy? If bounces or complaints are high, fix them before considering a dedicated IP.
- Do you need isolation? If you have a high-value stream such as transactional mail that must not be affected by marketing, consider a dedicated IP or at least a separate stream for it.
- Do you have capacity to manage it? Someone must own warm-up and monitoring.
- Are you ready to warm up? If you cannot ramp volume gradually, a dedicated IP will struggle.
If you answer yes to most, a dedicated IP is worth considering. If not, improve the weak points or stay on shared infrastructure.
Warm-up: what it involves
A new IP has no history, so mailbox providers treat it cautiously. Warm-up means sending increasing volumes over time, beginning with your most engaged recipients, while keeping bounces and complaints low. The schedule depends on your volume and the providers you send to, and you should adjust it based on what you see rather than following a fixed table. Our warm-up guide covers the process in detail. Key points:
- Start with recent, engaged recipients and the mail type with the highest engagement.
- Increase volume gradually and pause or slow down if you see deferrals, blocks or rising complaints.
- Spread sends to avoid sudden bursts, especially to a single provider.
- Keep sending regularly once warm; long gaps can reduce a good reputation.
- Do not mix risky mail into the warm-up.
Monitoring a dedicated IP
- Authentication. SPF, DKIM and DMARC alignment, plus reverse DNS for the IP. See authenticating your sending domain.
- Provider dashboards. Gmail reputation in Postmaster Tools. See Postmaster Tools setup.
- Blocklists. Check regularly. See blocklist checks and the free blocklist check.
- Bounce and complaint trends. By provider and campaign. See bounce codes explained.
- Automated monitoring. Reputation monitoring can alert you to changes.
Common myths
- "A dedicated IP fixes spam placement." It does not. Spam placement is driven by recipient behaviour, list quality and content.
- "Shared IPs are always bad." A well-run pool is a sensible choice for many senders.
- "I need a dedicated IP at a certain number of emails." Volume matters, but consistency and practices matter more.
- "I can buy a dedicated IP and send my whole list on day one." A cold IP needs warm-up.
- "More IPs are better." Spreading a small volume across many IPs gives each too little history.
When to revisit the decision
Review your choice when volume changes substantially, when you add a new type of mail, after a deliverability incident or when you change providers. See the migration checklist if you are moving, since new IPs always require warm-up. For authentication and reputation basics, the deliverability page explains how we manage our own infrastructure.
Talk through dedicated IPs See how dedicated IPs work with our relay, and what warm-up and monitoring involve before you decide.
References and further reading
Frequently asked questions
Do I need a dedicated IP for email?
Not necessarily. Consistent high volume, clean practices and capacity to manage it favour a dedicated IP. Low or irregular volume usually does better on well-managed shared infrastructure.
Will a dedicated IP improve my deliverability?
Only if your practices are good. It gives you control of your own reputation, but it does not fix list quality, content or complaint problems.
Does a dedicated IP need warm-up?
Yes. A new IP has no history, so you increase volume gradually, starting with your most engaged recipients, and adjust to what you see.
Can I use a dedicated IP for transactional mail only?
Yes. Many senders isolate transactional mail on its own IP or stream so campaign activity does not affect time-sensitive messages.
Are shared IPs bad for reputation?
Not inherently. A well-run pool groups similar senders, monitors abuse and keeps steady traffic. The risk is other senders in the pool, reduced by provider policy.