FAQ: enforce a UDRP decision a registrar will not implement for a .in…
FAQ: enforce a UDRP decision a registrar will not implement for a .in. UDRP and ccTLD domain recovery and defense across .info. Email the firm to assess your c…
A WIPO panel has ruled in your favor. The decision orders the .info domain transferred to you. Then nothing happens. The registrar does not move. Days pass, then weeks. What now?
When a registrar fails to implement a UDRP transfer order for a .info domain, the winning complainant has two principal routes: escalate to ICANN's compliance function, which can compel the registrar to act, or pursue court enforcement in the jurisdiction where the registrar is incorporated. The standard implementation window under the Policy is 10 business days after the decision is transmitted, absent a court challenge by the losing respondent. If that window closes without action, the non-compliance becomes an ICANN accreditation issue — and, where warranted, a matter for the courts.
This FAQ addresses the specific problem of a non-implementing registrar in the .info zone, covering the escalation mechanics, the court route, the evidence required, multi-domain scenarios, and realistic outcomes.
What does it mean to enforce a UDRP decision a registrar will not implement for a .info domain?
It means a panel at WIPO or another approved provider has issued a written decision ordering the .info domain transferred to the complainant, but the registrar of record has not executed that transfer within the required period and has not provided a satisfactory explanation.
Under the UDRP, the registrar is contractually bound — through its ICANN accreditation agreement — to implement panel decisions. The 10 business day post-decision window exists to allow the losing respondent to seek a court stay. If no stay is obtained and the registrar still does not act, that inaction is a breach of the registrar's obligations, not a flaw in the UDRP ruling itself.
Why does this happen at all? Sometimes the delay is administrative — a backlog, a staff change, an unclear decision notice. Sometimes the registrar's own terms of service create a conflict with a third-party privacy or proxy service that holds the registration. And in rarer cases, the registrar is simply unresponsive or has allowed its accreditation to lapse. Each cause leads to a different solution.
.info is a generic top-level domain managed by the registry operator under ICANN's oversight. It fully adopts the UDRP; the same three-element test, the same remedies, and the same implementation mechanics apply here as for .com. The difference from a ccTLD is significant: there is no national registry body to appeal to for .info — the enforcement path runs through ICANN compliance and, if necessary, the courts.
How long does it take to enforce a UDRP decision a registrar will not implement for a .info domain?
If the registrar simply failed to process the notice in time, a direct escalation to ICANN Compliance can produce movement within a few weeks. If the matter requires court action, the timeline depends entirely on the jurisdiction of the registrar's incorporation and can run from several months to over a year.
The sequence typically runs as follows. First, confirm that the 10 business day window has closed and that no court proceeding was initiated by the respondent. Second, contact the registrar directly with a formal written demand citing the decision and the ICANN implementation obligation. Third, if no response or action follows within a short further period — typically five to ten business days — file a complaint with ICANN Compliance. ICANN's Contractual Compliance team can issue a notice of breach to the registrar and, in serious cases, initiate proceedings that threaten the registrar's accreditation.
That escalation path resolves the majority of genuine non-implementation cases. Where it does not — where the registrar is unresponsive, defunct, or actively refusing — court action becomes necessary. In our practice, we assess the registrar's jurisdiction at the outset of any non-implementation matter, because the cost and timeline of litigation vary enormously between, say, a US-incorporated registrar (where US anticybersquatting litigation provides a parallel route) and one incorporated in a jurisdiction where domain-specific legislation does not exist. In the latter scenario, local litigation counsel in the relevant jurisdiction would handle the court proceedings.
What evidence is needed to enforce a UDRP decision a registrar will not implement for a .info domain?
The core evidence package is the signed panel decision, proof of proper service and transmission to the registrar, documentation that the 10 business day window has elapsed without a court filing by the respondent, and a written record of your demand to the registrar and its non-response.
Each element matters. The panel decision itself — a PDF or certified copy from the provider — establishes the legal basis. Proof of transmission, typically the provider's own confirmation email, shows the registrar received notice. A docket check or a sworn statement that no court challenge was filed removes the only valid reason for the registrar to hold back. And the written demand record is essential for any ICANN complaint or court filing: it shows that informal resolution was attempted and refused.
What else helps? WHOIS or RDDS records showing the domain is still registered to the respondent, not yet transferred, confirm the non-implementation is ongoing rather than resolved. If the registrar has been communicating, preserve every email thread. If the registrar claims a technical problem, request written confirmation of what that problem is and when it will be resolved — vague oral assurances are not useful in a compliance proceeding.
Where the escalation route moves toward court, additional evidence of harm becomes relevant: evidence that the .info domain is still active and being used in a way that damages the trademark owner, for example by redirecting customers or hosting competing content. That ongoing harm both supports urgency and, in jurisdictions that allow it, may support a claim for damages beyond simple transfer — though the UDRP itself does not award money, a court proceeding under the applicable national anticybersquatting statute may.
Can I enforce a UDRP decision a registrar will not implement for a .info domain for more than one domain at once?
Yes. If a single UDRP complaint covered multiple .info domains registered by the same holder, a single enforcement action — whether an ICANN compliance filing or a court proceeding — can address all of them together, because the same registrar obligation and the same decision apply across the set.
The UDRP permits a single complaint to cover multiple domains where the respondent is the same registered holder. If your complaint did that and the single decision covers all the domains, the non-implementation failure is also a single breach. One ICANN complaint can reference all domains listed in the decision. One court action can seek transfer of all of them.
The more complex scenario arises when the multiple domains are held at different registrars — either because the respondent spread registrations across providers or because a privacy service and the underlying registrant appear as separate registrants on different domains. In that case, the implementation obligations fall on each registrar separately. We regularly advise complainants who face this split: the practical answer is to pursue each registrar's compliance obligation in parallel, documenting each separately, and to escalate the non-complying ones to ICANN while allowing the complying ones to proceed on their own track.
There is also a timing consideration. If your original complaint addressed only some of the .info domains and you want to pursue others that were not included, a second complaint is required. A non-implementation enforcement action cannot be used to expand the scope of the original decision — it is a mechanism to give effect to what the panel already ordered, nothing more.
What are the possible outcomes when you enforce a UDRP decision a registrar will not implement for a .info domain?
The primary outcomes are: (1) the registrar completes the transfer following escalation, resolving the matter administratively; (2) ICANN Compliance compels the registrar to act under its accreditation obligations; (3) a court orders the transfer, sometimes with additional relief; or (4) if the registrar has become defunct, the domain is re-delegated or recovered through a registry-level process.
Administrative resolution — the registrar simply processing the transfer after a formal demand — is the most common outcome for genuine processing delays. No litigation, no ICANN complaint: a well-documented demand letter citing the decision and the registrar's ICANN obligations is often sufficient.
Where the registrar is unresponsive, ICANN Compliance proceedings introduce accreditation consequences. A registrar that persistently fails to implement decisions risks losing its ICANN accreditation — a serious consequence that most registrars move quickly to avoid once formally noticed. That threat alone produces action in many cases.
Court proceedings yield the broadest range of outcomes. Transfer is the floor. In jurisdictions with active anticybersquatting legislation — US anticybersquatting litigation being the clearest example — a court may also award statutory damages. In other jurisdictions, injunctive relief, costs, and declaratory orders are available. The right outcome to seek depends on which national law governs the registrar's conduct and what that law specifically provides. We assess the applicable national anticybersquatting framework before recommending a court route, because the cost of litigation must be proportionate to the value of the domain and the likely relief.
One outcome worth noting for completeness: where the respondent filed a court challenge within the 10 business day window and the registrar was correct to hold back, the enforcement question transforms into contested litigation. In that scenario, the UDRP decision is evidence, not a final order — the court starts fresh. That is a different matter entirely from non-implementation by a non-responding registrar.
What does it cost to enforce a UDRP decision a registrar will not implement for a .info domain at WIPO?
The original WIPO filing fee — USD 1,500 for a single-member panel covering one to five .info domains — was paid when the complaint was filed. There is no separate WIPO fee to enforce the decision; post-decision follow-up with WIPO's case administration is part of the original proceeding. Additional costs arise only if court action or ICANN Compliance engagement requires separate legal work.
WIPO's role ends when the decision is issued and transmitted to the registrar. If the registrar does not act, WIPO's case administration team can confirm the status and transmit reminders, but WIPO does not itself enforce panel decisions against registrars. It is ICANN — not WIPO — that holds the accreditation leverage.
Legal fees for an enforcement escalation are separate from the WIPO filing fee. An ICANN Compliance filing is a document-based administrative proceeding; the legal work involved in preparing it is typically less intensive than the original complaint. A straightforward escalation with a complete evidence record generally costs less than the original filing work. Court action, by contrast, is substantially more expensive and billed on a time basis — the cost depends on the registrar's jurisdiction, the complexity of the proceeding, and whether local litigation counsel in the relevant jurisdiction must be engaged.
One practical note: if you believe from the outset that the registrar is likely to be unresponsive — perhaps because it is a smaller operator with a history of compliance issues, or because it is located in a jurisdiction where ICANN's leverage is weak — factoring enforcement cost into the original decision to file the UDRP complaint is worthwhile. A USD 1,500 WIPO filing fee can look different when it is followed by significant court costs in a remote jurisdiction. We weigh that risk at the assessment stage, before the complaint is filed, because a court-only route may in some cases be more direct.
Related at COGNOMEN
What does it mean to enforce a UDRP decision a registrar will not implement for a .info domain?
It means a panel has ordered the .info domain transferred to you, but the registrar has not executed that transfer within the required 10 business day post-decision window and has not provided a valid reason. The registrar is contractually bound through its ICANN accreditation to implement panel decisions. Non-implementation is a breach of that obligation, and the remedy is ICANN Compliance escalation or court action — not a new UDRP filing.
How long does it take to enforce a UDRP decision a registrar will not implement for a .info domain?
An administrative escalation through ICANN Compliance can produce a result within a few weeks if the registrar responds to formal notice. Court action in the registrar's jurisdiction typically takes several months to over a year, depending on the forum and the complexity of the local proceeding. Determining the registrar's jurisdiction at the outset is essential because that choice shapes the timeline and cost of the entire enforcement effort.
What does it cost to enforce a UDRP decision a registrar will not implement for a .info domain at WIPO?
There is no additional WIPO fee after the original USD 1,500 filing fee for a single-member panel. Post-decision enforcement costs arise from the legal work of preparing an ICANN Compliance filing or, if necessary, initiating court proceedings. An ICANN escalation is generally less intensive than the original complaint; court action is substantially more expensive and depends on the registrar's jurisdiction and the scope of relief sought.
COGNOMEN is an independent boutique focused exclusively on domain-name disputes. We recover, defend, and transact internet domains across generic and country-code zones, before WIPO, the Forum, CAC, ADNDRC, and national procedures, and in court where arbitration cannot reach. We act for brand owners, domain investors, and registrants — including respondent-side defense and reverse domain name hijacking. In our practice, we have handled registrar non-compliance matters across multiple gTLDs and ccTLDs, and we assess the enforcement route — ICANN Compliance, court action, or registry escalation — at the outset of each matter. To discuss a domain, contact info@cognomenlaw.com.
For a read on whether the three UDRP elements are met, or to assess a registrar non-implementation problem, reach us at info@cognomenlaw.com.
Disclaimer: This article is general information about domain-name dispute procedures and does not constitute legal advice. Outcomes depend on the specific facts, the zone, and panel or court discretion. For advice on your domain, contact info@cognomenlaw.com.
Speak with Cognomen Law
For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter
Related
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.