How to defend a .in domain acquired as an investment

How to defend a .in domain acquired as an investment. UDRP and ccTLD domain recovery and defense across .in. Email the firm to assess your case.

A notice arrives: someone has filed a complaint under the .in Domain Dispute Resolution Policy – the INDRP – claiming your investment-grade .in domain was registered in bad faith and demands its transfer. You bought the name because it had generic or descriptive value. You never targeted anyone's brand. Now you have a short window to respond or lose the domain by default.

Defending a .in domain acquired as an investment turns on three questions: whether the INDRP's bad-faith test is met on the facts, whether you can establish a legitimate interest under the Policy's safe-harbor provisions, and whether the complaint itself crosses the line into reverse domain name hijacking. The governing procedure is the INDRP, India's national domain-dispute policy administered through the National Internet Exchange of India (NIXI) – a procedure distinct from the UDRP, with its own rules and timelines. A domain investor who moves quickly and assembles the right evidence record can defend the registration, and in appropriate cases obtain an RDNH finding against the complainant.

This page covers the INDRP test, the safe harbors that protect investment registrations, the evidence that decides outcomes, what an RDNH finding requires, and how to start a defense.

What governs a .in dispute – and how does it differ from the UDRP?

The INDRP is the mandatory dispute resolution mechanism for .in domains, administered by NIXI. It was modeled on the UDRP, so the structure will feel familiar – but the differences matter in practice. The INDRP requires the complainant to prove that the domain is identical or confusingly similar to a name in which the complainant has rights, that the registrant has no rights or legitimate interests, and that the domain was registered or is being used in bad faith.

That final element is significant. Unlike the UDRP – which requires the domain to have been registered and used in bad faith, a cumulative test – the INDRP reads "registered or used in bad faith." A complainant who cannot show bad-faith registration can still prevail if it shows bad-faith use after the fact. Conversely, a registrant who can demonstrate that current use is legitimate has a meaningful argument even where the original registration date might look suspicious to a casual observer.

The INDRP also operates under procedural rules set by NIXI. Timelines and fee structures are published by NIXI directly and can change; confirm the current rules with counsel before filing or responding. The available remedies under the INDRP are transfer or cancellation of the domain – no monetary relief, no injunction, and no costs award except in exceptional circumstances. An RDNH finding, as under the UDRP, is a reputational sanction rather than a financial one.

One more structural point: an INDRP decision does not preclude subsequent court proceedings in India. A party dissatisfied with an INDRP outcome may seek judicial review, though that route carries substantially higher cost and timeline. For most domain investors, the INDRP proceeding is the decisive battleground.

Do the UDRP safe harbors protect a .in investment domain?

The INDRP incorporates provisions analogous to Paragraph 4(c) of the UDRP – the safe-harbor defenses that establish rights or legitimate interests in a domain. Three principal safe harbors apply. First, demonstrable preparations to use the domain in connection with a bona fide offering of goods or services, made before notice of the dispute. Second, being commonly known by the domain name. Third, making a legitimate noncommercial or fair use of the domain, without intent for commercial gain by misleading diversion or trademark tarnishment.

For a domain investor, the first and third safe harbors are the most relevant. Generic or descriptive domain names – short dictionary words, common industry terms, geo-descriptive names – have long attracted investment because their value derives from the ordinary meaning of the term, not from proximity to any one trademark. Panels under the UDRP and analogous national policies have consistently held that registering a generic term for resale, parking, or future development is not inherently in bad faith, particularly when no specific complainant's trademark was targeted at the time of registration.

Building a legitimate-interest record means demonstrating, with contemporaneous evidence, why this domain had commercial value independent of any complainant's mark. What was the registrant's acquisition rationale? Were there documented plans for development, a parking arrangement generating revenue, or a history of holding similar generic names? Was the name registered before the complainant's trademark acquired significant reputation? These are the questions a well-prepared response addresses directly.

If you have received an INDRP complaint or a demand letter relating to a .in domain you acquired as an investment, contact COGNOMEN now at info@cognomenlaw.com to assess the three elements, identify safe-harbor arguments, and plan a response before your deadline.

What evidence actually decides the outcome of a .in investment domain defense?

Evidence is the backbone of a respondent defense. A response that states conclusions without documentary support gives a panel nothing to credit. In our practice, the evidence that most consistently moves the needle for investment-domain respondents falls into several categories.

Registration timing. The date the domain was registered relative to the date the complainant's trademark rights arose is frequently determinative. If the domain predates the trademark – or predates the trademark's entry into the Indian market – the bad-faith registration argument is severely weakened. Registration history, WHOIS/RDDS records, and archived screenshots are all relevant.

Generic or descriptive character of the term. Panels look at whether the string has a meaning independent of the complainant's mark. A domain consisting of a common English or Hindi word or phrase, a geographic term, or a widely used descriptive phrase supports the conclusion that the registration was not targeted at any one rights holder. Evidence of third-party use of the term in commerce, dictionary definitions, and search-volume data can support this characterization.

Portfolio context. A registrant who holds dozens of similar generic names presents a different profile than one who registered a single domain closely mirroring a well-known brand. Demonstrating the pattern of acquisition – that the registrant acquires descriptive or short terms across zones, not marks of specific companies – goes directly to the question of intent.

Absence of targeting conduct. Has the registrant ever approached the complainant, demanded a premium, or pointed the domain at content that could be confused with the complainant's goods or services? Absence of such conduct, documented carefully, undercuts the bad-faith use element even where a panel might consider bad-faith registration arguable.

