What Is an IP Address Registry and How Does It Work?

What Is an IP Address Registry?

An IP address registry is part of the global system used to coordinate and maintain registration information for Internet number resources, including IPv4 addresses, IPv6 addresses and Autonomous System Numbers (ASNs).

Its fundamental purpose is to help Internet number resources remain globally unique, accurately recorded and usable across independently operated networks.

The Internet is not operated by a single company, network or government. Instead, thousands of independent networks exchange traffic while relying on common technical identifiers.

That makes coordination essential.

The Internet Assigned Numbers Authority (IANA) maintains top-level registries for IPv4 addresses, IPv6 addresses and Autonomous System Numbers. RFC 7020 describes the Internet Numbers Registry System as a hierarchical framework for distributing globally unique Internet number resources and identifies uniqueness and accurate registration as core requirements.

For readers who want to start with the fundamentals of addressing itself, the Larus Foundation provides educational resources explaining how IP addresses support communication between networks.

For businesses and network operators, however, there is another important question:

Who maintains the records around those addresses, and what happens when those records become inaccurate, outdated or difficult to manage?

That is where the IP address registry system becomes important.

Why Does the Internet Need IP Address Registries?

The most fundamental reason is uniqueness.

Public Internet number resources need to be coordinated so that independent networks do not unknowingly rely on incompatible claims to the same identifiers.

RFC 7020 describes maintaining a registry of allocations to ensure uniqueness and accurate registration as a core requirement of the Internet Numbers Registry System.

Without reliable coordination, network operators could face uncertainty about:

• which organization is associated with a particular address range;
• which contacts are responsible for the resource;
• which registry administers the resource;
• whether registration information has changed;
• how a transfer or other change should be recorded; and
• where to begin when operational problems arise.

The registry system therefore provides an important information and coordination layer.

At a high level, it helps support:

• globally unique Internet number resources;
• accurate resource records;
• identification of organizations associated with resources;
• administrative, technical and abuse contacts;
• network troubleshooting;
• resource transfers and record changes;
• access to registration information; and
• continuity of important coordination functions.

This does not mean that a registry operates the networks using those addresses.

Networks remain independently operated.

The registry provides part of the coordination framework that helps those networks interact reliably.

How Does the Global IP Address Registry System Work?

A simplified view of the Internet number resource system looks like this:

IANA → Regional Internet Registries → Network Operators and Other Organizations → Networks and Users

In practice, Local Internet Registries, National Internet Registries, ISPs and other structures may also be involved, depending on the region and resource.

The important point is that the system is hierarchical rather than every individual organization obtaining address space directly from one global database.

1. IANA Coordinates Internet Number Resources Globally

At the global level, IANA maintains number-related registries for the three core resource types:

• IPv4 addresses;
• IPv6 addresses; and
• Autonomous System Numbers.

IANA also provides allocation data relating to resources distributed to Regional Internet Registries.

This provides a global coordination layer while allowing regional organizations to handle much of the day-to-day administration of Internet number resources.

For readers interested in the institutional relationship between the global and regional layers, BTW.Media explains how IANA and the Regional Internet Registries work together.

2. The Five Regional Internet Registries

There are currently five Regional Internet Registries, commonly called RIRs. The Number Resource Organization states that these RIRs manage, distribute and register IPv4 address space, IPv6 address space and Autonomous System Numbers within their respective service regions.

Each RIR operates within its own organizational, policy and service framework while participating in the wider Internet number resource system.

NRS provides a dedicated introduction to Regional Internet Registries and their role in Internet number resource management.

Understanding this structure is useful because the RIR associated with an IP block can affect the administrative processes that an organization encounters throughout the life of the resource.

3. Internet Number Resources Are Registered to Organizations

Internet number resources may ultimately be associated with:

• Internet service providers;
• telecommunications companies;
• cloud providers;
• hosting companies;
• data centres;
• enterprises;
• universities;
• governments; and
• other organizations operating networks.

Depending on the history of a resource, its current registry position may result from:

• an allocation;
• an assignment;
• a recognized transfer;
• a merger or acquisition;
• corporate restructuring; or
• another applicable administrative process.

That history can matter.

A block registered many years ago may today support an organization that has changed its legal name, ownership structure, infrastructure providers or network architecture.

As a result, Internet number resource management should not always be treated as a one-time administrative exercise.

Records need to remain understandable as organizations and networks evolve.

What Information Does an IP Address Registry Contain?

The exact information available differs according to the registry, resource type and applicable policies.

However, several types of information commonly appear in Internet number resource databases.

IP Address Range

The record identifies the relevant IPv4 or IPv6 address block.

Instead of treating every address separately, Internet number resources are commonly represented as prefixes or address ranges.

For example, an organization may operate a /24 IPv4 prefix rather than treating all 256 addresses as unrelated individual registrations.

