How to Sell IPv4 Addresses in 2026: A Step-by-Step Guide

Organizations holding unused or surplus IPv4 address space may be able to convert those resources into capital by selling them to another eligible organization.

But selling IPv4 addresses is not as simple as finding a buyer and exchanging payment.

A successful IPv4 sale normally involves several separate layers:

• confirming which IPv4 blocks are actually available;
• establishing the current registered holder and authority to transfer;
• checking the applicable Regional Internet Registry (RIR);
• verifying transfer eligibility;
• reviewing registry and resource records;
• agreeing commercial terms;
• completing the applicable registry transfer process; and
• verifying that records and operational dependencies are correctly updated after completion.

In 2026, sellers should think of an IPv4 transaction as both a commercial transaction and a coordinated registry process.

This guide explains how to sell IPv4 addresses step by step, what to check before entering the market, what documentation may be required and how to avoid common problems that delay an IPv4 transfer.

If your organization already knows that it wants to sell surplus address space, you can also explore LARUS's dedicated Sell IP Addresses service.

How to Sell IPv4 Addresses: Quick Answer

To sell IPv4 addresses, an organization should generally:

1. Identify the IPv4 block it wants to sell.
2. Confirm its CIDR size and current use.
3. Determine which RIR administers the resource.
4. Verify the registered holder and transfer eligibility.
5. Review registry records, routing state and resource history.
6. Decide whether selling is better than leasing.
7. Establish the commercial value of the block.
8. Identify and verify an eligible buyer.
9. Agree contractual and payment terms.
10. Submit the transfer through the applicable RIR process.
11. Complete payment according to the agreed transaction structure.
12. Verify registry and operational changes after completion.

The exact procedure depends on the resource, the seller, the buyer and the policies of the relevant RIR or RIRs.

Can You Sell IPv4 Addresses?

In many circumstances, organizations can commercially transfer eligible IPv4 address blocks to another organization through an applicable RIR transfer process.

However, not every IPv4 resource is automatically transferable.

Before describing a block as available for sale, a seller should determine:

• Which organization is currently registered for the resource?
• Which RIR administers it?
• Is it legacy or non-legacy address space?
• Is the resource subject to transfer restrictions?
• Is there an unresolved dispute involving the block?
• Has the resource recently been allocated or transferred?
• Is the organization authorized to initiate the transfer?
• Is the intended recipient eligible under the applicable policy?
• Will the transaction be intra-RIR or inter-RIR?

A commercial agreement between buyer and seller does not by itself replace the applicable registry process.

Where a registry transfer is required, the registry records must ultimately be updated through the relevant procedure.

Stop Using Class A, B and C When Preparing IPv4 for Sale

Older IPv4 guides sometimes describe address space using Class A, Class B and Class C terminology.

That is not the right way to prepare a modern IPv4 transaction.

Modern IPv4 networks use Classless Inter-Domain Routing (CIDR) notation.

Instead of saying that an organization has a "Class C" block, for example, a seller should identify the actual prefix:

• /24
• /23
• /22
• /21
• /20
• /19
• /18
• /17
• /16

The IETF's RFC 4632 describes CIDR and classless Internet routing.

Common IPv4 CIDR Block Sizes

For an IPv4 sale, the seller should know the exact prefix or prefixes involved rather than relying on obsolete address-class terminology.

Step 1: Identify the IPv4 Addresses You Actually Want to Sell

Start by conducting an internal IPv4 inventory.

Do not assume that an address block is unused simply because it no longer appears in a current network diagram.

IPv4 space can remain connected to:

• legacy servers;
• customer services;
• BGP advertisements;
• NAT pools;
• DNS records;
• reverse DNS;
• VPN configurations;
• firewalls;
• API allowlists;
• third-party integrations;
• monitoring systems;
• RPKI;
• IRR records; and
• internal documentation.

Before selling, identify exactly which prefixes are genuinely surplus.

For example, an organization controlling a /16 may discover that it still needs part of the address space but could potentially separate and transfer one or more smaller eligible blocks.

Whether a block can actually be divided and transferred depends on the applicable registry framework and resource status.

Step 2: Identify the Regional Internet Registry

