Step-by-step: draft a domain assignment agreement for a .finance doma…

Step-by-step: draft a domain assignment agreement for a .finance doma. UDRP and ccTLD domain recovery and defense across .finance. Email the firm to assess you…

A fintech company agrees to sell its flagship .finance domain. The purchase price runs to five figures. Handshakes are exchanged, an invoice is sent – and then nothing happens, because neither side has a signed, binding agreement that actually moves the name from one registrant to another. The deal stalls, one party loses confidence, and a registrar lock prevents any transfer while the dispute festers. This is a common failure mode in domain transactions, and it is entirely avoidable.

To draft a domain assignment agreement for a .finance domain, a buyer and seller must produce a written instrument that correctly identifies the domain by full string and registrar, states the consideration and payment mechanics, specifies the escrow structure, warrants chain of title and the absence of prior dispute history, and incorporates a step-by-step transfer protocol tied to registrar mechanics for new gTLDs. The assignment also must address what happens if a UDRP complaint is filed against the domain between signing and closing – a risk that is real and time-sensitive.

This guide walks each drafting step, flags the trap hidden inside it, and addresses the cross-zone and cross-forum dimensions that make .finance transactions different from a routine .com transfer.

Why is a .finance domain assignment different from a standard gTLD transfer?

.finance is a new gTLD operated under ICANN's delegation framework, and every registrar authorized to provision it must comply with the 2013 Registrar Accreditation Agreement and its successor policies governing inter-registrant transfers. That matters for drafting because the mechanics of pushing a new gTLD differ from .com in one critical respect: the domain string itself is longer and may trigger financial-sector brand-protection services that can block or flag a transfer attempt. Some registries operating financial-vertical new gTLDs apply additional compliance screens.

The UDRP applies to .finance in exactly the same way it applies to .com. A panel seated at WIPO or the Forum can order transfer or cancellation of a .finance domain on the same three-element test under Paragraph 4(a) of the Policy. What that means for a buyer is simple: if the seller acquired the name through registration conduct that would satisfy a complainant's bad-faith case, the buyer acquires that exposure too. The agreement must address it. We regularly advise buyers in financial-sector new-gTLD transactions who discover a prior UDRP complaint only after they have paid.

The practical difference also runs to market depth. .finance does not trade as frequently as .com. Comparable sales data is thinner, which means the price discovery process is less transparent and the buyer's due-diligence window should be longer, not shorter.

Step 1: Identify the domain and confirm current registrant status

The first step – and the one most frequently rushed – is to confirm in writing exactly which domain string is being sold, who holds it today, and whether that holder has unencumbered authority to transfer it. The WHOIS/RDDS record is the starting point, but it is not the finish line.

Check the following before any agreement is signed:

• Registrant name and organization as they appear in the registry RDDS output – these must match the seller's identity exactly.
• Registrar of record – the agreement must name the actual registrar, because the transfer protocol is registrar-specific.
• Registration and expiration dates – a domain expiring within 60 days of the planned closing date creates transfer-timing risk under most registrar policies.
• Lock status – a registrar lock or a UDRP-related lock will block the transfer; both must be resolved before closing.
• Any pending dispute flag – some registrars annotate the domain if a UDRP complaint has been filed; a WIPO or Forum case number visible in RDDS is a red stop signal.

The trap in Step 1: buyers assume the RDDS record is current. Under ICANN's privacy/proxy rules, the RDDS may show a proxy service as the registrant. The agreement should require the seller to confirm, by written declaration, that the beneficial owner is the party signing and that no proxy service holds rights the seller cannot transfer.

Step 2: Conduct chain-of-title and prior-dispute due diligence

Chain-of-title for a domain is not a registry document you can pull in one click. It is assembled from registration history, WHOIS snapshots, archived UDRP decisions, and – where the domain has changed hands before – prior assignment agreements. Each gap in that chain is a potential defect that a future claimant can exploit.

For a .finance domain, the specific searches to run are:

1. WIPO and Forum case search – both providers maintain public case databases. Search the full domain string for any filed complaint, including complaints that were withdrawn, settled, or decided in the registrant's favor. A settled case can still evidence a trademark owner's ongoing interest in the name.
2. Web archive review – the Wayback Machine and similar services show what the domain resolved to at material dates. A history of pay-per-click parking on a competitor's brand is a bad-faith indicator that a future complainant's lawyer will find in under ten minutes.
3. Trademark clearinghouse cross-reference – the Trademark Clearinghouse (TMCH) is an ICANN-mandated mechanism that flags new registrations that match protected marks. A .finance domain registered during a sunrise period has a different title posture than one registered in general availability; the agreement should confirm which category applies.
4. Prior owner correspondence – if the domain has changed hands, request copies of any cease-and-desist letters, settlement agreements, or licensing arrangements from prior owners. These can survive a transfer and bind the new registrant by conduct or estoppel.

