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

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

A retailer agrees to sell its .store domain. Both sides shake hands, the seller hands over the auth code, and the buyer discovers six months later that the domain carries a prior UDRP proceeding – one that nearly stripped the seller of the name and left a permanent record in the dispute history. The transfer is already done. The leverage is gone.

To draft a domain assignment agreement for a .store domain, you must address chain-of-title, prior dispute history, registrar mechanics, escrow structure, and post-transfer registration requirements specific to the .store new gTLD. The UDRP applies in full to .store domains, meaning a tainted registration follows the new owner unless the agreement quarantines that risk. A well-drafted assignment takes the process through at least five distinct steps, each hiding a different trap.

This guide covers each step in sequence, flags the trap inside it, and connects the drafting exercise to the broader .store transaction environment – including what to do when due diligence uncovers a problem before closing.

Why .store assignments differ from a plain .com transfer

.store is a new gTLD operated under ICANN's 2012 new gTLD program, which means the UDRP applies at every accredited registrar exactly as it does for .com, .net, and .org. A dispute or a panel finding under the UDRP attaches to the domain's registration record, not to the current registrant's identity. Buy the domain; inherit the history.

Beyond the UDRP exposure, .store carries registry-level policies set by the .store registry operator. Those policies govern permitted uses, registrant eligibility, and the conditions under which the registry may suspend or cancel a registration. A domain assignment agreement that ignores registry policy is not just incomplete – it is potentially void where the proposed transfer violates a registry rule the parties overlooked.

The URS (Uniform Rapid Suspension) is a second dispute route available for new gTLDs including .store. Under the URS, a brand owner can seek rapid suspension of a domain – not transfer, but suspension for the remainder of the registration term. A domain that has been suspended under URS and then re-registered is a domain with a visible dispute scar. Your assignment agreement must account for that possibility, particularly in representations and warranties.

In our practice, we regularly advise buyers who discover mid-negotiation that a .store domain they are acquiring was the subject of a prior URS filing that ended in settlement rather than a formal decision. Settlement closes the proceeding but does not erase the filing from the record. That fact matters for price, for warranty carve-outs, and for the due diligence timeline.

For an assessment of your .store domain transaction – whether you are buying, selling, or renegotiating after a diligence finding – contact info@cognomenlaw.com.

Step 1 – Run a chain-of-title and dispute-history check before drafting begins

Chain-of-title for a domain means the sequence of registrants from original registration to the present seller, and whether any link in that chain acquired the domain in circumstances that could taint the current holder's position. For a .store domain, that check runs through at minimum three sources: the RDDS (registration data) record, the WIPO case search, and the Forum's case search.

The trap in Step 1 is treating the RDDS record as complete. WHOIS/RDDS data has been progressively redacted under privacy and data-protection policies, and the displayed registrant may be a privacy proxy, not the beneficial owner. Your assignment agreement must require the seller to represent – with a warranty backed by indemnity – that the named registrant and the beneficial owner are the same person or entity, and that no undisclosed trust, lien, or prior transfer obligation encumbers the domain.

A prior UDRP proceeding that the complainant lost is not necessarily a problem. A prior proceeding that the respondent won by asserting a specific legitimate interest is actually useful: it creates a record supporting the current registrant's chain of title. A prior proceeding that was terminated because the parties settled, with an undertaking that the domain would not be used in certain ways, is a material encumbrance – it binds successors in interest if the settlement agreement says so.

Practical output of Step 1: a written chain-of-title memo that the parties attach to the assignment agreement as an exhibit. That memo lists each prior registrant (to the extent ascertainable), every dispute filing, and the outcome of each. It becomes the baseline for the seller's representations.

Step 2 – Structure the representations and warranties around .store-specific risks

Standard domain assignment templates borrow from .com practice. For .store, that is a starting point, not a finished product. The core seller representations in a .store assignment agreement should cover at least the following, each drafted to address the trap the generic template misses.

Registrant authority. The seller represents that it is the registered holder of record, that it has authority to assign without consent of a third party, and that no court order, arbitration award, or panel decision currently restricts transfer. The trap: an open UDRP proceeding triggers a registrar lock that physically prevents transfer. The agreement must address what happens if a proceeding is filed between signing and closing – a MAC (material adverse change) clause keyed to dispute filings is standard practice.

No pending disputes. The seller represents that no UDRP complaint, URS filing, or registry dispute is pending or, to the seller's knowledge, threatened. "To the seller's knowledge" is the negotiating battleground; buyers should push for a warranty without the knowledge qualifier for filed proceedings, because filed proceedings are objective facts.

Registry compliance. The seller represents that the registration is current, that all renewal fees are paid, and that the domain has not been placed on registrar or registry hold, lock, or suspension other than a standard registrar lock pending transfer. The trap: a registry-level hold for abuse (phishing, malware distribution, spam) follows the domain through a transfer. The buyer inherits not just the name but the registry's adverse action.

