RIPE Database docs
Sidebar Navigation

Introduction to the RIPE Database

RIPE Database Documentation Overview

Intended Audience

Conventions Used in the RIPE Database Documentation

What is the RIPE Database

Purpose and Content of the RIPE Database

History of the RIPE Database

Personal Data Database Management and Reponsabilities

RIPE Database Structure

Database Object

Primary and Secondary Objects

List of Primary Objects

List of Secondary Objects

The Attributes in Database Objects

Attribute Names

Attributes in an Object

Attribute Values

Attribute Properties

How to Organise Your Data

REST API Data model

RPSL Object Types

Descriptions of Primary Objects

Descriptions of Secondary Objects

Available Databases

RIPE Database

TEST Database

Release Candidate Database

Experimental Databases

Update Methods

RESTful API

Webupdates

Syncupdates

Email Updates

Updating Objects in the RIPE Database

Format of the Update Message

Accessing the Object Templates

Object Processing

Update Operations

Historical Data

Special Considerations for Object Creation

Garbage Collection

Dry run

Set Objects

Notifications

Acknowledgment Message

Notification Messages

Authorisation

Authorisation Model

Using the Authorisation Methods

Security of Data Using Authorisation

Protection of PERSON and ROLE Objects

Protection of AUT NUM Object Space

Protection of Address Space

Protection of Route Object Space

Protection of Reverse Delegation Objects

Protection of Objects with Hierarchical Names

Protecting Membership of a Set

Referencing an ORGANIZATION Object

Referencing an IRT Object

IRT Object

Force Delete Functionality

Request ENUM delegation

Request DNSSEC delegation

How to Query the RIPE Database

The Structure of a Query

Web Query Form

RESTful API Queries

Command Line Queries

Query Responses

Registration Data Access Protocol

Access to Personal Data

Types of Queries

Queries Using Primary and Lookup Keys

Queries for IP Networks

Queries for Autonomous Systems

More and Less Specific Lookups For Reverse Domains

Inverse Queries

Abuse Contacts

Grouping the RIPE Database Output

Filtering the Query Reponse

IRR Toolset Support

Persistent Connections and Keeping State

Getting All the Members of Set objects

Access Control for Queries

RIPE NCC Global Resource Service

Other Query Flags

Referenced Objects in Query Response

Historical Queries

Related Software and Tools

Geolocation in the RIPE Database

RIPE Database Mirror

Setup RIPE Database Mirror

Near Real Time Mirroring v3

Near Real Time Mirroring v4

Access to NRTM

Tables of Query Types Supported by the RIPE Database

How to Recover Access to a Maintainer Object

Installation and Development

Getting started on macOS

Getting started on Ubuntu Linux

Building whois

Configure MariaDB

Coding standard

Installation instructions

Database Support

Support Overview

Clean up of Unreferenced Data

Database Security

Configuring Reverse DNS

Database Business Rules

Highlighted Values in the RIPE Database

Create First Role Mntner

Removal of personal data

Release Notes

FAQ

Appendices

Appendix A Syntax of Object Attributes

Appendix B Copyright Statement

Appendix C RIPE Database Query Server Response Codes and Messages

Appendix-D--Route-Object-Creation-Flowchart

Appendix-E--Domain-Object-Creation-Flowchart

Appendix F Special Considerations for Object Types

Appendix G Object Types with Personal Data

Appendix H PGP Authentication Method

Appendix I Client Certificate Authentication

Appendix J Ripe Test Database

Appendix K API Keys

Glossary

Legal Information

RIPE Database Acceptable Use Policy

HTML Terms And Conditions

All Documentation Combined

On this page

Tables of Query Types Supported by the RIPE Database ​

Table 1: Queries Using Primary and Lookup Keys ​

