Step-by-step: draft a domain assignment agreement for a .us domain

Step-by-step: draft a domain assignment agreement for a .us domain. UDRP and ccTLD domain recovery and defense across .us. Email the firm to assess your case.

A brand acquires the .us domain that anchors its American web presence. The seller wires the transfer code. But has anyone checked whether that domain carries a prior dispute finding, a nexus-eligibility gap, or a chain-of-title defect that could unwind the deal months later? In the .us zone, those risks are real – and a badly drafted assignment agreement amplifies every one of them.

To draft a domain assignment agreement for a .us domain you must address four layers that do not exist in a generic gTLD transfer: the Nexus Requirement confirming the assignee qualifies to hold a .us name, the usDRP dispute-history check, the escrow structure that holds funds until the registrar confirms the push, and the representations and warranties that allocate post-closing risk. The zone is governed by the .us Registry Agreement and the usDRP, not the UDRP, which means the legal test and remedy structure differ from a .com assignment. Skipping any layer creates liability that no indemnity clause fully covers.

This guide walks every step in sequence, names the trap inside each one, and closes with a decision matrix for parties who also need to address a parallel gTLD or court dimension.

What Governs a .us Domain Assignment – and Why It Differs from a .com Transfer

The .us zone is a ccTLD administered by Neustar (now GoDaddy Registry) under authority delegated by the National Telecommunications and Information Administration (NTIA). That matters immediately for drafters: a .us domain may only be held by a person or entity with a qualifying US nexus – a US citizen, a US permanent resident, a US-incorporated entity, or an entity with a bona fide presence in the United States. This is the Nexus Requirement, and it applies at every moment of ownership, including the moment of assignment. If the assignee fails nexus, the registrar will reject the transfer regardless of what the agreement says.

The dispute mechanism for .us is the usDRP, a close relative of the UDRP that applies the same three-element test: confusing similarity to a mark, absence of legitimate interest, and bad-faith registration and use. The governing rules track UDRP language closely but operate through an NTIA-approved provider. What does that mean for a buyer? A domain that lost a usDRP proceeding – or narrowly survived one – carries reputational and legal baggage. Panels have consistently held that prior proceedings are admissible context in a later dispute. You want to know about them before closing.

Unlike the UDRP, the usDRP sits against the backdrop of US anticybersquatting litigation, which can reach monetary damages. A buyer who unknowingly acquires a domain with an active dispute or a bad-faith registration history may inherit exposure. The assignment agreement must address that directly.

Step 1: Confirm Nexus Eligibility Before Drafting a Single Clause

Nexus eligibility is a threshold condition, not a closing condition. If the assignee does not qualify on day one, nothing else in the agreement matters. Establish this fact in writing before you open a drafting session.

The Nexus Requirement recognizes three broad categories. First, individuals: US citizens and permanent residents qualify regardless of physical location. Second, organizations: a US-incorporated or -organized entity qualifies. Third, foreign entities with a bona fide US presence: those maintaining a physical office, a registered US agent, or a real operational US presence. A pure foreign holding company with no US footprint does not qualify and cannot receive a .us assignment.

The trap at this step is a corporate restructuring that changes the assignee's status between signing and the registrar push. We regularly advise buyers who have planned an acquisition through a holding-company structure that was solvent-but-foreign at closing. Build a nexus representation that survives organizational change: require the assignee to represent not only current eligibility but to covenant that it will maintain eligibility throughout the period it holds the domain, and that any transfer to a subsequent entity will similarly be conditioned on that entity's nexus.

Document nexus with a certified copy of the formation document, a copy of the EIN confirmation letter (for US entities), or a statutory declaration for individuals. Attach that document as an exhibit to the agreement. Registrars may request it on transfer or audit.

Step 2: Run a Chain-of-Title and Dispute-History Search

A domain's history predates its current registrant. Chain-of-title for a .us domain means tracing every ownership change, noting the registration date, and checking each prior holder against the NTIA-administered WHOIS/RDDS record as well as any historical RDDS archives. The operative question: did the domain ever change hands in circumstances that could constitute a bad-faith registration for usDRP purposes?

Dispute history is distinct from chain-of-title but equally critical. Search the published usDRP decision database for the domain name itself, for each prior registrant's handle, and for any substantively similar domain that shares the same mark. If a prior proceeding was filed and settled before a decision, that settlement will not appear in published decisions – ask the seller directly in a representations-and-warranties schedule, and obtain a clean certificate if the domain is commercially significant. Panels have consistently held that a prior dispute, even one resolved in the registrant's favor, is relevant context when evaluating a later claim of bad-faith registration.

In a recent matter involving a .us brand domain (spring 2025), we identified a withdrawn usDRP complaint against the domain's previous holder during due diligence. The complaint had been withdrawn before any decision – and was invisible in public databases. The seller's representations-and-warranties schedule surfaced it. That single discovery shifted the indemnity structure of the deal and reduced the purchase price. Buyers who skip this search carry the risk themselves.

