Skip to main content

RIPE Database

The RIPE Database is a database that contains information about IP addresses and autonomous system numbers (ASNs), and related resources within the RIPE NCC service region. It includes public data such as contact information for who is responsible for IP addresses and ASNs, how these resources are being used, and provides routing information. The database allows resource holders to maintain their data in the database.

The RIPE NCC has been tasked by the RIPE community to maintain this database of Internet resource information. The details in the RIPE Database are maintained jointly by the RIPE NCC and resource holders. The database is essential for maintaining the stability and security of the Internet. By providing accurate and up-to-date information about IP addresses and ASNs, it ensures that network operators can collaborate effectively, solve problems quickly, and keep the Internet running smoothly.

Here are the key features of the RIPE Database:

  • IP Address and ASN Registration: It records the allocations and assignments of IP address blocks and ASNs, which are unique identifiers for networks on the Internet. This ensures that there is no duplication or overlap of these resources.
  • Network Operator Information: It includes contact details and other relevant information about network operators and organisations that have been assigned IP resources. This is useful for operational purposes, such as resolving network issues or abuse complaints.
  • Routing Policy Information: Network operators can use the database to document their routing policies and interconnections with other networks. This information helps in the configuration and optimisation of routing on the Internet.
  • Geolocation: The database provides information that can be used to determine the geographical location of IP addresses, which can be useful for various purposes, such as network optimisation and content delivery.
  • Public Access: The database is publicly accessible, allowing anyone to query it to obtain information about IP addresses and ASNs. This transparency helps maintain the integrity and stability of the Internet.
  • Abuse Management: The database includes information about abuse contacts, which can be used to report issues such as spam or other forms of network abuse.
  • Policy enforcement: by maintaining accurate records in the RIPE Database, the RIPE NCC ensures that Internet number resources are used efficiently and in accordance with community-agreed policies. This transparency promotes trust and integrity in the way Internet resources are managed.

The RIPE Database contains records of:

  • Allocations and assignments of IP address space (the IP address registry or INR);
  • Reverse domain registrations;
  • Routing policy information (the Internet Routing Registry or IRR);
  • Contact information (details of people who are registered as contacts for the Internet resources used in the operation of networks or routers, and their organisations).

How to search the RIPE Database

Accessible through a user-friendly web interface and various command-line tools, the RIPE Database supports a wide range of users.

Here’s a guide on how to effectively use the RIPE Database to access and manage information about IP addresses, Autonomous System (AS) numbers, and other related data.

You can access the RIPE Database through the following methods:

Web Interface:

  • Visit the RIPE Database web interface.
  • Use the search bar to enter an IP address, AS number, or organisation name to find specific information.
  • The web interface provides a user-friendly way to query the database and view results in a clear format.

Command-Line Tools:

  • For more advanced users, the RIPE Database can be queried using command-line tools such as whois.
  • Use the following syntax to query the database:
RIPE DB command
  • Replace <query> with the specific IP

RIPE Database Records: Objects

The records in the RIPE Database are known as ‘objects'. The RIPE Database contains various objects, each representing different types of information related to Internet number resources. Objects in the RIPE Database fall into two categories, primary and secondary:

  • Primary objects contain operational data. For example inetnum and aut-num objects hold Internet resource information. Also, route and domain objects hold details of routing agreements and reverse delegations.
  • Secondary objects provide supporting and administrative details for primary objects. For example, person objects hold contact information for someone related to an Internet resource. Or organisation objects hold details of resource holders.

Here's an explanation of the key objects you might encounter:

  1. inetnum
  • Purpose: Represents an IPv4 address range.
  1. inet6num
  • Purpose: Represents an IPv6 address range.
  1. aut-num
  • Purpose: Represents an Autonomous System (AS) number.
  1. person
  • Purpose: Represents an individual contact person.
  1. role
  • Purpose: Represents a role performed by one or more individuals, such as a help desk or network operations centre.
  1. mntner
  • Purpose: Represents a maintainer, which is used to protect objects in the database from unauthorised changes.
  1. organisation
  • Purpose: Represents an organisation that holds Internet number resources.
  1. domain
  • Purpose: Represents a reverse DNS zone.
  1. irt
  • Purpose: Represents an Incident Response Team.

