Step-by-step: bring a court action when UDRP cannot reach a .in domain

Step-by-step: bring a court action when UDRP cannot reach a .in domain. UDRP and ccTLD domain recovery and defense across .in. Email the firm to assess your ca…

A brand owner traces a cybersquatting registration to a .in domain, prepares for a UDRP filing, and then discovers the problem: .in is governed by NIXI's INDRP, not the standard UDRP. The rules are related but distinct, the registry is Indian, and if the INDRP route has closed or is otherwise unavailable, the next path runs through the Indian civil courts. That shift changes everything – the timeline, the evidence standard, the relief available, and the strategic calculus.

To bring a court action when UDRP cannot reach a .in domain, a complainant must work through India's national courts, typically seeking an injunction and transfer order under the applicable national trademark and information-technology legislation. The INDRP arbitration run by NIXI is the primary administrative remedy for .in, but court action becomes necessary where the INDRP is unavailable, exhausted, or inadequate – for example, where damages are sought, where the registrant is unresponsive to arbitration, or where the domain is part of a larger cybersquatting or passing-off claim. Filing fees and timelines are determined by the Indian courts, not by WIPO or the Forum, and outcomes depend on the facts presented and the court's discretion.

This guide walks each step in sequence, identifies the trap hidden in each one, and explains when the court route is the stronger call and when it is not.

How does .in dispute resolution actually work – and when does INDRP fall short?

The .in ccTLD is administered by the National Internet Exchange of India (NIXI), which operates the .in Dispute Resolution Policy (INDRP) as the administrative remedy for abusive registrations. The INDRP tracks the three-element UDRP structure closely – confusing similarity, no legitimate interest, bad-faith registration and use – but it is a wholly separate procedure governed by Indian arbitration rules and heard by arbitrators appointed under the Arbitration and Conciliation Act of the relevant jurisdiction. It is not WIPO. It is not the Forum. WIPO has no jurisdiction over .in under INDRP unless NIXI separately appoints it.

So when does the INDRP fall short? Several situations arise in practice. First, if the registrant has committed domain theft rather than simple cybersquatting, the INDRP has limited capacity to address the chain-of-title issues and account-compromise evidence that a theft claim requires. Second, if the complainant seeks monetary damages – compensation for lost traffic, diversion of customers, or passing-off loss – the INDRP, like the UDRP, cannot award money. Third, if the registrant is demonstrably a serial abuser operating through layered privacy or proxy registration, the evidentiary reach of court subpoena power goes further than an arbitration panel's discovery tools. Fourth, INDRP decisions, while binding in arbitration, require separate enforcement steps if the registrant resists. A court order is more directly enforceable.

In our practice advising brand owners on cross-border disputes, we regularly encounter .in registrations that combine a cybersquatting motive with passing-off, trademark infringement, or outright phishing. Those multi-layered claims almost always require the court route, either instead of or in addition to INDRP.

To assess whether the INDRP, a court action, or a parallel approach is the right path for your .in domain, contact info@cognomenlaw.com.

Step 1: Confirm that court action is the appropriate route before you invest in it

The first decision – and the most consequential trap in the whole process – is assuming the court route is necessary before checking whether INDRP is available and adequate. Court litigation in any jurisdiction costs more, takes longer, and demands more of the client than administrative arbitration. File first in INDRP if the claim fits; reserve court action for the cases where it genuinely adds something the INDRP cannot deliver.

Run this checklist before proceeding to court. Does the claim involve monetary damages? INDRP cannot award them; court can. Is the registrant also infringing a trademark through active use of the domain that could sustain a passing-off or infringement injunction? A court action carries a broader injunction remedy. Is the situation a domain theft – meaning the .in was originally yours, was transferred without authorization, and you need to reverse an unauthorized transfer? Court action, combined with a registrar escalation and a DENIC-equivalent registry lock request, is the more direct path. Is the INDRP time-barred or otherwise closed? Then court is the only administrative alternative.

One critical fact: NIXI's INDRP arbitration and an Indian court action are not always mutually exclusive. Depending on the posture of the claim and the stage of proceedings, it is possible to pursue arbitration while preserving or initiating court proceedings for ancillary relief, particularly interim injunctions. Your local litigation counsel in the relevant jurisdiction will confirm whether that parallel strategy is available under the current procedural rules.

