What Proof Establishes IPv4 Ownership for an IP Transfer in 2026?

What Counts as Evidence of IPv4 Ownership?

The strongest evidence of IPv4 ownership is a verifiable chain connecting the legal entity claiming the address to the registry record for the relevant resource holder, number holder, or country code block. Depending on the transfer structure, that chain may include a registry extract, an authorized-signatory record, a sub-allocation record, a business-registration document, an assignment agreement, and proof that the transfer authority approved or completed the change. A screenshot of an IP geolocation page, WHOIS output, invoice, or domain registration is useful supporting material, but it does not by itself establish legal ownership.

Also worth reading: How Does IPv4 Ownership Verification Work, and What Evidence Do Registries Require? · What Does IPv4 Transfer Due Diligence Actually Require in 2026? · How Do IPv4 Transfer Policies Affect the Sale, Purchase, and Redeployment of Address Space?

IPv4 addresses are allocated and transferred through a hierarchical system rather than sold like ordinary assets in a retail marketplace. Regional Internet Registries manage address space, National Internet Registries often manage local allocation, and network operators receive allocations for their own use or distribute suballocations to customers. AFRINIC, for example, identifies two broad forms of address resource: scarce, widely supported IPv4 space and the much more plentiful IPv6 resource. Registry evidence is therefore strongest when it reflects the exact role of each party in that hierarchy, not merely the name shown beside an address block.

For due diligence, treat “ownership” as a claim that requires several forms of corroboration. Confirm the registry identity, allocation history, transfer status, authorization, legal entity, technical acceptance, and commercial rights separately. As of 26 September 2026, a buyer should not release the balance of a high-value IPv4 transaction until those elements align across the relevant records and the receiving network demonstrates that it can route the space in production.

Why the Registry Record Is the Starting Point

The relevant registry record is authoritative for network administration because it identifies the entity currently responsible for a particular allocation or assignment. It can reveal the resource holder, address range, allocation date, status, and administrative contacts, subject to current registry policies. A transfer may remain pending while documents are under review, so the wording and status fields must be preserved in the evidence package. A historical record, a record marked transferred, and a record showing the recipient as the active holder do not support the same conclusion.

Registry evidence does not answer every legal question. The record may establish the current recognized holder without showing the precise scope of an intellectual-property license, whether a transaction involved merely leased service, or whether a court has ordered a transfer. Conversely, a contract can describe an assignment while the registry still lists the old holder, leaving operational and documentary evidence out of sync. Counsel should therefore compare the contract, corporate authority, registry record, routing state, and payment record rather than treating one source as conclusive.

The address range and its RIR status must also be checked. Transfers within the same RIR generally follow that registry’s transfer process, while cross-RIR movement is more complex and may require inter-registry coordination. Legacy address space, reclaimed space, and transfers to or from special-purpose categories can involve different rules. Evidence should record the exact prefix, prefix length, RIR, current status, and date retrieved, because a 24 September 2026 record provides stronger transaction evidence than an undated copy supplied months earlier.

Documents That Corroborate a Transfer Claim

A well-prepared ownership file combines primary legal evidence with registry and technical verification. The core commercial document is an asset purchase agreement, assignment, transfer authorization, or service agreement that identifies the IPv4 block precisely. It should state whether the seller transfers the resource itself or grants a right of use, identify the legal entities by full registered names, establish closing conditions, and allocate responsibility for taxes, fees, and outstanding claims. For counsel, the document should connect the IP asset to the party that has authority to transfer it.

Corporate records then test whether that party could sign the transaction. A certificate of incorporation, current registry extract, board resolution, powers of attorney, or authorized-signatory confirmation may be appropriate, depending on the jurisdiction and deal value. If a parent, subsidiary, insolvency administrator, or asset manager participates, authority must be traced to the asset rather than inferred from a familiar company name. Domain and trademark registrations should not be offered as substitutes, because they demonstrate control of an identifier, not ownership of an address allocation.

Technical evidence should confirm what the receiving organization actually controls. A routing table extract, BGP origin record, RPKI authorization record, internal IP address-management export, and production test can show operational use. These records do not automatically prove beneficial or legal ownership, but they help detect fraud, duplicate announcements, and mistaken assumptions. The evidence package should also contain a custodian statement, data-room index, and dated chain of custody so a reviewer can reproduce what was checked rather than relying on a seller’s summary.

## The Practical Verification Process

Begin by obtaining the exact prefix rather than accepting a marketing description such as “a /16 owned by a telecom.” Record the RIR, registry account involved, allocation category, current holder, status, and date of retrieval. Preserve the original export and a human-readable copy, and calculate basic measures such as total addresses, whether the quantity is 256 in a /24 or 65,536 in a /16, and the number of addresses actually routed. A large allocation can include unused or reserved space, so advertised quantity should not be confused with sellable or operationally active capacity.

Next, compare the registry record with the seller’s legal identity and signing authority. A mismatch is not necessarily fatal because an assignment may be pending, but it should be explained in writing and linked to the transfer workflow. The authorization should identify the block, transaction, parties, and closing date, while the agreement should state who bears the risk if the registry rejects the transfer. Review any transfer policy, eligibility restriction, fee, escrow arrangement, or reserve or legacy designation that applies to the range. Registry consultation is appropriate where the interpretation of a status field affects completion.

