Step-by-step: defend a .in domain against a UDRP complaint

Step-by-step: defend a .in domain against a UDRP complaint. UDRP and ccTLD domain recovery and defense across .in. Email the firm to assess your case.

Twenty days. That is how long a registrant has to file a response once a UDRP complaint against a .in domain formally commences – and every day that passes without a plan is a day closer to a default transfer order. India's .in country-code zone operates its own dispute-resolution procedure, the INDRP, which tracks the UDRP closely but is not identical to it. Understanding where the rules diverge – and what the safe harbors actually require – is the difference between keeping a domain and losing it to an opportunistic complainant.

To defend a .in domain against a UDRP complaint you must respond within 20 days of commencement, invoke the Paragraph 4(c) safe harbors that establish your legitimate interest, and assemble evidence that the registration was made in good faith. The governing procedure for .in is the INDRP, administered through the National Internet Exchange of India (NIXI), which applies a three-element test closely mirroring the UDRP's Paragraph 4(a). A well-documented defense can also seek a finding of Reverse Domain Name Hijacking (RDNH) where the complaint is abusive.

This guide walks each step of the defense process – from the moment the complaint lands to the decision and beyond – and names the trap concealed in each one.

What governs a .in domain dispute, and how does the INDRP differ from the UDRP?

The INDRP applies to all .in registrations, administered by NIXI with arbitration conducted under the Arbitration and Conciliation Act of the relevant jurisdiction. For a respondent this distinction matters: unlike a UDRP panel, an INDRP arbitrator operates within a statutory arbitration framework, which means procedural formalities carry more weight and a poorly framed response can be treated as a waiver. The substantive test, however, is substantially the same three-element structure as the UDRP.

The complainant must prove: (1) the domain is identical or confusingly similar to a trademark or service mark in which it has rights; (2) the registrant has no rights or legitimate interests; and (3) the domain was registered or is being used in bad faith. Notice the "or" in the third element. Under the INDRP the bad-faith limb reads as registered or used – a materially lower bar for complainants than the UDRP's cumulative "registered and used." A domain registered entirely in good faith can still be lost if current use is later found abusive. Build the defense around both limbs from day one.

One further difference: INDRP decisions are subject to challenge in Indian courts, which creates an appeal avenue that pure UDRP cases lack. That avenue is rarely quick or inexpensive, but it exists. We regularly advise registrants to factor that option into their strategy when the stakes justify it.

Step 1 – Read the complaint immediately and record the deadline

The single most common trap at this stage is treating the 20-day response window as a rough guide rather than a hard deadline. It is not. Under the INDRP Rules the respondent has 20 days from the date the complaint commences to file a response. Missing the deadline means the arbitrator will almost certainly proceed to a default decision on the complainant's evidence alone.

Within the first 24 hours of receiving the complaint, confirm four things. First, the exact date the case commenced – this is the date of formal commencement notice from NIXI, not the date the complaint was filed by the complainant. Second, whether the domain registration details the complainant has cited are accurate; errors in WHOIS/RDDS data have been used against respondents as evidence of concealment. Third, what trademark the complainant relies on: a registered mark, an unregistered mark, or both. Fourth, which forum or body is administering the case, since NIXI engages an arbitrator rather than a standing panel, and the identity of the arbitrator matters for strategy.

An extension request is possible in limited circumstances, but it requires prompt action and a credible reason. Waiting until day 17 to ask is too late to be effective.

Step 2 – Establish which Paragraph 4(c) safe harbor applies to your registration

Your legitimate interest is the core of the defense. The INDRP, like the UDRP, recognizes three safe harbors under Paragraph 4(c): a bona fide offering of goods or services before notice of the dispute; being commonly known by the domain name; and legitimate noncommercial or fair use. Each one carries its own evidentiary trap.

The bona fide-use harbor is the most frequently invoked – and the most frequently lost, because respondents confuse activity with bona fide activity. A parked page that generates pay-per-click revenue from the complainant's own competitors does not qualify. A domain used for a genuine business – invoices, a client list, a service description, dated correspondence – does. Gather those records now, before you draft a single line of the response. Dated invoices, screenshots, contracts, and incorporation documents all carry weight. The trap: evidence created after the complaint was filed is discounted heavily.

The commonly-known-by harbor applies where the registrant is an individual, business, or organization that has been known by the domain name even without a trademark. This is particularly relevant for personal names, family surnames, and businesses operating informally. What decides it: third-party recognition, contemporaneous documents, social media history predating the trademark's filing date.

