How to respond to a UDRP complaint within the deadline for a .in doma…

How to respond to a UDRP complaint within the deadline for a .in doma. UDRP and ccTLD domain recovery and defense across .in. Email the firm to assess your cas…

A UDRP complaint lands in your inbox. The domain is a .in registration you acquired legitimately, built a business around, or held as a portfolio asset for years. The complainant's filing looks polished. The deadline feels immediate. What you do in the next 20 days determines whether you keep the domain or lose it to a transfer order you cannot reverse through the same procedure.

To respond to a UDRP complaint within the deadline for a .in domain, you must file a written response with the appointed dispute-resolution provider before the 20-day response window closes after formal commencement. The applicable procedure for .in is the IN Domain Name Dispute Resolution Policy (INDRP), India's ccTLD-specific adaptation of the UDRP model, administered by the National Internet Exchange of India (NIXI). The response must address all three elements of the policy's test: confusing similarity, rights or legitimate interests, and bad faith. Defaulting — filing nothing — is not a neutral act; panels regularly draw adverse inferences from silence.

This page covers the INDRP procedure and its relation to UDRP mechanics, the safe harbors that protect legitimate registrants, the evidence that decides outcomes, the realistic path to a Reverse Domain Name Hijacking finding, and what your next step should be if the clock is already running.

What Governs .in Disputes – and How the INDRP Differs From the UDRP

The INDRP is the dispute-resolution policy binding all .in domain registrations. NIXI administers the process through an arbitration mechanism rather than the panel-opinion model used by WIPO or the Forum for .com disputes. That distinction matters practically. INDRP proceedings are conducted under the Indian Arbitration and Conciliation Act as the procedural backdrop, which gives the proceeding a quasi-judicial character that pure UDRP arbitration at WIPO does not carry. Remedies available under the INDRP include transfer or cancellation of the domain; as with the UDRP, monetary damages are not available through this route.

The substantive test mirrors the UDRP's three-element structure. The complainant must establish that (1) the domain is identical or confusingly similar to a trademark or service mark in which the complainant has rights; (2) the registrant has no rights or legitimate interests in the domain; and (3) the domain has been registered or is being used in bad faith. That third limb is significant: some national ccTLD policies read the bad-faith element as "registered or used" — a lower threshold than the UDRP's cumulative "registered and used." Practitioners handling .in disputes should verify the current INDRP text with counsel, because the disjunctive reading affects how aggressively a respondent must rebut each limb separately. In our practice, we treat each limb of the bad-faith element as independently contestable unless the policy is confirmed otherwise.

One further structural note: because the INDRP draws on domestic arbitration law, decisions can in principle be subject to challenge in Indian courts, a procedural avenue that has no direct equivalent in UDRP proceedings at WIPO or the Forum. That does not make the INDRP softer — but it does mean the decision sits within a national legal order rather than operating as a purely contractual remedy between the registrant and the registry.

Why the 20-Day Response Deadline Is Not Negotiable

The 20-day response window is set by the procedural rules of the applicable provider and begins running from formal commencement — the date the provider notifies the registrant that the case has been accepted and the complaint is in proper form. That date is not necessarily the date you first saw the email. Check the commencement notice from the provider directly; that document controls the deadline, not the date stamp on the complaint itself.

What happens if you miss the deadline? The panel or arbitrator proceeds on the record as submitted by the complainant. Panels across UDRP-model procedures have consistently noted that a default is not an automatic grant of the remedy — the complainant still bears the burden of proving all elements. But in practice, an unanswered complaint means no rebuttal of the complainant's trademark evidence, no legitimate-interest record placed before the panel, and no explanation of the registration's purpose. Panels regularly infer that uncontested allegations are credible. The asymmetry is severe.

Extensions are rare and require demonstrated cause. Do not rely on obtaining one. If you received the commencement notice and the clock is already running, your first call should be to counsel today, not after you have assembled documents on your own schedule.

If the commencement notice has already arrived and your .in domain is at stake, do not wait. Contact info@cognomenlaw.com for an immediate assessment of the three elements and the strongest grounds for your response.

How to Build a Legitimate-Interest Record Under Paragraph 4(c) Safe Harbors

The second element of the INDRP test — rights or legitimate interests — is where most respondent defenses are won or lost. The burden of proof on this element sits with the complainant initially, but once a complainant makes a prima facie case, the burden shifts to the respondent to produce evidence of legitimate interest. Producing that evidence is the core task of a competent response.

The safe harbors recognized across UDRP-model policies, including the INDRP, are drawn from Paragraph 4(c) of the UDRP and its equivalents. Three categories provide the clearest protection:

