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

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

A startup acquires a clean-sounding .ai domain from a private seller, closes quickly, and discovers six months later that the name carries a prior UDRP complaint history and a disputed chain of title. The seller is unreachable. The domain is now the brand's primary web address, and the exposure is real. That sequence is avoidable – but only if the assignment agreement does the right work before the transfer, not after.

To draft a domain assignment agreement for a .ai domain you must address five distinct layers: the governing registry rules for Anguilla's .ai zone, a clean chain-of-title review, any prior-dispute history at WIPO or in the courts, an escrow structure that holds funds until the registrar confirms the push, and the representations and warranties that bind the seller to the accuracy of every fact you cannot independently verify. A well-structured agreement takes roughly five to ten business days to negotiate and execute when both parties are responsive. Without it, the buyer absorbs every risk the seller carried.

This guide walks each step, names the trap concealed in it, and explains how .ai's specific registry mechanics interact with the agreement.

What governs .ai domain assignments – and why it differs from .com

The .ai ccTLD is administered by the Government of Anguilla (through its Telecommunications Department), which makes it a country-code zone with its own eligibility and transfer rules rather than an ICANN-accredited gTLD regime. That distinction matters immediately when you draft the agreement. UDRP applies to .ai by virtue of Anguilla having adopted WIPO's dispute-resolution provider for .ai disputes, so a registrant's bad-faith history can still surface as a WIPO case in the dispute record – but the registration and transfer mechanics follow the Anguilla registry's own published procedures, not the standard ICANN transfer policy.

What does that mean in practice? First, the registry's authorization process for a name change (the formal assignment notification) may require direct registry approval in addition to a registrar-level push. Second, the eligibility rules for holding a .ai domain – historically more open than some ccTLDs but subject to periodic policy revision – should be confirmed with counsel before the agreement is executed, because a buyer who does not meet current eligibility cannot complete registration. Third, and most importantly, WIPO administers dispute resolution for .ai using the UDRP, so the three-element test of Paragraph 4(a) – confusing similarity to a mark, no legitimate interest, bad-faith registration and use – applies to any prior dispute against the domain. A prior WIPO panel ruling against the current registrant is a material fact that must be disclosed and warranted in the agreement.

In our practice advising on .ai acquisitions, we regularly encounter buyers who assume a ccTLD assignment works identically to a .com transfer. It does not. The procedural gap between registry approval and registrar push is a common source of delay and, in some cases, a failed transfer that requires re-filing. Build that contingency into the agreement's completion mechanics.

Step 1 – Conduct chain-of-title and prior-dispute due diligence before drafting anything

Due diligence is not a post-agreement formality. It is the foundation on which every representation and warranty in the agreement rests, and it must happen before a single clause is drafted. The trap in this step is speed: a buyer under competitive pressure to close signs a thin agreement, skips the history review, and inherits a compromised domain.

A proper chain-of-title review for a .ai domain covers four elements. First, identify every registrant of record since the domain's initial creation date – the current RDDS (WHOIS) record will show the present holder, but historical WHOIS data requires a specialist lookup. Second, search the WIPO case database for any filed complaint naming the domain, including cases withdrawn before a decision was issued. A withdrawal before panel appointment does not mean the claim was baseless; it may mean the parties settled – and the settlement terms may bind a successor. Third, search for any court action in Anguilla, in the UK (whose Privy Council is the final appellate court for Anguilla), or in any jurisdiction where the prior registrant operated. Fourth, check whether the domain is presently subject to a registrar lock, a WIPO provisional lock, or any transfer restriction arising from an active dispute.

If any of these searches surfaces a prior complaint, the agreement must address it explicitly. Representations that the domain is "free of all claims and encumbrances" are standard boilerplate; they become meaningful only when the seller has provided the documentary basis for making them. Demand the evidence, not just the warranty.

For a pre-acquisition due diligence review of a .ai domain – chain-of-title search, WIPO dispute history, and registry eligibility check – contact info@cognomenlaw.com.

Step 2 – Identify the parties and confirm eligibility before the recitals

Every assignment agreement opens with the parties, and that recital block is where the first legal trap hides. For a .ai domain, the seller must be the registrant of record at the Anguilla registry at the moment of execution. If the registered name-holder is an entity rather than the individual signing, the agreement requires authority documentation – a board resolution or an authorized signatory certificate – before it has any binding force. A discrepancy between the registered holder and the executing party renders the assignment unenforceable at the registry level.

On the buyer side, confirm eligibility under current Anguilla registry rules before the agreement recites the buyer as the incoming registrant. Eligibility requirements for .ai have historically been less restrictive than for some national ccTLDs, but policy has evolved and the registry retains discretion to refuse a registration that does not meet current criteria. If the buyer is a non-Anguilla entity – which is the common case for an AI-sector acquisition – confirm in writing with the registrar that the buyer's corporate form is accepted. That confirmation should be attached as an exhibit to the agreement.

