Step-by-step: structure escrow for a .in domain purchase

Step-by-step: structure escrow for a .in domain purchase. UDRP and ccTLD domain recovery and defense across .in. Email the firm to assess your case.

A brand owner identifies the perfect .in domain – already registered by a third party asking a five-figure sum. Before any money moves, one question decides whether the deal ends with a clean title or a costly dispute: is this domain safe to buy, and is the escrow structured to protect the acquirer if it turns out it is not?

To structure escrow for a .in domain purchase, a buyer must run a chain-of-title check, verify INDRP dispute history, confirm the seller's eligibility to hold a .in registration, and use a neutral escrow arrangement that conditions fund release on verified transfer completion at the NIXI registry. The .in zone is governed by NIXI and disputes proceed under the INDRP – a procedure with its own eligibility rules that can void a registration after a sale closes. A structurally sound escrow typically takes two to four weeks to execute when due diligence is clean.

This guide walks each step in order, flags the trap that hides in each one, and shows where a prior dispute history can turn a routine purchase into a recovery problem.

Step 1: Why the .in zone creates unique pre-purchase risk

The .in registry is administered by the National Internet Exchange of India (NIXI), and its dispute procedure – the INDRP – operates under rules that differ from the UDRP in ways that matter to a buyer. Understanding those differences before any escrow is funded is the foundation of the whole structure.

Unlike the UDRP, which requires that a domain was registered and used in bad faith cumulatively, the INDRP uses a slightly different standard that can expose a domain to challenge even where subsequent use has been passive. That distinction means a domain that looks dormant in WHOIS/RDDS could carry latent dispute exposure. A buyer who acquires it takes on not just the name but the risk that a future complainant applies the INDRP standard to the registration history of the original registrant.

What creates the specific trap at Step 1? Buyers often assume that a transfer resets the dispute clock. It does not. Panels reviewing post-transfer registrations regularly examine the original registration date, the original registrant's conduct, and whether the transfer itself was structured to launder a bad-faith history. Acquiring a tainted .in domain without due diligence can leave the buyer exposed to an INDRP complaint from day one of ownership.

The practical check at this step: confirm the registry zone is .in (not a confusable variant such as .co.in or .net.in), identify the current administrative and technical contact records through NIXI's RDDS, and note the original registration date. That date will anchor the chain-of-title review in Step 2.

If you are at the early stage of evaluating a .in acquisition and want a read on INDRP exposure before committing to price, contact info@cognomenlaw.com.

Step 2: How do you run a chain-of-title check for a .in domain?

A chain-of-title check for a .in domain traces every recorded transfer since the original registration, confirms that each transfer was authorized by the then-current registrant, and identifies any periods of disputed ownership. It is the single most important pre-escrow task.

The check has three layers. First, RDDS/WHOIS history: where available, review historical snapshots of the registration record to map prior registrants, prior registrars, and any gaps or anomalies in the registration timeline. Second, INDRP case archives: NIXI publishes INDRP decisions; a search on the disputed domain string, on the seller's name, and on any known affiliated names will surface prior proceedings. A domain that was once the subject of a complaint – even one that was withdrawn or decided in the registrant's favor – signals a contested name. Third, trademark clearinghouse and national trademark office search: check whether any Indian trademark owner holds a registration or pending application that is identical or confusingly similar to the domain string. That owner is a potential future complainant regardless of the current seller's good faith.

The trap in Step 2 is chain fragmentation. A domain that has changed registrars twice and registrants once in five years may have RDDS records that do not fully document each change. Gaps in the chain suggest either an undocumented transfer or, in worst cases, an unauthorized one. Where the chain cannot be closed through registry records, a representation-and-warranty clause in the purchase agreement must fill the gap – backed by an indemnity that survives the transfer.

We regularly advise buyers who discover, mid-due-diligence, that a .in domain passed through three hands in eighteen months without any documented assignment. That fact pattern is almost always a signal of either a dispute that was settled outside the record, or an acquisition at distress price that the buyer is now being asked to pass on. Neither is a reason to abort – but both require a price adjustment and a restructured escrow hold.

Step 3: What does the INDRP dispute-history check tell a buyer?

A prior INDRP proceeding against a domain – even one resolved years ago – tells a buyer three things: that a trademark owner once believed the name was registered in bad faith, that a panel reviewed the evidence, and that the outcome of that review is now part of the domain's public record.