• Bona fide offering before notice: You were using the domain in connection with a genuine offering of goods or services before you received any notice of the dispute. Evidence here includes website archives, invoices, customer correspondence, and business registration documents predating the complaint. The keyword is before notice — use that began after you received a cease-and-desist or the complaint itself does not satisfy this limb.
• Commonly known by the name: You or your entity are commonly known by the domain name, regardless of whether you hold a registered trademark. Personal names, business trading names, and brand identities established prior to the complainant's trademark rights can all qualify. Documentary proof — business filings, press coverage, social media history, correspondence with customers — builds this record.
• Legitimate noncommercial or fair use: You are making a genuine noncommercial or fair use of the domain, without intent to mislead consumers for commercial gain or to tarnish the trademark. This applies most frequently to criticism sites, fan sites, and commentary, but the line between legitimate commentary and commercial exploitation is contested and fact-intensive.

In our experience defending respondents across UDRP-model procedures, the single most common failure is an incomplete evidentiary record. The response states the conclusion — "we have legitimate interests" — but delivers few documents the panel can rely on. Panels cannot assume facts into the record; they can only weigh what is actually before them. Every factual assertion in the response needs a supporting exhibit.

For a .in domain specifically, evidence of a genuine India-market nexus strengthens the record further. Registration of an Indian entity, customer lists from India, invoices issued in India, or a regulatory filing in India — any of these adds weight to the claim that the .in domain was chosen because it speaks to an Indian audience, not because it mimics a foreign complainant's brand.

What Evidence Actually Decides the Outcome?

Beyond the legitimate-interest record, the response must squarely address bad faith — and, where the complainant's case is thin, the absence of bad faith. Evidence that consistently moves panels includes the following categories.

Registration history and chain of title. When was the domain registered? What was the state of the complainant's trademark rights at that date? A domain registered before a complainant obtained trademark rights is a powerful rebuttal to any bad-faith finding based on targeting the mark. Pull the WHOIS/RDDS historical data, the registration confirmation from your registrar, and any trademark office records showing when the complainant's mark first achieved registration or acquired distinctiveness in India or globally.

Dictionary, descriptive, or geographic terms. If the domain is composed of a common word, a descriptive phrase, or a geographic term, that goes directly to whether the registration was targeting a specific mark at all. The .in TLD itself is frequently chosen for its double meaning — it is India's ccTLD and also the English preposition — and a domain that legitimately exploits either meaning undercuts the targeting argument.

Commercial conduct since registration. Panels look at what the domain was actually doing. Parking pages that serve pay-per-click advertising in the complainant's industry sector are frequently cited as evidence of bad faith. By contrast, a domain forwarding to an active business site, hosting original content, or sitting idle without monetization presents very differently. Archive.org records, Google Analytics exports, and hosting records help establish the usage timeline.

The complainant's notice to you. Did you receive a cease-and-desist before the complaint was filed? What did it say, and what did you do in response? An offer to sell at an unreasonably high price after receiving notice cuts against you; a good-faith engagement with the complainant's concerns, or a considered refusal on principled grounds, cuts for you.

In a recent matter — a .in portfolio domain, summer 2025 — we assembled a response demonstrating that our client's registration predated the complainant's trademark application by more than three years and that the domain had hosted active business content continuously. The arbitrator found no bad faith and denied the transfer request.

When Is a Reverse Domain Name Hijacking Finding Realistic?

Reverse Domain Name Hijacking (RDNH) is a finding that the complainant brought the proceeding in bad faith, primarily to deprive a legitimate registrant of a domain. An RDNH finding is reputational — there is no monetary penalty under the UDRP or the INDRP — but it carries weight. It signals to the domain industry and to the complainant's own counsel that the filing was an abuse of the procedure, and it creates a public record that can deter future overreach.

When should you affirmatively seek an RDNH finding? The pattern that most often produces one involves a complainant who held its trademark rights after the domain was registered, who should have known it had no colorable bad-faith case but filed anyway, and who framed its complaint in a way that misrepresented or omitted material facts. Panels have found RDNH in cases where the complainant's mark was registered long after the domain; where the respondent's use was demonstrably bona fide and obvious from a basic WHOIS search; and where the complaint essentially sought to claw back a generic or descriptive term the market had settled on.

RDNH is not available simply because you win your defense. You must affirmatively request it and develop the argument in the response. The request should identify specifically what the complainant knew or should have known, what it misrepresented or omitted, and why the filing served no legitimate purpose under the policy. In our practice, we include a structured RDNH section whenever the facts support one — because a panel cannot make the finding without a record to support it.

If the complaint against your .in domain looks overreaching — filed on a weak trademark, filed after your registration date, or filed on a generic term — email info@cognomenlaw.com to assess whether an RDNH argument belongs in your response.

How Does .in Defense Compare to UDRP Defense at WIPO or the Forum?

The choice of procedure is not yours to make — the .in zone means the INDRP governs, not the UDRP rules at WIPO or the Forum. But understanding the differences matters for two reasons: it shapes how you frame the response, and it informs what happens if the dispute also involves a .com or other gTLD registration of the same name.

