Step-by-step: enforce a UDRP decision a registrar will not implement for a .ai domain
A WIPO panel has ordered transfer of a .ai domain. You expected the registrar to act within days. Instead: silence, deflection, or an outright refusal. The decision sits on paper while the registrant – or whoever now holds the domain – continues using it. What happens next is not automatic, and the window to act is shorter than most brand owners realize.
To enforce a UDRP decision a registrar will not implement for a .ai domain, you must move beyond the arbitration channel and into a second track: either a direct escalation through ICANN's registrar-compliance process, a petition to the .ai registry authority, or – where those routes fail – court action in the relevant jurisdiction with local litigation counsel. The UDRP panel has no enforcement power of its own; the transfer mechanism depends entirely on registrar cooperation. When that cooperation breaks down, the complainant must build a parallel enforcement record, fast.
This guide walks each step in sequence, flags the trap hidden in each one, and explains what evidence you need to make the court route viable if arbitration's reach runs out.
What makes .ai different: the zone, the registry, and the UDRP's reach
The .ai ccTLD is the country-code domain for Anguilla. It has become popular among artificial-intelligence companies because of the coincidence of initials, but it remains a ccTLD governed by Anguilla's registry authority, not by ICANN's standard accreditation framework that covers .com, .net, or .org. WIPO does administer dispute procedures for .ai, and a UDRP-based decision issued through WIPO can cover .ai registrations – but the enforcement architecture differs from a standard gTLD case in a critical way.
For a .com or .net domain, an ICANN-accredited registrar is contractually bound to implement a valid UDRP decision within a set period. For a .ai domain held at a registrar operating outside the standard ICANN accreditation chain – or at the registry itself – that contractual lever may not exist in the same form. The trap: many complainants assume a WIPO panel order is self-executing. It is not. If the registrar sits outside ICANN's disciplinary reach, the normal escalation path through ICANN's compliance office carries far less weight.
Before filing any enforcement action, confirm exactly which entity holds the registrar function for the disputed .ai domain and whether that entity is ICANN-accredited. That single fact determines which escalation route is available to you first.
Step 1: Obtain and authenticate the WIPO decision document
The first step is procedural, but skipping it costs weeks. WIPO issues the decision and notifies the registrar directly. You need the official decision document – not a dashboard screenshot – in a format the registrar, the registry, and any court will accept. Request the authenticated decision from WIPO in writing immediately after the notification period ends.
Simultaneously, capture a timestamped WHOIS/RDDS record showing the domain is still registered to the respondent. If the respondent transfers the domain to a third party during or after the UDRP proceeding – a tactic known as cyberflight – the UDRP decision may no longer bind the new registrant, and you face a separate claim. Document every WHOIS state at the time of filing, at the time of decision, and at the time of each subsequent enforcement step. That chain of evidence matters in court.
The trap in Step 1: waiting for the registrar to acknowledge the decision before you begin collecting evidence. Acknowledgment may never come. Start your evidence file the day the decision issues.
Step 2: Issue a formal written demand to the registrar
Send a written demand to the registrar – by email and by any courier address in the registrar's WHOIS or terms of service – citing the WIPO case reference, the decision date, and the specific transfer order. State a compliance deadline of no more than five business days. This is not optional courtesy; it is the first link in the enforcement record that any subsequent tribunal will read.
The demand letter should attach: (a) the authenticated WIPO decision, (b) the WHOIS record showing current registration status, (c) the complainant's trademark certificate or other rights evidence relied on in the UDRP, and (d) a clear statement that non-compliance may result in a formal complaint to ICANN's registrar-compliance department, a report to the .ai registry authority, and, if necessary, court proceedings.
The trap in Step 2: a demand that is too informal. An email that reads "please transfer the domain" without citing the legal basis gives the registrar a pretext to treat it as a routine customer inquiry. Cite the UDRP, cite Paragraph 4(a), and cite the decision explicitly.
Step 3: Escalate to ICANN registrar compliance (if the registrar is ICANN-accredited)
If the registrar holding the .ai domain is ICANN-accredited – and some are – ICANN operates a registrar-compliance function that receives complaints about an accredited registrar's failure to implement a valid UDRP decision. Filing a compliance complaint does not guarantee action on a fixed schedule, but it creates an official record and prompts a formal inquiry from ICANN to the registrar. Registrars under ICANN accreditation agreements risk sanction, suspension, or termination of accreditation for repeated non-compliance.
The compliance complaint should include everything in your demand letter plus the registrar's non-response or refusal. Be precise: state the number of days elapsed since the decision, attach the correspondence record, and attach the current WHOIS showing no transfer has occurred.
The trap in Step 3: treating an ICANN compliance complaint as the end of the road. ICANN's compliance process is slow and is not a substitute for court action where prompt relief is needed. File the compliance complaint, then continue to Step 4 in parallel.
The steps above describe the standard escalation path. Your registrar's accreditation status, the .ai registry's current dispute rules, and the registrant's conduct will determine which of these levers applies – and how quickly. For an assessment of your domain dispute, contact info@cognomenlaw.com.
Step 4: Petition the .ai registry authority directly
The .ai registry is administered under Anguilla's telecommunications authority. Where the registrar will not act, a complainant may petition the registry directly, citing the WIPO decision and requesting that the registry itself implement the transfer or impose a registrar lock pending a formal process. This route exists outside the normal UDRP implementation pathway, and its availability depends on the registry's current policies – which are subject to change and should be verified with counsel at the time of enforcement.
A registry-level petition is most useful when the registrar is non-responsive and the respondent may be attempting to move the domain to another registrar to frustrate enforcement. A registry lock prevents any outbound transfer while the enforcement dispute is live.
Practical note: the petition should cite the WIPO decision as primary authority, include proof of the complainant's trademark rights, and request a specific administrative action – not merely "please help." Vague petitions invite procedural delay. We regularly assist brand owners at this stage, preparing the formal petition and coordinating with registry contacts to establish a lock before a court application is necessary.
The trap in Step 4: assuming the registry will respond on the same timeline as a court. Registry correspondence can take weeks. If the domain is actively causing harm – diverting traffic, damaging reputation, enabling fraud – do not rely on the registry as your only line of enforcement. Move to Step 5 in parallel if the domain is causing active, measurable injury.
Step 5: Assess whether a court route is necessary – and where to file
Court action becomes necessary when the registrar defies the UDRP decision, the ICANN compliance process has stalled, the registry has not acted, and the domain continues to cause harm. It is also the right route when cyberflight has occurred – that is, when the registrant has transferred the domain to a new holder after the UDRP was filed, defeating the panel's jurisdiction over the original registrant.
Where do you file? The answer depends on three things: where the registrar is incorporated or operates, where the registrant is located, and whether any applicable law gives a court jurisdiction to order domain transfer. For .ai domains, the relevant jurisdictions may include Anguilla (as the ccTLD's home), the jurisdiction where the registrar is established, or the jurisdiction where the complainant holds trademark rights and where US or EU anticybersquatting legislation may apply. Anguilla is a British Overseas Territory; its court system applies English common law principles, and any claim there would be handled with local litigation counsel in Anguilla.
In our practice, we have seen situations where filing in the complainant's home jurisdiction – backed by a local trademark registration and a clear record of bad-faith conduct – produced a faster interim order than waiting for a foreign registry process to resolve. The court can issue an injunction ordering the registrar to transfer the domain and, in some jurisdictions, can hold the registrar in contempt for non-compliance. A UDRP decision, while not directly binding on a court, is powerful evidence of the panel's factual findings and is regularly cited in anticybersquatting litigation to establish the bad-faith element.
The trap in Step 5: forum shopping without jurisdiction analysis. Filing in a jurisdiction where the court has no personal jurisdiction over the registrar means the order cannot be served or enforced. Jurisdiction analysis – where the registrar is registered, where it has assets, where its servers or contracts are located – must come before any court filing.
What evidence decides the outcome?
Whether you are petitioning the registry, pressing ICANN compliance, or filing in court, the evidence file is the same: it must be complete, chronological, and self-explaining to a reader who did not follow the UDRP proceeding. Build it around six categories.
- The UDRP decision itself – authenticated, with the panel's finding on each of the three elements of Paragraph 4(a).
- The trademark record – the registration certificate or certificates relied on in the complaint, with evidence of priority dating.
- The chain of WHOIS records – from registration through the UDRP filing, through the decision, through the enforcement steps. Each snapshot must be timestamped and sourced from an authoritative RDDS query.
- The registrar correspondence record – every email, demand letter, and non-response, with headers intact. Silence is evidence of willful non-compliance.
- Evidence of harm – screenshots of the domain's active use (pay-per-click parking, phishing pages, diversion of traffic, competitive advertising), with metadata confirming the date captured.
- Evidence of cyberflight, if applicable – WHOIS history showing a registrant change after the UDRP was filed, or an unexplained change in registrar during or after the proceeding.
In a recent matter involving a .ai domain (spring 2025), we assembled an enforcement file covering all six categories within eight days of the registrar's first failure to respond. The structured file allowed us to approach the registry and, when that stalled, to brief local litigation counsel in the relevant jurisdiction within a further week. The domain was ultimately locked within approximately three weeks of the UDRP decision date. No single step was the solution; the speed came from running each track in parallel rather than sequentially.
Should you re-file a new UDRP complaint instead of enforcing the old one?
A question we hear regularly: if the registrar will not act, can you simply file a new UDRP complaint and hope the next registrar is cooperative? The short answer is that re-filing raises a procedural complication. UDRP panels apply a doctrine analogous to res judicata for cases involving the same parties, the same domain, and the same facts. A second complaint on the same grounds is likely to be dismissed as an abuse of process. Re-filing is not a substitute for enforcement, and it wastes the filing fee – USD 1,500 at WIPO for a single-member panel on one to five domains – without advancing the transfer.
There is a narrow exception: if new facts have arisen since the first decision – for example, the domain changed hands to a new registrant with a distinct pattern of conduct, or the use of the domain has materially changed in a way that creates independent bad-faith grounds – a second complaint on those new facts may be viable. That analysis requires careful review of the first decision to avoid collateral attack.
The myth worth addressing here is that a UDRP decision, once won, is as good as a court order. It is not. It is a contractual mechanism dependent on registrar cooperation. When that cooperation fails, the complainant who treats the decision as the finish line discovers that the real work begins after the panel signs off.
If a prior filing or a non-compliant registrar has left your UDRP decision unimplemented, a focused second read of the enforcement record can identify the step that was missed. To weigh your options – registry petition, ICANN compliance, or court action – email info@cognomenlaw.com.
Related at COGNOMEN
Frequently asked questions
What are the chances to enforce a UDRP decision a registrar will not implement for a .ai domain?
No prediction of outcome is appropriate without reviewing the specific registrar's accreditation status, the current .ai registry rules, and the registrant's conduct. In general, a complainant with an authenticated WIPO decision, a clear trademark record, and a complete correspondence trail stands in a strong position to compel action through ICANN compliance, a registry petition, or court proceedings. Each route carries distinct timelines and risks; a combined, parallel approach typically produces the fastest result.
What evidence do I need to enforce a UDRP decision a registrar will not implement for a .ai domain?
At minimum: the authenticated WIPO decision, the trademark registration relied on in the complaint, a chronological WHOIS record from filing through the present, every piece of registrar correspondence (including non-responses), and timestamped screenshots of the domain's current use. If cyberflight has occurred – a change in registrant or registrar after the UDRP was filed – add WHOIS history showing that transfer. That six-category file is the foundation for a registry petition, an ICANN complaint, and any court application.
Can I enforce a UDRP decision a registrar will not implement for a .ai domain without going to court?
Often yes, depending on the registrar's accreditation status and the registry's responsiveness. An ICANN registrar-compliance complaint and a direct petition to the .ai registry authority are both non-court routes that have produced results in practice. Court action becomes necessary when both of those routes fail, when the registrant has transferred the domain to frustrate enforcement, or when active harm – phishing, traffic diversion, fraud – requires an urgent injunction that only a court can grant.
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.