How to verify chain of title for a .in domain

A .in domain changes hands. The price looks fair. The seller looks legitimate. But behind the registration sits a dispute history the buyer never found — and six months later, a transfer order arrives from the .in arbitration panel, pulling the domain out from under the new owner. That scenario is not hypothetical. It happens when buyers skip chain-of-title verification before signing the purchase agreement.

To verify chain of title for a .in domain, a buyer must trace the full registration history through NIXI's WHOIS/RDDS records, check the INDRP dispute archive for prior complaints, confirm the current registrant's authority to transfer, and structure the transaction through escrow before releasing funds. The .in registry operates under the IN Domain Name Dispute Resolution Policy (INDRP), India's ccTLD equivalent of the UDRP. A clean chain of title means no prior dispute, no pending transfer lock, and a registration trail that shows legitimate acquisition at each step.

This page sets out the verification steps, explains the legal risks specific to .in, and describes how COGNOMEN structures due diligence and escrow for .in domain acquisitions.

What governs .in domains — and why it matters for title verification

The INDRP is the applicable dispute-resolution mechanism for all .in domains, administered under rules published by the National Internet Exchange of India (NIXI). It tracks the three-element structure of the UDRP — confusing similarity, no legitimate interest, and bad-faith registration and use — but applies India's trademark law as the rights framework. A buyer acquiring a domain without checking INDRP history is acquiring without knowing whether a prior complaint was filed, decided, or is still live.

Why does that matter for chain of title? A transfer order issued by an INDRP panel survives a subsequent sale. If the original registrant sold the domain to a second buyer while an INDRP complaint was pending, the incoming buyer may hold a registration that a panel can still reach. NIXI's rules do not automatically immunize a bona fide purchaser from a pending proceeding the way a court-ordered stay would. The practical answer is to verify before you pay.

Beyond INDRP, .in has its own registry-level eligibility rules. Not all applicants are eligible for every .in second-level registration; certain sub-zones carry specific eligibility criteria. A chain-of-title check must confirm not just that the domain was registered, but that it was registered by a party who met the applicable eligibility requirement at the time. A registration obtained in violation of eligibility rules is vulnerable to revocation regardless of its INDRP history.

In our practice, eligibility failures are among the most overlooked risks in .in acquisitions. The WHOIS record shows a name and a date. It does not flag whether the original registrant qualified for the sub-zone at registration. That gap requires direct verification with the registrar and, where the chain is long, a review of the original registration documentation.

If you are evaluating a .in domain acquisition and need the chain-of-title verified before closing, contact info@cognomenlaw.com for an assessment of the INDRP risk and the title record.

How to conduct a .in chain-of-title search step by step

A complete chain-of-title search for a .in domain covers five layers: RDDS/WHOIS history, INDRP dispute record, registrar-level lock status, registrant identity and authority, and sub-zone eligibility confirmation. Each layer answers a different question about the domain's legal health.

Step 1 — RDDS/WHOIS snapshot and historical records. Pull the current WHOIS record from NIXI's RDDS and document the registrant name, registrar, registration date, expiry date, and nameserver configuration. Then request historical WHOIS data through a commercial WHOIS history service. The goal is a timeline showing every registrant of record and every registrar change. A domain that has moved across three registrants in four years requires explanation at each step. Gaps — periods where the domain was "dropped" and re-registered — reset the registration date but do not reset any prior complaint history attached to the name.

Step 2 — INDRP dispute archive search. NIXI maintains a record of INDRP decisions. Search that archive against the domain name itself, not just the current registrant's name, because the domain could have been named in a proceeding under a prior holder. Search also for any decisions naming the current registrant in unrelated .in proceedings — a pattern of abusive registrations is a Paragraph 4(b)-equivalent bad-faith indicator under the INDRP and signals broader portfolio risk.

Step 3 — Registrar lock and transfer status. Contact the current registrar (or request the seller to provide written confirmation) that the domain is not subject to a registrar lock, a NIXI-imposed freeze, or any pending INDRP proceeding. A domain under INDRP complaint will typically have a transfer lock imposed by the registrar upon commencement. That lock is visible at the registrar level but not always surfaced in a public WHOIS query.

Step 4 — Registrant identity and authority to transfer. Verify that the entity named as registrant has authority to sell. For a corporate registrant, confirm that the entity is in good standing and that the signatory to the transfer agreement is authorized. For an individual registrant, confirm identity against a government-issued document. A mismatch between the registrant-of-record and the contracting party is a title defect that can render the transfer voidable.

