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

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

A buyer and seller agree on a price for a .ae domain. The registrant wants payment; the brand owner wants the name. Without a properly structured assignment agreement – one that accounts for the UAE registry's eligibility rules, the underlying chain of title, and a secure transfer mechanism – neither party gets what it actually needs. The agreement is not a formality. It is the document that decides whether the transfer sticks.

To draft a domain assignment agreement for a .ae domain, the parties must address three core requirements: confirmed eligibility of the incoming registrant under the .ae registry rules, a chain-of-title review to ensure no prior aeDRP dispute or encumbrance attaches to the name, and a structured escrow release tied to verified registrar completion of the transfer. The registry governing .ae domains is operated by the Telecommunications and Digital Government Regulatory Authority (TDRA), and eligibility conditions – including local presence or entity requirements – must be satisfied before any transfer will be processed. A signed assignment document alone does not guarantee a valid transfer under the applicable national procedure.

This page covers what the agreement must contain, how to structure escrow for a .ae transfer, and what due-diligence steps protect both sides before funds change hands.

What makes .ae domain transactions legally distinct?

The .ae registry operates under national telecommunications law, with eligibility and transfer rules administered by the TDRA. Unlike a .com, which transfers by standard ICANN-accredited-registrar change-of-registrant mechanism, a .ae domain is a ccTLD with specific requirements on who may hold the registration. An incoming registrant – whether a company or an individual – must meet TDRA's published eligibility criteria before a transfer is approved. If those criteria are not confirmed in advance, the assignment agreement may be fully executed, the funds released, and the transfer still refused at registry level.

That structural fact shapes every clause of a sound .ae assignment agreement. The agreement must treat eligibility confirmation as a condition precedent, not an afterthought. It must allocate the risk of a failed transfer clearly between the parties. And it must define what happens if the registry rejects the transfer request or imposes additional conditions after signing.

We regularly advise on .ae domain transactions where the buyer's first instinct is to treat the process identically to a .com acquisition. The differences are material. Registrar mechanics, transfer windows, and the requirement to use TDRA-authorized registrars all demand specific drafting. A generic domain assignment template will not carry the weight.

How does the aeDRP affect what you must check before signing?

The .ae Dispute Resolution Policy (aeDRP) is the policy under which .ae domain disputes are resolved. A domain with an open or recently decided aeDRP proceeding carries a material defect in its title. Before any assignment agreement is executed, the buyer must verify that no aeDRP complaint is pending and that no prior aeDRP decision imposed conditions – or resulted in a transfer or cancellation order – that affects the current registration's validity.

Why does this matter so acutely in a transaction? Because a domain that was transferred to the current registrant pursuant to a prior aeDRP order may carry a contested registration history that a future panel or registry proceeding could revisit. Equally, a domain that was the subject of a dismissed aeDRP complaint, where the respondent prevailed, is not necessarily clean: if the facts that gave rise to the earlier complaint have changed, a new complainant may have a stronger case. The buyer acquires the asset and the risk that attaches to it.

In our practice, chain-of-title review for a .ae domain includes four steps. First, confirm the current registrant's identity against the WHOIS/RDDS record. Second, search any publicly available aeDRP decision database for the domain string. Third, request from the seller a representation and warranty as to prior disputes, liens, and encumbrances. Fourth, confirm that no TDRA-imposed restriction is in place on the domain at registry level. Any gap in that sequence is a gap in the buyer's protection.

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

What must a .ae domain assignment agreement contain?

A well-drafted .ae domain assignment agreement is a short commercial document with a precise scope. It does not need to be long. It needs to be complete. The following elements are the minimum a practitioner should include when drafting for a .ae transaction.

Identification of the domain and registrant. The agreement should identify the domain name, the registrar of record, the current registrant's identity as it appears in the TDRA registry, and the date on which the registration was last renewed. Identifying the registrant solely by trade name, without confirming the legal entity on record, is a drafting failure that creates enforcement risk.

Eligibility representation. The buyer must represent that it meets TDRA eligibility requirements for holding a .ae domain. Where any doubt exists – for example, where the buyer is a foreign entity without a UAE business presence – the agreement should specify exactly how eligibility will be established before the registry transfer is submitted. Options include nomination of a local sponsoring entity or establishment of a UAE-registered entity prior to transfer. The agreement must not assume eligibility; it must confirm it as a condition.

Conditions precedent to transfer. The transfer obligation should be conditioned on: (a) registry eligibility confirmed; (b) no open aeDRP proceeding; (c) escrow agent's confirmation of cleared funds; and (d) registrar's readiness to process the transfer instruction within a defined window.

Escrow mechanism. Payment should be held by a neutral escrow agent and released only upon the buyer's confirmation of successful transfer at registry level – not upon submission of the transfer request. The difference is critical. Submission and completion are different events in ccTLD procedures. The agreement must specify the trigger for escrow release precisely.

