How to structure escrow for a .us domain purchase

How to structure escrow for a .us domain purchase. UDRP and ccTLD domain recovery and defense across .us. Email the firm to assess your case.

A .us domain changes hands and the wire clears — but three months later, a usDRP complaint arrives challenging the registration the buyer just paid for. The dispute history was there. Nobody checked. That is the scenario a properly structured escrow for a .us domain purchase is designed to prevent.

Structuring escrow for a .us domain purchase means more than routing funds through a neutral holder. It requires a chain-of-title review, a search of prior usDRP dispute history, confirmation of nexus eligibility under .us registry rules, and a transfer sequence that keeps the domain locked until cleared funds are confirmed. The entire process — from due diligence through registrar transfer and escrow release — typically runs two to four weeks for a straightforward acquisition. A tainted domain can cost more to litigate than it cost to buy.

This page covers the .us-specific legal context, the due diligence checks that matter, how to sequence the escrow and transfer mechanics, and the fact patterns that signal risk before a purchase closes.

What makes .us domain transactions different from .com purchases?

The .us ccTLD sits under a distinct regulatory regime that every buyer should understand before committing funds. Unlike .com, .us is a ccTLD administered under a Nexus Policy: only US citizens, permanent residents, organizations with a primary place of business in the United States, or entities otherwise meeting the stated nexus criteria may register or hold a .us domain. That eligibility requirement runs with the domain — the buyer must independently qualify, and a transfer to an ineligible party is grounds for revocation by the registry regardless of what the sale contract says.

The dispute procedure for .us is the usDRP — the US Dispute Resolution Policy — which mirrors the three-element structure of the UDRP but is specific to the .us zone. A complainant must show that the domain is identical or confusingly similar to a trademark 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. Note the disjunctive: the usDRP uses "or" for bad faith registration and use, a meaningful difference from the UDRP's cumulative standard. A buyer who inherits a domain with a compromised use history carries that history into any future dispute.

In our practice we regularly advise brand owners and domain investors who underestimate the transfer risk in .us. The nexus check is not a formality. A failed eligibility verification after transfer can unwind a deal that has already closed.

How does chain-of-title review protect a .us domain buyer?

Chain-of-title review for a .us domain traces the registration record from creation to the present seller, identifying any ownership gaps, forced transfers, or prior dispute proceedings that could encumber the buyer's title. This is the first line of due diligence, and it is non-negotiable for any transaction above a nominal sum.

The review covers four areas. First, RDDS (formerly WHOIS) history: current registrant data is checked against historical snapshots to identify undisclosed prior holders or suspicious transfer sequences. A domain that changed hands multiple times in a short window, particularly around a trademark registration date, is a warning sign. Second, usDRP complaint history: the registry and providers maintain records of filed proceedings; a domain that was previously the subject of a complaint — even one that settled or was withdrawn — carries a paper trail that a future complainant can use to establish a pattern. Third, trademark proximity: if the domain string is close to a registered mark, particularly a US mark held by a third party with no connection to the current seller, a buyer acquiring it steps into a potential Paragraph 4(b) bad-faith scenario under the usDRP. Fourth, registry compliance: the .us registry can revoke a domain for nexus breach, for violation of the Acceptable Use Policy, or for UDRP/usDRP non-compliance. Any open compliance flag must be resolved before escrow closes.

A domain that survived a prior usDRP complaint does not automatically become safe to buy. The prior panel's reasoning matters: was the complaint denied on the merits, or dismissed on procedural grounds? A procedural dismissal leaves the substantive claim open.

How should escrow be structured for a .us domain purchase?

A properly structured escrow for a .us domain purchase sequences four stages so that neither party bears the full performance risk at any point. Each stage has a defined trigger, a defined hold period, and a defined default consequence. Skipping stages — or compressing them into a single simultaneous exchange — is where transactions fail.

