ARIN and the economics of the title-insurance analogy

Summary

• The title-insurance analogy is useful as an economics lens, not as a proposal for ARIN to sell insurance or adjudicate private ownership.
• Scarce IPv4 transfers now depend on chain-of-custody confidence: current registration, corporate succession, authority, dispute status and service eligibility all shape reliance value.
• Private warranties and indemnities allocate loss, but they cannot substitute for an auditable public registry ledger that makes old defects legible.
• ARIN's strongest role is a restrained ledger function: preserving history, naming exceptions, protecting finality, and keeping policy discretion separate from commercial judgment.

A clean current record is not the same as insured confidence

The negotiation has already moved past the theatrical phase. The acquisition team has a data room, a purchase agreement in draft, a lender asking for collateral support, and a schedule of IPv4 blocks that are supposed to come with the business. Engineers say the addresses matter because customer migration, fraud controls, carrier-grade translation and launch timing all depend on them. Finance sees scarcity value. Counsel sees ARIN registration records, older Whois references, routing history, merger papers, officer certificates, transfer forms, board approvals, old seller names and a legal opinion that the seller may request the transfer.

The question in the room is not whether the current record looks clean. It is whether the record will stay clean after money has moved, debt has been drawn, customers have been migrated and the people who remember the old corporate history have left. A creditor asks the same question more sharply. What if a predecessor received the addresses under a name that was never the legal name? What if the addresses followed one business line while a later asset sale excluded that line? What if a reorganization missed a subsidiary? What if an old point of contact had access but not authority? What if a former affiliate, bankruptcy trustee, secured creditor, regulator or successor later claims that the transfer should not have been recognized?

That is where the analogy to title insurance becomes useful. It is not useful because IPv4 addresses are land. They are not. It is not useful because ARIN should sell insurance, guarantee commercial bargains or act as a property court. It should not. The analogy is useful because it separates three ideas that are often blurred: the existence of a public record, the quality of the historical chain behind that record, and the residual risk that an old defect will survive diligence and attack future reliance. In land markets, title insurance turns a messy historical record into a financeable transaction through search, standardized exceptions, public recording discipline, lender reliance, private underwriting and a promise to defend or compensate against specified hidden defects. The lesson for IPv4 is narrower but important: a scarce-resource market needs records that make past claims traceable, current authority legible and exceptions visible enough for residual risk to be priced.

The current registration record is the beginning of diligence, not the end. A line in RDAP or Whois can say which organization is presently recognized for a block. It can show contacts, names, handles and dates. It can orient a buyer, an abuse desk, an upstream provider or a researcher. But a current display line cannot by itself answer why the named organization is the right organization, whether earlier names were correctly mapped, whether the block was included or excluded in a past transaction, whether a dissolved predecessor had successors, or whether ARIN's historical file contains ambiguity that has never been tested because no one tried to sell or finance the block before.

That distinction matters more in a post-exhaustion market than it did when addresses were mostly obtained for use rather than acquired for consideration. Before scarcity, a record error was often an operating nuisance. It could delay a contact update, confuse an abuse complaint, or complicate reverse DNS. After scarcity, the same error can affect deal economics. A stale contact becomes a signing-authority problem. An old trade name becomes a corporate succession problem. A forgotten allocation to a predecessor becomes a balance-sheet question. An inaccurate registration date becomes evidence in a dispute over priority or provenance. A current record that works for ordinary network operation may be too thin for a lender asked to advance money against future control.

The title-insurance analogy clarifies why. A property buyer is not satisfied only by seeing that a seller currently appears in a local record. The buyer wants to know whether the chain leading to that record contains hidden mortgages, forged deeds, undisclosed heirs, boundary errors, defective acknowledgments, missing releases or recording mistakes. Many such defects do not matter every day. They matter when money changes hands and when future reliance must be defended against a third party. IPv4 has its own defect vocabulary: unauthorized transfer requests, stale point-of-contact control, missing merger documents, mismatched legal names, unresolved bankruptcy questions, disputed legacy status, policy restrictions, inaccurate reassignment data, inherited route-security artifacts, and reputation history that follows the block longer than the seller expects.

The current record can be correct and still not be enough. It may correctly describe the organization ARIN recognizes now, while the market still lacks confidence in how that organization became the recognized holder. It may show an allocation that has been operationally stable for years, while the legal entity behind the original allocation has been merged, renamed, liquidated, spun out, or folded into a holding structure. It may show contacts who can maintain records, while the corporate officer who must make a transfer representation needs a different evidentiary basis. It may show a block that routes without incident, while a past abuse or geolocation history creates commercial residue. In each case, the record is useful. It is not equivalent to insured confidence.

The economic difference is reliance value. A record has reliance value when parties outside the registrant can use it in decisions that are costly to reverse. A lender relies when it gives credit. A buyer relies when it pays and migrates customers. A board relies when it approves an acquisition thesis. An auditor relies when it evaluates whether an intangible resource has supportable value. A network operator relies when it configures routing and reverse DNS. The more valuable IPv4 becomes, the more reliance shifts from informal operational comfort to formal institutional comfort. That shift demands a ledger that is more than a gate through which requests pass.

IPv4 title is not property title, but transactions behave title-like

The analogy must be kept disciplined. Internet number resources are coordination identifiers. Their public value depends on uniqueness, routability, registry recognition and widespread operational acceptance. ARIN's Number Resource Policy Manual states the registration principle in functional terms: a public registry documenting allocations, reallocations, assignments and reassignments is necessary to ensure uniqueness, provide operational and security contacts, support transparency for efficient utilization, and assist allocation studies. The same manual states, in the IPv6 section, that allocation or assignment does not guarantee routing by any particular network operator. Those statements describe a coordination system, not a land-title office.

Nor does ARIN's role become ordinary property administration simply because IPv4 scarcity created market value. The market can price a block, but price does not settle the legal character of the underlying right. A buyer may speak colloquially of buying addresses. A lawyer may draft an asset purchase schedule. A bank may ask whether the rights can support collateral value. An engineer may care only whether the prefix can be announced and accepted. ARIN may focus on registration, agreement status, policy requirements and authorized change. The title-insurance analogy is useful precisely because it does not require these vocabularies to collapse into one another.