Next, determine which registry administers the address block.

The global Internet number-resource system includes five Regional Internet Registries:

The seller needs to know the RIR because transfer procedures are not identical across every registry.

At the global level, IANA coordinates Internet number resources , while the RIRs maintain regional registration and transfer processes.

Do All RIRs Have the Same IPv4 Transfer Rules?

No.

RIR policies and procedures differ, and they can change.

• ARIN provides formal procedures for resource transfers , including specified-recipient and compatible inter-RIR transfers.
• RIPE NCC facilitates transfers of Internet number resources and publishes procedures for transfers within and outside its service region.
• APNIC operates IPv4 transfer procedures covering multiple transfer scenarios and requiring transfers to satisfy applicable policy conditions.
• LACNIC policy provides for qualifying IPv4 transfers, including intra-RIR and compatible inter-RIR scenarios.
• AFRINIC's transfer-policy environment has continued to evolve, including policy developments during 2026.

Because policies change, sellers should verify the current official registry rules at the time of the transaction, especially for inter-RIR transfers.

Do not assume that a transfer completed under one RIR can be repeated under identical rules in another.

Step 3: Confirm Registered Holdership and Authority

One of the most important steps is establishing who is currently recognized in the relevant registry records and who has authority to initiate the transfer.

Check:

• registered organization name;
• organization identifier or membership account;
• administrative contacts;
• authorized officers;
• current corporate legal entity;
• historical mergers or acquisitions;
• legacy-resource status where relevant; and
• any discrepancies between current corporate structure and registry data.

This becomes particularly important when the original organization:

• changed its legal name;
• merged with another company;
• was acquired;
• was reorganized;
• dissolved;
• changed subsidiaries; or
• has not updated its registry information for many years.

If the resource record and current legal organization no longer match clearly, the discrepancy may need to be resolved before a normal sale can proceed.

Step 4: Check Whether the IPv4 Block Is Transfer-Eligible

Holding or administering an IPv4 block does not automatically mean that it can be transferred immediately.

Transfer eligibility may depend on factors such as:

• resource type;
• original allocation status;
• registry region;
• date of allocation;
• date of a previous transfer;
• legacy status;
• minimum transferable prefix size;
• recipient eligibility;
• resource disputes; and
• applicable registry policy.

Some registries also impose restrictions on resources obtained through particular allocation mechanisms or within specified time periods.

This is why eligibility should be checked before commercial negotiations become advanced.

A seller does not want to agree on a price, sign documents and prepare a buyer only to discover that the resource cannot currently follow the planned transfer path.

Step 5: Review WHOIS, RDAP and Registry Records

The next step is to examine the public and account-level information surrounding the block.

Useful checks include:

• WHOIS or RDAP organization data;
• resource status;
• administrative contacts;
• technical contacts;
• abuse contacts;
• allocation or assignment information; and
• registry account information.

If these records are outdated, resolve the issue early.

LARUS explains why this matters in Outdated WHOIS and RDAP Records: A Hidden Risk in IPv4 Transfers .

An IPv4 transfer is easier to understand when the registry state accurately describes the organization currently responsible for the resource.

Step 6: Review the Operational State of the IPv4 Block

Selling IPv4 addresses is not purely a registry exercise.

The seller should also determine what is happening operationally.

Check whether the prefix is:

• currently visible in BGP;
• originated by your ASN;
• originated by another ASN;
• covered by an active ROA;
• represented in an IRR route object;
• delegated for reverse DNS;
• associated with production services; or
• still referenced by customers or partners.

The objective is not necessarily to remove every routing record immediately.

The objective is to know what must change and when.

For example, deleting a ROA or withdrawing a route too early could disrupt a legitimate running service before the buyer is ready.

Good transfer planning separates:

1. commercial completion;
2. registry completion; and
3. operational migration.

They may be closely coordinated, but they are not identical events.

Step 7: Check IPv4 Reputation and History

IPv4 reputation can affect the commercial attractiveness and deployment readiness of a block.

Before selling, investigate whether the prefix has been associated with:

• spam;
• malware;
• abuse complaints;
• blacklists;
• previous hosting activity;
• unusual geolocation data; or
• problematic routing history.

