Step-by-step: bring a court action when UDRP cannot reach a .me domain

Step-by-step: bring a court action when UDRP cannot reach a .me domain. UDRP and ccTLD domain recovery and defense across .me. Email the firm to assess your ca…

You discover that a .me domain matching your brand has been registered by a stranger – or worse, transferred away from your account without your authorization. The UDRP process looks familiar. But the facts do not fit: the registrant may have a colorable claim to the name, the registrar is stonewalling, or the dispute involves account compromise that arbitration panels simply cannot remedy. What then?

When you need to bring a court action because UDRP cannot reach a .me domain, the path runs through Montenegrin civil courts or, where jurisdiction permits, a court in the complainant's own territory with a nexus to the harm. The UDRP does apply to .me – WIPO administers it – but arbitration is limited to transfer or cancellation and has no power to award damages, reverse an unauthorized transfer, or compel a registrar. A court action fills those gaps. The WIPO filing fee for a .me dispute begins at USD 1,500, but where UDRP cannot reach, a court route is the only way to recover money, restore a hijacked account, or pursue a registrant outside the Policy's reach.

This guide walks each step, names the trap inside it, and explains where the two routes diverge in practice.

Why Would UDRP Not Reach a .me Domain?

The UDRP applies to .me because the Montenegrin ccTLD registry has appointed WIPO as its dispute-resolution provider, and .me operates under UDRP-equivalent rules. So the Policy is available. The question is whether it is sufficient for the facts you are facing.

Several scenarios put a .me dispute beyond the Policy's effective reach. First, the UDRP's only remedies are transfer and cancellation – no damages, no costs, no injunctions. If your brand suffered measurable financial harm from the infringing registration – diverted customers, fraudulent invoices routed through the domain, or a phishing campaign – a UDRP panel cannot compensate you for that loss. Court can.

Second, UDRP panels decide whether the registration was abusive at the time of filing and use. They do not adjudicate ownership of an account that was compromised. If a domain was stolen – the registrar account was hacked, credentials were phished, or a social-engineering attack moved the domain to a new registrar – the dispute is not about "bad faith registration" in the UDRP sense. It is about theft, and a court order or registrar-escalation procedure backed by court process is the effective tool.

Third, the three UDRP elements under Paragraph 4(a) of the Policy require a trademark in which the complainant has rights. A domain investor who built value in a name but holds no registered mark may find Paragraph 4(a)(i) an obstacle, while a court action grounded in unfair competition or passing-off doctrine may still be available.

Finally, respondents who register in genuine good faith – acquiring a domain for its dictionary value, geographic meaning, or personal name – may defeat a UDRP complaint but nonetheless be using the domain in a way that causes ongoing commercial harm. Court proceedings can examine the full factual record and fashion relief proportional to it.

If you are unsure whether UDRP or court action is the right first move for your .me dispute, contact info@cognomenlaw.com for an assessment of the three elements and the remedies you actually need.

Step 1: Confirm Jurisdiction and the Applicable Legal Route

Before a single pleading is drafted, confirm which court has jurisdiction and which legal theory grounds the claim – this is the step where brand owners most often underestimate complexity, and where the wrong choice costs months.

The .me ccTLD is administered from Montenegro. Montenegrin courts have jurisdiction over the registry and, by extension, over the registrant's registration contract. However, if the registrant is located in a different country – a US company, a German individual, or an anonymous holding – your own jurisdiction may also support a claim. US anticybersquatting litigation, for example, can reach .me domains where the respondent has a US nexus, operates the domain to harm a US mark, or is served in the United States. When jurisdiction is genuinely ambiguous, the choice turns on where enforcement is most practical and where the applicable substantive law is most favorable to your facts.

The trap in this step is over-relying on the registrant's WHOIS data. RDDS/WHOIS records for .me may show a privacy proxy or a stale address. Courts require proper service of process; if you cannot serve the respondent, even a favorable judgment is unenforceable. Document every piece of identifying information before you file.

A parallel UDRP complaint at WIPO is not mutually exclusive with court action. Many brand owners run both concurrently – the UDRP to capture the domain quickly if it succeeds, the court action to pursue damages and compel the registrar. The two proceedings are independent, and a UDRP panel will typically suspend its proceeding if a court action is filed first and a stay is requested. Understand this dynamic before you choose to file in one forum and potentially foreclose speed in the other.

Step 2: Secure the Domain with a Registrar Lock and Preservation Order

A domain can be transferred, deleted, or re-routed at any moment. Step 2 is about freezing the asset before it disappears – and the trap here is assuming the registrar will cooperate voluntarily.

