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

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

A developer sells a .dev domain. A startup acquires one in an asset deal. A brand owner consolidates a portfolio and needs clean chain of title across every zone. In each situation, the parties need a written instrument that transfers the domain lawfully, survives registrar scrutiny, and does not hand the buyer a dispute history that resurfaces three years later.

To draft a domain assignment agreement for a .dev domain, you need a written contract that identifies the domain precisely, confirms the assignor holds clear title, transfers all registrant rights at the registry level, and structures payment through escrow so neither party is exposed. Because .dev operates under ICANN's accredited-registrar framework and WIPO administers disputes for the zone, any prior UDRP proceeding against the domain travels with the name until the new registrant establishes an independent record. A well-drafted agreement addresses that history before the transfer executes.

This page covers the governing rules for .dev, the agreement's essential terms, chain-of-title and prior-dispute checks, escrow mechanics, and the practical steps to close the transfer without acquiring someone else's problem.

Why .dev has its own transfer considerations

Google Registry operates .dev as an HSTS-preloaded, sponsored top-level domain restricted to developers and technology uses. That restriction matters for assignment drafting. The assignee must qualify under the registry's eligibility requirements, and the agreement should confirm that eligibility as a condition precedent to closing. If the transferee cannot satisfy the registry's policy at the time of transfer, the push to the new registrant account may fail or be reversed.

Beyond eligibility, .dev domains are subject to ICANN's Uniform Domain-Name Dispute-Resolution Policy. A UDRP complaint can be filed against a .dev registrant just as against a .com registrant. All three elements of Paragraph 4(a) still apply: confusing similarity to a trademark, absence of legitimate interest, and registration and use in bad faith. A UDRP decision transferring or canceling the domain follows the domain, not the registrant. If the seller acquired the name through a prior transfer in a disputed or opaque transaction, the buyer may inherit a chain-of-title problem that a subsequent complainant can use to argue bad faith extends to the new registration.

We advise buyers to treat the .dev zone with the same due-diligence discipline they would apply to a premium .com. The HTTPS-enforcement and developer-community association of .dev give these names genuine commercial value – and that value attracts the same registration disputes that affect the most contested gTLD zones.

What must a domain assignment agreement for a .dev domain contain?

A valid domain assignment agreement has eight core provisions; omitting any one of them creates a gap that registrars, registries, or a future panel may exploit. The provisions below reflect what COGNOMEN structures into every .dev assignment we handle.

• Identification clause. The domain name must be stated in full, including the label and the .dev extension. If the transaction covers multiple related domains, list each separately rather than relying on a defined group term.
• Representations on title. The assignor warrants that it is the registrant of record, that no third-party claim, lien, UDRP complaint, or court action is pending or threatened against the domain, and that the registration is in good standing. If a prior dispute exists, it must be disclosed here – not buried in a schedule.
• Assignment of all rights. The operative clause must convey not just the domain name but all registrant rights, including any goodwill associated with the name and any right to bring or defend a claim arising from use before the closing date. A narrow clause that purports only to "transfer the domain" leaves ownership of ancillary rights ambiguous.
• Registry eligibility confirmation. The assignee confirms eligibility under Google Registry's .dev policies at the date of the agreement and at the date of transfer. This protects the assignor if the transfer is later reversed for the assignee's ineligibility.
• Escrow mechanics. Payment and domain delivery should be simultaneous through a reputable escrow service. The agreement specifies the escrow agent, the release triggers, the inspection period, and the consequence of a failed push.
• Registrar authorization. The assignor agrees to execute whatever authorization codes (EPP/auth codes), registrar-change confirmations, or transfer approval emails the receiving registrar requires. Many failed .dev transfers collapse at this step, not at contract execution.
• Post-transfer WHOIS/RDDS update obligation. The parties agree that the registrant-of-record contact data will be updated within a specified period, typically five business days after the transfer is confirmed. Stale WHOIS data creates risk in any subsequent dispute.
• Governing law and dispute resolution. The agreement should specify the governing law and the forum for contract disputes between the parties. This is separate from any future UDRP proceeding – a UDRP panel decides registrant rights under the Policy, not the contract between buyer and seller.

At this stage in a .dev domain transaction, the buyer faces the most concentrated risk: paying before the push completes, or receiving a name whose prior dispute history is undisclosed. To assess the agreement terms and structure your transaction correctly, contact info@cognomenlaw.com.

How do you verify chain of title and prior dispute history for a .dev domain?

