FAQ: defend a .in domain registered before the complainant's trademark
FAQ: defend a .in domain registered before the complainant's trademark. UDRP and ccTLD domain recovery and defense across .in. Email the firm to assess your ca…
A complainant files against your .in domain. Their trademark registration is newer than your domain. Does that mean you win? Not automatically — but prior registration is one of the strongest defenses available under the .in dispute procedure, and knowing how to build that record is what decides the outcome.
To defend a .in domain registered before the complainant's trademark, a registrant must show that, at the time of registration, the complainant's mark did not yet exist in a protectable form and that the registrant had a plausible, good-faith reason to choose the name. The .in dispute procedure — the INDRP — applies Paragraph 4(a)-equivalent elements, including safe harbors closely tracking Paragraph 4(c) of the UDRP. A 20-day response window applies once the case commences, making early preparation essential.
This FAQ answers the questions registrants ask most often when facing a complaint over a domain they registered before the complainant even held a mark.
When can I defend a .in domain registered before the complainant's trademark?
Prior registration is your primary shield. If the domain predates the trademark, the complainant faces a significant hurdle on the bad-faith element — because bad faith at the time of registration is generally required, and it is difficult to act in bad faith toward a mark that did not yet exist.
That said, the analysis is more nuanced than a simple date comparison. The complainant may argue that the mark had acquired reputation or common-law recognition before formal registration — in other words, that you knew, or should have known, of the brand even before it was registered. Panels examining these disputes consistently look at what the registrant knew at the date of registration, not what the complainant's mark became worth afterward.
The strongest defense combines three elements. First, the domain registration date predates the trademark filing date — ideally by a meaningful margin. Second, the registrant had an independent, documented reason to choose that name: a business plan, a descriptive use of common dictionary words, or a personal name corresponding to the domain. Third, the domain was not subsequently weaponized — pointing it at competitor-disparagement content or a pay-per-click page targeting the complainant's customers can revive bad-faith arguments even when registration was clean.
In our practice, registrants who hold contemporaneous evidence of their original intent — emails, business registrations, website archives — are far better positioned than those who rely on the registration date alone. Date is necessary but not sufficient.
For a read on whether your registration predates the mark in a way that supports a full defense, reach us at info@cognomenlaw.com.
Does INDRP or a court decide a .in dispute?
The .in domain dispute procedure — the INDRP, administered through the National Internet Exchange of India — is the primary forum for .in disputes, and it operates as a mandatory administrative proceeding, much as the UDRP does for .com and other gTLDs. A registrant cannot opt out once a complaint is filed; the procedure runs whether or not the registrant participates.
The INDRP test broadly mirrors the three-element UDRP structure. The complainant must show that the domain is identical or confusingly similar to a mark in which it has rights, that the registrant has no rights or legitimate interests, and that the domain was registered and is being used in bad faith. The same Paragraph 4(b) bad-faith indicators and Paragraph 4(c) safe harbors that appear in the UDRP are reflected in the INDRP's rules. That means the body of UDRP consensus reasoning — including the weight given to pre-trademark registration — is persuasive, though not formally binding, in INDRP proceedings.
A court action in India remains available as a parallel or alternative route. However, court proceedings are substantially slower and more expensive. For most registrants whose goal is to keep the domain, the INDRP proceeding is where the dispute is decided in practice. If a complainant obtains a transfer order they believe is erroneous, they can apply to a competent court — and so can a registrant who believes the decision was wrong. But in our experience, parties rarely litigate further after an INDRP outcome.
One important cross-zone point: if the same brand is also registered under a .com, a complainant may file a UDRP complaint at WIPO or the Forum simultaneously. The .in and the .com disputes proceed under separate rules and separate timelines. A win or loss in one proceeding is not formally binding in the other — though a clear INDRP decision in the registrant's favor, including an RDNH finding, does carry persuasive weight.
How do I build a legitimate-interest record under Paragraph 4(c)?
The safe harbors in the INDRP rules track Paragraph 4(c) of the UDRP closely. There are three main paths: demonstrating a bona fide offering of goods or services using the domain before receiving notice of the dispute; showing that you are commonly known by the domain name; or showing legitimate noncommercial or fair use. For a domain registered before the complainant's trademark, the bona fide-use path and the "commonly known" path are the most frequently relevant.
What constitutes a bona fide offering? Panels look for use that is genuine, predates the dispute notice, and is not a pretextual post-complaint construction. An active website offering real goods or services under the domain name, a business registration that matches the domain, emails sent from the domain's address in the ordinary course of trade — these are the kinds of evidence that carry weight. A domain that simply resolves to a parking page, even if registered early, gives a panel little to work with on this element.
The "commonly known by the name" path is fact-intensive. It works well for individuals whose personal name or established trade name corresponds to the domain. It is harder to sustain for a corporate registrant whose actual trading name differs from the domain.
Assembling the record takes time. We regularly advise registrants to gather registration-date evidence (WHOIS history, registrar creation records), contemporaneous business documents (incorporation filings, early invoices, trade correspondence), and archived screenshots or Internet Archive captures of the domain's prior use. Waiting until after the complaint arrives to build this file is the most common and most damaging mistake.
What evidence actually decides the outcome in these cases?
Evidence of chronology and intent together decide most .in pre-trademark registration defenses. The registration date is the starting line. Everything after it — what the domain was used for, what the registrant's business looked like at the time, whether the complainant's brand was even known in India when the domain was registered — fills in the picture a panel needs to rule.
Panels weigh the following categories of evidence most heavily. First, timestamped documentation of the domain's first active use — the earlier and more specific, the better. Second, any evidence showing the registrant was unaware of the complainant's brand at the date of registration. Third, business records suggesting the domain corresponds to a legitimate independent commercial activity. Fourth, the subsequent conduct of the domain: a registrant who held the name dormant for years and then pointed it at a site competing with the complainant's products creates a bad-faith inference that prior registration alone may not fully overcome.
One pattern we see regularly: a domain registered against a descriptive or generic term, held by a registrant who used it for a corresponding descriptive purpose, and then targeted by a complainant who later built a brand around the same word. In those situations, where the term was not distinctive at the date of registration, the complainant faces a near-impossible burden. The absence of distinctiveness at registration is itself evidence that no bad faith could have attached.
A micro-case to illustrate: in a recent matter (a .in registration, spring 2025), a registrant had held a two-word domain corresponding to a common commercial phrase for more than eight years. The complainant's trademark had been filed approximately three years after the domain was created. We assembled a record of early web archives, email correspondence from the original registration period, and a business registration predating the mark filing. The panel found no bad faith and declined to transfer the domain.
What if the registrant does not respond?
Defaulting — failing to file a response within the applicable deadline — is a serious strategic error, even when the registrant has strong defenses. Default does not mean automatic loss; under the INDRP, a panel still reviews the complaint on its merits. But a panel considering an uncontested record has only the complainant's evidence and arguments before it.
The registrant's pre-trademark registration history, the legitimate-interest record, and any evidence of good faith at the time of registration are entirely absent. The panel draws reasonable inferences from what is in the file — and the only file is the complainant's. Transfer orders in default cases are common, even where a strong defense would have been available had it been asserted.
There is a second consequence. Where a complaint is weak — brought without adequate trademark rights, or against a domain clearly registered before any cognizable mark — a filed response can pursue a finding of Reverse Domain Name Hijacking (RDNH). RDNH means the panel declares that the complaint was brought in bad faith to deprive a legitimate registrant of a validly held domain. That finding is reputational and procedural: it carries no financial penalty, but it is a matter of public record and signals to the domain community that the complainant acted improperly. That finding is never available if the registrant defaults.
Twenty days to respond is the standard window once a case commences. In practice, preparation should begin the moment a registrant suspects a dispute is coming — ideally before any formal complaint is filed.
When is an RDNH finding realistic?
Reverse Domain Name Hijacking findings are available under the INDRP, following the same principles that apply under the UDRP. A panel may find RDNH where the complainant knew or should have known it could not succeed — for example, where the complainant filed after discovering the domain predated its own trademark, had no supporting evidence of pre-registration reputation, and offered no credible theory of bad faith.
RDNH findings are not granted lightly. A complaint that fails on the merits is not automatically RDNH. The registrant must demonstrate that the complaint was brought with knowledge of its weakness or to harass or pressure a legitimate holder. The strongest RDNH scenarios in pre-trademark-registration cases involve complainants who had clear access to the WHOIS creation date, knew their own trademark was filed years later, and filed anyway — relying on the registrant's likely ignorance of the process or inability to afford a response.
We have defended matters where the chronological gap between domain creation and trademark filing was so clear that the only rational inference was that the complaint was filed as a pressure tactic. In those situations, an RDNH finding is a realistic and appropriate goal, not merely a secondary hope.
The practical test: if a competent review of the WHOIS record and the trademark certificate would have told the complainant it had no viable bad-faith argument, pursuing the complaint anyway risks an RDNH finding. The reputational cost of that finding should deter calculated overreaching — and, for registrants on the receiving end of such a complaint, that vulnerability is worth pressing.
Can the decision be appealed or challenged?
An INDRP panel decision can be challenged in a court of competent jurisdiction in India. A registrant who believes the panel erred — for example, by discounting clear prior-registration evidence or applying the wrong standard on legitimate interest — may apply to court to have the decision reviewed or set aside. Similarly, a complainant dissatisfied with a decision in the registrant's favor may seek court relief.
Court challenges are significantly more costly and time-consuming than the original INDRP proceeding. In our assessment, they are reserved for high-value domains where the error in the panel decision is both clear and material. A panel that weighed conflicting evidence and resolved it against the registrant is unlikely to be overturned on that factual assessment alone. A panel that demonstrably misapplied the INDRP standard — for instance, requiring proof only of confusing similarity without adequately addressing legitimate interest or bad faith — may present stronger grounds.
Registrar implementation of an INDRP transfer order is normally stayed for a short period pending any court challenge. Registrants considering a court application must act quickly. The practical window to seek interim relief is narrow, and missing it means the domain transfers before any court can intervene.
Cross-zone note: if a parallel UDRP complaint was filed against the .com counterpart of the domain, a court challenge to the INDRP result does not affect that proceeding. Each dispute resolves under its own rules on its own timeline.
To assess whether your .in case warrants a response, an RDNH argument, or a court challenge, contact info@cognomenlaw.com.
Related at COGNOMEN
When can I defend a .in domain registered before the complainant's trademark?
You can defend a .in domain registered before the complainant's trademark where you can show the mark did not exist in any protectable form at the date of your registration and that you had a good-faith, independent reason to register the name. The INDRP requires bad faith at registration — a standard difficult to meet when the mark came later. Prior registration is not a guaranteed shield, but combined with contemporaneous evidence of legitimate intent and use, it is among the strongest defenses available.
Who can defend a .in domain registered before the complainant's trademark for a .in domain?
Any registrant of record — an individual, company, or other entity — has the right to file a response in an INDRP proceeding and assert the pre-registration defense. There is no residency or nationality requirement to participate as a respondent. Representation by counsel familiar with the INDRP rules and the applicable body of UDRP consensus reasoning significantly improves the quality of the record placed before the panel.
What is the deadline once a case starts?
The standard response period under the INDRP is 20 days from the date the complaint commences. Filing late or not filing at all leaves the panel with only the complainant's version of events. Preparation should begin well before the formal commencement notice arrives — ideally the moment a registrant learns that a complaint may be filed. Extensions are not routinely granted.
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 covers .in INDRP proceedings as part of a wider ccTLD and gTLD dispute practice, with published price ranges and no hidden fees. To discuss a .in defense or any domain dispute, contact info@cognomenlaw.com.
Disclaimer: This article is general information about domain-name dispute procedures and does not constitute legal advice. Outcomes depend on the specific facts, the zone, and panel or court discretion. For advice on your domain, contact info@cognomenlaw.com.
Speak with Cognomen Law
For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter
Related
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.