An IPv4 prefix can be visible on the Internet for years without anyone asking a difficult question:
Table of Contents
ToggleWho can actually prove control of it?
The question often appears only when something changes.
A company wants to transfer IPv4 resources.
A merger or acquisition occurs.
A registry account needs to be recovered.
An old corporate entity no longer exists.
A buyer begins due diligence.
A resource becomes disputed.
Or a Regional Internet Registry asks for evidence before updating its records.
At that point, simply saying “we have always used these addresses” may not be enough.
BGP announcements can demonstrate operational use.
WHOIS or RDAP can show registry information.
RPKI can show routing authorisation.
Corporate documents can establish legal succession.
Transfer agreements can establish a chain between previous and current holders.
But no single piece of evidence necessarily answers every question.
For network operators, the strongest approach is to maintain a verifiable chain of control connecting the registry record, legal entity, operational network and historical documentation.
This guide explains what that means and how organisations can prepare before a transfer, dispute or registry change makes proof urgent.
What Does “Control of an IPv4 Address Block” Mean?
The word control can refer to several different things.
An organisation may control the routing of a prefix.
It may control the registry account.
It may appear in the RDAP record.
It may hold the historical allocation documents.
It may have acquired the company that originally received the addresses.
These forms of control can overlap.
But they are not automatically identical.
A useful IPv4 resource review separates at least four layers.
Registry control
Who is recognised in the relevant Internet number registry?
Administrative control
Who can request changes to the registry record and associated services?
Operational control
Who can route, configure and use the addresses?
Documentary or legal control
What contracts, corporate documents and historical records establish the organisation’s relationship to the resource?
The strongest resource position is usually one in which these layers tell a consistent story.
Why Proof of Control Matters
For ordinary day-to-day routing, an organisation may not need to prove the full history of an IPv4 block every morning.
But proof becomes important when the resource needs to change.
Common triggers include:
IPv4 transfers;
mergers and acquisitions;
company name changes;
corporate restructuring;
registry-account recovery;
legacy-resource updates;
bankruptcy or liquidation;
disputes between parties;
due diligence before buying IPv4;
changes in registry relationships.
RIPE NCC’s current procedures illustrate how important documentation can become. For legacy resources, it may request company registration documents, proof of organisation name changes, transfer agreements and other evidence before recognising a party as the legitimate holder.
The lesson is simple:
Proof of control should be assembled before it is urgently needed.
Registry Records Are the First Layer of Evidence
Start with the authoritative registry record.
Depending on the resource, this may be accessible through RDAP, WHOIS or the relevant RIR’s internal registry systems.
Review:
registered organisation name;
IPv4 prefix or range;
organisation identifier;
resource status;
administrative contacts;
technical contacts;
abuse contacts;
registration events;
parent resource;
last-modified information.
If the public record names the organisation that actually controls the resource, that is a strong starting point.
But it should not be treated as the only evidence.
For older resources, especially legacy IPv4 space, the registered organisation may have changed its name, merged into another company or ceased to exist.
That is where the documentary chain becomes critical.
Registry Recognition Is Not the Same as BGP Control
Suppose Company A is recorded as the holder of an IPv4 prefix.
But ASN 64500 is currently announcing the prefix.
Does that mean ASN 64500 owns the addresses?
No.
BGP tells the Internet how traffic should reach a prefix.
It does not by itself prove the legal or registry status of the resource.
A resource holder may legitimately allow another network to originate its prefix.
Examples include:
transit providers;
hosting partners;
cloud infrastructure;
managed network providers;
customers;
leased address arrangements.
Therefore:
BGP announcement = evidence of routing activity
It is not automatically:
BGP announcement = proof of resource holdership
This distinction is essential during disputes.
RPKI Is Evidence of Routing Authorisation
RPKI provides another useful layer.
A Route Origin Authorisation can identify which ASN is authorised to originate a particular prefix.
If the organisation controls the registry relationship needed to create or modify the ROA, that can be valuable evidence of administrative control.
But RPKI still answers a specific question:
Which ASN is authorised to originate this prefix?
It does not necessarily answer:
Who legally owns the resource?
or:
How did the current organisation acquire it?
That is why RPKI should be included in an evidence package rather than treated as a complete ownership certificate.
Corporate Registration Documents Matter
One of the most important forms of proof is often surprisingly ordinary:
company documentation.
Consider this chain:
Original Networks Ltd received an IPv4 allocation.
Years later:
Original Networks Ltd changed its name to Example Infrastructure Ltd.
Later still:
Example Infrastructure Ltd merged into Example Holdings Ltd.
The public registry record may still contain one of the older names.
To establish continuity, the organisation may need documents showing that these entities are legally connected.
Useful evidence can include:
company registration certificates;
official extracts from company registries;
certificates of name change;
merger documents;
acquisition documents;
dissolution records;
court documents;
legal succession records.
RIPE NCC explicitly requires official corporate evidence in a variety of resource-change procedures, including mergers, acquisitions and changes in business structure.
This creates a documentary bridge between the old registry identity and the current organisation.
Transfer Agreements Are Critical Evidence
If IPv4 resources moved from one company to another, keep the agreement showing that movement.
Depending on the transaction, this may be:
a resource transfer agreement;
asset purchase agreement;
merger agreement;
acquisition agreement;
court-approved transfer;
bankruptcy documentation;
settlement agreement.
The exact document will depend on how the transaction occurred.
What matters is that the chain is understandable.
For legacy transfers, RIPE NCC currently requires supporting documents and a confirmation signed by an authorised representative before updating the registration information.
A future administrator should be able to reconstruct:
Original holder → transaction → new holder → current holder
without relying on employee memory.
Who Is Authorised to Act for the Resource Holder?
Proof that a company controls a resource is only half the problem.
The registry may also need proof that the person submitting a request can act for that company.
This matters because an employee having access to an email address does not automatically mean that person has authority to transfer valuable Internet number resources.
Depending on the situation, evidence may include:
director authority;
senior management authority;
registered administrative contact;
board authorisation;
power of attorney;
formal corporate authorisation.
RIPE NCC’s legacy-transfer procedure, for example, requires a confirmation signed by a legally authorised company director or supporting evidence such as a power of attorney when another person signs.
This protects the registry from accepting changes requested by an unauthorised person.
What If the Original Company No Longer Exists?
This is a common problem with older IPv4 resources.
A block may have been issued decades ago.
The original company may now be:
dissolved;
acquired;
merged;
renamed;
liquidated;
reorganised.
The network may still be using the resources normally.
But the documentary chain may be incomplete.
In this situation, the objective is to establish legal succession.
Ask:
What happened to the original entity?
Did another company acquire its assets?
Was there a merger?
Was the company renamed?
Did a court or administrator transfer the assets?
Do official records document the change?
RIPE NCC’s current transfer procedure specifically addresses situations where a transferring party no longer exists and may require official closure documents together with earlier agreements or other authorised evidence.
This is why old corporate documentation should not be discarded simply because the network continues to work.
How Legacy IPv4 Makes Proof More Important
Legacy IPv4 can be particularly documentation-sensitive.
These resources may have been issued before modern RIR agreements existed.
The original allocation may be decades old.
The holder may have undergone several corporate changes.
The registry relationship may have changed.
Historical correspondence may be incomplete.
In these cases, the resource holder may need to demonstrate a longer chain of evidence.
RIPE NCC states that legacy-resource due diligence can include company registration documents, evidence of name changes and transfer agreements when determining whether an organisation is the legitimate holder.
That is why organisations holding legacy IPv4 should build a permanent evidence archive.
What Is an IPv4 Chain of Control?
A useful concept is an IPv4 chain of control.
This is the documentary history showing how control of a number resource moved from its original holder to the organisation managing it today.
A strong chain might look like:
Original allocation
↓
Original holder
↓
Company name change
↓
Merger or acquisition
↓
Transfer documentation
↓
Current registry holder
↓
Current authorised contacts
↓
Current routing and RPKI state
The objective is not to create unnecessary paperwork.
It is to make the history independently understandable.
Evidence That Strengthens an IPv4 Control Claim
A strong proof package may include several categories.
Registry evidence
RDAP record;
WHOIS history;
registry account information;
resource status;
registry correspondence.
Corporate evidence
current company registration;
historical company registration;
name-change certificates;
merger records;
acquisition documents.
Transaction evidence
IPv4 transfer agreements;
asset purchase agreements;
court orders;
bankruptcy or liquidation records.
Administrative evidence
authorised contacts;
board or director authorisation;
power of attorney;
registry-account access records.
Operational evidence
BGP announcements;
RPKI ROAs;
IRR objects;
reverse DNS control;
network configuration;
upstream agreements.
No single organisation will always need every item.
The objective is consistency.
Is Routing History Proof of IPv4 Ownership?
Not by itself.
Historical BGP data can show that a network has announced a prefix for many years.
That can provide useful supporting evidence of operational continuity.
But long-term routing does not automatically establish registry or legal rights.
A network can legitimately announce space held by another organisation.
Similarly, an unauthorised party can sometimes originate a prefix.
Therefore, routing history is best treated as:
supporting operational evidence
rather than:
conclusive proof of holdership
Is WHOIS or RDAP Proof of Ownership?
It is strong registry evidence, but the word ownership requires care.
RDAP and WHOIS are designed to publish registration information.
They can show which organisation is associated with an Internet number resource in the registry.
That information matters significantly.
But legal rights may also depend on:
contracts;
transfer history;
corporate succession;
applicable law;
court decisions.
For this reason, it is usually safer to say:
the registry recognises this organisation as the resource holder
rather than assuming that one database field resolves every possible legal ownership question.
What If the Registry Record Is Wrong?
This is exactly why organisations should maintain independent evidence.
A registry record can become outdated after:
a company name change;
merger;
acquisition;
administrative mistake;
incomplete historic update.
The correct approach is usually to reconcile the record with documentary reality.
This is an important registry principle:
The registry should accurately reflect legitimate resource control.
If the database and corporate reality have diverged, the goal should be to update the record through a verifiable process.
RIPE NCC explicitly states that registration data should remain accurate and provides processes for updating records following business-structure changes.
What If Two Parties Claim the Same IPv4 Block?
This is where proof becomes especially important.
Imagine:
Company A appears in an old registry record.
Company B has routed the block for ten years.
Company C says it acquired Company A’s assets.
Which company controls the resource?
BGP alone cannot answer that.
The old registry record may not answer it either.
A proper review may need to examine:
original allocation;
corporate succession;
transfer agreements;
registry correspondence;
authorised representatives;
routing history;
relevant court decisions.
The system should distinguish between an outdated record and a genuine competing claim.
Where a real dispute exists, preserving evidence is more useful than pretending uncertainty does not exist.
Why Registry Audit Trails Matter
A trustworthy registry should make legitimate changes auditable.
Important questions include:
Who requested the change?
When?
Under what authority?
What supporting documents were reviewed?
What was the previous state?
What is the current state?
Auditability protects both the resource holder and the registry.
It helps reduce:
fraudulent transfers;
unauthorised changes;
disputes;
uncertainty following corporate restructuring.
For high-value IPv4 resources, a change history is part of infrastructure governance.
Do Not Wait Until You Want to Sell or Transfer the Block
A common mistake is to perform due diligence only when a transaction begins.
That is late.
Problems may take time to resolve.
For example:
the original company may have disappeared decades ago;
directors may no longer be available;
archives may be incomplete;
registry contacts may be outdated;
the corporate succession chain may require research.
If the company suddenly needs to transfer the addresses, these issues can delay the transaction.
A better approach is to maintain transfer readiness continuously.
IPv4 Control Audit Checklist
Network operators should periodically verify the following.
Registry
Which RIR administers the resource?
What organisation is currently registered?
Is the prefix correct?
Are contacts current?
Is the resource under the expected account?
Corporate
Does the registered entity still exist?
Has its legal name changed?
Have mergers or acquisitions occurred?
Can each change be documented?
Documentation
Is the original allocation evidence available?
Are transfer agreements archived?
Are registry communications preserved?
Is the chain between previous and current entities clear?
Administration
Who can access the registry account?
Who is authorised to request changes?
Is access dependent on one employee?
Are powers of attorney or board approvals documented where necessary?
Routing
Which ASN originates the prefix?
Is that expected?
Does the routing match internal documentation?
RPKI
Who can create or update ROAs?
Is the authorised origin correct?
Would the company retain access during staff turnover?
Reverse DNS
Who controls delegation?
Are nameservers current?
Can the organisation update them?
Internal ownership
Which department is responsible for the resources?
Are they listed in the asset inventory?
Are executives aware of their value and operational significance?
What Buyers Should Check Before Acquiring IPv4
A buyer should not rely only on a seller’s statement that it controls a block.
Verify independently.
Ask for evidence showing:
the seller is the recognised resource holder;
the person negotiating the transaction is authorised;
the corporate identity matches registry records;
any previous name changes or mergers are documented;
the prefix is not subject to an unresolved dispute;
the transfer can be processed under the relevant registry framework.
Operational checks should also include:
BGP history;
RPKI status;
IRR records;
reverse DNS;
reputation history.
This turns due diligence from a simple lookup into a full resource review.
What Sellers Should Prepare
Sellers can reduce transfer friction by preparing a documentation package before entering the market.
That package may include:
current registration documents;
registry resource list;
authorised-signatory information;
historical company changes;
previous transfer evidence;
current routing information;
relevant registry correspondence.
The cleaner the chain, the easier it is for another party—and the registry—to verify the transaction.
Proof of Control Is Also a Continuity Issue
This subject is not only about transactions.
Imagine the registry account is lost.
The employee managing the resource leaves.
The company reorganises.
The organisation now needs to prove that it is still entitled to administer the block.
If all evidence exists only inside an inaccessible account or the memory of a former employee, recovery becomes harder.
Proof of control should therefore be included in a company’s number-resource continuity plan.
The organisation should be able to prove its position even when:
credentials are lost;
staff change;
systems fail;
the company restructures;
registry services are interrupted.
That is infrastructure resilience.
What a Good Registry Should Verify
A registry has legitimate reasons to verify requests that change Internet number-resource records.
Those checks can protect:
uniqueness;
registry accuracy;
resource holders;
downstream operators;
transfer integrity.
Reasonable verification may include:
identity of the current holder;
authority of the requester;
evidence of corporate succession;
evidence of transfer;
absence of conflicting claims.
The purpose should be to keep the registry accurate.
Verification becomes most useful when it is based on objective evidence and predictable procedures.
The Difference Between Verification and Control
This distinction is important for Internet governance.
A registry needs enough authority to reject fraudulent record changes.
Otherwise, the database cannot be trusted.
But verifying that a requester controls a resource is different from deciding how that resource should be commercially used.
For example:
“Can you prove that your organisation is the legitimate holder?”
is a registry-accuracy question.
“Do we approve of your business model?”
is a different question.
A resilient registry architecture keeps these categories separate.
The registry should verify the chain of authority necessary to maintain accurate records without unnecessarily turning technical registration into broader commercial control.
Build the Evidence Before the Dispute
The best time to prove control of an IPv4 block is before anyone challenges it.
Build a permanent resource file containing:
registry evidence;
legal entity records;
transfer history;
corporate succession;
routing state;
RPKI information;
administrative authority.
Review it periodically.
Update it whenever:
the company changes name;
a merger occurs;
resources are transferred;
registry contacts change;
the origin ASN changes;
a new registry agreement is signed.
An IPv4 block can remain operational for decades.
Its documentation should be able to survive just as long.
Conclusion
Proving control of an IPv4 address block is not about producing one magic certificate.
It is about consistency.
The registry record should identify the correct holder.
Corporate documents should support that identity.
Transfer history should explain how the resource arrived there.
Authorised representatives should be verifiable.
Routing should match the intended network.
RPKI should reflect legitimate route-origin authority.
Operational records should support the same story.
When those layers align, IPv4 administration becomes easier to defend, audit and transfer.
When they diverge, risk grows.
For network operators, the principle is straightforward:
Do not merely route your number resources.
Document them.
Know who controls them.
Know how that control can be proved.
And make sure the evidence can survive the people, companies and systems that may change around the resource over time.
Frequent Asked Questions
Start with the authoritative registry record, then support it with corporate registration documents, allocation or transfer history, authorised contacts and relevant operational evidence such as routing and RPKI information.
It is important registry evidence, but broader ownership or control questions may also require corporate documents, contracts, transfer records and other evidence.
No. BGP demonstrates routing activity. A network can legitimately announce a prefix on behalf of another resource holder.
Not necessarily. A ROA demonstrates authorisation for an ASN to originate a prefix. It is useful evidence of routing control but does not replace registry and legal documentation.
