How to defend a .in domain registered before the complainant's tradem…

How to defend a .in domain registered before the complainant's tradem. UDRP and ccTLD domain recovery and defense across .in. Email the firm to assess your cas…

A brand owner files an INDRP complaint against your .in domain. You registered the name years before their trademark existed. The demand looks routine — but the chronology is on your side, and that changes everything.

To defend a .in domain registered before the complainant's trademark, you must show under the INDRP — India's ccTLD dispute policy, which closely mirrors the UDRP — that the complainant cannot satisfy all three elements of the policy's conjunctive test. Because the bad-faith limb requires registration and use in bad faith, a registration that predates the mark defeats the complaint on its face, provided you can document the timeline and your legitimate interest. The INDRP respondent has 30 days to file a reply once the proceedings formally commence. An RDNH finding is also available under the INDRP where the complaint was filed abusively.

This page covers how the INDRP applies to your situation, how to build the record that wins, what evidence decides the outcome, and when an RDNH finding is realistic — along with the next step if you are facing a complaint now.

What Governs .in Disputes, and Why Your Registration Date Is the Key Variable

The INDRP — the .IN Dispute Resolution Policy — is the governing procedure for .in domain disputes, administered by the National Internet Exchange of India (NIXI) through its appointed arbitrators. It tracks the UDRP closely: a complainant must prove (1) the domain is identical or confusingly similar to a trademark in which it has rights; (2) the registrant has no rights or legitimate interests; and (3) the domain was registered and is being used in bad faith. That third element is written conjunctively. Both limbs must be established.

Registration date is therefore the pivot. Where a registrant held the .in name before the complainant's mark was filed — let alone registered — the bad-faith-registration limb ordinarily fails as a matter of logic. A registrant cannot have registered a domain in bad faith with respect to a trademark that did not yet exist. This principle is well-settled across UDRP jurisprudence and is applied under the INDRP by analogy. Panels have consistently held that a complainant who acquires rights after the registration date carries a near-impossible burden on the third element.

There is one important qualification. Panels sometimes look past the registration date when a domain is later renewed or transferred after the complainant's mark arose, particularly where the renewal or transfer appears designed to exploit the reputation. If your registration has been held continuously, without gaps in registrant identity, the chronological defense is strong. If there was a lapse or a change in registrant, the analysis becomes more nuanced and the record needs to address those facts directly.

We regularly advise .in registrants who receive INDRP complaints asserting marks that postdate the registration by years. In our practice, the registration date — when properly documented and presented — is often the dispositive fact that turns a seemingly routine complaint into a clear respondent win.

How Does the INDRP Procedure Work, and What Are the Deadlines?

The INDRP procedure begins when NIXI receives a complaint and formally commences proceedings. From that commencement date, the respondent has 30 days to file a reply. That window is narrow; assembly of evidence and preparation of submissions must begin immediately. Unlike the UDRP's 20-day response window, the INDRP gives respondents slightly more time — but INDRP arbitration is conducted under Indian arbitration law, which means procedural formalities matter more than in a standard UDRP proceeding.

The arbitrator is appointed from NIXI's panel. A single arbitrator decides most cases; a three-member tribunal is available but rarely invoked. The remedy, if the complaint succeeds, is transfer or cancellation of the .in domain — exactly as under the UDRP. No monetary award is available, and no injunction issues. If the complaint fails and the arbitrator finds it was brought abusively, an RDNH-equivalent finding can be made.

What does "abusively" mean here? The INDRP, like the UDRP, recognizes that some complainants use the procedure to strip legitimate registrants of names they have every right to hold. A complainant who filed a complaint knowing the mark postdated the registration — or who deliberately suppressed that chronology — is a strong candidate for a finding of reverse domain name hijacking (RDNH). Such a finding carries reputational consequences for the complainant, even though it carries no monetary penalty.

The total timeline from filing to decision under the INDRP is typically shorter than a UDRP case, though the procedure has at various times experienced administrative delays. Work with the assumption that the process will move quickly once an arbitrator is appointed, and plan your evidence accordingly.