A history problem does not necessarily make an IPv4 block impossible to sell.

But undisclosed issues may complicate negotiations and post-transfer deployment.

A seller should therefore avoid representing a block as "clean" without appropriate verification.

The buyer will often perform its own due diligence.

Step 8: Decide Whether You Should Sell or Lease the IPv4 Block

Selling is not the only option for unused IPv4.

Some organizations may prefer to lease the address space.

The basic difference is:

LARUS provides a more detailed comparison in Selling vs Leasing IPv4 Addresses: Which Option Is Better for IP Holders? .

Organizations should make this decision before beginning a sale.

Once a transfer is completed, recovering the same address space later may be difficult or impossible.

What If You Want to Sell the IPv4 Asset but Still Need the Addresses?

This is where a sell-and-leaseback structure may be relevant.

Instead of completely giving up operational access to the address capacity, an organization may sell qualifying IPv4 resources and then lease capacity under a separate commercial arrangement.

This can be useful where the organization wants to:

• monetize the IPv4 asset;
• reduce direct registry exposure;
• preserve operational IPv4 capacity; and
• avoid an immediate large-scale renumbering project.

LARUS explains its current approach on the Sell IP Addresses page.

A sell-and-leaseback arrangement should be reviewed carefully because the sale and the subsequent right to use address capacity are separate commercial and operational considerations.

Step 9: Determine the Commercial Value of the IPv4 Block

There is no universal RIR-set selling price for IPv4 addresses.

The commercial value of a block depends on the market and transaction.

Factors may include:

• CIDR block size;
• RIR region;
• transfer eligibility;
• whether the transaction is intra-RIR or inter-RIR;
• registry readiness;
• block history;
• reputation;
• routing history;
• documentation quality;
• market demand;
• transaction timing; and
• commercial terms.

Larger blocks may also be valued differently from smaller blocks on a per-address basis.

For this reason, sellers should not rely on an old article stating that "IPv4 is worth $X per address."

IPv4 market conditions change, and two blocks containing the same number of addresses may not necessarily have identical transaction value.

For broader market context, see LARUS's Global IPv4 Pricing & Market Statistics .

If you are evaluating a portfolio for sale, you can submit your IPv4 addresses to LARUS for a transaction-specific discussion.

Step 10: Find and Verify the Buyer

An IPv4 transaction requires an eligible recipient.

That buyer may be:

• an ISP;
• hosting provider;
• cloud provider;
• data center;
• telecom company;
• enterprise;
• network operator; or
• specialized IPv4 infrastructure company.

The seller should know who the counterparty is.

Commercial due diligence may include:

• legal entity verification;
• authorized representatives;
• transaction authority;
• payment capability;
• recipient RIR;
• registry eligibility;
• intended transfer path; and
• sanctions or compliance checks where applicable.

A high headline offer is not necessarily the best transaction if the buyer cannot successfully complete the registry process.

Step 11: Agree on the IPv4 Sale Contract

Once both parties are ready, the commercial terms should be documented.

Depending on the transaction, an agreement may cover:

• exact IPv4 prefixes;
• purchase price;
• payment currency;
• payment mechanism;
• transfer responsibilities;
• registry fees where applicable;
• due-diligence conditions;
• representations and warranties;
• timing;
• termination conditions;
• confidentiality;
• applicable law;
• dispute resolution;
• operational transition; and
• post-transfer responsibilities.

The agreement should clearly distinguish between the commercial sale and the registry process required to implement the transfer.

Organizations should obtain appropriate legal and tax advice for their circumstances rather than relying on a generic IPv4 contract template.

Step 12: Prepare the Required Documentation

Documentation requirements vary by RIR and transaction structure.

A seller may need some combination of:

• corporate registration documents;
• proof of authority;
• registry account information;
• officer authorization;
• resource details;
• identification of the recipient;
• transaction documentation;
• merger or acquisition records where relevant;
• historical documentation for legacy resources; and
• registry-specific forms.

For example, ARIN states that transfer requests require an appropriate ARIN Online account and may require supporting documentation depending on the transfer type.