Lookup key(s)Objects Returned
IPv4 address prefix, range or single addressinetnum, route objects with exact match on the specified key. If the exact match does not exist, the objects with the smallest less specific match are returned. When you specify a single address, an inet-rtr object whose "ifaddr:" attribute matches the query argument is also returned..
IPv6 address prefix or single addressinet6num, route6 objects with exact match on a specified key. If the exact match does not exist, the objects with the smallest less specific match are returned. If you specify a single address, an inet-rtr object whose "interface:" attribute matches the query argument is also returned.
Network nameinetnum and inet6num objects whose "netname:" attribute matches the query argument.
AS Numberaut-num object whose "aut-num:" attribute matches the query argument and an as-block object with the range containing the aut-num object, if it exists.
AS Number - AS Numberas-block object whose primary key defines a range that exactly matches or fully contains the range specified in the query argument.
Domain/reverse domaindomain and inet-rtr objects whose primary keys match the query argument.
IRT nameirt object whose primary key matches the query argument.
Person or role nameperson and role objects whose "person:" or "role:" attributes contain the name specified in the query argument.
Set nameA as-set, filter-set, peering-set, route-set or rtr-set whose primary key matches the query argument.
NIC handleperson or role object whose "nic-hdl:" attribute matches the query argument.
Maintainer namemntner object whose primary key matches the query argument.
Organisation nameAll organisation objects with an "org-name:" containing the name specified in the query.
Organisation IDorganisation object whose primary key matches the query argument.
Key-certkey-cert object whose primary key matches the query argument.
Poempoem object whose primary key matches the query argument.
Poetic formpoetic-form object whose primary key matches the query argument.
Route/route6Exact match or less specific route/route6 object and exact match or less specific inetnum/inetnum6 object
Router interface addressinet-rtr with an "ifaddr:" containing the IPv4 or IPv6 address specified in the query
Emailperson, role and organisation objects with a matching "email:"

Table 2: Queries For IP Networks table ​

FlagObjects Returned or Effect
-x
--exact
Only inetnum, inet6num, route, route6 or domain objects that exactly match the prefix. If no exact match is found, no objects are returned.
-M
--all-more
All level more specific inetnum, inet6num, route, route6 or domain objects, excluding exact matches.
-m
--one-more
First level more specific inetnum, inet6num, route or route6 objects, excluding exact matches.
-L
--all-less
All level less specific inetnum, inet6num, route, route6 or domain objects, including exact matches.
-l
--one-less
First level less specific inetnum, inet6num, route, route6 or domain objects, excluding exact matches.
-d
--reverse-domain
When used with -x, -M, -m, -L and -l flags, both address and route object types and domain object types are returned.
-c
--irt
The smallest, less specific inetnum or inet6num object found encompassing the range specified in the query argument. Also any irt objects found referenced from the returned inetnum or inet6num, or referenced from the first less specific inetnum or inet6num to the returned object that has such a reference.
-b
--abuse-contact
Provides a brief output of ranges with associated abuse contact information.

Table 3: Inverse Queries ​

