Step-by-step: enforce a UDRP decision a registrar will not im… (.me 2)

Step-by-step: enforce a UDRP decision a registrar will not im… (.me 2). UDRP and ccTLD domain recovery and defense across .me. Email the firm to assess your ca…

You filed a UDRP complaint. The panel ruled in your favor. The transfer order is on record at WIPO. And the registrar has done nothing. If you are trying to enforce a UDRP decision a registrar will not implement for a .me domain, you are not facing a legal defeat – you are facing an implementation failure, and the two require entirely different responses.

The .me ccTLD operates under the UDRP as administered by WIPO, meaning a panel transfer order carries binding procedural force. When a registrar fails to implement that order, the immediate remedy is a structured escalation sequence: formal demand to the registrar, ICANN compliance reporting, and – where those channels stall – an application to the Montenegrin courts or a US anticybersquatting action against the registrar in its home jurisdiction. A standard WIPO case runs about two months; post-decision enforcement, when contested, typically adds several more weeks to months, depending on the route chosen.

This guide walks each step in sequence, flags the trap hidden in each one, and maps the decision between arbitration escalation and court action.

Why .me falls under the UDRP – and what that means for enforcement

The .me ccTLD is administered by the Montenegro-based registry DOMENA, which has designated WIPO as its dispute-resolution provider and adopted the UDRP. That designation means any panel decision on a .me domain carries the same procedural weight as a .com decision: the registrar is contractually required to implement it once the transfer lock period expires. That is the source of the obligation – not courtesy, not discretion.

Here is the trap most complainants miss. The .me adoption of the UDRP does not make Montenegro a common-law jurisdiction. If enforcement eventually moves to a local court, the proceeding is governed by Montenegrin civil procedure, not by the familiar US or EU framework. Any .me registrant who registers locally also benefits from local procedural protections. Planning for that contingency from the beginning – not after the registrar has stonewalled for six weeks – is the only way to keep timelines from compounding.

The key procedural fact: once a WIPO decision is rendered, the registrar has a defined implementation window. If it does not act within that window and no valid court proceeding has been commenced in the registrant's jurisdiction to stay implementation, the registrar is in breach of its registry agreement with DOMENA and its accreditation obligations with ICANN. Both levers exist independently, and both can be pulled at once.

Step 1 – Confirm the decision is final and the lock window has passed

Before escalating, verify that the 10-business-day implementation window has actually closed. WIPO notifies the registrar and the parties of the decision. The registrar must then lock the domain to prevent transfer and, after the window expires with no court filing, implement the transfer. The trap at this step: many complainants count calendar days, not business days, and escalate one or two days too early. That premature escalation can muddy the complaint record.

Pull the WIPO case notification email and the WIPO decision itself. Confirm: the decision date, the notification date to the registrar, and today's date. Map the business days excluding weekends and any WIPO-recognized public holidays. Only when that window has closed without implementation do you move to Step 2.

Also confirm the current WHOIS/RDDS record. The registrar should have placed a registrar lock on the domain. If the domain has been transferred during the lock window – which occasionally happens in cases involving account compromise or a non-cooperative registrar – the enforcement path shifts immediately to registrar escalation and, potentially, transfer reversal under domain-theft recovery procedures. That is a materially different situation from a simple implementation delay, and it requires a different response strategy.

Step 2 – Send a formal demand to the registrar of record

A formal written demand to the registrar's abuse desk and legal contact is not a formality. It is a prerequisite that creates a paper trail and sets the clock for what follows. The demand should: cite the WIPO case notification by date (not by case number, to avoid errors), reproduce the operative transfer order language from the decision, specify the exact domain, name the implementing registrar by its ICANN-registered company name, and set a response deadline – typically five business days.

The trap here is tone and channel. A demand sent only through a web-based abuse form is easily lost or auto-closed. Send it by email to the registrar's abuse address and to any general counsel or legal contact published on its ICANN registrar profile, with read receipts requested. If the registrar is US-based, copy the ICANN Contractual Compliance team in a separate notice filed the same day (see Step 3). Keep every email, every auto-reply, and every silence on record.