Chain-of-title verification for a .dev domain requires checking four independent sources before any agreement is signed. Skipping this step is the single most common reason buyers later face a UDRP complaint from a trademark owner whose claim pre-dates the transaction.

First, pull the current RDDS (registration data directory services) record – the successor to public WHOIS for domains where registrant data is accessible. Confirm the registrant name matches the seller's identity and that the record shows no registrar lock imposed by a dispute authority. A domain locked pursuant to a pending UDRP or court order cannot be transferred until the lock is released.

Second, search WIPO's online case database for any prior proceeding involving the domain. WIPO publishes decisions publicly; the Forum and CAC also maintain searchable records. A prior UDRP decision that ordered transfer of the domain and was then reversed by the then-registrant through a court action leaves a complex evidentiary footprint. A new buyer inheriting that name may find that a re-filed complaint references the prior decision as evidence of a pattern.

Third, review the domain's historical registration data. Gaps in registration – periods when the domain lapsed and was re-registered – may reset some elements of the factual record but do not erase trademark rights that existed during earlier registration periods.

Fourth, conduct a trademark clearance search to confirm that the domain label does not correspond to a registered or well-known mark. This is not optional for a .dev domain with commercial value. Panels have consistently held that a sophisticated buyer who acquires a domain that is confusingly similar to a well-known trademark without conducting clearance cannot rely on that ignorance as a defense.

In our practice, we run all four checks before advising a buyer to execute any domain assignment agreement. A clean result on all four is the minimum for a standard closing. Where any flag appears, we advise on the residual risk before the buyer commits funds to escrow.

For a detailed discussion of how to verify chain of title before executing a domain transfer, see our guide on verifying chain of title for domain acquisitions.

What escrow structure protects both parties in a .dev transfer?

Escrow is not a formality in a domain assignment. It is the mechanism that ensures neither side bears disproportionate counterparty risk during the gap between payment and confirmed transfer.

A properly structured .dev domain escrow works as follows. The buyer deposits the purchase price with the escrow agent before the transfer process begins. The assignor then initiates the transfer at the registrar level – providing the EPP/auth code and any required confirmation – and the domain moves into the receiving registrar account. The buyer has an agreed inspection period, typically five to seven days, to confirm that the domain resolves correctly, that the registrant-of-record data has been updated, and that no lock or hold has been placed on the name. Once the buyer confirms acceptance, the escrow agent releases funds to the seller. If the transfer fails or the domain arrives with an undisclosed encumbrance, the agreement specifies the remedy – typically a return of funds and a reversal of the transfer if the registry permits it.

Two failure modes recur in .dev transactions we have reviewed. The first is a seller who provides the auth code but delays the registrar-level confirmation, causing the transfer window to lapse. The agreement should specify a maximum number of days for each step and a cure period before the buyer can declare a breach. The second is a domain that clears the push but is then subject to a UDRP complaint filed by a trademark owner who had been monitoring the transaction. The assignee's agreement should include a representation that the assignor had no notice of any threatened claim, and the assignor should be required to cooperate in any subsequent UDRP defense during the period immediately following transfer.

What happens if a UDRP complaint is filed after the assignment closes?

A UDRP complaint filed after a domain assignment closes names the new registrant as the respondent. The prior owner's conduct is relevant evidence, but the panel evaluates the three elements as of the new registration date – or, where the domain has passed through multiple registrations, across the full registration history. This is where chain-of-title defects become expensive.

If the prior owner registered the domain in bad faith – for example, to sell it to a trademark owner at a profit – and the new buyer paid a price that reflects that positioning, panels have found that the new registrant adopted the prior bad faith. The test the consensus view applies is whether the new registrant knew or should have known of the trademark claim at the time of acquisition. A domain assignment agreement that includes accurate representations of title and a clean due-diligence record is the buyer's first line of defense in that analysis.

Conversely, where the assignee can show a genuine, independent legitimate interest in the domain – a development project, a product name, a personal name coincidence – the Paragraph 4(c) safe harbors are available. The agreement itself is evidence: a commercial transaction for a domain with a documented independent purpose looks materially different from a speculative acquisition of a name targeting a known trademark.

In a recent matter (a .dev assignment, spring 2025), we represented a buyer who had acquired a .dev name through an informal transfer without a written agreement. A UDRP complaint followed within four months. We built the legitimate-interest record from the buyer's development history, correspondence with the prior owner, and the commercial context of the transaction. The complaint was denied. The absence of a written agreement made the defense substantially harder than it needed to be – the buyer spent significantly more on the dispute than a properly structured assignment agreement would have cost at the outset.