The trap in Step 2: buyers treat a clean WIPO search as a clean bill of health. It is not. A trademark owner who has not yet filed a complaint may file one the day after closing. The due-diligence step does not eliminate that risk; it calibrates it. If the domain string is identical or closely similar to a mark in a financial-services class, the buyer's counsel should assess whether a UDRP complaint is a realistic post-closing threat and price that risk into the transaction.

In a transaction we advised on in early 2025, the buyer of a .finance domain discovered, during due diligence, that a prior registrant had settled a UDRP complaint by entering into a confidential coexistence agreement. The prior owner had not disclosed this. The assignment agreement was renegotiated to include a price reduction and an indemnity clause. Without that diligence step, the buyer would have acquired a contractual obligation it never agreed to.

For a read on whether the three UDRP elements are met for the domain you are acquiring or defending, reach us at info@cognomenlaw.com.

Step 3: Structure the payment and escrow mechanics

A domain assignment is not a standard goods sale. The "delivery" of the domain occurs through a registrar transfer process that can take days and can fail for reasons outside either party's control. Payment and delivery must therefore be sequenced through escrow – not through a wire transfer on trust.

The escrow structure for a .finance domain assignment should provide for the following:

• Funds deposited by buyer into escrow before transfer is initiated. The escrow agent holds the funds until the transfer is confirmed at the registry level – not merely at the registrar level.
• The seller initiates the transfer by unlocking the domain and generating an authorization code (also called an EPP/auth code or transfer key). This code is delivered to the escrow agent or directly to the buyer simultaneously with the funds instruction.
• The buyer or the escrow agent initiates the inbound transfer at the gaining registrar. Most registrars require the domain to be confirmed at the registry within a defined window after the authorization code is issued – typically five days, though this varies by registrar policy. The agreement should specify what happens if the transfer window expires.
• Release of funds to seller occurs upon registry confirmation that the domain is registered in the buyer's name. Not the registrar's acknowledgment email. Registry confirmation.
• The agreement should name a recognized escrow provider and state that the provider's standard escrow terms are incorporated by reference. No reputable domain transaction of meaningful value should bypass escrow.

The trap in Step 3: parties sometimes agree to a simultaneous exchange – buyer wires funds, seller pushes the domain, and each hopes the other performs. This is operationally risky for high-value .finance domains. A registrar system error, a transfer rejection, or a registry compliance flag can cause the domain to be held in limbo. Properly structured escrow eliminates that exposure for both sides.

Step 4: Draft the core agreement provisions

Once due diligence is complete and escrow mechanics are agreed, the assignment agreement itself needs to be drafted. A .finance domain assignment agreement should contain, at minimum, the following provisions:

Identification clause: State the full domain string (e.g., example.finance), the registrar of record as of the signing date, and the registry operator. If the registrar changes between signing and closing, the agreement should specify that this does not void the assignment but that the seller must give prompt written notice.

Consideration: State the purchase price in the currency of the transaction, the payment method, and the escrow mechanics by reference to the escrow agreement incorporated as an exhibit.

Seller representations and warranties: These are the most commercially negotiated provisions. The seller should warrant that: (a) it is the sole registered holder of the domain; (b) the domain is free of any lien, encumbrance, lock, or dispute; (c) no UDRP complaint, URS proceeding, or court action is pending or, to the seller's knowledge, threatened; (d) the domain was registered in good faith and there is no prior conduct that a complainant could characterize as bad faith under Paragraph 4(b) of the UDRP; (e) no cease-and-desist letter has been received and unanswered; and (f) the seller has full authority to assign the domain without any third-party consent.

Indemnification: The seller should indemnify the buyer against any loss arising from a breach of the representations above, including the costs of defending a UDRP complaint filed on the basis of pre-closing conduct.

Transfer protocol: Specify the exact sequence – unlock, generate auth code, deliver to escrow, initiate transfer, registry confirmation, release of funds – with a timeline and a responsibility matrix. This converts the general escrow structure into an enforceable obligation.

Closing conditions: The buyer should have the right to terminate without penalty if, between signing and closing, a UDRP complaint or URS proceeding is filed, a registrar lock is imposed, or a material warranty breach is discovered.

Post-closing obligations: The seller should cooperate with any registrar verification steps required by the gaining registrar, and should not take any action after closing that could interfere with the transfer or result in a registrar cancellation of the domain.