The trap: RDDS data for .us is subject to privacy-proxy services. If a privacy proxy is in place, the disclosed registrant in RDDS is the proxy, not the beneficial holder. Require full registrant identity disclosure – including the name, address, and email of the underlying beneficial owner – as a condition precedent to signing. Without it, you cannot run a meaningful dispute-history search, and you cannot identify whom the nexus representations bind.

Step 3: Structure the Core Assignment Agreement – Clause by Clause

A domain assignment agreement for a .us domain requires at minimum seven operative provisions. Each one hides at least one structural trap for the unwary drafter.

Identification of the domain and registrar. Identify the domain by its full ASCII and, if applicable, internationalized form. Name the current registrar of record. Include the IANA registrar ID. If the domain is at a privacy proxy, name the underlying registrar. Trap: the registrar may change between execution and the transfer push. Add a covenant requiring 14 days' prior notice of any registrar change, and make unauthorized migration a material breach.

Consideration and payment mechanics. State the purchase price in USD. Specify whether VAT or any US sales or use tax applies (it generally does not for domain transfers between businesses, but confirm this with tax counsel). Trap: wire fraud targeting domain transactions is not rare. Never release consideration based on a transfer-code delivery alone. Require an escrow arrangement, described in Step 4.

Representations and warranties of the assignor. The assignor must warrant: (a) it is the sole registered holder and beneficial owner; (b) the domain is free of any pledge, lien, or security interest; (c) no usDRP, court proceeding, or ICANN complaint is pending or, to its knowledge, threatened; (d) the domain was registered and has been used consistently with the Nexus Requirement and the .us Registry Agreement; (e) no bad-faith registration or use occurred during the assignor's period of ownership; and (f) full disclosure of any prior dispute, claim, or demand related to the domain, whether or not it resulted in a proceeding. Trap: "to its knowledge" qualifiers on items (c) and (f) are negotiated away by sophisticated buyers for commercially significant domains. Push for absolute warranties where the purchase price justifies it.

Representations and warranties of the assignee. The assignee must warrant nexus eligibility (see Step 1) and capacity to enter the agreement. Trap: if the assignee is a newly formed entity, capacity and nexus both require extra scrutiny – a company incorporated the week before signing should carry a fresh formation certificate dated before the signing date.

Conditions precedent to closing. These should include: nexus documentation delivered and approved by counsel; dispute-history search completed and cleared; registrar lock confirmed as disabled (not merely "requested"); and escrow funded.

Transfer mechanics and timeline. The standard registrar transfer process for .us domains follows ICANN's general transfer policy: the gaining registrar initiates; the losing registrar receives an approval request; the domain moves within approximately five to seven days absent a lock. Specify in the agreement: the deadline by which the assignor will disable the transfer lock and provide the authorization code; the window within which the assignee must initiate the gaining-registrar request; and what constitutes a "failed transfer" triggering escrow return. Trap: some registrars impose a 60-day post-creation lock or a 60-day post-transfer lock. If the domain was recently transferred to the assignor, it may be locked for a further period. Identify this before signing and adjust the closing timeline accordingly.

Post-closing obligations. The assignor should agree to cooperate with any registrar verification, to provide NTIA or the registry with information if audited, and to execute any additional instruments needed to confirm the transfer. Trap: without a cooperation covenant, a seller who has received payment has diminishing incentive to respond to a follow-up RDDS audit.

For an assessment of your domain transaction – including chain-of-title due diligence and full agreement drafting for .us assignments – contact info@cognomenlaw.com.

Step 4: Set Up the Escrow Structure

Domain transaction escrow functions as follows: the buyer deposits the purchase price with a neutral escrow agent before the transfer is initiated; the escrow agent releases funds to the seller only after confirmed receipt of the domain by the buyer's gaining registrar. This sequence protects both parties – the seller is assured of payment; the buyer is assured the funds do not move until the asset has arrived.