What makes IPv4 title-like is not metaphysics. It is transaction behavior. A scarce, uniquely registered resource moves through corporate transactions. It has a history. It can be included in or excluded from asset schedules. It can be claimed by successors. It can be impaired by defects in authorization. It can be affected by court orders or insolvency proceedings. It can be represented, warranted, indemnified, valued, discounted and financed. It can survive several corporate generations and then become economically decisive when a business is sold. It can be routed by one party while another party claims that the registration should belong elsewhere. Those are title-like facts even if the legal object is not a parcel of land.

The practical question is therefore not whether ARIN should declare an ownership theory. The practical question is whether the ARIN registry can support the level of chain-of-custody confidence that the market now needs. In a world of abundant IPv4, an organization with an old allocation had limited reason to reconstruct every corporate event since the 1990s. In a world of scarcity, the same organization may need to prove that the block survived mergers, divisions, name changes, bankruptcies, divestitures and record errors. A buyer does not have to win an abstract debate about property to need that proof. It only has to face a lender, a regulator, a board, a buyer in the next sale, or a claimant with enough documentation to create doubt.

The word "title" should therefore be understood as shorthand for control confidence, not as a conclusion about legal ownership. It asks whether the party presented as the current holder can defend the path by which it became the holder and can request changes without relying on mere possession of stale credentials. It asks whether a transfer can survive later dispute. It asks whether an old defect remains hidden because no transaction forced it into daylight. It asks whether the registry's evidence standard is predictable enough that legitimate successors can prove their case without granting ARIN broad discretion over commercial destiny.

That is why the title-insurance analogy is more useful than the simpler phrase "due diligence." Due diligence describes what a buyer does. Title confidence describes what a market produces when private diligence is supported by a reliable public ledger. A buyer can spend heavily on diligence and still face uncertainty if the registry history is incomplete, if official state definitions are unclear, if old records cannot be accessed, or if disputes are handled opaquely. Conversely, a strong ledger can lower diligence cost by giving parties a common starting point. It does not eliminate private review. It makes private review less dependent on rumor, bargaining power and memory.

The registry ledger as chain-of-custody infrastructure

A registry is sometimes imagined as a permission gate: a party submits a request, staff check requirements, and the record is updated or not. That view is incomplete. In a scarce-resource market, the registry is also chain-of-custody infrastructure. It preserves the public uniqueness of the resource, records the recognized holder, connects the holder to contacts, provides historical context, supports transfer review, and gives outsiders a place to begin their inquiry. The ledger is not valuable because it announces institutional power. It is valuable because it reduces the cost of verifying who may speak for a resource.

ARIN's public materials already reveal this function. Its transfer guidance for mergers, acquisitions and reorganizations says that the new organization must provide evidence that it acquired the assets using the resources. The examples include an asset purchase agreement and bill of sale, a finalized merger or amalgamation agreement filed with government authorities, a finalized court order, public filings documenting the transfer of assets, or authenticated name-change documents. If multiple transactions connect old and new organizations, documentation is required for each transaction. Financial and sensitive information may be redacted; the issue is not the price but the chain.

For specified-recipient transfers within the ARIN region, ARIN's guidance says the source organization must be the current registered holder, must not be involved in a dispute as to the status of the resources, and must provide a signed and notarized officer acknowledgement letter. Both sides submit separate ticketed requests, which ARIN staff link after review. ARIN says it respects each organization's privacy and that organizations should coordinate directly with each other to monitor progress. Upon approval, fees and a Registration Services Agreement may still be needed before completion. Those mechanics are usually discussed as process. Economically, they are evidence design: registered-holder status, dispute status, officer authority, privacy boundaries, and completion conditions are the grammar of reliance.

Historical access matters as well. ARIN's WhoWas service provides authorized users access to historical registration information for a given IP address or ASN, including the public history of a resource, associated organizations and points of contact. Access is not a mass-query public feed; it requires an ARIN Online account, a request and staff approval. That limitation may be reasonable for privacy and misuse reasons. But the existence of the service demonstrates a market fact: current records are not enough for many legitimate inquiries. Historical registration data is part of the diligence infrastructure.

The chain-of-custody problem also reaches beyond direct transfers. Legacy resources may sit outside a current agreement while still depending on ARIN for unique registration, record maintenance, reverse DNS and DNSSEC. ARIN's legacy-resource page, as of July 5, 2026, states that legacy holders not under an ARIN agreement can maintain unique registration in Whois/RDAP, update public data, manage reverse DNS delegations, maintain registry records through ARIN Online and access DNSSEC, but cannot access ARIN's RPKI or IRR services without being under an agreement. That service boundary is not merely administrative. It affects what a buyer, lender or operator can rely on after closing. The ledger, its services and its contract perimeter are parts of the same confidence system.

The strongest ledger is not the most discretionary ledger. It is the most auditable one. It should allow a legitimate holder to explain how the current state was reached, allow ARIN to reject forged or unsupported claims, allow a buyer to know where uncertainty remains, and allow future reviewers to distinguish an official registration state from a private assertion. A gatekeeper asks whether it should allow the next step. A ledger also asks whether the reason for that step will remain intelligible in ten years. Scarce IPv4 needs the latter discipline.

The defects hidden behind a neat registration line

The most dangerous title defects are not always dramatic. Many are ordinary corporate facts that become dangerous only because time has passed. A company changes its name. A division becomes a subsidiary. A university project becomes a separate foundation. A government contractor sells a business line but keeps some network assets. A telecom group merges operating companies while leaving old network records under former names. A bankrupt estate sells assets in several lots. A startup acquired for its customers never lists the associated address space separately. A predecessor used a trade name or abbreviation rather than a legal name. For years, nothing breaks. Then a transfer request or financing diligence asks for the chain, and the chain has gaps.

Authorization gaps are the first category. A person may have access to an ARIN account, control of an old email address, or operational knowledge of a network, but not authority to dispose of the resource. The distinction is fundamental. Contact control is not corporate authority. A registered point of contact may be able to update information, but a sale or transfer requires a defensible link to the recognized organization and an officer-level representation where ARIN policy or practice demands it. If the market treats account access as entitlement, stale credentials become a fraud vector.

Stale contacts are the second category. A resource that has been stable for years may have contacts who are retired, deceased, outsourced, unresponsive, or attached to a predecessor domain. Annual validation helps, but validation does not reconstruct corporate history. A contact can be reachable yet lack authority. A contact can be authorized for operations but unaware of asset history. A buyer that assumes contact cleanliness equals title cleanliness will underprice risk.

