Making Resource Holders Easier to Identify: Introducing reg-nr: in the RIPE Database

For nearly 30 years, the RIPE Database has evolved alongside the Internet itself. What began as a practical tool for network engineers to find contact details and troubleshoot operational issues has gradually developed into an authoritative source for Internet number resources and the organisations that hold them.

As part of this evolution, the focus of the RIPE Database has shifted towards greater clarity and reliability. Identifying the holder of each resource managed by the RIPE NCC is now a key function. With the introduction of a new attribute, reg-nr:, we are taking another step towards that goal.

From names to unique identification

For several years, organisation objects linked to RIPE NCC-managed resources have included the full legal name of the resource holder as well as the country of registration. This provides a solid basis for identifying an organisation.

However, in practice, this information is not always unambiguous. Companies may share the same or very similar names, especially in jurisdictions where registration is handled regionally. Identifying the correct legal entity can therefore require additional effort and external checks.

The new reg-nr: attribute addresses this challenge by introducing a unique and verifiable identifier: the official company registration number issued by a national or regional authority. This directly identifies the legal entity behind a resource and makes it easier to distinguish between organisations with similar or identical names.

From internal data to public value

The RIPE NCC has long maintained registration numbers in its internal systems as part of due diligence processes. With the approval of Numbered Work Item 21 (NWI-21) by the Database Working Group, these identifiers are now being published in the RIPE Database where applicable.

Users can now access this verified information directly, rather than relying only on names and country codes.

At the time of writing, more than 32,000 organisation objects include a unique reg-nr: value. These cover around 18,000 RIPE NCC members and 14,000 sponsored end users who are legal organisations across more than 130 economies. The numbers are published in their original national formats, which vary significantly between countries. Some are simple numeric identifiers, while others include letters or additional qualifiers such as regional or state information.

Ensuring accuracy and trust

A key design principle is reliability. The reg-nr: attribute is only added to organisation objects co-maintained by the RIPE NCC, where core details such as name, country, and registration number are verified.

As with other verified data, updates to these fields require proper validation by the RIPE NCC. This ensures that the information published in the database remains accurate and prevents the introduction of unverified or incorrect registration numbers.

Organisation objects can still be created by anyone. However, the reg-nr: attribute is only added once an object is linked to RIPE NCC–managed resources and has been verified.

Not all organisation objects will include a registration number. Where no public identifier exists, for example, in the case of natural persons or certain public bodies, the attribute is set to “not applicable”. We will also not publish registration numbers for sole traders and their registered businesses. While such entities may have an official registration number in some jurisdictions, Internet number resources are typically registered to the natural person behind the business. No personal identifiers or non-public data are published.

Making the most of reg-nr:

The addition of reg-nr: makes it easier to connect RIPE Database information with official company registries. By combining the registration number with the country code, users can reliably identify the correct registry and obtain further information about a resource holder where needed.

This can be useful in a wide range of scenarios, from administrative processes to due diligence activities.

Before publishing this data, the RIPE NCC carried out a comprehensive review of tens of thousands of registration numbers in its records. As much of this information was originally entered manually over many years, there may still be occasional inconsistencies. If you come across information that appears incorrect or incomplete, please let us know by emailing ripe-dbm@ripe.net, so we can further improve the dataset.

Why not link directly to company registries?

During the working group discussions leading up to this implementation, there were suggestions to include direct links to national company registries. While this would be a valuable addition, it is also challenging to implement in a reliable way.

Company registries differ widely across countries. In addition, registry platforms and URLs can change over time, which would require continuous maintenance.

For now, providing the registration number together with the country code of legal registration already enables users to locate the relevant registry with confidence, if needed, with some professional support in the country of legal registration. We will continue to explore whether additional support in this area can be provided in a sustainable way.

A collaborative step forward

The introduction of the reg-nr: attribute is a good example of how ideas from the RIPE community can quickly translate into practical improvements. The concept was presented at RIPE 91, discussed within the Database Working Group, and implemented within a relatively short time frame.

By adding a simple but powerful piece of information, we are making the RIPE Database more precise, more reliable, and more useful for everyone who depends on it.

As always, we welcome your feedback and look forward to continuing to improve the quality and usability of registry data together.