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

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

A corporate restructuring closes, an acquisition settles, or a brand consolidation reaches the point where a .group domain needs to move from one legal entity to another. The domain itself may be worth little on paper. The traffic, the email infrastructure, and the brand equity it carries can be worth far more. Getting the transfer wrong — or skipping a proper assignment agreement — creates a gap in chain of title that surfaces at the worst possible moment: during a UDRP challenge, a due-diligence review, or a follow-on sale.

To draft a domain assignment agreement for a .group domain, you need a document that transfers legal title, confirms no encumbrances, and survives scrutiny under the UDRP — the dispute procedure that governs .group as a new generic top-level domain (new gTLD). The agreement must record the assignor's right to transfer, the assignee's eligibility to hold the domain, the consideration, and any representations about prior-dispute history. It should be paired with escrow, a chain-of-title review, and a registrar-side transfer instruction before the deal is treated as closed.

This page covers the transaction architecture, the legal checks that matter in the .group zone, the escrow structure, and how to avoid acquiring a domain that carries a latent UDRP or URS problem into the new ownership.

What Governs the .group Zone and Why It Matters for a Transfer Agreement

The .group registry operates under ICANN's new-gTLD program, which means the UDRP applies in full — the same three-element test, the same panel remedies (transfer or cancellation), and the same bad-faith framework that govern .com. Additionally, the Uniform Rapid Suspension system (URS) is available to brand owners who need quick suspension of a new-gTLD domain without acquiring it. Both facts shape what a well-drafted assignment agreement must address.

Why does the governing procedure matter to a buyer or transferee? Because a domain can carry a prior dispute into its next ownership. Panels have consistently held that a domain's registration history — including prior UDRP complaints that were filed, withdrawn, or decided — is relevant evidence in any later proceeding. If you acquire a .group name that was previously the subject of a cybersquatting complaint, the new registration is not a clean slate. A transferee who later faces a UDRP complaint will be judged partly on whether the transfer itself was an attempt to launder a bad-faith registration. That is not a theoretical concern: panels have found bad faith where a domain changed hands shortly before a complaint was filed, particularly where the new registrant could not demonstrate independent legitimate interest.

The assignment agreement is the instrument that creates, or fails to create, a defensible paper trail. Drafted properly, it records bona fide consideration, the parties' identities, the transfer date, and the representations each side makes about title and prior use. Drafted carelessly — or not at all, relying only on a registrar push-transfer — it leaves the new owner exposed.

What Does a .group Domain Assignment Agreement Need to Contain?

A domain assignment agreement for a .group domain is a short-form commercial contract with five mandatory components and several domain-specific representations that standard commercial assignment templates omit entirely.

The five mandatory components are: (1) identification of the domain name in full, including the .group extension; (2) identification of the assignor and assignee with full legal names and, where applicable, corporate registration details; (3) the consideration — a specific monetary amount, or "nominal consideration" if the transfer is intra-group, but never left blank; (4) the effective date of transfer, which must be reconcilable with the registrar's WHOIS or RDDS record of the actual registrant change; and (5) the governing law and dispute-resolution clause, which should specify a jurisdiction whose courts the assignee can reach and, where relevant, agree that UDRP is the primary route for any third-party challenge rather than a clause that purports to exclude it.

The domain-specific representations are where most template agreements fail. The assignor must warrant: that it is the current registrant of record, that it has the right and authority to assign, that no UDRP or URS proceeding is pending or has been filed and withdrawn in the twelve months preceding the transfer, that no cease-and-desist or demand letter relating to the domain is outstanding, and that the domain has not been subject to a registrar lock or ICANN dispute other than the standard administrative lock that accompanies all registrar-to-registrar transfers. The assignee should represent that it holds (or intends to hold) a legitimate interest in the name — typically the trademark, business name, or organizational purpose that corresponds to the .group label — and that to its knowledge the acquisition does not infringe any third party's rights.

In our practice, we regularly see intra-group domain transfers executed with nothing more than a one-line board resolution and a registrar push. That is almost always sufficient for the internal accounting, but it is not sufficient if a trademark owner later challenges the domain under the UDRP and the assignee needs to demonstrate that the transfer was commercially genuine and preceded by independent due diligence.

To weigh the agreement structure for your specific .group transfer, email info@cognomenlaw.com.

How Do You Run a Chain-of-Title Check Before Executing the Agreement?

A chain-of-title check for a .group domain has four components: WHOIS/RDDS history, prior-dispute history, trademark clearinghouse interaction at registration, and registrar-record consistency.

