How to run due diligence before buying a .in domain

How to run due diligence before buying a .in domain. UDRP and ccTLD domain recovery and defense across .in. Email the firm to assess your case.

A domain acquisition can close in a day. The dispute it inherits can run for months. When the asset is a .in domain – India's country-code zone, administered by the National Internet Exchange of India (NIXI) – the governing dispute procedure, the eligibility rules, and the chain-of-title risks are all distinct from anything that applies to a .com. A buyer who skips the pre-purchase checks may own the name and the problem that came with it.

To run due diligence before buying a .in domain, you must verify chain of title, check the domain's prior-dispute history under the IN Domain Name Dispute Resolution Policy (INDRP), confirm no pending transfer lock or registry hold exists, assess whether the name's registration history creates bad-faith exposure under the INDRP three-element test, and structure an escrow arrangement that closes only on clean title. The INDRP is India's adaptation of the UDRP and closely tracks the three-element framework – confusing similarity, no legitimate interest, and bad-faith registration or use – with disputes administered by the National Internet Exchange of India through its appointed arbitrators.

This page covers each check in order, explains where .in diverges from the global UDRP standard, and sets out the realistic next steps for a buyer who is ready to proceed.

What governs .in domains – and why it matters before you buy

The INDRP is the mandatory dispute-resolution framework for .in registrations. It is modeled on the UDRP but administered through NIXI-appointed arbitrators, not through WIPO, the Forum, CAC, or ADNDRC. That distinction matters immediately: a brand owner who wants to challenge a .in registration cannot simply file with WIPO in the way a complainant can for a .com. The procedure runs through the NIXI INDRP machinery, and the arbitrator is drawn from a NIXI-approved panel rather than the global UDRP rosters.

The substantive three-element test mirrors the UDRP: the complainant must show the domain is identical or confusingly similar to a mark in which it has rights, that the registrant has no rights or legitimate interests in the domain, and that the domain was registered in bad faith and is being used in bad faith. That cumulative "registered AND used" standard – identical to the core UDRP requirement – is the point where a clean acquisition record becomes decisive. A seller whose historical use of the domain was passive parking, pay-per-click monetization on third-party marks, or redirect to a competitor's site may have handed any future complainant a ready-made bad-faith argument.

India also has its own national eligibility framework. The .in registry imposes registrant-eligibility requirements that differ from an open zone like .com. Before any acquisition, confirm that the buyer itself meets the current eligibility criteria and that the transfer will be permitted by NIXI's rules – because an ineligible buyer cannot hold the name regardless of what the escrow agreement says.

If you are assessing a .in acquisition and want a read on the INDRP risk profile before you commit, contact info@cognomenlaw.com.

How do you check chain of title for a .in domain?

Chain-of-title verification for a .in domain starts with the WHOIS/RDDS record and works backward through every registrant of record. The goal is to establish an unbroken line from the original registration to the current holder, identify every transfer event, and flag any gap that might indicate a hijacking, a forced transfer from a prior dispute, or an administrative cancellation followed by a re-registration.

Run the current NIXI WHOIS query first. Capture the registrant name, registrar, creation date, and expiry date. Note whether the domain shows a clientTransferProhibited, serverTransferProhibited, or other registry-level lock status. Any server-level lock that was not placed by the registrant on request is a red flag – it may signal an active dispute hold, a pending legal action, or a registry-initiated block.

Next, pull historical WHOIS data. Third-party archival services retain snapshots of registrant and nameserver history; some registrars will also produce a transfer log on formal request. What you are looking for: registrant changes without a corresponding escrow-transfer record, nameserver changes that point the domain at different commercial operations over time, and any period where the domain was pointed at parking or pay-per-click pages bearing marks that are not the registrant's own.

Each registrant change is a potential transfer event. Any transfer that occurred without consideration – particularly a transfer following a demand, a legal threat, or a dispute filing – is worth investigating further. A domain that was previously the subject of a forced transfer under the INDRP or a prior UDRP proceeding (if the domain was once registered in a gTLD zone as well) carries a documented bad-faith finding that a new complainant can cite.

In a recent matter (a .in acquisition, early 2025), we identified a historical server-level lock that the selling party had not disclosed. Further inquiry revealed a suspended INDRP proceeding from a prior year. The buyer paused, the escrow held, and the target domain was ultimately acquired only after the prior dispute record was resolved and NIXI confirmed clean title. The acquisition cost more time – not more money – because the checks ran before signing, not after.

What prior-dispute history reveals – and where to find it

Prior-dispute history is the single most predictive indicator of future challenge risk. A domain that has already been the subject of an INDRP arbitration, a WIPO complaint (if it was previously a gTLD or if the brand owner filed in a related zone), or an Indian court proceeding carries a record that any competent complainant will find and use.