Organization Information

Registry records may identify the organization associated with a resource.

Keeping this information accurate becomes especially important when companies:

• merge;
• restructure;
• change their legal names;
• acquire another business; or
• move resources between related entities.

Contact Information

Records may include administrative, technical or abuse contacts.

These contacts can help other operators identify the appropriate party when troubleshooting, security or resource-related communication is required.

Resource Status

Registries use different classifications to describe how resources are registered or administered.

The precise meaning of those classifications depends on the relevant registry and its policies.

Related Operational Information

Depending on the registry system, additional records or services may also support functions such as:

• reverse DNS;
• routing information;
• RPKI;
• resource delegations; and
• security-related coordination.

Together, these records form an important information layer around Internet number resources.

What Is RDAP?

RDAP stands for Registration Data Access Protocol.

It provides standardized web-based methods for retrieving registration information from registries.

RFC 9082 defines uniform patterns for constructing HTTP queries used to retrieve registration information, making RDAP a structured method for accessing registry data.

For a network operator, RDAP can help answer questions such as:

• Which registry administers this IP resource?
• Which organization is associated with the range?
• Which public contacts are available?
• What registration status information is provided?
• What other registration metadata is available?

Because RDAP returns structured data, it can also be easier for software and automated systems to process than older text-based approaches.

IP Registry vs. WHOIS vs. RDAP

These three terms are related, but they do not mean the same thing.

A simple way to remember the difference is:

Registry = maintains the record

WHOIS / RDAP = methods used to access registration information

The distinction matters because accurate query results depend on accurate underlying records.

For example, outdated organization names or contacts can make an IPv4 resource harder to investigate or administer even when the underlying network remains operational.

LARUS examines this problem in more detail in Outdated WHOIS and RDAP Records: A Hidden Risk in IPv4 Transfers, which discusses how stale registration information can complicate transfer due diligence, routing onboarding, abuse handling and operational continuity.

Does an IP Registry Record Prove Legal Ownership?

Not necessarily.

This distinction is especially important when businesses deal with valuable IPv4 resources.

A registry entry should not automatically be treated as the equivalent of a property deed or as a complete legal determination of ownership.

Internet number resources operate within technical, administrative, contractual and, in some circumstances, legal frameworks.

Questions concerning rights over a particular resource may depend on factors such as:

• how the resource was originally obtained;
• relevant contractual arrangements;
• applicable registry policies;
• transfer history;
• corporate history;
• supporting documentation;
• applicable law; and
• decisions of competent authorities where disputes arise.

A registry record can therefore be an important part of understanding how a resource is administered without necessarily answering every possible legal or contractual question.

For organizations considering a significant IPv4 transaction, corporate restructuring or dispute, registry information should be reviewed alongside appropriate documentation and relevant professional advice.

This approach protects against two opposite mistakes:

Mistake one: assuming registry information has no importance.

Mistake two: assuming one registry field answers every technical, commercial and legal question surrounding a resource.

Neither extreme provides a complete picture.

Why Accurate IP Registry Records Matter

Registry information can look like administrative paperwork.

For organizations operating important networks, however, it may have much wider practical significance.

1. Network Coordination

If one network needs to investigate activity associated with an IP prefix, accurate registration information can make it easier to identify the relevant organization and contact points.

This supports communication between independently operated networks.

2. Troubleshooting

Routing incidents, infrastructure migrations and security events can require coordination between multiple parties.

Accurate records help reduce uncertainty about who should be contacted.

3. Resource Administration

Organizations constantly change.

Employees leave.

Companies merge.

Legal names change.

Infrastructure moves.

Cloud architectures evolve.

An IP registration record that was correct five or ten years ago may no longer reflect current organizational circumstances.

Periodic review can help keep the registry layer aligned with verifiable information.

4. Transaction Due Diligence

Registry information can also become important when IPv4 resources are evaluated for transfer.

Questions may include:

• Which RIR currently administers the resource?
• Which organization appears in the records?
• Does the registration history correspond with available documentation?
• Are administrative contacts current?
• Are there unresolved inconsistencies?
• Which registry procedures apply to the proposed transaction?

Registry data is not the whole due-diligence process, but it is often an important starting point.

IP Address Registries and IPv4 Transfers

The registry layer becomes particularly visible when an IPv4 resource changes hands.

A commercial agreement between two organizations is only one part of an IPv4 transaction.

Registry records may also need to be updated through the processes applicable to the source and recipient.

If the organizations are associated with different RIR regions, the process can become more complex because more than one registry framework may be involved.

For organizations researching this area, i.LEASE provides a practical guide to which RIRs support inter-RIR IPv4 transfers in 2026.

This is a good example of why organizations should understand the registry layer before entering an important number-resource transaction.

