WHOIS SEARCH LOGIN TO MYAFRINIC

RDAP

Terms of Use - AFRINIC WHOIS Database

rdapThe Registration Data Access Protocol (RDAP) was designed by the Weirds Working Group of the Internet Engineering Task Force as a successor to the  WHOIS protocol.

RDAP provides a way to query registration data using a RESTful web service and uniform query patterns. The  service is implemented using the Hypertext Transfer Protocol (HTTP)

AFRINIC has an RDAP service available at https://rdap.afrinic.net/rdap

The RDAP protocol addresses the deficiencies with the WHOIS protocol that have been identified over time such as

  • Lack of standardised command structures
  • Lack of standardised output and error structures
  • Lack of support for Internationalization and localization
  • Lack of support for user identification, authentication and access control

The AFRINIC RDAP provides users with an interface to query the following

  • Network information by IP Address
  • AS numbers by autnum
  • Reverse DNS records by the domain
  • Entities (such as persons, roles, organization) by identifier

How to use

How to use AFRINIC RDAP service

IP networks

https://rdap.afrinic.net/rdap/ip//

This query will return the "most-specific" or smallest IP network which completely encompasses it in a hierarchy of IP networks.

For example, the following URL would be used to find information for the most specific network containing 196.1.0.0/24:

https://rdap.afrinic.net/rdap/ip/196.1.0.0/24

The following URL would be used to find information for the most specific network containing 2001:42d0::/32

https://rdap.afrinic.net/rdap/ip/2001:42d0::/32

AS Numbers

https://rdap.afrinic.net/rdap/autnum/

Used to identify autonomous system registrations and associated data referenced, for example, https://rdap.afrinic.net/rdap/autnum/37388

RDNS

https://rdap.afrinic.net/rdap/domain/

Used to identify reverse DNS information and associated data referenced, for example, https://rdap.afrinic.net/rdap/domain/112.192.196.in-addr.arpa

Entity

https://rdap.afrinic.net/rdap/entity/

Used to retrieve entity related information using an entity string identifier.

This can be an org-handle or nic-handle, for Example:

https://rdap.afrinic.net/rdap/entity/TEAM-AFRINIC

https://rdap.afrinic.net/rdap/entity/ORG-AFNC1-AFRINIC

RDAP Client

The NicInfo open source RDAP client developed by ARIN can be used to query RDAP records from the command line.

Out of Region Query

Out of region internet resource query

When the AFRINIC RDAP server encounters a query involving an internet resource that does not belong to the AFRINIC region, it responds with  HTTP status code 301, and "Location" header pointing to the correct RDAP resource

Example of an IP resource 198.0.0.0 that belongs to the ARIN region  https://rdap.afrinic.net/rdap/ip/198.0.0.0

Below is extract of the HTTP response HTTP/1.1 301 Moved Permanently Date: Wed, 15 May 2019 08:10:20 GMT Server: AfriNIC RDAP Access-Control-Allow-Origin: * Content-Type: application/rdap+json; charset=UTF-8 Location: https://rdap.arin.net/registry/ip/198.0.0.0

Reference

RFCs we have Implemented

RDAP is specified in a series of Internet Request for Comments (RFC) documents.

  1. RFC 7480 - HTTP Usage in the Registration Data Access Protocol (RDAP)
  2. RFC 7481 - Security Services for the Registration Data Access Protocol (RDAP)
  3. RFC 7482 - Registration Data Access Protocol (RDAP) Query Format
  4. RFC 7483 - JSON Responses for the Registration Data Access Protocol (RDAP)
  5. RFC 7484 - Finding the Authoritative Registration Data (RDAP) Service
  6. RFC 7485 - Inventory and Analysis of WHOIS Registration Objects

RDAP Implementation from other RIRs