How to warm up a newly acquired IP range for email
Every warming guide on the internet assumes the same thing: a clean address, handed to you by a sending platform, waiting for its first message. A range you bought or leased is not that. It arrives with a past, and warming it without reading that past first is how a careful four-week ramp stalls in week two for reasons that have nothing to do with your sending. The order is the method: history, records, delisting, then volume.
Your range has a past, and the filters remember it
Mailbox providers score the sending address and the block around it. Blocklists list addresses and ranges. None of those systems reset when a range changes hands, and none of them is told that it did. ARIN has made the same point about space returned to the registry itself: addresses come back still sitting on externally managed blocklists, on the strength of what previous registrants did with them. A transfer moves the paperwork. The reputation stays where it was, keyed to the addresses.
That is why warming a transferred or leased range is a different job from warming a fresh ESP address. The generic guides are not wrong about the ramp. They are silent about everything that has to happen before the ramp, and on a range with history, the before is most of the work.
Step one: read the history
Before anything touches DNS, find out what you actually acquired. Look the prefix up and read it the way a buyer should have read it before the money moved: which networks announced it and when, whether it went quiet before the transfer, and what independent feeds said about addresses inside it on the dates they were sampled. A range that spent 2024 flagged as proxy space needs a different plan, and a different timeline, from one that has been dark for five years.
Check the whole prefix, not one address. Listings and classifications are frequently applied at block granularity, and a /24 can hold a mix of clean and burned addresses. Sampling three addresses and finding them quiet tells you about three addresses; the honest unit of judgement is the block.
Step two: records before mail
Receiving systems look you up before they accept anything, and what they find should describe you, not the previous tenant.
- Reverse DNS. Every sending address gets a PTR record on your naming scheme, and the forward name resolves back. Mail from an address whose rDNS still carries the old holder's hostname is asking to be judged by the old holder's record.
- WHOIS and abuse contact. Netname, organisation and abuse mailbox point at you, so that complaints reach you instead of the seller. A complaint you never see becomes a listing you learn about from a bounce.
- Authentication. SPF authorises the new addresses, DKIM signs with your domain, DMARC states a policy. None of this is range-specific advice, but on a range with a past it matters more: you are asking filters to attach new behaviour to a new identity, and the identity has to be complete.
- Geolocation. If the range geolocates to the previous holder's country, fix the records and publish a geofeed before support tickets teach you about it.
Step three: delist before you send
Query the public blocklists across the whole range and read the listing dates, not just the yes or no. A listing dated before your acquisition is inherited, and saying exactly that, with the transfer date, is the single most useful sentence a delisting request can contain. Do this before the first message, because a bounce-driven discovery of the same listing costs you a week of ramp and a reputation dent on the mailbox side.
Be selective about effort. A listing on a list nobody consults costs you nothing; check whether the receivers you care about actually cite it before paying anyone for express removal. And automated, traffic-triggered listings age out on their own once the triggering traffic stops, which for your inherited entries means they were already decaying the day you took over.
Step four: the ramp itself
Only now does the generic advice apply, and it applies unchanged, so here it is in one paragraph rather than a fake schedule. Start small, on the order of hundreds of messages per address per day, to your most engaged recipients, the people who reliably open and never complain. Watch bounces, spam-folder placement and complaint rates per mailbox provider, and grow volume in steps, roughly doubling week over week, only while those numbers hold. Back off when they do not. Large mailbox providers build an internal reputation for a new sender over weeks of consistent behaviour, and there is no shortcut through consistency. Spread sending across the range's addresses evenly rather than burning one address first, and keep transactional and bulk streams on separate addresses so one stream's stumble does not price the other's.
Any schedule you find online, including the shape above, is a starting posture rather than a contract. The mailbox providers publish thresholds nowhere and change them without notice; the ramp that matters is the one your own bounce and placement numbers permit this week.
When warming stalls
A ramp that stalls despite clean sending is usually the past resurfacing, and the diagnosis order is the same as the preparation order. Re-check the blocklists: an old pattern can relist when volume appears from a range that was listed before. Re-read the range's reputation readings with dates: a classification applied years ago, VPN, proxy, hosting, does not expire because the tenant changed, and some commercial feeds revisit their labels rarely or never. If what you inherited was sustained deliberate abuse rather than a stray listing, the honest timeline is months, and the honest alternatives are a different range for mail, or a conversation with whoever sold or leased you this one. That conversation goes better with a dated history in hand than with a screenshot of a bounce.
Keeping it warm
Warmth is behaviour plus time, and it persists only while both continue. Keep volume consistent rather than bursty, keep complaint rates low, keep the records current, and keep an eye on the range itself: a lookup of your own prefix from time to time shows you what the feeds currently say, dated, before a customer's bounce does. The range's history did not stop being written when you acquired it. From the first message you send, it is recording you.
Look up any range on the front page before pointing mail at it. The report shows what the addresses have been flagged as and when, who announced the space and for how long, and says plainly when nobody has checked something.