The INDRP decisions are published by NIXI and accessible through the registry's online decision database. Search by domain name before completing any LOI or purchase agreement. A published decision transferring the domain to a prior complainant – even if that complainant later transferred it to the current seller – is a material fact. It tells you that at least one party has asserted trademark rights against this name, that an arbitrator found those rights plausible, and that the domain's bad-faith history is documented in a public record.

Also search the WIPO case database and the Forum's published decisions for any related domain. Brand owners who pursue .in names rarely target that zone alone; a complainant who won a .com transfer for the same mark is likely to notice, and contest, a .in holding that sits in the same portfolio.

What does a clean prior-dispute record tell you? It does not guarantee the domain is safe from future challenge. It tells you that no prior panel found the registration abusive – a useful data point, not a certification. The absence of a prior complaint says nothing about whether the name was registered in anticipation of a trademark right that had not yet been asserted.

One question worth asking at this stage: does the domain's commercial history support a legitimate-interest narrative? The Paragraph 4(c) safe harbors under the INDRP – bona fide offering of goods or services before notice of any dispute, being commonly known by the name, or legitimate noncommercial or fair use – attach to the registrant's own conduct. A buyer takes the name; it does not automatically inherit the seller's legitimate-use history. If the seller's legitimate interest was personal (a business operating under that name for years), confirm whether that interest survives a transfer to a new holder with a different identity.

How to structure escrow for a .in domain acquisition

Escrow is not optional for a domain purchase above a nominal value. It is the mechanism that aligns payment release with confirmed transfer completion – and for a .in acquisition, "confirmed transfer completion" means more than a registrar push. It means verifying that the NIXI transfer record updated, that no server-level lock re-appeared after transfer initiation, and that the domain resolves under the new registrant's control.

A properly structured .in escrow agreement covers four closing conditions. First, the seller delivers the domain transfer authorization code (the EPP/auth code) to the escrow agent. Second, the buyer initiates the transfer and confirms acceptance at the registrar level. Third, the registrar confirms the transfer to the new registrant of record at NIXI. Fourth, the buyer independently verifies the WHOIS/RDDS record shows the updated registrant data and the domain is free of server-level locks. Payment releases only when all four conditions are met.

Where any dispute hold, pending INDRP filing, or prior-dispute notation exists, the escrow agreement should suspend closing until that matter resolves and NIXI confirms the hold is lifted. This is not a negotiating point – it is a structural necessity. A payment that releases before a dispute hold lifts does not transfer clean title; it transfers a domain with an unresolved claim attached.

Sellers sometimes resist the delay this introduces. The commercial response is straightforward: the buyer is paying for a domain, not for the domain plus the cost of defending it. If the clean-title conditions cannot be met, the price needs to reflect the residual risk, or the deal does not close.

To structure escrow for a .in domain acquisition and confirm the closing conditions fit the registry's transfer mechanics, email info@cognomenlaw.com.

What evidence decides the outcome of an INDRP challenge after acquisition?

The evidence that decides an INDRP arbitration is the record of the domain's registration intent and commercial use – and a buyer inherits both, for better or worse. Understanding what a challenger would need to prove, and what the current record shows, is central to any pre-acquisition assessment.

Under the INDRP's three-element test, the hardest element for most complainants to satisfy is the cumulative bad-faith requirement: the domain must have been registered in bad faith and must be being used in bad faith. Registration intent is assessed at the moment of first registration, not at the moment of any subsequent transfer. This creates a dual protection for a buyer who acquires a domain with a clean registration history: if the original registrant had no knowledge of any relevant mark and registered the name for a legitimate purpose, that clean intent travels with the domain – it is not erased by a subsequent transfer.

The same logic works in reverse. If the original registrant registered the domain specifically to target a trademark owner, or in anticipation of a mark the complainant had applied for, the bad-faith finding attaches to the domain's registration history. A subsequent buyer – even one who paid a fair price and acted in good faith in the acquisition – cannot launder that history. The registration moment is fixed.

What specific evidence matters most? The original registration date relative to the complainant's trademark priority date is the threshold question. If the mark predated the registration, and the registrant's conduct at the time of registration shows awareness of the mark, bad faith is a credible allegation. If the mark postdates the registration, that allegation largely fails at the first gate – panels have consistently found that a domain cannot be registered in bad faith as to a mark that did not yet exist, absent extraordinary circumstances such as a clearly foreseeable brand launch.

Historical use evidence – archived pages, monetization records, registrant correspondence about the name – is equally significant. Parking pages that displayed pay-per-click links to competitors in the mark owner's industry are among the most consistently cited bad-faith indicators across UDRP and INDRP proceedings. If the domain's archive shows that history, build it into the risk assessment before closing.