Technical verification comes after documentary review but before final release. Check route origin, RPKI validity, visible routing, reverse delegation consistency, and whether the seller can withdraw control without disrupting the buyer. Confirm that the receiving network is legally and technically ready, including contacts, filtering, monitoring, and customer-impact planning. Some transfers are administratively simple, but cross-RIR or complex reallocations can take longer because multiple authorities and routing communities are involved. Give the process enough time to resolve mismatches instead of treating a database update as immediate operational delivery.

Comparing Direct Ownership, Leasing, and Brokered Access

Not every transaction labeled an “IPv4 purchase” is the same legal or operational arrangement. A direct transfer places an allocation under the recipient’s registry authority, which generally gives the recipient stronger control over the resource. A lease may leave the provider as holder while granting the customer contractual use for a term. Managed address service can provide routing, security, and operational support while the customer receives no transferable asset. Each option may be legitimate, but the ownership evidence and exit rights differ substantially.

A broker can facilitate any of these structures, but a broker’s statement that an allocation is “owned” is not equivalent to registry evidence. Ask whether the broker holds title, acts as agent, pools addresses from several providers, or has a contractual right to deliver the stated prefix. Reconcile commissions and fees, because a quoted purchase price can obscure the amount paid to the actual resource holder. For B2B registry and product workflows, the appropriate choice depends on whether the business needs durable IP assets, stable capacity, or simply secure connectivity.

Common Mistakes in Ownership Due Diligence

One common error is equating the network operator of a route with the legal owner of the resource. An upstream provider may announce addresses that are leased, suballocated, or temporarily held for a customer. Another error is relying on a static screenshot or commercial database that was correct when it was created. Ownership can change, and a database may lag a registry update or preserve only a normalized name, so its retrieval date and source must be recorded.

Buyers also fail to reconcile differing prefixes. The agreement may cover “the company’s IPv4 portfolio,” while the registry record concerns one allocation and routing covers another. Require schedules that state the exact address ranges, exclusions, reserved space, and delivery condition. Do not count route advertisements as proof that every address is usable; network policy, routing, reverse delegation, and organizational controls can limit actual deployment.

A subtler mistake is assuming that a clean corporate record resolves beneficial ownership. The registered entity may be a nominee, holding company, trustee, or special-purpose vehicle. Determine the contracting party, ultimate economic owner where material, and person authorized to dispose of the resource. Finally, avoid releasing funds solely because a portal displays the recipient’s name. Completion should require a coordinated set of evidence, including registry acceptance where applicable, technical validation, final documents, payment clearance, and a reliable operational handoff.

When to Act and What It May Cost

Act immediately when an IPv4 prefix appears in a transaction, security review, insolvency, M&A diligence process, or registry dispute. Obtain a dated ownership extract at the start, then refresh it before signing, before closing, and after transfer completion. The interval can be short for a routine same-RIR transfer, but a cross-RIR process may involve documentation review, policy checks, routing coordination, and waiting periods. If the address is under an active legal claim or operational incident, preserve records and escalate to the registry and qualified counsel rather than negotiating solely through informal email.

Pricing depends on the address block, market conditions, registry category, seller motivation, and transaction services. Registry and transfer fees are often modest relative to the commercial value of a large or clean allocation, while brokers, legal counsel, valuation, escrow, tax work, routing engineering, and address-management systems add separate costs. A /24 contains 256 addresses, whereas a /16 contains 65,536, but price cannot be inferred from count alone; reputation, routing history, location, cleanliness, transferability, and scarcity affect value. Ask for a complete fee schedule and distinguish the purchase consideration from administrative and professional expenses.

The threshold for enhanced diligence should rise with the value and operational importance of the block. Even a smaller allocation deserves current registry evidence, but a portfolio-sized transfer may require counsel, technical validation, sanctions and compliance screening, beneficial-ownership analysis, and a staged escrow process. Set a written materiality rule, such as requiring registry-certified records and independent technical confirmation for a transaction above the organization’s internal risk limit. The exact numerical threshold should reflect the company’s exposure, not an invented industry standard.

The Evidence Standard for a Defensible File

A defensible ownership file shows a continuous, dated chain from legal authority to registry status and technical control. It identifies the exact resource, names each relevant legal person, records who represented or authorized each party, and explains every transition. The final file should distinguish a completed transfer from a pending application and a contractual right from actual network use. It should be reproducible: a reviewer should be able to retrieve current records, compare document dates, and understand why a discrepancy does or does not change the conclusion.

The practical standard is not “the seller said so,” nor is it merely “WHOIS lists a name.” It is corroborated evidence that the party seeking to transfer or license the IPv4 resource had the relevant authority, the resource was available and eligible, the counterparty received the rights promised, and the network can operate the address space as represented. That standard supports B2B intellectual-property decisions without pretending that a database result resolves every legal question. It also gives counsel and product teams an auditable basis for accepting, rejecting, or monitoring an IPv4 asset claim.

For the date of this answer, 26 September 2026, records should be retrieved and preserved close to transaction milestones. The underlying allocation model remains hierarchical: regional registries such as AFRINIC and the RIPE NCC manage address resources, with national or local registries and network operators participating in distribution. IPv4 remains scarce compared with IPv6, but scarcity alone does not prove ownership. The best evidence is the current, exact, and internally consistent registry record supported by authority documents and technical confirmation.