How to recover a .in domain confusingly similar to your trademark

How to recover a .in domain confusingly similar to your trademark. UDRP and ccTLD domain recovery and defense across .in. Email the firm to assess your case.

A stranger registers yourbrands.in, points it at a pay-per-click parking page, and waits. Your Indian customers type the address expecting you. The registrant expects a buy-back offer. The question is which legal route retrieves the domain – and what it takes to satisfy every element of that test.

To recover a .in domain confusingly similar to your trademark, you will file under the .in Domain Name Dispute Resolution Policy (INDRP) – the ccTLD procedure that governs India's .in zone and closely tracks the UDRP's three-element test. You must show that the domain is identical or confusingly similar to a mark in which you hold rights, that the registrant has no legitimate interest, and that the domain was registered or is being used in bad faith. The respondent has 20 days to answer, and a straightforward case typically concludes in roughly two months. The only remedies are transfer or cancellation.

This page sets out the INDRP procedure, the evidence that decides close calls, the cost structure, and the practical next step for a brand owner ready to act.

What is the INDRP and how does it apply to .in disputes?

The .in Dispute Resolution Policy (INDRP) is the mandatory arbitration procedure administered by the National Internet Exchange of India (NIXI) for disputes over .in domain names. Every .in registrant accepts it at the point of registration. It mirrors the structure of the UDRP – three elements, a panelist-based hearing, and the same limited menu of remedies – but it is a distinct national procedure with its own rules, its own arbitrator roster, and its own fee schedule.

Because the INDRP tracks the UDRP closely, the body of UDRP panel decisions provides persuasive guidance. Panelists regularly cite UDRP consensus positions when resolving INDRP matters. That convergence matters in practice: a complainant with prior UDRP experience, or counsel familiar with WIPO and Forum decisions, is already oriented to the right analytical frame.

One procedural note: the INDRP designates NIXI as administrator and draws panelists from an approved roster of Indian arbitration practitioners. Filings and correspondence are handled through NIXI's published process. Unlike a WIPO filing, where you can choose between WIPO, the Forum, CAC, or ADNDRC for a .com dispute, the .in zone routes exclusively through NIXI. There is no forum selection.

If the same bad-faith registrant also controls a parallel .com or .net domain bearing your mark, that gTLD dispute is a separate UDRP filing. In our practice we regularly advise brand owners who face simultaneous registrations across zones – the INDRP and the UDRP proceed independently, and coordination of timing and evidence can matter.

What are the three INDRP elements you must prove?

The INDRP requires you to satisfy all three elements of the test – failure on any one defeats the complaint. The elements closely follow Paragraph 4(a) of the UDRP, and UDRP panel consensus informs how INDRP panelists assess each limb.

Element one: confusing similarity to your trademark

The domain must be identical or confusingly similar to a trademark or service mark in which you hold rights. Registered trademark rights are the clearest basis. Unregistered marks can qualify – common-law rights grounded in reputation and use in trade – but they require more evidentiary work. For a .in proceeding, Indian trademark registrations carry obvious weight; international registrations (Madrid Protocol, CTM, US registrations) are also accepted where the complainant demonstrates those rights are enforceable. The panel compares the alphanumeric string of the domain – stripping the .in suffix – with the mark as a whole.

Confusing similarity is assessed on the face of the strings. A domain that adds a generic word ("shop," "official," "india," "buy") before or after your mark is typically still confusingly similar. The addition does not dispel confusion; it often aggravates it by implying affiliation. Panels have consistently held that a geographic term appended to a mark – "brandindia.in," for example – does not break the confusing similarity because it merely describes the market the registrant targets.

Element two: no rights or legitimate interests

The complainant must show the registrant has no rights or legitimate interests in the domain. Because a complainant cannot search a registrant's mind, the burden here is structured: you make a prima facie showing, and the evidential burden shifts to the respondent to produce evidence of legitimate interest. The INDRP, like the UDRP, recognizes three safe harbors: a bona fide offering of goods or services under the name before notice of the dispute; the respondent being commonly known by the domain name; and legitimate noncommercial or fair use without intent to mislead. Parking pages generating pay-per-click revenue from your brand's traffic do not constitute a bona fide offering. Neither does holding a domain name with no active use and no credible explanation.