Transfer procedure and timeline. The agreement should specify which party is responsible for initiating the transfer request with the registrar, the maximum number of days within which the request must be submitted after signing, and what constitutes a failure to complete. TDRA transfer procedures have their own processing times; the agreement must build in realistic windows rather than importing .com assumptions.

Representations and warranties from the seller. The seller should warrant that it is the legal registrant of record, that the domain is free from any pledge, lien, or dispute encumbrance, that no aeDRP proceeding is pending or threatened, that the domain has not been subject to a transfer or cancellation order, and that it has the authority to assign the domain without third-party consent.

Post-transfer obligations. The agreement should require the seller to take all reasonably necessary steps to cooperate with the registrar and registry to complete the transfer, including providing any authorization codes or registry-specific documentation. This clause has practical importance in ccTLD transfers, where the registry may require original documents or notarized corporate authorizations.

Governing law and dispute resolution. For a .ae domain, the parties will typically need to address UAE law as the primary governing regime, given the registry's national jurisdiction. Where one or both parties are foreign, the governing law clause requires specific attention. The choice of dispute resolution mechanism – whether UAE arbitration, TDRA procedure, or another route – should be made expressly, not left to default.

How should escrow work in a .ae domain transaction?

Escrow is the mechanism that protects both parties when the transfer cannot be atomic. Payment and transfer do not happen simultaneously in a .ae transaction. The registry requires a transfer request to pass through its own processing window. That gap – between payment and confirmed transfer – is the moment of maximum risk for both buyer and seller.

A properly structured escrow for a .ae domain transaction works as follows. The buyer deposits the agreed purchase price with a neutral escrow agent before the transfer request is submitted to the registrar. The seller submits the transfer request. The registrar and registry process the transfer. Upon the buyer's confirmation – within a defined period, typically no more than five business days after registry transfer confirmation – that the domain now appears in its WHOIS/RDDS record as the registrant, the escrow agent releases the funds to the seller.

What if the transfer fails? The agreement must address this explicitly. If the registry rejects the transfer for eligibility reasons, the standard remedy is return of the deposit to the buyer and a defined cure period for the seller to resolve the eligibility defect and re-submit. If the seller fails to submit the transfer request within the agreed window, the deposit is returned automatically. These are not edge cases. In our experience advising on ccTLD transactions, registry-level rejections and eligibility gaps account for a significant share of disputes that arise after signing.

For buyers acquiring a .ae domain as part of a larger brand-protection strategy – for example, alongside a .com and other ccTLDs – the escrow structure should be unified across all legs where possible, with separate release triggers for each zone, since each ccTLD transfer has its own completion timeline and its own points of failure.

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

What due diligence protects a buyer against acquiring a tainted .ae domain?

Acquiring a domain with a disputed or irregular history exposes the buyer to an aeDRP complaint from a third-party brand owner on day one of ownership. The risk is not theoretical. A registrant who purchased a domain without checking its history can find themselves defending an aeDRP proceeding they did not create – arguing against a bad-faith registration they inherited.

Pre-acquisition due diligence for a .ae domain should cover the following. The domain's WHOIS/RDDS registration date and all publicly available historical registrant data. Any aeDRP decisions or pending proceedings associated with the domain string. Whether the domain resolves to content that could itself give rise to a third-party trademark complaint – pay-per-click advertising featuring a competitor's marks, for example, or unauthorized use of a brand's name and logo. The trademark landscape for the domain string: does any existing registration or common-law mark create a realistic risk that a complainant could satisfy the aeDRP elements post-transfer?

In a recent matter involving a .ae domain and a regional brand (a transaction completed in early 2025), due diligence uncovered a prior aeDRP proceeding that had been decided in the seller's favor. The domain was clean on that basis – but the due-diligence review identified that the domain string was confusingly similar to a recently filed trademark in the region, creating an ongoing risk for the buyer. The transaction proceeded at a renegotiated price, with an indemnity clause allocating the litigation cost risk to the seller for a defined period post-transfer. That outcome was only possible because the due diligence happened before signing, not after.

Could the buyer have skipped due diligence and relied solely on the seller's warranty? In theory, a well-drafted warranty provides contractual recourse if the seller's representations prove false. In practice, a warranty against a seller who is a foreign entity without UAE assets is worth no more than the ability to enforce it. Structural protection – due diligence before signing – is the only reliable defense.

What is the aeDRP, and when does it replace a contractual transfer?

The aeDRP is the .ae registry's domain dispute resolution policy, governing complaints by trademark owners and other rights holders against .ae registrants. It operates on a mechanism broadly analogous to the UDRP but adapted to the .ae zone and TDRA rules. Where a .ae domain is held in bad faith – registered to exploit a trademark, to block a brand owner, or to attract commercial gain through confusion – the aeDRP provides a non-court route to transfer or cancellation.

