Requesting non-public registration data through RDRS

On 28 January 2025, ICANN formally retired the WHOIS protocol as a mandatory registrar obligation, making RDAP – the Registration Data Access Protocol – the authoritative source for domain registration data. That change matters immediately for anyone trying to identify the person behind a domain: a parked page, a phishing site, a name that stopped resolving after an unauthorized transfer, or a typosquat mimicking your brand.

ICANN's Registration Data Request Service (RDRS) is the designated channel for requesting non-public registrant information from participating registrars. Participation by registrars is voluntary, and disclosure of any requested data remains at each registrar's discretion. The pilot was extended beyond its original two-year window; as of October 1, 2026, the RDRS remains operational while ICANN decides next steps – verify the current status before relying on it.

This page explains what the RDRS is, who can use it, how to build a request that stands a reasonable chance of being answered, and what the practical limits are for domain disputes and recovery matters.

What did ICANN change, and when did it take effect?

The retirement of mandatory WHOIS and the elevation of RDAP took effect on 28 January 2025. Before that date, accredited registrars were required to operate a publicly queryable WHOIS service. After it, the obligation shifted: registrars must provide registration data through RDAP, but personal data for individual registrants is redacted by default under applicable data-protection law. The result is that a standard RDAP lookup now returns a technical record – nameservers, status flags, registration and expiry dates – but frequently omits the registrant's name, organization, email address, and phone number.

The RDRS was introduced as the bridge between that redaction regime and the legitimate need of brand owners, domain dispute practitioners, and law enforcement to identify registrants. It is not a replacement for legal process. It is a facilitated request mechanism sitting on top of registrar discretion.

How does the RDRS work in practice?

A requestor creates an ICANN-managed account, submits a structured request identifying the domain and the legal basis for the disclosure need, and the request is routed to the registrar of record. The registrar then decides whether to disclose, partially disclose, or decline. There is no fixed response deadline enforced by ICANN. The registrar's decision is final at the RDRS level – the RDRS does not adjudicate disputes about registrar non-responses.

Two structural facts shape every RDRS request. First, registrar participation is voluntary. A significant number of registrars have joined, but not all; if the registrar for your target domain has not enrolled, the RDRS route is simply unavailable. Second, even a participating registrar retains full discretion. A well-formed request improves the odds of a response, but nothing compels disclosure short of a court order or a formal legal process compelling the registrar.

In our practice handling domain theft and recovery matters, the RDRS functions best as a first-pass tool to be filed promptly after a dispute surfaces, in parallel with – not instead of – the other identification routes. Where a domain was transferred without authorization or is being used in a phishing campaign, a well-documented RDRS submission often produces a faster initial result than opening formal proceedings with no registrant identity in hand.

What makes an RDRS request more likely to receive a substantive response?

Registrars reviewing RDRS requests apply their own internal standards. No published uniform criteria exist. That said, consistent patterns emerge from the requests that produce results and those that do not.

A request that clearly states the legal basis – an active or anticipated UDRP complaint, a domain theft, a court matter, an intellectual-property dispute – receives more attention than a generic inquiry. Specificity about the harm matters: a request that explains why the identity of this registrant is necessary to advance this legal process, and attaches supporting documentation such as a trademark registration certificate, screenshots of the disputed use, or a prior RDAP lookup showing redacted fields, gives the reviewer the context to justify an internal disclosure decision.

Requests that read as fishing expeditions, or that omit a stated legal purpose, are routinely declined. The registrar's compliance team must be able to document why disclosure was appropriate; your request needs to supply that rationale.

If you are trying to identify a registrant to support a UDRP filing or a recovery action after domain theft, reach us at info@cognomenlaw.com before submitting the RDRS request. A correctly framed submission, filed at the right moment in the dispute timeline, is more likely to produce a result.

What are the limits of the RDRS for domain disputes?