If you have received an INDRP commencement notice and your registration predates the complainant's trademark, the response window is already running. For an immediate assessment of the three elements and your RDNH prospects, contact info@cognomenlaw.com.

How Do You Build the Legitimate-Interest Record Under the INDRP?

A strong chronological defense rests on documentation, not just assertion. The INDRP adopts the UDRP's Paragraph 4(c) safe harbors, meaning a respondent can demonstrate legitimate interest by showing: (i) before notice of the dispute, a bona fide offering of goods or services in connection with the domain; (ii) being commonly known by the domain name; or (iii) legitimate noncommercial or fair use. Combining the registration-date defense with one of these safe harbors produces the most durable response.

What constitutes a "bona fide offering"? The phrase has been interpreted broadly across UDRP and INDRP cases. It does not require a fully operational commercial website. It requires use — or demonstrable preparation to use — in connection with a genuine business or project. Screenshots of the site as it existed at and after registration, archived web captures from services such as the Wayback Machine, email correspondence showing the domain was in active use, invoices or client records referencing the domain, business registration documents, and any published material tying the name to a legitimate activity all serve the purpose.

Where a registrant is commonly known by the name — a personal name, a business trade name, a community identifier — supporting evidence includes government-issued business registrations, commercial directories, press mentions, and any formal correspondence in which third parties addressed the registrant by the name. A sole trader operating under a personal name that predates the complainant's mark is in a particularly strong position.

Compile the evidence in chronological order. The arbitrator reads a mass of material quickly; a clear timeline — domain registered on Date A, site active by Date B, complainant's trademark filed on Date C — is far easier to evaluate than a disorganized bundle. We have found that presenting the chronology as a simple table, supported by dated exhibits, significantly sharpens the response.

What Evidence Actually Decides the Outcome?

The single most important exhibit is the WHOIS registration date, ideally accompanied by the original registration confirmation email or registrar receipt. That alone establishes the chronological sequence. Against it, place the complainant's trademark certificate showing the application or registration date — this will almost always be part of the complaint itself, and it will often reveal the postdating problem.

Beyond the date evidence, arbitrators look at several secondary factors. First: what was the registrant doing with the domain at the time of registration and in the months that followed? A domain parked at a monetization service immediately after registration, with pay-per-click links targeting the complainant's sector, tells a different story than a domain used for a genuine project. Even if the complainant's mark postdated the registration, passive holding combined with commercial exploitation in the mark's space can complicate the analysis.

Second: is the domain name itself descriptive or generic? A domain consisting of a common dictionary word, a geographic term, or an abbreviation with multiple plausible meanings is harder to characterize as targeting a trademark that did not yet exist. The more descriptive the name, the stronger the argument that the registration was opportunistic in a legitimate sense — chosen because it described the registrant's own business, not because it anticipated someone else's.

Third: what was the complainant's reputation at the date of registration? Even where no formal trademark existed, a complainant with substantial common-law reputation at the time of registration may argue the registrant knew of that reputation and registered in anticipation of it. This is a harder case for the respondent. But where the complainant was genuinely unknown or newly formed at the date of registration, the bad-faith case effectively dissolves.

In a recent matter — a .in domain dispute, spring 2025 — we assembled a record showing our client had registered the name more than four years before the complainant applied for its trademark, had maintained an active website throughout, and had no connection to the complainant's industry. The complaint was denied, and the arbitrator noted the complaint should not have been filed once the registration history was known. That observation positioned us for an RDNH argument, which we formally pressed in a supplemental submission.

When Is an RDNH Finding Realistic Under the INDRP?

Reverse domain name hijacking (RDNH) — a finding that the complaint was brought in bad faith to dispossess a legitimate registrant — is not granted lightly. But where the chronological gap is wide and the complainant is a sophisticated entity represented by counsel, the case for RDNH is materially stronger.

