Step-by-step: structure escrow for a .store domain purchase

Step-by-step: structure escrow for a .store domain purchase. UDRP and ccTLD domain recovery and defense across .store. Email the firm to assess your case.

You find the exact .store domain your brand needs. The seller quotes a price and asks for payment upfront. Wire the funds and you have no domain, no recourse, and a dispute that will take months to untangle. That is not a hypothetical. It is the most common way a domain acquisition goes wrong.

To structure escrow for a .store domain purchase, a buyer must verify clean chain of title, confirm the domain has no pending or prior UDRP history, engage a neutral escrow service, lock the transfer sequence so that the domain moves before funds release, and confirm ICANN's 60-day transfer lock does not trap the asset after acquisition. The .store gTLD sits fully within the UDRP, administered by WIPO and the Forum among others, so any complaint filed against the prior registrant can follow the name into your account. Getting the sequence right is not optional.

This guide walks each step, names the trap each step conceals, and sets out the realistic timeline and cost for a properly structured .store acquisition.

Why does the .store zone matter for escrow structure?

The .store extension is a delegated new generic top-level domain (new gTLD) that operates under standard ICANN policy, including mandatory UDRP dispute resolution. That single fact has two practical consequences for a buyer. First, WIPO, the Forum, CAC, and ADNDRC all have jurisdiction over any .store domain dispute. Second, bad-faith registration history on the domain does not die when the domain changes hands – a brand owner holding trademark rights can file a UDRP complaint against the new registrant if the name remains confusingly similar to their mark.

In our practice we have assessed acquisitions where the seller's prior use – parking the domain on a pay-per-click page, sending demand letters to a mark holder – had already seeded facts that a panel could use against the incoming buyer. The buyer was not the bad actor. The domain was.

Additionally, the .store registry imposes standard ICANN transfer policies, including the 60-day inter-registrar transfer lock that triggers after any registrant change. Plan for that window. If your business launch depends on the domain being live and pointed at your servers the day the deal closes, a 60-day blackout is a material operational risk. The escrow structure must account for it.

Step 1: Run the chain-of-title and prior-dispute check before any money moves

The first step is entirely defensive, and it must happen before you sign a letter of intent, before you fund escrow, and before you disclose to the seller that you are prepared to pay a specific figure. Pre-acquisition due diligence on a .store domain has three components.

WHOIS and registration history. Pull the current registrant, registrar, and creation date from the RDDS (Registration Data Directory Services, the successor to the legacy WHOIS system). Verify the creation date independently through an archived registrar record or a domain history service. A domain created weeks before an approach to buy is a warning sign – it may have been registered opportunistically in anticipation of your brand's market entry.

UDRP history check. Search the WIPO and Forum published decision databases for any proceedings in which this exact domain string was the subject. Also search for the seller as a named respondent across any domain. A seller with a pattern of registering brand-similar names and selling them – what Paragraph 4(b) of the UDRP calls a pattern of abusive registrations – is a material risk factor for the incoming buyer. The domain may carry that history even after transfer.

Trademark clearance on the string. Confirm whether any active trademark registration covers the .store name as a whole or the distinctive element within it. The UDRP's first element is confusing similarity between a domain and a mark in which the complainant has rights. Acquiring a domain that is confusingly similar to an active, registered mark in your industry is acquiring a latent dispute.

To run pre-acquisition due diligence on a .store domain before funds move, contact info@cognomenlaw.com. We assess chain-of-title, prior UDRP history, and trademark risk across the string.

Step 2: Agree the purchase terms in writing before funding escrow

A signed purchase agreement is not a formality. It is the document that controls what happens if the transfer fails, if the seller is unresponsive after payment, or if a UDRP complaint lands in the window between escrow funding and transfer completion. At a minimum, the agreement should address the following points.

The exact domain string. Write it out in full, including the TLD (.store). Sellers have delivered the wrong variant – a hyphenated version, a different extension – and argued the agreement was ambiguous.

Representations and warranties. The seller warrants that it is the sole registrant, that no dispute is pending, that no UDRP complaint has been received and not yet disclosed, and that the domain is free of any registrar lock imposed by a third party. These representations are meaningful: if a complaint surfaces post-closing, the buyer has a contractual claim against the seller even where the UDRP panel has no power to award damages.