Contact the registrar and request a registrar lock or "hold" status on the domain. Most accredited registrars respond to a documented legal notice. Frame the notice precisely: identify the domain, the legal basis for the lock request, and the evidence of the dispute or compromise. Send it by a traceable method. Keep the receipt.

If the registrar declines or does not respond within a reasonable period, the next tool is a court-ordered preservation or interim injunction. Courts in jurisdictions with experience in IP matters – and US federal courts in cybersquatting cases – are accustomed to issuing ex parte orders directing a registrar to lock a domain pending resolution. In Montenegro, civil procedural rules provide for interim measures in IP-adjacent disputes; local litigation counsel in the relevant jurisdiction can advise on the precise mechanism and the threshold showing required.

The evidentiary record you build in this step feeds directly into the merits. Document the current registration data, the DNS configuration, the resolving IP address, and any content the domain is serving – screenshots with timestamps and a page-source archive. If the domain is being used for email, trace the MX records. That technical record can demonstrate active harm and strengthen an argument for emergency relief.

In a domain-theft scenario – where your own account was compromised – the registrar-escalation and transfer-reversal process is distinct. Report the unauthorized transfer to the losing registrar and the gaining registrar simultaneously, using the account-compromise procedures most ICANN-accredited registrars publish. Provide authentication evidence: account logs, two-factor authentication records, prior billing correspondence. If the gaining registrar will not cooperate, a court order directed at both registrars is the escalation point. We have handled matters (a .me domain, summer 2025) where a registrar reversed an unauthorized transfer within days of receiving a court-backed preservation notice – speed of action was decisive because the registrant had not yet changed registrars again.

Step 3: Build the Evidence Record That Decides the Outcome

Evidence is not a support function for a court action – it is the case. The strength of the evidence determines whether you obtain interim relief, whether the court finds liability, and whether any judgment is enforceable.

For a cybersquatting or passing-off court action over a .me domain, assemble the following:

• Trademark documentation. Registered trademark certificates, application dates, first-use evidence, and geographic scope. A court action – unlike the UDRP – can also receive evidence of unregistered trademark rights, trade dress, and accumulated goodwill.
• Domain registration history. WHOIS snapshots, historical DNS records, and any available registrar data showing when the domain was registered, by whom, and how it changed hands. Tools that archive historical WHOIS data can fill gaps where current RDDS is obscured by a proxy.
• Use evidence. Screenshots of the domain's content, redirects, pay-per-click advertising, or phishing pages. Capture the metadata – URL, date, time in UTC, and the archiving tool used. Courts treat authenticated archive captures as admissible; unauthenticated screenshots printed from a browser carry less weight.
• Evidence of harm. Customer complaints, diverted inquiries, brand confusion incidents, or financial records showing revenue loss attributable to the infringing domain. This is the evidence that distinguishes a court action from a UDRP complaint, because panels cannot hear it.
• Account compromise evidence (theft cases). IP access logs, authentication records, password-reset emails, and any communications from a third party claiming ownership of the account. A chain-of-custody narrative showing the before, the moment of compromise, and the after is what courts and registrars look for.
• Correspondence with the registrant. Any demand, buy-back offer, or communication that shows the registrant's awareness of your rights and their intent. A five-figure buy-back demand sent after a domain is registered is a classic bad-faith marker both in UDRP and in court proceedings.

The trap in this step is delaying evidence collection while pursuing negotiation. Every day the domain is live and unarchived is a day's worth of evidence that can disappear. The registrant can delete content, transfer the domain, or simply let the registration expire and re-register it in another name. Collect first; negotiate after the record is secured.

Step 4: Understand What Decides the Court Action on the Merits

A court action over a .me domain is not a rerun of the UDRP. The merits test is broader, the defenses are broader, and the remedies are broader – in both directions.

In a Montenegrin court proceeding, the applicable national law on trademark infringement and unfair competition supplies the substantive test. The court does not apply the UDRP's three-element formula; it applies domestic IP statutes and, to the extent Montenegro has harmonized with EU IP directives, the broader EU framework. Practically, the key questions are whether the domain registration infringes your mark in the relevant territory, whether the registrant acted in a way that constitutes unfair competition, and whether the harm is attributable to the domain's operation rather than some independent cause.