Stage one: due diligence hold. The buyer deposits funds with the escrow agent. The domain is not moved. The seller places the domain under a registrar lock so it cannot be transferred, deleted, or moved to a privacy service during the review period. Due diligence runs concurrently: chain-of-title, usDRP history, trademark proximity, and nexus confirmation for the buyer. If any check fails, the buyer may withdraw and the escrow agent returns the deposit under the agreed cancellation terms. This stage typically runs five to ten business days.

Stage two: transfer initiation. Once due diligence clears, the seller initiates the registrar transfer by generating an authorization code (EPP/auth code) and providing it to the escrow agent or directly to the buyer under escrow instruction. The domain must still be locked at the seller's registrar pending confirmation that the receiving registrar has accepted the transfer request. Funds remain in escrow.

Stage three: transfer completion verification. The transfer window for a .us domain through the registry system follows standard ICANN transfer procedures. The buyer confirms that the domain has appeared in their registrar account, that RDDS data reflects the correct registrant information, and that nexus certification has been submitted to the registry if required. This verification step is separate from the transfer notification email — an email can be spoofed; a live registrar account check cannot.

Stage four: escrow release. Only after the buyer confirms successful transfer in writing does the escrow agent release funds to the seller. The release instruction should be time-bound: if the buyer does not confirm or raise a dispute within an agreed window (commonly two to three business days after transfer confirmation), the escrow agent releases automatically. That backstop prevents a buyer from sitting on the domain while withholding payment.

We have structured .us domain escrows where an undisclosed prior usDRP proceeding surfaced at stage one, allowing the buyer to renegotiate the price before funds moved. Catching it at stage three — after the transfer — would have been a far harder conversation.

To weigh the due diligence requirements for your .us acquisition, email info@cognomenlaw.com. We assess chain-of-title, prior dispute history, and nexus eligibility before escrow opens.

Which escrow agent should handle a .us domain transaction?

The escrow agent in a domain transaction is not merely a funds custodian; it is the party that controls the release trigger. Selecting an escrow agent without domain-specific experience introduces risk at every stage of the sequence described above.

A domain-specialized escrow service understands the distinction between a transfer notification and a completed transfer. It knows to hold funds until the domain appears in the buyer's registrar account, not merely until an auth code is delivered. It also provides a documented audit trail that can be used in any subsequent usDRP or court proceeding to establish the date and consideration of the transfer — evidence that matters if a bad-faith allegation later turns on the transfer price or timing.

For transactions where the parties are in different jurisdictions — a common scenario in .us deals, since the seller may be a non-US person divesting a domain they held under an earlier nexus-eligible structure — the escrow agreement should specify the governing law and dispute forum. A .us domain transaction does not automatically fall under US law simply because the zone is .us; the contract between the parties governs that question. Specify it explicitly.

Where the transaction value is substantial, a three-party escrow agreement — naming the buyer, seller, and escrow agent as parties, with the transfer sequence as an exhibit — is more defensible than an escrow service's standard click-through terms. We draft and review these agreements as part of our transaction support.

What evidence flags a .us domain as too risky to acquire?

Not every .us domain on the market is safe to buy. Several fact patterns, individually or in combination, should trigger either a price adjustment or a withdrawal from the transaction.

The highest-risk pattern is a domain string that incorporates a registered US trademark, particularly one in an active category, held by a seller with no apparent business connection to the mark. Under the usDRP's bad-faith standard — which includes registration or use to attract users by confusion, or registration to prevent a mark owner from reflecting its mark in a domain — this fact pattern is exactly what a complainant will allege. A buyer who acquires the domain takes on the reputational and legal exposure of the prior registration, even if they intend to use the domain legitimately.

A second warning signal is a domain with a very short registration history or one that was recently recovered from a drop or auction. Drop-caught domains sometimes carry Acceptable Use Policy flags or prior complaint records that do not surface in a basic search. A specialized usDRP history search, using the provider databases, is the appropriate check.

