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

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

A buyer and seller agree on a price. The seller hands over the registrar credentials. The deal is done – right? In practice, an undocumented .xyz domain transfer leaves the buyer exposed to prior disputes, chain-of-title gaps, and a registration that could be reversed before the ink on the invoice is dry. Knowing how to draft a domain assignment agreement for a .xyz domain protects both sides and gives the transaction a structure that survives scrutiny.

Drafting a domain assignment agreement for a .xyz domain requires six discrete steps: verify chain of title and prior dispute history, define the assigned property precisely, allocate representations and warranties, set escrow and transfer mechanics, handle UDRP-related rights separately, and register the change-of-registrant with the authoritative registry. The .xyz zone is a gTLD managed under ICANN's general contractual framework, meaning the UDRP and its three-element test govern any post-transfer dispute. The filing fee at WIPO for a single-domain complaint starts at USD 1,500 – a cost that falls on whoever ends up defending a complaint after a flawed acquisition.

This guide walks each step in sequence, flags the trap inside it, and explains what a clean .xyz assignment looks like from the perspective of a domain disputes practice that handles these transactions daily.

Why does a .xyz domain need its own assignment agreement?

A .xyz domain sits in the new-gTLD tier introduced under ICANN's expansion program, which means it operates under the standard ICANN Registrar Accreditation Agreement and is fully subject to the UDRP. That matters for assignments. The transfer of a domain under the UDRP is not a clean-slate event: a new registrant who acquires a domain tainted by a prior abusive registration may face a complaint on facts that predate their ownership. Panels have considered whether a post-transfer registration cures bad faith from an earlier holder, and the consensus view is that it does not automatically do so.

A purpose-built assignment agreement addresses this risk directly. It differs from a simple sale-and-purchase memo because it must speak to the UDRP regime, the registrar's transfer policy, the ICANN change-of-registrant (known in the industry as the "registrant transfer") rules, and the documentary chain that a future panel – or a future buyer – will want to inspect. In our practice, we regularly advise acquirers of new-gTLD domains who discover, weeks after a handshake deal, that the domain carries a prior complaint history that was never disclosed.

For a read on whether your proposed .xyz acquisition is free of prior dispute history, reach us at info@cognomenlaw.com.

Step 1: Verify the chain of title before drafting anything

Chain-of-title verification is the foundation of a safe .xyz assignment, and it belongs before a single clause is written. A domain name can change registrant hands multiple times; each transfer is a separate link in the chain, and a defective link – a forced transfer under the UDRP, a dispute-tainted registration, an unauthorized account hijack that was reversed – weakens every link that follows it.

The verification exercise has four components. First, pull the full WHOIS/RDDS history available through the registrar and through historical RDDS archives. Identify every registrant of record, every registrar of record, and every registration date. Second, search the public WIPO case database and the Forum's case search for the domain name. A prior UDRP proceeding that ended in transfer is a significant flag: the domain was found to have been registered and used in bad faith, and that history follows the asset. Third, check whether any URS suspension was ever imposed. URS suspensions under the new-gTLD program are recorded by the relevant registry; a domain whose suspension lapsed without a transfer may have been re-registered by a different party. Fourth, confirm the current registration status directly with the registrar: is the domain locked? Is there a pending registrar-to-registrar transfer? Is there an active UDRP lock or a DISPUTE notation from another procedure?

The trap in this step is assuming that a clean current WHOIS record equals a clean history. It does not. We have advised buyers who completed a purchase only to receive a UDRP complaint within weeks – one filed by a brand owner who had standing against the prior registrant and whose rights pre-dated the transfer.

See our dedicated service on verifying chain of title for domain acquisitions for the specific records search we run at COGNOMEN.

Step 2: Define the assigned property with precision

The subject-matter clause sounds simple. It is not. A domain assignment agreement must identify the domain with enough specificity to survive a registrar dispute, a customs or trade-classification query, and a UDRP panel's examination of what exactly changed hands. That means: the full domain label (including the .xyz extension), the registrar of record at the date of signing, the registrant account identifier where available, and – critically – any associated intellectual property that may travel with the domain.

That last point is where deals quietly go wrong. Does the assignment include the website content hosted at the domain? The social-media handles associated with that brand name? The trademark registration – if any – that gives the buyer UDRP standing to defend the domain in the future? Each of those is a separate asset class. Bundling them without definition creates disputes over what was actually sold.

A separate but related question: is the seller assigning a registered domain or agreeing to register a domain on the buyer's behalf and then assign it? The UDRP element of "registration in bad faith" attaches at the date of registration. A domain registered by a nominee and immediately assigned may carry the nominee's intent – including any bad faith – into the buyer's chain of title. Define which scenario applies and address it expressly.

