Recover a typosquatted .in domain: what panels actually decide

A brand owner searches for its own product name and finds a domain that substitutes one letter, drops a vowel, or doubles a consonant – all pointing at a parking page or a competitor's site. The domain is a .in, India's country-code extension. The brand owner wants it back. The question is which rulebook governs, what the panel will actually examine, and what evidence tips the decision.

To recover a typosquatted .in domain, a complainant proceeds under the .IN Domain Name Dispute Resolution Policy (INDRP), India's ccTLD dispute procedure. The INDRP imports the three-element test of Paragraph 4(a) of the UDRP almost verbatim: the domain must be identical or confusingly similar to the complainant's mark, the registrant must lack rights or legitimate interests, and the domain must have been registered and used in bad faith. A standard INDRP case can be resolved in a matter of weeks. The only remedies are transfer or cancellation.

This analysis covers the INDRP framework, the specific evidence patterns that panels use to decide typosquat disputes, the minority positions that can complicate an otherwise strong case, and the realistic choices a complainant or respondent faces at each stage.

What governs .in disputes – and how it differs from the UDRP

The INDRP, administered by the National Internet Exchange of India (NIXI), is the mandatory dispute-resolution procedure for all .in registrations. It draws its three-element test directly from UDRP Paragraph 4(a) and adopts the UDRP's familiar bad-faith catalogue from Paragraph 4(b). The Policy also preserves the Paragraph 4(c) safe harbors – bona fide offering before notice of the dispute, being commonly known by the name, and legitimate noncommercial or fair use.

There is one structural difference worth noting at the outset. The INDRP does not route cases through WIPO, the Forum, CAC, or ADNDRC. NIXI maintains its own roster of arbitrators, and cases are decided under the Indian Arbitration and Conciliation Act as well as the INDRP rules themselves. That domestic statutory backdrop means a dissatisfied respondent theoretically has a court challenge path that is broader than the narrow court route available after a UDRP decision. In practice, most decided .in cases proceed to a final award without challenge, but a complainant who obtains a transfer order should be aware that an Indian court could be asked to set it aside on procedural grounds.

For brand owners who hold both a .com and a .in: the UDRP governs the .com, the INDRP governs the .in, and the two proceedings run independently. There is no consolidated gTLD-plus-ccTLD procedure. We regularly advise complainants who need to pursue both simultaneously, and the evidence record assembled for one filing adapts well to the other – the element-by-element structure is nearly identical.

To assess whether your mark and the registrant's conduct meet the three INDRP elements, contact info@cognomenlaw.com.

How does typosquatting satisfy the confusing-similarity element?

The first element of the INDRP test – identical or confusing similarity to the complainant's mark – is almost always the easiest to satisfy in a typosquat case. A panel examining a domain that differs from the mark by one transposition, one substitution, or one omitted character will generally find the domain confusingly similar without extensive analysis. The visual and phonetic proximity is plain on its face.

Panels have consistently held that the addition of a generic word alongside a misspelling does not cure the confusion. A domain that misspells a well-known brand and appends "shop," "deals," or a geographic term still clears the confusing-similarity hurdle with ease. The TLD itself – .in – is disregarded for this element, following the same approach taken in UDRP proceedings. What matters is the second-level string compared to the mark.

Where does the first element genuinely become contested? Two patterns recur. First, a complainant who relies on an unregistered mark must show secondary meaning – widespread market recognition of the name as a source identifier. That showing requires evidence: marketing spend, media coverage, consumer surveys, or a substantial trading history under the name in India. Second, if the complainant's registration postdates the domain registration, the panel will look carefully at priority. A typosquat of a mark that did not exist when the domain was registered cannot satisfy the third element, and the panel may also question whether the complainant had rights "at the time of the dispute" in the sense required by the INDRP.

In our practice, the confusing-similarity element rarely decides a .in typosquat case on its own. It is the second and third elements – legitimate interest and bad faith – where outcomes are actually won or lost.

What evidence does a panel require to find no legitimate interest?

The second INDRP element requires the complainant to make a prima facie showing that the registrant lacks rights or a legitimate interest. Once that showing is made, the burden shifts to the registrant to produce evidence of a legitimate interest. That procedural structure matters: a complainant who does no more than assert "the respondent is a typosquatter" without explaining why the registrant has no colorable claim can face a panel that refuses to draw the inference.

The safest prima facie package for a typosquat .in complaint includes: evidence that the complainant or any licensee has never authorized the registrant to use the mark; a WHOIS or RDDS printout showing no registrant name that corresponds to the disputed string; and a screenshot of the domain's resolving page showing parking, pay-per-click links to the complainant's competitors, or a redirect to an unrelated commercial site. That combination typically satisfies the initial burden.