The consideration clause follows the parties. State the purchase price in the agreement's currency of record. If any portion of the consideration is contingent (on traffic metrics, brand valuation, or a development milestone), structure each contingent tranche with a defined measurement date and a dispute-resolution mechanism. Open-ended earnout provisions in domain agreements are a frequent source of post-closing disputes.

Step 3 – Draft the representations and warranties to cover the .ai-specific risks

Representations and warranties do the heaviest legal lifting in any domain assignment agreement. In a .ai context, the seller's reps must go beyond the standard "I own it and no one else has a claim." Here is what must be covered, and the trap concealed in each item.

No prior UDRP or national-court action. The seller warrants that no complaint under the UDRP or any equivalent procedure has been filed, threatened in writing, or settled in connection with the domain. The trap: a seller may truthfully warrant "no pending action" while knowing a demand letter was sent two months ago. Extend the warranty to cover any written demand or threat, not just filed proceedings.

Trademark non-conflict. The seller warrants that the domain does not infringe any registered trademark of a third party of which the seller is aware. The trap: this warranty is limited by the seller's actual knowledge. Supplement it with a buyer-side clearance search of the USPTO, EUIPO, and WIPO's Global Brand Database for marks that incorporate the domain string. A .ai name in the AI-technology sector carries elevated trademark-conflict risk given the density of registered marks in that space.

No registrar lock or transfer restriction. The seller warrants that the domain is not subject to a registrar lock, a 60-day post-creation lock, a dispute-related lock, or any contractual transfer restriction with a third party (including a prior purchase agreement or right of first refusal). The trap: a 60-day post-creation or post-transfer lock may be invisible in current RDDS data but will block the push regardless of what the agreement says. Confirm lock status with the registrar in writing before execution.

Authority and no third-party rights. The seller warrants full authority to assign and that no third party holds any claim, lien, license, or right in the domain. The trap: a domain acquired as part of a venture investment or a joint-development arrangement may carry an implicit license or a co-ownership claim. If the domain was ever used in a business with more than one founder, get a written release from any co-founders or co-investors before closing.

Step 4 – Structure the escrow and the transfer mechanics

Escrow is not optional for a domain assignment of material value. It is the mechanism that synchronizes the money and the domain so that neither party bears the full risk of the other's non-performance. The trap in this step is the assumption that escrow is automatic. It is not. You must specify the escrow provider, the escrow instructions, and the release conditions with precision.

For a .ai domain assignment, the escrow structure should work as follows. The buyer deposits the purchase consideration into a neutral escrow account held by an agreed provider before the seller initiates any registry action. The seller then notifies the Anguilla registry of the assignment and initiates the registrar-level push or change-of-registrant process. The escrow agent holds funds until the buyer's registrar confirms – in writing or through system acknowledgment – that the domain is active under the buyer's account and that no transfer restriction applies. Only at that point does the escrow agent release funds to the seller.

Define the failure conditions with equal precision. If the registry or registrar refuses the transfer due to a lock, an eligibility failure, or a prior encumbrance, the agreement must specify the remedy: a full refund from escrow, a defined cure period during which the seller may resolve the blockage, and a termination right if the cure period expires without resolution. Vague language ("the parties will cooperate") is not a remedy.

On the .ai-specific mechanics: the Anguilla registry's role means the transfer is not purely a registrar-level push. If the registry requires a separate approval step, the agreement's completion date must be long enough to accommodate it – typically allow at least 15 to 30 business days from execution to confirmed transfer, and build in a mutual extension mechanism if registry processing delays arise.

If a .ai transfer is stalled at the registry or registrar level, or if the seller has not performed within the agreed period, email info@cognomenlaw.com for an assessment of your options.

Step 5 – Address post-assignment UDRP exposure and indemnification

A UDRP complaint against a domain can be filed after the assignment closes. Under Paragraph 4(a) of the UDRP, the policy applies to the current registrant – which, post-closing, is the buyer. If a third party had a legitimate UDRP claim against the seller and delayed filing until the buyer acquired the domain, the buyer now faces the complaint. This is not a theoretical risk in the .ai space, where the domain suffix carries inherent brand value and trademark owners monitor registrations closely.

The assignment agreement must therefore include a seller indemnity covering any UDRP or ccTLD dispute proceeding filed within a defined post-closing period (a 24-month window is common in our practice for high-value domain assignments) arising from the domain's registration or use before the closing date. The indemnity should cover the buyer's forum filing fees, legal costs, and any loss of the domain resulting from a pre-closing bad-faith registration or use by the seller.