APNIC likewise requires information supporting transfer requests and processes transfers through the appropriate account and registry workflow.

Preparing documents early can prevent avoidable delays.

Step 13: Submit the IPv4 Transfer to the Relevant RIR

Once the commercial and administrative pieces are ready, the parties proceed through the applicable registry transfer process.

A simplified transaction may look like:

Seller identifies resource
↓
Buyer and seller complete due diligence
↓
Commercial terms agreed
↓
Transfer request submitted
↓
RIR evaluates the request
↓
Additional documentation provided if required
↓
Transfer approved
↓
Registry records updated
↓
Payment and operational transition completed according to the agreed transaction structure

The exact sequence can differ.

For example, APNIC's transfer workflow requires the relevant parties to complete the applicable registry steps before APNIC evaluates and records the transfer.

ARIN and RIPE NCC likewise operate their own transfer workflows.

What Is the Difference Between an Intra-RIR and Inter-RIR Transfer?

Intra-RIR Transfer

An intra-RIR transfer occurs when the source and recipient are handled within the same RIR framework.

For example:

RIPE NCC → RIPE NCC

or:

ARIN → ARIN

Inter-RIR Transfer

An inter-RIR transfer involves two compatible RIR regions.

For example:

ARIN → APNIC

Inter-RIR transfers can involve additional checks because both registry frameworks may be relevant.

Not every possible RIR pairing should be assumed to be available.

Always verify current compatibility with the involved registries before structuring an inter-RIR sale.

Step 14: Coordinate Payment Safely

Payment structure should be established in the contract before the registry transfer reaches completion.

Depending on the parties and transaction, payment may involve:

• direct settlement;
• staged payment;
• escrow; or
• another agreed settlement mechanism.

There is no single payment sequence suitable for every IPv4 sale.

The parties need to coordinate:

• when funds are deposited;
• when the transfer request is initiated;
• what constitutes registry approval;
• when funds are released; and
• what happens if the transfer is rejected or delayed.

The commercial settlement mechanism should reduce uncertainty for both seller and buyer.

Step 15: Update Routing and Operational Systems After the Transfer

Registry approval is not necessarily the end of the operational work.

Depending on how the prefix was previously used, the parties may need to update or remove:

• BGP announcements;
• ROAs;
• IRR route objects;
• reverse-DNS delegations;
• DNS records;
• geolocation information;
• abuse contacts;
• firewall rules;
• monitoring systems;
• customer configurations; and
• partner allowlists.

Timing matters.

The seller should avoid withdrawing operational dependencies prematurely if the prefix is still serving legitimate traffic.

The buyer, meanwhile, should avoid announcing the resource before the necessary authorization and transition steps are ready.

The objective should be a controlled transition in which registry records, security assertions and operational routing ultimately reflect the intended post-transfer state.

What Documents Should an IPv4 Seller Prepare?

Not every RIR will request every item in this table.

It is a transaction-readiness checklist, not a replacement for the applicable registry's official requirements.

Common Mistakes When Selling IPv4 Addresses

1. Using Class A, B and C Instead of CIDR

Modern IPv4 transactions should identify actual CIDR prefixes. Use /24, /22, /20, /16 and similar prefix lengths.

2. Negotiating Before Checking Transfer Eligibility

A commercial agreement cannot solve a registry eligibility problem. Verify the resource first.

3. Assuming the Registry Record Is Current

Old organizations, mergers and stale contacts can create transfer delays. Review WHOIS/RDAP and registry account information before entering the market.

4. Looking Only at Price

The highest offer is not necessarily the strongest transaction. Buyer eligibility, documentation, settlement structure and transfer certainty also matter.

5. Forgetting Existing Network Dependencies

A prefix that appears "unused" to finance or management may still appear in BGP, DNS, firewalls, customer allowlists or security systems.

Perform an operational audit first.

6. Deleting RPKI or Routing Records Too Early

Registry, security and operational changes should be coordinated. Removing them prematurely can cause unnecessary reachability problems.

7. Assuming Every RIR Uses the Same Rules

Transfer policies differ and evolve. Check the current official requirements of the relevant registry before proceeding.

8. Selling Address Space You May Need Again

