Guides

Dedicated or shared IP for email: when it's really worth the cost

Inherited or personal reputation: when sending volume justifies a dedicated IP, how to warm it up, and how to verify it before you buy.

UptimeMag editorial team · 30 October 2026 · 4 min read

IP dedicato o condiviso per inviare email: quando conviene davvero pagarlo

Anyone sending newsletters or transactional emails from a server or SMTP service will eventually face this choice in their provider's control panel: stick with a shared IP or pay for a dedicated IP. The question that matters isn't "which works better" but "does my sending volume justify the expense and effort of warming it up?" Let's look at the numbers.

Shared IP: your reputation isn't entirely your own

On a shared IP, the same address serves hundreds or thousands of different senders. If most of them send clean email, newcomers benefit too: reputation is already built by others and no warm-up is needed. The downside is that a single problematic sender on the same IP can degrade deliverability for everyone else.

Dedicated IP: your reputation is yours alone, but starts from zero

A brand-new dedicated IP has no sending history. Gmail, Outlook and Yahoo treat it as an unknown source until it proves, through gradually increasing sending volume, that it's a legitimate sender—this is the warm-up process, described in Mailjet's official guide to dedicated IPs. Until it's been warmed up, sending full volume immediately can cause email providers to throttle traffic, reject messages or route them to spam, according to Mailjet's documentation.

The threshold: when volume justifies the expense

This needs a number, not a "it depends". Twilio SendGrid's official guide is explicit: for lower email volumes, you generally send on a shared IP, which requires no individual warm-up. A dedicated IP is recommended only if you send more than 50,000 emails per month. Below that figure, a dedicated IP risks staying "cold" too long due to insufficient traffic to build reputation.

Another industry source, CaptainVerify, raises the bar, discussing effectiveness for sending volumes above 100,000 emails per year, and recommends starting with a shared IP and moving to a dedicated one as volume grows—consistent with SendGrid's threshold. Mailjet's documentation also confirms this principle: a dedicated IP is most effective when email volume is both high and consistent; if volume is lower, irregular or occasional, a shared IP is more efficient because its reputation is backed by a continuous flow of email traffic.

Monthly sending volume Recommended option Source
Below 50,000 emails/month Shared IP Twilio SendGrid
Above 50,000 emails/month Dedicated IP possible Twilio SendGrid
Above 100,000 emails/year (~8,300/month) Dedicated IP effective CaptainVerify
Low, irregular or occasional volume Shared IP Mailjet

Warm-up: how long it takes and how to do it

Warm-up involves gradually increasing the number of emails sent from a newly activated dedicated IP. According to SendGrid's guide, if you plan to send 90,000 emails in a month, you start with the first 50 emails on day one and increase volume day after day until you reach your target, prioritising the most engaged recipients. The same guide notes that warm-up can take up to 60 days.

There's a technical detail few consider: reputation isn't permanent. According to SendGrid, most reputation systems retain data for only 30 days, so you shouldn't go more than 30 days without sending on a given IP, or you'll need to warm it up again. Anyone with seasonal sending (Christmas promotions, one-off campaigns) should account for this: a dedicated IP left idle for a month loses all the work you put in.

Mailjet adds a practical rule about pacing: if your regular sending is three times a week, it's better to increase volume on those sending days rather than introduce artificial sends just for warm-up.

How to verify an IP's reputation before you buy it

A "new" dedicated IP when you purchase it is often not new at all: it may have been used in the past by other customers of the same cloud provider or hosting company, and may carry old complaints with it. Before activating it, it's worth checking it against the most commonly consulted public lists: Spamhaus, Talos Intelligence (formerly SenderBase) and aggregator tools like MXToolbox or multirbl.valli.org, which query dozens of DNSBLs together.

A check that's practically always skipped: Talos Intelligence also checks the reputation of IPs numerically adjacent to the one you're about to activate, because a "clean" IP surrounded by addresses already flagged in blocks (for example from the same /24 block of a budget hosting provider) can still start with more aggressive filtering from some email providers. It's worth asking your provider whether the IP is newly assigned or recycled, and getting confirmation before starting warm-up: restarting on an IP already tainted from day one means losing the first weeks of sending without any reputation benefit.

The prerequisite that doesn't change: SPF, DKIM, DMARC

Whether the IP is shared or dedicated, these three authentication protocols remain the first filter that email providers apply before even looking at your address reputation: without SPF, DKIM and DMARC correctly configured, no warm-up strategy holds up. We've already covered them on UptimeMag in a dedicated article on the practical configuration of the three DNS records: if you haven't set them up yet, do it before spending money on a dedicated IP, not after.

Written with the help of artificial intelligence and checked by the editors (EU AI Act, art. 50).