Assess my case

How to prove a legitimate interest in your .in domain

By Anton Grant, Respondent defense & RDNH ·

A complainant files against your .in domain, demands a transfer, and the clock starts running. You registered the name for a real purpose – a business, a project, a personal brand – and now you must prove it. The INDRP, India's domain-dispute procedure, follows the UDRP model closely, but the forum, the eligibility rules, and the record you need to build carry their own specific requirements.

To prove a legitimate interest in your .in domain under the INDRP you must satisfy at least one of the recognized safe harbors: a bona fide offering of goods or services before notice of the dispute, being commonly known by the domain name, or a legitimate noncommercial or fair use without intent to mislead. The respondent bears a practical burden to produce evidence once the complainant makes a prima facie case. A well-constructed record – documented before, not after, the complaint arrives – is the single factor that most reliably decides the outcome.

This page sets out the governing procedure, the three safe harbors, the evidence that carries weight, when an RDNH finding is realistic, and the step you should take today.

What procedure governs .in disputes, and how does it differ from the UDRP?

The .in domain dispute framework is administered under the INDRP – the .IN Dispute Resolution Policy – which follows the same three-element structure as the UDRP but is specific to India's country-code zone and is administered through the NIXI arbitration process. The complainant must prove that the domain is identical or confusingly similar to a trademark, that the registrant has no rights or legitimate interests, and that the domain was registered or is being used in bad faith. Note the disjunctive: unlike the UDRP's cumulative "registered and used in bad faith," the INDRP reads "registered or used" – a structurally lower bar for complainants on the bad-faith limb. That asymmetry makes a strong legitimate-interest record even more important for a .in respondent than it would be under the standard UDRP.

Procedure runs through a sole arbitrator appointed by NIXI. Timelines are broadly comparable to a UDRP case, though they can stretch depending on the arbitrator's schedule and any procedural complications. The remedy is transfer or cancellation, not monetary damages. A finding that the complaint was brought in bad faith – the equivalent of RDNH in the .in context – is possible, and it matters reputationally even where no financial penalty attaches.

For domains spanning both a .in and a .com registration, a separate UDRP complaint before WIPO or the Forum may run in parallel. Those are distinct proceedings, each decided on their own record. We regularly advise registrants who face simultaneous attacks across multiple zones and need a coordinated response rather than two siloed filings.

What are the three safe harbors, and which one applies to your situation?

The INDRP's legitimate-interest safe harbors mirror Paragraph 4(c) of the UDRP and give a respondent three distinct routes to rebut a complaint. Each route requires a different type of evidence, and the right one to lead with depends on what you actually did with the domain before the dispute arose.

Safe harbor one: bona fide use before notice. If you were using the domain in connection with a genuine offering of goods or services before you received notice of the complaint, that use is protected. "Before notice" is the critical phrase. Use that began after a cease-and-desist letter, a demand email, or the commencement of the INDRP proceeding itself will not satisfy this harbor. What counts: a live website with commercial content, invoices to customers, contracts, correspondence, screenshots with timestamps, archived pages from the Wayback Machine. The offering need not be large or profitable. It needs to be real and documented.

Safe harbor two: commonly known by the name. If you – as an individual, business, or organization – were commonly known by the domain name before the dispute, you can rely on that recognition. This harbor is most available to individuals registering their own name or to businesses with a trade name that predates the trademark on which the complainant relies. Evidence here includes business registration documents, trading history, press coverage, correspondence, and anything that shows the public or your customers associated you with that name.

Safe harbor three: legitimate noncommercial or fair use. Commentary, criticism, fan sites, and informational pages may qualify, provided there is no attempt to mislead users commercially or to tarnish the mark. This harbor is the narrowest and is most heavily scrutinized by arbitrators. If your site mixes criticism with any form of commercial activity – affiliate links, advertising, pay-per-click – the line blurs quickly. Panels have consistently held that a domain pointing at a pay-per-click page that generates revenue from the trademark owner's brand does not qualify as fair use, whatever the registrant's stated intent.

Identifying which safe harbor your facts support is the first step in building a defense. For an assessment of your .in domain dispute, contact info@cognomenlaw.com.

How do you build the legitimate-interest record before the response is due?

Once the INDRP proceeding commences, the respondent must act quickly. The response window is short – the equivalent of the UDRP's 20-day deadline applies – and the record you submit with your response is, in practice, the record you have. Arbitrators do not conduct their own investigations. They decide on what the parties put before them.