Trademark non-infringement. This is the most contested clause. The seller cannot represent that the domain does not infringe any trademark anywhere in the world – that is an impossibility. The practical drafting goal is a representation that, to the seller's knowledge after reasonable inquiry, no third party has asserted in writing a trademark claim against the domain, and that no such claim exists in a jurisdiction material to the buyer's intended use.

In a recent matter (a .store domain acquisition, spring 2025), we identified during due diligence a cease-and-desist letter from a European brand owner that the seller had received two years earlier and never disclosed. The letter had not ripened into a UDRP filing, but it established that a third party with plausible trademark rights had placed the seller on notice. The price was renegotiated; the agreement included a specific escrow holdback tied to that claim.

How to draft a domain assignment agreement for a .store domain – the core document architecture

The document architecture for a .store assignment agreement has seven operative sections. Each section has a specific drafting purpose; omitting one does not simplify the agreement – it creates an unallocated risk that surfaces at closing or in post-closing litigation.

1. Recitals. Identify the domain by full registrant name (not privacy proxy), registrar, registration expiry date, and registration ID. The trap: expiry within 60 days of signing. Registrar transfer policies for new gTLDs commonly prohibit transfers within a short window before expiry. Build in a renewal obligation or a pre-closing renewal condition.
2. Assignment clause. Assign "all right, title, and interest in and to the domain name registration." Do not limit the assignment to the "domain name" alone – that language omits the registration record, the transfer-authorization code rights, and any UDRP history that travels with the domain.
3. Representations and warranties. As set out in Step 2. Add a bring-down mechanism: warranties are true at signing and re-certified at closing.
4. Covenants. Seller covenants to cooperate with the registrar transfer, to provide the auth code within a specified number of business days after closing payment, and to take no action (including renewal, configuration change, or DNS alteration) between signing and closing without buyer consent.
5. Purchase price and escrow. See Step 3 below.
6. Post-closing obligations. Seller cooperates with any registrar-level dispute about the transfer itself. Buyer updates the RDDS record to its own details within a specified period. Failure to update creates a risk that the domain appears to remain in the seller's name, which can complicate a future UDRP analysis.
7. Governing law and dispute resolution. See Step 4 below.

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

Step 3 – Structure escrow to absorb dispute-history risk

