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

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

A .global domain changes hands through private sale, corporate restructuring, or brand acquisition. The parties sign what looks like a standard asset-transfer document. But the transfer then stalls at the registry, or the buyer discovers a prior UDRP complaint that clouds title, or the escrow structure leaves the seller holding the payment while the registrar lock has not yet lifted. Getting the paperwork right is not a formality. It is the transaction itself.

To draft a domain assignment agreement for a .global domain, the document must transfer registrant of record status through a registrar-compliant push or auth-code mechanism, recite clear representations on chain of title and prior dispute history, and pair with an escrow arrangement that conditions fund release on confirmed registry acceptance of the transfer. The .global zone is operated under ICANN's generic top-level domain rules, meaning UDRP proceedings can be filed against a .global domain at WIPO or the Forum before, during, or after a private transaction. A tainted assignment – one that moves a domain mid-complaint or ignores a prior bad-faith finding – may be unwound by a panel or registrar action.

This page covers the legal elements of a compliant .global domain assignment, the due-diligence steps that protect a buyer, the escrow structure that protects a seller, and what COGNOMEN does to support each stage of the transaction.

What governs a .global domain assignment?

The .global zone is a new generic top-level domain (gTLD) governed by ICANN's standard registrar agreements and the Uniform Domain-Name Dispute-Resolution Policy (UDRP). A private assignment agreement between parties does not override those rules. The registrar of record must be notified of and must process the change of registrant; ICANN's Change of Registrant Policy governs how that happens. Until the registrar confirms the transfer in the registry database, the assignee has no standing as the registrant, regardless of what the private agreement says.

Because .global is a gTLD, any party with trademark rights can file a UDRP complaint against the domain at WIPO, the Forum, CAC, or ADNDRC at any time. A pending or completed assignment does not strip a complainant of that right. Panels have consistently held that a transfer during a pending complaint does not moot the proceeding; the incoming registrant steps into the respondent's position. Drafting the assignment agreement without accounting for this exposure is one of the most common errors in domain transactions.

The assignment agreement itself is a creature of contract law – the applicable national law of the parties, typically as chosen in a governing-law clause. What makes it specialized is the need to mesh private contract terms with the ICANN/registrar mechanics and the UDRP policy layer sitting above both.

For an assessment of your domain transaction, contact info@cognomenlaw.com.

What must a .global domain assignment agreement actually contain?

A compliant assignment agreement for a .global domain must address six structural elements: identification of the asset, representations on title and dispute history, the transfer mechanics, the consideration and payment trigger, warranties and indemnities, and governing law with a dispute-resolution clause.

Asset identification. Name the domain exactly as it appears in the RDDS/WHOIS record: the full domain string, the registrar of record, the current registrant email and account ID if available, and the registration expiry date. A mismatch between the agreement and the registry record creates a gap the registrar will use to delay the transfer. If the transaction includes multiple .global domains or a mixed portfolio, list each in a schedule and cross-reference it from the main body.

Representations on title. The seller must represent that it is the sole legal and beneficial owner of the domain; that the domain is free of any encumbrance, lien, or registrar lock other than the standard 60-day transfer lock that follows a change-of-registrant event; and that no third party has asserted or, to the seller's knowledge, intends to assert any right over the domain. A qualified representation – "to the best of seller's knowledge" – is weaker than an unqualified one. In our practice, buyers should push for an unqualified representation unless the seller discloses a specific uncertainty, which then becomes a scheduled exception.

Prior-dispute history. The agreement must expressly warrant that no UDRP, URS, or any other dispute-resolution proceeding has been initiated or is pending against the domain. It should also warrant that no prior proceeding resulted in a transfer order that was reversed, stayed, or is currently subject to an appeal-equivalent court challenge. A seller who cannot make this representation without qualification is signaling a title defect – one the buyer's due diligence should have already surfaced.

Transfer mechanics clause. Specify whether the transfer proceeds by registrar push (if both accounts are at the same registrar) or by auth-code delivery. Set the deadline for the seller to initiate the change-of-registrant request with the registrar: typically five business days after the escrow agent confirms receipt of cleared funds or upon signature if escrow is waived. Include a cure period if the registrar rejects the initial transfer request for a correctable technical reason.

Warranties and indemnities. The seller warrants that the domain has not been used in a manner that constitutes bad faith under Paragraph 4(b) of the UDRP or that would give a trademark owner grounds for a complaint. This is not a legal opinion – it is a contractual allocation of risk. The indemnity clause should require the seller to defend and hold harmless the buyer from any UDRP or URS proceeding arising from the seller's use of the domain prior to the transfer date. Carve out from seller's indemnity any post-transfer conduct or post-transfer complaint filed in response to the buyer's own use of the domain.

