How to draft a domain assignment agreement for a .shop domain

How to draft a domain assignment agreement for a .shop domain. UDRP and ccTLD domain recovery and defense across .shop. Email the firm to assess your case.

A .shop domain changes hands on a handshake every day. The transfer completes at the registry. The dispute arrives six months later, when the seller surfaces a prior UDRP complaint, a competing trademark claim, or a lien the buyer never knew existed. Drafting a clean assignment agreement before the transfer closes is the only way to shift that risk to the party in the best position to know it.

To draft a domain assignment agreement for a .shop domain, you need a document that does four things: confirms clean title in the assignor, specifies the exact domain string and the registry (GMO Registry, which operates .shop under a WIPO-administered dispute procedure), sets out escrow mechanics for simultaneous payment and transfer, and includes representations covering prior disputes, trademark conflicts, and registration-history gaps. The WIPO filing fee for a .shop UDRP complaint starts at USD 1,500 for a single-member panel. An assignment agreement that triggers none of those facts is worth more than the domain itself.

This page sets out what the agreement must cover, how chain-of-title due diligence works for .shop, and where an improperly drafted transfer can expose a buyer to a UDRP complaint they did not expect to inherit.

Why .shop is different from a standard .com assignment

The .shop zone is a new gTLD administered by GMO Registry. It operates under the UDRP – the same Uniform Domain Name Dispute Resolution Policy that governs .com and .net – and WIPO is the most active provider for disputes in this zone. That means a buyer who acquires a .shop domain tainted by bad-faith registration history acquires the dispute too. The original registrant's conduct travels with the domain string.

Why does that matter for drafting? Because the UDRP asks whether the domain was registered and is being used in bad faith – Paragraph 4(a)(iii) of the Policy. Panels have consistently held that a transfer to a new registrant can restart the analysis only if the acquisition itself was genuinely independent of the original bad-faith act. A buyer who pays for a domain without due diligence, then receives a UDRP complaint, cannot rely on their own good faith alone if the registration history shows the original purpose was abusive.

In our practice, we regularly review .shop assignments where the buyer assumed a clean slate. The assumption is not always right. A domain assignment agreement that captures the right representations and warranties converts a future dispute into a contractual claim against the seller. That is a far better position than defending a UDRP alone.

To assess the chain-of-title risk on a .shop domain you are acquiring, or to review a draft assignment agreement before the transfer completes, contact info@cognomenlaw.com.

What should a .shop domain assignment agreement contain?

A well-drafted .shop domain assignment agreement is a short, precise commercial document. It is not a license. It is not an asset purchase agreement covering a whole business. Its purpose is to transfer the registration record cleanly, allocate risk, and create a paper trail that survives a WHOIS/RDDS audit or a panel review.

The core clauses are:

• Identification of the domain. The exact second-level label plus the .shop TLD, the registrar of record at signing, and the registrant account details. Never describe the domain by intent or by a common name alone.
• Representations on title. The assignor warrants that it is the sole registrant of record, that no third party holds a lien, security interest, court order, or registrar lock on the domain, and that no UDRP, URS, or other dispute proceeding is pending or has been threatened in writing.
• Representations on dispute history. A look-back clause requiring the assignor to disclose any prior UDRP complaint, URS filing, Uniform Rapid Suspension proceeding, or arbitration demand relating to the domain, whether resolved or withdrawn. A resolved complaint that ended in a transfer is a red flag – the domain may carry a pattern of conduct that a new complaint can use under Paragraph 4(b)(ii) of the UDRP.
• Trademark-conflict representation. The assignor represents that it is not aware of any registered trademark that is identical or confusingly similar to the domain string and that was the basis of a prior demand, whether formal or informal. This shifts the risk of undisclosed claims to the party who registered in the first place.
• Escrow mechanics. Payment and transfer should be simultaneous. The agreement should name the escrow service, specify the release conditions, and set a deadline for initiating the registrar push or authorization-code transfer. Specifying the registrar-change process for .shop is important: the registry lock status, any redemption-grace-period issue, and the expiration date of the registration should all be confirmed before escrow opens.
• Assignee's UDRP assumption clause. The assignee takes the domain as-is for purposes of the registry and the UDRP, but the agreement should make clear that any cost, loss, or liability arising from a UDRP or URS complaint filed after the transfer date that is based on conduct predating the transfer remains the assignor's contractual responsibility.
• Governing law and dispute resolution. Choose a jurisdiction with a clear commercial-contract body of law. The contract dispute is separate from any UDRP or registry proceeding; an arbitration clause for contract disputes is common but should be carefully drafted to avoid confusion with the UDRP procedure.
• Completion mechanics. A step-by-step completion schedule: escrow funding → assignor initiates registry transfer → registrar sends authorization code → assignee accepts → registrar confirms new registrant of record → escrow releases funds. Each step should have a deadline and a default remedy.