Step 5 — Sub-zone eligibility confirmation. If the domain sits in a restricted sub-zone (such as .gov.in, .edu.in, .ac.in, or .mil.in), confirm that the transferee meets the eligibility criteria before proceeding. NIXI publishes eligibility requirements; compliance at the time of transfer is the buyer's responsibility. An ineligible buyer who completes a transfer may face revocation by the registry, independent of any INDRP proceeding.

We regularly conduct this five-layer search for clients acquiring .in domains in both private treaty and auction contexts. The process typically takes several business days when registrar cooperation is prompt, longer when historical records are fragmented or the seller is slow to provide registrar-level confirmation.

What prior INDRP dispute history reveals — and when it is a deal-breaker

Not every prior INDRP filing disqualifies a domain from sale. What the dispute history reveals, and how it is interpreted, requires legal judgment. Panels have consistently held that a transfer to a new registrant does not extinguish a complainant's rights — if the underlying trademark claim survives, the domain remains vulnerable even after the sale closes. That is the central risk a buyer must quantify.

A prior INDRP complaint that was denied on the merits — where a panel found the registrant had legitimate rights — is generally a positive signal. The decision record forms part of the chain. A buyer stepping into a registrant's position inherits that favourable finding as evidence of clean title, though it does not bind a future panel on entirely different facts.

A prior complaint that was transferred — where the original registrant lost and the domain moved to a complainant — raises a different question. If the domain was subsequently re-registered by the seller, that re-registration after a panel-ordered transfer is highly suspicious. Panels have, in repeated cases, treated re-registration following a transfer order as itself a bad-faith act. A buyer acquiring such a domain may be acquiring something a complainant can reach again under a fresh INDRP filing.

A pending INDRP proceeding is an absolute stop. No reputable escrow structure should release funds while a proceeding is live, because the pending proceeding may result in a transfer order that overrides the contractual sale.

In a recent matter — a .in brand domain, early 2025 — we identified a withdrawn INDRP complaint in a seller's history that the seller had not disclosed. The withdrawal appeared to have been negotiated as part of an earlier sale at a price that implied value from the brand association. We advised the buyer to require the original complainant's written release before closing. Without that step, the buyer would have acquired a domain that the prior complainant could renew as a fresh filing against the new registrant.

If a domain you are reviewing has INDRP history — decided, settled, or withdrawn — email info@cognomenlaw.com before you proceed. We assess whether prior proceedings create residual exposure for the buyer.

How should escrow be structured for a .in domain transaction?

Escrow for a .in domain transaction follows the same structural logic as any ccTLD purchase: funds are held by a neutral agent, released only when the registry confirms the transfer to the buyer, and the domain is returned to the seller if the transfer fails within the agreed window. The wrinkle with .in is that the INDRP transfer lock means a failed or delayed registry confirmation is not always a technical problem — it may signal a proceeding that opened after signing.

A properly drafted .in escrow agreement should address four points specifically. First, the release condition must be the confirmed change of registrant in the NIXI/registrar records, not the seller's representation that the transfer was "initiated." Second, the agreement should include a representation and warranty that no INDRP proceeding is pending or threatened as of the date of signing. Third, the agreement should specify what happens if a transfer lock is imposed between signing and closing — typically a right to terminate and a return of funds, or an extended escrow window with the buyer's election. Fourth, the escrow period should be long enough to allow the full registrar transfer process to complete under .in's rules, which can take several business days.

Where the transaction value is significant, we recommend retaining a neutral third-party escrow service experienced with domain transfers rather than relying on the seller's proposed mechanism. The specific escrow structure — including which service, what the release trigger is, and how the warranty language is drafted — is a matter of transaction counsel, not just technical process.

For a broader analysis of how escrow functions across domain zones and transaction types, see our analysis of domain escrow for online transactions.

What evidence decides a title dispute at INDRP — and how verification protects a buyer

If a title dispute reaches an INDRP panel after a completed sale, the panel will examine the same elements it would in any INDRP proceeding: trademark rights, the registrant's legitimate interest, and bad faith. The buyer-now-registrant is the respondent. Their defense rests on the evidence they can produce of the acquisition process — specifically, whether they conducted reasonable due diligence and paid market value in an arm's-length transaction.