For situations where a dispute escalates beyond the UDRP to court proceedings, our guide to court action for cybersquatting sets out the anticybersquatting litigation route and when it becomes necessary.

If a UDRP complaint has already been filed against a .dev domain you recently acquired, the response window is 20 days from commencement. To build the legitimate-interest record and assess RDNH potential, reach us at info@cognomenlaw.com.

How does the UDRP versus a court action differ for .dev domain disputes?

Choosing between UDRP arbitration and court action for a .dev domain dispute depends on what the parties want to achieve and what the procedural posture permits.

The UDRP at WIPO or the Forum is the standard route for a complainant seeking transfer or cancellation. The WIPO filing fee starts at USD 1,500 for a single-member panel covering one to five domains. A decision typically arrives within about two months. The remedy is limited: transfer or cancellation only. No monetary damages are available through the UDRP, and no costs award is made against the losing party. For a buyer or seller facing a post-assignment complaint, the UDRP is normally the first proceeding they must manage.

A US anticybersquatting court action is the alternative where the complainant seeks monetary damages in addition to transfer, or where the domain registrant is located in a jurisdiction where US court jurisdiction can be asserted. That route is slower and significantly more expensive than UDRP arbitration. It is warranted when the scale of the harm – lost sales, diverted customers, fraud on third parties – justifies the additional cost and time. For most .dev domain assignment disputes, the UDRP resolves the immediate question of ownership. Court action enters the picture when the contract between assignor and assignee itself is disputed – for example, where the seller refuses to execute the transfer after receiving payment – and that contract dispute requires a court to enforce specific performance or award damages.

The practical decision matrix is straightforward. If the goal is domain transfer or cancellation and the complainant has a clear trademark right, file at WIPO. If the goal is damages or court-enforced contract performance, proceed to litigation with local litigation counsel in the relevant jurisdiction. If both goals apply, a UDRP proceeding and parallel court action can coexist, though WIPO panels will typically suspend or await the court's decision on jurisdiction if asked.

Our domain transactions practice covers both the pre-acquisition agreement stage and the post-transfer dispute stage, so the same team that structures the assignment can manage any subsequent UDRP defense.

What evidence decides the outcome of a .dev domain dispute after an assignment?

In any post-assignment UDRP proceeding, the evidence that determines the outcome falls into three categories: title documents, use evidence, and intent evidence. The assignment agreement itself is often the most important document in the file.

Title documents include the written assignment agreement, any prior transfer history, the escrow record showing the purchase price, and the RDDS records at each point in the chain. A high purchase price paid without a written agreement is the fact pattern panels find most suspicious: it suggests the buyer knew the name had value to a trademark owner and acquired it speculatively.

Use evidence covers what the buyer has done with the domain since acquisition. Active development, a live website, a product tied to the domain label – all of these support a Paragraph 4(c) legitimate-use defense. A domain that resolves to a parking page or to a page offering the name for resale after an assignment is the opposite: it reinforces the complainant's bad-faith argument regardless of what the contract says.

Intent evidence is the most contested category. Panels examine the buyer's background in the domain market, the number of similar domains the buyer holds, whether the domain label targets a specific known brand, and whether the purchase followed the complainant's trademark filing or press coverage. A buyer who holds a portfolio of developer-oriented .dev names and acquires one consistent with that portfolio presents a materially different intent profile from a buyer who acquires a single .dev that matches a recently announced tech product name.

We regularly advise registrants to begin building the legitimate-interest record before any complaint is filed – through documented development activity, internal communications about the domain's planned use, and a clean due-diligence file that shows the trademark check was performed. That record, assembled early, is far easier to present to a panel than a post-complaint reconstruction.

In a second recent matter (a .dev name acquisition, summer 2024), we conducted pre-closing due diligence for a technology company acquiring a short, generic .dev label from an individual registrant. The clearance search identified a pending trademark application from a third party with a plausible claim to the label. We restructured the closing to include a contractual indemnity from the seller covering any UDRP proceeding filed within twelve months of transfer, and we advised the buyer to begin documented development immediately. No complaint followed, and the domain is now in active production use.

The assignment agreement and the due-diligence record together determine how a post-transfer UDRP proceeding is won or lost. Both must be in order before closing, not assembled afterward.

Related at COGNOMEN

• Domain transactions, due diligence, and portfolio brand protection at COGNOMEN
• How to verify chain of title before a domain acquisition
• When to pursue court action for cybersquatting in place of the UDRP