Many registrars implement the decision quietly within 48 hours of a formal demand. The ones that do not usually fall into one of three categories: technical delay with a genuine resolution in progress; a dispute about the identity of the registrant (relevant where a bulk reseller is involved); or an active court proceeding in the registrant's home jurisdiction that is staying implementation. Knowing which category you face determines the next step.

Step 3 – File an ICANN Contractual Compliance complaint

ICANN's Contractual Compliance team is the body that oversees registrar obligations under the Registrar Accreditation Agreement. Non-implementation of a UDRP decision is a breach of that agreement. Filing a compliance complaint costs nothing and creates an official record. It also, in practice, moves registrar legal teams in a way that informal emails alone often do not.

File the ICANN compliance complaint online. Attach the WIPO decision, the registrar demand letter, and any response (or silence) from the registrar. State the domain, the registrar's ICANN IANA ID, and the implementation window closure date. ICANN will send the complaint to the registrar's compliance contact and request a response, typically within a defined review cycle.

The trap: ICANN Contractual Compliance does not itself implement transfers. Its tool is escalation and, ultimately, registrar accreditation sanction – a serious threat that accelerates most cases, but one that moves on ICANN's timeline, not yours. File it in parallel with the formal demand, not as a substitute. If you are also considering a court action, file the ICANN complaint before commencing litigation; it demonstrates exhaustion of administrative remedies and strengthens your record.

If the registrar has gone silent or produced a response that raises new procedural objections, a second read of the UDRP decision and the registrar's correspondence can identify whether a compliance complaint alone will resolve it or whether court action is the only path forward. To weigh those options for your .me domain, email info@cognomenlaw.com.

Step 4 – Assess whether a court route beats the compliance channel

Court action to enforce a UDRP decision is rarely the first choice – it is slower, materially more expensive, and involves retaining local litigation counsel in the relevant jurisdiction. For a .me domain, the relevant jurisdictions are potentially Montenegro (where DOMENA, the registry, is based), the registrant's home jurisdiction (if known and accessible), and the registrar's home jurisdiction (often the United States for ICANN-accredited registrars).

The decision matrix works as follows. If the registrar is US-based and the dispute involves a US trademark, a US anticybersquatting court action is often the most efficient court route: it allows the complainant to name the registrar directly, seek the same transfer remedy the UDRP awarded, and in some situations pursue damages that the UDRP cannot award. That route is handled with local litigation counsel in the relevant US jurisdiction. If the registrant is based in a jurisdiction where the registrar operates and has assets, a direct action in that court – supported by the UDRP decision as persuasive evidence – may compel implementation or obtain an independent transfer order.

The .de situation offers an instructive contrast: for a .de domain, there is no UDRP at all, and the German courts are the primary forum, with DENIC's DISPUTE entry used as a registration block during litigation. For .me, the arbitration path via WIPO exists and has already run its course – you have the decision. The court option is therefore not a replacement for the UDRP but a downstream enforcement mechanism for a decision that a registrar refuses to execute. That distinction matters when a court considers costs and remedies.

The realistic cost of court enforcement is substantially higher than the UDRP itself. Describe it only qualitatively: it will involve hourly legal fees, potentially in multiple jurisdictions, and timelines measured in months rather than weeks. The decision to proceed should be driven by the domain's commercial value to the brand, the availability of a clean court path, and whether a damages claim – unavailable under the UDRP – justifies the additional investment.

Step 5 – Address account compromise or unauthorized transfer before anything else

If the WHOIS/RDDS check at Step 1 reveals that the domain has already been transferred away from the registrar of record – either to a new registrar or to a new registrant – the enforcement path changes entirely. That scenario is domain theft layered onto an existing UDRP proceeding, and it is one of the most complex recovery situations in practice.