Making Updates in the RIPE Database

Updating your details in the RIPE Database is a straightforward process, but it requires proper authentication to ensure the accuracy and security of the information.

Making updates using the RIPE Database web interface

Here are the steps to update your details:

  1. Go to the RIPE Database web interface.
  2. Log in using your RIPE NCC Access account. If you do not have an account, you will need to create one.
  3. Locate the Object to Update. Use the search functionality to find the object you want to update (e.g., an inetnum, person, or organisation object). Enter relevant search criteria such as the IP address, AS number, or contact name.
  4. Once you locate the object, click on it to view its details. Click the “Update” button to make changes. This will open the object in an editable format.
  5. Update the necessary fields with the new information. For example:
  • For a person object, you might update the phone or email fields.
  • For an organisation object, you might update the address or admin-c fields.
  • Ensure that you do not alter any critical fields that you are not authorised to change.
  1. Before you can submit changes, you need to authenticate as a maintainer. This is usually done through maintainer (mntner) objects.
  2. Once you have made the necessary changes and provided the required authorisation, submit the update.

The system will validate the changes and, if everything is correct, the object will be updated in the database.

  1. After submitting the changes, you will receive a confirmation email indicating that the update has been processed. It is good practice to review the updated object to ensure that all changes have been applied correctly.

Using the Command-Line Interface

Alternatively, if you prefer to use the command-line interface (CLI), you can update objects using the whois tool. Here’s how:

  1. Query using the REST API or web application to retrieve the full maintainer object.

csharp
Copy code: whois -h whois.ripe.net <object-ID> > object.txt

Include the "-B" or "--unfiltered" flag to return the complete unfiltered object that can be updated.

Replace <object-ID> with the ID of the object you want to update (e.g., a specific IP address or person handle).

  1. Edit the Object. Open the object.txt file in a text editor and make the necessary changes.
  2. Add Authorisation

Ensure that the maintainer (mntner) authorisation details are included in the file. This usually involves adding an auth line with your API key or PGP key.

  1. Submit the updated object to the RIPE Database. You can send the modified object file by email to auto-dbm@ripe.net, but email should only be used if the request is authenticated with PGP or X.509 (S/MIME). If you are using API keys, submit the request over HTTPS instead, using either the REST API or Syncupdates.

Important Considerations

  • Accuracy: Ensure that all changes are accurate and reflect the correct information.
  • Authorisation: Only authorised individuals should make updates to prevent unauthorised changes.
  • Compliance: Adhere to RIPE NCC policies and guidelines when making updates.

History

From the very first RIPE Meeting in 1989, the need for some sort of registry was identified. In the early years of RIPE, this consisted of documenting the use of IPv4 address space in the RIPE region on a voluntary basis. The actual address space was not distributed by RIPE.

From August 1992, the newly established RIPE NCC started distributing address space in its service region. The RIPE Database was launched to document these IP address allocations and ASNs within the RIPE NCC service region. Allocations made by the RIPE NCC have always been documented in the registry by the RIPE NCC and the Local Internet Registries (LIRs).

The RIPE Database holds data for three separate registries:

  • RIPE Internet Number Registry (RIPE INR)
  • RIPE Internet Routing Registry (RIPE IRR)
  • Reverse Delegation and ENUM Registry

These could be three independent databases, however the information in each of them is related to each other. It was therefore decided to integrate the three registries into one logical database. In practice, it is also one physical database.

The database evolved to include contact details for troubleshooting and handling abuse reports. It became part of the global Internet governance ecosystem, integrating with other Regional Internet Registries (RIRs) and their databases. In the 2000s, new features were added, such as support for routing information through the RIPE Internet Routing Registry (IRR).

Today, the RIPE Database is a cornerstone of the Internet's infrastructure, enabling efficient network management and fostering trust and accountability in the global Internet community.

Its development is guided by the RIPE community through the Database Working Group, which discusses changes to objects, new features, data distribution, and security related to the RIPE Database.