How does chain-of-title due diligence work for .shop?

Chain-of-title due diligence for a .shop domain means reconstructing the registration history before you sign. It is the single most important pre-signing step and the one most often skipped in private sales.

Start with the current WHOIS/RDDS record. Confirm the registrant of record matches the person signing the assignment. Discrepancies between the named registrant and the contracting party are surprisingly common in brokered sales; they indicate either a name change, a prior undisclosed transfer, or a registration under a proxy service. Each requires a specific cure before closing.

Next, check the public UDRP case databases. WIPO's online case search is a public record. Search the domain string exactly. Search also for variant strings – common typosquats of the same mark – if the domain you are buying is itself a descriptive .shop registration that a brand owner might challenge. A prior UDRP complaint that was withdrawn or settled is visible in the public record and is not a clean result; it tells you a complainant had enough of a case to file.

Third, examine the domain's content history. Publicly available web-archive tools allow you to see what the domain resolved to across time. A .shop domain that previously resolved to a pay-per-click parking page featuring a competitor's brand is exactly the fact pattern Paragraph 4(b)(iv) of the UDRP addresses: using a domain to attract users for commercial gain by creating confusion with a mark. A buyer who acquires that history without a contractual backstop from the seller is accepting residual risk.

Fourth, run a trademark search. The key question is whether any registered trademark – particularly a word mark in the same goods or services class as the .shop label – is identical or confusingly similar to the domain string. This step cannot be delegated to the assignor's representations alone. A credible due diligence memo should include the search results as an exhibit to the assignment agreement.

In a recent matter – a .shop domain acquisition, spring 2025 – we identified a prior UDRP complaint against the same domain string that had been administratively closed without a decision. The seller had not disclosed it. The clause we inserted required the seller to indemnify the buyer for any future complaint based on conduct predating the transfer date. The deal closed; the complaint did not arrive. But the clause was the protection, not the luck.

If you are acquiring a .shop domain and need a pre-acquisition due diligence review and a compliant assignment agreement, email info@cognomenlaw.com.

What escrow structure is appropriate for a .shop transfer?

Escrow is not optional for any .shop domain sale above a nominal amount. The risk without it is asymmetric: the buyer wires funds, the seller delays the registry push, and by the time the transfer window closes the relationship has deteriorated. A robust escrow structure makes the payment and the domain change simultaneously – or neither does.

The assignment agreement should specify the escrow provider by name, the currency, the exact amount, the release conditions, and the timeline. For .shop domain transfers, the registrar push or authorization-code mechanism is standard. The agreement should specify which method applies, which party initiates it, and the deadline for each step.

Three structural points matter for .shop specifically. First, confirm the domain is not in a transfer-lock period. A domain recently transferred or recently renewed may be locked by the registrar for a set period; attempting to transfer during that window will fail at the registry level, and an imprecise assignment agreement may leave the parties arguing about who bears the resulting delay. Second, confirm the expiration date is at least 60 days out. A domain expiring within days of the transfer is a material risk; the assignment agreement should include a pre-closing renewal obligation on the assignor if the expiration is imminent. Third, confirm there is no pending registrar dispute, UDRP action, or registry lock. A locked domain cannot be transferred; discovering a registrar-initiated lock at completion is a common deal-breaker that a pre-closing checklist prevents.

We structure escrow mechanics in .shop assignments to close in a defined sequence: escrow funded by buyer → assignor pushes transfer → buyer accepts at new registrar → new registrar confirms → escrow releases. Deviation from sequence triggers escrow hold and a defined remedy period. That sequence, written precisely into the agreement, is the difference between a smooth closing and a contested transfer.

What happens if the .shop domain carries a prior dispute?

A prior UDRP complaint that ended in a transfer order means the domain was once taken from someone for bad-faith registration. That history is public. It does not necessarily prevent a subsequent legitimate use, but it creates a factual context that any future complainant will use.

A prior complaint that was denied – where a panel found the registrant had legitimate rights – is a different fact pattern. The UDRP decision is public, and the reasoning in the denial may actually support the current registrant's position if a new complaint is filed. In that case, the assignment agreement should reference the prior decision, attach it as an exhibit, and include a warranty from the assignor confirming the domain's continued registration is consistent with the legitimate-interest finding.

