FAQ: defend a .me domain registered before the complainant's trademark

FAQ: defend a .me domain registered before the complainant's trademark. UDRP and ccTLD domain recovery and defense across .me. Email the firm to assess your ca…

A brand owner files a UDRP complaint against your .me domain. The brand they are asserting did not exist – or was not registered as a trademark – when you registered your name. Does that alone protect you? The answer is more precise than a simple yes.

When a .me domain was registered before the complainant held any trademark rights, that chronological gap is among the strongest available defenses under the UDRP as applied to .me. The third UDRP element – bad faith at the time of registration and in use – is very difficult to establish when no mark existed yet. Registration timing is decisive evidence, but panels also examine the registrant's purpose and conduct throughout the domain's life. A response must be filed within 20 days of commencement.

The questions below address the governing procedure, the available safe harbors, the evidence that decides outcomes, and what happens if no response is filed. For advice on a specific dispute, contact info@cognomenlaw.com.

Does WIPO or a court decide a .me dispute?

WIPO decides the overwhelming majority of .me domain disputes under the UDRP, because .me – Montenegro's ccTLD – has appointed WIPO as its dispute-resolution provider and operates under the UDRP rules. That means the three Paragraph 4(a) elements apply in exactly the same form as for .com or .net. A complainant must prove: confusing similarity to a trademark it holds; the registrant's lack of rights or legitimate interests; and registration and use in bad faith. All three must be satisfied. The remedy, if the complainant wins, is transfer or cancellation – not damages. For disputes not resolved through the UDRP, Montenegrin national courts retain jurisdiction, though that route is rarely pursued by either side in a .me name dispute. In our practice, virtually every contested .me case we have handled has proceeded through WIPO.

When can I defend a .me domain registered before the complainant's trademark?

The registration date is your first and often most powerful argument. Panels have consistently held that a registrant cannot have acted in bad faith toward a mark that did not yet exist at the time of registration. If no trademark was applied for, registered, or in demonstrable commercial use when your domain was acquired, the complainant faces a near-insurmountable burden on the third UDRP element. That said, the defense requires evidence, not merely assertion.

Three conditions strengthen the pre-trademark defense materially. First, the registration date must be documented – the original WHOIS record, the registrar's transaction history, or a contemporaneous invoice all serve this purpose. Second, the domain must not have been put to uses that look like targeting the complainant after their mark emerged. A domain that was legitimately dormant for years, then suddenly redirected to a competing site the week after the complainant's product launch, invites a bad-faith-in-use finding even if registration was clean. Third, the registrant should have an independent explanation for why the name was chosen – a personal name, a descriptive term, a pre-existing project – rather than a coincidence that happens to match a later-arising brand. We regularly advise registrants to compile these records before a response is due, because the 20-day window is short.

To assess whether the pre-trademark timeline supports your defense, email info@cognomenlaw.com for an initial read of your situation.

What UDRP safe harbors apply to a .me registrant?

Paragraph 4(c) of the UDRP lists three non-exclusive safe harbors. Any one of them, if established, demonstrates a legitimate interest. The first is a bona fide offering of goods or services under the domain name before any notice of the dispute – panels look for evidence of genuine commercial activity, not a site assembled after the complaint arrived. The second is being commonly known by the name, independently of any trademark; this covers personal names and established handles. The third is legitimate noncommercial or fair use, without intent to mislead or tarnish. For a domain registered before the complainant's trademark existed, the first and third safe harbors are typically most relevant. A registrant who operated a real website, maintained a project under that name, or used the domain for personal or community purposes will have a far stronger record than one whose domain has sat parked with pay-per-click links pointing at competitors.

Building the legitimate-interest record means gathering everything contemporaneous: screenshots, archived pages, correspondence, invoices, social media activity, and any evidence of the original purpose when the domain was acquired. The Wayback Machine is a common source. Panels treat a persuasive, documented narrative more favorably than a bare chronological argument, even when the timeline itself is clearly favorable.

When is a reverse domain name hijacking finding realistic?