Panels across UDRP and INDRP proceedings have found RDNH where: (a) the complainant's trademark clearly postdated the registration and that fact was visible from publicly available WHOIS data; (b) the complainant misrepresented the timeline or omitted the registration date from its submissions; (c) the complaint made no serious attempt to distinguish the respondent's documented legitimate use; or (d) the claim relied on a trademark obtained after the dispute arose, specifically to manufacture standing.

An RDNH finding under the INDRP is a reputational sanction. No monetary penalty attaches. But it is published in the case record and sends a signal — to the complainant, to their counsel, and to the broader dispute-resolution community — that the complaint was abusive. For respondents who anticipate repeat targeting by the same complainant across multiple zones, an RDNH finding also strengthens the position in later disputes.

We have defended multiple .in and gTLD registrants against complaints where the complainant's trademark postdated the registration. In our practice, we formally seek RDNH where the gap exceeds two years and the complainant was represented — because at that point, a competent review of the public record would have revealed the registration predate.

If you believe the complaint against your .in domain was filed abusively, email info@cognomenlaw.com to assess the RDNH prospects alongside the substantive defense.

How Does the .in Defense Compare to UDRP Defense for a .com or New gTLD?

The right route depends on the zone. If the domain at issue is a .com registered before the complainant's trademark, the UDRP at WIPO or the Forum applies. The response window is 20 days from commencement, compared to 30 days under the INDRP. WIPO's filing fee for a complainant bringing a single-domain case is USD 1,500 (single-member panel); the INDRP has its own, generally lower, arbitration fee structure. Both policies use the same three-element test, and the chronological registration-date defense works in both.

If the domain is a new gTLD — such as .shop or .tech — and the complainant is seeking only suspension rather than transfer, the URS (Uniform Rapid Suspension) procedure applies. The URS uses a higher "clear and convincing" evidentiary standard, which favors respondents in close cases. Where the registration predates the trademark, that standard is nearly impossible for a complainant to meet.

A .in domain cannot be disputed under the UDRP directly; the INDRP is the applicable procedure. The two policies are substantively similar but procedurally distinct. If the same registrant holds both a .com and a .in, a complainant may file separate proceedings in parallel — a UDRP for the .com and an INDRP for the .in. Coordinating the two responses is critical; inconsistencies in the factual record across parallel proceedings create unnecessary risk.

Where neither the INDRP nor the UDRP is available or sufficient — for example, where the complainant seeks monetary relief or where the dispute raises complex ownership questions — litigation before the competent Indian court, with local litigation counsel in the relevant jurisdiction, remains an option. INDRP arbitration and court proceedings are not mutually exclusive, though the interplay requires careful coordination.

What Are the Realistic Outcomes, and What Happens After the Decision?

The INDRP arbitrator has three options: deny the complaint (your domain is retained), order transfer to the complainant, or order cancellation. Where the registration-date defense is established and supported, denial is the expected outcome. No outcome is guaranteed — domain disputes turn on specific facts and arbitrator discretion — but the chronological defense is among the strongest available positions in domain dispute proceedings.

If the complaint is denied, NIXI instructs the registrar to take no action; your domain remains registered in your name. If the complaint is denied with an RDNH finding, that finding is published alongside the decision. If the complaint succeeds — which, in a well-documented preregistration case, is an atypical outcome — an appeal mechanism exists under the INDRP, and Indian court challenge of the arbitration award remains available under the applicable Indian arbitration statute (a challenge on procedural grounds, not a re-hearing on the merits in the first instance).

A second micro-example: in an autumn 2024 matter involving a .in domain used for a technology consultancy for more than five years before the complainant applied for its trademark, we secured a denial within approximately ten weeks of filing the response. The arbitrator accepted the registration date, the continuous site use, and the generic character of the name as independently sufficient to defeat each prong of the complaint. No RDNH finding was sought in that matter because the complainant withdrew a parallel .com proceeding before decision — a common outcome once the chronological record is established in a co-pending INDRP.

Related at COGNOMEN

• Respondent defense and RDNH across gTLDs and ccTLDs — full service overview
• Defending fair use and descriptive term domains in financial sector disputes
• Guide to defending a generic domain under Chinese ccTLD dispute procedures