We advise respondents to treat the evidence-gathering phase as a structured audit. Work through these categories in order of availability:

One common error is building the record after the complaint arrives – repopulating an empty website, backdating marketing materials, or registering a trademark in a hurry. Arbitrators recognize these post-complaint efforts and treat them with skepticism. The record that matters is the one that existed before notice.

In a recent matter (a .in domain, summer 2025), we assembled a legitimate-interest record for a registrant who had operated a small services business under the domain name for several years before a much larger company filed an INDRP complaint. The business records, archived screenshots, and a local trade-name registration together demonstrated continuous use predating the complainant's India trademark by more than two years. The arbitrator rejected the complaint and declined to transfer the domain.

When is a finding of reverse domain-name hijacking realistic in a .in case?

A reverse domain name hijacking (RDNH) finding – a declaration that the complaint was brought in bad faith to dispossess a legitimate registrant – is available under the INDRP's framework, just as it is under the UDRP. The standard is demanding: the respondent must show not merely that the complaint failed, but that it was filed knowing it lacked merit or that the complainant used the proceeding as a strategic weapon against a registrant with a clear right to the name.

RDNH findings are more likely where: the complainant's trademark rights postdate the domain registration by a significant margin; the complainant omitted known facts about the registrant's prior use; the complaint made assertions about bad faith that were contradicted by publicly available evidence the complainant plainly had access to; or the complainant filed against multiple registrants in a pattern inconsistent with a genuine rights-protection exercise.

What does an RDNH finding actually achieve? In the .in context, as under the UDRP, there is no monetary award. The finding is a formal record, however – one that other panels may reference, that the domain industry reads, and that can affect the complainant's ability to pursue similar actions credibly in the future. For a respondent defending a name with real commercial value, an RDNH finding is a meaningful vindication, not merely a procedural footnote.

We have defended registrants in proceedings where the filing was plainly opportunistic – a brand owner expanding into a new territory and filing against a local business that had operated under the name for years before the brand arrived. In those situations, we do not only aim to defeat the transfer demand. We build the record for an RDNH finding from the outset.

If a prior filing or response produced a bad outcome, a focused second read can find the element that was missed. Email info@cognomenlaw.com to discuss your position.

What evidence actually decides the outcome, and what does not?

Arbitrators assessing a .in legitimate-interest defense weigh evidence against a practical question: would a person looking at the whole record believe this registrant had a real, independent reason to hold this domain? Several categories of evidence consistently move that inquiry in the respondent's favor.

Evidence that carries weight: contemporaneous business records, especially those predating the registration; third-party confirmation of the respondent's identity and trading history; a trademark or company registration in the respondent's own name bearing the domain string; long-term uninterrupted use of the domain as an operating website; and a clear factual explanation of why the respondent registered this particular name without reference to the complainant's brand.

Evidence that tends not to move the needle: unsupported assertions that the domain was registered for a future project with no supporting documents; a newly created website launched after the complaint; a general-purpose affidavit with no specifics about dates or customers; and registrations of multiple similar domains without a coherent business explanation. Panels have consistently found that holding a domain passively, without any use, is neutral at best and negative at worst.

One category that often surprises registrants is the weight given to the timing of events. If your domain was registered years before the complainant acquired its trademark in India, that chronology is powerful. If the registration followed the complainant's public launch in India by a short interval, the arbitrator will look closely at whether you could have been aware of the mark. Documenting your registration decision – ideally in writing that predates the registration – closes that inquiry before it opens.

In a second matter (a .in domain, autumn 2024), we represented a respondent who had registered a domain matching a regional trade name used in the hospitality sector. The complainant was a foreign brand with Indian trademark rights acquired after the domain registration. We produced hotel-booking records, a signed services agreement dated before the trademark filing date, and local press coverage. The arbitrator held that the respondent was commonly known by the name and that no bad faith existed. The complaint was denied.

How does the .in defense compare to defending a UDRP complaint for a .com?

The strategic differences between defending a .in INDRP proceeding and a standard UDRP complaint before WIPO or the Forum are meaningful, and a response built for one forum does not automatically work for the other.

The most significant doctrinal difference is the bad-faith element. The UDRP requires the complainant to prove the domain was registered and used in bad faith – both limbs, cumulatively. The INDRP reads registration or use, which means a complainant can succeed even if the registration itself was entirely innocent, provided it can show the domain is currently being used in bad faith. That disjunctive standard narrows the available defense space. A respondent who acquired an aged domain in good faith but subsequently pointed it at content the complainant can characterize as bad-faith use faces a harder case under the INDRP than under the UDRP.

