Case study: defend a generic-word .in domain
Case study: defend a generic-word .in domain. UDRP and ccTLD domain recovery and defense across .in. Email the firm to assess your case. Transparent fees, resp…
A complainant files under the INDRP claiming ownership of a single common English word registered as a .in domain. The registrant – a small digital business based in India – has held the name for years, operated a content site under it, and never approached the complainant. Still, a formal complaint arrives, demanding transfer.
Defending a generic-word .in domain turns on the Paragraph 4(c) safe harbors and the registrant's ability to document a legitimate interest that pre-dates any notice of the dispute. The INDRP mirrors the three UDRP elements closely, so the same evidentiary logic applies: a complainant who cannot establish distinctiveness in a descriptive term, or who cannot show the registrant lacked any legitimate interest, will not prevail. Where the complaint is thin and the bad faith showing is absent, an RDNH finding is a realistic outcome.
This case study walks the situation, the defense strategy, and the result.
The Situation
Our client had registered a two-syllable English word – a term used generically across the Indian e-commerce market – as a .in domain in 2019. The complainant was a foreign company holding a regional trademark registration for the same word, used in connection with a narrow product category. The complainant had no registered mark in India at the time of our client's registration. Our client's site had operated continuously, aggregating supplier listings for a product class that shared the generic word as its common name.
The complaint's core claim: the domain was identical to the mark; the registrant had no rights; and the registration was made in bad faith to attract users by confusion. The filing also alleged the registrant had never built a "real" business – a framing that overlooked three years of live operation and a modest but documented user base. We were contacted within days of the complaint's commencement.
The Strategy
We assessed the three INDRP elements immediately. The first element – confusing similarity – was effectively conceded by the name's identity with the mark. That is routine. The real contest was elements two and three.
On legitimate interest, we assembled the record under Paragraph 4(c): the client's business registration pre-dating any notice of the dispute, three years of hosting logs and traffic analytics, archived versions of the active site, and supplier correspondence using the domain in email headers. The point was not merely that the client owned the domain. The point was that the client was commonly known by that name in its trade, and had used it in connection with a bona fide commercial offering before receiving any notice of the complainant's claim.
Critically, the word itself was generic in the Indian market for the product class. Panels deciding cases under the UDRP – and under the INDRP, which closely tracks it – have consistently held that a complainant cannot rely on a descriptive or generic term to foreclose all third-party registrations, particularly where the complainant holds no trademark in the registrant's home jurisdiction at the date of registration. We built a record of third-party uses of the same word to reinforce the descriptiveness argument.
On bad faith, the complainant's evidence was thin. There was no evidence the client had registered the domain to sell it to the complainant, to disrupt a competitor's business, or to attract users by confusion with the complainant's specific product. The client had never contacted the complainant. There was no pattern of abusive registrations. We documented all of this in the response, and then went further: we argued the complaint was brought in bad faith, in circumstances where the complainant plainly knew that a descriptive word could not sustain a transfer order against a registrant with a documented operating history.
In a comparable matter – a .in aggregator site, spring 2025 – we built a similar legitimate-interest record for a registrant facing a five-figure buy-back demand framed as a UDRP complaint. The panel denied transfer and issued an RDNH finding. The outcome rested entirely on the quality of the documentary record assembled before the response deadline.
If you have received a complaint against a .in or other ccTLD domain, the response window is short. Email info@cognomenlaw.com to assess whether the three elements are met and whether an RDNH finding is realistic in your case.
The Outcome
The panel denied the transfer. It found that the complainant had not established that the registrant lacked a legitimate interest: the site's documented commercial use pre-dating any notice of the dispute satisfied the bona fide offering safe harbor. On bad faith, the panel noted the absence of any evidence of targeting and the generic character of the term, and declined to find registration or use in bad faith.
The panel also issued an RDNH finding. It noted that a complainant aware of a registrant's operating history and the descriptive nature of the term cannot credibly maintain that the registration was abusive. RDNH carries no monetary penalty under the INDRP, but the finding is on the public record and signals to the market that the complaint was an improper use of the procedure.
Our client retained the domain. The complainant's filing cost it the forum fee and its own legal expenses – with nothing to show for either.
To plan a respondent defense – including an RDNH argument – for a .in or other ccTLD domain, contact info@cognomenlaw.com. We act exclusively in domain-name disputes, and our fees are published in ranges rather than quoted on request.
Related at COGNOMEN
Case questions
What was the situation?
A foreign trademark holder filed an INDRP complaint demanding transfer of a generic English-word .in domain from an Indian registrant who had operated a commercial content site under the name for three years. The complainant held no Indian trademark at the date of the client's registration and presented no evidence the domain was registered to target the complainant's business.
What did the firm do?
We assembled a pre-dispute legitimate-interest record: business registration documents, hosting logs, archived site versions, and supplier correspondence. We argued the word was generic in the Indian market, that no bad-faith circumstance under Paragraph 4(b) was present, and that the complaint itself was brought in bad faith – supporting an RDNH finding on the public record.
What was the outcome?
The panel denied the transfer on both the legitimate-interest and bad-faith elements, and issued a reverse domain name hijacking finding against the complainant. Our client retained the .in domain. The RDNH finding is publicly recorded. No monetary penalty or damages are available under the INDRP, but the complainant bore its own costs with no remedy.
COGNOMEN is an independent boutique focused exclusively on domain-name disputes. We recover, defend, and transact internet domains across generic and country-code zones, before WIPO, the Forum, CAC, ADNDRC, and national procedures, and in court where arbitration cannot reach. We act for brand owners, domain investors, and registrants – including respondent-side defense and reverse domain name hijacking matters. We handle .in disputes under the INDRP and related ccTLD procedures alongside global gTLD work. To discuss a domain, contact info@cognomenlaw.com.
Disclaimer: This article is general information about domain-name dispute procedures and does not constitute legal advice. Outcomes depend on the specific facts, the zone, and panel or court discretion. For advice on your domain, contact info@cognomenlaw.com.
Speak with Cognomen Law
For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter
Related
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.