For a .us assignment, an escrow arrangement should specify: (a) the triggering event for release (gaining-registrar confirmation that the domain is active in the assignee's account, with RDDS reflecting the updated registrant); (b) the hold period before automatic release (typically 24–72 hours after confirmed transfer, to allow the buyer to verify the domain resolves correctly and carries no registrar flag); (c) the instructions for return of funds in the event the transfer fails, the registrar rejects the transfer due to a nexus defect, or a usDRP complaint is filed between signing and closing; and (d) fees of the escrow agent, which the parties allocate by agreement.

The trap here is thin: many parties use ad hoc "I'll pay you once I see it in my account" arrangements. That is not escrow. It is a handshake that fails whenever a transfer is rejected mid-process. Use a recognized domain escrow service. The agreement should identify the escrow agent by name and attach the escrow instructions as a schedule.

A domain filing or complaint received between signing and closing creates a specific problem. If a usDRP complaint is filed naming the current registrant (the assignor), the registrar will typically lock the domain for the duration of the proceeding. That lock survives a change in beneficial ownership. The agreement should include a MAC (Material Adverse Change) right allowing the buyer to terminate and recover escrow funds if a usDRP filing or registrar hold occurs after signing and remains unresolved at the closing deadline.

Step 5: Address the Cross-Zone Dimension

Many .us acquisitions occur as part of a broader brand-protection project that also involves a .com, a .org, or a matching Nominet .uk domain. Each zone has distinct rules. The decision depends on zone, goal, and timeline.

If the parallel acquisition involves a .com, the assignment agreement structure is broadly similar but without the Nexus Requirement. A .com transfer is governed by ICANN's Inter-Registrar Transfer Policy alone; there is no residency or citizenship condition. The UDRP (not the usDRP) governs disputes. A buyer acquiring both the .us and the .com should run separate chain-of-title and dispute-history checks for each zone and draft separate assignment agreements – cross-referencing them in a closing schedule if the consideration is structured as a portfolio price.

If the portfolio also includes a Nominet .uk domain, a further layer applies. Nominet's terms of service impose their own registrant eligibility rules, and the DRS (Domain Resolution Service) governs disputes rather than the UDRP or the usDRP. The DRS "abusive registration" test reads "registered or used" abusively, a lower complainant burden than the cumulative UDRP standard. A .uk domain with a contested history therefore carries higher carryover risk than a comparable .com, even if the prior proceeding was resolved favorably for the seller. We discuss this in depth at our page on .uk domain assignment agreements.

If the intended acquisition is part of a broader brand-protection monitoring program – watching for new registrations in .us and related zones that could generate future disputes – that function should sit alongside the assignment, not after it. We outline the full transaction and monitoring toolkit at our domain transactions and brand protection services page.

A party who needs to recover or defend a .us domain that is not available for voluntary assignment faces a different path entirely. The usDRP provides a mechanism to compel transfer or cancellation, subject to the three-element test. A party also considering whether a dispute implicates a trademark that is "confusingly similar" under the usDRP's version of the test should review the analysis at our confusingly similar trademark FAQ, which examines how panels approach that element across zones.

In a recent cross-zone matter (summer 2025), a US brand owner was acquiring the .us, .com, and .org variants of its mark from three different sellers. Each had a distinct dispute history. The .us domain had a withdrawn usDRP complaint in its past; the .com was clean; the .org had been the subject of a failed UDRP (the complainant lost on the bad-faith element). We structured three separate agreements with a unified closing schedule, coordinated escrow release timings across two escrow agents, and drafted the .us agreement to include a MAE clause triggered by any registrar lock on any of the three domains. The closing completed without incident.

To weigh UDRP against a court action for your case, or to structure a multi-zone domain acquisition, email info@cognomenlaw.com.

Step 6: Execute, Lodge, and Confirm – and What to Do If the Transfer Fails

Execution of the agreement should occur in counterparts, with each party retaining a signed copy. Electronic signatures are generally valid for domain assignment agreements under US law, but check the applicable state's electronic signature rules if the deal is structured under a specific state's law. Identify the governing law and dispute resolution clause early – and for a .us domain transfer between two US parties, a US governing law and US arbitration clause is typical.

Once executed and escrow is funded, the assignor disables the registrar lock and provides the authorization (auth) code. The assignee submits the gaining-registrar request. At this point, the losing registrar will send a confirmation email to the RDDS-listed email address for the domain. That email carries a time-limited acceptance window – typically five days. If the assignor does not respond or the email reaches a stale address, the transfer times out and must restart. The trap: outdated RDDS contact emails are one of the most common causes of failed transfers. Require the assignor to confirm and update the RDDS contact email before providing the auth code, and include this as a closing condition.

If the registrar rejects the transfer – citing a lock, a pending dispute hold, or a nexus flag – the agreement must specify a cure period (typically 15–30 days), a mechanism for the parties to cooperate in curing the defect, and a termination right with escrow return if cure is impossible. Do not rely on the registrar to advise either party promptly; build the parties' obligations and notice requirements directly into the agreement.

After a confirmed transfer, update the domain's nameservers, verify RDDS reflects the new registrant, and document the completed transaction. Retain the fully executed agreement, the escrow release confirmation, the gaining-registrar confirmation email, and the RDDS screenshot in a persistent file. If a usDRP complaint is filed in the 12 months following acquisition – an adversary claiming the new registrant acquired in bad faith – that documentation file is the foundation of the defense.

What if the domain cannot be acquired voluntarily? If the current holder refuses to sell at any price, the buyer's options depend on whether the registration is itself abusive. A usDRP complaint is available where the three elements are met. A US anticybersquatting court action may be available where damages are also sought. Those paths require different preparation from a transactional assignment – but the chain-of-title and dispute-history research conducted for a prospective purchase translates directly into the evidentiary record for a usDRP complaint.

Related at COGNOMEN

• Domain transactions, due diligence, and brand-protection monitoring across gTLDs and ccTLDs
• Draft a domain assignment agreement for a .uk domain – Nominet DRS considerations
• Confusingly similar trademark FAQ – how panels assess the first UDRP element across zones