WHOIS and RDDS records for .group domains are subject to ICANN's privacy and redaction rules, which means the current published record may not show the original registrant's identity if privacy service was applied. A buyer must request, as a condition of signing the assignment agreement, full disclosure of the registrant history — particularly any change in registrant that occurred within the preceding twenty-four months. A domain that has changed hands multiple times in a short period without a clear commercial rationale is a risk signal, regardless of what the current published record shows.

Prior-dispute history should be searched at WIPO and the Forum, both of which maintain publicly searchable databases of filed UDRP cases. A search by domain name will return any filed complaint, including those withdrawn before a decision. A withdrawal before decision does not mean the domain is clean: it may mean the prior registrant transferred the name to a third party to moot the proceeding, which is precisely the scenario that panels scrutinize when a new-registrant respondent later claims good faith.

The Trademark Clearinghouse (TMCH) interaction is relevant because new-gTLD registries including .group were required under ICANN's new-gTLD program to implement Sunrise and Claims periods at launch. A domain registered during a Claims period, where the registrant received and acknowledged a TMCH notice about a matching trademark, carries a record of that notice. The assignment agreement should ask the assignor to confirm whether a Claims notice was acknowledged at registration — and if so, the original registrant's basis for proceeding despite the notice.

Registrar-record consistency is the final check. The registrar's internal records of the named registrant, the registration date, and the expiry date must match the WHOIS/RDDS output and the assignment agreement's representations. Discrepancies — a registration date that predates the assignor's corporate existence, for example — create doubt about which entity actually holds title. We have encountered situations where a domain had been renewed in the name of a dissolved entity for several years, creating a title defect that required formal registrar escalation to correct before the assignment could proceed.

How Should Escrow Be Structured for a .group Transfer?

Escrow for a domain transfer serves two purposes that are easily confused: it protects the buyer's funds pending successful transfer, and it creates a contemporaneous record of the deal's commercial reality that can be produced in a later UDRP proceeding to demonstrate bona fide acquisition.

The mechanics for a .group domain transfer are the same as for any new gTLD. The registrar processes the transfer using ICANN's registrant change (RGP) procedures. The buyer deposits the agreed purchase price with a domain-specialized escrow provider. The escrow release is triggered by a confirmed registrant-of-record change in the WHOIS/RDDS record — not by the assignor's confirmation that the push was sent, but by verified change of the named registrant. The agreement should specify the number of business days within which the registrar must complete the change, and provide for automatic release or automatic reversal if the change does not occur within that window.

For intra-group transfers where the consideration is nominal, a formal escrow is often omitted. That is usually appropriate, but the assignment agreement should still document the nominal consideration explicitly and should be executed as a deed (or equivalent formality in the governing jurisdiction) to ensure enforceability without a commercial exchange. The contemporaneous-record function of escrow — demonstrating that the transfer was genuine and not a sham to defeat a pending complaint — can be served by a board resolution, an intercompany services agreement, or a transfer pricing ledger entry, provided those documents are dated consistently with the transfer date in the WHOIS/RDDS record.

In one recent matter (an intra-group .group transfer, spring 2025), a client's restructuring moved approximately a dozen branded new-gTLD domains between two subsidiary entities in connection with a brand consolidation. No escrow was used, but we prepared a group-wide assignment deed, verified each domain's prior-dispute record, and documented the WHOIS change date against the deed date. When a trademark challenge to one of the transferred domains arose several months later, the assignment deed, the board resolution, and the registrar-confirmed change date were produced together — providing a defensible paper trail that supported the subsidiary's legitimate-interest claim.

For an assessment of your domain dispute or transfer structure, contact info@cognomenlaw.com.

What Evidence Decides Whether a Transfer Survives a UDRP Challenge?

If a trademark owner challenges a .group domain after an assignment, the panel will apply all three UDRP elements of Paragraph 4(a) to the new registrant as respondent. The transfer date is not itself a defense. What matters is whether the assignee can demonstrate a legitimate interest in the name that is independent of the assignor's history — and whether the registration, viewed as a whole, was made in bad faith.

The evidence that most often saves a transferee respondent is: proof that the assignee held a trademark, business name registration, or demonstrated commercial use in the relevant term before the transfer; the assignment agreement itself, showing consideration and a business rationale; the chain-of-title record, showing no prior disputed use; and correspondence or registrar records showing the transfer was conducted through normal commercial channels rather than at arm's length from a known bad-faith holder.

The evidence that most often defeats a transferee is: a short interval between the prior registrant's receipt of a demand letter and the transfer; consideration that is implausibly low given the domain's apparent value; the absence of any legitimate-interest documentation by the transferee; and a pattern of similar transfers across related domains that suggests a deliberate strategy of recycling names to defeat trademark owners.

