How to draft a domain assignment agreement for a .net domain

How to draft a domain assignment agreement for a .net domain. UDRP and ccTLD domain recovery and defense across .net. Email the firm to assess your case.

A .net domain changes hands every day – through purchase, settlement, corporate restructuring, or the resolution of a dispute. In each of those moments, the legal instrument that matters most is the domain assignment agreement. Get it wrong and the transfer can be reversed, the registrar can refuse to execute it, or a buyer can inherit a registration with a disputed history that comes back as a UDRP complaint months later.

To draft a domain assignment agreement for a .net domain, you need an instrument that identifies the domain precisely, confirms the registrar holds no competing lock or dispute hold, establishes a clean chain of title, pairs the document with a Verisign-compliant registrar transfer, and structures consideration through escrow. The .net zone is a gTLD operated under ICANN-accredited registrar rules; the UDRP applies to it in full, meaning any pending or recently concluded dispute affects the transaction's validity and your exposure as acquirer. A well-drafted agreement closes those gaps before money moves.

This page covers what belongs in a .net domain assignment agreement, how chain-of-title and prior-dispute due diligence shapes the drafting, how escrow fits in, what common errors produce failed or voidable transfers, and when to involve counsel before – not after – you sign.

Why a .net domain assignment agreement is different from a standard asset transfer

A .net domain is not real property and not a chattel; it is a contractual right between the registrant and an ICANN-accredited registrar, governed by registration agreements and ICANN's policies. Assigning it requires more than a bill of sale. The assignor holds a registration right, not title in the property-law sense, so the agreement must transfer that registration right while ensuring the registrar recognises the new holder and ICANN's chain of accountability remains intact.

Three features make .net assignments distinctive. First, the zone is subject to the UDRP in full – any third party with trademark rights can challenge the registration within the life of the domain. A buyer who takes over an abusively registered .net does not inherit immunity; the UDRP complainant names the registrant of record at the time of the complaint. Second, ICANN's inter-registrar transfer policy imposes a 60-day lock after a change of registrant, during which most inter-registrar transfers are blocked. Poorly timed assignment agreements trigger this lock and strand the buyer at the wrong registrar. Third, .net is a legacy gTLD operated by Verisign under ICANN oversight; any registry-level restriction or suspension overrides the private agreement. The agreement cannot transfer what the registry has already frozen.

In our practice, the most common drafting error we see is an agreement that treats the domain like a piece of equipment – a simple quitclaim of "all right, title, and interest" with a payment and a signature. That language is legally inert if the domain sits under a registrar lock, a UDRP registrar-hold, or a dispute-triggered transfer prohibition. The agreement needs to address those conditions explicitly, with representations, conditions precedent to closing, and an escrow release mechanism tied to registrar confirmation of transfer completion.

What goes into a well-drafted .net domain assignment agreement?

A sound .net domain assignment agreement contains eight core components. Each one either protects the buyer from inheriting a defect or protects the seller from post-closing liability. Together they produce a document a registrar can implement and a future UDRP panel cannot use against either party.

Domain identification and registrar confirmation. Name the domain exactly as it appears in WHOIS/RDDS – registrant name, domain name, registrar name, and current expiration date. Attach a screenshot of the RDDS record as an exhibit. Discrepancies between the agreement and the registrar's records create ambiguity about what was transferred.

Representations on title and encumbrances. The assignor represents that it is the registrant of record, that it has not pledged the domain as security, that no UDRP complaint is pending or threatened to its knowledge, that no court order restricts transfer, and that it has not received any trademark demand letter relating to the domain within a stated look-back period. These are negotiated representations. A seller who cannot make them is a seller with a title problem.

Representations on dispute history. This goes beyond "no pending complaint." The assignor should represent whether the domain has been subject to any prior UDRP or ccTLD proceeding, any settlement agreement that might restrict future use, any URS suspension that has expired, or any prior registrar-change in the preceding 60 days. If a prior proceeding exists, the parties need to understand whether the panelist found the registration legitimate or simply dismissed the complaint on procedural grounds – the distinction matters for future exposure.

Conditions precedent to closing. Closing should be conditioned on: (a) verification that no UDRP complaint has been filed and no registrar lock is in place; (b) confirmation by the registrar that the domain is unlocked and transfer-eligible; (c) the seller initiating the transfer in the registrar's system and the buyer accepting it. If either condition fails, escrow does not release.