Governing law and dispute resolution. A clause selecting the law of a jurisdiction familiar with domain-asset transactions (US states with well-developed UCC frameworks, England and Wales, or Singapore are common) provides a stable foundation. Pair it with an arbitration or mediation clause that keeps contract disputes out of court unless the sum in dispute warrants litigation cost. Do not route contract disputes through the UDRP – the UDRP resolves domain registration/use disputes, not breach-of-contract claims between transaction parties.

How should escrow be structured for a .global domain transfer?

Escrow is not optional for any domain sale above a nominal amount. The transfer risk is asymmetric: the buyer who pays before the transfer is confirmed is exposed to seller insolvency or bad faith; the seller who pushes the domain before payment clears is exposed to buyer default. A properly structured escrow eliminates both exposures.

The mechanics are straightforward. The buyer deposits funds with a neutral escrow agent. The seller initiates the change-of-registrant process with the registrar. The escrow release condition is confirmation – typically a screenshot of the RDDS record showing the buyer as the new registrant of record – that the .global domain now resolves to the buyer's account. Only then does the agent release funds to the seller. If the transfer does not complete within the agreed window, the funds are returned and the parties' obligations are suspended pending cure or termination.

Several points are specific to .global and new gTLD transfers. First, some registrars impose a 60-day lock on outbound transfers following any change-of-registrant event, including a name or email update. If the seller recently updated the registrant contact details, that lock may prevent the transfer for up to 60 days even after the agreement is signed. The agreement should account for this by extending the transfer window and specifying who bears the cost of any resulting delay. Second, the seller should represent in the agreement whether the domain is currently subject to any registrar-imposed lock related to a dispute, fraud flag, or court order.

In a recent transaction (a .global brand domain, spring 2025), we identified a 60-day lock triggered by a contact-email update the seller had made to comply with an ICANN verification request. The escrow agreement was amended before closing to extend the transfer window by 45 days and to add a seller-funded extension fee. The transaction closed without dispute.

What chain-of-title and prior-dispute checks does a buyer need before signing?

Chain-of-title due diligence on a domain is the buyer's primary protection against acquiring a domain with a defect that cannot be cured after closing. For a .global domain, the diligence has four components.

RDDS/WHOIS history. Query the current RDDS record and, where available, historical WHOIS data. Confirm that the seller shown in the agreement matches the current registrant of record. Gaps – periods where the domain shows a different registrant, or where historical data was masked without a clear explanation – warrant follow-up. A domain that changed hands multiple times in a short period may have been used in a pattern of bad-faith registrations, a Paragraph 4(b) factor that survives the transfer.

UDRP and URS search. Search the public WIPO, Forum, CAC, and ADNDRC case databases for the exact domain string. This is free and takes minutes. A prior complaint that resulted in a transfer order means the current registrant acquired the domain either before or after the panel's decision; either scenario requires explanation. A prior complaint that was denied is not disqualifying, but the panel's reasoning should be read to confirm the denial was on the merits and not on a procedural default that could be re-litigated.

Trademark landscape. Run a basic trademark clearinghouse and USPTO/EUIPO search for the domain string or its dominant element. A domain that matches a registered mark – particularly a well-known mark – carries ongoing UDRP exposure regardless of who holds it. The buyer's intended use matters: a buyer who intends to use the domain in commerce related to a third party's mark takes on a complaint risk that the prior registrant may not have faced.

Registration date and history. When was the domain first registered? Has it expired and been re-registered? A re-registration resets the registration date in the UDRP analysis. Panels treat re-registration as a new registration for purposes of the bad-faith element. If the domain was registered after the trademark owner's mark became well known in the relevant market, that temporal relationship is evidence of bad faith even if the domain itself has been transferred multiple times since.

To weigh UDRP against a court action for your domain transaction, email info@cognomenlaw.com.

How does the UDRP intersect with a completed .global assignment?

A completed assignment does not immunize the domain from a UDRP complaint. A trademark owner with rights in the string can file a complaint against the new registrant at any time during the registration period. The three UDRP elements – confusing similarity, no legitimate interest, and bad faith – are assessed as of the date of the complaint and the date of registration by the current registrant, not by a predecessor.

This creates a specific acquisition risk. A buyer who purchases a .global domain from a registrant who used it in bad faith does not inherit that bad faith for the purposes of Element 3 – the complaint must show the buyer's registration or use was in bad faith. However, if the buyer acquires the domain knowing it is subject to a pending complaint, or knowing it has a prior bad-faith finding that the prior registrant evaded by transferring, panels have treated that knowledge as evidence of the buyer's own bad faith. Willful blindness – not checking WIPO's public database – does not protect a buyer in that analysis.