Element three: bad-faith registration and use

This is usually where contested cases turn. The INDRP, like the UDRP, requires both registration in bad faith and use in bad faith – though some INDRP panels have read the conjunctive test somewhat flexibly in cases of passive holding. Non-exhaustive indicators include: registering the domain primarily to sell it to the mark owner at a profit; registering to disrupt a competitor; registering to attract users for commercial gain by creating confusion; or a pattern of abusive registrations. Passive holding – registering a domain and doing nothing with it – can still satisfy the use limb where the surrounding circumstances make any good-faith use implausible.

For a read on whether the three INDRP elements are met in your specific situation, reach us at info@cognomenlaw.com.

What evidence decides an INDRP complaint?

Evidence is the fulcrum of any domain dispute, and a well-documented complaint is materially less likely to be denied than one that recites legal principles without supporting proof. Assembling the right record is the first practical step after deciding to file.

For the similarity element, you will need your trademark registration certificates (or, for common-law marks, evidence of use and reputation: sales records, press coverage, advertising spend, customer declarations). For Indian marks, the registration certificate from the Trade Marks Registry suffices. For foreign marks, the registration document from the relevant office and, where useful, evidence of use in the Indian market or directed at Indian consumers.

For the legitimate-interest element, document what the respondent is doing with the domain. Screenshots of the landing page – timestamped via an archiving service – are standard. If the page carries pay-per-click links related to your industry, that is significant. If it carries links to competitors, stronger still. WHOIS or RDDS history can reveal whether the registrant has ever operated under the domain name or associated business name. If a registrant has no pre-dispute history of being known by the domain string, the absence of legitimate interest is easier to demonstrate.

For bad faith, the most direct evidence is a demand. If the registrant contacted you – or you found a "for sale" listing citing a figure beyond out-of-pocket registration costs – that points squarely to Paragraph 4(b)(i)-type conduct (registering primarily to sell). Timing is also telling: a registration filed days after your product announcement, after a press release, or after a trademark publication signals opportunism. We have seen registrations dated to the same week as a brand's public launch, and in those cases the chronological record is compelling.

In a recent matter (a .in cybersquatting complaint, spring 2025), we assembled a chain-of-title and web-archive record that showed the respondent had registered approximately eight confusingly similar domains across Indian ccTLD variants within a single week of a product launch announcement – a pattern of abusive registration that supported a strong bad-faith finding. The transfer order issued roughly eight weeks after filing.

The complainant must also comply with the formal requirements of the INDRP rules: the complaint document, annexes, the arbitration fee payment, and a certification of accuracy. Errors in any of these can delay commencement and eat into your timeline advantage.

How does the INDRP process actually run, and how long does it take?

A standard INDRP proceeding moves in five stages: complaint filing and administrative review by NIXI, formal commencement, the respondent's response window, panelist appointment and the decision, and finally registrar implementation.

The respondent has 20 days from commencement to file a response. If no response is filed, the panel decides on the complaint alone – a default is not an automatic win, but the evidentiary burden on the complainant is lighter. A contested case with a response typically adds time for panel deliberation. Overall, a straightforward .in dispute resolves in roughly two months from filing, assuming no procedural complications or requests for supplemental submissions.

Unlike the UDRP, where WIPO offers an expedited option delivering a decision within about one month for single-panel cases of up to five domains, the INDRP does not have a published expedited track. Speed depends on NIXI's current caseload and panelist availability.

What happens after the decision? If the panel orders a transfer, NIXI notifies the registrar (typically NIXI itself, which is also the .in registry). The registrar implements the transfer unless the respondent files a lawsuit in a competent court within the specified period to stay the transfer – the INDRP, like the UDRP, preserves the right to litigate the underlying dispute in court. In practice, stays are uncommon in straightforward cybersquatting matters.

