A Practical Guide To Safer IPv4 Transfers

Your phone system runs on a SIP trunk, a voice service that carries calls over the internet. Your provider wants one static IP on its allowlist, but your ISP keeps rotating the address. Every change means dropped calls, broken rules, and another support ticket.

That usually pushes teams toward acquiring their own /24 block. Then the warnings start: blacklisted ranges, hijacked prefixes, and sellers who disappear after a wire transfer.

I have seen small operators lose weeks and real money on bad deals. A safer transfer starts with right-sizing the block, checking its history, using escrow, and finishing the setup after ARIN approves the move.

Key Takeaways

A clean transfer depends on proof, patience, and post-transfer hardening.

• New allocations are gone. ARIN and RIPE exhausted their free pools years ago, so transfers are now the standard path.

• ARIN starts at a /24. Buyers usually need to show they will use at least 50% of the requested space within 24 months.

• Safety comes from verification. Check chain of custody, registry status, blocklist history, and use escrow tied to the registry update.

• Stable space helps operations. Voice, email, cloud links, and vendor allowlists work better when your source IP stops changing.

• Deployment matters. Publish ROAs, fix reverse DNS and geolocation, and update access lists so the block is ready for production.

What You Are Really Acquiring

You are acquiring the right to use and register an IPv4 block through a Regional Internet Registry, or RIR, such as ARIN. The numbers are not owned like land. What matters is a clear right to use them, a valid transfer path, and a clean operating history.

A clean registry record matters because old abuse, incomplete paperwork, or disputed authority can delay the transfer or poison the range after it closes.

IPv4 space is scarce. IANA handed out its last large blocks to the RIRs in 2011. ARIN's free pool hit zero on September 24, 2015, and RIPE NCC announced exhaustion on November 25, 2019. That is why nearly every deal now happens on the transfer market.

For a small business, the need is usually practical. A fixed block helps with SIP trunk allowlists, stable outbound mail, cloud interconnects, or BYOIP, which means bring your own IP, in platforms that support it.

The 3 Business Wins of Owning IPv4

A dedicated block gives you stability that an ISP-assigned address cannot.

1. Provider Portability for Voice and Apps

When you change internet providers or add a backup circuit, your vendors can keep the same source IP on their allowlists. That cuts call failures, keeps failover cleaner, and speeds up onboarding for payment tools, APIs, and remote admin systems.

2. Deliverability and Trust

Clean space plus correct reverse DNS helps billing emails, alerts, and login messages land where they should. Google expects sending IPs to have valid PTR records, and missing or mismatched PTR data can break delivery.

3. Cost Control and Flexibility

Recent pricing shows why buyers still step in. Large-block averages fell below $20 per IP in 2025, while small /24 blocks often cleared in the low $30s per IP. If you plan to keep the space for two to four years, ownership can beat a long lease on both cost and control.

What To Prepare Before You Contact a Seller

Preparation is what separates a smooth transfer from an expensive mess.

Size and Budget

Map what you need now and what you will need in 24 months. A /24 gives you about 256 addresses, enough for one PBX, network address translation egress, and a handful of fixed services. It also gives you room for growth, testing, and cleaner separation between systems.

Move up to a /23 or /22 if you expect Border Gateway Protocol, or BGP, multihoming or clean subnet separation for voice, mail, and web.

ARIN Account Setup

Create your ARIN Online account and Org ID before shopping. Sign the right services agreement and prepare an internal needs statement showing you will use at least 50% of the space within 24 months. That paperwork removes the most common delay.

Reputation and Risk Checks

Use WHOIS and RDAP, the registry lookup systems, to confirm the current registrant and transfer history. Screen the range against IANA's special-purpose registry so you do not touch reserved or bogon space, which cannot be routed on the public internet.

Then check blocklist history through Spamhaus and Cisco Talos. A Policy Block List entry can be routine. A long SBL or CSS history is different, and past abuse can linger in spam filters and geolocation databases long after the registry record changes.

Spamhaus says SBL removal has to start with the responsible service provider, not the end user, so stubborn listings are a serious warning.

Transaction Protections

Do not prepay on trust. Use a licensed escrow service with terms tied to the registry change. The safest flow is simple: you fund escrow, the RIR transfer completes, your organization appears in WHOIS, and only then do funds release.