Escrow mechanics. In any .net transaction of meaningful value, consideration moves through a neutral escrow agent. The escrow agreement runs parallel to the assignment agreement. Funds are released only when the buyer's registrar confirms the domain is in the buyer's account. The assignment agreement should cross-reference the escrow agreement by name or exhibit and define what constitutes "transfer confirmed."

Trademark and use representations. If the buyer intends to operate the domain for a particular business, the agreement can record that the buyer's intended use is bona fide and unrelated to any third party's mark – a representation that becomes useful evidence of good-faith registration if a future UDRP complainant argues bad faith at the registration stage. Panels have consistently held that registration intent is relevant to the bad-faith analysis; a documented bona fide intent helps a respondent at the third UDRP element.

Post-closing obligations. The seller agrees to execute any further registrar documentation required to complete the transfer, to cooperate with any registrar escalation if the automated transfer fails, and not to attempt recovery of the domain through a reverse transfer or UDRP complaint after closing. The buyer agrees not to use the domain to infringe the seller's marks (if the seller retains a related brand).

Governing law and dispute resolution. For a .net domain, parties typically choose a commercially neutral governing law. If a dispute arises about the agreement itself – as opposed to the domain registration – it is a contract claim, not a UDRP matter. The UDRP cannot award contract damages or declare a private agreement void. The agreement should specify arbitration or a court jurisdiction for those private disputes.

If you are ready to structure a .net domain assignment and want each of these components drafted correctly from the outset, contact COGNOMEN at info@cognomenlaw.com for an assessment of the transaction.

How does chain-of-title due diligence shape the drafting?

Chain-of-title due diligence for a .net domain means reconstructing every prior registrant, every prior registrar change, and every prior dispute or demand – then deciding whether what you find changes the price, the representations, or the decision to proceed. The results of that investigation feed directly into what the seller can honestly represent and what the buyer needs by way of indemnification.

The starting point is the current RDDS record and WHOIS history. Historical WHOIS data shows prior registrants and approximate change dates. If the domain changed hands multiple times in quick succession, that pattern raises a question: was it traded through legitimate resale channels, or does it track a monetization scheme that attracted a prior trademark complaint? Either answer changes the drafting.

The second check is WIPO's UDRP search tool and the Forum's published decision database. Both are publicly accessible. A search on the domain name reveals prior complaints, prior decisions, and the outcome. A prior complaint that was dismissed on the merits – where the panel found the registration was not abusive – is a useful document for the buyer: it establishes that a panel has already assessed the domain's legitimacy. A prior complaint that was dismissed for lack of standing or on procedural grounds carries no such protection. And a prior transfer order that the current registrant has ignored is a serious title defect.

The third check is trademark clearance. Who holds trademark rights in the string that forms the domain? If a well-known brand owner holds a registration for the mark corresponding to this .net, the buyer should assess whether that brand owner has previously filed UDRP complaints, whether its registration predates the domain's registration, and whether the buyer's intended use would give a future complainant a colorable confusing-similarity argument. This is not a guarantee against a complaint; it is a risk-calibration exercise that informs whether the price reflects the legal exposure.

In a recent matter – a .net domain sale, spring 2025 – we identified a prior UDRP complaint filed against the then-registrant that had been dismissed on procedural grounds rather than on the merits. The buyer, initially unaware of the prior proceeding, adjusted the purchase price and required a broader indemnification clause after we flagged the gap. The assignment agreement was then drafted to include a specific indemnity covering any UDRP complaint arising from conduct predating closing. That adjustment protected the buyer from inheriting a dispute that the seller had not disclosed.

If a prior filing or response produced an uncertain outcome and you are now considering whether to transact on that domain, a focused review can identify whether the record creates exposure for the buyer. Reach us at info@cognomenlaw.com.

How does UDRP exposure affect a .net domain transaction?

The UDRP applies to .net in full, and a transfer of the domain does not reset the clock on any trademark owner's ability to file. A complainant who believes the domain infringes its mark can file a UDRP complaint against whoever is the registrant of record at the time – including a buyer who completed a good-faith purchase last month. The buyer's good faith at the transaction stage is not one of the three UDRP elements; what matters to the panel is whether the domain was registered and is being used in bad faith, assessed at the time of the complaint.

This asymmetry means that a well-drafted assignment agreement cannot, by itself, immunize the buyer. But it creates two important protections. First, the seller's representations about dispute history and trademark knowledge create a contractual indemnification pathway if a complaint arises post-closing based on pre-closing conduct. Second, the buyer's documented bona fide intent – recorded in the agreement and in contemporaneous business planning – supports the legitimate-interest and good-faith arguments that Paragraph 4(c) of the UDRP recognises as safe harbors.