Procedurally, the UDRP at WIPO offers a highly structured process with published timelines, multiple arbitration centers, and an extensive body of publicly indexed decisions. The INDRP arbitration process has a smaller decision corpus, which can make predicting arbitrator reasoning harder. That uncertainty counsels in favor of a more thorough response – one that addresses every element fully, rather than relying on a well-settled consensus view that a panel will fill in from prior decisions.

Cost structure also differs. WIPO's filing fee for a single-member UDRP panel starts at USD 1,500, and legal fees for a respondent defense commonly fall in a range comparable to complainant-side work. The INDRP filing fees are set separately by NIXI and are denominated in Indian rupees; verify current fees directly with NIXI or with counsel, as they are published independently of the verified fee registry applicable to WIPO and the Forum. The practical cost of a full defense response, including evidence assembly and legal drafting, should be evaluated against the commercial value of the domain.

Where a registrant faces simultaneous complaints across a .in and a .com, WIPO handles the .com under the UDRP while the INDRP proceeding covers the .in. Those are separate records, separate arbitrators, and separate deadlines. Coordination matters: an admission in one proceeding can be cited in the other.

What is the realistic next step if you have received an INDRP complaint?

The answer is to act immediately. The response deadline is short, evidence-gathering takes time, and a default – failing to respond – almost always results in a transfer. Arbitrators decide defaults on the complainant's record alone.

The first decision is whether to respond substantively or not to respond at all. That is almost never a genuine choice. For any domain with commercial value, a well-structured defense built around a clear safe harbor, supported by contemporaneous evidence, is the only rational path. A default costs you the domain. A response preserves the possibility of retaining it.

The second decision is how to structure the response. A response that leads with the strongest safe harbor, anchors every assertion in dated documentary evidence, and addresses the bad-faith element directly – including the "registered or used" structure of the INDRP – is substantially more likely to succeed than a general denial. We build every respondent response around the specific fact pattern, the available evidence, and the arbitrator's likely analytical framework.

The third decision, for registrants whose facts support it, is whether to seek an RDNH finding. That requires a separate affirmative showing and is worth pursuing only where the evidence of the complainant's bad faith is strong. We assess that question at the outset, not as an afterthought.

If you have not yet received a complaint but hold .in domains that may draw attention – because they match a brand, contain a trademark term, or were acquired as part of a portfolio – pre-dispute preparation matters. Documenting your registration intent, maintaining active use, and monitoring for incoming complaints before they commencement preserves your options.

Related at COGNOMEN

Frequently asked questions about proving a legitimate interest in a .in domain

What are the chances to prove a legitimate interest in your .in domain?

No outcome can be guaranteed; the result turns entirely on the facts, the evidence assembled, and the arbitrator's assessment of the record. Registrants who can show documented pre-complaint use, a corresponding business identity, or a clear factual basis for registration that is independent of the complainant's trademark consistently perform better. A well-constructed response built around the applicable safe harbor is the single most controllable factor in the outcome.

What evidence do I need to prove a legitimate interest in your .in domain?

The most valuable evidence is contemporaneous and predates the complaint: business registration documents, invoices, dated website screenshots or Wayback Machine archives, contracts, correspondence, and any trademark or trade-name registration in your own name corresponding to the domain. Evidence of continuous and genuine use is more persuasive than volume. Anything created after you received notice of the dispute will be scrutinized closely and carries significantly less weight.

Can I prove a legitimate interest in your .in domain without going to court?

Yes. The INDRP is an administrative arbitration procedure, not a court proceeding. A successful defense is decided entirely within that administrative process, and the arbitrator has authority to reject the complaint and confirm the domain remains with the registrant. Court action in India is a separate route available to either party and is not required to establish a legitimate interest under the INDRP. Most .in domain disputes are resolved through the arbitration process alone.

About COGNOMEN

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. Our practice is exclusively domain disputes; we do not handle general IP or trademark prosecution, which means every matter we take on is assessed against a deep cross-zone knowledge base. To discuss a .in domain dispute or any domain matter, contact info@cognomenlaw.com.

Author: — Respondent defense and reverse domain name hijacking (RDNH). Meet the team.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

No obligation. Confidential. We reply within two hours in business hours.

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.