rdap.arin.netWhois/Registration Data Access Protocol (RDAP) - American Registry for Internet

Numbers Your IP address is Log in Log in User Dashboard Settings Profile and security information Log Out Search all requests subject to terms of use Search IP Addresses & ASNs Get Started ARIN Account Management Requesting IP Addresses or ASNs IPv6 Information IPv4 Addressing Options Autonomous System Numbers Legacy Resources at ARIN Fee & Billing Information Fee Schedule Premier Support Plan (PSP) Make a Payment How Billing Works Resource Revocation, Returns, and Reinstatement IP & ASN Registry Services Managing Resource Records Transferring IP Addresses & ASNs Reporting Reassignments Autonomous System Originations (Origin AS) Using Whois Resource Management Services Automating Record Management with Reg-RWS Securing DNS (DNSSEC) Routing Security Eligibility FAQs Resource Certification (RPKI) Internet Routing Registry (IRR) Reverse DNS Policy & Participation Policy Number Resource Policy Manual Policy Development Process (PDP) Draft Policies and Proposals Meetings & Events Public Policy and Members Meetings Outreach Events ARIN Fellowship Program Sponsorship Past Meetings Membership & Elections Membership Elections Community Interaction ARIN Community Satisfaction Surveys Mailing Lists Consultations & Suggestions Reference & Tools Tools Operational Test and Evaluation (OT&E) Environment CIDR Calculator Community Software Repository Internet Number Resource Fraud Reporting Reference Spam & Network Abuse Reporting Registry Data Description Data Accuracy Information Security at ARIN ARIN Software Releases Research Statistics & Reporting Historical Whois Data (WhoWas) Bulk Whois Data Training & Education ARIN Leadership Development Program Instructional Webinars Resource Materials ARIN Online Help Videos About Welcome to ARIN Organization Structure & Staff Our Region ARIN Board of Trustees Advisory Council NRO Number Council Careers Corporate Documentation Corporate Documents Annual Reports Strategic Planning & Budgeting Agreements History of ARIN Third-Party Vendors and IPv6 Community Grants ARIN Community Grant Program Community Grant Program Recipients External Relations Internet Governance Memberships, Sponsorships, and MOUs Law Enforcement & Public Safety Technical Community Blog Pay Now Feedback Home IP Addresses & ASNs IP & ASN Registry Services Using Whois Whois/Registration Data Access Protocol (RDAP) Using Whois Whois/Registration Data Access Protocol (RDAP) On this pageLooking for instructions on using ARIN’s Whois/RDAP search? Visit ARIN’s Whois page . Overview Registry Data Access Protocol (RDAP) is a Whois alternative for querying resource registration data from Domain Name Registries (DNRs) and Regional Internet Registries (RIRs) like ARIN. When you use RDAP clients to query registration data, responses are delivered in JavaScript Object Notation (JSON) format (instead of the text format provided by Whois). When you use the Search Site or Whois feature or use https://search.arin.net/rdap/ for Whois queries, RDAP responses are returned in formatted HTML. RDAP works so that it queries additional RIRs and registrars to obtain some information. Other organizations may collect data that ARIN does not, or contain data that is named, formatted, or displayed differently than ARIN’s data. Checking the Source Registry field” or the footer in the search results will help identify the specific RIR or registrar where the data originates and explain differences in content and format. For a full listing of possible results returned in an RDAP query, visit RFC 7483, JSON Responses for the Registration Data Access Protocol (RDAP). How does RDAP differ from Whois? RDAP is an HTTP-based REST-style protocol with standardized responses specified in JSON, whereas Whois is a text based protocol, utilizing a specialized protocol and port. RDAP meets the industry-accepted definition for a web-based RESTful protocol. It serves JSON responses over HTTP/HTTPS using URLs to distinguish various resources. The only HTTP methods used by RDAP are HEAD and GET . RDAP response data objects are easily translated into languages other than English, whereas Whois response data objects may not be. RDAP responses offer direct referrals to other RIRs, whereas Whois defines no queries or responses, and interaction with DNRs and RIRs can vary significantly. Understanding Bootstrapping A bootstrap server is a special type of server for helping clients find an authoritative server to query (this is called bootstrapping). Query bootstrapping can be an expensive process for some clients, and a bootstrap server can alleviate that expense by pre-loading the bootstrapping information. To utilize an RDAP bootstrap server, an RDAP client simply sends RDAP queries and receives HTTP redirects to the authoritative server. Bootstrap files are JSON files specified in RFC 7484 . The Internet Assigned Numbers Authority (IANA) publishes the following files: Autonomous System Numbers IPv4 Allocations IPv6 Allocations Domain Registries If you use the correct query URL in your RDAP query, ARIN’s bootstrap server automatically sends the queries to the correct server. Operating Your Own Bootstrap Server The ARIN bootstrap server is open source and can be found on GitHub . How to Get Registration Information Using RDAP You can use RDAP to get registration information from ARIN using the following methods: Using the Whois/RDAP web interface Using an RDAP client Using Query URLs Using the Whois/RDAP Web Interface You can access the Whois/RDAP web interface by choosing one of these options: Enter https://search.arin.net/rdap/ into the address bar of your web browser. After reaching the ARIN Whois/RDAP page, enter your search term in the field and choose Search . Enter the item you want to search Whois for into the search box (labeled Search Site or Whois ). ARIN sends this query to search.arin.net , and returns results based on what type of search it guesses you were trying to perform. For example, if the search engine thinks you are searching for information about subject areas on the web site (for example, policy, services, or ARIN functions), it returns results from www.arin.net (you can then choose the Search ARIN’s Whois instead link on the results page). If you enter a search term that has a specific format, such as an IP address (for example, 2001:500:11:: ) or an Autonomous System Number (ASN) (for example, AS64496 ), the search engine automatically queries Whois/RDAP. For more information on using the Whois/RDAP web interface, visit the Whois page . Using an RDAP Client ARIN has written a command-line RDAP client called NicInfo . In addition, there are clients available from DNSBelgium , CNNIC , and CentralNIC . RDAP queries are entered with a specific structure. The following examples use the NicInfo client. NicInfo Query Structure The parts of an RDAP query are comprised of the object you are querying and the bootstrap server (optional). For example, to query an object using ARIN’s bootstrap server, you would enter the command: nicinfo object base http://rdap-bootstrap.arin.net/bootstrap/ where object is an IP address, domain name, ASN, or entity identifier. To query an object without using ARIN’s bootstrap server, you would enter: nicinfo object base http://rdap-bootstrap.arin.net/registry/ where object is an IP address, domain name, ASN, or entity identifier. For a specific example, to query an ASN of AS64496, you would enter the following query (using bootstrap): nicinfo asn base http://rdap-bootstrap.arin.net/bootstrap The returned response for a query for AS64496 might look like the following example. Sample Output computer:~ user$ nicinfo AS64496 base http://rdap-bootstrap.arin.net/bootstrap/ # NicInfo v.1.4.1 # Result type is ASNUMBER. [ RESPONSE DATA ] 1= AS64496 `- 1= Internet Assigned Numbers Authority ( IANA ) |- 1= Internet Corporation for Assigned Names and Number ( IANA-ARIN ) `- 2= ICANN ( IANA-IP-ARIN ) [ AS NUMBER ] Handle: AS64496 Start AS Number: 64496 End AS Number:...