What is RDRS (Registration Data Request Service)?
The RDRS (Registration Data Request Service) is an ICANN-operated channel through which authorized parties – including intellectual property professionals and law enforcement – may submit formal requests to participating registrars for non-public domain registration data that is no longer visible in standard RDAP or WHOIS lookups.
Since 28 January 2025, registrars are no longer required to operate a public WHOIS service; RDAP (the Registration Data Access Protocol) replaced it as the standard lookup. For individuals, RDAP typically returns redacted records. The RDRS is the formal route to request the underlying data – the registrant name, email, and contact details – from registrars that participate. Disclosure is not automatic: each registrar assesses the request independently, and the response timeline is outside the requester's control.
This page explains precisely what RDRS is, where it sits in the rules, the patterns in which it matters most, and why it is not the same thing as a subpoena or a formal discovery order.
What RDRS is – and what it is not
The RDRS is a structured intake form, not a legal instrument. Submitting a request through ICANN's RDRS portal asks a participating registrar whether it will voluntarily disclose non-public registration data for a named domain. The registrar may disclose, decline, or ask for additional justification. It has no obligation to respond within any set deadline, and ICANN does not adjudicate the request.
The term readers most often confuse RDRS with is RDAP – the Registration Data Access Protocol. RDAP is the technical protocol that replaced WHOIS as the query mechanism for publicly available registration data. RDRS, by contrast, is the procedural channel for requesting data that RDAP deliberately withholds. They are complementary, not interchangeable. A practitioner's first step is always an RDAP lookup; RDRS comes into play only when that lookup returns a redacted or privacy-protected record.
RDRS also differs from a court-ordered subpoena or a pre-action disclosure order. A subpoena compels production. RDRS requests it. Where identification of a registrant is essential to litigation – for example, a US anticybersquatting action against a John Doe defendant – a court order remains the only mechanism that compels the registrar to produce what RDRS may not.
Where RDRS comes from in the rules
The legal backdrop is ICANN's long-running effort to reconcile registrar data obligations with data-protection law. Following the enforcement of the EU General Data Protection Regulation, ICANN developed a Temporary Specification for gTLD Registration Data that effectively mandated redaction of personal data for individual registrants. WHOIS – once the universal public registry for registrant identity – became largely opaque for natural persons.
ICANN launched the RDRS as a pilot to test a standardized, privacy-compliant channel for legitimate access requests. ICANN announced on 20 November 2025 that the pilot was extended beyond its original two-year term while next steps are decided; the current status should be confirmed before relying on it for a live matter. Participation by registrars remains voluntary at the pilot stage, meaning coverage is uneven across the market. Not every registrar accepts RDRS requests, and some of the largest registrars by domain count have their own disclosure-request workflows that sit outside the ICANN portal.
The operative consequence for a dispute practitioner is this: identifying a registrant behind a privacy screen now routinely requires an RDAP lookup to establish what is publicly available, an RDRS request to the relevant registrar for the underlying data, and – where the registrar declines or does not respond – a court order or formal legal process to compel disclosure.
How RDRS plays out in practice
Three patterns recur in our practice when clients need registration data to advance a dispute or theft claim.
Pattern one – UDRP pre-filing identification. A brand owner runs an RDAP lookup on a cybersquatted .com and receives a redacted record showing only the registrar's name and the registration date. To build the UDRP complaint, the owner needs to name the registrant. In many cases the complaint can proceed on the basis that the registrant is the person or entity who registered the domain, even without a confirmed identity – panels accept that fact. But where the complainant wants to identify related registrations or a pattern of abusive conduct across multiple domains, knowing the underlying registrant data matters. RDRS is the first port of call before the complaint is filed.
Pattern two – domain theft response. A registrant wakes to find that the registration record for a domain has changed – the registrar contact email has been replaced, and the domain is no longer under the account holder's control. This is the situation our clients find most alarming: the domain has effectively been stolen. Identifying who now controls the record requires an RDAP lookup on the current record, followed, if the new registrant contact is redacted, by an RDRS request, and in parallel an immediate escalation to the registrar's abuse team to invoke a registrar lock and preserve the chain of custody. Time is critical. In a recent matter – a .com domain theft, spring 2026 – the account compromise was confirmed within hours and a lock placed before the domain was transferred to a second registrar, preserving the basis for transfer reversal.
Pattern three – litigation prerequisite. A US anticybersquatting action names an unknown defendant. Counsel files a John Doe complaint, obtains a court order directing the registrar to produce the registrant's contact information, and substitutes the named defendant once disclosure is made. The RDRS step, if attempted first, can sometimes produce voluntary disclosure quickly enough to avoid the cost of a formal court order. Where the registrar participates and responds promptly, RDRS materially reduces the cost of litigation. Where it does not, the court order remains the only path.
Why RDRS matters to a brand owner or registrant
For a brand owner, RDRS is the first non-litigious step toward identifying the person behind an anonymous registration. Before the privacy redaction era, a WHOIS lookup could name a registrant in seconds. Today that same lookup returns a proxy or a redacted field. The RDRS does not restore that speed – disclosure depends on the registrar's participation and internal review – but it provides a structured, documented request that can be presented to a court as evidence that the party attempted voluntary disclosure first.
For a domain theft victim, the RDRS is one element of an immediate-response protocol. It does not substitute for a registrar-abuse escalation or a court order. Its practical value is in parallel: a disclosure request through RDRS, combined with a formal abuse report to the registrar and a registrar lock request, creates a documented record of the response that supports a subsequent transfer-reversal claim.
A common myth worth correcting here: some brand owners assume that a court action is always faster than an arbitral route. In most domain disputes that assumption is wrong. A UDRP complaint before WIPO or the Forum normally resolves in about two months. A court action, even an anticybersquatting case, routinely takes considerably longer and costs considerably more. The RDRS sits upstream of both: getting the registrant's identity confirmed before choosing a route avoids the risk of filing a complaint against the wrong party or in the wrong forum.
COGNOMEN focuses only on domain-name disputes – recovery, defense, and transactions. We regularly advise registrants and brand owners who discover that the first obstacle is not the dispute itself but identifying who they are disputing against. For an assessment of your registration data situation or a domain dispute, contact info@cognomenlaw.com.
Related at COGNOMEN
Frequently asked questions
What is RDRS (Registration Data Request Service)?
The RDRS is an ICANN-operated portal through which authorized parties may request non-public domain registration data – such as the registrant's name and contact email – from participating registrars. Since January 2025, most registration data for individual registrants is redacted under RDAP, making RDRS the primary structured channel for legitimate disclosure requests. Disclosure is voluntary on the registrar's part and is not guaranteed. The pilot was extended by ICANN in November 2025 while next steps are determined.
How is an RDRS request made and what does it produce?
A requester submits a request through ICANN's RDRS portal, identifying the domain and the legal basis for the request – such as an intellectual property dispute or a fraud investigation. The relevant registrar then reviews the request independently and may disclose, decline, or seek further information. There is no set response deadline. If the registrar declines or does not respond, the requester must pursue the data through a court order or formal legal process. RDRS is a first step, not a guarantee of access.
Why does RDRS matter to my domain dispute or theft claim?
Identifying the registrant behind a privacy-protected record is often the first practical obstacle in a UDRP complaint, a domain theft response, or an anticybersquatting court action. The RDRS provides a structured, documented route to request that data from the registrar without immediately resorting to litigation. A successful RDRS disclosure can accelerate the entire dispute process and reduce legal costs. Where it fails, the documented request itself supports the case for a court-ordered disclosure.
Author: Adrian Harland — Court anticybersquatting and domain theft recovery. Meet the team.
Speak with Cognomen Law
For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.