A prior URS suspension – the Uniform Rapid Suspension procedure for new gTLDs including .shop – is the most serious prior-dispute flag. A URS suspension requires a "clear and convincing" showing of bad faith, a higher threshold than the UDRP. If a .shop domain was previously suspended under the URS, its commercial value may be severely impaired. That prior suspension may recur if the domain string remains associated with the abusive-registration record, regardless of who now holds it. We advise clients not to acquire .shop domains with a prior URS suspension without a detailed factual analysis of the specific grounds and the registrant's current use plan.

In a second matter – a .shop domain with a prior URS suspension, summer 2025 – a prospective buyer sought our review before closing. The prior suspension had been based on a well-known word mark in the retail sector. The buyer's intended use was in an entirely different category. We assessed the risk, structured the representations, and documented the legitimate use case in a pre-acquisition memo attached to the assignment agreement. That memo would have formed the basis of a Paragraph 4(c) defense had a new complaint followed. It did not need to; the factual record was clean enough to deter a filing.

How does the UDRP apply to .shop domains, and what does a buyer inherit?

The UDRP applies to .shop through the registry agreement between GMO Registry and ICANN. Every .shop registrant agrees to the Policy as a condition of registration. When you acquire a .shop domain by assignment, you step into that registrant role. You do not inherit the prior registrant's intent – but you do inherit the domain string, and any complainant with trademark rights can file against you for your own registration and use.

The three UDRP elements a complainant must prove under Paragraph 4(a) are: (1) the domain is identical or confusingly similar to a mark in which the complainant has rights; (2) the registrant – now you – has no rights or legitimate interests; (3) the domain was registered and is being used in bad faith. For a buyer who acquired in good faith and is using the domain for a legitimate commercial purpose, elements (2) and (3) should be defensible. The Paragraph 4(c) safe harbors are available: bona fide offering before notice of the dispute, being commonly known by the name, or legitimate noncommercial or fair use.

What the assignment agreement cannot do is retroactively cure a domain registered originally in bad faith and subsequently transferred to defeat a UDRP complaint. Panels have consistently scrutinized transfers made after a demand letter or after a UDRP threat. If the assignment itself was designed to obstruct a legitimate complaint, the panel may look through the transfer and treat the original bad-faith registration as continuing. This is why the timing of the assignment agreement matters as much as its content: a transfer made before any dispute arises, for legitimate consideration, supported by credible due diligence, is treated very differently from a transfer made after a lawyer's letter arrives.

What is the cost structure for a .shop domain assignment?

The cost of a .shop domain assignment has two components: the transaction cost and the dispute-risk cost. The transaction cost is straightforward: the domain price (negotiated between the parties), the escrow fee (typically a percentage of the transaction value charged by the escrow provider), and legal fees for drafting and due diligence.

Legal fees for a .shop domain assignment agreement with a full chain-of-title due diligence review are typically in the range the market describes for domain transaction work: modest for a clean, single-domain assignment; higher where the domain has a dispute history, multiple prior registrants, or a complex trademark landscape. We provide clear fee ranges before engagement, not billing surprises after the transfer closes.

The dispute-risk cost is harder to quantify but easy to frame. If you acquire a .shop domain without due diligence and a UDRP complaint follows, the legal cost of a defense runs in a range comparable to the complaint cost – legal fees commonly in the USD 3,000–7,000 range for a single-domain defense, separate from any WIPO filing fees. The WIPO filing fee for a three-member panel in a .shop case is USD 4,000, which you would share if the complainant requested a single-member panel and you exercised your right to upgrade under the Rules.

The right framing is simple: invest in the assignment agreement before closing, or invest in the UDRP defense after. The former is reliably cheaper. The latter is uncertain in outcome.

The right route depends on the situation. If the domain has a clean registration history and no trademark conflict, a standard assignment agreement with representations and escrow will close the deal efficiently. If the domain has a prior UDRP complaint, a URS history, or a complicated WHOIS record, the due diligence step comes before the agreement, not after. If the domain is already the subject of a dispute – a UDRP filed, a demand letter in hand, a registrar lock in place – the assignment cannot proceed without first resolving or staying the dispute. In that case, the choice is between defending the UDRP, negotiating a settlement that transfers the domain as part of the resolution, or exercising the Paragraph 4(b)(iii) defense against a complaint designed to force a sale at undervalue. Each path has a different cost structure, timeline, and risk profile. We advise on all three.

Related at COGNOMEN

• Domain transactions, due diligence, and portfolio brand-protection services
• Brand-protection monitoring for domain portfolios across gTLD and ccTLD zones
• How to request a three-member UDRP panel and when the upgrade is worth the cost