Organizations holding IPv4 address space face an increasingly important question:
What should you do when your IPv4 resources have significant value, but your network still depends on them?
The obvious choices appear to be either keeping the address space or selling it.
But there is another model worth considering: IPv4 sell-and-leaseback.
Under this structure, an organization can sell eligible IPv4 resources and continue using address capacity through a leasing arrangement.
This creates an alternative for businesses that want to unlock value from IPv4 without treating an address sale as an immediate requirement to renumber their entire infrastructure.
For organizations researching how to sell IP addresses, understanding the difference between owning IPv4 and maintaining operational access to IPv4 can change the decision entirely.
Why Organizations Consider Selling IPv4 Addresses
Companies accumulate IPv4 resources for many reasons.
Some received addresses when available pools were larger. Others acquired IPv4 through mergers, transfers, infrastructure expansion, or historical network requirements.
Over time, the role of those resources may change.
An organization may now be:
- Moving infrastructure to the cloud
- Consolidating data centers
- Expanding IPv6
- Reducing legacy network operations
- Restructuring its balance sheet
- Reassessing capital tied to network resources
- Holding more IPv4 than it needs directly
As a result, management may begin evaluating whether to sell IPv4 addresses.
However, determining that IPv4 has financial value is much easier than determining whether the organization can operate without it.
The Problem With a Simple IPv4 Sale
Imagine an enterprise owns a large IPv4 block that has been part of its infrastructure for years.
The addresses may be connected to:
- Public servers
- DNS records
- APIs
- Firewalls
- VPN gateways
- Customer allowlists
- SaaS integrations
- Monitoring platforms
- BGP announcements
Selling the block outright could require the organization to replace those addresses.
That creates a potentially significant renumbering project.
A network team may need to:
- Obtain replacement address space.
- Configure new routing.
- Update DNS.
- Change firewall policies.
- Update customer allowlists.
- Modify applications.
- Reconfigure VPNs.
- Update monitoring.
- Coordinate migrations with customers.
- Retire the old addressing safely.
Suddenly, monetizing IPv4 becomes much more than a financial transaction.
What Is IPv4 Sell-and-Leaseback?
IPv4 sell-and-leaseback separates two concepts that are often treated as the same thing:
Holding the IPv4 resource and using IPv4 capacity.
In a simplified structure:
Step 1: The organization sells eligible IPv4 resources.
Step 2: The organization enters into an agreement to lease back the address capacity it still requires.
The business therefore converts the underlying resource through a transaction while continuing to obtain the network capacity needed for operations.
This concept resembles sale-and-leaseback structures used with other business resources, although IPv4 has its own registry, routing, contractual, and operational considerations.
Why Would a Business Sell IP Addresses It Still Uses?
At first, the idea can sound contradictory.
If an organization still needs the addresses, why sell them?
Because the business may value continued network use more than direct resource holding.
Those are not necessarily the same objective.
Consider a company whose priority is:
- Stable public IPv4 capacity
- Predictable routing
- Customer continuity
- Operational flexibility
- Reduced internal administrative burden
The company may not necessarily need direct holding to accomplish those goals.
A sell-and-leaseback structure can therefore change the question from:
“Do we still need IPv4?”
to:
“Do we still need to hold IPv4 directly?”
That is a very different strategic decision.
Benefit 1: Unlock Value From IPv4 Resources
One of the clearest reasons organizations choose to sell IP addresses is financial.
An IPv4 block sitting on an organization’s network may represent significant value.
Selling can convert that resource into deployable capital.
That capital could potentially support:
- Network expansion
- Cloud infrastructure
- Server upgrades
- Data center investment
- IPv6 migration
- Product development
- Acquisitions
- Debt reduction
The sell-and-leaseback approach can make this option more practical for businesses that still require IPv4 capacity after the transaction.
Benefit 2: Avoid Immediate Network Renumbering
Renumbering production infrastructure can be complicated.
An IP address may have dependencies that are not obvious when looking only at routing tables.
Customers may have placed it in an allowlist years ago.
A third-party platform may use it for API authentication.
A security team may have written firewall policies around it.
A legacy service may still depend on it.
Changing addresses therefore creates operational work throughout the organization.
If a sale-and-leaseback structure allows existing address capacity to remain operational under the agreed arrangement, the business can potentially avoid treating the transaction as an immediate wholesale migration.
For infrastructure teams, that can be one of the most important differences between a conventional sale and a sell-and-leaseback model.
Benefit 3: Separate Network Use From Resource Holding
IPv4 discussions often assume that the party using an address must also be the party directly holding the underlying resource.
Modern Internet infrastructure already demonstrates that this is not always necessary.
Businesses routinely use IP address space obtained through:
- Cloud providers
- Internet service providers
- Hosting companies
- IPv4 leasing providers
- Network partners
The operational requirement is usually access to stable, usable, routable address capacity.
Direct holding is one structure for achieving that goal, but it is not the only structure.
Benefit 4: Reconsider Registry-Layer Exposure
Holding IPv4 directly also means maintaining the organizational and contractual relationship associated with the relevant registry framework.
That can involve:
- Resource records
- Administrative standing
- Contractual requirements
- Policy obligations
- Transfer procedures
- Compliance processes
Organizations should therefore evaluate not just the benefits of direct holding, but also the administrative and continuity responsibilities attached to that structure.
This issue is central to LARUS’s sell-and-leaseback model. LARUS positions itself as the first-party buyer and operator after closing, allowing the seller to continue obtaining IPv4 capacity while moving the direct resource-holding relationship into a specialist structure.
Organizations considering this approach can learn more about how to sell IP addresses to LARUS.
Sell-and-Leaseback vs Selling IPv4 Outright
The two approaches have different objectives.
Selling IPv4 Outright
A conventional sale may be appropriate when:
- The addresses are permanently surplus.
- The organization does not expect to use them again.
- No important operational dependencies remain.
- The business wants a complete exit from the resource.
Once the transition is complete, the seller moves forward without depending on that address capacity.
Sell-and-Leaseback
Sell-and-leaseback may be considered when:
- The organization wants to monetize IPv4.
- Network operations still depend on address capacity.
- Renumbering would create unnecessary disruption.
- Continued IPv4 access remains important.
- Direct holding is no longer the preferred structure.
The distinction is primarily about continuity after the sale.
What Should Organizations Check Before Selling IPv4?
Whether an organization sells outright or uses a sale-and-leaseback structure, due diligence is important.
1. Confirm Which Addresses Are Actually Needed
Begin with a utilization audit.
Identify:
- Active prefixes
- Reserved addresses
- Production services
- Customer assignments
- Routing dependencies
- Disaster-recovery resources
This determines how much address capacity the organization needs after the transaction.
2. Map DNS Dependencies
Search for DNS records connected to the address space.
These may include:
- A records
- MX infrastructure
- Nameservers
- API endpoints
- Legacy services
Documenting these dependencies helps determine the operational cost of changing addresses.
3. Review Customer Allowlists
Customers and partners may have authorized specific IP addresses.
Changing those addresses can require coordination with potentially hundreds of external organizations.
For some businesses, this alone can make retaining the same operational address capacity valuable.
4. Review BGP Routing
Understand:
- Current origin ASN
- Upstream providers
- Existing advertisements
- Route objects
- Prefix filters
If the addresses will continue to be used after the transaction, routing continuity needs to be planned carefully.
5. Review RPKI and ROA
Route Origin Authorization should match the intended post-transaction routing arrangement.
Questions include:
- Which ASN will originate the block?
- Who manages the ROA?
- Will the current authorization remain appropriate?
- How quickly can changes be made?
A commercially completed transaction still needs technically valid routing.
6. Check Reverse DNS
PTR records may be associated with:
- Mail infrastructure
- Servers
- Hosting platforms
- Monitoring
If the organization continues using the address capacity, clarify how reverse DNS will be administered after the transaction.
7. Evaluate IP Reputation
Addresses accumulate operational history.
Check the block for:
- Spam history
- Blocklists
- Abuse records
- Security reputation
For continued use, preserving a known address block may sometimes be preferable to migrating immediately to replacement space with a different history.
8. Review Geolocation
Address geolocation can affect:
- Customer experience
- Security tools
- Regional services
- Fraud systems
If the same addresses continue being used in the same environment, maintaining geolocation continuity may reduce operational friction.
What Makes a Good Sell-and-Leaseback Partner?
The counterparty matters.
A sell-and-leaseback arrangement creates an ongoing relationship rather than ending at the sale.
Organizations should therefore evaluate several factors.
Is the Buyer a Direct Counterparty?
Understand whether the transaction involves a first-party buyer or multiple intermediaries.
More contractual layers can create more dependencies when routing, renewal, rDNS, abuse, or other issues need resolution.
Can the Buyer Support Long-Term Use?
The organization should understand what happens after the transaction.
Ask about:
- Lease duration
- Renewal
- Address continuity
- Replacement procedures
- Support
Who Manages Routing?
The routing model should be clear from the beginning.
Who Controls RPKI?
ROA management can directly affect whether the address space remains validly routed.
How Is Abuse Managed?
A production network requires clear processes for legitimate abuse reports.
How Is rDNS Managed?
Organizations depending on PTR records should establish who controls reverse DNS after closing.
First-Party Buyer vs Broker
Another distinction is whether the company buying IPv4 becomes the ongoing operator or merely introduces the seller to another party.
A broker typically facilitates a transaction between buyer and seller.
A first-party buyer purchases the resource directly.
In a sell-and-leaseback structure, this distinction becomes especially important because the relationship continues after closing.
LARUS describes its model as first-party: it buys IPv4 directly and can become the ongoing leasing and continuity counterparty rather than simply introducing two independent parties.
That can simplify responsibility for organizations that prioritize operational continuity over a purely transactional sale.
Is Sell-and-Leaseback Suitable for Every IPv4 Holder?
No.
Some organizations should simply keep their IPv4.
Others may be better served by selling resources completely.
Sell-and-leaseback is most relevant when three conditions exist at the same time:
1. The IPv4 resource has value the organization wants to unlock.
2. The organization still needs public IPv4 capacity.
3. Direct holding is no longer strategically necessary.
If the company expects to stop using IPv4 entirely, leasing the capacity back may provide little benefit.
Likewise, if direct resource holding is strategically important to the organization, retaining the resource may be preferable.
What About IPv6?
IPv6 should be part of any long-term address strategy.
But migrating to IPv6 does not necessarily remove every IPv4 requirement immediately.
Organizations may still depend on IPv4 because of:
- Customer networks
- Third-party integrations
- Legacy applications
- Security systems
- External services
- Compatibility requirements
This creates a transition period where IPv6 adoption grows while IPv4 remains operationally necessary.
Sell-and-leaseback can be considered within that broader transition strategy.
An organization could monetize IPv4 resources, retain the capacity it currently requires, and gradually reduce that requirement as IPv6 adoption increases.
How Much IPv4 Should You Lease Back?
Organizations do not necessarily need to lease back the entire amount sold.
Suppose a company holds a /16 but only actively requires a portion of that capacity.
It could first determine:
- Current utilization
- Growth expectations
- Redundancy requirements
- IPv6 migration forecasts
- Customer demand
The resulting analysis can help determine how much IPv4 capacity must remain available operationally.
This makes the transaction part of a broader address-management strategy rather than simply a sale.
A Practical Decision Framework
Keep IPv4 Directly When:
- Direct holding is strategically important.
- Future network demand is expected to grow significantly.
- The resources are deeply integrated into long-term plans.
- The organization is comfortable managing the associated administrative structure.
Sell IPv4 Outright When:
- The addresses are permanently surplus.
- The organization no longer needs the capacity.
- Renumbering or retirement is already planned.
- An ongoing IPv4 relationship is unnecessary.
Sell and Lease Back When:
- Capital can be unlocked from the resource.
- Continued IPv4 use remains necessary.
- Operational continuity matters.
- The organization prefers a specialist first-party counterparty for ongoing address capacity.
Questions to Ask Before You Sell IP Addresses
Before choosing any transaction structure, ask:
- How much IPv4 do we currently hold?
- How much do we actively use?
- Which applications depend on these addresses?
- Which customers have them allowlisted?
- What would renumbering cost?
- How much IPv4 will we need in three years?
- Can IPv6 reduce that requirement?
- Do we need to hold IPv4 directly?
- Would leasing back capacity preserve operations?
- Who would carry the ongoing administrative and continuity responsibilities?
These questions turn an IPv4 sale from a short-term pricing decision into a long-term network strategy.
Final Thoughts
Organizations investigating how to sell IP addresses should not assume that selling automatically means giving up the ability to use IPv4.
Direct resource holding and operational address use are separate questions.
A conventional sale can make sense when IPv4 is genuinely surplus and no longer needed.
But organizations that want to monetize their resources while maintaining production IPv4 capacity can also evaluate a sell-and-leaseback structure.
The goal is to balance three priorities:
Capital, continuity, and control.
For some organizations, keeping IPv4 will remain the best option.
For others, selling outright will be appropriate.
And for companies that want to unlock value without immediately disrupting the networks built around their existing address capacity, sell-and-leaseback offers a third path.
Organizations evaluating this model can review how to sell IPv4 addresses to LARUS and continue obtaining required address capacity through a first-party operating structure.
Frequently Asked Questions
Can I sell IP addresses and continue using them?
A sell-and-leaseback structure can allow an organization to sell eligible IPv4 resources and then continue obtaining address capacity through a leasing arrangement, subject to the agreed transaction and operational structure.
Why would a company sell IPv4 addresses it still needs?
A company may want to unlock value from IPv4 resources while continuing to use public address capacity. Selling and leasing back separates direct holding from operational use.
What is IPv4 sell-and-leaseback?
It is a structure in which IPv4 resources are sold and the seller subsequently leases address capacity for continued network use.
Can selling IPv4 cause network disruption?
It can if the transaction requires immediate renumbering or routing changes. DNS, firewalls, BGP, RPKI, customer allowlists, APIs, and other dependencies should be reviewed before any transition.
What should I check before selling IPv4 addresses?
Review utilization, future requirements, DNS, BGP routing, RPKI, reverse DNS, reputation, geolocation, customer allowlists, and the proposed post-sale operating structure.
Is selling IPv4 better than leasing it?
Neither model is universally better. Selling can unlock immediate value, while leasing can preserve operational access without permanent resource acquisition. Sell-and-leaseback combines elements of both.
What is the difference between an IPv4 broker and a first-party buyer?
A broker generally facilitates a transaction between independent parties. A first-party buyer purchases the IPv4 resource directly and becomes the transaction counterparty.
Does IPv6 eliminate the need for IPv4 sell-and-leaseback?
Not necessarily. Organizations may continue requiring IPv4 while deploying IPv6. Sell-and-leaseback may be relevant during that transition when IPv4 capacity is still operationally necessary.