Historical allocation ambiguity is the third category. Early Internet allocations were often made in a different administrative culture. Some records were created when formal agreements were less common and organizational structures were simpler. ARIN's legacy-resource history acknowledges that early IP address space was allocated liberally to organizations that fulfilled simple request requirements without formal legal agreement, before administration became distributed through the RIR system. That history is not a scandal. It is the origin of today's title-confidence problem. Records created for technical coordination now support assets with strategic value.

Corporate succession is the fourth category. This is where the title-insurance analogy is most direct. A land-title search follows deeds, mergers, probate records, releases and liens. An IPv4 chain follows allocation records, organization names, merger documents, asset purchase agreements, court orders, bills of sale, public filings, name-change certificates and sometimes evidence that a network or customer base moved with the resource. If one link is missing, the market must decide whether the gap is curable, whether the seller bears the risk, whether ARIN will accept alternative evidence, whether the buyer should demand a discount, or whether the resource should be excluded.

Fraud is the fifth category. Scarce resources invite impersonation, forged documents, false officer claims, compromised accounts and attempts to exploit defunct organizations. Fraud risk is not only a private loss. It attacks the registry's public uniqueness function. If a forged transfer is recognized, later correction may be costly for innocent parties who built reliance on the record. If ARIN reacts by making every transfer painfully uncertain, legitimate market activity becomes expensive. The ledger must therefore be hard to defraud but not impossible for honest successors to use.

Policy reinterpretation is the sixth category. A transfer may look clean under one understanding of need, source eligibility, inter-RIR compatibility, legacy status or agreement coverage, only to become harder to defend if policy language or staff interpretation changes later. The danger is not that policies never change. They must. The danger is that market participants cannot tell which parts of the record are stable reliance points and which are conditional on future institutional discretion. A lender dislikes a resource whose transferability depends on a rule that can be reinterpreted without a predictable reliance treatment.

Disputes and court orders form the seventh category. ARIN's transfer guidance treats disputed resource status as a bar to specified-recipient source eligibility. That is sensible: a registry should not let a disputed claimant create irreversible change merely by moving quickly. But the economic question is what happens around the dispute. Is the dispute visible enough for buyers to know? Is the running network preserved where possible? Are competing claims isolated from unrelated resources? Does the registry avoid turning uncertainty into punishment? Does it preserve the evidentiary trail so that a later resolution can be implemented without destroying reliance?

Routing and reputation residues are the eighth category. They are not title defects in the narrow legal sense, but they affect title confidence because they shape the value of the control being acquired. Old ROAs, IRR objects, reverse-DNS delegations, abuse contacts, geolocation assumptions, spam history, proxy use, botnet associations, customer assignments and filtering memories can survive the registry update. ARIN's transfer guidance tells source organizations to edit or delete transferring prefixes from source ROAs, update or remove IRR objects, coordinate reverse DNS and ensure the recipient understands its own responsibilities. That checklist is operational, but it has an economic meaning: registry control and usable control are connected but not identical.

Each defect type shows why a neat current record is insufficient. The market needs to know not only what the record says, but what defects have been searched for, what exceptions remain, who bears them, and how future disputes will be handled. That is the title-insurance question translated into number-resource economics.

Why private warranties cannot replace public ledger confidence

Purchase agreements can do much of the work. A seller can represent that it is the current registered holder, that it has authority, that no undisclosed disputes exist, that no prior transfer or encumbrance conflicts with the sale, that fees are current, that contacts are accurate, that it has provided true documents, that it will cooperate with ARIN, and that it has disclosed known routing, reverse-DNS or reputation problems. The buyer can demand indemnities if those statements fail. A lender can require covenants, collateral descriptions and reporting duties. Counsel can draft conditions around registry completion. These instruments matter. They allocate loss.

But private warranties have four limits. First, they are only as good as the warrantor's solvency and survival. A seller that dissolves, enters bankruptcy, distributes sale proceeds, or lacks meaningful assets may not be a reliable source of recovery. Second, they bind parties to the contract, not the whole world. A third-party claimant, a regulator, a court or a registry may not be defeated merely because the seller promised the buyer that the chain was clean. Third, warranties often discover defects after reliance has already occurred. Money can be recovered later, but customers may have been migrated and network architecture changed. Fourth, warranties cannot by themselves update the public record. They can say what should happen. They cannot make the Internet recognize it.

This is why land markets developed both public recording and private insurance. The buyer's contract with the seller was not enough for lenders. Lenders needed confidence in the public record and a risk carrier for defects that escaped search. The lesson for IPv4 is not that ARIN should underwrite losses. The lesson is that private contracting cannot produce full reliance when the decisive public state belongs to a registry. A seller's indemnity may compensate a buyer if ARIN refuses a transfer for a seller-side defect. It does not supply the block. It does not restore market timing. It does not erase the operational disruption caused by uncertainty.

Private diligence also suffers from unequal access. A repeat buyer, large cloud platform, experienced counsel team, or specialist intermediary may know how to read ARIN history, request relevant records, identify old corporate gaps and structure conditions. A smaller operator may not. If the public ledger is thin or hard to interpret, the market rewards the parties with private memory and punishes those who rely on surface records. That is not merely a fairness issue. It raises transaction costs and discourages legitimate transfers from holders who fear they cannot navigate the evidence burden.

There is also a collective-action problem. Each buyer can demand documents in its own deal, but no single buyer has the incentive to improve the registry's historical clarity for everyone. Each seller can clean its file before sale, but many will wait until a transaction forces the issue. Each lender can apply a haircut, but haircuts do not repair the record. The public ledger is the shared asset. If it is stronger, private warranties become narrower and cheaper. If it is weaker, contracts become longer, indemnities broader, discounts larger and disputes more likely.

The best institutional design therefore treats warranties as complements to the ledger, not substitutes. ARIN should verify what belongs to registry recognition: current holder, authority evidence, policy eligibility, dispute status, agreement requirements and record completion. Private parties should allocate commercial risk: price, tax treatment, post-closing cooperation, seller knowledge, indemnity caps, technical cleanup and remedies for breach. When the boundary is clear, contracts can rely on the registry without asking ARIN to insure them. When the boundary is blurred, every contract must reinvent public confidence privately.