Conversely, a buyer who acquires a .global domain through a properly documented transaction, for a legitimate commercial purpose, with full due diligence, is in a strong position to defend a UDRP complaint. The Paragraph 4(c) safe harbors – a bona fide offering of goods or services before notice of the dispute, or a legitimate noncommercial or fair use – can be established through the assignment agreement itself, the escrow record, and post-transfer use evidence. The agreement should be drafted with this possibility in mind: include a recital stating the commercial purpose of the acquisition and confirming that no notice of a dispute was received prior to signing.

In a recent matter (a .global domain, late 2024), we acted for a buyer who had completed a private assignment without legal review. A UDRP complaint was filed six weeks after closing. The complainant argued that the transfer itself was evidence of a pattern of abusive registrations. We demonstrated, through the escrow record, the assignment agreement's warranty provisions, and the buyer's pre-transfer trademark clearance search, that the acquisition was bona fide. The complaint was denied. We regularly advise registrants in this position and the outcome depends on the documentary record the buyer built at the time of the transaction – not on explanations constructed after the fact.

What is the realistic route and timeline for completing a .global assignment?

The right structure depends on the parties' risk tolerances and the complexity of the domain's history. Here is how the main scenarios play out.

A straightforward .global assignment – single domain, clean title, no prior disputes, both parties at the same registrar – can close in under two weeks. The agreement is drafted and negotiated (two to four days for a standard form), the registrar push is initiated on signing, and the escrow agent releases funds on RDDS confirmation. Legal fees for a transaction of this complexity are typically in the lower range of domain transaction work, and the forum filing fee question does not arise because no dispute is pending.

A more complex assignment – multiple domains, a prior UDRP search returning results that require analysis, a registrar change required alongside the transfer, or a seller in a different jurisdiction – adds time and cost at each step. Allow three to five weeks from term-sheet to confirmed transfer. The due-diligence phase alone may take one to two weeks if historical WHOIS data is sparse and trademark searches span multiple registries. Where the seller is outside the buyer's jurisdiction, the governing-law clause and any notarization or apostille requirements for the agreement add a further variable.

If a UDRP or URS complaint is filed against the .global domain after signing but before the transfer is confirmed, the situation becomes a dispute matter as well as a transaction matter. ICANN's rules generally lock the domain during a pending UDRP proceeding. The assignment agreement should address this scenario explicitly: state which party bears the cost of the defense, whether the buyer has the right to terminate the agreement if the complaint is not resolved within a specified period, and how any transfer order or denial affects the parties' obligations.

Where the domain dispute cannot be resolved through the UDRP – because the buyer wants monetary damages or the registrant is identifiable and subject to jurisdiction – US anticybersquatting litigation or equivalent proceedings in another jurisdiction may be necessary, handled with local litigation counsel in the relevant jurisdiction.

What is the cross-zone dimension for a .global domain portfolio?

A brand that holds a .global domain often also holds, or wants to acquire, the same string in other zones: .com, .net, country-code domains such as .uk, .de, or .eu, and other new gTLDs. Each zone has its own transfer mechanics and dispute-resolution layer. The assignment agreement should account for the full portfolio, not just the .global component.

For the .com component: the UDRP applies in identical form. WIPO filing fee starts at USD 1,500 for a single-member panel on one to five domains. A combined complaint covering a .com and a .global domain at the same registrant is permitted under the UDRP if both domains are in dispute – the complaint may cover multiple domains provided the registrant is the same holder.

For the .uk component: the Nominet DRS applies, with its own "abusive registration" test and a free mediation stage before any expert decision. The assignment mechanics for .uk domains differ from gTLDs; the Nominet registry operates its own transfer process. A combined portfolio transaction that includes a .uk domain should have separate transfer clauses for the Nominet-administered component.

For a .eu component: the EURid ADR.eu procedure governs disputes; the .eu registry has its own eligibility requirements for registrants (an EU/EEA nexus), which means a buyer without EU/EEA status cannot hold a .eu domain – a basic eligibility check is a prerequisite for any .eu component in a cross-zone assignment.

For .de: there is no UDRP. Disputes go to the German courts, and the DENIC DISPUTE entry can block transfer while litigation proceeds. A seller of a .de domain must confirm no DENIC DISPUTE entry exists before signing.

When a transaction spans two or more of these zones, the assignment agreement should be structured as a master agreement with zone-specific schedules. Each schedule addresses the transfer mechanics, the escrow release condition, and the dispute-resolution provision applicable in that zone. A single undifferentiated agreement for a cross-zone portfolio is an invitation to ambiguity.

We regularly advise on cross-zone portfolio transactions where the domain string sits in multiple registries simultaneously, and the sequencing of transfers across zones – which moves first, how escrow conditions are layered – is often the most consequential structural decision in the deal.

Related at COGNOMEN

• Domain transactions, purchase, sale, and portfolio brand protection services
• Verify domain chain of title and prior dispute history before acquisition
• URS suspension analysis: when the Uniform Rapid Suspension procedure applies