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

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

A .com changes hands every hour of every day. Some transfers are clean. Others carry hidden problems that surface months later – a prior UDRP complaint that stained the registration history, a lien from an escrow dispute, or a registrant on record who never formally released the name. When the assignment document is inadequate, the buyer may have paid and still not own the domain.

To draft a domain assignment agreement for a .com domain, you need six core elements: a precise identification of the domain, a representation of chain of title, warranties against prior disputes, the escrow and push mechanics, post-closing registrar confirmation, and a governing-law clause that survives a cross-border dispute. The agreement is separate from, and supplements, the ICANN registrar transfer process. Omitting any element creates a gap a counterparty – or a future UDRP panel – can exploit.

This guide walks each step in order, flags the trap hidden in each one, and explains how the .com zone and WIPO's dispute machinery interact with private assignment documents.

Step 1: Identify the domain with precision – and the trap in the name itself

The first clause must name the domain exactly as it appears in the authoritative WHOIS/RDDS record: lowercase, with the ccTLD or gTLD suffix, and with the registrar of record, the registrant organization, and the IANA-assigned registrar IANA-ID all stated. Do not abbreviate. A mismatch between the agreement and the registrar's record – even a single character – can stall or block the transfer push at the registrar level.

The trap here is not a typo. It is assuming the domain in the listing is the domain being sold. We regularly advise buyers who discover, after signing, that the domain listed in the commercial term sheet was a variant of the one the seller actually controlled. Confirm the exact string against the live RDDS record before the agreement is drafted, not after.

Also confirm the registration expiration date. A domain within 30 days of expiry faces deletion risk. The agreement should include a representation that the domain will not expire during the escrow window, and a covenant by the seller to renew if necessary before closing.

Step 2: Run the chain-of-title check before a single clause is written

Chain of title in the domain context means documenting every transfer in the domain's history from original registration to the present seller. This step is not optional. It is the due-diligence predicate for the warranties you will ask the seller to give.

What does a chain-of-title check actually examine? At minimum: the full WHOIS/RDDS history available through a reverse-lookup service, any record of prior UDRP or ccTLD dispute proceedings, and the current lien or security interest status of the domain in the seller's jurisdiction. A domain that was once the subject of a UDRP complaint – even one the respondent won – carries a dispute fingerprint. Future panels are not bound by prior decisions, but they will see the history. A buyer acquiring a name in a similar category may be acquiring an elevated risk of a repeat challenge.

In a recent matter (a .com acquisition, spring 2025), we identified a prior UDRP proceeding in the chain-of-title search that the seller had not disclosed. The domain had been the subject of a complaint that was ultimately denied on the first element. The brand at issue had since been acquired by a larger company. We restructured the purchase price and added a specific indemnity covering any UDRP filed within twenty-four months of closing. That clause ultimately justified itself.

The chain-of-title representation in the agreement should state: (a) the seller is the sole record registrant; (b) no third party holds a lien, pledge, or security interest in the domain; (c) no UDRP, URS, ccTLD dispute, or court proceeding relating to the domain is pending or, to the seller's knowledge, threatened; and (d) the seller has not received any demand letter asserting trademark rights in the domain string.

If the chain-of-title search raises questions your team cannot resolve, we can assess the prior-dispute history and help you structure the right representations. Contact info@cognomenlaw.com for an assessment.

How should the price and escrow mechanics be structured for a .com assignment?

Escrow is not a courtesy in a domain transaction; it is the mechanism that synchronizes payment and delivery. Without it, either the buyer pays and the seller delays the push, or the seller pushes the domain and the buyer delays the wire. Both situations produce disputes. For .com transactions of any material value, a licensed escrow service that handles domain-specific transactions is the appropriate structure.

The assignment agreement must specify: (a) the escrow agent by name and account details; (b) the sequence of steps – buyer funds escrow, seller initiates the registrar push, buyer confirms receipt, funds release; (c) the inspection period, typically five business days, during which the buyer confirms the domain has transferred correctly and no adverse notice has arrived at the registrar; and (d) the dispute resolution mechanism for failed transfers.

The trap in this step is the informal side payment. Sellers sometimes ask for a partial payment outside escrow to "confirm the buyer's commitment." Agree to a deposit only if it is held by the escrow agent, not by the seller. Any amount paid directly to a seller before the domain is in escrow is effectively unsecured. If the deal collapses, recovery depends entirely on the governing-law clause and the seller's willingness to return it.

