Step-by-step: draft a domain assignment agreement for a .org domain

Step-by-step: draft a domain assignment agreement for a .org domain. UDRP and ccTLD domain recovery and defense across .org. Email the firm to assess your case.

A nonprofit closes a deal to acquire a .org it has used informally for years. The handshake is done. Then the registrar asks for a formal transfer authorization — and neither party has a written assignment agreement. The closing stalls, the seller gets cold feet, and the domain sits in limbo.

To draft a domain assignment agreement for a .org domain, you need more than a sale price and a transfer code. The agreement must confirm clean title, address UDRP and prior-dispute history, structure payment through escrow, and satisfy the Public Interest Registry's transfer rules — all before the registrar executes the push. Skipping any step risks acquiring a domain that arrives encumbered, disputed, or subject to a pending complaint.

This guide walks each step in sequence, names the trap inside it, and explains how .org's governing rules shape the deal.

What governs a .org domain assignment — and why it differs from a simple transfer?

A .org domain assignment is a contractual transfer of all rights in a registered domain name from a seller (assignor) to a buyer (assignee), distinct from the registrar-level authorization transfer that actually moves the name in the DNS. The Public Interest Registry (PIR) operates .org, and every registrant is bound by the ICANN-accredited registrar agreement and the UDRP as adopted across all major gTLDs. That means all three UDRP elements — confusing similarity to a mark, no legitimate interest, registration and use in bad faith — can be raised against the new registrant after the transfer if the domain's history is tainted.

Why does that matter at the agreement stage? Because the UDRP treats a new registrant as standing in the shoes of the prior holder for purposes of bad-faith analysis in some panels' reasoning. A buyer who acquires a .org that was the subject of an abusive registration does not automatically inherit a clean slate. The assignment agreement must therefore do two things at once: serve as a binding commercial contract and function as a risk-allocation instrument that protects the assignee if a dispute arises post-transfer.

The assignment agreement is also distinct from a registrar authorization. The registrar only sees the transfer code (EPP auth-info code); it does not verify whether the commercial terms of the deal were met. If the seller provides the code before payment clears, the buyer holds the domain with no contractual leverage. If the buyer pays before receiving the code, the seller holds the money with no obligation to deliver. The written agreement — with escrow — is the only mechanism that closes both gaps simultaneously.

Step 1: Run a chain-of-title and prior-dispute check — this is the trap most buyers miss

Before drafting a single clause, verify that the seller can actually convey clean title. This is the step that buyers most frequently skip, and the consequences appear months later when a third-party trademark owner files a UDRP complaint against the newly registered domain.

The chain-of-title check covers four areas. First, confirm the current registrant of record in the WHOIS/RDDS for the .org domain. The seller's name in RDDS must match the legal entity executing the assignment; discrepancies require an explanation and, often, a corrective registrar-level amendment before closing. Second, search the WIPO case database and the Forum's published decisions for the exact domain and for phonetically similar variants. A prior UDRP complaint — even one that was denied or withdrawn — signals that a trademark owner considered the domain contentious. Third, check ICANN's TMCH (Trademark Clearinghouse) and any pending URS proceedings; a suspended new-gTLD domain cannot be transferred while suspension is active, and a .org under an active UDRP proceeding is subject to a registrar lock that prevents transfer. Fourth, review the registration history through a domain-history service: multiple prior registrants, sudden re-registrations around trademark filing dates, or a gap registration (a drop-and-catch immediately after a prior holder let it expire) all warrant closer diligence.

In a recent matter — a .org acquisition in late 2024 — due-diligence review uncovered a withdrawn UDRP complaint filed two years earlier by a US nonprofit with a federally registered mark. The buyer had already signed a letter of intent. We renegotiated the price downward and added a representation that no further claim had been threatened; the seller's indemnification obligation in the agreement covered any complaint filed within 24 months of closing. That clause cost nothing to draft but would have cost five figures to litigate without.

Step 2: Structure the agreement — the six clauses that decide whether the deal holds

A domain assignment agreement for a .org domain needs six substantive components. Each one closes a specific gap that a generic "bill of sale" leaves open.

Clause 1 — Definitions and subject matter. Identify the domain by the exact string (the full registrar-assigned domain, not a descriptive label), the registrar of record, the registration expiration date, and the IANA-assigned registry (PIR/.org). Include the auth-info code delivery obligation — specifying when it is delivered and to whom — or cross-reference an escrow instruction that governs delivery timing.

Clause 2 — Representations and warranties. The seller warrants: (a) that it is the sole registrant of record; (b) that the domain is not subject to any pending UDRP, URS, or court proceeding; (c) that no UDRP complaint has been filed and remains undecided; (d) that it has not received a cease-and-desist or demand letter regarding the domain within a defined lookback period (commonly 36 months); (e) that the domain is not subject to a registrar lock other than the standard ICANN transfer-out lock; and (f) that the seller has full authority to assign. These representations survive closing — a post-closing UDRP complaint that reveals a pre-closing misrepresentation gives the buyer a contractual claim against the seller.