What trips complainants up? Three recurring gaps. First, the complainant omits the authorization point entirely, treating it as obvious. Second, the complainant relies on a WHOIS record that lists a privacy or proxy service without attempting to look behind it. Third, the complainant files before checking whether the registrant operates a genuinely descriptive business under a name that happens to be close to the disputed string. We have seen panels in analogous UDRP proceedings decline to transfer where the respondent produced a business registration certificate and a trading history pre-dating the complainant's notice of the dispute.

On the respondent side: the Paragraph 4(c) safe harbors remain available under the INDRP. A registrant who received a complaint after building a bona fide business around the registered string – even a slightly misspelled one – has a real argument under the first safe harbor, provided the use preceded any notice of the dispute and was genuinely in connection with a legitimate offering.

What bad-faith patterns do panels find in .in typosquat disputes?

The third INDRP element is cumulative: the domain must have been both registered and used in bad faith. That conjunctive requirement – carried over from the UDRP – means a complainant cannot succeed by showing only a bad-faith use that arose after an innocent registration, nor only a bad-faith registration followed by purely passive holding.

Typosquat cases often produce the clearest bad-faith findings in the entire domain-dispute canon. The deliberate misspelling of a well-known brand is difficult to explain innocently. Panels have consistently held that the act of registering a domain that closely mimics a trademark – especially one with strong recognition in the relevant market – raises a strong inference of intent to divert traffic or profit from the mark owner's goodwill. Where that inference stands unrebutted, the third element is met.

The Paragraph 4(b) catalogue provides the most common footholds. Registration to attract users for commercial gain by creating confusion with the mark – the so-called "parking for profit" pattern – fits squarely in the bad-faith taxonomy whenever the resolving page carries pay-per-click advertising, affiliate links, or competitive product offers. A pattern of abusive registrations – multiple misspellings of the same brand or misspellings of several different brands in the same registrant's portfolio – also weighs heavily.

Where does the bad-faith analysis become genuinely difficult? Two scenarios. First, passive holding: the registrant registered the domain, it resolves to a blank page or a "coming soon" notice, and there is no active monetization. Panels in the UDRP context have recognized that passive holding can still constitute bad faith where the mark is sufficiently well-known that no plausible legitimate use of the misspelling exists. The same reasoning applies under the INDRP, but the panel must engage with it – a complainant who simply calls passive holding "bad faith" without addressing the strength of the mark and the absence of any plausible innocent use invites a more skeptical read.

Second, the genuine descriptive overlap: what if the misspelled string also happens to be a common word or phrase in an Indian vernacular language, or corresponds to a place name? Panels do not usually accept these coincidences without more, but a well-prepared respondent can use them to complicate the intent analysis.

In a recent matter – a .in typosquat complaint, spring 2025 – we assembled a bad-faith record that combined parking-page screenshots showing competitor advertising, a NIXI registrar log showing the domain had been registered within days of our client's product launch, and a print of the registrant's portfolio showing three other near-identical misspellings of the same brand. The panel transferred the domain.

If a respondent has already answered or you have received a complaint, a careful second read of the evidence record often reveals the element that was missed. Email info@cognomenlaw.com to arrange a review.

What is the realistic timeline and what can a panel actually order?

The INDRP sets its own procedural timeline, and NIXI's published rules provide for arbitration under the Indian Arbitration and Conciliation Act. The practical pace of a straightforward .in case is broadly similar to a UDRP proceeding – commencement, response window, arbitrator appointment, award, and registry implementation. A respondent who wishes to contest the complaint should act promptly; default awards are common where no response is filed, and a default does not help the registrant.

The only remedies the INDRP arbitrator can order are transfer of the domain to the complainant or cancellation of the registration. There are no monetary damages and no costs awards in the INDRP procedure itself. If a brand owner also needs compensation for lost business or wants to pursue the registrant personally, that requires separate court action in India, handled with local litigation counsel in the relevant jurisdiction.

Compare this to the available remedies in a UDRP proceeding for a parallel .com typosquat: the position is the same – transfer or cancellation only, no damages. The practical difference is the forum and the governing procedure. WIPO, the Forum, CAC, and ADNDRC are the UDRP providers; NIXI is the INDRP forum. A brand owner needing both domains recovered must file two separate complaints.

What about cancellation versus transfer? Transfer is almost always the complainant's requested remedy, and most awards in successful cases grant it. Cancellation is occasionally ordered when the complainant for some reason cannot take ownership – for example, if the complainant does not meet a residency or nexus eligibility requirement the registry imposes. A complainant should verify current NIXI registration eligibility rules before filing, because the domain cannot be transferred to a holder who is ineligible to register .in names.

How does the INDRP compare with the UDRP and when should a complainant choose which route?

The right starting point is the zone, not the procedure. If the typosquat sits in a .com, .net, .org, or another gTLD, the UDRP governs and the complainant chooses among WIPO, the Forum, CAC, or ADNDRC. Filing fees at WIPO start at USD 1,500 for a single-member panel covering one to five domains; the Forum begins around USD 1,300 for one to two domains. If the typosquat sits in a .in, the INDRP governs and NIXI is the forum. There is no choice of provider for .in.