How does escrow protect a .xyz domain transaction?

Escrow is the mechanical core of a safe domain assignment. It holds the purchase consideration while the registrar transfer completes, so neither side bears the counterparty risk of paying first and receiving nothing. For a .xyz transaction, the standard escrow structure runs in three stages: (1) the buyer funds escrow before the seller initiates the registrar push or change-of-registrant; (2) the seller triggers the transfer with the registrar; (3) escrow releases funds to the seller only upon confirmed registration in the buyer's account.

The trap here is timing. ICANN's change-of-registrant policy introduced a 60-day lock period after certain registrant data changes. That lock prevents a transfer of the domain to a different registrar for 60 days. A buyer who closes escrow before accounting for this lock may find the domain stranded at the original registrar for two months – unusable for its intended business purpose and potentially exposed to a UDRP complaint filed against the seller during that window.

The assignment agreement should state explicitly who bears the cost of the lock period, which party controls the registrar account during the lock, and what happens if a UDRP complaint or URS proceeding is filed while the lock is live. A locked domain subject to an active UDRP complaint cannot be transferred to a new registrar; the registrar lock imposed by the UDRP rules takes precedence. That is a scenario escrow instructions must address in advance.

In a recent matter – a .xyz domain acquisition, spring 2025 – we identified a 60-day lock conflict during due diligence and restructured the escrow release schedule before signing, avoiding a situation where the buyer would have held consideration in escrow for two months longer than anticipated while the seller retained control of the account.

Step 3: Draft the representations, warranties, and indemnities

Representations and warranties in a domain assignment agreement do specific legal work that generic commercial contracts often leave unaddressed. For a .xyz domain, the seller's representations should cover at minimum: no active or threatened UDRP or URS proceeding; no prior UDRP transfer order that the seller has sought to evade through a subsequent transfer; no outstanding registrar dispute; full authority to assign (meaning the seller's account credentials are not subject to a third-party claim); and no trademark that the domain was registered to target, to the seller's knowledge.

Why does the last point matter? Because the UDRP's bad-faith element looks at the registrant's intent at the time of registration. A seller who registered the domain knowing it matched a competitor's mark and then assigns to an innocent buyer has not cured the underlying bad faith – it is already baked into the chain. A warranty that the original registration was not made in bad faith shifts the financial risk of a post-transfer UDRP loss back to the seller through the indemnity.

The indemnity should cover: WIPO or Forum filing fees (starting at USD 1,500 for a single-member WIPO panel), reasonable legal fees for defending a UDRP complaint arising from pre-assignment conduct, and the value of the domain if a transfer order is entered against the buyer as a result of the seller's pre-assignment conduct. Cap the indemnity at the purchase price if both sides insist, but document it explicitly rather than leaving it implied.

To weigh UDRP exposure against transaction structure for your .xyz deal, email info@cognomenlaw.com.

Step 4: Address UDRP-related rights in the assignment

A domain assignment transfers the domain name. It does not automatically transfer the trademark rights – if any – that might give the new owner standing to defend against a future UDRP complaint under Paragraph 4(c) of the Policy. That is a separate, and often overlooked, clause.

The Paragraph 4(c) safe harbors protect a registrant who can show: a bona fide offering of goods or services before notice of the dispute; that the registrant is commonly known by the domain name; or legitimate noncommercial or fair use. For a newly transferred domain, demonstrating "commonly known by the domain name" takes time. The buyer has no history under the name the day after assignment.

What the agreement can do is document the buyer's legitimate business purpose in acquiring the domain and the seller's acknowledgment that no dispute is pending or threatened. That evidence is relevant to the "bona fide offering" safe harbor if a complainant argues the assignment itself was an evasive maneuver. We regularly include a recital in the assignment agreement that describes the buyer's intended use – not as legal proof, but as a contemporaneous record that a panel can weigh alongside later conduct.

If the seller also holds a trademark registration covering the domain name or related goods and services, consider whether a trademark assignment or license should accompany the domain assignment. A UDRP panel assessing whether the buyer has rights in a name it now uses commercially will look for exactly that kind of supporting record.

Step 5: Set the transfer mechanics and post-closing obligations

The mechanical transfer of a .xyz domain involves steps at the registrar level that the contract must specify precisely. These include: who initiates the registrar push or auth-code transfer request; the deadline for doing so after signing; the verification procedure the buyer must complete; and who contacts the registry if the transfer fails at the registrar level.