Governing law and dispute resolution: Choose a jurisdiction with a developed body of contract law and, separately, address how domain-specific disputes will be handled. Many practitioners include a clause clarifying that nothing in the agreement constitutes a waiver of any party's rights under the UDRP or applicable registry policies, since those are not subject to private contractual modification.

The trap in Step 4: sellers often push for minimal representations, arguing that a domain is sold "as is." For a .finance domain in a high-value transaction, an "as is" clause without specific carve-outs for UDRP exposure is commercially dangerous for the buyer. The warranty and indemnification package is not boilerplate – it is the economic heart of the deal.

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

Step 5: Address UDRP risk in the gap period between signing and closing

The gap between signing an assignment agreement and completing the registrar transfer can run from a few days to several weeks. During that window, a trademark owner who becomes aware of the pending transaction may choose to file a UDRP complaint against the current registrant – the seller. If a UDRP complaint is filed and the registrar imposes a lock, the transfer cannot proceed until the UDRP is resolved. That resolution takes roughly two months at WIPO in a standard case.

The agreement should address this scenario in three ways:

• Notification obligation: the seller must notify the buyer within 24 hours of receiving any UDRP complaint, cease-and-desist letter, or registrar communication relating to the domain after signing.
• Termination right: the buyer may terminate the agreement without penalty if a UDRP complaint is filed during the gap period and the domain is locked as a result.
• Cooperation obligation: if the buyer elects to keep the agreement in place and wait for the UDRP to resolve, the seller must cooperate fully in the defense and must not make any settlement offer or take any procedural step in the UDRP without the buyer's written consent.

Why does this matter specifically for .finance? The financial-services sector is heavily branded. Trademark portfolios in banking, payments, lending, and insurance are aggressively monitored. A .finance domain transaction on a high-value string will likely be visible to brand protection teams at major financial institutions. The risk of a gap-period complaint is not theoretical.

Step 6: Execute, complete the transfer, and confirm registration

Execution of the agreement should be by the registrant of record – not a related entity, a corporate parent, or an authorized representative acting without documented authority. If the seller is a corporate entity, the agreement should include a resolution or officer's certificate confirming that the signatory is authorized to transfer the domain.

After execution, the transfer sequence follows the protocol in the agreement. The practical steps are:

1. Seller confirms the domain is unlocked and no active locks are in place.
2. Seller generates and delivers the authorization code to the escrow agent within the agreed timeframe.
3. Buyer's gaining registrar initiates the inbound transfer using the authorization code.
4. Registry confirms the transfer is complete and the domain is now registered to the buyer.
5. Escrow agent releases funds to seller on receipt of written confirmation of registry-level transfer.
6. Both parties execute a short-form closing confirmation for the record.

The trap in Step 6: the authorization code expires. Most registrar policies impose a validity window – commonly five to seven days – on the auth code once generated. If the gaining registrar's system is slow, or if the buyer's account verification is pending, the code may expire before the transfer is initiated. The agreement should specify what happens in that scenario: the seller re-generates the code and the escrow timeline is extended by a defined period.

After transfer confirmation, the buyer should immediately verify the RDDS record reflects the new registrant information and update all registrant contact data at the gaining registrar. Failing to update contact data creates a secondary risk: if a UDRP complaint is filed after closing and the prior registrant is still shown in RDDS, the complaint may be served on the wrong party.

How does the cross-zone picture affect a .finance domain assignment?

A buyer acquiring a .finance domain often operates across multiple zones. The same brand may exist as a .com, a national ccTLD such as .uk or .de, or other financial-vertical new gTLDs. The assignment agreement for the .finance domain does not automatically extend to any other domain. Each zone requires its own transfer mechanics.

The cross-zone dimension matters for three reasons. First, if the buyer intends to consolidate a multi-zone portfolio, the assignment agreements for each zone should be executed simultaneously or with sequenced closings, to avoid a gap where the brand is split across registrants. Second, the UDRP applies to .finance but not to .de – a .de dispute would proceed through the German courts, with DENIC offering a DISPUTE entry to block transfer during litigation. Third, if the seller also holds the .uk counterpart, the Nominet DRS governs any dispute under the "abusive registration" test, which reads "registered or used" abusively – a materially different standard from the UDRP's cumulative "registered and used" requirement. A buyer assuming uniform UDRP protection across all zones is working from an incorrect premise.

Where a portfolio transaction involves both a .finance domain and ccTLD registrations in European jurisdictions, the assignment documentation should be coordinated with local litigation counsel in the relevant jurisdiction for the ccTLD transfers. The UDRP agreements are straightforward; the ccTLD-specific transfer mechanics and dispute exposure are not.

Related at COGNOMEN

• Domain transactions, due diligence, and portfolio brand protection services
• Recovering a lapsed or expired domain registration
• How to recover a stolen or hijacked domain