For a standalone .in dispute, the arbitration character of the INDRP means the proceeding has a formal legal footing in Indian law. If the outcome is adverse and the arbitrator's decision is challenged in an Indian court, that challenge follows domestic arbitration procedure — a significant distinction from UDRP decisions, which can in practice only be overturned by a court of competent jurisdiction that takes the case de novo. The practical implication: a .in respondent who has strong facts and deep legitimate-interest evidence may have more judicial recourse than a UDRP respondent in a comparable gTLD dispute.

If the same complainant also holds or pursues a .com for the same name, that parallel dispute follows the UDRP at WIPO (filing fee from USD 1,500) or the Forum (filing fee from approximately USD 1,300). Strategy in the .in proceeding and any parallel gTLD proceeding should be coordinated — inconsistent factual claims across proceedings are a liability.

Where no dispute procedure exists or the available remedy is insufficient — for example, where the registrant seeks damages alongside a domain transfer — court action in India is the alternative route. That litigation would be handled with local litigation counsel in the relevant jurisdiction, coordinated with the broader strategy COGNOMEN develops for the matter.

Step-by-Step: What a Competent .in Domain Response Looks Like

A strong response to a .in domain dispute is not a form document. It is a structured argument that addresses each element the complainant has alleged, deploys every available safe harbor, and supports each factual claim with evidence the arbitrator can weigh. Here is the sequence we follow.

1. Verify the commencement date and calculate the hard deadline. Pull the provider's commencement notice and confirm the 20-day window precisely. Mark the filing deadline and work backwards from it — a response assembled in hours at the deadline is weaker than one prepared over several days with supporting exhibits.
2. Analyze the complaint element by element. Read every paragraph of the complaint against the three-element test. For each element, identify what the complainant asserts, what evidence it offers, and where the gaps or misrepresentations are. This analysis drives the response structure.
3. Collect the legitimate-interest evidence. Gather registration records, business filings, invoices, website archives, customer correspondence, and any other documents showing bona fide use or recognition as a name before notice of the dispute. Organize these as numbered exhibits.
4. Build the bad-faith rebuttal. Pull the WHOIS history, the trademark registration dates of the complainant's marks, and any archive records of the domain's usage since registration. Prepare a chronological record that the arbitrator can follow without ambiguity.
5. Assess the RDNH argument. If the facts support it, draft a specific, evidence-backed section requesting a finding of RDNH. Identify what the complainant knew, what it misrepresented, and why the filing was abusive rather than merely unsuccessful.
6. Decide on panel composition. Under UDRP-model rules, a respondent can in many procedures request a three-member panel even if the complainant requested a single panelist — typically at shared cost. For high-value domains or complaints where the panel composition could change the outcome, this option deserves deliberate consideration.
7. File the response before the deadline. Confirm receipt from the provider. Do not assume filing is complete until you have a formal acknowledgment.

In a .in matter from spring 2025, a registrant had held a two-word .in domain for a business in the travel sector for approximately six years before a European trademark holder filed a complaint. We assembled a response covering all three elements, presented seven years of website archive evidence and client correspondence, and built a chronological trademark timeline that placed the complainant's India-market rights after the domain's registration date. The arbitrator denied the transfer and found the complaint without merit on the bad-faith element.

What Are the Common Failure Modes in .in Respondent Defenses?

Respondents lose defensible cases. This is the pattern we see most often, and each failure is avoidable.

Filing no response at all. The reasoning is understandable — the proceeding looks expensive, the odds seem uncertain, or the domain feels like a minor asset. But defaulting removes your legitimate-interest argument entirely and leaves the panel only with the complainant's evidence. Even a basic response preserves the record and forces the arbitrator to find all three elements met on the complainant's evidence alone, which is not always possible.

Responding with a legal argument only and no evidence. Panels operate on the record. Asserting that you have rights or legitimate interests, without submitting documents showing what those rights are and when they arose, is not a defense — it is an assertion. The response must exhibit the underlying facts.

Offering to sell the domain in the response. If the complaint alleges you registered the domain to sell it to the complainant, a response that includes an offer to sell at a price confirms the allegation. Keep any settlement discussions entirely separate from the formal response.

Misreading the deadline as calendar days from receipt of the complaint. The 20-day window begins from formal commencement by the provider, not from the date you first saw the email or the complaint document. Verify the commencement notice date directly.

Ignoring India-specific evidence of nexus. For a .in domain, the India-market connection of the registration is highly relevant. Omitting India-specific business evidence when it exists leaves the record thinner than it needs to be.

Related services at COGNOMEN

• UDRP and ccTLD respondent defense – full service across gTLDs and national zones
• Fair-use and descriptive-term defense for domain registrants facing abusive complaints
• Domain transactions, due diligence, and escrow structuring for buyers and sellers