If you have already received a complaint or a NIXI notice, email info@cognomenlaw.com to assess your response options within the 20-day window.

How do INDRP costs compare with UDRP filing fees?

The cost structure for a .in dispute involves two separate components: the official arbitration fee paid to NIXI and the legal fee for preparing and filing the complaint.

NIXI's published arbitration fees are a matter for current confirmation with NIXI directly, as they are set by the registry and subject to revision. They are characteristically modest relative to WIPO's schedule. For reference, WIPO charges USD 1,500 for a single-panel .com complaint covering one to five domains; the INDRP fee structure is generally lower – verify the current figure at the time of filing. NIXI's process requires the complainant to pay the arbitration fee at the filing stage.

Legal preparation fees depend on complexity. For a single .in domain with clear-cut evidence, the market range for legal preparation of a domain-dispute complaint is broadly comparable to UDRP work. For contested matters requiring extensive evidence marshaling, the fee scales accordingly. At COGNOMEN we provide clear fee ranges before any engagement; domain disputes should not require a client to file in the dark on cost.

The fee structure also affects the strategic choice between INDRP and other routes. Where a bad-faith registrant controls the same name across .in and .com, a complainant may file parallel proceedings – the INDRP for the .in domain and a UDRP before WIPO or the Forum for the .com. Coordinating those filings reduces duplicative evidence preparation and may allow timing that limits the respondent's window to obscure conduct between filings.

What are the realistic outcomes, and what can go wrong?

The only remedies available under the INDRP – as under the UDRP – are transfer of the domain to the complainant or cancellation of the registration. There are no monetary damages, no costs awards, and no injunctions. If your goal is compensation rather than domain control, an INDRP proceeding cannot deliver it. A court action in the relevant Indian jurisdiction would be required for any damages claim.

Transfer is the common outcome when a complainant satisfies all three elements. Cancellation is sometimes preferable where the complainant cannot hold .in (certain eligibility requirements apply to .in registrations) or where deletion removes a domain being used to harm the brand without the complainant needing to operate it. Verify current .in eligibility rules with counsel before requesting transfer as the remedy.

What are the failure modes? The most common is a complaint that does not close all three elements. A complainant with a pending (unregistered) trademark application rather than a granted registration faces a harder first element. A respondent who can show any plausible pre-dispute use of the domain – even a modest website predating the complaint – complicates the legitimate-interest limb. A complaint filed before the complainant's brand is publicly known risks a finding that the registrant could not have targeted a mark that was not yet in the market.

There is also a reverse-domain-name-hijacking risk for complainants who overreach. An INDRP panel may find that a complaint was brought in bad faith to strip a legitimate registrant of a domain – a reputational sanction, not a monetary one, but one that COGNOMEN takes seriously when advising brand owners on whether to proceed. We do not file complaints designed to fail or to bully a legitimate registrant.

In a recent matter (a .in dispute, autumn 2024), a brand owner approached us wanting to recover a domain that, on investigation, had been registered years before the complainant's own trademark filing. The registrant had a demonstrable pre-dispute business use. We advised against filing, which avoided a probable denial and a possible RDNH finding. That kind of early-stage assessment is where the engagement pays for itself.

How does the .in route compare with a UDRP or court action?

The right route depends on the zone, the remedy needed, and the evidence in hand. Here is how the options map out for a brand with a .in problem.

If the domain is a .in and the goal is to transfer it, the INDRP is the mandatory arbitration route – it is the only specialist procedure designed for .in. You cannot file a UDRP complaint at WIPO or the Forum for a .in domain unless NIXI has adopted those bodies as providers (verify current rules; at the time of writing the INDRP is administered exclusively through NIXI). The INDRP is therefore the natural first step.