Panels have distinguished between buyers who acquired domains with knowledge (actual or constructive) of a trademark claim and those who acquired in genuine good faith. A buyer who skipped INDRP history checks and paid a below-market price will struggle to demonstrate good faith. A buyer who has a documented chain-of-title search, a properly structured escrow, and a purchase price supported by market comparables is in a materially stronger position.

The evidence that carries weight includes: the chain-of-title documentation assembled before closing; the escrow agreement showing the arm's-length structure; any legal opinion on INDRP exposure obtained prior to the transaction; and correspondence showing no knowledge of a pending trademark claim. These are not documents a buyer creates after a complaint arrives. They are documents assembled during due diligence.

The INDRP safe-harbor equivalent — that the registrant has a legitimate interest because they acquired the domain bona fide, at market value, without knowledge of the dispute — depends entirely on the paper trail existing before the complaint. In our practice, the clients best positioned to defend a post-acquisition INDRP complaint are those who treated verification as a transaction step, not an afterthought.

For context on what panels look for when assessing whether a respondent holds legitimate interests, our page on proving no legitimate interest in a global UDRP context sets out the analytical framework that applies across the UDRP and its ccTLD equivalents, including the INDRP.

What distinguishes a .in title search from a .com due diligence?

The comparison matters because buyers who have conducted .com due diligence often assume the process is identical for .in. It is not. Four differences are worth stating plainly.

First, the applicable procedure is the INDRP, not the UDRP. The INDRP applies Indian trademark law as the rights framework. A mark registered in India carries the relevant weight; a purely US trademark registration does not automatically satisfy the rights element in the same way it would at WIPO. A buyer acquiring a .in to hold alongside a US trademark portfolio should confirm whether the underlying Indian trademark position is sufficient to defend the name if challenged.

Second, the INDRP panel archive is less extensively documented in commercial databases than WIPO's publicly searchable UDRP case library. A .com due diligence can rely heavily on WIPO's case search interface; a .in search requires direct engagement with NIXI's published decision records and, where the record is thin, registrar-level inquiries.

Third, .in sub-zone eligibility adds a layer absent from .com. There is no eligibility filter for a .com second-level registration beyond ICANN's standard accreditation. For .in restricted sub-zones, the buyer must affirmatively qualify.

Fourth, the regulatory context is India's. Domain transfers that involve a cross-border payment — a foreign buyer purchasing from an Indian seller, or vice versa — may engage India's foreign exchange regulations. That is a tax and compliance matter beyond INDRP, but a competent due-diligence review flags it so the buyer can take appropriate advice.

The right route depends on the domain and the buyer's position. A .in domain acquisition by a brand owner with existing Indian trademark rights, buying from an Indian corporate registrant with a clean INDRP record, is a relatively straightforward transaction. A .in domain with multiple prior registrants, a withdrawn INDRP proceeding, and a seller operating outside India is a complex one. The due-diligence scope should match the risk profile. Our domain transactions practice handles both.

Is a .in domain acquisition different when the seller is outside India?

Cross-border .in acquisitions introduce two additional layers: the question of the seller's authority under their home jurisdiction and the logistics of a registrar transfer that may involve an Indian-based registrar unfamiliar to the buyer's counsel.

Authority to transfer is straightforward in theory — the registrant of record authorizes the transfer — but in practice, a foreign-registered company selling a .in domain may have organizational documents in a language or legal system that requires translation and verification. The due-diligence step for registrant identity and authority takes longer when the registrant is a foreign entity.

The registrar logistics matter because .in domains must be managed through a NIXI-accredited registrar. If the buyer's preferred registrar is not NIXI-accredited, the transfer involves an additional registrar change after the ownership change, extending the timeline and adding a potential point of failure. Confirming the registrar path before signing avoids a closing delay.

For matters involving litigation or enforcement steps in Indian courts — where the INDRP has not resolved the dispute and court action is needed — COGNOMEN works with local litigation counsel in the relevant jurisdiction. We coordinate the strategy and the INDRP analysis; the court filing is handled by qualified Indian counsel.

Related at COGNOMEN

• Domain Transactions & Brand Protection — acquisition, due diligence, escrow, and portfolio monitoring
• Domain Escrow for Online Transactions — structuring release conditions and transfer risk
• Proving No Legitimate Interest — UDRP and ccTLD respondent defense framework

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.