RFC 9224: Finding the Authoritative Registration Data Access Protocol (RDAP) Service
In plain English — editorial summary, not part of the RFC
This document specifies a method to find which Registration Data Access Protocol (RDAP) server is authoritative to answer queries for a requested scope, such as domain names, IP addresses, or Autonomous System numbers. This document obsoletes RFC 7484.
Document record
- Document ID
- RFC9224
- Published
- March 2022
- Authors
- M. Blanchet
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 15
- Also known as
- STD95
- Obsoletes:
- RFC 7484
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8305Happy Eyeballs Version 2: Better Connectivity Using ConcurrencyCurrent
December 2017
- RFC 7984Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP NetworkCurrent
September 2016
- RFC 6535Dual-Stack Hosts Using "Bump-in-the-Host" (BIH)Current
February 2012
- RFC 8994An Autonomic Control Plane (ACP)Current
May 2021
- RFC 10001Operational Guidelines for DNS Transport in Mixed IPv4/IPv6 EnvironmentsCurrent
August 2026
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 3574Transition Scenarios for 3GPP NetworksCurrent
August 2003
- RFC 3056Connection of IPv6 Domains via IPv4 CloudsCurrent
February 2001
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?