How to draft a domain assignment agreement for a .in domain

How to draft a domain assignment agreement for a .in domain. UDRP and ccTLD domain recovery and defense across .in. Email the firm to assess your case.

A .in domain changes hands on a handshake far more often than it should. The registrant transfers the name, the buyer pays, and six months later a dispute surfaces – a prior INDRP proceeding, a lien from a previous owner, or a registry eligibility problem that voids the transfer entirely. The agreement drafted on the day of the deal is the instrument that either prevents that outcome or accelerates it.

To draft a domain assignment agreement for a .in domain, the parties must address the governing registry rules under NIXI and the INDRP, confirm chain of title, disclose any prior dispute history, and structure escrow to protect both sides. A well-drafted agreement is typically concluded within one to three weeks depending on due-diligence findings and negotiation. Without a written instrument verified against the registry's transfer mechanics, neither side has a defensible record of what was sold.

This page covers the governing rules, the essential clauses, the due-diligence steps that decide whether the deal is safe, and how COGNOMEN structures .in domain transactions from first instruction to registry confirmation.

What rules govern a .in domain assignment?

A .in domain is administered by NIXI (the National Internet Exchange of India), and every .in registration is subject to the INDRP – the .in Domain Name Dispute Resolution Policy – which is a close adaptation of the UDRP. That policy travels with the domain. A buyer who acquires a .in domain from a registrant who registered it in bad faith may inherit an abusive registration; an INDRP complainant can pursue a transfer remedy against any current registrant, not only the original one. Chain-of-title matters here for the same reason it matters in real property.

The INDRP uses a three-element test that parallels the UDRP's Paragraph 4(a): the complainant must show that the domain is identical or confusingly similar to a name or mark in which it has rights, that the registrant has no rights or legitimate interests, and that the domain was registered or is being used in bad faith. That "registered or used" formulation is a materially lower bar than the UDRP's cumulative "registered and used" standard. A buyer who inherits a domain being used in bad faith – even if the original registration was clean – can face a successful INDRP complaint. This is not a theoretical risk. In our practice we have seen post-acquisition INDRP filings directed at buyers who performed no pre-closing due diligence.

At the registry level, NIXI processes transfers through accredited registrars and requires a valid authorization code (EPP/Auth code) from the losing registrant. The registrar must confirm eligibility – .in is open registration with no strict nexus requirement for most second-level names, but certain third-level zones (.co.in, .net.in, .org.in, .gen.in, .firm.in, .ind.in) carry historic eligibility policies that the registrar must verify. An assignment agreement that recites the wrong zone or misidentifies the registrar adds delay and, in edge cases, can cause a failed transfer that triggers a default renewal cycle.

What are the essential clauses in a .in domain assignment agreement?

A binding .in domain assignment agreement should contain at minimum eight substantive provisions, each calibrated to the zone's specific rules and transfer mechanics.

• Identification of the asset. The full domain name, the zone (.in or the relevant third-level variant), the registrar of record, and the registrant's WHOIS/RDDS data as of the agreement date. Any discrepancy between the contract and the registry record is a due-diligence flag.
• Representation of good title. The assignor warrants that it is the sole legal owner, that no lien, pledge, or security interest encumbers the domain, that no INDRP or court proceeding is pending or threatened, and that the domain was not registered in violation of any third party's trademark rights. This clause is the written form of the chain-of-title search.
• Dispute-history disclosure. The assignor discloses all prior INDRP filings involving the domain, all court proceedings, all cease-and-desist demands received in connection with the domain, and any registrar-level locks or holds. Silence is not sufficient; the clause must require affirmative disclosure.
• Consideration and payment mechanics. The purchase price, currency (INR or foreign currency with any required regulatory acknowledgment under Indian foreign-exchange rules), payment milestones tied to transfer completion, and the consequence of non-payment.
• Escrow structure. For any transaction above a nominal threshold, funds are held by a neutral third-party escrow service pending registry confirmation of the transfer. The escrow release condition is the buyer's receipt of the authorization code and successful completion of the registrar-to-registrar transfer, verified by a WHOIS/RDDS check showing the buyer as the new registrant of record.
• Transfer mechanics and timeline. The assignor agrees to provide the authorization code within a stated number of business days of escrow confirmation; the buyer agrees to initiate the transfer within a stated window. Both parties agree to cooperate with the registrar's verification process. A longstop date triggers escrow reversal if the transfer fails.
• Representations on INDRP eligibility. The assignor confirms that the domain was registered in good faith and is not subject to any agreement that would give a third party a prior right to the name. The buyer acknowledges that it has conducted its own due diligence and is not relying solely on the assignor's representations.
• Governing law and jurisdiction. Indian law governs .in domain assignments as a practical matter; the registrar agreement with NIXI is subject to Indian law, and an INDRP proceeding will apply Indian law and INDRP rules. The agreement should designate Indian law expressly, specify a forum for commercial disputes between the parties, and address the parties' rights if a post-closing INDRP complaint is filed by a third party.

