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

Web Query Form ​

The web query form is available at: https://apps.db.ripe.net/.

This is part of the RIPE Database web interface that also includes Webupdates.

The query argument is entered into the form. Many of the query flags can be selected with check boxes. The database source can also be selected this way. If you know the query flags you want, you can also type them into the form with the query argument.

Using Full Text Search ​

If you are looking for a specific piece of information and you don't know one of the values required to find what you are looking for, you may consider using the Full Text Search instead of doing a standard query. Full Text Search treats the entire database as a flat text file and allows you to search for anything. The search is done on object text without regard for any relationships. As such, results may be very unstructured, but it can provide a good starting point for more specific standard queries later on. Keep in mind that Full Text Search is only available on the RIPE NCC website and not in other methods to query the RIPE Database.

Personal data may be returned by the Full Text search API. You may be blocked if excessive amounts of personal data is returned. For more information refer to blocking access section

URI Format: /fulltextsearch/select?... ​

Query Parameters ​

nameDefaultdescription
qThis parameter is used to specify the query for requesting documents. This query allows to filter by the attribute type and/or the object type. This parameter is required.
  • Query for "RIPE": q=(RIPE)
  • Query for "RIPE", filtering by attribute type: q=(org:(RIPE))
  • Query for "RIPE", filtering by object type: q=(RIPE)%20AND%20(object-type:mntner)
  • Query for "RIPE", filtering by attribute and object type: q=(org:(RIPE))%20AND%20(object-type:mntner)
  • Logic expressions are allowed to concatenate more than one term:
    • Querying by "RIPE" and "NCC": q=(RIPE%20AND%20NCC)
    • Querying by "RIPE" or "NCC": q=(RIPE%20OR%20NCC)
    • Querying by "RIPE NCC": q=(%22RIPE%20NCC%22)
    • Querying by "RIPE", filtering by multiple attributes and object types: q=(e-mail:(RIPE)%20OR%20org:(RIPE))%20AND%20(object-type:organisation%20OR%20object-type:person)
    • Keywords: Using "AND," "OR," or "NOT" as a query term is not permitted.
rows10The amount of documents to return. The maximum value is 10,000
start0The starting row. The maximum value is 100,000
hlfalseHighlight the matching values from the fetching documents.
hl.simple.pre<b>The highlight PRE value.
ht.simple.post</b>The highlight POST value.
wtxmlThe format of the highlights. If the format is not xml "hl.simple.pre" and "hl.simple.post" will be discarded.
facettrueCount the object types.

There are some limitations to take care on:

  • Not allowed to fetch more than 10,000 documents per request.
  • There is a maximum of 100,000 results per query (with paging).
  • The maximum highlight characters is trimmed to 100,000 characters.

The possible values that you can specify for the Accept/Content-Type header are:

  • application/xml for XML
  • application/json for JSON

Clients can also append an extension of .xml or .json to the request URL instead of setting an Accept: header. The server will return a response in the appropriate format for that given extension. XML format is the default one.

Last updated:

Pager
Previous pageThe Structure of a Query
Next pageRESTful API Queries