How to Buy IPv4 Addresses: Costs, Transfer Rules, Risks
Quick answer: to buy IPv4 addresses, define the block you need, choose between buying, leasing and BYOIP, check the block before you pay, sign an agreement with escrow, and complete the registry transfer for your region. The registry approves the transfer, not the seller, and no price, timeline or approval is guaranteed. Current figures are on IPv4 pricing. If you hold a block and want to sell, read the sell guide.
Buy, lease or BYOIP
| Model | Control | Cost shape | Best for |
|---|---|---|---|
| Buy | Registered holder, full routing control | One-off price plus transfer costs | Long-term networks |
| Lease | Rights for a fixed term | Recurring fee, nothing to transfer | Short projects, tests |
| BYOIP | Your block runs on a provider network | Provider terms apply | Cloud and CDN use |
The exact legal status of an address depends on the registry, the contract and the jurisdiction, so treat "ownership" with care.
Define the requirement
- Block size - /24 is the usual routing minimum, bigger blocks follow your growth plan.
- Registry - RIPE NCC, ARIN or APNIC rules differ; do not mix them.
- ASN and routing - who will announce the prefix, and from where.
- Geolocation - the country you need the addresses to map to.
- Timeline - transfers take as long as the registry needs.
- History - your tolerance for past abuse or blacklist records.
Where buyers find blocks
Through a broker, a marketplace or a direct deal. Each has different fees and risks, compared in broker vs marketplace vs direct sale.
Full acquisition cost
The price per address is only one line. Add the broker or marketplace fee, escrow, registry fees, legal review, routing and RPKI work, and renumbering. Price depends on block size, registry and history; see the pricing guide for dated observations.
Due diligence before payment
Confirm the seller is the registered holder, read the WHOIS history, check blacklists and prior routing, and look for open disputes. Details are in how to check a block before buying.
Agreement and escrow
Put block, price, conditions and a deadline in writing. Escrow holds the payment until the registry confirms the transfer. Define what happens if the transfer is refused.
Recipient requirements (last checked 2026-10)
- RIPE NCC - allocated resources go only to a RIPE NCC member; IPv4 cannot be transferred again for 24 months after receipt. Source: RIPE Resource Transfer Policies.
- ARIN - the recipient signs an RSA, the minimum transfer is a /24, and use on an operational network is expected (NRPM 8.5). Source: ARIN NRPM.
- APNIC - minimum /24; a recipient with no IPv4 must show a detailed plan to use it within 24 months. Source: APNIC policy, section 11.
Inter-RIR transfers add the conditions of both registries. Rules change, so confirm them on the official pages before you sign. Details: RIPE transfer guide.
After the transfer
Update WHOIS and route objects, create ROAs for RPKI, announce the prefix and check geolocation data. Allow time for databases to catch up.
Common buyer mistakes
- Paying before the seller is verified.
- Skipping the blacklist and routing history check.
- Forgetting fees outside the price.
- Assuming one registry's rules apply to another.
Buyer checklist
- Size, registry, purpose and timeline written down.
- Seller and holder confirmed.
- WHOIS, blacklist and routing history reviewed.
- Escrow and a refusal clause in the agreement.
- Post-transfer plan: WHOIS, RPKI, announcement.
A "clean block" is not a lifetime guarantee. Reputation can change after the transfer, so keep monitoring.
Next step
Tell us the registry, prefix size, purpose and timeframe: email ipv4@dcxv.com or use the Request an IPv4 block form. See also the buy page and IPv4 pricing.