A completed sale is different from leasing. If the organization still depends on the block, evaluate leasing or a structured sell-and-leaseback alternative before permanently transferring it.

How Long Does It Take to Sell IPv4 Addresses?

There is no universal timeline.

The duration can depend on:

• finding a buyer;
• seller documentation;
• recipient readiness;
• RIR review;
• intra-RIR versus inter-RIR transfer;
• corporate history;
• legacy status;
• payment arrangements; and
• whether records require correction.

A well-documented transfer involving a prepared buyer may progress more efficiently than a transaction involving unclear registry records, organizational restructuring or disputed resource status.

Sellers should therefore treat "transfer readiness" as something that can be improved before entering the market.

How Can You Make an IPv4 Block Easier to Sell?

Confirm the Prefix

Know exactly what CIDR block you are offering.

Correct Registry Information

Make sure important organization and contact records are accurate.

Document Corporate Changes

If the organization has changed names, merged or reorganized, assemble the relevant documentation.

Understand Routing

Know whether the prefix is still being announced.

Review RPKI and IRR

Know which authorizations and policy records exist.

Review Reputation

Understand any significant abuse or blacklist history.

Identify Operational Dependencies

Make sure internal teams understand what will stop working if the prefix is transferred.

Decide Whether the Entire Block Is Truly Surplus

Do not sell infrastructure that the organization may still need.

A clean, well-documented resource is generally easier for buyers and registries to evaluate.

Should You Sell Unused IPv4 Addresses?

Selling may make sense when:

• the resources are genuinely surplus;
• the organization prefers immediate capital;
• future internal demand is unlikely;
• continued resource administration is undesirable; or
• the company is consolidating its network portfolio.

LARUS discusses this use case further in Sell Unused IP Addresses: Turn Surplus IPv4 Into Value .

Selling may be less suitable when:

• the organization expects significant future IPv4 demand;
• the addresses are deeply embedded in production systems;
• renumbering would be expensive;
• recurring income is preferred; or
• long-term control remains strategically important.

In those circumstances, compare selling with leasing before deciding.

Why Registry Accuracy Matters During an IPv4 Sale

An IPv4 sale involves more than a private agreement between two companies.

The applicable registry performs an important coordination role by recording the transfer according to its policies and processes.

That record should ultimately reflect the legitimate post-transfer state of the resource.

At the same time, registry state should be coordinated with the operational systems surrounding the block.

A well-managed transaction therefore considers:

Commercial agreement
↓
Registry transfer
↓
RPKI / IRR / rDNS updates
↓
Operational routing
↓
Post-transfer verification

This layered approach is consistent with a broader Internet-governance principle:

Coordination systems are most useful when the records and authorizations they maintain accurately describe the legitimate network state they are intended to support.

How to Sell IPv4 Addresses to LARUS

Organizations with eligible IPv4 resources can discuss a direct sale with LARUS.

A typical starting point is to provide:

• IPv4 block or block size;
• RIR;
• organization details;
• whether the resource is currently in use;
• expected timing; and
• whether continued IPv4 capacity is required after the transaction.

LARUS can then evaluate the potential commercial and transfer path.

Unlike the older version of this guide, the objective is not to describe LARUS simply as a generic IPv4 broker.

LARUS also acquires IPv4 address space for its own first-party operating supply.

For organizations that still require address capacity after monetizing the asset, a sell-and-leaseback structure may also be discussed where appropriate.

Sell IPv4 Addresses to LARUS

IPv4 Seller Checklist

• ☐ We know the exact CIDR prefix.
• ☐ We know which RIR administers the resource.
• ☐ We have confirmed the current registered organization.
• ☐ We have authority to initiate the transaction.
• ☐ We have checked current transfer eligibility.
• ☐ We understand whether the resource is legacy or non-legacy.
• ☐ We have reviewed WHOIS/RDAP information.
• ☐ We have reviewed BGP routing.
• ☐ We have reviewed RPKI/ROA state.
• ☐ We have reviewed relevant IRR records.
• ☐ We know whether reverse DNS is in use.
• ☐ We have checked for major reputation or abuse issues.
• ☐ We know which internal systems still use the prefix.
• ☐ We have decided between selling and leasing.
• ☐ We understand the buyer's RIR and transfer path.
• ☐ Commercial terms are documented.
• ☐ Payment sequencing is clear.
• ☐ Post-transfer operational responsibilities are clear.