What lenders, boards and auditors need from a registry record

The credit committee's question is not philosophical. It asks whether the IPv4 block can support cash flow, continuity and recoverable value under stress. If the borrower defaults, can the lender understand who controls the resource? Can the block be transferred to a qualified buyer? Would a receiver or bankruptcy estate face a registration dispute? Are the resources under an agreement that affects service access? Are points of contact current? Are fees in good standing? Is there any evidence that the resource is restricted, reserved, disputed or tied to a line of business that was not transferred? If the lender cannot answer those questions, the collateral value falls.

A board approving an acquisition has a similar but broader concern. It needs to know whether the deal thesis depends on IPv4 continuity, whether the seller's authority file has been tested, whether customer contracts assume stable addressing, whether address transfer is a closing condition or a post-closing covenant, whether technical cleanup is scheduled, and whether a later dispute could impair the acquired business. Directors do not need to become registry specialists. They do need a record system whose outputs can be translated into risk categories: current recognition, historical chain, known exceptions, service dependencies, transfer state and residual uncertainty.

Auditors and valuation advisers ask a different version of the same question. If management assigns value to IPv4 resources, what evidence supports control? If a company treats address space as part of an acquisition premium, can the record be reconciled with the purchase agreement? If a resource is impaired by a dispute, how is that reflected? If the company relies on legacy resources outside a current agreement, what service limitations matter? If the addresses can be transferred only under certain policies, how does that affect recoverable value? These are not requests for ARIN to certify accounting value. They are requests for a ledger that supplies reliable inputs.

The more institutional the audience, the less useful informal assurance becomes. An engineer saying that the block has routed for years is relevant but not enough. A broker saying that similar transfers have closed is relevant but not enough. A lawyer saying that the seller appears authorized is relevant but not enough if the registry history contains untested gaps. A current RDAP line is relevant but not enough if a lender worries about old defects. Institutional reliance requires triangulation: public record, historical chain, authority documents, operational evidence and contractual allocation.

This is where ARIN's role becomes more important even as it remains limited. ARIN should not opine on loan-to-value ratios, purchase price fairness or the commercial wisdom of holding IPv4. But it is the only institution that can make the current registry state authoritative for ARIN-administered resources. It is the only institution that can say whether it recognizes a transfer under its policy. It is the keeper of historical registration data. It controls the service boundary for reverse DNS, RPKI, IRR and related registry services. That makes its ledger a public input into private finance.

Finance does not require perfection. It requires known exceptions. A lender can price a resource with an old corporate gap if the gap is disclosed, bounded and allocated. A buyer can accept reputation cleanup if the cost is known. A board can approve a transaction with a pending registry step if completion is a clear condition. An auditor can evaluate a resource whose agreement status is documented. What finance cannot easily absorb is unbounded historical uncertainty: the possibility that any old defect, unknown to all current participants, might later emerge and undermine reliance without a clear process for resolution.

Title insurance in land markets exists because perfect historical certainty is impossible. The economic lesson for IPv4 is similar. ARIN need not guarantee the past. It should make the past searchable, exceptions legible and present recognition defensible. The market can then decide how much residual risk to bear.

The lender's hidden question: will the record survive dispute?

The real test of a registry record is not how it looks on a quiet day. It is how it behaves under dispute. A clean-looking record has limited value if it collapses as soon as a claimant appears. A rigid record has limited value if it refuses to correct genuine defects. A discretionary record has limited value if participants cannot predict what evidence matters. The lender's hidden question is therefore: if something goes wrong, will the ledger remain stable enough for the running network and fair enough for the parties?

Dispute survival has several dimensions. The first is notice. If ARIN is aware of a resource-status dispute, potential transferees need a way to avoid treating the block as ordinary clean supply. That does not require publication of every private allegation. It does require a mechanism by which known disputes prevent misleading transfers and, where appropriate, make uncertainty visible to those with a legitimate need to know.

The second dimension is isolation. A dispute over one block should not automatically poison a whole organization if the evidence is specific. A dispute over a seller's authority should not necessarily interrupt unrelated operational services. A disputed transfer request should not become a reason to disrupt customers who had no role in the dispute. Scarce-resource value can be destroyed by overbroad uncertainty before any formal decision occurs. A mature ledger contains disputes; it does not amplify them.

The third dimension is continuity. Number resources are not inactive files. They support running services, customer networks, security controls and reverse DNS. When a title-like defect appears, the registry must avoid two opposite errors: permitting irreversible changes by a weak claimant, and using uncertainty to break stable operation unnecessarily. Running network reality is not a moral endorsement of the current holder. It is evidence that continuity has public value while the authority question is resolved.

The fourth dimension is evidentiary order. The registry should be able to state what kinds of evidence matter for different defects: court orders, corporate filings, merger documents, asset purchase schedules, officer acknowledgements, name-change records, historical registration data, proof of operational succession, and records showing that a disputed asset was included or excluded. That order should be predictable enough that parties can prepare before conflict becomes urgent.

The fifth dimension is finality. At some point, a transfer recognized by ARIN must become a reliance event, subject to correction only under defined conditions. No market can operate if every transfer is forever provisional. Yet no registry can maintain legitimacy if a transfer obtained by fraud becomes uncorrectable merely because time has passed. Title systems handle this tension imperfectly through statutes, recording rules, notice principles, insurance and court processes. ARIN's version must be narrower, but it faces the same economic tension: finality encourages reliance; correction protects integrity.

For lenders, the question is not whether all disputes can be eliminated. They cannot. It is whether the dispute process is legible enough that credit risk can be modeled. A block with a known exception and a defined cure path may still be financeable. A block whose risk depends on unpredictable registry discretion will receive a deeper discount or be excluded from collateral value. That is how registry confidence enters cost of capital without ARIN setting a single price.

Title insurance is an analogy, not a product recommendation

It would be a mistake to read this argument as a call for ARIN to become a title insurer. An insurer prices risk, collects premiums, defines covered losses, maintains reserves, defends claims and pays under a policy. ARIN is a registry. Its legitimacy comes from maintaining unique, accurate, authorized and operationally useful records under community-developed policy and applicable agreements. Turning it into an insurer would blur functions, create conflicts, invite moral hazard and require capital, regulation and claims expertise that are outside the registry's proper role.