Trap in Step 1: Clients who start with a court filing without checking INDRP availability often find that the court refers the matter back to arbitration, wasting both time and the filing fees paid.

Step 2: Assemble the evidence – what decides the outcome in an Indian court?

Indian courts adjudicating cybersquatting and domain disputes apply a combination of national trademark law, passing-off principles, and the information-technology legislation in force at the time of filing. No statute article numbers are cited here, because branch references vary; your local litigation counsel will confirm the current operative provisions. What matters for this guide is the category of evidence the court will require, because that determines how you build the file.

The core evidence kit has four components. First, trademark ownership documentation: your registered trademark certificates, proof of filing dates, and if the mark is unregistered, evidence of acquired distinctiveness and prior use (sales records, advertising invoices, media coverage). Second, the .in WHOIS and registration history: print and preserve the current WHOIS/RDDS record for the disputed domain, including the registrant name, registrar, registration date, and any historical WHOIS snapshots available through archive tools. Third, evidence of bad faith or abusive use: screenshots of the domain's resolving page, emails sent from the domain, evidence of phishing, pay-per-click monetization, or active passing-off; all screenshots should be captured with timestamps and a notarized or certified digital verification where possible. Fourth, harm evidence: where damages are sought, quantified evidence of traffic diversion, lost sales, consumer confusion reports, or brand reputation damage. Courts award damages on proof, not on assertion.

The trap in Step 2 is timing. WHOIS data degrades. Registrant details can be masked through privacy services before the filing date. Domain parking pages can be taken down overnight. Preserve everything as early as possible, before any demand letter or notice reaches the registrant.

In a recent matter (a .in domain used for phishing, spring 2025), our team assembled the evidence file – certified WHOIS captures, archived parking-page screenshots, and trademark registration certificates – within 72 hours of the client's instruction. That speed was decisive because the registrant took the domain offline within days of receiving informal notice. Early preservation of the live state of the domain was the record the court ultimately relied on.

Step 3: Registrar lock and transfer-reversal mechanics – stop the domain moving while you litigate

One of the greatest risks in any domain dispute – and a particular hazard in court proceedings, which are slower than INDRP – is that the domain is transferred to a new registrant, moved to a different registrar, or re-registered to a different entity during the proceedings. That transfer can make the court order harder to enforce and requires additional steps to reverse.

The mechanics of a registrar lock in the .in context work as follows. NIXI, as the .in registry, has authority to place a lock on a domain that prevents transfer while a dispute is pending. In court proceedings, a court-ordered interim injunction can direct either the registrar or NIXI to place a registry-level lock on the domain. This is the functional equivalent of what DENIC's DISPUTE entry does in the .de context: it holds the domain in stasis while the substantive claim is resolved. Filing for an interim injunction – commonly styled as an ad interim or ex parte injunction in the Indian courts – should therefore be among the very first steps after evidence preservation, not an afterthought after the case is briefed.

Transfer-reversal mechanics require a separate analysis if the domain was already transferred without authorization before you could lock it. In that scenario, the complaint is in part a domain theft claim rather than a cybersquatting claim. The steps then are: (a) escalate immediately to the registrar of record, documenting the account compromise with server logs, email headers, and any other evidence of unauthorized access; (b) file a formal abuse report with NIXI citing the unauthorized transfer; (c) seek a court order directing the registrar to reverse the transfer and restore the registration to the original holder. We regularly advise registrants navigating exactly this sequence, and the window for successful reversal is short – typically measured in days, not weeks.

Trap in Step 3: Clients who delay the interim injunction application – waiting for the full complaint to be briefed – often find the domain has moved registrars by the time the application is heard. Apply for interim relief on an urgent basis, separately and immediately.

If your .in domain has already been transferred without authorization, the window for reversal is narrow. Contact info@cognomenlaw.com for an immediate assessment.

Step 4: Drafting the court filing – structuring the claim to maximize the chance of transfer or injunction

An Indian court action for a .in cybersquatting dispute is not a single claim type. It typically combines multiple causes of action, framed around the relief sought. The two primary heads of relief are a permanent injunction against use of the domain (and, where feasible, an order for transfer) and damages or account of profits where the domain was used to generate revenue or cause quantifiable harm.

