IP warming: how to earn a new IP's reputation without getting it blocked
IP warming is gradually ramping the volume you send from a new dedicated IP — over roughly four to eight weeks — so mailbox providers learn to trust it before you send at full volume. It matters because a brand-new IP has no history, so a sudden burst of thousands of emails looks exactly like a spammer who just bought a fresh IP to blast a harvested list, and providers respond by throttling, deferring or blocking your mail. You warm it by starting small — 50 to 200 emails a day to your most engaged recipients — increasing no more than about 50% day over day, expanding to less-engaged segments as you go, and sending every single day so the momentum doesn’t reset. Throughout, you watch the gates: bounce rate under 2%, complaint rate under 0.1%. But the step almost everyone skips is step zero: clean, verified data and live SPF, DKIM and DMARC before email number one, because most warming failures are data-quality failures, not scheduling ones. Two honest caveats: you only warm dedicated IPs — shared IPs come pre-warmed, and under about 50,000 emails a month you probably shouldn’t have a dedicated IP at all — and the automated “warmup tools” that fake engagement are for cold email, not for marketing or transactional mail. The whole discipline is the reputation lesson made literal: trust is earned slowly, one consistent day at a time, and lost in an afternoon if you rush it.
Why a cold IP gets treated like a spammer
The logic behind warming is simpler than the schedules make it look. Every new IP and every new domain starts with no reputation, so mailbox providers — Gmail, Outlook, Yahoo, Apple Mail — have no history to tell them whether you send wanted mail or not (Mailflow Authority, 2026). When a fresh IP suddenly sends 50,000 emails on day one, that pattern looks exactly like what happens when a spammer acquires a new IP and blasts a harvested list before it gets burned — a pattern providers have seen millions of times (InboxStack, 2026).
Their response is automatic and aggressive. A cold IP sending at volume gets throttled, sees its mail deferred with 421 or 450 codes, lands in spam across providers, and in severe cases gets the IP blacklisted on Spamhaus or Barracuda (BulkEmailSetup, 2026). Warming solves this by introducing the IP slowly, with small volumes to engaged recipients, building a positive reputation over time — which is the same reputation our guide on sender reputation describes, here being built from zero rather than defended.
IP warming versus domain warming
Two reputations are in play, and they warm on different clocks. IP warming builds trust for a specific sending IP and applies only to new or dormant dedicated IPs, running four to eight weeks; domain warming builds trust for your sending domain, applies to any new domain regardless of IP, and takes about two to four weeks (Mailflow Authority, 2026). Mailbox providers evaluate the two as separate signals, so if you launch a new domain on a new dedicated IP, both need warming simultaneously (Mailflow Authority, 2026).
The distinction matters because it tells you what you’re actually dealing with. Moving to a new dedicated IP means an IP warmup; changing providers while staying on shared IPs may mean re-establishing domain reputation with the new infrastructure; and reputation is even tracked per address, so a warmed domain doesn’t automatically lend its trust to a brand-new mailbox on it (SyncGTM, 2026). Knowing which reputation is cold tells you which clock you’re on.
The schedule: slow, engaged, and every single day
A warming schedule is a set of operating rules, not a rigid calendar, but the shape is consistent. You start at roughly 50 to 200 emails a day, sent only to your most engaged recipients — people who opened or clicked in the last 30 days — because their positive engagement builds reputation fastest, and you let no one else touch the new IP in the first two weeks (Mailflow Authority, 2026). From there you increase by no more than about 50% day over day, expanding the engagement window as you go.
| Stage | Audience | Volume behaviour |
|---|---|---|
| Weeks 1–2 | Opened/clicked in last 30 days | Start 50–200/day, ramp ≤50% day-over-day |
| Weeks 3–4 | Expand to last-60-day engaged | Continue ramping if metrics stay healthy |
| First 45 days | Avoid anyone inactive 90+ days | Approach full volume |
Four rules govern the whole ramp. Send every day, because gaps reset your momentum. Warm to your average daily volume, not your peak — if you blast 50,000 once a week but average 7,000 a day, warm to 7,000 (Prospeo, 2026). Keep the same sender name and address throughout, since changing mid-ramp confuses providers’ algorithms. And distribute each day’s volume across Gmail, Microsoft and Yahoo rather than dumping it all into one, because you’re effectively running three warmups at once, and Microsoft’s filtering is stricter enough in 2026 to warrant an extra week for M365-heavy audiences (Prospeo, 2026). A useful trick sits underneath all of this: route your transactional mail — receipts, password resets, confirmations — through the new IP first, because its very high engagement gives providers the cleanest possible early read before any marketing volume arrives (Prospeo, 2026).
The gates you watch the whole way
Warming is metric-gated, meaning you advance only when the numbers stay healthy. The two hard limits are a bounce rate under 2% and a spam-complaint rate under 0.1%; a bounce rate above 5% or complaints above 0.3% mean stop immediately and fix the cause before sending more (Mailflow Authority, 2026). Deferrals need a calmer read: some 421 responses are normal during warming and represent ISP throttling rather than failure, so your mail server should retry automatically, but sustained mass deferrals mean reduce volume for 24 to 48 hours and let the retries clear (Prospeo, 2026).
You also watch the trend, not the thresholds alone. In Google Postmaster Tools your reputation should climb over the ramp, and inbox-placement tests should improve as you progress. Warming is genuinely complete only when you can send your target volume with a delivery rate above 97%, bounce under 2%, complaints under 0.1%, and consistent inbox placement across providers (BulkEmailSetup, 2026). Until every gate holds at your target volume, you’re still warming.
Step zero is clean data, not the schedule
Here’s the part most warming guides bury, and it’s the part that decides success. The most common way a warmup fails has nothing to do with the schedule: it’s dirty data. The classic disaster is provisioning a fresh IP, sending the first campaign to 10,000 unverified contacts, and watching 40% land in spam with a 5% bounce rate — reputation cratered before it began, and no schedule could have saved it, because it was a data-quality problem, not a scheduling one (Prospeo, 2026).
So two things happen before email number one. You verify your entire list — catching invalid addresses, catch-all domains, spam traps and honeypots — to keep bounces under 2% from the first send (Prospeo, 2026). And your authentication is already live and passing, because SPF, DKIM and DMARC failures cancel out the reputation work you’re trying to do (SyncGTM, 2026). This is exactly why our guides on list hygiene and authentication come first: warming a dirty list on unauthenticated infrastructure is warming a hole.
Do you even need to warm an IP?
The honest question comes before the schedule, and for many senders the answer is no. Warming applies only to dedicated IPs that are new or have been dormant more than about 30 days; if you’re on a shared IP, the pool is already warmed by other senders’ traffic and the provider manages its reputation, so you don’t warm it yourself (Prospeo, 2026). And under roughly 50,000 to 100,000 emails a month, a shared IP is usually the better choice, because a dedicated IP can’t generate enough consistent volume to hold a stable reputation in the first place (Prospeo, 2026).
There’s a deeper version of the same honesty. A lot of deliverability problems blamed on “not warming enough” are really caused by old lists, poor segmentation and inconsistent cadence — and trying to fix those by sending slower is backwards, because a warming schedule only works when the underlying program is already disciplined (ReachInbox, 2026). So the first question isn’t how to warm an IP; it’s whether a dedicated IP is even your problem, or whether your reputation, list and consistency are. If your volume doesn’t justify dedicated infrastructure, warming is a solution to a problem you don’t have — which is exactly the kind of thing our guide on choosing your email infrastructure is meant to help you work out before you provision anything.
The warmup-tool trap, and where managed warming fits
A whole category of “warmup tools” exists, and it’s worth understanding what they actually do. Tools like Warmbox and Mailreach exchange artificial emails between a network of inboxes to manufacture engagement signals, and they’re built for cold-outreach domain warming — not for marketing or transactional IP warming (Mailflow Authority, 2026). Point one at a marketing setup and it generates fake engagement that never teaches providers your real audience wants your real content, so your actual campaigns keep landing in spam. For marketing and transactional warming there is no substitute for real recipients engaging with real content, and much of this tool category exists mainly because senders skip list verification — clean data is the only warmup “hack” that reliably works (Prospeo, 2026).
This is where our own offering fits, said plainly. Warming a dedicated IP well is a daily, weeks-long discipline — the ramp, the segmentation, the per-provider distribution, the throttling response — and it’s exactly the kind of thing we handle as part of the email infrastructure we run: a defined warming schedule with automatic throttling when providers push back, overflow to a shared pool so nothing is ever forced onto a cold IP, and monitoring across mailbox providers throughout. But the honest gate still comes first — if your volume doesn’t call for a dedicated IP, we’ll tell you to stay on shared infrastructure and skip warming entirely, because selling you a warmup you don’t need would be the opposite of the point. Warming is the reputation lesson from our pillar on reaching the inbox made operational: trust is earned slowly and lost fast, whether a machine or a person is minding the ramp.
Frequently asked
- What is IP warming?
- IP warming is the practice of gradually increasing your sending volume from a new or dormant dedicated IP address over several weeks, so that mailbox providers can build trust in it before you send at full volume. A brand-new IP has no sending history, so when providers see it suddenly send thousands of emails, the default assumption is that it's a spammer who just acquired a fresh IP — and they throttle, defer or block it. Warming avoids that by starting with small volumes to your most engaged recipients and ramping up slowly, demonstrating over time that your mail is wanted.
- How long does IP warming take?
- Typically four to eight weeks to reach full volume safely. Senders with a small target volume and a clean, highly engaged list can sometimes finish in three to four weeks, while high-volume senders reaching hundreds of thousands or millions a day should expect six to eight weeks or more. You should never rush warming below two weeks, because ramping too fast makes providers throttle or block your mail. Domain warming, which is separate, takes about two to four weeks — and if you're launching a new domain on a new dedicated IP, both need warming at the same time.
- What's the difference between IP warming and domain warming?
- They build two different reputations that mailbox providers evaluate independently. IP warming builds trust for a specific sending IP address and applies only to new or dormant dedicated IPs, taking four to eight weeks. Domain warming builds trust for your sending domain and applies to any new sending domain regardless of IP, taking two to four weeks. If both your domain and your dedicated IP are new, warm them simultaneously. Shared IPs don't need IP warming at all, because they're already warmed by the other senders' traffic in the pool — but you still warm a new domain and maintain list hygiene.
- Do I need to warm my IP?
- Only if you're on a dedicated IP that's new or has been dormant for more than about 30 days. If you're on a shared IP — which is the right choice for most senders under roughly 50,000 to 100,000 emails a month — the provider manages the pool's reputation and you don't warm the IP yourself. In fact, many problems blamed on 'not warming enough' are really caused by weak lists, poor segmentation or inconsistent sending, which a warming schedule can't fix. The honest first question isn't how to warm an IP, but whether a dedicated IP is even the right infrastructure for your volume.
- Do email warmup tools work for marketing email?
- No — and this is a common, expensive mistake. Automated warmup tools work by exchanging artificial emails between a network of inboxes to manufacture engagement signals, and they're designed for cold-outreach domain warming, not for marketing or transactional IP warming. Using them to warm a marketing setup generates fake engagement that doesn't teach mailbox providers your real audience wants your real content, so your actual campaigns still land in spam. For marketing and transactional warming you need real recipients engaging with real content — and clean, verified data, which is the single fix that eliminates most warmup failures.