Escrow in a domain assignment serves two functions that generic escrow frameworks sometimes collapse into one: payment security (the buyer's funds are protected pending transfer) and claim holdback (a portion of the price is retained pending the expiry of a defined risk period). For a .store domain, the claim holdback function is the more legally interesting one.

A UDRP complaint filed against the domain after the assignment closes will name the new registrant as respondent. The new registrant – the buyer – then has 20 days to file a response and must bear the cost and effort of defending a proceeding that originated in the seller's conduct. The escrow holdback structure addresses this by reserving a portion of the purchase price for a defined period (commonly 12 months after closing, or until the expiry of the first full registration year post-transfer), with release conditioned on no UDRP or URS filing being commenced.

The trap in Step 3 is the holdback trigger language. A filing is a filing even if the complaint is facially deficient. The parties must decide whether the trigger is (a) the filing of any complaint, or (b) the commencement of a proceeding that passes the provider's formal compliance review. Option (b) is narrower and more defensible; option (a) is simpler and gives the buyer more protection against the distraction cost of defending even a weak complaint.

A second escrow consideration specific to .store: renewal costs. The .store registry commands a higher annual renewal fee than .com or .net. Where the domain is renewing within 12 months of closing, the agreement should either (a) require the seller to renew pre-closing so the buyer takes a fresh registration year, or (b) adjust the purchase price to credit the buyer for the imminent renewal cost. Neither approach is unusual; we recommend making it explicit because disputed renewal obligations are a common source of post-closing friction.

Step 4 – Choose governing law and a dispute resolution clause that fits a .store context

A domain assignment agreement is a private contract. Governing law is freely chosen by the parties. For a .store domain, that choice has a practical implication: the UDRP and URS operate independently of the governing law of the contract. A panel deciding a post-transfer UDRP complaint applies the Policy, not the parties' chosen law. The governing law clause controls contract disputes between the parties; it does not shield the domain from a post-transfer UDRP action by a third party.

What is the right law to choose? The answer turns on where the parties are located and what enforcement risk is most salient. A buyer in the United States and a seller in the European Union will typically choose either New York law (familiar to both sides' commercial counsel) or the law of the seller's jurisdiction if the primary litigation risk is seller non-performance. The practical floor is that the choice must be a jurisdiction where a contract judgment can be enforced against the other party without prohibitive difficulty.

The dispute resolution clause for the contract itself – as distinct from any domain dispute – should address at minimum: (a) the forum for contract litigation, (b) whether arbitration is elected in lieu of court, and (c) jurisdiction for emergency relief (registrar lock orders). A clause that sends all disputes to arbitration but does not carve out emergency injunctive relief can leave a buyer without a practical remedy if the seller tries to transfer the domain to a third party between signing and closing.

Cross-border dimension: if the .store domain is the subject of a separate UDRP proceeding filed concurrently with a purchase negotiation, the contract and the UDRP track run in parallel. We regularly advise buyers in exactly this situation – where the purchase price is conditioned on a clean UDRP outcome but the UDRP timeline of roughly two months does not align neatly with a transaction timeline driven by business imperatives.

Step 5 – Execute the transfer and update the registration record

Execution of a domain assignment is not just signing a PDF. The legal transfer is complete only when the registrar implements it. For a .store domain at an ICANN-accredited registrar, the standard mechanism is an auth code (also called an EPP code or transfer authorization code) provided by the seller to the buyer, who then initiates a registrar transfer request. The receiving registrar confirms with the gaining registrant; the losing registrar has five days to object or approve.

The trap in Step 5 is the five-day window combined with a seller who drags its feet. If the seller does not explicitly approve (or does not respond within the window), the transfer typically proceeds by default approval. However, if the seller affirmatively objects – even without legal justification – the transfer is blocked and the buyer must pursue the registrar's dispute mechanism or seek court intervention. The covenant in Section 4 of the assignment agreement (cooperate with transfer, do not act unilaterally) is the pre-contractual protection; a short-form indemnity for costs incurred if the seller obstructs the transfer is the post-contractual backstop.

After the transfer completes, the buyer must update the RDDS/WHOIS registration record to reflect its own details. Failure to do so is not merely an administrative lapse. If a third party files a UDRP complaint naming the prior registrant, the panel may dismiss the complaint on technical grounds – or worse, issue a default transfer order against the prior registrant's data before the buyer even knows there is a proceeding. Update the record promptly. Build a contractual deadline into Step 2's post-closing obligations.

In a second matter we handled (a .store domain sale, autumn 2024), the buyer completed the transfer but did not update the RDDS record for approximately three months after closing. A brand owner with a plausible trademark claim filed a UDRP complaint during that window. The matter was ultimately resolved, but the delay in updating the record created unnecessary procedural complexity and cost that a simple post-closing covenant would have prevented.

When due diligence reveals a problem: the route options

Not every .store domain transaction closes cleanly. Due diligence sometimes reveals a material dispute risk – an open UDRP threat, a prior settlement with use restrictions, or a registry-level hold – that the buyer was not expecting. At that point the parties face a decision matrix with four practical routes.

Route A: Renegotiate and continue. The parties adjust the purchase price to reflect the identified risk, restructure the escrow holdback, and add a specific warranty covering the discovered issue. This is the most common outcome where the underlying risk is quantifiable. It requires that the parties agree on how to value the risk, which in turn requires an assessment of whether the third party with the trademark claim is likely to file a UDRP and, if so, whether the new registrant would prevail. We assess those three UDRP elements and provide that analysis as part of due diligence for .store acquisitions.

Route B: Seek a clean-up filing first. Where the domain carries an arguable trademark conflict and the buyer intends to use the domain in the relevant sector, one option is to file a defensive UDRP response (as respondent, if the complaint has been filed) before completing the assignment. Transfer during a pending UDRP proceeding is blocked by the registrar lock triggered on commencement, so this route applies where the complaint has not yet been filed but the risk is foreseeable. The buyer can negotiate a price conditioned on the seller successfully defending a hypothetical complaint, effectively requiring seller representations about the strength of their legitimate-interest claim.

Route C: Walk away. Where the dispute history is genuinely tainted – for example, a prior panel finding of bad faith that the current registrant explains away as a clerical error in registration – the buyer may be better served by declining and seeking a cleaner alternative domain. .store is an active TLD with meaningful inventory. A tainted .store domain bought cheaply can cost multiples of the savings in defense costs within a single registration year.

Route D: Proceed to court first. Where the domain is subject to a court order (for example, a US anticybersquatting judgment or an injunction preventing transfer), neither the assignment agreement nor the UDRP resolves the problem. Local litigation counsel in the relevant jurisdiction must address the court order before any domain assignment can close. This route adds time and cost but is the only legally sound one when a court has jurisdiction over the domain's chain of title.

The right route depends on zone, timeline, and litigation appetite. A .store domain conflict that could be resolved through a UDRP proceeding (roughly two months, starting at USD 1,500 at WIPO for a single-member panel) looks very different from one requiring court action. If the domain also has a parallel .eu or .uk presence, the buyer should note that both the EURid ADR.eu procedure and the Nominet DRS have their own distinct tests and timelines – the .eu and .uk disputes do not follow the UDRP's "registered AND used in bad faith" framework in all respects, and a parallel assignment covering those ccTLDs requires separate analysis.

Related at COGNOMEN

• Domain transactions, due diligence, and escrow services across all zones
• Global brand-protection monitoring for domain portfolios and new gTLDs
• Transfer remedies under the .eu ADR procedure: analysis and strategy