Step-by-step: verify chain of title for a .us domain

Step-by-step: verify chain of title for a .us domain. UDRP and ccTLD domain recovery and defense across .us. Email the firm to assess your case.

A buyer wires funds, the registrar completes the push, and thirty days later a cease-and-desist arrives — the domain changed hands three times in five years, one of those transfers was a theft recovery, and the current chain is legally murky. That is the transaction a proper chain-of-title review is designed to prevent.

To verify chain of title for a .us domain, a buyer must trace every registrant of record, confirm each transfer was authorized, identify any prior usDRP dispute or registrar-level dispute entry, and clear the nexus eligibility of both seller and buyer under the .us registry rules. The process typically takes one to three weeks depending on the depth of WHOIS history available and the complexity of any transfer gap. Skipping any step risks acquiring a domain that is already the subject of a pending claim — or that cannot lawfully be registered in your name at all.

This guide walks each step in order, names the trap hidden inside it, and explains how the usDRP dispute procedure intersects with a clean purchase.

Why chain of title matters more for .us than for .com

The .us ccTLD carries a baseline eligibility requirement that generic domains do not: every registrant must have a bona fide nexus to the United States — citizenship, permanent residence, a US-organized entity, or a presence with a bona fide office in a US state or territory. That requirement does not disappear on transfer. A buyer who lacks nexus cannot validly hold a .us domain, and the registry may revoke a registration that fails the test. Before any other due-diligence step, confirm that you qualify.

Equally important: .us operates under the usDRP (the usTLD Dispute Resolution Policy), which closely tracks the three-element UDRP framework — confusing similarity, absence of legitimate interest, and bad-faith registration or use — but is administered under its own registry rules. A domain with a usDRP history is not automatically untransferable, but it signals contested title that any buyer should examine before committing funds.

We regularly advise buyers who discover a prior usDRP proceeding only after the transfer completes. That discovery almost always costs more to resolve than a pre-acquisition review would have.

Step 1: Pull the full WHOIS and RDDS history — and spot the gap

The first step is to collect every registrant-of-record entry for the domain. Current WHOIS output under ICANN's Registration Data Access Protocol (RDAP) gives you the present registrant; what you need is the longitudinal record — who held the domain at every point in its life.

Start with archive services that cache historical WHOIS snapshots. Compare each name, organization, and contact against the chain you are being told by the seller. Any gap longer than a few days between a documented outgoing registrant and the next documented incoming registrant is a flag. Legitimate transfers at arm's length leave traces: registrar confirmation emails, account-change timestamps, and escrow release records. A gap with no paper trail may indicate a theft recovery, an unauthorized push, or a domain that cycled through a drop-catch service.

The trap in this step: sellers routinely describe a gap as "a routine registrar migration." Migrations leave records at the losing registrar. Request those records in writing before you treat any explanation as satisfactory.

Step 2: Search the usDRP dispute record and any registrar-level dispute entries

Once you have the chain of registrants, cross-reference each against the public usDRP decision database. The procedure is administered by the National Arbitration Forum under the usTLD Dispute Resolution Policy. Decisions are published and searchable by domain name.

What you are looking for: any complaint filed against the domain, the outcome (transfer, cancellation, denial), and — critically — whether the current seller was the complainant, the respondent, or an acquiring party after a transfer order. A domain transferred by usDRP order is not tainted in itself; the incoming registrant may be perfectly clean. But a domain that was the subject of a recent proceeding may still be within the period where a losing respondent could pursue a court challenge. That risk window is narrow under US law, but it is real.

Also check for any registrar-level dispute entry or "registrar lock" placed by a third party, which would block transfer regardless of the seller's intention. A locked domain cannot move; the buyer's funds should not move either until the lock is cleared and its origin explained.

For an assessment of your domain dispute, contact info@cognomenlaw.com.

Step 3: Verify the nexus eligibility of every link in the chain — and the buyer

The .us nexus requirement applies to every registrant, not just the current one. A prior registrant who lacked qualifying US nexus held the domain in breach of registry rules. That breach does not void the subsequent transfers automatically, but it does create a compliance gap that the registry can invoke — and that a future claimant could raise in a usDRP proceeding to argue defective title.

For each entity that appears in your chain-of-title reconstruction, verify: (a) the entity type — natural person, corporation, LLC, or partnership — and (b) the US nexus basis for that entity at the time it held the domain. Publicly available state incorporation records, US entity registrations, and, for individuals, documented US presence are the evidentiary sources. You cannot verify a foreign shell company's nexus on its face alone.

Apply the same check to yourself as buyer. If your qualifying nexus is a US subsidiary, ensure that entity is the named registrant — not a parent company organized abroad. The registry's Nexus Requirements are explicit on this point. Confirm current requirements with the registry or counsel, as administrative rules can be updated.