Paragraph 4(b) of the UDRP lists four non-exhaustive indicators of bad faith. Panels applying those factors to post-transfer registrants have generally focused on whether the transfer was commercially genuine — that is, whether the assignee was simply the next holder of a bad-faith registration or a genuinely independent acquirer with its own legitimate interest. The assignment agreement is the primary document through which that distinction is made. A document that records the parties, the date, the consideration, and the assignee's representations of legitimate interest is not a guarantee of success. But the absence of that document — or a document that is generic, undated, or inconsistent with the registrar record — will be read against the respondent.

The URS adds a further dimension specific to new gTLDs including .group. A URS complainant must meet a higher "clear and convincing" standard, and the remedy is suspension rather than transfer. But a URS suspension of a domain held by an assignee who cannot produce clean title documentation will damage the assignee's ability to resist a follow-on UDRP complaint, because the suspension record becomes part of the domain's dispute history.

When Does a .group Transfer Require Court Action Instead?

Most .group domain transfers are consensual — the parties agree, the contract is executed, and the registrar processes the change. Court action becomes relevant in three situations: the assignor refuses to complete the agreed transfer, a third party claims title to the domain and files an injunction to block the transfer, or a UDRP complaint is filed between signing and completion of the registrar change.

The right route depends on the zone and the goal. If the dispute is between the contracting parties — the assignor is refusing to release the domain despite receiving payment — a breach-of-contract claim in the governing-law court is the direct remedy. The UDRP does not resolve contract disputes between the buyer and seller; it resolves disputes between a trademark owner and a registrant. A buyer who paid for a .group domain and did not receive it cannot file a UDRP complaint against the seller. The court route, with an application for specific performance or interim injunction, is the mechanism. COGNOMEN coordinates that work with local litigation counsel in the relevant jurisdiction.

If a trademark owner files a UDRP complaint after signing but before the registrar change is recorded, the proceeding will name the registrant of record at the time of filing — typically the assignor. The assignee's interest in the domain may not be formally recognized by the panel, but it is directly affected by the outcome. Both parties should be notified immediately, and the response strategy should be coordinated between assignor and assignee. In a competitive bid situation (a second matter, autumn 2024), we were engaged mid-transfer when a .group domain sale was interrupted by a UDRP filing from a trademark holder. The assignor remained the named respondent; we coordinated the defense record across both parties and ultimately the transfer completed after the complaint was denied on legitimate-interest grounds, with the contemporaneous sale documentation serving as evidence of the bona fide commercial chain.

How Does This Compare to a .com or .uk Transfer?

The core assignment agreement structure — identification, consideration, representations, governing law — is the same across gTLD zones. The procedure-specific differences matter at the margins and in the risk profile.

A .com transfer is governed by the UDRP at WIPO or the Forum, with a filing fee starting at USD 1,500 for a single-member panel and a typical resolution timeline of about two months. The .com zone has the deepest panel precedent, the most predictable outcomes, and the highest volume of prior-dispute history to search. An assignment agreement for a .com domain that does not address prior-dispute history is omitting the single most consequential piece of due diligence.

A .group transfer faces the same UDRP rules but benefits from a shorter history of prior cases — fewer disputes have been filed over .group names than over .com names, which means less legacy history to search but also less panel precedent to predict how a given fact pattern will be decided. The TMCH interaction at registration is a .group-specific feature with no equivalent in the .com legacy zone. And the URS suspension risk — absent from .com — adds an additional enforcement exposure specific to new gTLDs.

A .uk transfer is governed by the Nominet DRS, a distinct procedure with a free mediation stage, a different legal test ("abusive registration" rather than "registered and used in bad faith"), and fees denominated in GBP rather than USD. A domain assignment agreement for a .uk name should be reviewed against the Nominet DRS rules and any applicable Nominet registrant eligibility requirements — particularly where the transferee is a non-UK entity seeking to hold a .uk domain. Chain-of-title checks for .uk names require searching the Nominet DRS public database rather than WIPO or the Forum.

For a brand owner managing transfers across multiple zones simultaneously — a .com, a .group, and a .uk as part of a single consolidation — the due-diligence structure must be adapted zone by zone. The assignment agreement can be a single instrument covering all named domains, but the representations, the escrow trigger, and the prior-dispute searches must address each zone's specific procedure.

Related at COGNOMEN

• Domain transactions, purchase, sale, escrow, and pre-acquisition due diligence
• Verify chain of title before acquiring a domain: what to check and why it matters
• URS versus UDRP: choosing the right procedure for a new-gTLD domain dispute