Summary
- North American enterprise legacy holders are not address specialists; they are banks, manufacturers, insurers, retailers, airlines and other mature companies whose inherited IPv4 ranges have become latent capital only if title, authority, routing, reverse-DNS and reputation evidence can be made current.
- Dormant or underused enterprise holdings are not automatically available supply: internal dependency, subsidiary rights, renumbering risk, lease reputation, M&A history and transfer timing all determine whether a block can be sold, leased, divided or prudently held.
- The useful ARIN role is narrow but economically decisive: protect uniqueness and accurate records, verify current authority, keep legacy-resource service states intelligible and make legitimate transfer-readiness predictable without becoming a planner of corporate address strategy.
The audit room finds a balance-sheet ghost
The first discovery is rarely made by the network team. It appears in a board-risk pack, a divestiture schedule, a cyber-insurance questionnaire, a treasury review or an internal audit of data-centre exits. A large company is preparing to sell a subsidiary, renew a major insurance policy, move a recovery site, answer a banking due-diligence request or document externally reachable systems after a security review. Buried among old diagrams, firewall rules, partner allowlists and public registration records is an IPv4 range that has been in the business for decades. It is visible. It is scarce. It may be worth money. Yet the company cannot immediately say who controls it in a legally useful way.
The range may still route. It may appear in public records under a predecessor name. It may be used by a few systems that nobody wants to disturb. Reverse DNS may still point to an operating name that disappeared after a merger. A retired engineer may have managed the original record. A provider may have maintained part of the routing state under an outsourcing contract. A subsidiary may believe it has always used the space and should keep using it. The parent may believe the space belongs to the group. The buyer in a carve-out may expect enough address capacity to keep the acquired business running. The address block is real enough to matter and messy enough to delay.
That is the enterprise legacy-holder problem in the ARIN region. The company is not a carrier, hoster, cloud platform or address specialist whose inventory is the product. It is a bank, insurer, manufacturer, airline, logistics group, retailer, media company, industrial firm, technology conglomerate or other mature enterprise that obtained or inherited public IPv4 space during an earlier Internet. The space entered the organization as infrastructure. Scarcity has made it behave like latent capital. It can support continuity, preserve bargaining power, reduce dependence on providers, be leased, be sold or be held as reserve. But each option is only useful if the company can prove that the public record, corporate history and present authority all line up.
The meeting therefore becomes uncomfortable. Treasury sees a balance-sheet opportunity that may not have been recorded as an asset. Legal sees succession evidence, old corporate names, officer authority, confidentiality, tax, representations and the risk of selling something that another group company still needs. Information security sees exposure, reputation and abuse handling. Network staff see brittle dependencies in firewalls, monitoring systems, source allowlists, disaster-recovery plans and partner connections. Internal audit sees undocumented control. Corporate development sees a deal issue. The board sees a small technical item that could become a governance embarrassment if handled casually.
IPv4 scarcity has turned forgotten administrative history into present corporate choice. The ARIN ledger gives outsiders a starting point for who is recognized. It does not by itself solve the corporate question. A public entry may name an entity that no longer exists in that form. A working route may show operational use without proving signatory power. An old letter may support history without proving current approval. A broker's valuation may assume clean transfer when the evidence file is not clean. The address economy therefore forces non-network enterprises to do something they were never organized to do: treat a historic numbering record as capital whose usefulness depends on proof.
For ARIN, the issue is also a test of registry discipline. The registry has a legitimate role in protecting uniqueness, maintaining accurate public records, preventing false transfers, preserving reverse-DNS and routing-related continuity, and recognizing authorized changes. It also sits at a point where delay, service labels, agreement boundaries and evidentiary thresholds affect the price and mobility of scarce inputs. The useful question is not whether ARIN should ask for proof. It should. The question is whether it can keep proof narrow enough that the ledger becomes more reliable without turning enterprise-held IPv4 into capital trapped behind avoidable uncertainty.
What makes an enterprise legacy holder different
An enterprise legacy holder is a non-network corporation whose historical public IPv4 range is not its main product, but remains a scarce operational and financial position. The distinction matters. A regional access provider, data-centre company or hosting platform normally understands address capacity as direct inventory. It buys, leases, routes, subdivides and manages addresses because that work is part of customer delivery. A bank or manufacturer may have the same kind of public numbering in registry terms, but its internal culture treats it as infrastructure residue. It is important when it breaks and invisible when it works.
The enterprise may hold a large aggregate, several smaller legacy ranges, or fragments inherited through acquisitions. Its address use may be mixed. Some space may support live services. Some may be parked in old network plans. Some may be announced only for remote access, mail, partner systems, monitoring, recovery or industrial links. Some may be unused but feared because nobody has tested every dependency. Some may have been informally lent to a subsidiary, service provider or historical joint venture. In ordinary corporate language all of that may be described as "the network." In a scarcity economy it is a portfolio of choices.
The economic feature of this portfolio is optionality. A company can keep the space as a reserve, allocate it to a subsidiary, use it for disaster recovery, support a migration, hold it as a hedge against provider lock-in, lease a clean portion, sell a block after renumbering, or use its existence in negotiations with managed-service providers. A range that appears idle may still be valuable because it gives management room to act later. But optionality is not the same as liquidity. An option that cannot be exercised because the company cannot prove control is worth less than one backed by current records and corporate authority.
Enterprise legacy holders therefore differ from professional address holders in three ways. First, they often lack a single internal owner. The network team may know the routes but not the legal history. Legal may know merger documents but not public addressing. Treasury may value the block but not understand reverse-DNS or route-origin evidence. The corporate secretary may hold name-change filings but not know why they matter to ARIN. Second, they face asymmetric career risk. A successful sale may produce a one-time gain. A failed renumbering, abuse incident or disputed authority file can damage reputations inside the company for years. Third, their address decisions compete with many larger corporate priorities. If the issue is not forced by a deal, audit or outage, it can be postponed indefinitely.
This makes enterprise supply more cautious than headline scarcity arguments suggest. A theoretical surplus in a bank or industrial group does not automatically become available capacity for the wider Internet. Management needs confidence that selling or leasing will not harm operations, create a reputational problem, trigger a tax surprise, breach a contract, strand a subsidiary or invite a dispute over who had authority. A company whose core business is aviation, payments, manufacturing or retail will not build an address desk merely because prices look attractive. It will act when evidence, governance and execution risk are clean enough.
The term "legacy" also needs care. It does not mean defective. It means the history of the resource may predate ARIN's current contractual and account practices. ARIN was formed in 1997 and inherited administration of earlier IPv4 and ASN records not already administered by other established regional registries. Early public address allocations often reflected a different era of abundance, looser documentation and large institutional demand. Many records were created before today's transfer economy, routing-security expectations and account controls existed. That history can make a resource stronger in one sense, because the allocation may have deep continuity, and weaker in another, because the proof may be scattered across corporate archives.
Enterprise legacy holders sit at that intersection. They are not necessarily speculators. They are not necessarily hoarders. They are companies that carried a useful technical position through decades of corporate change until scarcity made the position financially visible. Some should monetize. Some should keep. Some should divide. Some should clean evidence and wait. The policy problem is not to force the same answer on all of them. It is to reduce the cost of finding the right answer without weakening the registry record that others rely upon.
Why ARIN's region has so many quiet corporate ranges
ARIN is a particularly important place to examine enterprise legacy holders because of North America's early role in the commercial Internet. Large corporations, banks, insurers, manufacturers, airlines, universities, technology firms, media groups, retailers, transport networks and industrial companies connected early, built large internal networks, and often received public address space when conservation had a different meaning. Universities are a separate category with their own mission and governance issues. The enterprise category is different: the holder's business is not research networking, public administration or address sales. The holder is a commercial or corporate institution that may have treated public IPv4 as a useful input rather than strategic capital.
Early allocation practice gave some organizations more public numbering than their current architectures would require if designed from scratch. Over time, private addressing, NAT, outsourcing, cloud migration, managed security services, data-centre consolidation and vendor platforms reduced visible internal use. Yet the old space did not disappear. It remained in public records, routing tables, firewall assumptions, mail systems, monitoring policies, VPN sources, partner allowlists and merger files. Some ranges were renumbered out of active use. Some became reserves. Some were forgotten. Some became embedded in the few systems most resistant to change.
The North American economy also created frequent corporate succession. Banks merged across states and provinces. Insurers consolidated brands. Airlines absorbed carriers and alliances. Manufacturers sold divisions, closed plants and separated industrial lines. Retailers bought e-commerce businesses and distribution networks. Media groups merged content, advertising and cable assets. Technology conglomerates acquired firms with their own network histories. Each event can leave public address records behind the business line, the parent, the buyer or a shared services group. The legal entity that requested the space may not be the entity using it today. The route may be operationally continuous while the authority story is fragmented.
ARIN's post-exhaustion environment makes this more valuable. Its free pool was depleted in 2015. Since then, meaningful IPv4 growth in the region has depended on waiting-list fragments, transfers, acquisitions, leases, internal reuse and legacy holdings. ARIN has a mature transfer framework and a region with deep demand from carriers, hosting companies, cloud platforms, security firms, financial services, enterprise networks and infrastructure buyers. That maturity increases the price signal. It also raises the diligence standard. A non-network enterprise that once ignored its old ranges may now receive serious inquiries from brokers, buyers, lessees, lenders or auditors.
ARIN's legacy-resource boundary sharpens the point. Holders outside a current ARIN agreement may still have certain core registration and reverse-DNS functions, while other services, including ARIN-hosted routing-security or routing-registry capabilities, may require agreement coverage. A holder deciding whether to monetize or modernize must evaluate the service benefits, fee exposure, policy relationship and legal terms together. That decision is not simply administrative. It affects whether a buyer sees the block as ready, whether a lessee trusts routing support, and whether internal counsel views the company's position as protected or exposed.
The result is a large, uneven reservoir of quiet corporate capacity. It matters because meaningful IPv4 supply can emerge there without new allocation. ARIN's challenge is to make that emergence safer when holders choose it, not to command it. Enterprise holders will release capacity when cash value exceeds internal option value and when the proof path is predictable.
How administrative residue became latent capital
The transformation of old public address space into latent capital did not happen because a board suddenly became interested in packet routing. It happened because scarcity gave an old coordination record new economic meaning. When addresses were abundant, an allocation file was a way to make sure the same number range was not assigned twice and that the right network could be contacted. After exhaustion, that same file became a gate into transfer value, leasing yield, continuity assurance and bargaining power.
Scarcity does not make every address block equally valuable. Size matters, but so do reputation, transferability, registry status, route history, reverse-DNS control, routing-security readiness, corporate authority and the absence of hidden dependencies. A large block with unclear succession can trade at a discount or not trade at all. A smaller block with current records, clean reputation and obvious authority can be easier to monetize. The asset is therefore not just the count of addresses. It is the count plus confidence that the holder can lawfully and practically use, delegate, lease, transfer or reserve them.
For a non-network enterprise, this creates a recognition gap. Internal asset systems may list offices, vehicles, aircraft parts, software licenses, patents, insurance recoveries and data-centre contracts. They may not list an IPv4 range as a financial asset. The network team may maintain spreadsheets or IP address management entries, but those do not automatically feed treasury. The legal department may have acquisition agreements but no prefix schedule. The corporate secretary may have merger filings but no idea that a registry may ask for them. Accounting may treat the addresses as part of operating infrastructure rather than as a separable position. Scarcity exposes the gap.
The first corporate response is often over-simple. One camp says the space is unused and should be sold. Another says it is part of the network and should not be touched. Both may be wrong. A portion may be unused. Another portion may be essential. Another may be usable after a renumbering plan. Another may have reputational problems that require cleaning before any lease. Another may belong more naturally with a subsidiary that depends on it. The useful corporate exercise is not a yes-or-no vote. It is a classification of choices and constraints.
Latent capital has value because it can be activated under different conditions. A bank may keep address space for recovery and supplier independence. An insurer may reserve it for claims-system continuity. A manufacturer may use it to avoid disrupting plant links or vendor access. A logistics group may need stable public sources for customs, tracking, airport and port interfaces. An airline may have partner systems that still recognize fixed ranges. A retailer may value the ability to operate payment or fraud systems outside a single provider's numbering. In each case, the financial value of keeping the block may exceed the sale price, at least until dependencies are mapped.
Leasing adds another option, but not a free one. Leasing can produce income while preserving long-term control, yet it introduces counterparty risk, abuse handling, reputation exposure, routing coordination, contract enforcement and internal monitoring. A non-network enterprise may not want its brand associated with a lessee's mail abuse, scraping, fraud complaints or law-enforcement inquiries. It may decide that leasing is acceptable only through a managed structure, with clear termination rights, screening, monitoring, logs and a route back to clean use. Yield must be adjusted for those burdens.
Sale is cleaner in one sense because it can remove continuing responsibility. It is messier in another because it requires the company to surrender optionality. The one-time cash gain must be compared with future flexibility, disaster-recovery value, bargaining power, provider independence and the cost of renumbering. In a stressed balance sheet, the cash may win. In a regulated bank or infrastructure-heavy industrial company, the reserve may win. The correct answer depends on evidence and risk appetite, not on a slogan about unused space.
The latent-capital frame also explains why old ranges can sit idle for years. Idleness is not always waste. It may be a rational response to uncertainty. If a company cannot tell whether a range is free of dependencies, whether the registry record is clean, whether a subsidiary will claim it, whether a transfer can close, or whether leasing will contaminate reputation, inaction preserves the option. The wider address economy may dislike that result. But the way to mobilize supply is to reduce uncertainty, not to treat all reserve capacity as bad faith.
Custody inside the corporation is fragmented by design
The hardest part of enterprise IPv4 is often not ARIN's external process. It is the corporation's internal map. Public address space touches several departments whose incentives do not naturally align. The network team wants continuity and technical clarity. Treasury wants valuation, cash, yield and capital efficiency. Legal wants authority, warranties, contract terms, evidence and risk allocation. The corporate secretary wants proper approvals and clean entity records. Information security wants abuse control, exposure reduction, reputation protection and incident-response clarity. Internal audit wants documented ownership, access controls and change evidence. Business units want not to be disrupted.
This fragmentation is normal in a large company. It becomes a problem when no one has final custody. The network team may have operational knowledge but not approval power. Legal may have approval power but lack technical facts. Treasury may push monetization without knowing that a payment partner still relies on an old allowlist. A subsidiary may route part of the range through its own provider while the parent holds the registry record. A managed-service vendor may operate systems that expose the address space without owning the underlying authority. If a broker calls, the company may not know who may answer.
A strong enterprise process assigns custody before a transaction. That does not mean network staff lose control of technical use. It means the company identifies a cross-functional owner for the address portfolio, evidence file and external communications. The owner should maintain a list of all ranges, the recognized holder name, current contacts, agreement status, reverse-DNS control, routing-security state, current advertisements, internal assignments, dependent systems, subsidiaries that use the space, vendors with control, and any planned sales or leases. Without that map, each decision begins with rediscovery.
Internal authority should also be separated by action. A technical manager may maintain reverse DNS and routing-related records. A legal officer may approve a sale. Treasury may approve valuation and commercial terms. Information security may approve lease conditions and abuse response. Corporate secretary may certify the officer and entity chain. A business unit may approve renumbering of services it uses. Treating one person's login or institutional memory as enough for all actions is dangerous. It invites both internal error and external doubt.
The company also needs a clear story for subsidiaries. Many legacy ranges predate modern group structures. A parent may have received the original allocation and later spread use across subsidiaries. A subsidiary may have acquired a business that brought part of a range into the group. Another may have been divested but kept temporary use under a transition agreement. If the parent sells the range without resolving these histories, it may create post-closing disputes. If a subsidiary assumes the space is its own without proof, it may delay a sale or audit. The internal map should identify legal entity, operational user and approval path separately.
Information security adds a separate reason for custody. Public IPv4 space carries reputation memory. If the company leases a range, the lessee's behavior can affect mail filtering, blocklists, fraud systems, upstream acceptance and future buyer confidence. If an old range has been misused by a contractor or forgotten system, cleaning it may require a documented remediation path. If reverse DNS points to obsolete names, security teams may misunderstand alerts or external parties may question control. Good custody therefore includes reputation monitoring and abuse-response procedures, not only registry paperwork.
Treasury should resist the temptation to value addresses before custody is understood. A simple price-per-address estimate is the easiest number to produce and often the least useful. The right valuation starts with clean, restricted and burdened categories. Clean space is available for sale or lease after normal approval. Restricted space can become available after renumbering, dependency removal or subsidiary negotiation. Burdened space supports live systems, regulated operations, contracts or unresolved authority. The company may still decide to monetize restricted or burdened space, but it should price the work and risk openly.
Corporate succession is where authority decays
Enterprise legacy holdings become difficult because companies change faster than registry records. Name changes, mergers, acquisitions, divestitures, bankruptcy sales, subsidiary dissolutions, outsourcing contracts, management turnover and data-centre migrations all reshape the real company while an old public entry can remain stable for years. Stability is useful for routing. It can be dangerous for authority. A record that still works operationally may no longer explain who may act.
Consider a manufacturer that received address space before ARIN's formation, later merged into a holding company, sold two divisions, closed several plants and outsourced its network operations. The public record may still contain the old manufacturer name. The routing may now be handled by a managed provider. A small part of the space may support a plant sold to another company under a transition deal. Another part may be idle. If the holding company wants to sell the aggregate, it must prove more than current desire. It must show how the recognized holder relates to the present legal entity, whether the assets moved, which officer may sign, and whether any divested party has a right or dependency.
The documents are often imperfect. Old allocation letters may be missing. Purchase agreements may refer to "network assets" without naming prefixes. Board minutes may have approved a merger without discussing address resources. Outsourcing contracts may grant a provider operational control without registry authority. A subsidiary dissolution may have moved assets by operation of law, but the registry file may not say so. A retired employee may have answered ARIN emails for years without formal delegation. None of these facts necessarily defeats the holder's claim. Together they create evidentiary work.
For ARIN, corporate succession is a fraud-control problem as well as a service problem. A registry should not let a person with a plausible old email move a valuable range if the entity chain is unclear. A buyer should not receive recognition from a seller that cannot prove it speaks for the holder. A revived shell with a similar name should not be able to displace a living successor. Strong proof protects legitimate enterprise holders from capture. Yet if proof requests are broad, unpredictable or slow, legitimate corporate change becomes expensive to regularize.
The strongest approach is fact-specific. If the issue is a name change, ask for name-change evidence. If the issue is merger continuity, ask for documents showing the predecessor became the successor. If the issue is asset transfer, ask for the relevant schedule or a reliable substitute showing that network assets moved. If the issue is officer authority, ask for a current certificate or approval. If the issue is a dispute, label and isolate the dispute. A request for "more documents" without naming the missing link increases cost without necessarily increasing confidence.
Succession also interacts with ARIN's transfer categories. A company selling unused space to a third party may need first to clean the holder record or use an appropriate merger, acquisition or reorganization path if the current claimant is a successor. A divestiture may require deciding whether a subsidiary receives address space through a transfer, temporary use, service agreement or compensation. An inter-regional transaction may add another registry's requirements. The company that treats these issues as a closing-week detail can lose time and bargaining power.
The career-risk dynamic explains why many enterprises postpone. Nobody gets promoted for discovering that an old merger file is missing an address schedule. A legal team may prefer to wait until a transaction justifies the cost. A network team may fear that asking for updates will disturb working systems. Treasury may not want to spend money proving an asset that accounting has never recognized. The result is stale authority until the point of maximum pressure. By then, a buyer is waiting, a carve-out deadline is running, or an audit finding needs a response.
The better discipline is evidence preservation before monetization. Every enterprise with legacy space should gather historical allocation material, registry correspondence, corporate name-change and merger files, acquisition agreements, officer delegations, provider contracts, routing and reverse-DNS records, and dependency maps. The file should explain not only how the company got the range, but why the current signer may act. It should be updated after every merger, divestiture or outsourcing change. Corporate succession will never be perfectly tidy. It can at least be made explainable.
Dormant supply is rationally reluctant
The address economy often treats enterprise legacy holdings as a dormant supply pool. That is partly right. Non-network companies may hold ranges that exceed current use. Data-centre exits, cloud migration, private addressing, security redesign and consolidation can leave public space underused. A bank that once numbered many systems publicly may now expose only narrow gateways. A retailer may have moved store networks and payment systems behind provider services. A media group may have inherited space from old online properties that no longer operate. An airline or logistics company may use only a fraction of a historic range.
But latent supply is not available supply. Enterprises hesitate because the upside is visible and the downside is personal. A sale produces a measurable gain. An outage after renumbering produces blame. A lease produces yield. A lessee's abuse can create public complaints, blocklisting or legal notices. A transfer can clean the balance sheet. A later dispute with a divested subsidiary can make the approval look careless. A reserve may look inefficient to treasury. Losing it may look reckless after a crisis. In large companies, the person recommending action carries risk that the price rarely compensates.
Reluctance is therefore rational. A company does not evaluate IPv4 like a professional trading desk. It evaluates it like a risk-bearing institution whose main revenues depend on something else. A bank's primary concern is not maximizing address yield; it is avoiding disruption to payments, treasury links, customer portals and regulatory systems. An airline worries about reservations, loyalty platforms, cargo systems and airport integrations. A manufacturer worries about plants, suppliers and industrial control. A logistics group worries about tracking, customs, depots and partner interfaces. These concerns can justify holding more space than current utilization suggests.
Renumbering is a particular source of fear. In a clean diagram, moving services to new addresses looks manageable. In a mature enterprise, public ranges can be embedded in supplier allowlists, fraud engines, VPN configurations, certificates, firewall rules, monitoring systems, incident-response plans, mail reputation, batch processes and old contracts. Some dependencies belong to third parties that move slowly. Some belong to systems that no current employee fully understands. Some are not found until after a change. The cost of renumbering is not only engineering. It is coordination across organizations that may not care about the seller's address strategy.
Leasing has its own hesitation. It may look attractive for idle space, especially if the company wants to preserve future control. Yet leasing requires the enterprise to become a steward of counterparty behavior. It must know who uses the space, for what, under what contract, with what abuse response, routing plan, termination path and reputation monitoring. If the lessee causes harm, the public may not distinguish the lessee from the holder. If the company later wants to sell, a buyer will ask whether any lease rights, reputation damage or routing dependencies remain. Yield is real, but so is the administrative burden.
Selling creates finality, but only after the company decides what it is giving up. A reserve may be worth more than cash if the business expects future migrations, acquisitions, customer requirements or provider pressure. In a crisis, public address capacity can provide independence. In a carve-out, it can reduce transition friction. In vendor negotiations, it can improve leverage. In a data-centre exit, it can support parallel operation. These option values are hard to price, so they are easily ignored. Sensible boards should not ignore them.
The public policy lesson is that dormant supply moves when trust improves. If holders believe that cleaning records will trigger open-ended scrutiny, they wait. If they believe that selling will expose them to uncertain registry treatment, they wait. If they believe that leasing will contaminate reputation without a clear way to prove control and responsibility, they wait. Heavy pressure can therefore preserve idleness. Clear proof paths, reliable service labels and bounded review are more likely to mobilize supply than moral pressure against corporate reserves.
Valuation begins with exercisable choice
The treasurer's first question is usually simple: what is the block worth? The better question is: what choices can the company actually exercise? A range with many addresses but weak authority may have a large theoretical price and a low practical value. A range with clean documentation, current contacts, known dependencies, good reputation and predictable transfer steps can be converted into cash, yield or resilience more easily. Valuation should therefore begin with exercisability.
The company should build several cases. In the hold case, the range remains a strategic reserve. Value comes from continuity, provider independence, future migration capacity, subsidiary support and bargaining power. Carrying costs include record maintenance, audit, abuse response, internal custody and opportunity cost. In the lease case, the range generates recurring income while the company keeps long-term control. Value is yield adjusted for counterparty risk, reputation, monitoring, routing coordination and contract enforcement. In the sale case, the company receives cash and sheds future responsibility. Value is price less renumbering cost, legal cost, tax, closing risk and lost optionality.
There are hybrid cases. A company may sell a clean portion and reserve the rest. It may lease only through a specialist structure with strict abuse controls. It may transfer a range to a subsidiary as part of a carve-out and receive compensation elsewhere in the deal. It may keep a smaller public footprint and sell the remainder after a staged renumbering. It may hold space until a major migration completes, then revisit. These choices are economically different. Treating the range as a single lump can destroy value.
Collateral-like thinking should be cautious but not dismissed. Lenders may avoid treating IPv4 as simple property, yet they can still care about address-supported revenue, lease income, sale proceeds and operational resilience. A company with clean address evidence may be more bankable than one whose critical services depend on poorly documented public space. A lender financing a carve-out may ask whether the buyer receives enough address capacity or whether it must renumber quickly. A lender financing an address-rich company may ask whether the resources can be sold if needed. None of this requires an exaggerated legal theory. It requires confidence in control and transfer path.
Valuation discounts should be explicit. Weak chain of custody, stale contacts, old corporate names, missing officer authority, unclear subsidiary use, questionable reverse DNS, uncertain route-origin support, reputation damage, existing leases, unresolved abuse history and ambiguous agreement status all reduce value. Some discounts can be cured. Others can only be priced. If a block needs six months of renumbering work before sale, the discount is timing and labor. If a predecessor's succession evidence is missing, the discount is legal uncertainty. If a portion is essential to disaster recovery, the discount may be a decision not to sell at all.
The best valuation report should end with a decision tree, not a single number. It should state which ranges are clean, which are dependent, which are disputed or uncertain, which can be monetized after specific cures, and which should be held. It should estimate price under low, base and high evidence-quality cases. It should identify who must approve each branch. It should treat ARIN-facing proof as part of capital discipline. The company is not merely valuing addresses. It is valuing its capacity to act.
Liquidity discounts are evidence discounts
Every market discounts uncertainty. IPv4 is no exception. A clean ARIN-region block with current holder information, validated contacts, clear authority, good reputation, aligned reverse DNS, understood route-origin state and no hidden dependencies will attract more confidence than an equally sized block with stale public records and a murky corporate story. The difference is not only legal risk. It is time, attention, escrow, warranties, lender comfort and buyer confidence.
The first discount is chain of custody. A buyer wants to know how the current seller connects to the recognized holder. If the holder name is a predecessor, the seller must show merger or succession. If a business line was acquired, it must show the relevant assets moved. If the space was assigned across subsidiaries, it must show that the selling entity can act. If an officer signs, the buyer wants proof that the officer can bind the correct entity. Each missing link widens the spread between headline value and executable price.
The second discount is contact staleness. Public contacts that bounce, old role accounts, retired employees and unmanaged domains do not merely inconvenience ARIN. They suggest that the company may not control the registry-facing surface. A stale contact can be benign. It can also indicate account recovery risk, internal neglect or a possible path for capture. Buyers, lessees and lenders do not know which without proof. They price the uncertainty.
The third discount is service uncertainty. Reverse DNS, DNSSEC, routing-security services and routing-registry entries can matter to customers and counterparties. A buyer that cannot tell who can update reverse DNS may require a holdback. A lessee that needs route-origin support may discount if agreement status or account authority is unclear. A company selling space that still has old route-origin statements or provider-maintained entries must coordinate cleanup. These are technical tasks with commercial consequences.
The fourth discount is reputation. A block can route and still be commercially dirty. Mail blocklists, fraud signals, abuse complaints, geolocation mistakes, prior leasing history or suspicious traffic patterns can reduce value. Reputation damage may be temporary, but cleaning it requires evidence and time. An enterprise holder that leases without monitoring may convert idle capital into a contaminated asset. A buyer that inherits such history will demand protection.
The fifth discount is internal dependency. A seller may claim space is unused, but if internal scans, firewall rules, partner contracts or business-unit interviews show dependencies, the buyer will question timing. The seller may still close after renumbering. The price will reflect the work. If dependencies are unknown, the discount is larger because unknown risk is harder to insure. A company that can prove a range is clean has created value even before negotiation.
The sixth discount is ARIN process uncertainty. If the expected review path is clear, parties can plan. If the file may require account recovery, legacy regularization, successor evidence, officer acknowledgement, agreement coverage or inter-regional coordination, parties need time and contingencies. ARIN's legitimate review affects price because it determines when private agreement becomes public recognition. The issue is not whether review is proper. It is whether review is predictable enough to price.
Enterprise holders often underestimate these discounts because they compare their ranges to published price chatter. Address markets are less transparent than mature commodities. A quoted price assumes specific conditions. Block size, reputation, region, clean title, registry readiness, buyer profile and urgency all matter. A holder entering the market once in a generation may mistake an indicative price for realizable value. The cure is preparation. Clean evidence narrows discounts; wishful thinking does not.
Routing, reverse DNS and reputation convert paperwork into price
Technical evidence is not a replacement for corporate authority, but it is part of price. ARIN's record can identify the recognized holder and service state. BGP history can show who has originated the space. Reverse DNS can reveal whether operational naming matches present control. Routing-security data can support or complicate claims about authorized origin. Abuse history can show whether the block has been managed responsibly. Together these signals tell buyers and internal reviewers whether the address range is merely visible or truly ready.
Enterprises sometimes treat routing evidence as a network detail to be handled after the deal. That is a mistake. If a range is being sold, the buyer will want to know whether existing announcements must be withdrawn, whether upstream filters will change, whether route-origin statements need new authority, whether provider-maintained records exist, and whether old customer or partner routes linger. If a range is being leased, the lessor needs rules for how announcements are made, who can change them, how abuse is handled and how routes are withdrawn at termination. A vague routing plan creates settlement risk.
Reverse DNS deserves special attention because it is both mundane and visible. Mail systems, logging tools, security platforms, customer diagnostics and reputation systems often consume reverse-DNS signals. A legacy enterprise block may still have PTR naming tied to a predecessor, old division, outsourced provider or retired domain. That may not break traffic, but it can weaken commercial confidence. A buyer may see outdated naming as evidence of stale control. A lessee may need specific naming. A security team may struggle to map alerts. The ability to update reverse DNS quickly is therefore part of liquidity.
Routing-security support can be equally important, especially where counterparties expect modern origin assurance. A holder that cannot access or manage relevant services because account authority or agreement status is unclear may face a discount. A buyer wants a clean handover. A lessee wants confidence that its announcements can be authorized and later withdrawn. A lender may not study ROAs in detail, but it will care if customer revenue depends on routes that may be questioned. The service layer turns proof into operational assurance.
Reputation links the technical and the corporate. Address ranges carry memory in mail filters, fraud engines, threat-intelligence feeds, hosting platforms, geolocation vendors and upstream networks. A block used by a careless lessee may become harder to sell. A block that has sat dormant may have a cleaner reputation but less current routing evidence. A block with old abuse complaints may require remediation before monetization. Reputation is not formal title, but it affects realizable value.
ARIN's constructive role is to maintain service-specific clarity. If reverse-DNS authority is clean, say so through the normal service state. If routing-security access requires agreement coverage, make the path and consequence clear. If a transfer will require withdrawal or re-creation of related entries, make the expectation predictable. If a service is paused due to authority review, label the pause narrowly. Service ambiguity should not become a general cloud over the resource.
Enterprises should treat the service layer as part of diligence, not as aftercare. Before sale or lease, they should map all current announcements, reverse-DNS delegations, route-origin statements, routing-registry entries, upstream filters, provider contracts, customer allowlists and reputation issues. They should decide which must be preserved, changed, withdrawn or assigned. They should test access to the accounts and contacts needed to act. A clean legal file with a messy technical handover still produces discounts.
The deeper point is that IPv4 capital is not a number detached from the Internet. It is a recognized, routed and reputationally remembered position. The company's proof must satisfy legal, registry and operational reliance at the same time. That is why enterprise legacy holdings are so awkward. The old range may have become financially meaningful, but its value is still produced through many small technical signals that outsiders use to decide whether they can trust it.
The AFRINIC warning for quiet corporate records
AFRINIC is not the subject here, but it offers a useful warning. Public reporting about address theft and contested records in that region showed that dormant or weakly monitored address records can become vulnerable when registry certainty and corporate custody are weak. Old contacts, uncertain authority, internal process weaknesses and valuable IPv4 can combine into a costly recovery problem. Once a false or contested control state has been relied upon by downstream users, buyers, lessors or operators, correction is slow and expensive.
The ARIN region is institutionally different. Its procedures, published transfer categories, legacy materials, service practices and corporate environment are more mature. That difference matters. The caution is not that ARIN faces the same crisis. It is that the economics of dormant records do not respect institutional pride. Valuable public address space with stale authority is attractive wherever it sits. A non-network enterprise that ignores its records because traffic still flows may be leaving a scarce position exposed to confusion, capture or discount.
The AFRINIC lesson should be kept narrow. It does not justify treating every old holder as suspicious. It does not justify open-ended registry control over lawful commercial choices. It does not prove that leasing, transfers or reserve holdings are inherently risky. It proves that a ledger with scarce value needs strong authority controls, tamper-resistant history, notice, cure, review and preservation of last verified state. It also proves that correction after reliance accumulates is much harder than prevention.
For enterprise holders, the warning is practical. Do not wait until a broker, buyer or hostile claimant forces the question. Confirm that the company knows every range it holds or uses. Confirm that public holder names match current legal reality or have a documented succession explanation. Confirm that contacts reach durable role addresses and responsible people. Confirm that old provider access cannot quietly change records. Confirm that officer authority is current. Confirm that subsidiaries, vendors and business units are not relying on undocumented assumptions. Dormant is not the same as safe.
For ARIN, the warning is about balance. Weak verification invites fraud. Overbroad verification immobilizes legitimate holders and reduces supply. A registry that wants a healthy address economy must make false authority hard and legitimate movement predictable. That means preserving ledger facts, reducing verification cost where risk is low, separating record evidence from discretionary commercial judgment, aligning control with liability, and avoiding hidden capital controls over scarce productive inputs.
The phrase "capital control" may sound dramatic, but the economic mechanism is plain. If a holder can use a range only when a private coordination body approves broad matters beyond uniqueness, authority, fraud, dispute status and service continuity, the registry has become a gate over capital movement. Some gates are necessary. Fraud gates are necessary. Dispute gates are necessary. Sanctions and court restraints may be necessary. But a gate should name the risk it prevents. Otherwise it becomes a price that holders pay without a clear liability match.
The better reading of AFRINIC's history is therefore not fear but discipline. The ledger must be protected because value attracts manipulation. The holder must be respected because it bears operational and financial downside. The registry must be constrained because its decisions affect value beyond its own exposure. The enterprise must be prepared because stale custody turns a useful option into a fragile one. ARIN can learn from the warning without importing the crisis.
What ARIN can do without becoming a capital planner
ARIN's constructive role is strongest when it behaves like a reliable ledger and service coordinator, not like a planner of corporate address strategy. Enterprise legacy holders need the registry to tell the truth about recognized records, authority, service state, transfer paths and disputes. They do not need ARIN to decide whether a bank should lease, whether a retailer should sell, whether a manufacturer should reserve, or whether a conglomerate's internal option value is wise. Those choices belong to the holder and its counterparties.
The first improvement is stable and explainable record history. Enterprises with decades of mergers and name changes need a way to connect old records to current authority without restarting the entire historical debate each time. ARIN can support this by keeping clear organizational history, accepted successor evidence, validated contacts and prior determinations in a form that reduces repeated proof. A holder that has already proved a name change should not have to rediscover the same file for every later action unless new facts raise risk.
The second improvement is narrow proof requests. When ARIN asks for evidence, the request should identify the fact that remains uncertain. Is the issue current legal existence, signer authority, predecessor succession, asset inclusion, account recovery, dispute status, service eligibility or suspected compromise? Each asks for different evidence. Precision lowers cost for honest holders and improves the registry's own defensibility. It also prevents a legacy file from feeling like a general audit every time a company tries to clean data.
The third improvement is clear successor-evidence categories. Enterprise history is diverse. Public companies, private firms, banks, insurers, airlines, cooperatives, holding companies and foreign subsidiaries do not all produce the same documents. ARIN can publish useful categories of evidence and acceptable substitutes without exposing fraud triggers. For straightforward name changes, public filings may be enough. For mergers, survival documents and officer certificates may be enough. For asset acquisitions, relevant schedules, affidavits and operational continuity evidence may work together. The goal is not weaker proof. It is proof holders can understand before a deadline.
The fourth improvement is service-specific labeling. If a record is under authority review, say which actions are affected. If a transfer is paused, the pause should not automatically taint routine contact maintenance or existing reverse-DNS service unless the same risk applies. If routing-security access depends on agreement coverage, the status should be intelligible. If a dispute affects only a portion of a range or a specific action, label the scope. Broad uncertainty creates broad discounts. Narrow status lets counterparties price the real issue.
The fifth improvement is predictable support for reverse DNS and routing evidence. Enterprises need to know how these services will move during sale, lease, recovery or internal restructuring. A buyer wants to avoid operational debris. A seller wants to avoid continued responsibility after closing. A lessee wants assurance that authorization can be granted and withdrawn. ARIN can reduce friction by making handoff expectations, authority requirements and timing categories visible.
The sixth improvement is account-authority recovery that preserves continuity. Old enterprise records often have retired contacts, lost credentials and changed structures. Recovery should be secure, but it should not treat every honest repair as an emergency. ARIN should preserve the last verified operational state, require specific evidence for current authority, notify existing contacts where safe, restrict only risky changes while review proceeds, and give holders a clear path to cure. Recovery is a continuity service as much as a security control.
The seventh improvement is aggregate delay metrics. ARIN does not need to expose private files to report useful timing. It can publish how long different categories of legacy regularization, authority recovery, transfer review, reverse-DNS changes and routing-related service changes take, how many rounds of evidence are typical, which missing facts are common and how often files are abandoned. Such metrics help enterprises plan. They also show whether review is a measured control or an invisible tax.
Finally, ARIN should keep portability in view. Portability does not mean duplicate records or chaotic competition between registries. It means the value of a recognized address position should not depend more than necessary on discretionary institutional control. The ledger should preserve uniqueness, history and reliance. The holder should be able to move value through lawful, evidenced paths. The registry should reduce verification cost rather than create dependency rents. That is the difference between a trusted record system and a quiet capital bottleneck.
The enterprise holder's practical discipline
The constructive test ends inside the company. ARIN can make records clearer and review more predictable, but the enterprise holder must treat registry-facing proof as part of capital discipline. A board cannot value, reserve, lease or sell a historic IPv4 range responsibly if it does not know what it holds, who can act, who depends on it and what evidence supports its position.
The first step is a complete inventory. Identify every public IPv4 range held, announced, used, reserved or inherited by the corporate group. Include ranges held under predecessor names, subsidiaries, acquired businesses and historical provider arrangements. Compare public records, internal IP address management, firewall rules, BGP advertisements, reverse-DNS delegations, security tools, vendor diagrams, disaster-recovery plans and business-unit records. The inventory should distinguish current use, historical use, reserve use and unknown use.
The second step is a legal-entity map. For each range, identify the recognized holder, the original or historical holder where known, the current legal successor, the business unit using it, any subsidiary claiming rights, and any vendor with operational access. Preserve merger filings, name-change records, acquisition agreements, asset schedules, officer certificates, board approvals, outsourcing contracts and prior registry correspondence. If a document is missing, record the substitute evidence that supports continuity.
The third step is internal custody. Assign a named executive sponsor and a working owner for the address portfolio. Define who may approve routine technical updates, who may speak to ARIN, who may negotiate sale or lease terms, who may approve officer acknowledgements, who handles abuse notices, who maintains reverse DNS, who manages routing-security evidence and who updates the file after corporate changes. Do not let an old engineer's memory or a single login become the company's control model.
The fourth step is dependency classification. Place each range into categories: essential live use, recoverable live use, reserve, available after cleanup, available now, disputed or unknown. For live use, map applications, partner allowlists, suppliers, VPNs, mail systems, monitoring, certificates, industrial links, customer services, security tools and recovery plans. For reserve space, state why the reserve exists and when it will be reviewed. For unknown space, set a deadline for investigation.
The fifth step is technical evidence. Confirm current advertisements, route-origin support, routing-registry entries, reverse-DNS control, DNSSEC where relevant, provider filters, geolocation, blocklist status, abuse-contact routing and account access. Clean obsolete reverse-DNS names. Remove stale routing data where appropriate. Preserve evidence of current control. If the company plans to lease, create monitoring and termination procedures. If it plans to sell, prepare a handoff plan.
The sixth step is value and decision. Estimate hold, lease, sale, partial sale, subsidiary allocation and staged-renumbering options. Include renumbering cost, tax, legal cost, internal staff time, reputation risk, counterparty risk, lost optionality and ARIN review timing. Do not rely on a single per-address price. Value clean, restricted and burdened space separately. The board should see the choices, not just the headline value.
The seventh step is record regularization before urgency. Update public contacts, recover accounts, document successors and test authority before a deal, audit or incident forces action. If ARIN review is needed, approach it with a narrow evidence file tied to the specific correction. Keep copies of submissions, responses, approvals and service changes. Make the proof reusable for future transactions and audits.
The final discipline is cultural. Treat old IPv4 ranges neither as free money nor as untouchable relics. They are scarce corporate positions whose value depends on evidence, continuity and judgment. Some should become supply. Some should remain reserve. Some should be divided. Some should be cleaned before any decision. The address economy benefits when enterprise holders can act voluntarily and confidently. ARIN benefits when its records become more accurate. Networks benefit when scarce inputs move without fraud, hidden pressure or avoidable delay. The balance-sheet ghost becomes useful only when the company can prove it is real, controlled and ready for the choice management intends to make.