An IP range gets sold like inventory. It behaves like a used car with no service history. Every address in that block carries whatever the previous holder did with it, and mailbox providers do not wipe the slate clean when the paperwork changes hands. The expensive part of a bad buy is almost never the lease fee. It’s the quarter you spend explaining throttled delivery to your stakeholders while tickets pile up and campaign numbers drift sideways. And the annoying thing? Nearly all of that is findable beforehand, if you know which signals to pull and how to read them. Below: the pre-purchase checks that actually matter - reputation history, registry hygiene and ownership trail, blocklist status at both address and netblock level, PTR and authentication readiness, seller vetting, and the warm-up discipline that has to follow.
Why Reputation Travels With the IP, Not With You
Mailbox providers and network filters score individual addresses and whole ranges, and they keep those historical signals long after a block changes owners. Your company name means nothing to a filter. The address does. Then there’s the neighbour problem: filtering models treat everything inside a /24 as related evidence, so what the guy three addresses down does lands partly on you. That’s the same dynamic behind the shared and dedicated IP hosting , and it’s exactly why you assess the range, not one IP that happens to come back clean.
Learn to tell transient throttling from real damage. Deferrals ease off once your volume settles into a pattern. Reputational scarring is different - it gets baked into the filtering models and survives ownership changes. Some abuse categories leave deeper marks than others. Snowshoe spam (spreading low volume across many addresses to duck thresholds) and phishing infrastructure both pull long-lived suppression. A block that scans clean today might just be quiet. If the abuse only stopped a few weeks back, nothing has been rehabilitated. It’s been paused.
Tip: weight recency heavily. Silence after recent abuse is not the same thing as a track record of legitimate sending.
Registry Records: RIR Data, WHOIS and Ownership Trail
Start at the allocating registry - RIPE, ARIN, APNIC, LACNIC or AFRINIC - and confirm the seller actually holds what they’re selling you. Where the registry exposes object history, read it properly. Don’t skim. Frequent transfers, holders that resolve to shell entities, rapid re-registration after a cancellation: all of those tell you something about how the space has been used. Regional allocation matters here too, and if you’re buying into a specific market it pays to understand the tactics behind Nordic IP ranges before you commit.
Check that abuse-c and the abuse contact fields point at a monitored mailbox and not a dead alias. Providers escalate hard against ranges whose complaint channel goes nowhere. And get the transfer type pinned down in plain language:
- Full transfer - the range moves to your registry account and you control the objects.
- Lease with LOA - the holder authorises your announcement but keeps registry control.
- Sub-allocation - you get part of a bigger block, with thinner independence.
Watch for space flagged as hijacked or reclaimed. Watch too for policy restrictions that limit resale once a transfer completes.
Tip: ask for the registry object identifier up front and verify it yourself. A screenshot is not verification.
Blocklist and Reputation Checks to Run Before Signing
Sample testing is how buyers get burned. Query every address in the block, not a convenient handful, because listings cluster unevenly across a range. My sequence:
- Check public DNSBLs, policy blocklists and URL-based lists where the addresses previously hosted web content.
- Test both single-IP entries and CIDR-level listings, since several operators publish whole netblocks rather than individual hosts.
- Pull reputation portals and postmaster tooling wherever a provider exposes historical rather than current data.
- Review passive DNS and historical hostname records to see what actually ran on those addresses.
- Search open proxy, compromised host and bulletproof hosting datasets for any overlap.
Delisting is doable, so a live listing isn’t automatically a dealbreaker. Read it as information about where the range has been rather than a problem that evaporates the moment it’s removed. The listing history tells you far more than the listing status.
Technical Readiness: PTR, rDNS Delegation and Authentication
Deliverability leans on control you might not automatically get. Confirm you’ll receive rDNS delegation - through the seller’s nameservers or straight from the registry - before you call the technical side settled. Forward-confirmed reverse DNS has to resolve consistently in both directions. A mismatch on its own is enough to cost you inbox placement at the big providers.
Plan your hostname naming so PTR records reflect your sending domain instead of generic provider strings, which read as shared infrastructure to anything doing the filtering. Work out how the range will be announced and by which ASN, because routing origin feeds filtering decisions on its own, separate from the address. The rest of the alignment is on you: SPF entries covering the new ranges, DKIM signing on every stream, DMARC set to whatever enforcement you can actually stomach. If setting that up in-house isn’t realistic, it’s worth checking what a provider handles on the infrastructure side before you take the range on.
Tip: get rDNS control in writing before you pay. Retrofitting it later is the single most common regret I hear from buyers.
Vetting the Seller and the Contract Terms
Run due diligence in a fixed order so nothing gets dropped when the deal starts moving fast:
- Establish the legal identity of the registered holder and match it against the entity invoicing you.
- Obtain proof of allocation traceable to the registry object.
- Confirm the transfer mechanism and who keeps administrative rights afterwards.
- Read the acceptable use terms, particularly volume and content restrictions.
- Examine dispute, suspension and clawback clauses before signing.
Ask, straight out, what happens if the range gets listed after purchase and whose job remediation is. On a lease, your usable lifespan depends on the announcing network staying cooperative. That’s a real dependency and it deserves a price. Find out whether the provider runs a documented abuse desk, and how fast it moves.
Red flags: no written LOA, refusal to name the announcing ASN, pressure to close quickly, and pricing well below market.
What to Do in the First Weeks After Acquisition
Before you send a single message, record a baseline: listing status across your chosen sources, rDNS state, routing config. Then whatever changes later is attributable instead of mysterious. Warm up gradually across the block and open with your most engaged recipients, because positive engagement is the earliest reputation signal you can generate.
Segment by traffic type so transactional mail never inherits risk from marketing volume. Read your bounce codes and deferral strings closely - they usually flag a reputation problem days before the aggregate metrics budge. And resist the urge to light up every address at once. Holding part of the range back gives you clean capacity if the first cohort disappoints.
Tip: treat any newly acquired range as provisional for the first month and keep a fallback sending path ready to absorb critical traffic.
Conclusion
Three things define a clean range: verifiable registry records, consistent technical control including rDNS, and no history that nobody can explain. Miss any one of those and you’re buying uncertainty at a price you can’t calculate. The verification here costs you hours of focused work. Recovering from a poisoned block costs months of constrained sending and some very awkward conversations.
Think of the decision as risk pricing, not a pass/fail gate. Minor historical listings on an otherwise well-documented block can be perfectly fine at the right price. An opaque ownership trail rarely is, no matter the discount. One caveat worth repeating: reputation is earned through sending behaviour, so even a spotless range is only a starting position, and the wider background on hosting and addressing is worth reading if you’re new to this. What you do with it over the following months decides whether it stays that way.