If several of these questions cannot yet be answered, the block may not be transaction-ready.

Frequently Asked Questions About Selling IPv4 Addresses

Can I legally sell IPv4 addresses?

Eligible IPv4 resources can be commercially transferred under applicable registry policies and contractual frameworks. The precise legal and contractual position depends on the resource, jurisdiction, registry and transaction, so organizations should avoid assuming that every IPv4 block can be sold in the same way.

How do I sell my IPv4 addresses?

Start by identifying the exact CIDR block, confirming the RIR and registered organization, checking transfer eligibility, reviewing registry and operational records, finding an eligible buyer and then completing the applicable registry transfer process.

What is the minimum IPv4 block I can sell?

Transferable block-size requirements vary by registry and resource type. A /24 is a common minimum in several RIR transfer frameworks, but sellers should verify the current rules applicable to their specific resources.

Can I sell a /24 IPv4 block?

Potentially, yes. A /24 contains 256 IPv4 addresses and may be transferable under several RIR frameworks if the resource and parties satisfy the relevant requirements.

Can I sell part of a larger IPv4 block?

Possibly. Whether a larger block can be subdivided for transfer depends on registry policy, minimum transfer size, resource status and operational considerations.

How much are IPv4 addresses worth?

There is no single universal IPv4 sale price. Commercial value depends on block size, RIR region, transfer eligibility, resource history, market conditions, reputation, transaction timing and other factors.

Do I need an IPv4 broker?

Not necessarily. A seller may transact with a direct buyer or use an intermediary. What matters is that the parties understand commercial due diligence, registry requirements, documentation and transfer execution.

Does LARUS buy IPv4 addresses directly?

LARUS accepts inquiries from organizations seeking to sell eligible IPv4 address space and uses acquired resources as part of its first-party IPv4 supply strategy. Transaction availability and terms depend on the specific portfolio.

Should I sell or lease my IPv4 addresses?

Selling is generally better suited to organizations seeking immediate capital and an exit from the asset. Leasing can be more suitable when recurring revenue and future control are important. Read Selling vs Leasing IPv4 Addresses for a detailed comparison.

Can I sell IPv4 addresses and continue using them?

A structured sell-and-leaseback arrangement may allow an organization to monetize qualifying resources while retaining contracted IPv4 capacity. The exact structure and continuity terms should be evaluated before the sale.

Is an IPv4 sale complete when the contract is signed?

Not necessarily. Where an RIR transfer is required, the relevant registry process must also be completed. Operational records such as RPKI, IRR and reverse DNS may require additional coordination.

Does an IPv4 transfer automatically change BGP?

No. A registry transfer and a BGP announcement are different layers. Routing changes must be coordinated separately with the intended network deployment.

Can outdated WHOIS or RDAP records delay an IPv4 sale?

Yes. Inaccurate organization or contact information can complicate verification and transfer processing. Sellers should review registry records before beginning the transaction.

Conclusion

Learning how to sell IPv4 addresses in 2026 requires more than finding someone willing to pay for a block.

A successful IPv4 transaction begins with understanding exactly what resource you control and whether it is truly surplus.

The seller should then verify:

• the CIDR block;
• the applicable RIR;
• registered holdership;
• transfer eligibility;
• documentation;
• resource history;
• routing state;
• RPKI and IRR;
• reputation;
• commercial terms; and
• operational dependencies.

Only after those pieces are understood should the seller move through the registry transfer and payment process.

A good IPv4 sale aligns the commercial transaction, registry record and intended operational state rather than treating any one of those layers as the whole transaction.

For organizations that no longer need their IPv4 holdings, selling can convert scarce infrastructure resources into immediate business value.

For organizations that still depend on the addresses, leasing or a structured sell-and-leaseback arrangement may deserve consideration before a permanent transfer.

Ready to sell surplus IPv4 resources? Sell IPv4 addresses to LARUS.