Parking and monetization terms. If the domain has been parked, the content of the parking page matters. Pay-per-click links that relate to the complainant's business or trademark are a liability. Parking revenue from links that reflect the generic meaning of the term, by contrast, supports the legitimate-use argument. Capture the historical parking content – archival records are often essential.

In a recent matter (a .in generic-term domain, spring 2025), we built a defense around registration timing – the domain predated the complainant's Indian trademark registration by several years – combined with a portfolio of analogous generic acquisitions and an absence of any demand or targeting conduct. The panel denied the complaint. The domain remained with our client.

When is reverse domain name hijacking a realistic outcome?

Reverse domain name hijacking (RDNH) is a finding that the complaint was filed in bad faith, primarily to deprive a legitimate registrant of a domain. An RDNH finding is reputational – it appears in the published decision record – but carries no monetary sanction. It does, however, send a signal to future panels evaluating the complainant's conduct, and it matters to the complainant's counsel and management.

RDNH findings are more available than many registrants realize. Panels have made RDNH findings where the complainant knew, or clearly should have known, that the respondent had a plausible legitimate interest – yet filed anyway. The hallmarks of a strong RDNH argument include: the complainant's trademark postdates the domain registration; the domain consists of a generic or descriptive term that the complainant cannot plausibly claim exclusive rights over; the complainant submitted misleading or incomplete evidence; or the complaint was filed after a purchase negotiation broke down, suggesting the proceeding was a pressure tactic rather than a genuine rights assertion.

An RDNH finding requires that the respondent affirmatively request it and provide the factual basis. Panels do not make RDNH findings on their own motion as a rule. This means the response itself must set out the argument, supported by the same evidence categories described above – registration timing, generic character, and absence of targeting.

We regularly advise registrants on whether the facts of their situation support an RDNH request. The analysis is fact-specific. A borderline complaint where the complainant had a colorable argument – even one that ultimately fails – is less likely to attract an RDNH finding than a complaint that was objectively baseless from the outset.

If you believe the complaint against your .in investment domain is abusive or opportunistic, email info@cognomenlaw.com. We will assess whether an RDNH argument is viable and build the record that supports it.

How does the .in defense compare to a UDRP or other ccTLD defense?

The right strategy depends on the zone. The INDRP governs .in; the UDRP governs .com, .net, .org, and most new gTLDs. They differ on one element that matters directly to investment-domain respondents: the bad-faith standard.

Under the UDRP, both registration and use in bad faith must be shown – a cumulative test. A domain investor who registered in good faith, even if current use generates commercial revenue, has a strong argument that the bad-faith registration element is not met. Under the INDRP, the "registered or used" formulation gives the complainant an additional avenue. A respondent must therefore be prepared to address both limbs, not only registration intent.

Under the Nominet DRS for .uk domains, the test is "abusive registration" – the complainant shows rights plus a registration or use that took unfair advantage or was unfairly detrimental. The "or" formulation again applies. The Nominet DRS also includes a mandatory mediation stage before any expert decision, which can create an early settlement opportunity unavailable in the INDRP.

For .de domains, there is no UDRP equivalent; disputes require German court proceedings, with a DENIC DISPUTE entry to block transfer while litigation proceeds. That route is substantially more expensive and time-consuming.

When a portfolio of domains spans .in alongside .com or other gTLDs, the dispute strategy must account for each zone's rules separately. A consolidated approach to evidence – building a single, coherent picture of acquisition rationale and legitimate use – serves the respondent across all forums, even when the legal test varies. In our practice, we frequently advise on multi-zone portfolios where parallel or sequential proceedings require coordinated defense.

In a 2024 matter (a .com and .in portfolio dispute, autumn 2024), we coordinated a UDRP defense for the gTLD component and a parallel INDRP response for the .in name. The complainant withdrew the INDRP filing after the UDRP panel denied the complaint, finding no evidence of targeting or bad faith.

What are the realistic outcomes, and how do you start a defense?

The realistic outcomes of a .in domain defense are: denial of the complaint (domain stays with the registrant), transfer or cancellation (complaint succeeds), or – in appropriate cases – denial with an RDNH finding. There is no monetary remedy in any direction. The decision is published and adds to the precedent record.

The defense process begins from the moment the INDRP complaint is formally commenced. The response deadline is defined by NIXI's procedural rules; verify the current deadline with counsel immediately on receiving notice. Missing the response deadline typically results in a default decision, and panels may still consider the record even in an uncontested case, but a default creates substantial risk. Acting early is the single most important practical step.

A well-structured defense response will: set out the registrant's rights and interests directly; marshal the documentary evidence across each category described above; address the bad-faith elements explicitly (both registration and use); and, where the facts support it, make the RDNH argument with full factual backing.

COGNOMEN's approach is to assess the three INDRP elements against the client's specific facts, identify the strongest safe-harbor arguments, build the evidence record, and where warranted, construct the RDNH case in the response. We do not offer generic template defenses. The outcome of a panel decision depends on the facts placed before the panel – the quality and completeness of the evidence, not the volume of the submission.

Related at COGNOMEN

• Respondent defense and RDNH across gTLDs and ccTLDs – full practice overview
• Defending a UDRP complaint filed against a domain portfolio or group of names
• URS vs. UDRP for new-gTLD disputes – a comparative analysis