If the prior complaint resulted in a transfer order that was appealed or not implemented, the domain may still be subject to challenge. If it resulted in a finding for the registrant, review the reasoning: a decision on a narrow technical ground (say, the complainant lacked sufficient trademark rights at the time) does not insulate the domain against a better-resourced future complaint by a different rights-holder. If the complaint was withdrawn before decision, the reason for withdrawal is unknown and the risk is unquantified.

The INDRP also recognizes a complaint pattern worth noting for acquirers: where a domain has been transferred shortly before a complaint was anticipated, some panels have looked skeptically at the transfer and treated the new registrant's conduct as continuous with the prior registrant's. That doctrine – sometimes described as treating a bad-faith transfer as ineffective to cure a bad-faith registration – is the specific legal risk that a clean escrow structure must address.

Practically, the check means: run the domain string through the NIXI INDRP decision database, and then run the seller's name and registrant organization. A seller with a pattern of prior INDRP losses on other domains is a red flag even if the specific domain being sold has a clean record.

If a prior dispute appeared in your INDRP search and you want to assess what it means for the proposed acquisition, email info@cognomenlaw.com.

Step 4: How to structure the escrow arrangement itself

Once due diligence is complete, the escrow structure for a .in domain purchase follows a defined sequence: the buyer funds escrow, the seller initiates the NIXI transfer, the buyer confirms receipt of the authorization code (auth-code or EPP key), and the escrow agent releases funds only after the buyer completes the transfer at their chosen NIXI-accredited registrar. Every deviation from this sequence creates a gap that can leave one party unprotected.

The neutral escrow agent is the structural keystone. The agent holds funds in a trust account, communicates with both parties, and releases funds against a defined trigger – completion of the domain transfer, confirmed in writing by the buyer. The agent does not decide disputes; the agent executes the agreed release condition. Choosing an escrow service that has experience with domain name transactions, rather than general merchandise escrow, matters because domain transfer mechanics – auth-code expiry, registrar push timing, registry transfer windows – require a trigger definition that a general commercial escrow template may not handle correctly.

The release trigger deserves specific attention. A release condition that reads "transfer of the domain to the buyer's registrar account" is stronger than one that reads "provision of the auth-code by the seller." Auth-codes can expire, can be generated multiple times, and – in cases of account compromise – can be issued without the registrant's authorization. Tying escrow release to verified WHOIS/RDDS confirmation that the buyer's registrar is now shown as the registrant's registrar of record, and that the buyer's contact data appears in the registration, is the tightest standard.

Timing matters. NIXI's transfer process runs through accredited registrars and involves a standard registrar-to-registrar transfer window. Structure the escrow hold period to exceed that window with a buffer – typically the transfer window plus five business days – so that a registrar-side delay does not trigger a premature fund release or a disputed hold extension.

In a recent matter (a .in brand acquisition, spring 2025), we structured an escrow arrangement where the release trigger was RDDS confirmation of the new registrant of record, with a ten-business-day buffer over the standard NIXI transfer window. The prior registrant had attempted to revoke the auth-code during the transfer window, citing a claimed internal authorization dispute. Because the escrow had not yet released funds, the buyer was fully protected, the revocation was reversed, and the transfer completed within the buffer period.

Step 5: What must the purchase agreement cover for a .in transaction?

The purchase agreement for a .in domain is not a standard asset sale contract. It must address the specific mechanics of NIXI registration, the representations unique to domain title, and the indemnities that survive the transfer and address future INDRP exposure.

The minimum required provisions are these. First, a representation that the seller is the sole registrant of record, that no third party holds any claim or interest in the domain, and that no INDRP or other dispute proceeding is pending or threatened. Second, a warranty that the domain was not registered in bad faith with respect to any trademark owner's rights – this is the provision that shifts residual INDRP risk back to the seller. Third, an indemnity: if a third party files an INDRP complaint within a defined period after the transfer and the complaint is based on conduct predating the sale, the seller bears the cost of defense and any adverse outcome. Four to five years is a reasonable indemnity window for .in, given that INDRP complaints can surface on names that have been dormant for extended periods.

