FAQ: structure escrow for a .xyz domain purchase

FAQ: structure escrow for a .xyz domain purchase. UDRP and ccTLD domain recovery and defense across .xyz. Email the firm to assess your case.

A brand owner or investor eyeing a .xyz domain faces a question that sounds simple but carries real risk: how do you pay for a domain without first losing your money or your leverage? Structuring escrow correctly is the answer – and for .xyz, the mechanics matter more than most buyers expect.

To structure escrow for a .xyz domain purchase, the parties agree on a neutral escrow holder before any funds move, tie the release of payment to confirmed registrar transfer, and run a prior-dispute check against the domain's WHOIS and WIPO history. The .xyz registry operates under standard gTLD rules, which means the UDRP governs disputes and WIPO or the Forum can be the applicable provider. A transaction that skips due diligence risks acquiring a domain with a live complaint, a prior transfer order, or a chain-of-title defect that exposes the new registrant to the same UDRP attack the seller faced.

The questions below address the full cycle: what applies in the .xyz zone, how to check the domain's history, how escrow is structured, what can go wrong, and what to do if a dispute arises before or after closing.

When can I structure escrow for a .xyz domain purchase?

Escrow is appropriate – and advisable – any time a .xyz domain purchase involves a price material enough that either party could suffer a loss if the other defaults. There is no floor. In our practice, we see escrow used on transactions ranging from a few hundred dollars up to five-figure and six-figure acquisitions. The trigger is not price alone; it is the combination of price, the counterparty's identity (known broker vs. anonymous registrant), and whether the domain has a dispute history that might unwind the transfer after funds clear.

Timing matters. Escrow should be arranged before the seller receives any payment and before the buyer initiates a push or transfer-authorization code (auth code) request. The correct sequence is: agree on price and terms, fund the escrow account, receive the auth code from the seller, initiate the registrar transfer, confirm the domain is now in the buyer's account, and only then release funds to the seller. Reversing any of those steps creates exposure. A buyer who pays first and requests the auth code second has no leverage if the seller stalls or disappears.

For .xyz domains specifically, confirm with the escrow provider that the domain is currently unlocked and not subject to a registrar hold, a Redemption Grace Period flag, or a pending UDRP proceeding. A domain mid-complaint cannot be transferred to a third party without the forum's and the registrar's consent – so that check must happen before the escrow is funded, not after.

Who can structure escrow for a .xyz domain purchase for a .xyz domain?

A specialist domain escrow service – one accredited by ICANN or operating under a recognized regulatory framework – is the standard choice for .xyz transactions. Generic payment processors do not understand the mechanics of a registrar transfer; they cannot time fund release to confirmed domain delivery, and they have no protocol for a failed transfer or a post-closing dispute notice.

Legal counsel familiar with domain transactions adds a second layer. We regularly advise buyers and sellers on the due-diligence component that an escrow service alone cannot supply: chain-of-title review, prior UDRP complaint history, trademark clearance against the string, and drafting of a short purchase agreement that governs what happens if a complaint is filed after closing. The escrow provider holds the money; counsel checks whether the domain itself is clean enough to buy at the agreed price.

For larger transactions, the purchase agreement should specify who bears the cost of defending a post-closing UDRP complaint, what constitutes a material defect in title sufficient to void the deal, and whether the seller represents that no complaint is pending or threatened. Those are not questions an escrow platform answers. They require a practitioner who works at the intersection of domain transactions and dispute procedure.

Does WIPO or a court decide a .xyz dispute?

.xyz is a new-gTLD zone that operates under the standard UDRP framework, meaning WIPO and the Forum are both available as dispute-resolution providers, and a complainant may also use the Czech Arbitration Court (CAC) or ADNDRC. A court is not required and is rarely the first resort. The UDRP's filing fee at WIPO starts at USD 1,500 for a single-member panel covering one to five domains, and a standard case is decided within about two months.

Why does this matter to a buyer? Because it means a trademark owner who believes a .xyz domain was registered in bad faith can file a UDRP complaint against whoever holds the registration at the time of the complaint – including a buyer who acquired the domain after the original bad-faith registration. Panels have consistently held that a respondent who acquires a domain with knowledge of an earlier trademark cannot rely on the acquisition itself to reset the bad-faith clock. Buying a tainted domain does not cure the taint.

Court action in the .xyz zone is possible where the UDRP's remedies – transfer or cancellation only, no damages – are insufficient. US anticybersquatting litigation, for example, can reach monetary relief that the UDRP cannot. That path is substantially more expensive and slower; we handle it in coordination with local litigation counsel where the facts justify it. For most .xyz buyers and sellers, the UDRP is the operative risk to assess before closing.

What if the registrant does not respond?

A default – where the respondent fails to file a response within the 20-day response window – does not automatically result in a transfer. The panel still applies all three UDRP elements and must find that the complainant has met each one. In practice, default removes the principal source of rebuttal evidence. Panels in default cases regularly find against respondents on the basis of the complaint record alone, particularly where the domain string is identical to a registered mark and no plausible legitimate use is apparent from the record.

For a buyer considering a .xyz domain, a seller's prior default in a UDRP proceeding is a serious title defect. If a panel issued a transfer order and the domain was transferred to the complainant, the seller has no title to convey to anyone. If the prior case was terminated before a decision – say, the complaint was withdrawn – the risk is different but not eliminated: the trademark owner may refile, and the domain's litigation history is now part of the public record that due diligence will surface.

A domain that survived a prior complaint – where a panel ruled for the respondent – can be acquired with more confidence, provided the basis of that ruling still applies. If the panel found legitimate interest in the seller, the buyer must be prepared to demonstrate its own independent legitimate interest, because the prior finding does not transfer with the domain the way a warranty deed transfers real property.