The analogy is valuable because it exposes the institutional ingredients of confidence. First, title insurance depends on search. The underwriter investigates the record before accepting risk. For IPv4, the equivalent is historical registration review, authority evidence, dispute checks and operational-state review. Second, title insurance depends on exceptions. The policy says what it does not cover. For IPv4, the equivalent is making known uncertainties visible: unresolved corporate gaps, agreement boundaries, ongoing disputes, technical cleanup not yet complete, reputation risk not certified, and policy conditions that remain open.

Third, title insurance depends on public recording. The insurer can underwrite because there is a public record to search. For IPv4, ARIN's ledger is the record on which private reliance depends. Fourth, title insurance depends on claim defense. The insurer does not merely pay; it may defend title against a covered claim. For IPv4, ARIN should not defend private buyers as an insurer would, but it should defend the integrity of the registry by preserving evidence, resisting forged claims, recognizing valid court orders and applying rules consistently.

Fifth, title insurance depends on lender reliance. Mortgage lenders accept real estate collateral in part because title risk is standardized. IPv4 lenders need a different but related standardization: a way to classify registry risks so that financing does not depend entirely on bespoke legal memos. Sixth, title insurance depends on institutional modesty. A land recorder records; a court adjudicates; an insurer underwrites; a lender lends; a buyer buys. The system fails when one institution pretends to do all functions. IPv4 markets need the same separation.

The product recommendation would be wrong, but the economics are right. A market with valuable, scarce, historically complicated registered resources needs more than a current display. It needs a confidence architecture. Private insurers may or may not ever build products around number-resource defects; that is not the central question. The central question is whether the public registry is strong enough that any private risk allocation, whether insurance, indemnity, escrow holdback or lender haircut, can rely on a coherent chain of custody.

Using the analogy also guards against an opposite error: pretending that because IPv4 is not land, title-like risk does not exist. Markets do not wait for perfect legal categories. They create practical categories around risk. If a defect can impair transferability, financing, continuity or resale, it is economically title-like. The registry can acknowledge that fact without declaring a property theory. Indeed, acknowledging it may help ARIN keep its role narrow. The more clearly it treats chain-of-custody confidence as a registry function, the less pressure there is to expand into price regulation, market planning or broad commercial judgment.

Due diligence has become underwriting of historical uncertainty

In a mature IPv4 transaction, diligence is no longer a checklist performed after price agreement. It is underwriting of historical uncertainty. The buyer asks whether the seller can prove current holder status. The seller asks whether the buyer can satisfy recipient requirements. Counsel asks whether the chain of corporate events is complete. The finance team asks whether delay affects funding. The technical team asks whether route-security and DNS artifacts can move. The compliance team asks whether counterparties and funds flow pass review. The future buyer, not yet known, hovers in the background: will this file be good enough to sell again?

The underwriting mindset changes incentives. A seller with clean records can command more confidence. A seller with gaps may still sell, but it must accept conditions, discounts, holdbacks or extra documentation. A buyer that understands title risk can avoid overpaying for a block whose apparent scarcity hides transferability problems. A lender can distinguish between a resource that is valuable to the borrower while operated by the borrower and a resource that would be liquid under default. A board can distinguish between a strategic network asset and a registration headache.

This is not a plea for paperwork for its own sake. It is an argument that documentation is part of the asset. The same /20 can have different economic value depending on whether the chain is clear, whether the organization record is current, whether legacy status is understood, whether there are old claims, whether RPKI and IRR service access is available where needed, whether reverse DNS can move, and whether the seller's officer can make representations without relying on institutional memory. Scarcity gives the addresses value; evidence preserves it.

The title-insurance analogy also explains why defects should be found early. In land transactions, a title search performed late can derail closing after the parties have spent money and lost alternatives. In IPv4 transactions, late discovery of a missing merger document, a non-current registrant, a dispute, a reserved-pool restriction or a policy mismatch can have the same effect. The market response is not only delay. It is distrust. Buyers assume sellers are hiding risk. Sellers assume buyers are using diligence to renegotiate. Lenders demand larger cushions. The resource becomes less liquid.

Early underwriting should not mean premature disclosure of every confidential commercial term. ARIN's own transfer guidance permits redaction of monetary and sensitive information in merger or acquisition contracts, and says ARIN is not concerned with associated costs. That boundary is important. Title confidence does not require the registry to know the purchase price. It requires enough evidence to show that the relevant assets or organization moved, that the source is recognized, that the request is authorized, and that policy conditions are met. Commercial confidentiality and chain-of-custody evidence can coexist.

The harder question is who pays for historical cleanup. Sometimes the seller should, because the defect lies in its own corporate past. Sometimes the buyer should, because it is demanding a level of financeable certainty beyond ordinary operational use. Sometimes costs should be shared because a transfer creates value for both sides. The registry should not decide that bargain. It should make the evidence requirement clear enough that the parties can price it.

Settlement is only one node in the title-confidence chain

Settlement matters, but it is not the center of this analysis. A funds custodian can hold money until ARIN completes a transfer. Conditions can define what happens if the registry refuses, delays or asks for more evidence. Holdbacks can cover technical cleanup. Those tools are useful. They reduce the risk that one side performs before the other. But settlement mechanics do not create title confidence; they depend on it.

The deeper question is what the settlement condition is built upon. If the source holder's authority is weak, escrow only pauses the loss; it does not fix the chain. If the seller's warranties are broad but the historical file is thin, the buyer still faces uncertainty about registry recognition and future dispute. If ARIN completes the transfer but old route-security artifacts, reverse DNS or reputation problems remain, the buyer has a different kind of residual risk. If a later claimant attacks the prior transfer, the fact that funds were released at closing does not by itself defend the current holder.

This is why title confidence must be assessed before settlement terms harden. The parties should know whether they are closing a routine transfer by a current holder, curing a historical corporate succession, moving resources as part of a merger or reorganization, handling inter-RIR compatibility, or accepting a known exception. The settlement design follows the title file. Treating every transaction as though it only needs a payment condition misreads the asset.

The registry ledger gives settlement its anchor. The public event is ARIN's recognition of the transfer in its records. But the value of that event depends on the evidentiary foundation behind it. A registry update that is well supported becomes reliance. A registry update that later appears unsupported becomes a dispute seed. The market should therefore care not only that the record changes, but why the record could justifiably change.

Brokers are dependent users of title confidence, not the main story

