The logic is the same as warming a new domain, but the reputation being built attaches to the IP address that connects and delivers your mail rather than to the domain in your From: line. A fresh dedicated IP has no sending history, so a sudden flood of mail from it looks like a newly compromised host — precisely the pattern receivers block. You build IP reputation the same way you build domain reputation: by sending steadily increasing, well-engaged volume until providers learn the IP is a legitimate source.
Do you even need a dedicated IP?
Warm-up is only worth doing if a dedicated IP is right for you in the first place. A dedicated IP needs consistent, substantial volume to stay warm — as a widely-used rule of thumb, roughly tens of thousands of messages per week, sent regularly. Below that, the IP never accumulates enough recent activity to hold a stable reputation, and you’re better off on a well-run shared pool where established volume from other reputable senders keeps the IP warm for you. If you send low or spiky volume, stay shared — see shared vs dedicated sending IP for the full decision. The rest of this guide assumes you’ve decided a dedicated IP is justified.
Get the foundation right first
Before the first send, make sure the IP’s technical setup is clean. Confirm forward-confirmed reverse DNS (a PTR record whose hostname resolves back to the IP) with the Reverse DNS Checker — receivers check this on connection and a missing or mismatched PTR alone can sink a warm-up. Publish and align SPF, DKIM and DMARC so the mail authenticates, and verify the whole picture with the Email Health Check. Warming an IP that fails these checks just teaches receivers to distrust it.
Segment by engagement, and lead with your best
As with a domain, the recipients you choose first decide how fast reputation builds. Positive engagement is the strongest trust signal and complaints are the most damaging, so send the earliest, lowest-volume days only to your most engaged contacts — recent openers, clickers and buyers. These people generate the opens and near-zero complaints that push a new IP’s reputation up quickly. Widen to less-engaged segments only once the IP is established. Verify every segment with the Email Verifier first, because a bounce or trap hit early in an IP warm-up does outsized damage when there are few positive signals to offset it.
Stage the daily increases
There is no official schedule — the right pace is whatever the receivers tolerate. The principle is to raise the daily cap in small steps and let provider behaviour set your speed. Many senders start in the low tens of messages and roughly double each day, holding whenever a provider starts deferring. Here is an illustrative ramp to show the shape; treat it as a pattern, not a fixed rule:
Illustrative daily ramp — adjust to receiver response:
Day 1 ~50 messages most engaged contacts only
Day 2 ~100
Day 3 ~500
Day 4 ~1,000
Day 5 ~5,000
Day 6 ~10,000
Day 7+ increase ~2x/day while reputation stays clean
Split the day's volume across your main receivers (Gmail,
Yahoo, Outlook) roughly in proportion to your list. If any
provider defers or throttles, hold that provider's volume.A few practical points. Warm each major receiver in proportion to your list — Gmail, Yahoo and Outlook each score you independently, so a healthy Gmail reputation doesn’t carry Outlook. Keep the cadence consistent: an IP that sends daily looks far healthier than one that sends in weekly bursts, and gaps let reputation decay. And treat deferrals (4.x.x responses) as instructions to slow down — hold that provider’s volume rather than hammering retries, which only compounds the problem.
Watch blocklists and Postmaster Tools
- Blocklists. A new IP that ramps too fast is the classic listing trigger. Check the IP against the major DNSBLs regularly during warm-up with the Email Blacklist Check, and if it’s listed, pause and work through the delisting process before continuing.
- Google Postmaster Tools. Watch IP reputation climb out of “unknown,” and keep spam rate under 0.3% (ideally below 0.1%). Setup is covered in monitoring deliverability with Postmaster Tools.
- Microsoft SNDS. For Outlook and Hotmail, Smart Network Data Services shows per-IP complaint and trap data straight from Microsoft — essential when warming an IP that sends to those inboxes.
- Bounce and complaint rates. Rising numbers mean you’re ramping faster than reputation can support. Hold volume, re-verify the list, and only resume once they settle.
Keep it warm afterward
A dedicated IP’s reputation is a moving average of recent activity, so warm-up isn’t a one-time event — it’s the start of a sending pattern you have to maintain. Keep volume consistent, avoid long gaps, keep list hygiene tight with periodic re-verification, and keep complaints low. Let the IP go quiet for weeks and you’ll effectively have to warm it again. For the ongoing health checks that keep both IP and domain reputation strong, see how to check and repair your sender reputation.
Sources
Per-provider IP reputation comes straight from the receivers: Google Postmaster Tools for Gmail and Microsoft SNDS for Outlook. Warm-up schedules are industry conventions, not a published standard — the ramp above is illustrative. Reverse-DNS and connection-trust expectations follow from standard SMTP practice defined in RFC 5321.