For a buyer or seller, the relevance of the aeDRP extends beyond disputes. A domain that was previously transferred to its current registrant by an aeDRP panel order is a domain whose registration history includes a contested element. The buyer must understand whether that prior order affects the current registration's standing. More importantly, a domain that was the subject of an aeDRP complaint where the complainant lost on one element – for example, the panel found no bad faith – may still be vulnerable to a new complaint by a different mark owner or on different facts.

The aeDRP is also the forum to which a dissatisfied brand owner will take a newly transferred domain if they believe the transfer was structured to move a name between related parties to defeat a pending complaint. Anti-circumvention concerns are real in .ae, as in any ccTLD dispute system. The assignment agreement should not be used – and must not appear to be used – to launder a tainted registration.

The UDRP applies to .com domains, not .ae. If a brand owner holds a .com and a .ae domain that are both registered in bad faith by the same party, the two disputes proceed under different rules. The .com dispute goes to WIPO, the Forum, or another ICANN-accredited provider under the UDRP, with a standard case running about two months and a WIPO filing fee starting at USD 1,500 for a single-member panel. The .ae dispute goes under the aeDRP. A coordinated strategy – filing both in parallel or sequencing them to maximize evidentiary leverage – requires specific planning.

Which route applies when a .ae transaction fails or becomes a dispute?

The right route depends on the nature of the failure. Three common breakdowns, and the applicable mechanism for each:

If the seller refuses to complete the transfer after escrow is funded, the primary route is a contractual claim under the agreement's dispute resolution clause. If the agreement specifies UAE arbitration, that proceeding governs. If the seller has no assets accessible to enforcement, the practical option may be a complaint to the TDRA registry. In that circumstance, COGNOMEN works with local litigation counsel in the relevant jurisdiction to pursue enforcement.

If a third-party brand owner files an aeDRP complaint against the domain after the buyer takes ownership, the buyer stands in the registrant's position and must defend the aeDRP proceeding. If the domain was purchased in good faith, from a registrant who provided accurate representations, and the due diligence confirmed no prior bad faith use, the buyer's position as a good-faith purchaser is a material element of the defense. Evidence of the transaction – the agreement, the escrow records, the diligence file – becomes the respondent's record in the aeDRP proceeding.

If the dispute involves a .com and a .ae domain held by the same party, and the brand owner wants both, the decision is whether to file the UDRP and the aeDRP concurrently or to sequence them. Filing concurrently requires two parallel filings and two separate legal strategies. Sequencing can allow a favorable UDRP panel decision to reinforce the aeDRP filing. The correct approach is fact-specific and depends on the state of the evidence and the relative strength of the case in each forum.

Can an aeDRP complaint be filed before or instead of a contractual dispute? Yes, where the complainant is a trademark owner and the domain holder is not a party to the assignment. An aeDRP complaint targets the registrant, not a contractual counterparty. These are parallel tracks, not mutually exclusive remedies.

What should the governing-law and enforcement clauses address?

A .ae domain assignment agreement involving cross-border parties – a foreign seller and a UAE buyer, or vice versa – requires specific attention to governing law, enforcement, and currency. The following points are not drafting niceties. They are the clauses most likely to be litigated if the transaction fails.

Governing law. UAE law is the natural governing law for a transaction involving a .ae registry asset. The parties may choose a different governing law by agreement, but that choice must be expressly stated. An agreement silent on governing law will be interpreted under the law of the jurisdiction with the closest connection to the transaction – which, for a .ae domain, is likely UAE law in any event.

Enforcement mechanism. Specifying "UAE courts" as the dispute resolution forum is not sufficient. The parties should specify whether they mean DIFC courts, ADGM courts, onshore UAE courts, or a named arbitral institution. Each has distinct procedural rules and enforceability characteristics. For a cross-border transaction, an LCIA or ICC arbitration clause seated in a recognized jurisdiction may produce a more readily enforceable award than a clause specifying UAE domestic courts alone.

Currency and payment mechanics. The agreement should specify the currency of the purchase price, the payment method, and the account details of the escrow agent with particularity. For transactions involving non-UAE parties, AML compliance requirements may impose documentation obligations that the agreement should address expressly.

Entire agreement and amendment. In our practice, .ae domain transaction disputes most often arise from informal amendments – an email chain or a WhatsApp exchange that purports to modify the core terms. The agreement should state unambiguously that no modification is effective unless signed in writing by both parties. This clause matters in any transaction. It is especially important where cross-border parties rely on messaging platforms rather than formal correspondence.

Is a TDRA-registered notarization or legalization required? That depends on the nationalities of the parties and the nature of any supporting documentation. The parties should confirm current TDRA and registrar requirements before finalizing the agreement. Requirements change, and the agreement should not assume that the requirements at the time of drafting remain constant through the transfer process.

Related at COGNOMEN

• Domain transactions, due diligence, and portfolio brand-protection services at COGNOMEN
• FAQ: how domain escrow works in cross-border ccTLD transactions
• Alert: recovering a stolen or hijacked domain – procedures and options