Brokers and specialist advisers appear in many IPv4 transactions because search is costly, supply is fragmented and evidence requirements are unfamiliar. They can help locate counterparties, identify likely documentation problems, explain transfer categories and coordinate expectations. In title-confidence terms, they are dependent users of the ledger. Their commercial value rises when they can help parties understand where a chain may break.

But the title-insurance analogy warns against letting private intermediaries become substitute recordkeepers. A broker may know that a block has been offered before, that a seller has weak documents, that a buyer failed a prior diligence review, or that a reputation problem caused a discount. That private memory can be useful in a transaction. It is not a public chain of custody. A future buyer should not need to know which intermediary handled a past conversation in order to understand who the recognized holder is and what known exceptions attach to the record.

This is why brokers are not the center of this article. The broker is one participant in a larger reliance system. If the public ledger is strong, brokers compete on service, search, judgment and coordination. If the public ledger is weak, brokers can sell privileged interpretation of uncertainty. The first is a market service. The second is quasi-gatekeeping. Title confidence should be produced by the interaction of public records and private diligence, not by private control of market memory.

The same point applies to lawyers, technical consultants and lenders. Each has expertise. None should become the hidden registry. The public ledger must remain the reference point because Internet number resources are coordination identifiers. Private advisers can help parties understand and allocate risk; they should not become the source of recognized control.

Public uniqueness coordination requires more than gatekeeping

The ARIN region has a relatively mature transfer system. It has documented transfer categories, a current NRPM, public guidance, officer acknowledgement requirements, transfer statistics, historical data services and a visible legacy-resource framework. These are strengths. The institutional risk is not obvious disorder. It is the subtler temptation to treat the ability to approve or deny requests as the essence of registry legitimacy. In a scarce market, that is too thin.

Public uniqueness coordination is the registry's core function. There must be one authoritative answer to who is recognized for a resource within the relevant registry system. That answer helps prevent duplicate claims, supports operational contacts, enables reverse DNS, underpins routing-security services and gives the rest of the Internet a reference. But uniqueness is not preserved only at the moment of approval. It is preserved through historical traceability, consistent evidence standards, dispute handling, service continuity and restraint in policy interpretation.

A gatekeeper can stop bad transfers. A ledger can also make good transfers durable. A gatekeeper can ask whether a request meets today's form. A ledger asks whether the record will remain intelligible after three more corporate transactions. A gatekeeper can demand documents. A ledger can preserve why those documents mattered. A gatekeeper can refuse a disputed source. A ledger can isolate the dispute, preserve stable operation and show future reviewers how the issue was resolved. The distinction is not rhetorical. It determines whether the market treats ARIN's record as a durable reliance asset or merely as an administrative hurdle.

The phrase "mandate laundering" is useful in public analysis when it describes a general institutional pattern: a narrow coordination mandate is expanded through broad language until commercial discretion appears to be technical necessity. A registry may need to protect uniqueness, accuracy, authorized change and operational stability. Those needs should not become a license to judge every business model, every valuation, every buyer preference or every private bargain. The more valuable IPv4 becomes, the more carefully ARIN should separate ledger protection from gatekeeping over the asset's economic uses.

That separation is not anti-registry. It is the registry's best defense. If ARIN can show that it validates authority without becoming a property court, preserves history without guaranteeing all private risk, supports transfers without planning the market, and handles disputes without destabilizing running networks, its legitimacy improves. If it uses scarcity to enlarge discretion, the market will price that discretion as a risk.

Running networks are evidence, not the whole answer

One of the hardest title-confidence questions is how to treat operational reality. A block may have been routed by the same organization for many years. Customers may depend on it. Abuse contacts may work. Reverse DNS may be stable. That running-code reality matters. It shows reliance, continuity and practical control. It may support a claim that a resource followed a business even if old documents are imperfect. It may justify caution before disrupting service.

But operation is not the whole answer. A hijacker can route. A former affiliate can continue using space after a divestiture. A contractor can operate a network for a client without owning the relevant rights. A dissolved entity's former staff can maintain records without corporate authority. A bankrupt estate can leave technical control in place while legal rights are contested. If the registry treated routing alone as title, it would reward possession over authority. If it ignored routing entirely, it would risk harming innocent customers and discounting real-world reliance.

The better approach is to treat running operation as one form of evidence within a broader chain. It can support continuity. It can help identify which assets used the resources. It can show whether a claimed successor actually inherited the network. It can reveal whether a transfer would disrupt customers. But it must be tested against documents, corporate authority, registry history and dispute status. The title-insurance analogy again helps: possession of land may matter, but the record and chain still matter; visible use may support reliance, but it does not erase defects.

This is especially important for old allocations. Early records may not contain modern legal precision. A resource may have supported a business through several transformations. The equitable answer may not always be visible from a single document. ARIN should be able to consider practical evidence without turning practical evidence into discretionary favoritism. That requires transparent categories: operational continuity, documented succession, historical record, current holder status, authority to request change, known claims and policy eligibility.

For buyers and lenders, running operation is reassuring only when it aligns with the registry file. A block that has routed quietly but has uncertain holder history may be useful to the current operator and still weak as transferable value. A block with a clean chain but known routing residue may be transferable and still costly to integrate. The market needs both views.

How ARIN can improve auditability without becoming a property court

The title-insurance analogy points toward practical improvements in auditability, not a wholesale change in ARIN's role. The first improvement is clearer state language. ARIN can distinguish current registration, transfer-request submission, source authority review, recipient qualification, known dispute, approval, completion, agreement coverage, and post-transfer service status. Some of this language already exists in public guidance, but a more standardized vocabulary would reduce confusion in contracts, board memos and lender files.

The second improvement is better historical extracts for legitimate diligence. WhoWas already provides historical registration information to authorized users. The market value of that service will grow as older blocks move through finance and acquisition diligence. ARIN can preserve privacy and misuse controls while making the output easier to interpret: what changed, when, which organizations and contacts appeared, what public history exists, and what the report does not prove. The goal is not high-volume curiosity. It is auditable chain reconstruction.

The third improvement is explicit treatment of known exceptions. If a resource is subject to a dispute, a known court order, a pending 8.2 chain review, an agreement boundary, or a service limitation, parties with a legitimate need should be able to understand the category of exception without exposing confidential detail unnecessarily. Title confidence often depends less on eliminating exceptions than on naming them.