The fair-use harbor protects legitimate commentary, criticism, and noncommercial fan sites, provided the registrant is not misleadingly diverting commercial traffic. The trap here is dual: commentary must be genuinely noncommercial, and the domain itself must not create a false impression of affiliation with the mark owner.

Whichever safe harbor you invoke, the evidence record must predate the date the complainant can show it first had trademark rights. If the complainant's mark predates your registration, you need a compelling legitimate-interest narrative. If your registration predates the mark, the entire third element collapses – document that date discrepancy prominently.

How do you build a legitimate-interest record that actually holds up?

Evidence quality, not evidence volume, decides these proceedings. An arbitrator reviewing a default can be moved by a single well-dated document. An arbitrator reviewing a 200-page submission without a coherent narrative is not.

Structure the legitimate-interest record in three layers. The first layer is documentary: registration history (WHOIS historical records, screenshots, registrar confirmation), business records (incorporation, licenses, filing dates), and commercial activity (invoices, customer correspondence, product listings). The second layer is temporal: arrange every document on a timeline that begins before the complainant's trademark. Every item that postdates the trademark needs an explanation. The third layer is contextual: explain why someone with no connection to the complainant would register this domain – the generic meaning of the term, the industry you operate in, the geographic or linguistic context. Generic and descriptive terms make strong respondent cases because they have obvious legitimate uses beyond the complainant's mark.

In a recent matter (a .in registration for a common descriptive term, early 2025), we built a defense showing the registrant had operated a services business under the term for several years before the complainant's trademark application was even filed. The response combined a business registration certificate, dated client invoices, and archived website screenshots. The complaint failed at the second element. No RDNH finding was sought, but the outcome was complete: the domain remained with the registrant.

The trap in this step: respondents sometimes hold back documents because they seem irrelevant or embarrassing. Anything that is contemporaneous and authentic should be disclosed. Selective disclosure is visible to an experienced arbitrator and can be read against you.

Step 3 – Identify and respond to the bad-faith allegations specifically

A complainant asserting bad faith under the INDRP will typically point to one or more of the Paragraph 4(b) circumstances: registration to sell to the mark owner for a profit above cost; registration to disrupt a competitor; registration to attract users for commercial gain by creating confusion; or a pattern of abusive registrations. Each allegation needs a direct, evidence-backed answer.

If the complainant alleges you offered to sell the domain for a large sum, confirm whether any such communication occurred and in what context. An unsolicited approach by the complainant followed by a commercial response is not the same as registering a domain to extract money. Document the sequence. If the complainant alleges confusion-based bad faith, address any parking-page content directly – explain what it showed, when, and whether it was under your control. Third-party PPC systems that auto-populate a parked domain with related advertising are a genuine trap: panels and arbitrators regularly find bad faith even when the registrant did not choose the specific advertisements.

For the "registered OR used" formulation in the INDRP, consider both directions separately. If registration was clearly in good faith, say so with evidence and explain why. Then address current use explicitly. If the site currently holds content that could be read as trading on the complainant's mark, change it immediately (document the change with a screenshot and timestamp) and address the prior state in your response.

When is a Reverse Domain Name Hijacking finding realistic?

RDNH – a panel or arbitrator finding that the complaint itself was brought in bad faith – is available under both the UDRP and the INDRP. It carries no monetary penalty. The reputational consequence for the complainant is real, however, and an RDNH finding on record deters future abusive filings against the same registrant.

RDNH is realistic in three fact patterns. First, where the complainant's trademark postdates the registration by a significant margin and the complainant knew or should have known it could not make out the bad-faith element. Second, where the complainant is a sophisticated rights-holder with UDRP experience and is using the procedure as a low-cost substitute for a negotiated acquisition. Third, where the complaint materially misrepresents facts – a cooked timeline, an omitted prior proceeding, or a cherry-picked WHOIS record.

We have defended .in and gTLD registrants against complainants that fit the second pattern: large brand owners filing INDRP or UDRP proceedings against domains registered years before their trademark, with the primary goal of avoiding a market-rate purchase. In those situations we seek RDNH explicitly and frame the entire response around it.

The trap: RDNH is not a fallback argument to raise in the last paragraph of a response. It must be argued affirmatively, with evidence, and the response structure should lead the arbitrator to that conclusion well before the final request for relief.

For a broader view of how to prove legitimate interest in the context of respondent defense, see our guide to building a legitimate-interest record.

If you have received a UDRP or INDRP complaint against a .in domain, the response window is short and the first steps are the most consequential. For an assessment of whether your registration is defensible – and whether an RDNH claim is worth pursuing – contact info@cognomenlaw.com.