The RDRS is not a dispute-resolution mechanism. It does not transfer a domain, suspend it, or impose any obligation on the registrant. Even full disclosure of registration data does not by itself create a right to recover the name. What it does is give you an identity – a starting point for a UDRP complaint, a court filing, or a demand letter.

Several limits are worth stating plainly. Non-participating registrars are unreachable through this channel. Participating registrars are not required to respond within any specified window, and delays of weeks are common. Disclosure is not guaranteed even where the request is well-founded. And data obtained through the RDRS may need to be independently verified before use in formal proceedings, because the registrar is not acting as a source of certified record evidence.

There is also the question of what happens when the RDRS does not work. A registrar that declines to disclose and sits outside the reach of ICANN contractual enforcement may still be subject to a court subpoena or equivalent compelled-disclosure process in its home jurisdiction. That is a different tool entirely, and one that typically requires local litigation counsel in the relevant jurisdiction.

A separate misconception worth addressing: some brand owners assume a court action is always faster than arbitration for domain recovery. For most gTLD disputes, the opposite is true. A UDRP complaint at WIPO or the Forum resolves in roughly two months, with a filing fee starting at USD 1,500 for a single-member panel. Court proceedings in most jurisdictions take considerably longer and cost substantially more. The RDRS fits into the UDRP path efficiently; it fits into the court path as an early preservation step while the substantive litigation proceeds.

How does the RDRS interact with DNS abuse reporting?

Since 5 April 2024, amendments to ICANN's Registrar Accreditation Agreement impose a duty on registrars to take prompt, reasonable action to stop or disrupt defined DNS abuse – malware, botnets, phishing, pharming, and spam used as a delivery vector for those four. That obligation is a mitigation duty, not a rights-adjudication mechanism. A registrar that receives a well-documented DNS-abuse report may act on it without identifying the registrant to you. The RDRS and the DNS-abuse track therefore serve different needs and should not be conflated.

Where a domain is both a cybersquatting target and a technical abuse vector – a phishing site using a typosquat of your brand, for instance – it makes sense to pursue both channels simultaneously. The DNS-abuse report may result in the domain being suspended at the registrar level; the RDRS request may produce the registrant identity needed to file a formal UDRP complaint or pursue recovery in court. Neither replaces the other.

To weigh UDRP against a court action for your case, or to plan an RDRS submission as part of a broader recovery strategy, email info@cognomenlaw.com.

What should practitioners and brand owners do now?

Three steps apply immediately to anyone facing an identity-gap in a domain dispute. Check first whether the registrar of the disputed domain participates in the RDRS; this can be confirmed through the ICANN RDRS portal. If it does, prepare a structured request with a stated legal basis and supporting documentation before filing anything formal – obtaining registration data early in the process avoids the delay of trying to identify the registrant mid-proceedings.

If the registrar does not participate, or if a well-formed RDRS request goes unanswered, the options move to compelled disclosure through formal legal process – a subpoena in the registrar's home jurisdiction, or a request through applicable cross-border data-sharing channels. Both require case-specific legal advice and, for registrars based outside your jurisdiction, local litigation counsel.

Finally, document your RDRS submission and any response or non-response. In a subsequent UDRP or court proceeding, the record of your good-faith attempt to identify the registrant through official channels is often relevant to showing you acted promptly and through proper means.

COGNOMEN focuses only on domain-name disputes – recovery, defense, and transactions. We handle Court Action & Domain Theft matters across gTLDs and ccTLDs, and we regularly advise brand owners and registrants on how to build the evidentiary record before and during formal proceedings. For an assessment of your domain dispute, contact info@cognomenlaw.com.

Related at COGNOMEN

• court recovery – the full menu of recovery routes across gTLDs and ccTLDs
• DNS abuse obligations: what changed on 5 April 2024 – how the 2024 registrar amendments affect enforcement
• registrar lock escalation ca – escalating a registrar lock when a domain transfer is unauthorized

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.