Registrar practice after a UDRP decision
As of October 27, 2026, the step that closes most domain disputes – registrar implementation of a UDRP transfer or cancellation order – remains largely invisible to parties who have never run one before. A panel issues its decision. The registrar receives it. The domain moves. But the mechanics between those moments involve a defined waiting period, a court-challenge window that can pause everything, and – less often than it should be – a registrar that simply does not act on time.
After a UDRP panel orders a transfer or cancellation, the registrar is required to implement that decision after a 10-business-day waiting period during which the losing respondent may seek relief from a court of competent jurisdiction. If court proceedings are filed and notified to the registrar within that window, implementation is paused pending the court's outcome. If no court action is filed, the registrar implements the decision – transferring or canceling the domain – at the end of the period. The process is governed by the UDRP and the registrar's accreditation obligations under ICANN.
This page explains what happens step by step after a decision issues, what triggers the pause, and what a winning complainant – or a respondent facing an adverse order – should do if the registrar falls silent.
What the UDRP rules require registrars to do
The UDRP is not self-executing. A panel has no enforcement arm. Its decision is relayed to the registrar through the administering forum – WIPO, the Forum, CAC, or ADNDRC – and the registrar is then contractually bound, under its ICANN accreditation, to carry that decision out. That contractual obligation is what makes the system work without a court order.
Specifically, the registrar must wait out the 10-business-day period – often described in forum communications as the "lock period" – before effecting any transfer or cancellation. During that time the domain stays registered in the respondent's name but is typically locked to prevent any outgoing transfer. The registrar notifies both parties of the decision and of the deadline. If the window closes without court proceedings, the registrar carries out the instruction. No further direction from the complainant is needed at that stage.
It is worth noting what the registrar does not do during this process: it does not evaluate the merits of the panel's decision, it does not re-examine the evidence, and it does not adjudicate any dispute between the parties. Its role is ministerial. The substance was decided by the panel; implementation is mechanical. That is a feature of the system, not a gap in it.
What is the 10-business-day court-challenge window?
The court-challenge window is the UDRP's built-in safety valve for respondents who believe the panel erred. It exists because the UDRP is a contractual arbitration procedure, not a judicial proceeding – and the parties' agreement to it does not strip them of the right to litigate the underlying dispute in a court of competent jurisdiction.
If a respondent files a court action within those 10 business days and notifies the registrar of the filing, the registrar is required to suspend implementation until the court proceedings are resolved or the court directs otherwise. The notification must be prompt – a court action filed in time but not communicated to the registrar before the deadline may not achieve the pause. In our practice, we have seen registrars implement a decision where the respondent filed proceedings but notified the wrong contact address; the domain moved before the registrar's compliance team became aware of the filing.
What courts are competent? The UDRP does not designate a specific jurisdiction; it requires that the court have jurisdiction over the domain and the parties. For a .com domain, US district courts regularly hear these actions under US anticybersquatting legislation, though the parties may agree on other forums. For ccTLDs, national courts in the registry's home jurisdiction often have jurisdiction by default. Any respondent considering this route should consult local litigation counsel in the relevant jurisdiction without delay – 10 business days goes quickly.
If you have received an adverse UDRP decision and are weighing whether to seek court relief within the challenge window, reach us at info@cognomenlaw.com for an assessment of whether and where a court action is available.
What can delay or block implementation after the window closes?
Implementation should be straightforward once the court-challenge window expires without a filed action. In practice, delays occur. A registrar's compliance workflow may queue transfer orders behind volume. The forum's notification may reach a technical mailbox rather than the compliance team. Where the losing registrant has disputed the domain through the registrar's own systems – reporting a compromised account, for example – the registrar may place an internal hold pending its own investigation.
Complainants who have won a UDRP transfer order sometimes discover that weeks pass with no movement. That silence is not a reversal of the decision. But it does require action. The correct first step is to contact the registrar's compliance or legal department directly, citing the forum's decision reference, the decision date, and the expiry of the 10-business-day window. Most registrars resolve a logged escalation within days. Some require the complainant to submit a formal implementation request accompanied by the decision document.
A second source of delay: the domain is held at a different registrar than the one that registered it at the time of the complaint. Transfers between registrars during a proceeding are prohibited under the lock that the registrar applies at commencement. But if the lock was not applied promptly – or if the registrant arranged a transfer before the lock took effect – the decision may reach a registrar that did not receive the original notification. The complainant then needs to engage the current registrar with the full record of the proceeding and the decision.
What happens when a court action is filed in time?
Implementation is paused. The registrar holds the domain in its current state – registered to the respondent, locked against transfer – until the court resolves the claim or issues a direction. There is no fixed timeline for that resolution; US federal court proceedings in domain disputes have run from months to several years depending on complexity and congestion. The pause itself does not expire automatically.
Some respondents file court proceedings not with a genuine expectation of success, but to delay implementation. Panels have noted this possibility, and some forum rules allow a complainant to seek a court's assistance in shortening the stay or obtaining a preliminary order directing the registrar to act pending trial. In our practice, we have seen a US court proceeding – filed as a delay tactic against a .com transfer order, autumn 2025 – resolved on summary judgment within four months, with the transfer ultimately implemented. That outcome is not guaranteed, but it illustrates that a court filing does not necessarily mean a long wait.
What about the complainant's position during the court proceedings? The complainant did not start those proceedings and is responding to them. The complainant typically becomes the defendant in a declaratory action brought by the respondent – seeking a declaration that the respondent has rights to the domain, that the UDRP decision was wrong, or that the transfer would violate applicable law. Responding to such a claim requires local litigation counsel, full access to the UDRP record, and a clear brief on the complainant's trademark rights.
If a respondent has filed court proceedings after an adverse UDRP order and named you as a defendant, contact info@cognomenlaw.com to discuss how to coordinate your response with the original dispute record.
What if the registrar never implements?
A registrar that fails to implement a UDRP decision without a valid reason – no court action filed, no court order staying implementation – is in breach of its ICANN accreditation obligations. That is not merely a service failure; it is a compliance matter for ICANN. The complainant's options in that situation include: a direct escalation to the registrar's legal or compliance department with a formal demand letter citing the decision and the ICANN obligation; a complaint filed with ICANN's Contractual Compliance team; and, where the registrar's non-compliance is sustained, a court application for an order directing the transfer.
The DNS-abuse obligation amendments that took effect on 5 April 2024 tightened contracted parties' accountability to ICANN more broadly – though those provisions address technical abuse (malware, phishing, botnets, pharming) rather than the transfer of domain ownership following an arbitration decision. The UDRP implementation obligation remains the contractual mechanism, not a DNS-abuse enforcement route. Conflating the two wastes time.
We recommend that complainants who win a UDRP transfer order set a calendar reminder for the day the 10-business-day window closes. If no transfer has occurred within two to three business days after that date, begin escalation immediately. Waiting weeks before escalating allows a simple compliance backlog to become an entrenched dispute with the registrar.
Myth: a court action is always faster than waiting for UDRP implementation
Many brand owners – particularly those accustomed to obtaining preliminary injunctions in trademark litigation – assume that filing a court action will resolve a domain dispute faster than a UDRP complaint. For most domains, that assumption is incorrect. A UDRP at WIPO for a standard case runs approximately two months, start to finish, at a forum filing fee of USD 1,500 for a single-member panel. A US district court action on equivalent facts rarely reaches final judgment in under a year, and preliminary relief requires a separate application with its own showing of irreparable harm and likelihood of success.
There are circumstances where court is the right first route: when monetary damages are sought, when the registrant's identity cannot be established through available RDAP lookups and disclosure requests, or when the domain is in a zone that has no UDRP equivalent – notably .de, which directs disputes to German courts. But for a .com, .net, .org, or any zone that has adopted the UDRP or a close variant, arbitration is almost always the faster and less expensive route to a transfer remedy.
The UDRP also provides no monetary damages – that limitation is the cost of its speed. If the complainant needs both the domain and compensation for harm caused during the infringement period, a court action after a successful UDRP may be the right sequence, with the UDRP proceeding first to recover the name quickly. That sequencing is worth discussing before filing either action.
What to do now
If you are a complainant awaiting implementation, check today whether the 10-business-day window has expired. If it has, and the domain has not transferred, send a written demand to the registrar's compliance contact citing the forum, the decision date, and the decision reference. If there is no response within five business days, escalate to ICANN Contractual Compliance and consider whether a court application for an order compelling transfer is warranted in the relevant jurisdiction.
If you are a respondent who has just received an adverse decision, the clock is running. You have 10 business days from the date of the decision notification to file a court action and notify the registrar if you intend to challenge the outcome in court. Every day of delay narrows your options. If you are not certain whether the panel's reasoning was sound, have the decision reviewed immediately. An RDNH finding is available only from the panel at the decision stage – a court proceeding, if you pursue one, runs on different grounds.
As of October 27, 2026, the proposals to add an appeals layer to the UDRP – recommended in the December 2025 review by WIPO and the Internet Commerce Association – have not been adopted. The current 10-business-day court window remains the only formal challenge mechanism within the Policy. Verify the current position before advising a client or respondent that appeals are available; they are not yet part of the UDRP as in force.
COGNOMEN focuses only on domain-name disputes – recovery, defense, and transactions. We handle UDRP complaints and responses, cybersquatting litigation with local litigation counsel in the relevant jurisdiction, and registrar escalation when a winning order is not implemented. To discuss a domain dispute or an implementation problem, contact info@cognomenlaw.com.
Related at COGNOMEN
Frequently asked questions
What changed and when?
The UDRP's implementation mechanics – the 10-business-day court-challenge window and the registrar's obligation to transfer or cancel after it expires – have been part of the Policy since it was adopted in 1999. No substantive change occurred to those rules in 2025 or 2026. What did change is the procedural context around them: WIPO's expedited procedure (introduced 9 March 2026) now shortens the decision phase to roughly one month for eligible cases, which means the implementation window follows sooner. The proposed appeals layer recommended in December 2025 has not been adopted as of October 27, 2026; verify before advising any client that it applies.
Who does this affect?
Anyone involved in a concluded UDRP proceeding – complainants waiting for a transfer order to be carried out, and respondents who have received an adverse decision and are considering whether to challenge it in court. Registrars are also directly affected, as they bear the implementation obligation under ICANN accreditation. Brand owners with portfolio enforcement programs face this step repeatedly; the most common problem in volume enforcement is tracking implementation status across dozens of domains and multiple registrars simultaneously.
What should I do now?
If you are a complainant, monitor the 10-business-day window and escalate to the registrar's compliance department the moment it expires without a transfer. If you are a respondent, decide within the first day or two after receiving the decision whether court relief is worth pursuing – local litigation counsel in the relevant jurisdiction can assess the grounds quickly. Do not wait to make that call. If the decision mentions reverse domain name hijacking, preserve that finding; it is reputational and cannot be re-sought in a subsequent proceeding.
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.