Clause 3 — Indemnification. The seller indemnifies the buyer for any third-party trademark claim, UDRP complaint, or court action arising from conduct prior to the transfer date. Define "conduct" broadly to include the registration, any prior use (including parked pages, pay-per-click links, or redirects), and any communications with trademark owners. A time cap on indemnification — typically 24 to 36 months, or aligned with the UDRP's lack of a hard statute of limitations — is a common negotiating point.

Clause 4 — Purchase price and payment mechanics. State the price in a specific currency, the payment method, and the escrow provider. For transactions above a nominal threshold, escrow is not optional — it is the mechanism that ensures simultaneous exchange of code and funds. The escrow instruction should specify: release of the auth-info code from escrow to the buyer upon escrow funding; release of funds to the seller upon confirmation that the domain has transferred to the buyer's registrar account; and a return-of-funds trigger if transfer fails within a defined window (commonly 10 business days).

Clause 5 — Transfer mechanics and registrar cooperation. Specify who initiates the registrar-level transfer, which party bears any transfer fee, and the deadline for initiating the transfer after the agreement is signed. Note that the standard ICANN 60-day lock on newly registered or recently transferred domains applies to .org: if the domain was transferred to the seller recently, a new outbound transfer may be locked for 60 days from that prior transfer date. Build a closing condition that confirms no such lock applies — or a deferred closing schedule that accounts for it.

Clause 6 — Governing law and dispute resolution. Choose a governing law matched to the parties' jurisdictions and the nature of the transaction. For cross-border deals, the agreement should specify an arbitration clause or a chosen court, not leave it to implied rules. Note that the UDRP does not resolve disputes between a buyer and seller — it only resolves disputes between a registrant and a trademark owner. A breach-of-warranty claim after a post-transfer UDRP loss belongs in contract law, in whatever court or arbitration the agreement designates.

For an assessment of your domain transaction — including which clauses carry the most risk for your specific .org acquisition — contact info@cognomenlaw.com.

Step 3: Set up escrow — and choose the right escrow structure for a .org deal

Escrow is the settlement layer that makes a domain transaction enforceable in practice. Without it, the assignment agreement is a piece of paper that requires litigation to enforce if the other side does not perform. For a .org acquisition, escrow serves three functions: it holds the purchase price pending successful transfer, it controls the delivery of the auth-info code, and it provides a neutral record of the transaction that can be produced in any subsequent dispute.

The escrow structure for a domain deal differs from real-estate or securities escrow in one key respect: the "delivery" event is the confirmed appearance of the domain in the buyer's registrar account, not the issuance of a transfer confirmation email. Registrar confirmation emails arrive before the WHOIS/RDDS record updates. The escrow instruction should tie fund release to the buyer's independent verification — checking the RDDS record — not to a confirmation from the seller or the registrar.

For .org transactions specifically, the registrar-to-registrar transfer process is governed by ICANN's transfer policy. The receiving registrar sends a transfer request, and the losing registrar has five calendar days to respond (or the transfer proceeds automatically after five days without an explicit denial). The escrow window — the period between code delivery and fund release — must account for this five-day window plus any variation in registrar processing speed. A 10-business-day escrow window is the standard minimum; for high-value or cross-border transactions, 15 business days is common.

We regularly advise buyers who have completed a domain transfer without escrow and then discovered that the domain arrived with a UDRP lock — meaning the prior registrant had initiated a complaint just before the transfer pushed through. In one such situation involving a .org in the nonprofit sector (spring 2025), the registrar froze the domain pending the complaint's resolution before the new registrant could even update the DNS. The assignment agreement had no escrow and no UDRP representation. The buyer had paid in full and held a domain it could not use. Escrow would not have prevented the UDRP complaint, but a warranty clause would have given the buyer a contractual recourse against the seller.

Step 4: Address UDRP exposure — what happens after the transfer if a complaint is filed?

A UDRP complaint can be filed against a .org domain at any point during its registration life. The fact that the domain recently changed hands does not reset the clock or insulate the new registrant from a complaint about the domain's prior use. Panels have held that where a domain was originally registered in bad faith, a subsequent transfer to a new registrant does not cure the bad-faith finding — particularly where the new registrant had constructive or actual notice of a trademark owner's interest.

For the buyer, this means the indemnification clause in the assignment agreement is not merely a formality. It is the only instrument that shifts the cost of defending a post-transfer UDRP complaint — at USD 1,500 or more in WIPO filing fees alone, plus legal fees — from the buyer back to the seller who made the misrepresentation. Without it, the buyer defends the complaint at its own expense and pursues the seller separately under general contract law.

From a defensive posture, the buyer should also prepare a post-transfer UDRP defense file at the time of closing. This means preserving the chain-of-title documents, the due-diligence record, the representations in the assignment agreement, and any evidence of the buyer's own legitimate interest in the .org string — its own trademark registrations, organization name, or longstanding use of the name in commerce. If a UDRP complaint arrives, 20 days to respond is a short window; a buyer who has to reconstruct its own history under time pressure is at a structural disadvantage.

