Case study: recover a .io domain confusingly similar to your trademark

Case study: recover a .io domain confusingly similar to your trademark. UDRP and ccTLD domain recovery and defense across .io. Email the firm to assess your ca…

A software company discovers a .io domain identical to its product name – save for a single added word – pointing at a page offering the domain for sale at a five-figure price. The registrant registered it weeks after the company's trademark published. The question is immediate: can the domain be recovered, and how quickly?

The .io ccTLD is administered by a registry that has adopted WIPO as its dispute-resolution provider, meaning the UDRP applies in full to .io domains. To recover the name, a complainant must satisfy all three elements of Paragraph 4(a): confusing similarity to a mark it holds, absence of the registrant's legitimate interest, and registration and use in bad faith. A standard case concludes in approximately two months, and the only available remedies are transfer or cancellation.

This case study describes how COGNOMEN approached one such matter – the situation, the strategic choices made, and the result – in entirely anonymized form.

What was the situation?

The client was a UK-founded technology company that had been trading under its product mark for several years, holding registrations in both the EU and the United States. In early spring 2026, the company's brand-protection team flagged a .io domain combining the mark with the descriptive word "app." The domain resolved to a broker landing page carrying a buy-it-now price well into five figures. WHOIS records placed registration three weeks after the EU mark's publication date.

Two features made this a strong candidate for UDRP proceedings rather than direct negotiation. First, the timing was hard to explain innocently: the registrant had no apparent business history under the name, no social-media footprint, and no prior use predating the trademark. Second, the markup was striking. The company had invested years building brand equity in the mark; paying the demanded price would have set a precedent and, in our assessment, rewarded conduct the Policy is designed to deter.

The client's concern was speed. A competing product was launching in the same space, and an unaffiliated "app" domain in the company's own name carried real reputational risk.

For an assessment of your domain dispute, contact info@cognomenlaw.com.

What did the firm do?

We began with a factual review against the three UDRP elements, assessing the bad-faith evidence, selecting the forum, and preparing the complaint.

On the first element – confusing similarity – the analysis was straightforward. The disputed domain incorporated the trademark in its entirety, adding only the generic word "app." Panels have consistently held that adding a descriptive or generic term to a mark neither eliminates nor reduces confusing similarity; it may even increase it where the added word directly describes the complainant's goods or services. The mark was registered and in active commercial use. This element presented no meaningful hurdle.

The second element – rights or legitimate interests – required showing the registrant had none. The Paragraph 4(c) safe harbors were methodically excluded. There was no evidence of any bona fide offering of goods or services under the domain name before notice of the dispute. The registrant was not commonly known by the name. The domain pointed at a commercial broker page, not any legitimate noncommercial or fair use. The absence of any credible counter-narrative strengthened this limb considerably.

The third element – bad faith in registration and use – was anchored on Paragraph 4(b). Offering a domain to the mark owner at a price significantly exceeding out-of-pocket registration costs is one of the enumerated bad-faith circumstances. The timing of registration relative to the trademark's publication, the lack of any independent business identity, and the brokerage landing page together formed a coherent bad-faith narrative. We also documented the commercial misdirection risk: a technology audience searching the product name could land on a third-party resale page, creating confusion as to the company's own web presence.

We filed at WIPO, selecting a single-member panel given the relative clarity of the elements and the client's priority on cost efficiency. The WIPO filing fee was USD 1,500 for a single-member panel on one domain. The respondent had 20 days from commencement to file a response.

No response was received. The case proceeded to panel appointment on the standard track.

To weigh UDRP against a court action for your case, email info@cognomenlaw.com.

What was the outcome?

The panel transferred the domain to the complainant. The decision issued approximately eight weeks after the complaint was filed – within the standard two-month window for UDRP proceedings. All three elements were found satisfied. The panel specifically noted the combination of registration timing, the brokerage offer, and the complete absence of any competing legitimate use as evidence of opportunistic registration.

The registrar implemented the transfer within the standard post-decision window. The company now holds the .io domain and has redirected it to its main product site.

Two features of this matter are worth isolating for any brand owner weighing a .io complaint. First, the "app" addition to the mark did not protect the registrant – it never does where the word simply describes what the complainant sells. Second, default (no response filed) does not automatically mean a transfer; the panel still examined the evidence on all three elements. A well-documented complaint carries the day regardless of the registrant's participation.

What does this case tell you about .io domain recovery?

The .io zone operates under the UDRP in the same way as .com, .net, or .org. A brand owner with a registered mark and a clear bad-faith narrative has the same procedural path available. The practical differences are narrow: the registry's technical implementation of the transfer follows standard WIPO protocols, and there is no separate ccTLD procedure to navigate first.

The strategic choice is forum and panel size. For a clear case – strong mark, obvious bad-faith indicator, no plausible respondent defense – a single-member panel at WIPO minimizes cost and maintains the two-month timeline. Where the facts are more contested, or where the registrant has any arguable legitimate interest, a three-member panel at USD 4,000 provides three independent assessments and reduces the risk that a close call goes the wrong way.

One situation to watch: a registrant who has genuinely built a product or service under a domain name that post-dates your mark is not automatically a cybersquatter. Panels examine whether any legitimate interest arose between registration and the dispute. In our practice, we regularly advise clients who underestimate this risk. A case that looks like a guaranteed transfer on the surface sometimes contains a Paragraph 4(c) defense the complainant did not anticipate. Assessing that risk before filing is as important as building the affirmative case.

For cross-zone situations – a .io complaint running alongside a parallel .com dispute – it is possible to consolidate both under a single WIPO proceeding if the registrant is the same entity. We have handled multi-domain filings where this consolidation materially reduced both cost and elapsed time.

Related at COGNOMEN

• UDRP recovery service – filing a UDRP complaint across all gTLD and adopted ccTLD zones
• Analysis: recovering a typosquat .cn domain – cross-zone strategy and ccTLD procedure
• Respondent defense in .br – fair use, RDNH, and legitimate interest under ccTLD rules