Step 4: Obtain and review every assignment agreement in the chain

A registrar push transfers technical control. An assignment agreement transfers legal title. The two do not always happen together, and the gap between them is where disputes are born.

Request copies of any domain purchase agreement, asset purchase agreement containing the domain, or assignment agreement executed at each transfer point in the chain. Review them for: (a) whether the transferor had authority to assign at the moment of assignment; (b) whether any license, encumbrance, or security interest was noted; (c) whether any warranty of title was given. A seller who cannot produce even a basic bill of sale for a prior transfer is a seller who cannot substantiate clean title.

In a recent matter — a .us domain acquisition, spring 2025 — we identified an unrecorded security interest in a prior asset purchase agreement that had nominally included the domain as part of a broader digital asset sale. The secured party had not released its interest. The buyer's proposed wire transfer was held pending a formal release, ultimately avoiding what would have been a disputed purchase.

The trap in this step: sellers frequently argue that registrar confirmation emails constitute a full assignment. They do not. They confirm an administrative change of registrant, not a contractual transfer of rights.

Step 5: Structure the escrow to match the verified chain — and hold funds until clean

Once you have verified the chain, the structure of the closing must protect the buyer if any post-closing claim materializes. Standard escrow practice for domain transactions — holding funds with a neutral escrow provider until the registrar confirms the inbound transfer — is a minimum, not a ceiling.

For .us acquisitions with any title ambiguity, consider three additional protections. First, a representations-and-warranties provision in the purchase agreement where the seller warrants clear title, absence of pending disputes, and nexus compliance at the time of sale — with a survival period long enough to cover any usDRP challenge window. Second, a holdback: a portion of the purchase price held in escrow for a defined period after transfer, released only if no claim is filed within the window. Third, a right of indemnification if a usDRP complaint is filed by a third party within that period based on pre-closing conduct.

Escrow release should be conditioned on written confirmation from the registrar that the inbound transfer to the buyer is complete, that no lock or dispute entry exists on the domain, and that the buyer's nexus documentation has been accepted by the registry.

How does usDRP procedure affect a .us acquisition?

The usDRP closely parallels the UDRP but applies only to .us domains. A complainant must prove the same three elements: confusing similarity to a mark, absence of legitimate interest, and bad-faith registration or use. The remedies are transfer or cancellation — no monetary damages. A buyer who acquires a domain that was registered in bad faith by the prior holder does not inherit that bad faith automatically, but the new registration must still be valid and in nexus compliance.

Where a pending usDRP complaint was filed before your closing, the registrar will typically apply a lock preventing transfer. Closing before that lock is confirmed absent is not legally possible under registry mechanics. Do not allow a seller to represent that a pending usDRP proceeding "will be dismissed" — that is the panel's call, not the seller's.

Where no complaint is pending but you have identified a prior dispute, review the decision itself. A transfer order in a prior case means the domain moved from a bad-faith registrant to the winning complainant. That prior complainant's title is generally clean from that point forward — provided the chain from that complainant to your seller is documented. The risk is not the usDRP transfer itself; it is the undocumented gap afterward.

To weigh UDRP against a court action for your case, email info@cognomenlaw.com.

What evidence decides whether title is clean?

The short answer: documentary continuity. Clean title is demonstrated, not asserted. The evidence that satisfies a buyer — and that would satisfy a panel or court if title were later challenged — consists of four categories.

First, a linked chain of registrant-of-record entries from original registration to the present seller, with no unexplained gap. Second, a corresponding chain of written assignment instruments, each executed by a party with authority to assign. Third, nexus documentation for each registrant in the chain that held the domain while the .us nexus requirement was in force. Fourth, absence of any live dispute entry, registrar lock, or pending usDRP complaint at the time of closing.

What does not substitute for this evidence: the seller's verbal assurance; a registrar confirmation email for a prior push; a domain valuation report; or the domain's age alone. Age establishes that the domain has existed continuously, not that it changed hands lawfully.

In a second recent matter — a .us portfolio acquisition, autumn 2025 — a buyer approached us after receiving a usDRP complaint against one of forty-two domains acquired six months earlier. The complaint alleged that the prior registrant — two links back in the chain — had registered the domain to target a mark the complainant had held for years. We were able to demonstrate that our client was a good-faith purchaser with no knowledge of the original bad faith, and that the registration had changed hands in a documented transaction. The complaint was defeated. Had no records existed, the outcome would have been harder to predict.

Related at COGNOMEN

• Domain transactions, due diligence, and portfolio monitoring services at COGNOMEN
• FAQ: what a domain assignment agreement must contain for an enforceable transfer
• Guide to ccTLD mediation for .au domain disputes in Australia