Assess my case

FAQ: draft a domain assignment agreement for a .me domain

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

A .me domain changes hands every day — through private sale, brand acquisition, settlement of a UDRP dispute, or corporate restructuring. The assignment document that records that transfer is the last thing most buyers think about and the first thing that causes problems later. Drafting a sound domain assignment agreement for a .me domain requires understanding both the transactional mechanics and the dispute-history risks that follow the name, not just the money.

A domain assignment agreement for a .me domain is the legal instrument that transfers ownership of the registration from one party to another. Because .me operates under WIPO's dispute-resolution provider framework — meaning the UDRP applies to .me — the agreement must address not only the transfer mechanics at the registrar level but also any unresolved or prior dispute history, chain-of-title representations, and the escrow structure that protects both sides. No registry-specific statute governs the form; the parties and their counsel write it.

The FAQ below covers the full lifecycle: when to draft, who does it, what goes inside, how escrow works, how to verify the domain's dispute history, and what happens if the .me is or becomes the subject of a UDRP proceeding.

When can I draft a domain assignment agreement for a .me domain?

The agreement can be drafted and signed at any point in a private transaction — before or after price negotiation — but it must be executed and held in escrow before any funds move or any transfer of the registrar account is initiated. Timing matters because the .me registry follows the same 60-day inter-registrar transfer lock that governs most gTLD registrations: a domain recently renewed or transferred may be temporarily locked against further transfer at the registry level. Drafting the agreement too late, after the buyer has already moved funds, leaves the buyer exposed if the transfer fails or if a UDRP complaint is filed against the name mid-transaction.

In our practice, we recommend completing the agreement — including all representations on dispute history and chain of title — before the buyer releases any payment. That sequence mirrors the standard escrow structure and eliminates the window in which a bad-faith registrant could pocket funds and then trigger a complication at the registry.

Who can draft a domain assignment agreement for a .me domain?

Either party's counsel can prepare the initial draft, but — because .me operates under the UDRP and any prior-dispute finding travels with the name — a lawyer familiar with domain-name transactions and ccTLD dispute procedures is the right choice. A general commercial solicitor or a corporate M&A associate may produce a technically valid agreement that nevertheless omits the UDRP representations, the RDNH risk allocation, and the chain-of-title warranty that protect the buyer in a domain-specific context.

At COGNOMEN, we handle domain assignment drafting as part of our broader domain transactions practice, which covers pre-acquisition due diligence, escrow coordination, and post-transfer monitoring. We regularly advise buyers who discover after signing a bare-form agreement that the domain they acquired had a prior UDRP proceeding or a disputed chain of ownership — situations that are avoidable with the right representations at the drafting stage.

For an assessment of a .me transaction or to discuss agreement structure, contact info@cognomenlaw.com.

What should a .me domain assignment agreement contain?

The core provisions of a sound domain assignment agreement for a .me domain fall into five groups. First, identification: the domain name in full, the current registrar, the registrant of record as confirmed by WHOIS/RDDS at execution, and the unique registration identifiers. Second, the assignment itself: clear words of transfer (the equivalent of a deed of assignment), confirmation that the transferring party holds full, unencumbered title, and a representation that no third-party rights restrict the transfer. Third, UDRP and dispute-history representations: a warranty that no UDRP complaint is pending, that no prior adverse UDRP decision has been issued against the name, and that the registrant has not engaged in the pattern-of-registration conduct described in Paragraph 4(b) of the Policy. Fourth, the transfer mechanics: the agreed registrar-push or auth-code procedure, the timeline for completing the registrar-level transfer after funds clear escrow, and what happens if the registry rejects or delays the transfer. Fifth, governing law and dispute resolution for the agreement itself — a clause that is distinct from the UDRP, which governs the domain registration, not the private contract between buyer and seller.

Optional but recommended: a holdback or indemnity covering any UDRP or ccTLD challenge filed within a defined period after closing, and a monitoring undertaking requiring the seller to cooperate with any registrar inquiry arising from the transfer.

How do I verify the .me domain's dispute history before signing?

Because .me uses WIPO as its designated dispute-resolution provider, the WIPO domain-dispute database is the primary source for prior case history. A search against the domain name itself will surface any completed UDRP case, including decisions in which the domain was transferred to a prior complainant, cancelled, or the complaint was denied — including any reverse domain name hijacking (RDNH) finding. A clean WIPO result is necessary but not sufficient: you should also search the Forum and CAC databases, check the RDDS/WHOIS record for creation date and any registrar-lock status, and review the domain's web archive for content that could indicate prior bad-faith use.