The fourth improvement is published evidence expectations for recurring defect types. ARIN's transfer guidance already gives examples of acceptable documents for mergers, acquisitions, reorganizations and name changes. More examples, carefully bounded, could help holders prepare before a sale: dissolved predecessor, trade-name registration, old asset sale with missing schedules, government reorganization, university spinout, bankruptcy sale, parent-subsidiary consolidation, and correction of an original registration error. ARIN does not need to promise outcomes. It can tell the market what evidence usually matters.

The fifth improvement is preservation of decision rationale at the file level. Future reviewers should be able to understand why a chain was accepted, what documents were relied upon, what was redacted, and what limitations remained. That rationale need not be public in full. But if the same resource is sold again years later, the holder should not have to rebuild the entire past from memory because the prior acceptance left no intelligible audit trail.

The sixth improvement is dispute-containment design. ARIN should continue preventing disputed resources from moving as though they were ordinary clean supply. But it should also make clear how stable services are preserved, how claimants can present evidence, how court orders interact with registry action, and how finality is restored after resolution. The market does not need ARIN to adjudicate every private right. It needs ARIN to keep the ledger coherent while rights are adjudicated elsewhere.

The seventh improvement is reliance framing around legacy services. The boundary between resources under agreement and resources outside agreement is a legitimate legal and operational design choice, but it should be explained in reliance terms. Which services are available, which require an agreement, what happens on transfer, how fee changes affect coverage, and how security services interact with market confidence should be presented as parts of the asset's operational continuity. ARIN's legacy page already provides some of this information. The market will need it in sharper form as more legacy resources become financeable assets.

None of these improvements requires ARIN to sell insurance, guarantee values, certify clean reputation, publish private prices or decide private ownership theories. They require a registry to treat its ledger as long-lived infrastructure. That is a narrower role than a property court and a stronger role than a gatekeeper.

Post-exhaustion scarcity makes old history economically decisive

ARIN's free pool of IPv4 address space was depleted on September 24, 2015. After depletion, ordinary requests could no longer be fulfilled from abundant stock except through limited policy paths such as reserved pools for special cases, waiting-list availability, or transfers to specified recipients. That date changed the economic meaning of old records. A registration entry created for technical coordination could become the basis for a valuable transfer, a financing discussion or a corporate-control dispute.

Scarcity does not create every risk. Many defects existed before depletion. But scarcity raises the payoff to exploiting them and the cost of ignoring them. A stale point of contact attached to a low-value resource is a nuisance. Attached to a large legacy block, it may be an invitation to fraud. A missing asset schedule in a long-closed acquisition may have been harmless when no one priced the block. It becomes material when a buyer wants to pay for it. A dispute between successors may have slept while the block was used internally. It awakens when one successor tries to monetize it.

This is why old registration history now affects present allocation efficiency. A block trapped by uncertain history cannot move easily to a network that needs it. A block sold with weak evidence imposes risk on the buyer and on future counterparties. A block whose operational history is not documented may be discounted even if it is technically usable. Scarcity turns historical quality into liquidity.

The effect is distributional. Large firms can hire counsel, reconstruct old corporate chains, absorb delay and negotiate indemnities. Smaller networks may avoid otherwise useful transfers because the evidentiary burden feels unpredictable. Legacy holders with sophisticated advisers can monetize dormant space; holders with weaker records may be trapped. The public ledger cannot equalize every resource-holder capacity difference, but it can reduce unnecessary complexity.

Old history also affects institutional legitimacy. The RIR system depends on the claim that regional registries coordinate unique number resources in the public interest, not that they own the economic value of every scarce entry. As scarcity increases the capital effect of registry decisions, registries must show that their decisions are evidence-based, proportionate and reviewable. A policy process alone is not enough if the outcome makes legitimate historical reliance unfinanceable. Conversely, private property rhetoric alone is not enough if it would allow forged, stale or disputed claims to pass into the registry. The ledger must discipline both sides.

IPv6 will not immediately dissolve this problem. IPv6 is the long-run technical direction, but IPv4 remains embedded in access networks, cloud services, hosting, enterprise systems, security controls, customer equipment, mobile translation systems and business assumptions. As long as IPv4 remains economically useful, old IPv4 history will remain economically relevant. The title-confidence question will outlive the depletion event that made it visible.

The boundary between correction and confiscation

Historical defects raise a hard question: what should happen when the registry discovers that a current record may be wrong? A strong ledger must be able to correct errors. If an original registration was made under a fictitious or trade name, ARIN's transfer FAQ says documentation may be needed to show the original registration was in error and that the name has always been registered to the actual legal organization. If a current registrant no longer exists, an 8.2 transfer may be required before a specified-recipient transfer. These are correction mechanisms.

But correction can feel like confiscation if the holder has relied on the record for years and the process is opaque. A legitimate operator may fear that asking for a routine update will reopen old history. A legacy holder may fear that entering an agreement or requesting services will change its rights. A buyer may fear that a post-closing review will revisit matters it thought were settled. A registry that wants accurate records must therefore make correction safe enough that holders are not punished for surfacing problems.

The distinction between correction and confiscation depends on process. Correction identifies the best-supported recognized holder, fixes names, records succession, prevents unauthorized change and preserves continuity where possible. Confiscation uses uncertainty as a reason to seize value, redistribute resources or force concessions unrelated to the ledger defect. The former strengthens the registry. The latter converts coordination power into economic power.

This boundary is especially important when policies evolve. If a resource was registered under one historical context, later policy should not casually erase reliance created under that context. At the same time, old reliance should not allow indefinite evasion of basic authority, accuracy and security requirements. The balanced position is not simple. It requires proportionality: fix what threatens the ledger; do not use the fix to enlarge control beyond the ledger.

Title insurance again offers a useful frame. Hidden defects are handled through search, exceptions, curative documents, indemnities and, when necessary, claims. The response is targeted. A missing release is cured; an undisclosed lien is paid or excepted; a boundary dispute is identified. The system does not treat every defect as proof that the recorder should own the land. IPv4 should follow the same discipline in its own narrower domain. A defect in the chain should lead to evidence, correction, exception or dispute handling, not institutional overreach.

Official materials are exhibits, not conclusions