How does the .in procedure compare with the UDRP and the gTLD route?

The right route depends on the zone and the nature of the dispute. If the same brand is registered as both a .com and a .in, a complainant has two distinct paths. For the .com, the UDRP applies – filing with WIPO at a starting fee of USD 1,500 for a single-member panel, with a standard decision timeline of roughly two months. For the .in, the INDRP applies, administered through NIXI-appointed arbitrators with its own fee schedule and procedural rules.

The two procedures run separately; a complainant cannot consolidate a .com and a .in in a single UDRP filing unless both domains share the same registrant and the filing meets the UDRP's requirements for multi-domain complaints. In practice, a brand owner who holds a UDRP transfer order for a .com will often move next against the corresponding .in – and will use the UDRP decision as persuasive (though not binding) evidence of the mark's priority and the registrant's bad-faith pattern.

For a buyer who acquires a .in domain, this cross-zone dynamic is a real risk factor. A seller who lost the .com under the UDRP, then transferred the .in to a nominee, then offered the .in for sale is not a hypothetical scenario – it is a known acquisition pattern in markets where brand owners pursue only the most prominent zone first. A thorough due diligence check runs the seller's identity against UDRP decision records across all zones, not just the .in registry.

Court litigation in India is the alternative for disputes that fall outside the INDRP's scope, or where the claimant seeks monetary relief or injunctive remedies that the INDRP cannot provide. The INDRP, like the UDRP, delivers only transfer or cancellation. It awards no damages, imposes no costs beyond the arbitration fee, and cannot restrain the respondent from operating a related website through a different domain. Where the commercial harm extends beyond the domain itself, the national court route – handled with local litigation counsel in the relevant jurisdiction – is the appropriate complement.

What is the realistic risk if you skip pre-acquisition due diligence for a .in domain?

The realistic risk of skipping pre-acquisition checks for a .in domain is not abstract. It has three concrete forms: a post-closing INDRP complaint that targets the name you just bought, a domain that cannot be transferred because of a hold you did not know existed, and a purchase price that reflects a clean asset but funds the transfer of a tainted one.

Can a new owner defend an INDRP complaint filed after a legitimate acquisition? Yes, in principle. The new registrant can appear, document its own good-faith acquisition, and argue that the registration history – however it looked under prior ownership – no longer supports the bad-faith element. Panels have considered post-transfer acquisition arguments. But the outcome turns on the facts: if the underlying registration was abusive and the prior bad-faith use is documented, a new owner's clean intent at the moment of acquisition may be insufficient to defeat the element that attaches to the domain, not the person.

In a second matter from our recent practice (a .in domain acquisition, spring 2025), a registrant acquired a name through a marketplace platform without prior INDRP screening. Within three months of closing, the prior complainant – who had filed and withdrawn a proceeding before the sale – refiled against the new registrant. The new owner bore the full cost and time of a contested defense, despite having paid market rate for the domain in good faith. The defense ultimately succeeded on the registration-date analysis, but the outcome was not certain, and the cost of the defense exceeded the acquisition price of the domain itself.

That pattern is precisely what pre-acquisition due diligence is designed to prevent. The checks are not bureaucratic formality. They are the mechanism that makes the purchase price rational.

How should you handle a .in domain with prior complaints or a disputed title?

A .in domain with a prior INDRP complaint or a disputed title is not automatically off the table. It is a different commercial transaction – one that requires a different structure, a different price, and explicit agreement on who bears the residual risk.

Three approaches are available. First, condition the acquisition on resolution of the prior matter. The escrow does not close, and the purchase price does not release, until the prior complaint is withdrawn, dismissed, or decided in the seller's favor and any appeal period has lapsed. This is the cleanest path and the one we recommend where the prior complaint is active or recently resolved.

Second, obtain a price reduction that reflects the cost of defending a potential re-filing. If the prior complainant withdrew voluntarily and disclosed no settlement, the risk of re-filing persists. Price the domain as if the defense cost will materialize; if it does not, the buyer retains the discount.

Third, obtain a representation and warranty from the seller that the prior complaint is fully resolved, that no further claims are pending or threatened, and that the seller will indemnify the buyer against costs arising from any claim rooted in conduct or use predating the transfer. A warranty without an indemnity is commercially thin; insist on both.

What if the title dispute stems from a domain-hijacking event rather than a trademark complaint? That is a distinct recovery path: registrar escalation, account-compromise documentation, and transfer-reversal procedures at the registry level, handled before any acquisition closes. Acquiring a domain whose title is in question because of a prior hijacking does not clear the hijacking; it compounds it.

Related at COGNOMEN

• Domain transactions, due diligence, and brand-protection services
• Guide to domain due diligence in cloud and SaaS brand acquisitions
• ccTLD mediation and dispute procedures: a country-code guide