The claim structure should do the following. It should identify the claimant's trademark rights with precision, anchored to a specific registration date that predates the domain's registration. It should plead the confusing similarity between the mark and the domain, addressing any additions (hyphens, generic words, country suffixes) that the registrant may argue distinguish the two. It should set out the bad-faith indicators: the timing of registration relative to the mark's public recognition, the content served at the domain, any demand for payment, and any pattern of similar registrations by the same registrant. Where domain theft is alleged, the claim must separately plead the unauthorized access, the registrar's failure (if any) to verify the transfer request, and the chain of title that demonstrates the claimant's original ownership.

The decision matrix here is between two approaches. Where the registrant is identifiable and solvent, a full damages claim alongside injunctive relief maximizes recovery. Where the registrant is anonymous or offshore, the priority is injunctive relief and transfer, with damages as a secondary head that may be assessed later. Court proceedings in India allow for an ex parte application for interim relief before the defendant is served, which can be critical in fast-moving theft scenarios.

In a recent matter (a .in brand impersonation, autumn 2024), we worked with local litigation counsel to file an ex parte application for interim injunction within 48 hours of instruction. The domain was locked at the registry level within a week, before the registrant had any opportunity to move it. The substantive case then proceeded on a full schedule. That sequencing – lock first, litigate second – is the standard approach we recommend for any .in dispute that reaches court.

Step 5: Forum selection and practical procedural considerations for .in court litigation

Indian courts with jurisdiction over domain disputes are typically the High Courts – specifically those with jurisdiction over intellectual-property matters in the relevant territorial district. The choice of court and the applicable procedural rules are questions for your local litigation counsel, who will confirm which forum carries jurisdiction based on the claimant's domicile, the place of business, and the location of the infringing activity.

One practical consideration deserves emphasis: court proceedings in India, like litigation in most jurisdictions, are substantially more expensive and time-intensive than INDRP arbitration. A full court case from filing to final order commonly takes significantly longer than an INDRP decision, which itself runs longer than a UDRP case. Where the claimant's primary goal is domain transfer and the facts fit the INDRP three-element test, INDRP remains the faster and cheaper path. Court action earns its cost premium where damages are a real objective, where the claim involves theft with account-compromise evidence, or where the breadth of injunctive relief sought goes beyond what INDRP can grant.

The cross-zone dimension matters here too. A brand owner with disputes across .com and .in faces two separate procedures with two different standards. The .com can go to WIPO or the Forum under the UDRP, with a filing fee starting at USD 1,500 for a single-member panel and a typical timeline of about two months. The .in requires INDRP or Indian court action – neither of which WIPO administers under the standard UDRP framework. Coordinating both proceedings requires careful sequencing: the evidence assembled for one can often support the other, but the filing strategies and timelines must be managed separately.

Step 6: What happens after the court order – enforcement, transfer, and next steps

A successful court order in an Indian cybersquatting action typically directs the registrar and/or NIXI to transfer the domain to the claimant or to cancel the registration. Enforcement of that order runs through the registrar and the registry. If the registrar of record is an Indian-accredited registrar under NIXI, the order is served directly. If the registrar is an international entity, service of the court order may require additional steps, including service through the registrar's Indian registered office or through NIXI as the registry authority with power to implement transfers at the registry level regardless of the registrar.

Post-transfer steps are equally important. Once the domain is transferred, the new registration details should be updated immediately to reflect the claimant's correct WHOIS data. Any DNS propagation should be monitored. Where the domain was actively used by the cybersquatter – whether as a phishing site, a parking page, or a passing-off vehicle – the existing DNS records (A records, MX records) should be audited and corrected before the domain is put to any use. Residual malware or phishing infrastructure linked to the domain during the cybersquatter's tenure can cause downstream harm if not cleared.

Finally: winning the court order does not end the risk. A determined registrant may re-register similar domains under different extensions or in other ccTLDs. Portfolio monitoring – tracking new registrations of your brand across gTLDs and ccTLDs – is the standard follow-on step after any domain recovery action. That monitoring is part of the brand-protection service COGNOMEN provides alongside dispute and recovery work.

Related at COGNOMEN

• Court action and domain theft recovery – the full COGNOMEN service overview
• Registrar lock and escalation mechanics in ccTLD disputes – analysis (.au focus)
• Responding within deadline in ccTLD disputes – analysis (.ae focus)