The agreement should also address what happens if the registrar rejects the transfer. Registrars can place a domain on transfer lock for several reasons: a recent change of registrant, a court order, an active UDRP proceeding, or a registrar-specific hold. If the transfer lock was not disclosed and the escrow window closes without a completed push, the buyer needs a contractual remedy – typically a right to terminate and recover escrowed funds, plus a specific-performance clause.

See our detailed guidance on domain escrow structure and mechanics for a deeper treatment of the sequence and the registrar-specific variables.

What warranties and representations protect a .com buyer?

The representations section is where a domain assignment agreement either earns its fee or fails. Standard boilerplate from a general commercial template will miss domain-specific risks. The following warranties should appear in every .com assignment.

Title and authority. The seller warrants that it holds the domain free and clear, has authority to assign it, and has not previously assigned, pledged, or licensed it to any third party. Where the seller is a corporate entity, the agreement should require evidence of board authority or the equivalent under the seller's corporate law.

No trademark conflict known to seller. The seller warrants that, to its knowledge, the domain string does not infringe any registered trademark. This is a knowledge-qualified warranty, not an absolute one. For the buyer, a separate trademark clearance search – against the relevant trademark registers – provides a belt-and-suspenders check that the agreement alone cannot substitute for. We have seen buyers skip the clearance search in reliance on a seller warranty, and then receive a UDRP complaint within six months of closing.

No pending or threatened UDRP or court action. This covers WIPO, the Forum, CAC, ADNDRC, and any court with jurisdiction over the domain or the seller. It should expressly include URS proceedings for any new gTLD extension of the same string if the seller controls related domains.

Accurate WHOIS/RDDS data. The seller warrants that the current RDDS record reflects the true registrant and that no privacy or proxy service obscures a different beneficial owner. Where a privacy service is in place, the agreement should require its removal before or concurrently with closing, so the buyer's details can be entered correctly.

No content liability. If the domain is currently resolving to a website, the seller warrants that the content published at the domain does not infringe third-party rights, did not generate regulatory liability, and is not the subject of any takedown notice or enforcement action. A domain that hosted infringing content before the transfer may attract reputational or legal liability that the buyer inadvertently steps into.

How does the ICANN registrar transfer process interact with a private assignment agreement?

The assignment agreement is a private contract between the parties. The ICANN transfer process – the mechanism that actually moves the domain from one registrant to another in the authoritative database – is a separate, mandatory regulatory step that the agreement cannot replace or modify.

Under ICANN's Transfer Policy, a registrar-to-registrar transfer involves an authorization code (also called an EPP or auth code), a registrar push, or both, depending on whether the buyer is migrating to a different registrar. The agreement should specify which method applies and commit the seller to: (a) releasing the domain from any registrar lock within a set number of business days after escrow is funded; (b) providing the auth code to the escrow agent or the buyer; and (c) not making any changes to the registration record – registrant name, contact details, nameservers, or renewal date – between signing and closing.

The trap here is the ICANN 60-day lock. ICANN's Transfer Policy imposes a 60-day lock on a domain following a change of registrant information (the IRTP-B rule). If a seller updates the WHOIS record for any reason after signing – including correcting a typo – the domain may become untransferable for 60 days. The agreement should prohibit the seller from making any registrant-data change without the buyer's written consent after the execution date.

A second trap: the seller's registrar may apply its own transfer-away lock period, typically up to 60 days after the domain's last registrar transfer. Ask the seller to confirm when the domain last moved registrars. If it moved recently, the buyer may need to wait, and the agreement should account for that window.

If a prior filing or response in a related domain dispute produced a bad outcome, a focused second read can find the element that was missed. For help assessing how a prior UDRP interacts with a proposed acquisition, email info@cognomenlaw.com.

What governing law and dispute resolution clauses work for a cross-border .com assignment?

A .com domain has no geographic location, but the parties to an assignment agreement usually do. The governing-law clause should specify a jurisdiction with a clear body of contract law and, where the buyer is a brand owner, one that also has anticybersquatting or equivalent legislation available if the seller's warranties prove false and litigation becomes necessary.