Where does the risk concentrate? It concentrates in domains where the string is a close match to an active trademark, where the prior registrant monetized the domain by pointing it at a pay-per-click landing page, or where the domain has been passively held with no apparent legitimate purpose. Panels have consistently found passive holding in bad faith where the registrant has no plausible explanation for why it holds a mark-matching domain. A buyer stepping into that record should insist on seller representations covering the prior use, seek evidence of what the domain resolved to during the seller's period of ownership, and consider whether the domain's value is worth the litigation risk.

The decision matrix runs like this. If the .net domain has a clean history, no prior UDRP complaint, and a legitimate descriptive or generic character, the transaction proceeds on relatively standard terms with escrow as the main structural protection. If the domain has a prior complaint that was decided on the merits in the registrant's favor, the buyer has additional evidence of legitimacy but should still conduct trademark clearance. If the domain has a prior complaint that was dismissed on procedural grounds or never reached a decision because the complainant withdrew, the buyer should treat that gap as unresolved risk and price accordingly. If the domain has a pending UDRP complaint at the time of the proposed transaction, a registrar lock is almost certainly in place; the registrar will not execute a transfer while the proceeding is open, and attempting to assign the domain in that window is a UDRP-prohibited circumvention attempt that panels take seriously.

What is the right escrow structure for a .net domain assignment?

Escrow in a .net domain transaction protects both sides simultaneously. The buyer deposits funds; the seller initiates the registrar transfer; the escrow agent releases funds only on confirmed receipt by the buyer's registrar. Neither side is exposed to a simultaneous performance risk. Without escrow, one side sends first and trusts the other to perform – an arrangement that breaks down exactly when the stakes are highest.

The escrow agreement should define three trigger events precisely. The first is the deposit trigger: when must funds be deposited, and in what currency. The second is the release trigger: what constitutes confirmed transfer – typically a written confirmation from the buyer's registrar or a verified RDDS record showing the buyer as the new registrant. The third is the return trigger: what causes funds to be returned to the buyer – typically failure of the transfer within a defined period (commonly 30 days), a registrar rejection, or a UDRP lock that prevents the transfer from completing.

The assignment agreement and the escrow agreement must cross-reference each other. An assignment agreement that is silent on escrow, paired with a separate escrow agreement that is silent on what constitutes closing under the assignment, creates an ambiguity about whether closing has occurred. In a contested situation – if the seller disputes whether the transfer was complete – that ambiguity can freeze the funds indefinitely.

In a second recent matter – a .net portfolio transaction involving several related domain names, autumn 2024 – we structured a phased escrow release tied to each domain's individual transfer confirmation rather than a single release event for the entire portfolio. One domain in the set triggered the 60-day ICANN registrant-change lock and could not transfer with the others. The phased structure allowed the buyer to receive the majority of the portfolio on schedule while holding a proportionate portion of the consideration in escrow pending resolution of the locked domain. That structure was only possible because the assignment agreement anticipated the possibility at drafting stage.

What route applies when a .net dispute arises after the transaction?

If a trademark owner files a UDRP complaint after a .net domain has been assigned, the complaint names whoever is the registrant of record at the time of filing. The new owner is the respondent. The response window is 20 days from the date the case commences. Missing that window means the panel decides on the complaint alone, with no evidence of the respondent's position – an outcome that almost invariably results in a transfer order.

The right route for a post-transaction UDRP defense depends on the merits. If the buyer holds a legitimate interest – a bona fide business use, a generic or descriptive domain, or a registration history that predates the complainant's trademark rights – those are the arguments under Paragraph 4(c) of the UDRP that panels recognise as safe harbors. The assignment agreement and the due diligence record assembled before closing become exhibits in that defense: evidence of good-faith acquisition and bona fide intent.

If the complaint appears abusive – filed by a complainant who knows the registrant has a legitimate interest but hopes a default will produce a transfer – the respondent may seek a finding of Reverse Domain Name Hijacking (RDNH). An RDNH finding carries no monetary penalty, but it is a reputational sanction that panels attach to complaints brought in bad faith against legitimate registrants. We handle RDNH defense alongside standard respondent cases.

How does WIPO differ from a national court for a .net dispute? WIPO's UDRP proceeding is faster and cheaper – a standard case closes in roughly two months at a filing fee of USD 1,500 for a single-member panel – but its remedies are limited to transfer or cancellation. No damages. No attorney fee awards. If a brand owner wants money, or if the domain's use constitutes something that goes beyond what a UDRP panel can address (fraud, passing off at scale, trademark infringement in commerce), the dispute belongs in a national court, with local litigation counsel in the relevant jurisdiction. UDRP and court action are not mutually exclusive; a complainant can file a UDRP for speed while reserving court rights, and a respondent can challenge a transfer order through a court injunction in the relevant jurisdiction.