A resource may be technically routable, commercially valuable and operationally useful, while still requiring careful administrative planning to ensure the surrounding records remain accurate.

Why IP Address Registration Is a Business Continuity Issue

For some organizations, an IP address starts as ordinary network capacity.

Over time, that address can become embedded into the organization’s operational environment.

It may appear in:

• customer allowlists;
• firewall rules;
• VPN configurations;
• API access controls;
• payment systems;
• DNS records;
• email infrastructure;
• cloud environments;
• security monitoring systems;
• partner integrations; and
• compliance documentation.

Once enough external systems depend on a particular address or prefix, changing that number can become significantly more complicated than editing a router configuration.

This is why Internet number resource management can become a business continuity issue.

NRS explores this relationship in How IP Address Rights Affect Business Continuity, examining how dependence on Internet number resources can turn registry and administrative issues into operational concerns.

The practical principle is straightforward:

The more operational dependency a business builds around an Internet number resource, the more important continuity of that resource becomes.

A well-managed organization should therefore know not only which IP addresses it uses, but also how those resources are registered, administered and documented.

Registry Records Should Support Operational Reality

One useful way to understand the Internet number registry system is to distinguish between two layers.

The registry layer records and coordinates information.

The network layer carries the traffic.

Both layers matter, but they perform different functions.

A registry record by itself does not route a packet.

At the same time, an operational network can become harder to administer when its registry information no longer corresponds with verifiable organizational circumstances.

That is why accurate records matter.

Good registry administration should seek to maintain reliable information while supporting:

• uniqueness;
• traceability;
• security;
• interoperability; and
• continuity.

This leads to an important principle for Internet infrastructure:

The value of coordination comes from helping independent networks operate reliably together.

A registry is most useful when its records provide an accurate and dependable coordination layer for the networks that rely on them.

Why Network Operators Should Audit Their Internet Number Resources

Organizations that depend on public IP infrastructure should periodically audit their Internet number resources.

A useful review can begin with several questions.

What Internet Number Resources Do We Depend On?

Create an inventory covering relevant:

• IPv4 prefixes;
• IPv6 prefixes;
• Autonomous System Numbers; and
• related infrastructure dependencies.

For large organizations, it may also be useful to document which business units, cloud environments, data centres or customers depend on each resource.

Where Are Those Resources Registered?

Identify the RIR or other applicable registry structure associated with each resource.

Do not assume that every resource in the organization follows exactly the same administrative history.

Are Our Organization Details Accurate?

Check whether registration records reflect the appropriate organizational information.

Corporate restructuring can easily create discrepancies if registry records are not reviewed at the same time.

Are Our Contacts Current?

A former employee should not remain the only administrative or technical contact associated with strategically important number resources.

Contact maintenance should be part of normal infrastructure governance.

Do We Understand the Resource History?

For older IPv4 blocks, organizations may benefit from maintaining documentation relating to:

• original allocation or assignment;
• transfers;
• mergers;
• acquisitions;
• organizational changes; and
• other important administrative events.

Do We Control Administrative Access?

Registry accounts and resource-management systems should be treated as infrastructure security assets.

Organizations should understand who has access, how credentials are recovered and what happens when responsible employees leave.

Do We Maintain Supporting Documentation?

Important transfer records, agreements, correspondence and corporate documentation should be maintained according to appropriate organizational and legal requirements.

The purpose of this exercise is not simply compliance.

It is visibility, resilience and continuity.

Why Registry Resilience Matters

The Internet derives much of its resilience from the fact that it consists of independently operated networks rather than a single global network operator.

A similar resilience mindset can be useful when considering Internet number resource administration.

Organizations can ask:

• Are critical registry records auditable?
• Can historical changes be traced?
• Are administrative responsibilities clearly documented?
• Can important services recover from technical failures?
• Can disputes be managed without unnecessarily disrupting running networks?
• Are there appropriate backups and continuity mechanisms?
• Are there dependencies on a single person, account or process?
• What happens if an important administrative relationship changes?

The objective is not to eliminate coordination.

It is to make coordination more dependable.

Critical infrastructure benefits from credible recovery paths.

Critical records benefit from redundancy.

Critical administrative systems benefit from clearly defined continuity procedures.

Internet number resources should be considered through the same lens.

Why IP Address Portability Matters

Portability introduces another important dimension to registry resilience.

At the network-provider level, portability may describe the ability to continue using important addressing resources when infrastructure or connectivity providers change.

At a broader governance level, portability also raises questions about how number-resource continuity can be preserved if the administrative environment surrounding a resource changes.

The Larus Foundation’s guide to why IP address portability matters for network operators explores this issue in detail, including network continuity, registry resilience, failover and the distinction between changing an administrative relationship and transferring a resource to another organization.

Portability should not be interpreted as an argument that registries have no useful role.