ARIN's public pages are important factual exhibits. They show that transfer mechanics are real, that current-holder status matters, that disputes matter, that officer acknowledgement matters, that multiple historical transactions may need documentation, that sensitive commercial terms may be redacted, that transfer completion follows approval, fees and an agreement where applicable, that legacy services have defined boundaries, and that historical registration data exists through WhoWas. They also show that ARIN publishes transfer statistics and a common NRO transfer-log format, while leaving commercial terms outside the registry record.

But official materials should not be treated as the framing authority for the economic conclusion. A registry can accurately describe its process and still leave open whether the process produces enough reliance value for a post-exhaustion market. The question in this article is not whether ARIN has a process. It does. The question is whether the ledger function is sufficiently auditable, historically intelligible and restrained to support the title-like reliance that buyers, lenders, boards and operators now need.

This distinction matters because institutions often defend themselves by showing forms: manuals, pages, tickets, agreements, forms and public statistics. Forms are necessary. They are not sufficient. A title system is judged by how it performs when history is messy, incentives are adverse and reliance is costly. The same should be true for a number-resource registry. Does the process surface defects early? Does it preserve old evidence? Does it prevent fraud without freezing legitimate successors? Does it distinguish public record confidence from private commercial risk? Does it keep running networks stable while disputes are resolved? Does it avoid converting policy vocabulary into broad economic discretion?

These are institutional economics questions, not customer-service questions. They are about transaction costs, information asymmetry, reliance, residual risk, cost of capital and legitimacy. ARIN can be orderly and still face them. Indeed, an orderly registry is where they become most visible, because the problem is not obvious chaos. It is whether a mature coordination body can remain a ledger when scarcity tempts every participant to treat the ledger as a choke point.

What a title-confidence agenda would look like

A serious title-confidence agenda for ARIN-region IPv4 would begin with a simple proposition: the registry's greatest market contribution is reliable recognition, not commercial judgment. From that proposition, several design principles follow.

First, preserve history. Historical registration data should be treated as market infrastructure. It should remain accessible under controlled conditions for legitimate diligence. Reports should be interpretable by counsel, auditors and serious transaction participants, not only by registry specialists. The market cannot rely on a chain it cannot reconstruct.

Second, define states. Current holder, historical holder, contact, authority, submitted transfer, linked transfer, approved transfer, completed transfer, disputed resource, agreement-covered resource, legacy resource, and service-eligible resource should not blur into one another. Each state carries different reliance value. Precision lowers the cost of contracts and reduces disputes about what a message or record means.

Third, name exceptions. If ARIN knows that a resource is subject to a status dispute, a required succession cure, an agreement boundary, an inter-RIR compatibility issue or a service limitation, the category of uncertainty should be available to those who legitimately need to rely. Confidential detail can be protected. Hidden categories cannot be priced.

Fourth, separate ledger questions from market questions. Source authority, current registration, policy eligibility, dispute status and authorized change are registry questions. Purchase price, broker compensation, tax allocation, financing structure and ordinary commercial regret are market questions. The boundary should be repeated because scarcity creates pressure to blur it.

Fifth, make curative paths visible. Holders with old records should know how to prepare before a transaction: validate contacts, gather name-change documents, preserve merger papers, map asset schedules, identify excluded assets, inventory route-security objects, document reverse DNS, and understand agreement status. The best title defect is the one cured before a buyer appears.

Sixth, protect finality without protecting fraud. A completed transfer should carry reliance value. Later challenge should require defined evidence and process. Fraud, forged authority and material error must remain correctable; ordinary second-guessing should not. Markets need both integrity and repose.

Seventh, keep services aligned with reliance. RPKI, IRR, reverse DNS, DNSSEC and registry maintenance are not ornamental. They are part of how public control becomes operational confidence. Service eligibility and agreement requirements should be explained in ways that transaction participants can evaluate.

Eighth, avoid becoming a property court. ARIN should not adjudicate all private rights, decide asset value, insure losses or bless commercial bargains. Courts, contracts, lenders and private risk carriers have their own roles. The registry's role is to maintain a reliable, auditable and restrained public ledger.

These principles would not remove every defect. They would make defects legible. That is the realistic standard. Markets can price known risk; they punish uncertainty that cannot be named.

Legitimacy comes from surviving time, dispute and transfer

The acquisition team returns to the closing room. It has the current record, the historical reports it can obtain, the seller's officer acknowledgement, the merger documents that connect old names to the current entity, the representations and indemnities, the routing cleanup plan, the reverse-DNS plan, the agreement-status analysis, and the lender's list of exceptions. The file is not perfect. No old file is. But it is coherent. The buyer can explain why the seller is the recognized holder. The lender can explain what residual risk remains. The board can see that registry recognition, operational continuity and private warranties are different things. The transfer can close without pretending that the registry has guaranteed every possible future dispute.

That is the economic value of title confidence. It is not certainty. It is disciplined reliance. It lets scarce resources move without turning every transaction into blind faith. It lets old records support new investment without letting stale contacts or hidden defects dominate the market. It lets ARIN remain a registry rather than a bank, insurer, exchange or property court. It lets private parties allocate risk while preserving the public record as the shared reference.

The title-insurance analogy also supplies a warning. If the public ledger is too thin, private markets will build substitutes: private databases, broker memory, bespoke counsel opinions, lender exclusions, larger discounts and narrower buyer pools. Those substitutes may help individual transactions, but they fragment public confidence. If the public ledger becomes too discretionary, the market will price registry power as a political risk. The healthy middle is a ledger strong enough to support reliance and modest enough not to claim the asset's economic value as its own.

IPv4 scarcity has made old registration history economically decisive. The answer is not to force Internet number resources into a real-estate box. Nor is it to deny the title-like risks that scarce resources now carry. The answer is to build registry confidence around the facts that matter: chain of custody, authorized change, dispute survival, historical auditability, service continuity, and clear boundaries between public recognition and private bargain.

ARIN's legitimacy in this market will not come from broader discretion. It will come from the opposite: the ability to maintain a ledger that survives time, dispute and transfer. A record that looks clean today is helpful. A record whose history can be examined, whose exceptions can be named, whose authority can be defended, and whose finality can be relied upon is more valuable. That is the title-insurance lesson, stripped of the insurance product and applied to the economics of the registry. The confidence that matters is not the confidence of a gatekeeper at the moment of approval. It is the confidence of a market that can still explain, years later, why the record deserved to be trusted.