For transactions involving parties in different countries, the clause should specify: (a) the governing law by jurisdiction (not by general principles or "applicable law"); (b) the courts or arbitral body with exclusive jurisdiction over contractual disputes arising from the agreement; and (c) language of the proceeding. A mismatch – for example, English governing law but a dispute-resolution clause pointing to a jurisdiction that does not recognize ICANN authority – creates an enforcement gap.

The right route depends on the parties' locations and the value at stake. Two parties in the same country can usually agree on domestic courts without complexity. Where one party is outside a treaty-enforcement regime, arbitration under a recognized set of rules provides a path to enforcement across borders. Where the agreement is between a brand owner and a domain investor, the brand owner may want to preserve its right to file a UDRP after closing if the seller's warranties prove false – the governing-law clause should not inadvertently waive that option.

Note that the UDRP and the assignment agreement operate on separate tracks. A private agreement between the parties does not prevent a third-party trademark owner from filing a UDRP against the domain after it transfers to the buyer. The buyer's risk of a post-closing UDRP depends on the domain string, not on the private contract. That is precisely why the chain-of-title check and the trademark clearance search are not optional steps.

What should the post-closing process include?

Closing is not complete when the wire clears and the domain appears in the buyer's registrar account. Three post-closing steps determine whether the transfer will hold and whether the buyer's position is defensible if challenged.

Confirm the RDDS record. Within 24 hours of the transfer, check the live RDDS record to confirm that the registrant name, organization, email, and nameservers reflect the buyer's correct details. Any discrepancy should be corrected immediately through the registrar's change-of-registrant process, with documentation preserved.

Enable registrar lock. Place the domain on registrar lock (also called "client transfer prohibited" status) immediately after transfer. This prevents an unauthorized outbound transfer while the buyer establishes control.

Preserve the closing record. Retain the signed agreement, the escrow confirmation, the auth-code exchange, and the before-and-after RDDS screenshots as a contemporaneous record. If a UDRP is filed after the acquisition, the panel will consider the date of registration and the circumstances of the transfer. A complete closing record supports the buyer's position that the acquisition was conducted at arm's length and in good faith.

In a recent matter (a .com portfolio acquisition involving several dozen names, autumn 2024), a buyer who had documented the full closing record for each domain was able to respond to a post-acquisition UDRP complaint with a clear account of the transfer sequence and good-faith purpose. The complaint was denied. Buyers who treat record-keeping as optional tend to learn otherwise when they are standing in front of a panel.

For an integrated view of the transaction process, including pre-acquisition due diligence and brand-protection monitoring after closing, see our domain transactions and brand protection services page.

How does a tainted domain history affect a buyer's UDRP exposure?

Buyers sometimes ask whether purchasing a domain cleanly – paying market price, using escrow, documenting everything – insulates them from a future UDRP complaint. The short answer: it helps significantly, but it does not provide absolute protection.

Under the UDRP, the bad-faith element must be established both at registration and in current use. When a domain changes hands, the acquisition date resets the "registration" clock for the new registrant. Panels have consistently held that a good-faith purchaser who had no knowledge of a trademark owner's rights and conducted reasonable diligence is in a stronger position than one who acquired the domain with notice of a dispute.

However, panels have also held that certain domain strings carry such obvious trademark resonance – a well-known brand, a distinctive coined word, a name with no plausible generic use – that a buyer's claim of ignorance is difficult to sustain. The pre-acquisition trademark clearance search is the buyer's evidence that the investigation was conducted. Without it, the panel has no basis to credit a good-faith defense.

What does the UDRP safe harbor under Paragraph 4(c) actually require? A buyer claiming legitimate interest must show: a bona fide offering of goods or services under the domain before notice of the dispute, a commonly known name corresponding to the domain, or a legitimate noncommercial or fair use without intent to mislead. A bare acquisition – holding the domain without use – satisfies none of those tests if the domain string is confusingly similar to a mark in active use.

The myth that a private assignment agreement creates a shield against the UDRP is one we address regularly. The UDRP is a creature of ICANN policy, not a party to the agreement. No private contract between seller and buyer alters the Policy or the panel's jurisdiction.

For guidance on documenting a legitimate interest before and after a .com acquisition, see our resource on how to prove legitimate interest in a .com domain.

Related at COGNOMEN

• Domain transactions, due diligence, and brand-protection monitoring across gTLDs and ccTLDs
• Domain escrow structure, mechanics, and registrar push sequencing for .com transfers
• How to prove legitimate interest in a .com domain after acquisition or in a UDRP defense