Registries perform important coordination functions.

Instead, portability introduces a resilience question:

Can the coordination function remain dependable even when the organization, service provider or administrative relationship around a running network changes?

That is a useful question for any critical infrastructure system.

Coordination and Control Are Not the Same Thing

One of the most useful distinctions in Internet governance is between coordination and control.

The Internet unquestionably requires coordination.

Independent networks need common mechanisms for:

• maintaining unique identifiers;
• exchanging traffic;
• locating relevant resource information;
• maintaining accurate records;
• supporting security mechanisms; and
• preserving interoperability.

But coordination does not require every technical, operational or commercial decision to be centralized.

For Internet number resources, a focused coordination layer can prioritize several principles.

Uniqueness

Internet number resources should remain globally coordinated so incompatible duplicate registration does not undermine reliable network operation.

Accuracy

Registry information should remain aligned with verifiable information.

Transparency

Operators should be able to understand relevant records and processes.

Security

Resource-related coordination should support secure network operation.

Continuity

Administrative processes should take the continuity of networks relying on number resources seriously.

Resilience

Critical functions should be designed to reduce unnecessary single points of failure.

These principles provide a constructive way to evaluate Internet number resource governance while keeping the focus on the networks that actually use the resources.

For readers interested in the wider relationship between registry structures, policy and Internet infrastructure, BTW.Media provides ongoing coverage of Internet governance and Regional Internet Registry developments.

The IPv4 Market Adds Another Layer

IPv4 scarcity has added a commercial dimension to Internet number resource management.

IANA’s current allocation information notes that its general IPv4 supply has been exhausted, while IPv6 and ASN resources continue to be allocated through the regional system.

As a result, organizations seeking IPv4 capacity may encounter:

• transfers;
• leasing arrangements;
• IPv4 marketplaces;
• legacy resources;
• corporate acquisitions; and
• other mechanisms for obtaining usable address space.

This creates an important distinction.

The registry layer and the commercial layer are related, but they are not the same thing.

A commercial transaction concerns the arrangement between parties.

The registry layer concerns the accurate administration and recording of relevant number-resource information under the applicable framework.

Network deployment adds yet another layer:

• BGP routing;
• LOAs;
• reverse DNS;
• RPKI;
• reputation;
• geolocation;
• abuse handling; and
• customer continuity.

A well-managed IPv4 strategy needs to understand how these layers interact rather than assuming that any single layer answers every question.

For businesses evaluating IPv4 leasing and IP management, LARUS focuses on operational IPv4 services and network continuity.

For organizations evaluating IPv4 buying, selling or transfer processes, i.LEASE provides transaction-focused information and market workflows.

These commercial services are separate from the basic registry function, but they illustrate why modern Internet number resource management increasingly involves technical, administrative and business considerations at the same time.

What Should Businesses Do?

Organizations do not need to become Internet governance specialists to manage Internet number resources responsibly.

A practical starting point is to:

1. Maintain an inventory of important IPv4, IPv6 and ASN resources.
2. Identify the registry relationship associated with each resource.
3. Verify organizational information periodically.
4. Keep administrative and technical contacts current.
5. Understand important resource history, particularly for older IPv4 space.
6. Retain supporting documentation relating to material changes and transactions.
7. Protect registry account access with appropriate security controls.
8. Review routing, DNS, RPKI and other dependencies.
9. Understand applicable administrative procedures before major changes.
10. Include strategically important number resources in business continuity planning.

Where significant financial, contractual or legal questions are involved, organizations should seek technical or professional advice appropriate to their own circumstances.

Final Thoughts

An IP address registry is much more than a searchable list of numbers.

It is part of the coordination infrastructure that helps independent networks use globally unique Internet number resources.

IANA maintains the global top-level registries for IPv4, IPv6 and Autonomous System Numbers, while the five Regional Internet Registries manage, distribute and register Internet number resources within their respective service regions.

For network operators, the most useful principles are straightforward:

Keep resources unique.

Keep records accurate.

Keep administration understandable.

Keep critical functions resilient.

Protect operational continuity.

As businesses become increasingly dependent on stable public network infrastructure, understanding the registry layer becomes part of understanding the infrastructure itself.

The question is no longer only:

Which IP addresses does our organization use?

Businesses should also ask:

Where are those resources registered?

Are the records accurate?

Who controls administrative access?

Which systems and customers depend on those resources?

What documentation do we maintain?

And how prepared are we to preserve network continuity when circumstances change?

The Number Resource Society works to improve understanding of Internet number resources and encourages approaches to governance that support openness, accountability, resilience and decentralization.

Ultimately, the Internet does not require every network to be centrally operated.

It requires independent networks to coordinate reliably.

Accurate, transparent and resilient Internet number resource registration remains an important part of making that possible.