Reverse domain name hijacking (RDNH) is a panel finding that the complaint was brought in bad faith – that the complainant used the UDRP as a weapon to deprive a legitimate registrant of a name it had no rightful claim to. The finding carries no monetary penalty, but it is a public record and a reputational mark against the complainant. Panels grant RDNH findings sparingly, but the pre-trademark timing scenario is precisely the fact pattern where they arise most often. If a complainant files knowing that the domain predates its mark, knowing that the registrant has a plausible independent reason for the name, and pursues the complaint anyway, panels have held that conduct to satisfy the RDNH standard.

We have defended registrants in situations where an RDNH finding was not only a realistic outcome but was the primary objective – because the transfer attempt was clearly opportunistic. The critical ingredients are: a demonstrably earlier registration date, a credible independent purpose, no evidence of the registrant ever targeting the complainant, and a complaint that relies on a mark with a post-registration filing date. Where those four elements align, a respondent's counsel can simultaneously pursue full denial of the transfer and seek the RDNH finding in the same response.

What evidence decides the outcome of a .me defense?

Evidence in a .me/UDRP defense falls into three categories. The first is chronological proof: registration confirmation emails, WHOIS historical records, and any documentation showing the domain was acquired before the complainant's trademark priority date. The second is purpose evidence: what was the domain used for, starting when, and why does that use make sense independent of the complainant's mark? Screenshots, project records, business correspondence, and domain registration invoices all speak to purpose. The third is negative evidence: the absence of conduct that panels associate with bad faith – no offers to sell to the mark owner at an inflated price, no pattern of registering similar names, no redirection to a competing business, and no pay-per-click pages monetizing the complainant's brand.

A single weak link can undermine an otherwise strong pre-trademark defense. In a recent matter (a .me defense, late 2025), a registrant who had held a name for several years before the complainant's mark issued had nonetheless allowed the domain to resolve to a page with advertising links referencing the complainant's industry. The panel looked past the favorable registration date and focused on current use. We rebuilt the legitimate-interest argument around the original purpose, and the case ultimately resulted in a denial of transfer – but the pay-per-click period made the outcome less clean than it would otherwise have been. The lesson: if a complaint arrives, audit the current and historic use of the domain immediately.

What if the registrant does not respond?

A registrant who fails to respond within the 20-day window defaults. Default does not mean automatic loss. Panels are required to examine whether the complainant has met its burden on all three elements, regardless of whether a response was filed. But default removes the registrant's ability to present the pre-trademark evidence, the Paragraph 4(c) safe-harbor record, and any RDNH argument. As a practical matter, the overwhelming share of defaulted cases result in transfer, because the complainant's submissions go unopposed and the panel has no favorable record from which to find a legitimate interest. For a registrant with a genuinely strong pre-trademark defense, default is the worst available choice. The cost of a well-prepared response is modest relative to the value of a domain and the cost of re-acquiring it, if it can be re-acquired at all.

Can the decision be appealed or challenged?

The UDRP does not provide an internal appeal mechanism. Once a panel issues its decision and the registrar implements the transfer (following a short implementation window), the administrative remedy is spent. There is, however, a court route. Either party may bring proceedings in a court of competent jurisdiction – typically either the complainant's or the respondent's domicile, or the court chosen under the registration agreement – to override a UDRP decision. A successful court challenge can result in a transfer back to the original registrant. This path is pursued rarely, because litigation is slow and expensive relative to the UDRP process itself. The stronger practical tool is a well-prepared response that prevents an adverse decision in the first place. We have advised registrants on the court-challenge route where a panel made clear errors on the chronology or failed to address a safe-harbor argument, though outcomes in that route depend entirely on the national court and the strength of the record available.

If an adverse decision has been issued or a complaint is pending, email info@cognomenlaw.com to discuss options before the implementation window closes.

Related at COGNOMEN

• Respondent defense and RDNH – full service overview and how we build a .me or gTLD defense
• Guide to defending an investment domain under a national ccTLD procedure
• How transfer remedies work under ccTLD dispute procedures – the .it example