Shared vs dedicated IP for email

The short version of shared vs dedicated IP: a shared IP lends you a provider's existing reputation, and a dedicated IP gives you a reputation that's entirely your own. A dedicated IP helps when you send steady, wanted mail in enough volume for mailbox providers to judge it. It can hurt when you send little or irregularly, because there's no history and no pool to cushion you.

This post covers when each makes sense, what dedicated IPs cost at the big providers as of October 2026, and why a self-hosted server gives you one by default.

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

Every email arrives from an IP address. Gmail, Outlook, Yahoo and the rest keep track of how mail from each IP behaves: complaints, bounces, spam-trap hits, whether people open and reply.

• Shared IP: many customers of a provider send through the same pool of addresses. The pool's reputation is the sum of all of them.
• Dedicated IP: only you send from the address. Its reputation reflects only your mail.

IP reputation is not the whole picture. Mailbox providers also judge your domain, which is why SPF, DKIM and DMARC alignment matter whichever IP you use. Our guide to why emails go to spam covers the other factors.

When a shared IP is the better choice

• Low or irregular volume. If you send a few hundred emails a week, or in occasional bursts, mailbox providers barely see your IP. A shared pool already has a history.
• You want zero warm-up. A shared pool is already warm. You can send on day one.
• You don't want to manage reputation. On a shared pool, the provider monitors and protects the IPs.

The trade-off is that other senders' behaviour affects you. Providers manage their shared pools, but you don't control who else is on them.

When a dedicated IP helps

• Steady, meaningful volume. If you send every day at a consistent level, a dedicated IP builds a reputation that reflects your own good practices.
• Clean lists and wanted mail. Transactional email (receipts, password resets, alerts) is mail people expect, which is good reputation-building material.
• Isolation. No neighbour's campaign can affect your placement.
• Separating streams. With more than one IP, you can keep a new or higher-volume stream away from your important transactional mail.

When a dedicated IP hurts

• Too little volume. There's no official threshold, but the principle is simple: if mailbox providers see too little mail from an IP, they can't form a good opinion of it.
• Skipping warm-up. A new IP has no history. Start at tens of emails a day and increase gradually over 2–6 weeks, sending to engaged recipients first. Our IP warm-up guide has a schedule.
• Bad list hygiene. On a shared pool, a spike in bounces is diluted. On a dedicated IP, every complaint is yours.

We saw the "no history" effect on our own server. On day one, two near-identical test emails to Gmail from two of our domains split: one landed in the inbox, the other in spam, with SPF, DKIM and DMARC all passing. Gradual, engaged sending is what fixes that.

How much does a dedicated IP cost?

As of October 2026, from third-party pricing trackers. Confirm on each vendor's pricing page.

On SendGrid, the step from Essentials ($34.95 for 100k) to Pro ($89.95 for 100k) is $55 a month, and the dedicated IP is the main difference. See our SendGrid pricing breakdown for the tiers.

Self-hosting gives you a dedicated IP by default

A VPS comes with its own IPv4 address. When you run your own mail server on it, you're on a dedicated IP automatically, with no add-on fee. The VPS typically costs $5–20 a month.

What you need to get right:

• Reverse DNS (PTR). Your VPS provider sets it. It must match a hostname that resolves back to the same IP (forward-confirmed reverse DNS). Our PTR guide shows how.
• Port 25. AWS and many other clouds block outbound port 25 by default. Check your provider.
• Warm-up. Same as any dedicated IP.
• Blocklist noise. Some lists, like UCEPROTECT level 3, list entire provider networks. That's not a listing of your IP. Spamhaus results from public DNS resolvers can also look like listings when they aren't.

You can also add more IPs. Our own server has two, and Postfix picks the outbound IP per sender domain using sender_dependent_default_transport_maps. That keeps one domain's reputation separate from the other's on the same machine.

Questions to ask before paying for a dedicated IP

Before you add a dedicated IP at a provider, or move to a plan that includes one, answer these honestly:

1. Do I send every day? Consistency matters more than any single big send. An IP that's quiet for a week and then sends a burst looks unpredictable.
2. Is my list clean? If you have old, unengaged addresses, clean them first. On a dedicated IP, every bounce and complaint counts against you alone.
3. Is authentication already right? SPF, DKIM, DMARC alignment and reverse DNS should pass before you change IPs. A new IP won't fix a broken setup. Our deliverability fix covers exactly that.
4. Do I have time to warm it up? Plan for 2–6 weeks of gradual increases. If a launch is next week, stay on the shared pool for now.
5. Am I separating streams? If marketing and transactional mail share one IP, a campaign that draws complaints can affect your password resets. Separate IPs, or separate providers, avoid that.

Which should you choose?

• Sending little or irregularly, and happy on a hosted API: stay on a shared pool.
• Sending steadily and paying for an add-on IP: compare that fee with a server you own.
• Want your own IP plus no per-email fees: a self-hosted server, warmed up properly.

If you want the server and the IP without the upkeep, see our managed email server, or compare all plans on the pricing page.