Flag Argument (Alternative Form)Lookup Key(s)Objects Returned
-i am (abuse-mailbox)EmailObjects whose "abuse-mailbox:" attribute matches the query argument.
-i au (abuse-c)NIC handleObjects whose "abuse-c:" attribute matches the query argument.
-i ac (admin-c)NIC handleObjects whose "admin-c:" attributes match the query argument.
-i pc (ping-hdl)NIC handleroute(6) objects whose "ping-hdl:" attribute match the query argument.
-i ah (author)NIC handlepoem object whose "author:" attribute match the query argument.
-i at (auth)PGP keymntner objects whose "auth:" attribute matches the query argument. Please note that encrypted passwords and SSO usernames cannot be inverse- searched, but only PGPKEY and X509 certificates.
-i fp (fingerpr)Fingerprintkey-cert objects whose "fingerpr:" attribute matches the query argument.
-i pn (person)NIC handleObjects whose "admin-c:", "tech-c:", "zone-c:" or "author:" attribute matches the query argument.
-i iy (irt-nfy)Emailirt objects whose "irt-nfy:" attribute matches the query argument.
-i la (local-as)AS Numberinet-rtr objects whose "local-as:" attribute matches the query argument.
-i mi (mnt-irt)IRT nameinetnum and inet6num objects whose "mnt-irt:" attribute matches the query argument.
-i mr (mbrs-by-ref)Maintainer nameSet objects (as-set, route-set and rtr-set) whose "mbrs-by-ref:" attribute matches the query argument.
-i mo (member-of)Set nameObjects whose "member-of:" attribute matches the query argument and their membership claim is validated by the "mbrs-by-ref:" attribute of the set. Absence of the "mbrs-by-ref:" attribute means that the membership is only defined by the "members:" attribute of the set.
-i mb (mnt-by)Maintainer nameObjects whose "mnt-by:" attribute matches the query argument.
-i md (mnt-domains)Maintainer nameObjects whose "mnt-domains:" attribute matches the query argument.
-i ml (mnt-lower)Maintainer nameObjects whose "mnt-lower:" attribute matches the query argument.
-i mn (mnt-nfy)Emailmntner objects whose "mnt-nfy:" attribute matches the query argument.
-i mu (mnt-routes)Maintainer nameaut-num, inetnum, route and route6 objects whose "mnt-routes:" attribute matches the query argument.
-i mz (mnt-ref)Maintainer nameReturns all objects whose "mnt-ref:" attribute matches the query argument.
-i ny (notify)Organisation objects with a matching "ref-nfy:"Objects whose "notify:" attribute matches the query argument.
-i ns (nserver)Domain name or single addressdomain objects whose "nserver:" attribute matches the query argument.
-i or (origin)AS Numberroute and route6 objects whose "origin:" attribute matches the query argument.
-i og (org)Organisation IDObjects whose "organisation:" attribute matches the query argument.
-i tc (tech-c)NIC handleObjects whose "tech-c:" attribute matches the query argument.
-i dt (upd-to)Emailmntner objects whose "upd-to:" attribute matches the query argument.
-i zc (zone-c)NIC handleObjects whose "zone-c:" attribute matches the query argument.
-i rn (ref-nfy)EmailObjects whose "notify" attribute matches the query argument.
-i fr (form)Poetic formPoetic form objects whose matches the query argument.
-i sp (sponsoring-org)Organisation IDObjects whose "sponsoring-org:" attribute matches the query argument.

Table 4: Query Support For Tools ​

FlagLookup Key(s)Effect
-F --briefProduces output using shorthand notation for attribute names. Produces slower responses.
-K --primary- keysRequests that only the primary keys of an object be returned. The exceptions are set objects, where the "members:" attributes will also be returned. This flag does not apply to person and role objects.
-k --persistent- connection(optional normal query)Requests a persistent connection. After returning the result, the connection will not be closed by the server and a client may issue multiple queries on the same connection. The server implements a "stop-and-wait" protocol, whereby no next query can be sent before receiving a reply for the previous one. Use RIPE Whois client to be able to send queries in batch mode. Except the first -k query, -k without an argument closes the persistent connection.

Table 5: Miscellaneous Queries ​

FlagArgumentEffect
-r --no- referencedSwitches off lookups for referenced contact information after retrieving the objects that match the lookup key.
-B --no- filteringSwitches off default filtering of objects.
-G --no- groupingSwitches off grouping of associated objects.
-T --select- typesComma separated list of object types, no white space is allowedRestricts the types of primary objects to lookup in the query.
-a --all- sourcesSpecifies that the server should perform lookups in all available sources. See also -q sources query. `
-s --sourcesComma separated list of sources, no white space is allowed.Specifies which sources are to be looked up when performing a query and in which order.
--list- versions
--diff- versionsVersion numberIndicates the difference between given historical versions of the object.
--show- versionVersion numberReturns the historical version of the object with this index number. Must use --list- versions to get the index numbers.
--typesLists available RPSL object types.
--versionDisplays the current software version.
--list- sourcesReturns the current set of sources along with the information required for mirroring.
--resourceSearch all sources for the specified resource and returns the authoritative one. Placeholders are omitted.
--show- personalInclude referenced person and role objects in results.
--no- personalFilter referenced person and role objects from results. A client can be blocked for excessive querying of these objects.

Table 6: Informational Queries ​

The following notations are used in this table:

<object-type> means full or abbreviated name;

FlagArgumentEffect
-qsourcesReturns the current set of sources along with the information required for mirroring.
-qversionDisplays the current version of the server.
-qtypesA list of all available object types.
-t --templateObject typeRequests a template for the specified object type.
-v --verboseObject typeRequests a verbose template for the specified object type.
-V --clientClient typeSends information about the client to the server.

Last updated:

Pager
Previous pageAccess to NRTM
Next pageHow to Recover Access to a Maintainer Object