Transfer mechanics and the escrow release trigger. Define precisely what event releases funds to the seller. The only defensible trigger is confirmed receipt of the domain in the buyer's registrar account with the lock status cleared. Not "transfer initiated," not "transfer auth code provided," not "registrar confirms processing." Confirmed receipt.

UDRP suspension clause. If a UDRP complaint is filed after escrow is funded but before transfer is completed, the domain will be locked by the registrar. The agreement should require the seller to cooperate with any dispute, indemnify the buyer for legal costs of defending a complaint arising from the seller's prior use, and allow the buyer to terminate the agreement and recover escrowed funds if a complaint results in a transfer or cancellation order.

Step 3: Select and fund an independent escrow service

Escrow protects both parties. The buyer releases funds into a neutral account; the seller transfers the domain; the escrow agent releases funds only upon confirmed receipt. The trap in this step is not the concept – it is the execution.

Use only an escrow provider regulated as a money transmitter in the jurisdiction where it operates. In domain transactions, the standard is a provider that is explicitly licensed for internet property transactions and publishes its licensing status. In our practice, we do not name specific providers, but the principle is firm: if the escrow service is not separately licensed for financial services and domain transactions, it is not escrow – it is the seller's payment processor with a different name on the website.

The escrow fee is typically paid by the buyer, though parties sometimes split it. It is a modest percentage of the transaction value and is disclosed in advance by the escrow provider. Budget for it. Do not let the seller redirect the transaction to a "faster" or "lower-fee" alternative at the last moment – that is a common setup for payment fraud.

Domain transaction escrow for a new gTLD like .store involves the escrow provider issuing the transfer auth code (EPP code) to the buyer's registrar only after both sides confirm readiness. The buyer's registrar then initiates the pull. Confirm with your registrar in advance that it accepts push transfers for new gTLDs in the .store zone; some registrar platforms impose additional validation steps that add days to the timeline.

If you have already signed a purchase agreement and need a review of escrow structure before funding, email info@cognomenlaw.com. We read the transfer mechanics and spot the clause gaps that enable fraud or failed transfers.

Step 4: Execute the transfer sequence in the right order

The transfer sequence is where most errors occur. The correct order for a .store domain acquisition through escrow is fixed and non-negotiable.

1. Buyer funds escrow. The full purchase price (and escrow fee if buyer-paid) is deposited. The escrow agent confirms receipt to both parties. No partial funding; no staged payments unless the purchase agreement specifically addresses a milestone structure with defined completion criteria at each stage.
2. Seller unlocks the domain at the current registrar. The seller disables the registrar lock (also called the "registrar status: clientTransferProhibited" flag). The buyer verifies the lock is removed using the RDDS before the next step.
3. Seller provides the EPP auth code to the escrow agent. The auth code goes to the escrow agent, not directly to the buyer, until escrow conditions are met. Some platforms allow the buyer's registrar to initiate the pull using the code once the escrow agent confirms it is held. Either structure is acceptable; direct delivery of the auth code to the buyer before escrow funds are confirmed is not.
4. Buyer initiates transfer at their registrar. The buyer's registrar sends a transfer request. ICANN's transfer policy gives the losing registrar five calendar days to approve or deny. Absence of action within five days results in automatic approval. Both parties should be available during this window.
5. Buyer confirms receipt of the domain. Once the domain appears in the buyer's registrar account with the correct registrant data, the buyer instructs the escrow agent to release funds. This confirmation is the contractual trigger in a well-drafted agreement.
6. Escrow releases funds to the seller. The escrow agent pays the seller. The transaction is complete.

The trap in step 4 is impatience. Sellers sometimes push buyers to release funds once the transfer is "in progress." Do not. A transfer that is in progress has not yet completed. Until the domain is in your account, it is still controlled by the seller's registrar and, in theory, the seller.

Step 5: Confirm the 60-day lock and plan for post-transfer UDRP risk

After a successful inter-registrar transfer, ICANN policy requires a 60-day transfer lock on the domain. During this window, the domain cannot be transferred to a third registrar. It can, however, be pointed, managed, and used. The operational risk is limited to further resale or emergency re-transfer, not day-to-day use.