In that circumstance, the immediate priority is registrar escalation for a transfer hold, not implementation of the UDRP decision. Contact the original registrar's abuse team to report the unauthorized transfer and request a registration lock or ERRP (Expired Registration Recovery Policy) hold. Simultaneously, contact ICANN Contractual Compliance to report a potential unauthorized registrar transfer. If the domain moved to a new registrar, that registrar must also be contacted directly.

The trap: an unauthorized transfer following a UDRP decision is a compound event. The UDRP decision addressed the original registrant. If the domain is now in different hands, the decision may need to be supplemented by a new proceeding naming the current registrant, or by court action seeking a chain-of-title transfer order. We have managed situations involving .com and new-gTLD domains – including one matter in spring 2025 where a domain was transferred out during the implementation window – and in each case early escalation within 24 to 48 hours of discovering the unauthorized transfer was the decisive factor in whether the domain could be recovered.

Evidence of compromise that carries weight in registrar and court proceedings includes: login-event logs from the registrar showing the timing and IP address of the unauthorized access; email headers from any transfer authorization messages; and any communications from the former registrant or a third party offering to sell the domain after the UDRP decision was published. Preserve all of that material before contacting the registrar; it can be overwritten or deleted quickly.

If a post-decision unauthorized transfer has occurred, the next step needs to be taken quickly. For an assessment of recovery options for your .me domain, contact info@cognomenlaw.com.

Step 6 – Assemble the evidence package for any escalation path

Whichever escalation route you pursue – ICANN compliance, court action, or registrar escalation for theft – the evidence package required is materially the same. Assembling it once, correctly, avoids the delay of reconstructing it under pressure at each stage.

The core package for a non-implementation enforcement proceeding includes:

• The WIPO decision in full, including the notification date to the registrar and the parties.
• Timestamped WHOIS/RDDS screenshots taken at the moment the implementation window closed and at intervals since.
• The formal demand letter and all registrar correspondence, including auto-replies and silence records (date-stamped email thread exports).
• The ICANN compliance complaint filing confirmation.
• Proof of the complainant's trademark rights, as submitted in the original UDRP complaint – panels and courts sometimes ask for this as a standing check even in enforcement proceedings.
• If account compromise is suspected: any registrar login-event logs, IP access records, email change notifications, or MFA-bypass events available from the registrar's account security logs.

Brand owners managing portfolio-scale enforcement – covering multiple zones simultaneously – find that a standardized evidence template maintained at the portfolio level dramatically reduces the turnaround time at each escalation stage. We regularly advise registrants and complainants on structuring that kind of evidence infrastructure before a dispute arises, not only after a panel decision has issued.

Step 7 – Understand the realistic timeline for each path

Setting accurate expectations at this stage prevents decisions driven by impatience rather than strategy. Here is a realistic map of the timelines involved at each escalation level.

Formal demand alone: if the registrar responds and implements, resolution typically comes within two to ten business days. Most cooperative registrars act within that window once formal notice is properly served. ICANN Contractual Compliance: the compliance review cycle runs on ICANN's own timeline, which varies. Resolution via this channel, without a parallel court filing, typically runs several weeks to a few months depending on case volume and the registrar's responsiveness. Court enforcement – US anticybersquatting: from filing to a transfer order, assuming the registrar or respondent does not actively contest, typically runs several months at minimum and can extend well beyond that in contested proceedings. Court enforcement – Montenegrin courts or other local civil proceedings: timelines depend on the applicable civil procedure rules and docket conditions in the jurisdiction; local litigation counsel in the relevant jurisdiction should provide current guidance.

The practical answer for most .me brand-recovery matters is that the formal demand and ICANN compliance path, run together and with professional follow-up, resolve the large majority of non-implementation cases before court action becomes necessary. Court action should be budgeted for and available, but it is the escalation backstop, not the opening move.

Related at COGNOMEN

• Court recovery and domain theft services – the full menu of post-arbitration and litigation routes
• Enforcing a UDRP decision for a .dev domain – step-by-step for new gTLD registrations
• Proving legitimate interest in a .mx UDRP – respondent defense strategy and evidence