For a .net domain specifically, the UDRP is almost always the first-resort mechanism because .net is a gTLD and there is no national ccTLD procedure that would apply instead. The choice is UDRP for transfer/cancellation, or court for damages and injunctive relief – not a choice between competing arbitration procedures.

What common errors make a .net domain assignment agreement defective?

Most defective .net assignments share one of four failure modes.

The first is executing the agreement while the domain is under a registrar lock that neither party checked. The agreement is signed, consideration moves, and then the buyer discovers the registrar will not execute the transfer because the domain is locked pending a UDRP complaint, a chargeback dispute on a prior sale, or ICANN's 60-day registrant-change restriction. The deal is not void – it is simply unperformable until the lock clears – but the buyer's funds are exposed if escrow was not structured to handle the delay.

The second is using a template assignment agreement that describes the domain as "intellectual property" or "intangible asset" without engaging with the registrar-contract dimension. A domain is assigned at the registrar level; the private agreement alone does not effect the transfer. If the assignment agreement does not condition closing on registrar confirmation, the agreement can be "complete" under contract law while the domain remains in the seller's account.

The third is failing to confirm that the seller is the registrant of record – not merely the administrative or technical contact. ICANN's policies distinguish registrant from administrative contact. Only the registrant can authorize a transfer. An agreement signed by a party who holds the administrative contact credentials but is not the registrant of record cannot lawfully effect the transfer.

The fourth is omitting a dispute-history representation. If the seller knows of a prior UDRP demand letter or complaint that was settled informally – without a panel decision – and does not disclose it, the buyer has no way to assess whether the underlying trademark dispute is truly resolved or merely deferred. A confidential settlement between a prior registrant and a trademark owner may contain use restrictions that run with the domain and bind future holders. Representations about prior demands, settlement agreements, and use restrictions protect the buyer from inheriting obligations it never knew existed.

We regularly advise buyers who discover one of these defects after signing a draft agreement they prepared without counsel. In most cases the defect can be cured by amendment before closing; in a few, it reveals a title problem serious enough to re-price or exit the transaction. Earlier engagement almost always costs less than the repair.

Cross-zone considerations: when a .net transaction touches a ccTLD or a court proceeding

A .net domain transaction does not occur in isolation. Many domains are part of a multi-zone portfolio where the seller holds the .com, the .net, and one or more ccTLDs under the same brand string. Assigning only the .net while the seller retains the .com and the ccTLDs creates a fragmented ownership picture that can generate trademark conflicts later. The buyer of the .net operates a domain that points at its business; the seller retains the .com that a brand owner – or a future UDRP complainant – can use to argue that the seller is the "real" rights holder in the string.

Where a portfolio transfer covers both a .net and a ccTLD, the assignment agreement must address each zone separately. The .net assignment proceeds under ICANN's inter-registrar transfer policy. Each ccTLD has its own transfer rules set by the national registry. A .de, for example, has no UDRP; ownership disputes are litigated in the German courts, and the DENIC dispute entry (which blocks transfer) is a separate step from any private assignment agreement. A .uk assignment proceeds under Nominet's registrant-change procedure, which is distinct from the Nominet DRS used for dispute resolution. The private assignment agreement covers the parties' obligations; each registry's own procedures govern whether and when the record changes.

If a court proceeding in a national jurisdiction has already produced an injunction or judgment affecting the .net domain, the registrar is bound by that order regardless of what the private assignment agreement says. A buyer transacting on a domain subject to a court-ordered hold needs a legal opinion from local litigation counsel in the relevant jurisdiction before signing anything. The assignment agreement is subordinate to the court order; it cannot transfer more than the court permits.

For cross-zone portfolio transactions, we identify the governing national procedure for each ccTLD involved, check eligibility under each registry's rules, and prepare assignment documentation and transfer filings for each zone in parallel with the .net assignment. That coordination prevents the situation where the .net transfers successfully but a ccTLD transfer fails because the buyer does not meet the registry's eligibility requirements or because the registrant-change procedure was skipped.

Related at COGNOMEN

• Domain transactions, escrow, and pre-acquisition due diligence across gTLD and ccTLD zones
• Domain due diligence for pre-acquisition chain-of-title and prior-dispute history checks
• UDRP recovery for passively held cloud and technology domains