In a US anticybersquatting court action brought over a .me domain with a US nexus, the substantive test focuses on the registrant's bad-faith intent to profit from a distinctive or famous mark. Courts examine a non-exhaustive list of factors: the registrant's trademark rights in the name (if any), whether the domain was the registrant's legal name, prior use of the domain in connection with a bona fide offering, the registrant's intent to divert consumers, and any offer to sell the domain for a profit above documented out-of-pocket costs. A court, unlike a UDRP panel, can weigh all the evidence and draw inferences – which can help or hurt depending on your facts.

What decides outcomes in practice? In our experience handling court actions where UDRP was either unavailable or insufficient, three factors recur as determinative. First, the clarity of the trademark record: a registered mark with an application date predating the domain registration is the clearest anchor. Second, the documentary evidence of the registrant's intent: a buy-back demand, a pattern of similar registrations, or content designed to attract the brand's customers are each powerful individual evidence of bad faith. Third, the speed and completeness of the preservation step: a court action that begins with a domain still locked and still serving infringing content is a stronger case than one filed after the registrant sanitized the DNS.

If a prior UDRP complaint produced a default or a panel decision that left remedies incomplete, a court action can address the gap. For a second-read assessment of your .me dispute, email info@cognomenlaw.com.

Step 5: Choose Between Running UDRP in Parallel or Sequencing the Proceedings

The decision whether to file a UDRP complaint at WIPO alongside the court action – or to sequence them – is not a formality. It is a strategic choice with real consequences for speed, cost, and the final scope of relief.

Running both concurrently maximizes coverage: WIPO can deliver a transfer order in roughly two months, which is far faster than most court proceedings, and the UDRP's single-member panel fee of USD 1,500 is modest compared with litigation costs. If the UDRP succeeds first, you may obtain the domain before the court action concludes. The court action then continues for the damages and injunctive relief that the UDRP cannot provide.

The risk of parallel proceedings is that a court filing may cause a WIPO panel to suspend the UDRP proceeding pending the court's decision, under the principle that a court is the superior forum for contested factual issues. If the court action is slow – and cross-border litigation routinely is – that suspension can strand the UDRP for months. In those circumstances, sequencing may be more effective: file the UDRP first to capture the domain quickly if the three elements are clearly met, then follow with court action for the broader remedies.

The right approach depends on the strength of the three UDRP elements, the likely speed of the relevant court, and whether the registrant is the type of actor who would transfer or delete the domain if a UDRP is filed. Where the registrant is a sophisticated actor with multiple similar registrations, a court-first strategy backed by an immediate preservation order is often the sounder choice. Where the domain is a straightforward typosquat with no plausible defense, a UDRP-first strategy at WIPO recovers the asset fastest.

A third scenario: some brand owners discover that the .me registrant is also operating confusingly similar domains across a .com, a .net, and regional ccTLDs simultaneously. A single UDRP complaint can cover multiple domains if the registrant is the same holder. A court action, by contrast, is typically filed in one jurisdiction and reaches only the domains within that court's enforcement reach. Portfolio-wide relief often requires a combination: UDRP to sweep the gTLDs and WIPO-administered ccTLDs, court action for the jurisdictions where arbitration falls short.

Step 6: Pursue Enforcement After Judgment

A court judgment ordering transfer of a .me domain must be implemented by the registrar and, ultimately, recognized by the registry operator. This is where brand owners who have won in court are sometimes surprised to find that winning was not the last step.

Serve the judgment on the registrar with a clear instruction specifying the domain, the ordered remedy (transfer to the complainant, or cancellation), and the timeframe. Most ICANN-accredited registrars have legal compliance teams that process court orders; the process is documented, if not always fast. Where the gaining registrar is in a different jurisdiction from the court that issued the order, recognition of the foreign judgment may require a separate filing in the registrar's home jurisdiction. This is where local litigation counsel in the relevant jurisdiction becomes essential – a judgment that is unenforceable in the registrar's home country is effectively hollow.

For domain-theft cases, the transfer-reversal process after a court order follows a similar path: the order is served on the gaining registrar, the registry operator confirms the update, and the domain returns to the registrant's original account. Document every step in the chain, because registrars sometimes require additional authentication even after a court order is served.

The trap in this final step is assuming the registrant will comply voluntarily. They may not. Build enforcement mechanisms into the original application for relief: request that the court order be directed at the registrar as well as the registrant, and that the registry operator be named as an interested party where procedurally available. A judgment that binds only the registrant but not the registrar may require additional proceedings to implement.

Related at COGNOMEN

• Court recovery and domain theft: when arbitration is not enough
• Step-by-step court action for cybersquatting over a .mx domain
• UDRP recovery after a failed buy-back approach for .org domains