Establishing secure connection…Loading editor…Preparing document…

Domain Name Assignment Agreement

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!
Domain Name Assignment Agreement

What a Domain Name Assignment Agreement Covers

A Domain Name Assignment Agreement is a legal contract that transfers ownership and all associated rights in one or more internet domain names from the assignor (current registrant) to the assignee (new owner). The agreement documents consideration, the list of domains being transferred, representations about registrant authority and no conflicting claims, and the steps each party will take to complete the registrar-level transfer. Typical elements include authorization codes (EPP), a timeline for registrar actions, WHOIS updates, warranties against infringement, and any escrow or payment terms tied to the transfer.

Why documenting a domain transfer matters

A written assignment creates clear evidence of intent, allocates risk, and records the technical and contractual steps needed to move a domain between registrars or registrants. Proper documentation reduces disputes about ownership, simplifies WHOIS changes, and supports later enforcement of IP or contract rights.

Why documenting a domain transfer matters

Who commonly prepares or signs a Domain Name Assignment Agreement

Users include parties selling or assigning a domain, counsel, brokers, and in-house IP or asset managers who must document a transfer of registrant rights.

  • Domain sellers and buyers: Parties to a sale who need clear transfer terms and payment conditions.
  • Corporate legal teams: In-house counsel handling IP transfers, diligence, and post-closing WHOIS updates.
  • Law firms and brokers: Advisors preparing assignment language, escrow terms, and verifying clear title.

The agreement is useful across transactions from individual sales to portfolio transfers and should match the complexity of the deal and the registrars involved.

Core provisions to include in a professional assignment

A comprehensive Domain Name Assignment Agreement addresses identity, scope of transfer, consideration, technical steps, representations and warranties, and dispute resolution to create a clear legal and operational record.

Parties

Full legal names and contact details for assignor and assignee, and entity capacity (individual, LLC, corporation).

Domain List

Exact domain names (including TLDs) and any related subdomains or variants to be transferred as part of the agreement.

Consideration

Monetary amount or other value exchanged, payment schedule, escrow instructions, and conditions for release.

Registrar Actions

Technical steps, authorization/EPP codes, registrar account access, and timing to effect the registrant/WHOIS change.

Warranties

Assignor representations about ownership, absence of liens or disputes, and authority to transfer the domains.

Post-Transfer Steps

WHOIS updates, DNS delegation timing, privacy-service removal, and obligations for cooperation after closing.

Required details commonly captured in the agreement

Assignor Name: Full legal name of current registrant.
Assignee Name: Full legal name of new owner.
Domain(s): Exact domain names including TLDs.
Registrar Info: Registrar name and account identifiers.
Authorization Code: EPP/Auth code or transfer token.
Effective Date: Date obligations begin.

Step-by-step: completing a Domain Name Assignment Agreement

Follow these core steps to prepare, execute, and effect a domain transfer while minimizing operational risk.

  • 01
    Draft terms: List parties, domains, consideration, and timelines clearly.
  • 02
    Obtain auth codes: Assignor retrieves EPP/authorization codes from the registrar.
  • 03
    Sign agreement: Both parties sign and date the assignment document.
  • 04
    Execute transfer: Initiate registrar transfer and update WHOIS on completion.

Customizing the assignment for online completion

When preparing an online or e-signed assignment, configure fields and authentication to match the transaction’s risk profile.

Field Configuration
Domain field Mandatory, textbox with validation
EPP code field Password-style field, required
Consideration field Numeric or text, conditionally required
Signature block Signer name, date, and role fields

Where to send or file the signed agreement

After signatures, distribute executed copies to the registrar, escrow agent if used, legal counsel, and each party for their records.

  • To the Registrar: Provide executed assignment and EPP code where required.
  • To the Assignee: Deliver fully signed copy for account setup.
  • To Escrow: Send closing docs if funds or assets are escrowed.
  • To Counsel: Share for IP clearance and recordkeeping.

Digital signing and technical delivery considerations

Use an e-signature platform that supports audit trails, secure storage, and conditional fields to capture transfer-critical data.

  • Audit Trail: Capture timestamps and IP addresses
  • File Formats: PDF and DOCX supported
  • Integrations: Salesforce, NetSuite, Google Workspace

Platforms with registrar and CRM integrations streamline coordination and record retention; ensure the vendor can meet any industry-specific compliance needs before use.

Typical timelines and processing expectations

Timelines depend on registrar procedures, parties’ responsiveness, and any required authentication or escrow steps.

Effective Date:

Date recorded in agreement when obligations begin.

Authorization Retrieval:

Assignor should request EPP codes promptly to avoid expiry.

Registrar Processing:

Registrar may take several days to complete transfer.

WHOIS Update:

WHOIS may update after registrar confirms transfer.

Payment Release:

Escrow or payment release follows agreed closing conditions.

Common mistakes to avoid when preparing the agreement

  • Using informal or incomplete domain descriptions, such as omitting the top-level domain, which can cause ambiguity and transfer failures.
  • Failing to obtain or verify the correct EPP/authorization code before signing, resulting in delays or failed transfers.
  • Neglecting to specify who pays registrar or transfer fees, leaving parties to dispute payment after closing.
  • Overlooking reputational or trademark claims in advance, which can trigger registrar or UDRP disputes post-transfer.

Risks and legal consequences of incorrect or incomplete assignments

Failed Transfer: Registrar rejection or delay
Title Disputes: Third-party claims may arise
Payment Disputes: Escrow or release conflicts
Trademark Exposure: Infringement claims risk liability
WHOIS Errors: Incorrect records harm enforcement
Tax Reporting: Unreported consideration may trigger tax issues

eSignature vendor comparison for executing Domain Name Assignment Agreements

Compare baseline pricing and common features across major eSignature vendors; signNow is listed first per vendor comparison conventions.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes (Business Premium) Varies by plan Varies by plan Varies by plan Varies by plan
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA available) Yes (BAA available) Yes (BAA available) Varies Varies

Frequently asked questions about Domain Name Assignment Agreements

Answers to common questions on signatures, notarization, registrar actions, revocation, and post-transfer obligations.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users