If you are buying or selling a .in domain and need a reviewed assignment agreement, contact info@cognomenlaw.com for an assessment of the transaction structure and the due-diligence scope.

How do you perform due diligence on a .in domain before assignment?

Due diligence on a .in domain has four tracks: chain-of-title, dispute history, trademark clearance, and registry-status verification. Skipping any track is the mechanism by which buyers acquire problems rather than assets.

Chain-of-title. The WHOIS/RDDS record for a .in domain shows the current registrant and, through registrar-held audit data, often the registration history. Where the domain has changed hands multiple times, each prior assignment should be traceable. An unexplained gap – a registration period with an unrelated registrant, a sudden change of registrant contact data shortly before the present deal – warrants a direct inquiry to the registrar and, where available, a review of archived WHOIS snapshots. We regularly advise buyers to obtain the assignor's confirmation of every prior registrant during the domain's lifetime, backed by the disclosure clause described above.

INDRP dispute history. INDRP decisions are published by the INDRP service providers. A search against the domain name will surface any decided case. Pending filings may not be publicly visible until decided, which is why the contractual disclosure clause is essential – the assignor's representation fills the gap that a database search cannot. A prior INDRP finding of bad faith against the domain is not disqualifying per se, but it is a strong indicator that the name carries trademark risk. A prior RDNH finding against a complainant, on the other hand, can be evidence that the domain has a legitimate history.

Trademark clearance. The buyer should run a search against Indian trademark registers for marks that are identical or confusingly similar to the domain. A conflicting mark creates INDRP exposure for the buyer post-closing. The search should cover the relevant class or classes for the use the buyer intends, plus a broader search for marks that are phonetically or visually similar to the domain string.

Registry-status verification. Confirm through the registrar that the domain is not subject to a registrar lock, a registry hold, an INDRP-ordered lock, or a court-ordered freeze. A locked domain cannot be transferred until the lock is released. The agreement should require the assignor to cause any removable lock to be lifted before closing. Non-removable locks – locks imposed by an INDRP panel or a court – require resolution of the underlying proceeding before transfer can occur.

In a recent transaction (a .in brand domain, spring 2025), due diligence surfaced an undisclosed registrar hold placed after a trademark owner's informal demand letter. The seller had received the letter and taken no action. We restructured the deal to make closing conditional on a written release from the trademark owner, avoiding a post-closing INDRP filing that would have targeted the buyer as the new registrant.

To weigh UDRP against a court action for your case, or to assess whether a .in domain acquisition is safe to proceed, email info@cognomenlaw.com.

How does escrow protect both parties in a .in domain transfer?

Escrow in a domain transfer is the mechanism that decouples payment risk from transfer risk. Without it, the buyer who pays first risks losing money if the transfer fails; the seller who transfers first risks losing the domain if payment is not made. A structured escrow eliminates both risks by conditioning release of funds on verified transfer completion.

For a .in domain, the recommended escrow sequence runs as follows. First, the buyer deposits the agreed consideration with a neutral escrow holder. Second, the assignor provides the authorization code to the escrow holder or directly to the buyer, depending on the parties' agreement. Third, the buyer initiates the registrar-to-registrar transfer. Fourth, the escrow holder confirms transfer completion by reference to the WHOIS/RDDS record showing the buyer as the new registrant of record. Fifth, the escrow holder releases funds to the seller. If the transfer fails within the agreed longstop period, funds are returned to the buyer and the authorization code is treated as expired.

The assignment agreement must specify the escrow provider, the escrow fee allocation (customarily split equally, though negotiable), the precise release condition, and the dispute mechanism if the parties disagree about whether the release condition has been met. Vague escrow provisions – "funds released when transfer completes" without defining what "completes" means – generate post-closing disputes that erode the value of the deal for both sides.

What happens if a third party files an INDRP complaint after the assignment closes?

A post-closing INDRP complaint is filed against the current registrant – the buyer. The buyer's defense rests on its own registration and use, not on the seller's. This is a critical point that buyers who perform no due diligence frequently miss. If the domain was registered in bad faith by the original registrant, and the buyer acquires it without adequate disclosure and representation, the buyer may face an INDRP panel that finds bad faith in the current use even if the buyer's intent was innocent.