Your contract should also say the seller has authority to transfer the block, that no liens or other claims exist, and that prior assignments were disclosed. If escrow will not tie release to registry proof, pick another service.

Red Flags To Walk Away From

• The seller refuses escrow or will not provide chain-of-custody records.

• WHOIS, RDAP, or blocklist data contradicts the seller's story.

• You are pushed toward crypto, direct wire payment, or a same-day decision.

Where To Source Space Safely

The safest channel is the one that makes verification easy and shortcuts impossible.

Brokers and Marketplaces

Strong brokers guide the paperwork, coordinate escrow, and explain ARIN policy in plain language. Favor firms that show a standard purchase agreement, clear KYC steps, price history, and a written transfer process. Ask how fees work, who controls each step, and what proof you will receive before funds release.

Once you have verified the broker's process, pricing, chain of custody, and escrow controls, a focused next step can save time for teams that need one stable public address for SIP trunk allowlisting, clean vendor access lists, and less day-to-day support churn across voice and cloud systems. If you are ready to compare inventory and pricing after due diligence, Buy IPv4 can help move a buyer from quote to ARIN transfer in about two to three weeks.

Direct From Holders

Private deals can work when you know the counterparty, but comfort is not control. Use the same escrow, registry, and reputation checks you would use with a broker.

Corporate Events and M&A Transfers

If the block is part of an acquisition, treat it like any other asset. Trace the rights through every handoff and confirm policy limits. ARIN says IPv4 space received from its waiting list cannot be transferred for 60 months, so origin matters.

Close Clean, Deploy Clean: Your Post-Purchase Runbook

A good transfer is only valuable if the block works on day one.

1. Confirm Registry and Paper Trail

Make sure WHOIS and RDAP show your organization as the registrant. Store the purchase agreement, bill of sale, and transfer approvals in one place, and update every ARIN contact record.

2. Secure Your Routing

If you will announce the prefix through BGP, publish Route Origin Authorizations, or ROAs, using ARIN's hosted RPKI service. RPKI, short for Resource Public Key Infrastructure, helps other networks validate that your AS is allowed to originate the route. Without it, a valid block can still be harder to trust during hijacks or route leaks.

Also create Internet Routing Registry entries and monitor global visibility.

3. Set DNS Hygiene

Create forward and reverse DNS for every public service. Add SPF, DKIM, and DMARC, the core records that prove your mail is approved and authentic. That protects billing mail, alerts, and password resets.

4. Fix Geolocation Early

Transferred space can keep stale location data for months. Submit corrections to providers such as MaxMind early so customers do not hit country blocks, fraud filters, or wrong-language experiences.

5. Wire It Into Your Communications Stack

Update SIP trunk access lists, firewall rules, monitoring, and failover tests. Then place inbound and outbound calls, test cutover paths, and verify quality of service after the new source IP goes live. This is where the operational payoff shows up.

Make The Block Earn Its Keep

Owning space pays off when you treat it like infrastructure, not a one-time purchase.

Review ROAs, routing entries, DNS, and vendor allowlists every quarter. Watch call completion, email bounces, and support tickets tied to the new range. That discipline matters even more when the block supports phones or payment workflows, where one bad change is instantly visible to customers.

FAQ

These answers cover the questions that usually slow a first transfer.

What Size Block Should a Small Operator Start With?

Most teams start with a /24 because it meets ARIN's minimum transfer size and keeps routing simple. That is usually enough for one PBX, network egress, and a few fixed services. Move up only if you expect BGP multihoming or clear subnet separation.

How Long Does an ARIN Transfer Usually Take?

When both sides have clean paperwork and respond quickly, an ARIN-to-ARIN transfer often closes in two to three weeks. Missing lineage, slow approvals, or inter-RIR deals can stretch the timeline.

What Should You Do if the Range Shows Up on Spamhaus?

Start by checking which list is involved. A PBL entry can be normal. An SBL or CSS entry is far more serious, and removal may depend on the responsible service provider. If the history is persistent, treat the range as damaged unless the risk, discount, and cleanup plan are all clear.

Is Leasing Better for a First Rollout?

Leasing can make sense for a short pilot or a temporary service. If you expect multi-year use and you care about consistent reputation, ownership usually gives you better control and a steadier total cost.