If the same registrant also controls yourbrands.com or yourbrands.net, those gTLD domains are proper subjects for a UDRP filing at WIPO (filing fee USD 1,500, single panel, one to five domains), the Forum, CAC, or ADNDRC. A parallel strategy – INDRP for .in, UDRP for the .com – is something we coordinate regularly, and the evidence record built for one proceeding substantially serves the other.

If you want damages, or if the registrant is also infringing your trademark through the website content (counterfeit goods, phishing, fraud), an Indian court action is the proper route for relief beyond transfer. Court proceedings are slower and more expensive than INDRP arbitration, but they reach monetary remedies the INDRP cannot. Where local-court action is warranted, COGNOMEN works with local litigation counsel in the relevant jurisdiction.

If the registrant controls the domain only briefly, or if only suspension – not transfer – is needed in the interim, the picture is different for new gTLDs: the Uniform Rapid Suspension (URS) is the fast-track remedy for new gTLD domains, not applicable to .in. For .in the INDRP is the specialist path, and there is no interim suspension procedure short of court relief.

If the domain is a .uk, .eu, or .de, entirely different procedures apply. The Nominet DRS governs .uk; ADR.eu governs .eu; .de disputes go through German courts with a DENIC DISPUTE entry to block transfer pending litigation. We handle those routes separately. See our broader guidance on UDRP and ccTLD recovery across zones.

What if you are on the respondent side of an INDRP complaint?

Not every INDRP complaint is legitimate. A brand owner can over-assert trademark rights against a registrant who registered the domain in good faith – perhaps a business trading under the name before the complainant's mark existed, or a descriptive term the complainant does not actually control. The INDRP, like the UDRP, recognizes that complainants can abuse the procedure.

If you are a .in registrant who has received an INDRP complaint, the response window is 20 days from commencement. Missing that window does not automatically transfer the domain, but it reduces the evidentiary record before the panelist to the complainant's submission alone. A well-drafted response addressing each of the three elements – and invoking the safe harbors where they apply – materially changes the outcome probabilities.

Where the complaint is clearly abusive – where the complainant lacks genuine trademark rights, registered the mark after you registered the domain, or is pursuing the domain for anti-competitive reasons – a panelist finding of reverse domain name hijacking (RDNH) is worth pursuing. An RDNH finding is a reputational sanction; it does not result in compensation, but it places on the public record that the complaint was filed in bad faith. In our practice, we pursue RDNH affirmatively when the facts support it.

The audience myth worth addressing here: many registrants assume that because they registered the domain legitimately, the complaint will obviously fail. That is not guaranteed. Panels assess the three elements on the record presented. A registrant who presents no evidence, fails to articulate why the safe harbors apply, or ignores the response deadline risks losing a domain they were entitled to keep. Defense requires the same level of preparation as prosecution.

For .in respondent-side analysis, see our guidance on confusingly similar trademark disputes in other ccTLD zones.

Brand-protection monitoring: catching .in registrations before they harm you

The most cost-effective moment to address a confusingly similar .in registration is before it is fully deployed. A domain registered against your brand yesterday – before a parking page or phishing site is operational – is cheaper to recover and easier to prove than one with months of established use.

Brand-protection monitoring watches new .in registrations (and registrations across gTLDs and other ccTLDs) for strings that match or closely resemble your marks. When a suspect registration surfaces, you receive an alert early enough to choose your response: a cease-and-desist, an INDRP filing, a negotiated purchase, or a watch-and-wait decision. For brand owners with active product launches, seasonally targeted campaigns, or significant Indian market presence, a monitoring program pays for itself in avoided disputes and reduced recovery costs.

COGNOMEN operates brand-protection monitoring alongside dispute proceedings. For portfolio-wide coverage and analysis of monitoring options, see our analysis of brand-protection monitoring for .com and broader zones.

Related at COGNOMEN

• UDRP domain recovery across gTLDs and ccTLDs – full service overview
• Confusingly similar trademark disputes in ccTLD zones – practitioner's guide
• Brand-protection monitoring for .com and multi-zone portfolios – analysis