Where the brand owner faces typosquats in both zones – a common pattern – the cases proceed in parallel. The UDRP complaint timeline of roughly 45 to 60 days for a standard case and the INDRP timeline are broadly similar, so the two proceedings can often be concluded within the same window. Evidence prepared for one complaint adapts to the other with moderate effort: the trademark rights exhibit, the confusing-similarity analysis, and the bad-faith evidence are all reusable across jurisdictions.

A distinct decision arises when the brand owner also wants monetary relief or needs to stop ongoing consumer harm quickly. The INDRP (and the UDRP) cannot grant injunctions or damages. If the typosquatting domain is actively diverting traffic to a site selling counterfeit goods, causing concrete harm in the Indian market, the complainant may need to pursue parallel court action in India for interim relief – again, through local litigation counsel in the relevant jurisdiction. The arbitration route and the court route are not mutually exclusive, but coordinating them requires care to avoid procedural inconsistencies.

In a second recent matter – a multi-domain typosquat campaign, winter 2025, involving approximately a dozen near-identical misspellings spread across .com and .in – we coordinated parallel UDRP and INDRP complaints. The complainant recovered all the .com domains through the UDRP and the .in domains through the INDRP within a comparable timeframe, avoiding the need for court action.

What is the minority view, and does it create a genuine risk for complainants?

The consensus in both UDRP and INDRP proceedings is that deliberate typosquatting of a well-known mark, combined with commercial use of the resulting domain, meets all three elements. That consensus is strong. But three minority or contrarian positions appear often enough to merit attention.

First, some panels have declined to transfer where the complainant's trademark was geographically limited – for example, registered only in a jurisdiction with no market presence in India. The argument runs that if the brand owner's rights are entirely foreign, the registrant cannot have been targeting the mark owner's Indian consumer base. This position is a minority one, but it surfaces in cases where the complainant relies solely on a home-country registration with no Indian trademark and no evidence of Indian trading activity.

Second, panels have occasionally refused transfer in cases where the complainant's trademark registration postdated the domain registration and the complainant could not demonstrate common-law rights as of the date the domain was registered. This is not unique to .in, but it is a trap for brand owners who file quickly without checking their trademark priority.

Third, the RDNH (Reverse Domain Name Hijacking) finding – available in UDRP proceedings and recognized in the INDRP context – represents a genuine risk for complainants who file without adequate evidence. An RDNH finding carries no monetary penalty, but it is a reputational mark against the complainant (and the complainant's counsel). We have defended respondents where the complainant had no registered trademark, a mark clearly postdating the domain, or a case theory that ignored a published legitimate-use website. In each instance, an RDNH finding was either secured or available. The availability of that finding is a check on abusive filings, and a complainant who cannot meet all three elements cleanly should pause before filing.

What evidence record wins a .in typosquat case?

Assembling the right evidence record is where a well-prepared complaint separates itself from a borderline one. The core package for a .in typosquat complaint should include the following elements, each matched to one of the three INDRP elements.

For confusing similarity: certified copies of the complainant's trademark registration in India, evidence of use in India predating the domain registration, and a side-by-side visual comparison of the mark and the disputed domain showing the precise typographic deviation. If the mark is unregistered in India, add evidence of acquired distinctiveness – advertising figures, media mentions, consumer-recognition surveys, or a declaration from a senior officer of the complainant.

For no legitimate interest: the WHOIS or RDDS record, the complainant's written confirmation that no authorization was ever granted, a screenshot of the resolving page, and, where the registrant has provided contact details, any correspondence showing a demand for payment or a refusal to engage. If the registrant operates under a privacy service, a request to unmask through NIXI's process should be made at or before filing.

For bad faith: screenshots of the resolving page over time (use a web archive service to capture historical states), evidence of the registrant's portfolio if multiple misspellings are held, any communications from the registrant offering to sell the domain at a price exceeding documented registration costs, and documentation of any consumer complaints or misdirected communications received by the brand owner.

What should a respondent assemble if contesting the complaint? The Paragraph 4(c) safe harbors are the starting point: a business registration or trading certificate predating the complaint, evidence of actual use of the string in commerce before notice of the dispute, and any evidence showing the string corresponds to a descriptive or personal-name basis unrelated to the complainant's mark. A response that produces these materials promptly – within the applicable response window – substantially changes the proceeding's dynamics.

Related at COGNOMEN

• UDRP domain recovery services – complainant and respondent work across all major forums
• Alert: recovering a typosquatted .shop domain – recent panel developments
• Guide: recovering a .shop domain from a passive-holding registrant

Author: Cordelia Roe — UDRP complainant practice & gTLD recovery; domain transactions and brand protection. Meet the team.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Domain in disputeYour sideI want to recover a nameI received a complaint — I need a defensePortfolio / brand protectionWhat happenedEmailI agree to the processing of my enquiry as described in the privacy policy.Assess my case

No obligation. Confidential. We reply within two hours in business hours.

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.