The assignment agreement should therefore include an indemnification clause under which the assignor indemnifies the buyer against INDRP complaints arising from acts or omissions that occurred before closing. The clause should have a time limit (commonly one to two years), a cap on indemnified amounts, a requirement that the buyer promptly notify the assignor of any claim, and a right for the assignor to participate in the defense at its own cost. Without this clause, a buyer who wins or loses an INDRP proceeding bears the full legal cost of the defense.

Buyers who receive a post-closing INDRP complaint have 20 days to file a response after the case commences – a deadline set by the INDRP Rules, not by the parties. Missing that deadline results in a default proceeding in which the panel decides on the complainant's record alone. We have defended .in registrants in exactly this posture, and the strength of the defense depends almost entirely on the quality of the documentation assembled at the time of acquisition – the agreement, the due-diligence record, the escrow confirmation, and the intended-use evidence.

In a recent matter (a .in domain, late 2024), a buyer who had not obtained a dispute-history disclosure received an INDRP complaint within four months of closing. The assignor denied knowledge of the prior trademark dispute. Because the assignment agreement contained no disclosure clause and no indemnity, the buyer bore the full cost of a successful defense that required a detailed reconstruction of the domain's registration history from archived sources.

How does a .in assignment differ from a .com UDRP assignment, and when should you choose a different route?

The right route depends on the zone, the goal, and the existing state of the domain's title. If the domain is a .com and a dispute has already arisen, the UDRP at WIPO or the Forum is the standard path – filing fees begin at USD 1,500 at WIPO for a single-member panel, and a standard case resolves in roughly two months. The UDRP's only remedies are transfer or cancellation; there are no damages. The .in INDRP tracks that model closely, but the "registered or used" formulation in the INDRP's bad-faith limb makes post-acquisition exposure higher for .in buyers who inherit a disputed domain.

If the domain is a .com and the parties have agreed to transfer it commercially – no dispute, a willing seller – the assignment agreement for a .com operates under the same general contract principles, but the UDRP's bad-faith standard does not travel with the domain in the same way. A .com buyer who takes the domain from a willing seller in good faith, with proper documentation, does not automatically inherit the prior registrant's bad-faith history for UDRP purposes. The INDRP's lower bar for the bad-faith element makes .in assignments more legally sensitive, not less.

If the domain is a ccTLD in a jurisdiction with no UDRP analog – .de, for example – there is no arbitration route. A dispute must be resolved through the German courts, often with a DENIC DISPUTE entry to block transfer while litigation proceeds. A .in domain sits between those poles: it has an arbitration route (the INDRP), and it has court access under Indian law, but the governing registrar agreement and the INDRP Rules make the written assignment agreement the primary instrument of risk allocation before a dispute arises. Waiting until a dispute has materialized to address title is the most common and most avoidable mistake we encounter in .in domain transactions.

What if the buyer wants the .com and the .in for the same brand? Both should be addressed in a single transaction or in coordinated transactions, with separate assignment agreements for each zone and a consolidated due-diligence process that covers dispute history in both zones simultaneously. A single WIPO complaint that targeted the .com would not bind an INDRP panel on the .in – the proceedings are independent – but evidence of bad faith in one can be placed before a panel in the other. Portfolio buyers should structure their due diligence accordingly.

What is the realistic cost and timeline for drafting a .in domain assignment agreement?

The cost of a .in domain assignment agreement depends on three variables: the complexity of the due-diligence scope, the presence of prior disputes or encumbrances, and the time required to negotiate the representations and indemnity provisions with the counterparty's counsel. A clean transaction – willing seller, no prior disputes, no third-level zone eligibility issues – can be documented and closed in one to two weeks. A transaction where due diligence surfaces a registrar hold, an undisclosed INDRP filing, or a conflicting trademark will take longer, because those issues must be resolved or disclosed before closing is advisable.

COGNOMEN publishes its approach to domain transaction pricing transparently. Legal fees for a .in assignment in the straightforward range are typically within the range commonly charged for a single UDRP complaint (market rates are in the USD 3,000–7,000 range for flat-fee matters, separate from any escrow or registry fees), though the precise scope depends on what due diligence reveals. Transactions that require registrar negotiations, lock-release proceedings, or parallel INDRP defense work fall outside a flat-fee structure and are scoped on instruction. We will tell you at the outset what the scope covers and where additional work would be charged separately.

The timeline to registry confirmation – from executed agreement to WHOIS/RDDS showing the buyer as registrant of record – depends on the registrar's processing speed and any queue delays at NIXI. In our experience, a straightforward .in transfer completes at the registry level within a few business days of the authorization code being provided and the transfer being initiated. The legal work of drafting and executing the agreement is typically the longer phase.

Related at COGNOMEN

• Domain transactions, due diligence, and portfolio brand-protection monitoring across zones
• How to recover a lapsed domain under the .au framework
• Registrar lock escalation for .cn domain disputes and transfers