A third pattern is a seller who resists placing the domain under a registrar lock during due diligence. A legitimate seller has no reason to object to a temporary lock. Resistance usually means either a competing offer is being solicited or there is a compliance issue the seller does not want the buyer to find before funds are committed.

In a recent matter (a .us brand-adjacent domain, spring 2025), we identified an open usDRP complaint that had been filed against the seller two weeks before the proposed closing date. The buyer's contract contained no dispute-discovery condition. We negotiated a closing postponement, the complaint was resolved, and the transaction ultimately closed — at a materially reduced price reflecting the dispute risk that had now been priced in.

How does the usDRP affect a buyer who acquires a disputed .us domain?

A buyer who completes a .us domain purchase while a usDRP complaint is pending against the seller inherits a serious procedural problem. The usDRP, like the UDRP, generally treats a transfer during a pending proceeding as an attempt to frustrate the dispute — the new registrant may be added to the proceeding or the complaint may be refiled against them directly. Registrar locks imposed during a usDRP proceeding are designed to prevent exactly this transfer.

But what if the complaint is filed after the transfer closes? The usDRP's bad-faith analysis looks at the registration history and the use pattern — not just the current registrant's conduct. A complainant alleging that the domain was registered in bad faith will point to the seller's registration-era conduct. The buyer's defense then depends on whether they can show that they acquired the domain in good faith, without knowledge of the bad-faith history, and that they are making a legitimate use of it going forward. That defense is much stronger when the buyer can produce the due diligence record, the escrow documentation, the transfer sequence, and evidence of their intended legitimate use — all of which should have been created during a properly structured transaction.

We have defended registrants in exactly this situation. The documentation produced during a structured escrow is the first thing we ask for. Its absence is the first thing a complainant notices.

If a usDRP complaint has arrived after a recent .us acquisition, or if you are purchasing a .us domain and want the transaction documented to withstand a future challenge, contact info@cognomenlaw.com.

How does .us escrow structure compare to .com and other ccTLD transactions?

The right approach depends on the zone. A .com acquisition under the UDRP does not carry the nexus eligibility requirement that defines .us — any person or entity worldwide may hold a .com. The UDRP's bad-faith standard requires registration and use in bad faith cumulatively, while the usDRP's disjunctive standard ("or") means that use alone, post-acquisition, can ground a complaint even if the original registration was clean. That makes .us due diligence into use history more important than in a typical .com deal.

A .eu transaction involves different eligibility rules: the buyer must have an EU or EEA nexus (citizenship, residence, or establishment) or a qualifying establishment in the Union. The ADR.eu procedure at the Czech Arbitration Court handles .eu disputes; remedies include transfer or revocation depending on the complainant's eligibility. A .uk transaction falls under the Nominet DRS, which tests "abusive registration" — a standard that reads "registered or used" abusively, similar in that respect to the usDRP's disjunctive approach, but applied under Nominet's own rules and with a free mediation stage before any expert decision. An escrow for a .de domain must account for the fact that there is no arbitral dispute procedure for .de; the DENIC DISPUTE entry blocks transfer while a German court action proceeds, and any acquisition of a contested .de domain faces that litigation risk.

For a buyer acquiring domains across multiple zones — a not uncommon scenario in portfolio transactions — the due diligence and escrow structure must be zone-specific for each domain in the lot. A single-format escrow across .com, .us, .eu, and .uk will miss the eligibility and dispute-history checks specific to each ccTLD.

Where the transaction is a portfolio acquisition involving domains in multiple jurisdictions, we coordinate with local litigation counsel in the relevant jurisdiction for any zone where a court action or registry compliance issue is already active.

Related at COGNOMEN

• Domain transactions, due diligence, and brand-protection monitoring across all zones
• Pre-acquisition due diligence for .it domain purchases and portfolio acquisitions
• Recovering a .uk typosquat domain through the Nominet DRS