Can the decision be appealed or challenged?

The UDRP has no formal appeal mechanism within the procedure itself. A party dissatisfied with a UDRP decision may seek de novo review by a court of competent jurisdiction – typically the registrant's jurisdiction or the registrar's jurisdiction – but that requires separate litigation and the UDRP registrar implementation is not automatically stayed pending that challenge. A respondent who loses a UDRP and wants to prevent transfer must move quickly to obtain a court order halting implementation before the registrar acts, which typically happens within a short window after the decision is issued.

For a buyer of a .xyz domain, the practical implication is this: if you acquire a domain that was previously the subject of a UDRP decision favoring a complainant, and that decision was somehow not implemented, you are not insulated. The original complainant may seek enforcement or refile. The escrow structure and purchase agreement should include a representation from the seller that no unsatisfied UDRP order exists against the domain.

A court challenge to a UDRP decision is uncommon and expensive. It is relevant primarily where the respondent has a strong legitimate-interest claim that the panel misweighed. We have defended .xyz registrants in precisely that posture – building the legitimate-interest record, documenting good-faith registration, and where warranted, seeking a finding of reverse domain name hijacking (RDNH) that goes to the complainant's conduct rather than the merits of the underlying mark.

What is the deadline once a case starts?

Once a UDRP complaint commences formally – that is, once the forum accepts the filing and notifies the registrant – the respondent has 20 days to file a response. Missing that window means the case proceeds on the complaint record alone; the respondent has no further right to submit evidence or argument in the standard proceeding. Extensions are available only in limited circumstances and require a showing of good cause to the panel or the forum administrator.

For a buyer who is mid-escrow when a complaint notice arrives, the situation is urgent. The domain is typically locked by the registrar on commencement of the proceeding, which means the transfer needed to close the escrow cannot proceed while the complaint is pending. Escrow funds may need to remain held, the purchase agreement may provide a right to terminate, and the buyer faces a decision about whether to intervene or step back entirely.

This is why we recommend, as a standard matter, running a dispute check at the time of signing a letter of intent and again immediately before releasing escrow funds. A complaint filed the day before closing will not appear in a check done at signing a week earlier. The two-check protocol is a small cost against the risk of funding an escrow on a domain that is already locked by a pending UDRP proceeding.

What chain-of-title checks protect a .xyz buyer?

Due diligence on a .xyz domain acquisition covers at least four areas. First, WHOIS/RDDS history: who has held the registration, how many times has it changed hands, and does any prior holder have a connection to trademark disputes or parking operations associated with the complainant's mark? Second, UDRP complaint history: WIPO and the Forum both maintain publicly searchable case databases. A search on the domain string and on the registrant's known email addresses or proxy accounts will surface prior proceedings. Third, trademark clearance: does the domain string match or closely resemble a registered mark in a class relevant to the buyer's intended use? A buyer who intends to use the domain for commerce in a category where a third-party mark exists is a foreseeable UDRP target. Fourth, registrar status: is the domain active, not in a redemption or pending-delete state, and free of registrar or registry holds that would block transfer?

In a recent transaction matter (a .xyz domain in the technology sector, autumn 2025), we identified a prior WIPO proceeding against an earlier registrant during the chain-of-title review. The complaint had been withdrawn before a decision. We advised the buyer that the withdrawing complainant retained the right to refile, assessed the buyer's own legitimate-interest position, and adjusted the purchase price to reflect the residual risk. The deal closed on modified terms, with a seller indemnity covering any complaint filed within twenty-four months of transfer.

For a read on whether the three UDRP elements are met against a .xyz domain you are considering, or to structure a due-diligence review before a purchase closes, reach us at info@cognomenlaw.com.

How does the escrow mechanics work step by step?

A correctly structured .xyz domain escrow runs in the following sequence. The parties agree on price and execute a short purchase agreement covering title representations, allocation of post-closing dispute risk, and the governing escrow terms. The buyer funds the escrow account with the agreed amount. The seller receives confirmation of funding and then requests the transfer-authorization code (auth code) from the current registrar. The seller delivers the auth code to the escrow agent or directly to the buyer under the escrow agreement's terms. The buyer initiates the registrar transfer using the auth code. The transfer is confirmed – the domain appears in the buyer's registrar account and the registry WHOIS reflects the new registrant. Only then does the escrow agent release funds to the seller.

Variations on this sequence introduce risk. Some sellers request partial payment on delivery of the auth code and the remainder on transfer confirmation. That structure is workable if the purchase agreement is clear, but it gives the seller a partial payment before the buyer has confirmed domain receipt. In our practice, we generally recommend full payment held in escrow until confirmed transfer, with a defined window – typically five to ten business days – for the transfer to complete before the escrow agreement addresses what happens on failure.

For a .xyz domain with a prior dispute history or a trademark-adjacent string, the purchase agreement should also address the scenario where a UDRP complaint is filed after the auth code is delivered but before the registrar transfer completes. A domain mid-transfer is in a technically ambiguous state. Defining which party bears the cost of defending that complaint, and whether the escrow funds are released, held, or returned if the domain is locked by the forum, prevents a dispute between buyer and seller on top of the external dispute with a trademark owner.

To plan the escrow structure for a .xyz transaction and run the pre-acquisition due diligence, contact info@cognomenlaw.com.

Related at COGNOMEN

• Domain transactions, escrow, and pre-acquisition due diligence services
• Case study: escrow and chain-of-title review in a ccTLD domain purchase
• Analysis: choosing between WIPO and the Forum for a gTLD domain dispute