Step 4 – Decide on a single-member arbitrator or a three-member panel

Under the INDRP, as under the UDRP, the default appointment is a single arbitrator. The respondent may request a three-member panel. This matters strategically. A three-member panel offers a broader range of views, is statistically less likely to produce a default on a borderline case, and is generally preferred when the domain is of significant commercial value or when RDNH is being actively argued.

The cost trade-off is real. If the complainant requested a single arbitrator and the respondent requests three members, the parties typically split the higher fee. The official fee structure for .in/INDRP proceedings – including any split cost arrangements – should be confirmed directly with NIXI at the time of filing, as fees have changed over time and the current schedule governs. Do not budget based on outdated figures.

The trap in this step: respondents sometimes decline a three-member panel to save money on a case worth far more than the incremental fee difference. Evaluate that trade-off on the domain's value, not on the filing fee alone.

Step 5 – File the response and follow up on the record

The response document itself must be precise, organized, and evidenced. An INDRP arbitrator is operating under an arbitration framework that rewards procedural care. The structure should follow the three elements of Paragraph 4(a) in sequence, addressing each one with a clear position and the supporting evidence referenced by exhibit number.

After filing, confirm receipt from NIXI and verify that all exhibits were received in their entirety. The arbitration record is closed at the point of filing; supplemental submissions are permitted only in limited circumstances and are frequently rejected. If there is a material document you realize you omitted, contact the administering body immediately to assess whether a supplement is procedurally possible.

Following the arbitrator's appointment, monitor for any procedural communication. Some arbitrators issue procedural orders or requests for clarification. Missing one of those is a trap that can shift the record against a respondent who would otherwise have won.

What are the realistic outcomes, and what happens after a decision?

The INDRP's remedies mirror the UDRP: transfer to the complainant, cancellation of the domain, or – for the respondent – a decision that the complaint failed, leaving the domain in place. An RDNH finding may accompany a dismissal. There are no damages and no costs awards under either procedure.

A decision in the complainant's favor triggers a registrar lock and eventual transfer. The registrant has a brief window – typically ten business days under the standard implementation period – during which a court filing in the relevant jurisdiction can stay the transfer. Given that INDRP decisions are subject to challenge in Indian courts, a registrant with strong grounds and high-value domain has a real, if expensive, post-decision option that does not exist under a pure UDRP ruling.

A decision in the respondent's favor simply closes the proceeding. The complainant can refile only if circumstances change materially – a new trademark registration, a change in how the domain is being used. In practice a well-reasoned dismissal, particularly one accompanied by an RDNH finding, effectively ends the dispute.

In a matter involving a .in domain for a descriptive business term (spring 2025), the respondent's record of pre-dispute commercial use was sufficiently clear that the arbitrator dismissed the complaint at the legitimate-interest element without reaching bad faith. The RDNH argument was included in the response but not ultimately addressed; the dismissal was the outcome sought, and it was achieved.

If a prior INDRP or UDRP filing produced an adverse outcome, or if a current complaint presents a complex fact pattern, contact info@cognomenlaw.com to assess whether a focused second review can identify what was missed.

UDRP versus INDRP: which rules actually apply to your .in domain?

The right route depends on what the complainant filed and where. A complainant targeting a .in domain has two realistic options. It can file under the INDRP before NIXI – the dedicated procedure for the .in zone. Or, if the same registrant also holds an identical or confusingly similar gTLD domain, it may file a combined UDRP complaint covering both the .com and the .in, provided the registrant is the same holder of record.

A combined UDRP filing against a .in domain is uncommon but procedurally possible where the ccTLD has effectively adopted the UDRP or where WIPO has been appointed as a provider. Verify with counsel which procedure actually governs the complaint you received. If the complaint header references NIXI and the INDRP Rules, the procedure is the INDRP. If it references WIPO or the Forum and the UDRP Rules, the applicable procedure – and the applicable substantive test – may differ from what is described in this guide.

For a comparison of the URS suspension remedy with the UDRP transfer remedy – relevant for registrants holding new-gTLD registrations alongside a .in – see our FAQ on URS versus UDRP. And for the full respondent-defense service, including .in and cross-zone matters, see our respondent defense and RDNH service page.

Related at COGNOMEN

• Respondent defense and RDNH – full service across gTLDs and ccTLDs
• How to build a legitimate-interest record for a UDRP or INDRP defense
• URS versus UDRP: suspension versus transfer compared