The right route for post-transfer UDRP defense depends on the complaint's theory. If the complaint relies on a trademark that predates the domain's original registration, the buyer's strongest argument is that it is a good-faith acquirer with no notice of the claim — but that argument requires documentary proof. If the complaint relies on post-registration use, the buyer can point to its own use as a bona fide offering or legitimate noncommercial use under Paragraph 4(c) of the Policy. In either case, the assignment agreement's representations are the evidentiary foundation of the defense.

Step 5: Finalize and execute — the closing checklist for a .org assignment

Execution is not just signing. For a .org domain assignment, closing has a specific sequence that the agreement should set out explicitly.

The pre-closing checklist confirms: (a) the domain is not locked for any reason other than standard ICANN transfer-out lock; (b) the WHOIS/RDDS registrant matches the signatory; (c) no active UDRP or URS proceeding is pending; (d) the escrow account is funded and the escrow instruction is countersigned; (e) the auth-info code has been generated within the past 24 hours (codes expire, and a stale code will cause the transfer to fail); and (f) the domain's registration does not expire within 60 days of the transfer date (some registrars will not initiate a transfer for a domain within 60 days of its expiration).

At closing: the auth-info code is delivered to escrow; the buyer's registrar initiates the transfer request; the losing registrar approves the transfer (or the five-day window lapses); the domain appears in the buyer's registrar account; the buyer confirms the RDDS record; and the escrow releases funds to the seller. The assignment agreement should specify that the seller has no further obligation to the registrar once the auth-info code is delivered and the transfer is approved — but that the buyer may require the seller to cooperate with any remedial action if the transfer fails due to a lock that was not disclosed.

Post-closing: the buyer should update the registrant contact information in the registrar's system immediately. Stale WHOIS/RDDS records — showing the prior registrant's contact details after a transfer — create confusion in any subsequent dispute and may cause UDRP complaint notices to be delivered to the wrong party, triggering a default.

Cross-zone considerations: does the .org assignment interact with ccTLD registrations?

A brand owner acquiring a .org often holds or seeks companion registrations — the equivalent .com, or a country-code domain in a key market. The assignment agreement governs only the .org, but the due-diligence phase should map the full domain portfolio picture. If the seller also holds a .com on the same string, that companion domain is a separate asset requiring a separate assignment or a different deal structure. Conflating the two in a single agreement creates ambiguity about which domain is being transferred and at what price.

Where the .org string corresponds to a name that is also registered as a .uk or .eu by the same or a different party, the buyer should assess whether acquiring the .org creates an exposure in those zones. A trademark owner with rights in the EU may file an ADR.eu complaint against the .eu equivalent; a UK rights holder may file a Nominet DRS complaint against the .uk. Neither of those proceedings affects the .org assignment, but they affect the buyer's overall brand position in those markets.

For deals involving a .org and a ccTLD companion, we advise treating each domain as a separate closing with its own assignment agreement, its own escrow, and its own chain-of-title check. The legal tests differ — the Nominet DRS "abusive registration" test applies to .uk, the EURid ADR procedure governs .eu — and a representation that is accurate for the .org may not address the ccTLD's specific procedural requirements. Collapsing multiple zones into one agreement saves drafting time but creates gaps that a well-advised counterparty will exploit.

To weigh UDRP against a court action for your case, or to assess the full portfolio picture across .org and ccTLD zones, email info@cognomenlaw.com.

What evidence decides the outcome if a post-transfer dispute arises?

Whether the dispute is a UDRP complaint filed by a trademark owner or a breach-of-warranty claim by the buyer against the seller, the same body of evidence is decisive: the contemporaneous record of what both parties knew, and when they knew it.

For a UDRP complaint filed against the buyer post-transfer, the panel will examine: the domain's original registration date relative to the complainant's trademark; the domain's use history (parked pages, pay-per-click links, redirects); any communications between the prior registrant and the trademark owner; and the buyer's own evidence of legitimate interest. A buyer who can show a clean due-diligence record, a good-faith acquisition price that reflects the domain's generic or descriptive value rather than its trademark association, and its own pre-existing rights in the string has a strong defense. A buyer who paid a premium that can only be explained by the domain's association with a trademark, and who conducted no diligence, faces a much harder argument.

For a breach-of-warranty claim, the evidence is the assignment agreement itself, the representations made in it, and the correspondence between the parties during negotiation. Emails in which the seller acknowledged awareness of a trademark claim — even informally — are significant. So is the absence of a due-diligence request: a buyer who never asked about prior disputes has a harder time claiming the seller concealed them.

In our practice, we have seen post-transfer disputes resolved quickly where the assignment agreement was thorough and the due-diligence file was preserved intact. Where the agreement was a one-page transfer form with no representations, the same disputes took months to resolve and required external counsel in two jurisdictions.

Related at COGNOMEN

• Domain transactions and pre-acquisition due diligence services at COGNOMEN
• Analysis: domain escrow structures and US transaction mechanics
• Guide to ccTLD transfer remedy procedures and cross-zone considerations