Post-closing obligations are equally important and frequently omitted. After a registrar transfer completes, the buyer should update the WHOIS/RDDS data to reflect accurate registrant information. Inaccurate WHOIS data is itself a ground for UDRP finding against a registrant in some panels' reasoning; inheriting the seller's WHOIS record and leaving it unchanged for months is a minor but avoidable red flag.

The agreement should also address domain renewal. A .xyz domain that lapses for non-renewal during or immediately after the transfer process reverts to general availability. The seller and buyer each assume the other is handling renewal; neither acts; the domain drops. Build a renewal-responsibility clause with a specific obligation on the buyer from the moment the registrar transfer confirms, and a backup obligation on the seller until that confirmation is received in writing.

In a second recent matter – a new-gTLD portfolio transaction, autumn 2024 – a buyer acquired twelve .xyz and other new-gTLD domains in a single assignment. The seller failed to renew two of them in the week between signing and transfer completion. By the time the buyer noticed, both had entered the redemption period and required a redemption fee to recover. The assignment agreement in that case was silent on renewal responsibility during the transfer window. It is not silent in our standard drafts.

Step 6: Register the assignment and document the chain

A domain assignment agreement is a private contract. The registry and registrar do not automatically know it exists. The legal transfer of the domain in the registry's systems occurs only through the registrar's change-of-registrant process – and that process creates a new registration record, not a continuation of the old one in most registry data models.

Documenting the chain means: retaining the signed assignment agreement; retaining the registrar-generated confirmation of the change of registrant (typically an email or dashboard record); retaining the prior WHOIS history; and retaining any escrow release confirmation. These records collectively constitute the chain-of-title evidence that a UDRP panel or a future buyer will examine. Panels have consistently held that a registrant who cannot explain the registration history of a domain – including how it was acquired – has a weaker position on the rights-or-legitimate-interests element of the UDRP test.

How long should you keep these records? For as long as you hold the domain and for a reasonable period after any sale, because a successor buyer may need them and because a UDRP complainant can theoretically file years after a transfer. There is no statutory limitation period in the UDRP; the Policy does not impose a time bar. Retention for the full registration period plus several years is a sound working rule.

Which forum decides a .xyz dispute after the assignment?

Any post-transfer UDRP complaint against a .xyz domain goes to one of the four accredited UDRP providers: WIPO, the Forum, the Czech Arbitration Court (CAC), or the ADNDRC. The complainant chooses the forum; the respondent does not. WIPO and the Forum together account for roughly 97% of all UDRP proceedings, and WIPO administered a record 6,282 domain-name cases in 2025 – reflecting the scale of the dispute environment a .xyz registrant operates in.

The right route for a post-acquisition dispute depends on the nature of the problem. If a third-party complainant files against the new .xyz registrant alleging bad faith – relying on the prior registrant's conduct – the defense requires demonstrating clean acquisition: good-faith purchase, full consideration, no knowledge of the complainant's mark, and a legitimate intended use. That is exactly the evidence the assignment agreement and chain-of-title records are designed to supply.

If the assignment itself is challenged – for example, if the seller claims the transfer was unauthorized – the dispute is a registrar-level matter first, then potentially a court matter, because the UDRP does not adjudicate contractual disputes between registrants. The forum for that claim is determined by the governing law clause in the assignment agreement. Choose that clause carefully: designate a jurisdiction with a functioning court system and legal rules that treat domain names as assignable property.

For comparison: if the same brand name were registered as a .de domain, neither the UDRP nor the new-gTLD framework would apply. The dispute would proceed in the German courts, with a DENIC DISPUTE entry available to block transfer during litigation. A .eu domain would go to the ADR.eu platform under EURid's rules, with an eligibility requirement for the transferee. And a .uk domain under Nominet's DRS would test whether the registration is an "abusive registration" under a standard that reads "registered or used" abusively – a lower bar than the UDRP's cumulative "registered and used in bad faith." These cross-zone differences matter when a brand owner holds the .xyz and needs to recover a parallel ccTLD, or when the assignment needs to cover multiple zones in one transaction.

See our analysis of URS suspension for new-gTLD domains for the specific dynamics that apply when a quick suspension – rather than a full transfer remedy – is the right tactical choice.

• Domain transactions and brand-protection monitoring at COGNOMEN – the full service menu for acquisitions, sales, escrow, and portfolio oversight.
• Verify chain of title for a domain acquisition – RDDS history, prior dispute searches, registrar status, and transfer-risk assessment.
• URS suspension for new-gTLD domains – when a suspension remedy is faster and cheaper than a full UDRP transfer complaint.