The mirror risk runs the other way: if the buyer's own trademark portfolio or planned use of the domain creates a new conflict post-closing, that exposure falls on the buyer alone. A pre-acquisition clearance search – cross-referencing the domain string against live trademark registers in the buyer's key commercial markets – is the most effective way to identify that second category of risk before rather than after the agreement is executed.

In a recent matter (a .ai acquisition by a technology company, spring 2025), we identified a prior WIPO demand letter in the seller's files that had not been disclosed. The discovery came during due diligence, before signing. The agreement was restructured to include a full indemnity and an escrow holdback for the duration of a potential complaint window. The transfer completed without incident. Had due diligence been skipped, the buyer would have received both the domain and the undisclosed legal exposure.

Step 6 – Governing law, dispute resolution, and the final execution mechanics

A domain assignment agreement for a .ai domain raises an immediate choice-of-law question: which legal system governs the contract itself? The .ai zone is administered under Anguilla law, but neither party to a typical AI-sector acquisition is Anguillian. Most parties choose the law of a commercially familiar jurisdiction – New York, California, English law, or the law of the buyer's or seller's home state – with a clear exclusion of conflict-of-law rules that might redirect to Anguilla. Whatever jurisdiction is chosen, state it expressly; courts will not infer it from the zone of the domain.

Dispute resolution for the agreement itself (as distinct from any UDRP proceeding against the domain) should be addressed separately. International commercial arbitration – under ICC, LCIA, or UNCITRAL rules – is appropriate for cross-border high-value transactions. For smaller transactions, a jurisdiction clause pointing to a US federal or state court, or an English court, is workable. The trap: choosing arbitration without specifying the seat, the rules, and the language produces an agreement that is technically binding but practically unusable if a dispute arises.

The execution block must confirm: (1) the date of execution; (2) the capacity in which each signatory signs; (3) whether wet signatures are required by the Anguilla registry or whether electronic execution (under applicable e-signature law) is accepted for the registry's purposes. Confirm the registry's acceptance of electronic signatures before relying on a DocuSign-type execution, particularly if the registry form requires notarization or apostille.

Finally, include an integration clause confirming that the written agreement supersedes all prior oral discussions and letters of intent. In domain transactions, where negotiation often begins with an informal broker exchange or a messaging thread, the absence of an integration clause creates ambiguity about which terms were "agreed" before signing.

How does a .ai assignment compare to a .com or other ccTLD assignment?

The right route and the right agreement structure depend on the zone. A .com assignment is the simplest case: the registrar-to-registrar transfer follows ICANN's standardized transfer policy, escrow mechanics are well-understood, and UDRP applies directly. No separate registry approval is required beyond the registrar level. A .ai assignment is more involved: the Anguilla registry's role adds an approval layer, eligibility must be confirmed, and the combination of ccTLD mechanics with UDRP dispute exposure creates a dual-track risk picture that a standard .com assignment agreement does not address.

Compare a .de assignment: DENIC (the .de registry) requires direct registry approval and a formal change-of-holder process with specific documentation requirements. There is no UDRP for .de, so dispute exposure runs through the German courts, and the DENIC DISPUTE entry – which blocks transfer while a claim is pursued – must be searched and cleared before the assignment can complete. A .uk assignment under Nominet adds a distinct DRS procedure (with its "registered or used abusively" test, a lower bar than the UDRP's cumulative "registered and used in bad faith") and a free mediation stage that may affect settlement dynamics if a prior claim existed.

For any ccTLD not addressed in published registry guidance, verify the current transfer procedure with counsel before executing. Registry policies change, and an assignment agreement drafted on outdated assumptions about the transfer process may fail at the registry level regardless of how well it is drafted as a contract.

The cost comparison also matters. A .com assignment at ICANN-standard registrar fees is the lowest-friction route when the buyer already operates in the gTLD space. A .ai assignment carries the additional cost of registry engagement and, if a prior dispute is discovered, the cost of a UDRP response or a pre-assignment release negotiation. Budget for that contingency at the term-sheet stage, not after signing.

In a second recent matter (a .ai-to-.com simultaneous acquisition, summer 2025), a buyer acquiring both zones discovered that the .ai domain had a different beneficial owner from the .com – a common scenario when a domain portfolio has been built across registrars over time. Two separate assignment agreements were required, each with its own escrow tranche and its own registry process. The failure to anticipate this at term-sheet stage added approximately three weeks to the closing schedule.

Related at COGNOMEN

• Domain purchase, sale, escrow, and brand-protection monitoring services at COGNOMEN
• Analysis: domain assignment agreements in technology-sector transactions
• Guide: protecting your brand across new gTLD launches