The trap in Step 5 is the "as-is" clause. Sellers of secondary-market domain names routinely propose an as-is sale with no representations. For a low-value generic domain this may be acceptable. For any domain carrying trademark exposure, an as-is clause without a carve-out for INDRP claims is commercially unreasonable for the buyer. Negotiate the warranty and indemnity as non-negotiable items; if the seller will not provide them, price the residual dispute risk into the purchase price or walk away.

For a detailed look at how assignment agreements interact with prior-dispute history across multiple zones, see our analysis of domain assignment agreements.

Step 6: Cross-zone considerations – when the acquisition spans more than .in

A buyer acquiring a .in domain rarely acquires it in isolation. Brand protection strategy typically requires securing the .com, .net, and regional ccTLD equivalents in parallel. When those zones are in play simultaneously, the escrow structure and due diligence process must account for each zone's separate registry mechanics and separate dispute procedures.

The decision matrix runs roughly as follows. If the target portfolio includes a .com alongside the .in, the UDRP governs disputes in the .com zone and the INDRP governs the .in zone. The two procedures share structural similarities but the bad-faith standard and the panel's approach to post-transfer registration differ. Run separate UDRP and INDRP dispute searches for each domain. Structure separate escrow triggers for each zone, because NIXI transfer mechanics and ICANN/gTLD transfer mechanics run on different timetables. Do not use a single release trigger that treats a .com transfer and a .in transfer as a single event.

If the acquisition also involves a .uk domain, Nominet's transfer mechanics apply, and the Nominet DRS governs any future dispute. The Nominet DRS test – whether a registration is "abusive" – uses an "OR" standard for the use limb, distinct from both the UDRP and the INDRP. That difference affects how a prior dispute record in one zone is read in another: a domain that survived a UDRP complaint is not automatically safe from a Nominet DRS complaint, and vice versa.

Where the brand has operations in multiple jurisdictions, the cross-zone due diligence should include a trademark clearance search in India (for .in) and in each country whose ccTLD is being acquired. An Indian trademark registration in the relevant class is strong evidence against a future INDRP complaint; its absence is a gap that a future complainant can exploit.

In a separate recent matter (a multi-zone acquisition spanning .in, .com, and .co.uk, summer 2025), we ran parallel INDRP, UDRP, and Nominet DRS searches and discovered that the .in domain had a prior INDRP complaint (withdrawn by the complainant) that had not appeared in the seller's disclosures. The acquisition was restructured: the escrow for the .in domain was held an additional thirty days, the warranty and indemnity provisions were expanded, and the purchase price was adjusted to reflect the residual dispute risk. The transaction closed cleanly.

Step 7: What happens if an INDRP complaint is filed after the purchase?

If a third-party trademark owner files an INDRP complaint against the domain after the buyer has completed the purchase, the buyer becomes the respondent. The INDRP procedural timeline is set by the registry rules, and the respondent has 20 days to file a response after the complaint is formally commenced. That deadline is fixed; missing it results in a default decision on the complainant's papers alone.

The buyer-respondent's primary defense is legitimate interest. Paragraph 4(c) of the UDRP – and its INDRP equivalent – recognizes that a registrant who acquired a domain in good faith, paid fair market value, and has no intent to target a trademark owner has a defensible position. The escrow documentation, the purchase agreement, the due diligence record, and the chain-of-title analysis all become exhibits in that defense. This is the direct reason why thorough pre-purchase documentation is not merely good practice: it is the evidentiary record that makes a post-purchase defense possible.

Where the indemnity provision in the purchase agreement is in place, the seller bears the cost of that defense. Where the domain was purchased as-is with no representations, the buyer bears the full cost alone – which is why the provisions in Step 5 are non-negotiable for any name with trademark exposure.

For a detailed analysis of how to prove legitimate interest in a dispute context, see our guide on how to prove legitimate interest.

If the post-purchase INDRP complaint is itself abusive – filed by a rights-holder whose mark postdates the domain registration, or by a complainant who misrepresents its rights – the respondent can seek a finding of reverse domain name hijacking (RDNH). An RDNH finding does not carry monetary penalties under the INDRP, but it is a formal public record that the complaint was brought in bad faith, which has real reputational weight for repeat complainants.

Related at COGNOMEN

• Domain transactions and pre-acquisition due diligence across gTLDs and ccTLDs
• How domain assignment agreements interact with prior dispute history
• How to prove legitimate interest in a UDRP or INDRP proceeding