The UDRP risk, however, does not pause during the lock period. A trademark owner has no obligation to wait for the lock to expire before filing a UDRP complaint. In a recent matter – a new gTLD acquisition, autumn 2024 – we advised a buyer who received a UDRP complaint notice within three weeks of a completed transfer. The complaint was directed at prior use by the seller. The buyer had clean hands. But the defense still required filing a response within 20 days of commencement, presenting evidence of the buyer's good-faith acquisition, and demonstrating that the new registrant had legitimate interests going forward. The case was resolved without a transfer order. The cost and disruption were real.

The lesson: do not close a .store acquisition without a contingency plan for a UDRP complaint arriving in the weeks that follow. The due diligence in Step 1 is your primary protection. The contractual indemnity from the seller in Step 2 is your secondary one. Knowing the UDRP response deadline – 20 days from commencement – is your operational floor.

What decides the outcome if a UDRP complaint follows your .store purchase?

A panel assessing a UDRP complaint filed post-acquisition against an incoming buyer applies the same three elements under Paragraph 4(a): confusing similarity, absence of legitimate interest, and bad faith in registration and use. The evidence that decides the outcome is different for a buyer than for an original registrant.

Good-faith acquisition documentation. The purchase agreement, the escrow records, the trademark clearance search you ran in Step 1, and any correspondence showing you evaluated the domain against third-party rights – all of this is direct evidence that your registration is not in bad faith. A buyer who paid a commercial price through a neutral escrow service and ran a trademark search before closing is a materially stronger respondent than one who sent a cryptocurrency payment to a seller's personal wallet with no due diligence.

Intended use of the domain. If you have a business plan, a website in development, or branding materials that predate the complaint, present them. Paragraph 4(c) of the UDRP recognizes legitimate noncommercial or fair use and bona fide offerings as safe harbors. Evidence of actual or planned use – not passive holding – strengthens the legitimate-interest prong significantly.

The seller's prior use. Panels have addressed the question of whether a new registrant can inherit bad faith from a predecessor. The consensus view is that a buyer who had actual or constructive knowledge of the prior bad-faith use, or who paid a price that reflects the domain's value to the complainant rather than its inherent commercial value, may face an adverse inference. This is the exact reason why due diligence in Step 1 is not separable from the escrow structure in Steps 3 and 4. The record you build before closing is the record you may need to defend after closing.

Cross-zone considerations: .store vs. .com and ccTLD acquisitions

Where does .store sit relative to other zones in a domain acquisition?

A buyer acquiring both a .store and a .com variant of the same brand string faces different risk profiles. The .com sits in the original UDRP universe and carries decades of panel precedent. The .store, as a new gTLD, operates under the same UDRP rules but has a shorter dispute history. That shorter history is not a safe harbor – WIPO panels apply the same analytical framework across all gTLDs, treating the TLD as generally irrelevant to the confusing-similarity analysis (the TLD is typically disregarded when comparing the domain to the mark).

If the brand has national trademark registrations in specific jurisdictions but not a US federal registration, the UDRP is still available – the UDRP does not require a US mark. Common-law trademark rights, established through genuine commercial use, can satisfy the first element. The strength of common-law evidence varies, and a prospective buyer assessing a .store domain where the underlying brand rights are common-law only should weigh that uncertainty carefully.

For .de domains, neither the UDRP nor the escrow structure described here applies directly. DENIC (.de) disputes run through the German courts, with a DENIC DISPUTE entry available to block transfer while litigation proceeds. For a .eu domain, the ADR.eu procedure at the Czech Arbitration Court applies, and EU/EEA eligibility is required to hold the registration. A buyer acquiring a portfolio that spans .store, .com, and a national ccTLD such as .de or .eu should treat each zone as a separate legal problem requiring zone-specific diligence. We regularly advise clients on multi-zone acquisitions where the escrow mechanics differ by zone and the due diligence scope must cover each separately.

Related at COGNOMEN

• Domain acquisition, sale, escrow, and brand-protection services across all zones
• Pre-acquisition due diligence for .biz and other new gTLDs: chain-of-title and dispute history
• Case study: defending a UDRP complaint in the .me zone after a legitimate acquisition