We address the full due-diligence sequence for ccTLD acquisitions in our chain-of-title verification analysis, which covers how to read a registration history and what red flags in prior content or transfer patterns should trigger a deeper review. A domain with multiple prior ownership changes in a short window, or a gap in public RDDS data attributable to privacy service churn, deserves particular scrutiny.

How should escrow be structured for a .me domain sale?

Escrow for a .me domain transaction follows the same architecture as a .com sale but with one additional consideration: the .me registry's transfer rules may impose a brief hold between the auth-code release and the completed gain of control at the new registrar. The escrow structure should account for that window explicitly.

A standard structure works as follows. The buyer deposits funds with an independent escrow agent. The seller initiates the registrar-level transfer by releasing the auth code and unlocking the domain. The buyer confirms WHOIS/RDDS shows the new registrant of record. The escrow agent then releases funds. If the transfer is not confirmed within an agreed period — typically a defined number of days — funds are returned and the transaction unwinds. The assignment agreement governs all of this; the escrow instruction letter is a schedule to it, not a separate document.

What the escrow arrangement cannot do is protect the buyer from a UDRP filed after closing. That protection comes from the representations and indemnities in the assignment agreement itself.

Does WIPO or a court decide a .me dispute?

.me disputes are decided under the UDRP, administered by WIPO as the registry's designated provider, unless the parties choose court litigation instead — which the UDRP itself preserves as a right for either party. WIPO appoints a panel (one or three members), which applies the standard three-element test of Paragraph 4(a): confusing similarity to a trademark, no legitimate interest, and bad faith in both registration and use. The only remedies a UDRP panel can order are transfer or cancellation. There are no monetary damages, no costs awards, and no injunctions available through the UDRP process itself.

A court in the jurisdiction of the registrant or the complainant may also have authority over the domain, and a court action can reach monetary relief where a UDRP cannot. In practice, the UDRP at WIPO is the dominant route for .me disputes precisely because it is faster, cheaper, and available to complainants worldwide without the complexity of cross-border litigation.

What if the registrant does not respond to a .me UDRP complaint?

If the respondent does not file a response within the 20-day response window, the case proceeds to a panel on the pleadings filed by the complainant. A default does not mean automatic transfer. The panel still examines whether all three UDRP elements are satisfied on the evidence in the complaint. Panels in default cases do, however, typically draw reasonable inferences from the respondent's silence where the complainant's prima facie case is well-constructed.

Default is therefore a risk for both sides. For a complainant, a thin complaint filed on the assumption that default will carry the case can still be denied — and in an egregious case, result in an RDNH finding against the complainant despite the default. For a registrant, failing to respond forfeits the opportunity to establish the safe-harbor defenses of Paragraph 4(c): a bona fide offering, a prior right to the name, or legitimate noncommercial use. We have defended registrants who defaulted in a prior proceeding and then faced the consequences of that lost record.

Can a .me UDRP decision be appealed or challenged?

There is no formal appeal within the UDRP itself. A UDRP panel decision is final as to the administrative proceeding. However, either party may — within 10 business days of notification of the decision — commence a court action in the jurisdiction named in the registration agreement (typically the registrar's jurisdiction) or the jurisdiction of the registrant. If the losing respondent files court proceedings within that window, the registrar will typically suspend implementation of the transfer order pending the court outcome.

In practice, court challenges to UDRP decisions are uncommon. They are expensive relative to the UDRP itself, and courts in most jurisdictions apply a deferential standard to a reasoned panel decision. The more realistic post-decision routes are: a new UDRP complaint on materially changed facts (where the first complaint was denied), a court action for cybersquatting where damages are sought, or — for a respondent who won but faces ongoing harassment — a documented RDNH finding in a subsequent complaint that a panel treats as a pattern of abuse by the complainant.

Related at COGNOMEN

About COGNOMEN

COGNOMEN is an independent boutique focused exclusively on domain-name disputes. We recover, defend, and transact internet domains across generic and country-code zones, before WIPO, the Forum, CAC, ADNDRC, and national procedures, and in court where arbitration cannot reach. We act for brand owners, domain investors, and registrants — including respondent-side defense and reverse domain name hijacking. Our transactions practice covers domain purchase and sale, escrow coordination, chain-of-title due diligence, and portfolio brand-protection monitoring. To discuss a domain, contact info@cognomenlaw.com.

By Cordelia Roe | Domain transactions, due diligence, and brand-protection monitoring

Disclaimer: This article is general information about domain-name dispute procedures and does not constitute legal advice. Outcomes depend on the specific facts, the zone, and panel or court discretion. For advice on your domain, contact info@cognomenlaw.com.

Speak with Cognomen Law

For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter

Related

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.