Can a Domain Transfer Agreement be e-signed?

Yes. Electronic signatures are enforceable under the federal ESIGN Act (15 U.S.C. §7001) and nearly all states' UETA statutes. For consumer-facing records, meet ESIGN consumer disclosure requirements (15 U.S.C. §7001(c)).

Who must sign the agreement?

An authorized registrant or corporate officer must sign; for entities, attach a corporate resolution or proof of authority when a non-officer signs to avoid later challenges.

Is notarization required?

Not typically required for domain transfers. Use notarization or RON only if parties want extra authentication; check state notary fee caps and RON rules if used.

What if the domain is locked?

Request the current registrar to remove the registrar lock and confirm via email before initiating transfer; locked domains are routinely rejected by gaining registrars.

How do I revoke or cancel a transfer?

Contact both registrars immediately; some transfers can be canceled in the authorization window. Document cancellation in writing and retain evidence to resolve disputes.

What supporting documents are helpful?

Include proof of registrant identity or corporate authority, invoices or escrow receipts for payment terms, confirmation emails from registrars, and any prior transfer authorization records.

Electronic Signature
Templates
Miscellaneous
Domain Transfer Agreement

Domain Transfer Agreement

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

DOMAIN TRANSFER AGREEMENT

This Domain Transfer Agreement ("Agreement") is entered into as of by and between the parties identified below.

Parties

Transferor (current registrant) Transferor Address

Transferor Entity Type (select applicable) Individual Corporation LLC Other

Contact Email/Phone Transferee (recipient) Transferee Address

Transferee Entity Type (select applicable) Individual Corporation LLC Other

Contact Email/Phone

RECITALS

WHEREAS, Transferor is the current registrant and legal owner of the internet domain name(s) identified in this Agreement and has the authority to effectuate transfer of those domain name(s); and

WHEREAS, Transferee desires to acquire from Transferor, and Transferor agrees to transfer to Transferee, ownership and control of the domain name(s) subject to the terms and conditions set forth herein; and

WHEREAS, the parties intend for this Agreement to govern the transfer process, the consideration to be paid, the timing for transfer, and related obligations necessary to effect a complete transfer of rights.

SCOPE OF TRANSFER

Transferor agrees to transfer, assign and deliver all rights, title and interest in each domain name listed below, together with any associated registrant account information, authorization codes, and such further cooperation as reasonably required to effect the transfer to Transferee.

Domain Names to be Transferred (list one per line) Transfer Authorization / EPP Codes (if applicable) Gaining Registrar / Account Instructions

PAYMENT TERMS

In consideration for the transfer described herein, Transferee shall pay Transferor the sum set forth below in accordance with the agreed schedule. All amounts are payable in lawful currency of the stated jurisdiction and are exclusive of any taxes unless otherwise stated.

Transfer Consideration (total) Payment Schedule / Due Dates Late Payment Charge

If any payment is not received when due, interest shall accrue at the rate specified above or, if no rate is specified, at the lesser of 1.5% per month or the maximum rate permitted by applicable law, plus all collection costs and reasonable attorneys' fees incurred in enforcing payment.

TERM AND TERMINATION

This Agreement commences on the Effective Date and shall remain in effect until completion of the transfer obligations and payment in full, unless earlier terminated as provided below.

Agreement Start Date Anticipated Completion / End Date Termination Notice Period

Either party may terminate this Agreement for material breach by the other party that remains uncured for the notice period specified above. Termination does not relieve either party of obligations accrued prior to termination, including payment obligations and obligations to complete partially performed transfer steps.

REPRESENTATIONS, WARRANTIES AND COVENANTS

Transferor represents and warrants that it is the lawful owner of the domain name(s) listed herein, that the domain name(s) are free and clear of any liens, encumbrances or claims, and that Transferor has full authority to execute and perform this Agreement. Transferee represents that it has the full legal capacity and authority to accept the transfer and to perform its payment obligations.

Each party covenants to execute such documents and take such actions as are reasonably necessary to effectuate the transfer promptly upon request of the other party.

CONFIDENTIALITY

Each party shall hold in confidence and not disclose to any third party any non-public business, technical or financial information regarding the other party obtained in connection with this Agreement, except as required by law or as necessary to effect the transfer (including disclosure to registrars or legal advisors). Confidential information shall not include information that becomes publicly available without breach of this Agreement or that a party can prove was already in its possession prior to disclosure.

INDEMNIFICATION

Each party agrees to indemnify, defend and hold harmless the other party from and against any claims, liabilities, losses or expenses (including reasonable attorneys' fees) arising out of a breach of its representations, warranties or obligations under this Agreement, or from claims by third parties relating to ownership of the domain name(s) prior to the effective transfer.

LIMITATION OF LIABILITY

Except for liability arising from willful misconduct or gross negligence, or for indemnification obligations under this Agreement, neither party shall be liable to the other for consequential, incidental, special or punitive damages, and each party's aggregate liability shall be limited to the total amounts actually paid or payable under this Agreement.

GOVERNING LAW; DISPUTE RESOLUTION

This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction specified below without regard to conflict of laws principles. The parties agree that any dispute arising out of or relating to this Agreement shall be resolved by the courts located in that jurisdiction, and each party submits to the exclusive jurisdiction and venue of such courts.

Governing Jurisdiction (state or country)

ENTIRE AGREEMENT; AMENDMENT

This Agreement, including any exhibits or schedules executed by the parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior negotiations, understandings and agreements. This Agreement may be amended only by a written instrument signed by both parties.

MISCELLANEOUS

If any provision of this Agreement is held unenforceable, the remaining provisions shall remain in full force and effect. No waiver of any breach shall constitute a waiver of any other breach. Neither party may assign its rights or obligations under this Agreement without the prior written consent of the other party, except that Transferee may assign to an affiliate or successor in connection with a merger or sale of substantially all of its assets.

Additional Terms / Notes

Transferor Name:

By:

Date:

Transferee Name:

By:

Date:

What a Domain Transfer Agreement Covers

A Domain Transfer Agreement is a written contract that documents the authorized transfer of one or more internet domain names from a transferor to a transferee and records related obligations such as payment, timing, DNS updates, and dispute resolution. It identifies the registrant, administrative and technical contacts, the current and gaining registrars, and the authorization code (EPP). The agreement also describes when ownership and control pass, any escrow or payment conditions, and responsibilities for renewing or restoring the domain after transfer. Use it to reduce misunderstandings during registrar-to-registrar transfers.

Why documenting a domain transfer matters

A clear Domain Transfer Agreement reduces ownership disputes, clarifies who must unlock the domain and provide EPP codes, and records consent that supports enforceability under electronic signature law (15 U.S.C. §7001) and state UETA statutes.

Step-by-step: completing a Domain Transfer Agreement

Follow these steps in order to prepare and finalize a domain transfer with minimal friction.

01

Prepare details: Gather domain list, registrant contact, and EPP codes before drafting.
02

Remove locks: Ask the current registrar to remove the registrar lock for each domain.
03

Provide EPP: Obtain and verify the exact authorization codes required by the gaining registrar.
04

Authorize transfer: Have authorized signers sign the agreement and confirm any escrow or payment terms.

How to configure the transfer workflow

Set up a repeatable workflow that assigns roles, notification rules, and retention to avoid missed steps.

Field	Configuration
Authentication	Email + optional SMS code for signer identity
Notifications	Auto-notify admin, registrar rep, and technical contact
Signer Order	Transferor signs first, then transferee
Retention	Store signed agreement for at least 3–7 years

Who does what during a transfer

Domain transfers involve coordinated actions by the parties, registrars, and registry; assign responsibilities clearly in the agreement.

Transferor: Removes lock, supplies EPP code, signs transfer authorization.
Transferee: Initiates transfer with gaining registrar and confirms payment or escrow release.
Gaining Registrar: Submits transfer request to registry and monitors acceptance or rejection.
Registry: Processes transfer per ICANN policy and updates WHOIS on completion.

Essential clauses to include in the agreement

A professional Domain Transfer Agreement should address authorization, timing, payments, post-transfer control, dispute resolution, and change management to limit surprises.

Transfer Authorization

An explicit statement that the transferor authorizes transfer of the listed domains, including signature block and scope of authorization for specific domains.

EPP and Lock Removal

Procedures and timing for providing EPP codes, removing registrar locks, and confirming the domain is eligible for transfer.

Payment and Escrow

Payment terms, escrow instructions (if used), and conditions for release of funds tied to successful registry update.

DNS and Service Continuity

Responsibilities for DNS changes, TTL considerations, and minimizing downtime during the transfer window.

Representations & Warranties

Statements that the transferor has authority to transfer, that WHOIS data is accurate, and no encumbrances exist.

Dispute Resolution

Governing law, arbitration or courts, and remedies for failed or disputed transfers.

Security and compliance essentials to document

Transport Encryption: TLS 1.2/1.3

Data at Rest: AES-256

Audit Trail: Timestamped signing history

ESIGN / UETA: Electronic signature legal basis

HIPAA (if needed): BAA required for PHI

Certifications: SOC 2 Type II, ISO 27001

Who typically completes a Domain Transfer Agreement

These agreements are used by businesses and individuals when ownership or control of domain names changes hands.

Website owners transferring brand domains to new owners or acquirers, ensuring continuity of service and control.
Marketing or IT teams consolidating domains under a single registrar for centralized management and lower risk.
Buyers and sellers in asset sales where domains are a material asset and must be documented for closing.

Tailor the agreement to the parties' roles—clearly list signers, registrar contacts, and technical designees to speed processing.

Signatory roles and typical authority

Domain Owner — Chief Technology Officer

The registrant or authorized corporate officer who can instruct the registrar to unlock domains, provide EPP codes, and transfer administrative control; verify corporate resolution if acting for an entity.

Registrar Representative — Compliance Officer

A registrar or legal representative who can confirm account ownership, accept transfer requests, and verify receipt of funds or escrow conditions when required.

Comparing eSignature vendors for domain transfer workflows

Vendor pricing and capabilities affect per-document cost, bulk transfer workflows, and regulatory compliance; 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 plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes (Business Premium)	Varies by plan	Varies by plan	Varies by plan	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes (BAA available)	Yes	Yes	No	No

Technical requirements and integrations

Choose a platform that supports your file formats, authentication needs, and integrations with existing systems.

File formats: PDF, DOCX, HTML accepted for agreements
Integrations: Salesforce, Microsoft 365, NetSuite, Google Workspace supported by leading platforms
Authentication: Email, SMS, KBA, and advanced signer authentication options

Confirm the eSignature provider supports audit trails, secure storage (AES-256), and any industry addenda such as a HIPAA BAA when PHI is involved.

Common pitfalls to avoid

Using an incorrect or expired EPP/authorization code that results in transfer rejection and delays.
Forgetting to remove the registrar lock before initiating transfer, causing automatic denial of the request.
Failing to update WHOIS contact information, which can prevent authorization emails from being delivered.
Neglecting to coordinate DNS and SSL certificate renewals, producing unexpected website or email downtime.

Risks and potential consequences

Transfer Failure: Loss of time and possible additional fees

Ownership Dispute: Requires legal resolution or UDRP proceeding

Service Downtime: Website/email interruption risk

Financial Exposure: Escrow disputes or withheld payments

Compliance Gaps: HIPAA or contractual breaches if data mishandled

Registrar Limits: Registrar policies or 60-day locks may block transfer

Typical timing and deadlines to account for

Track key timing windows set by registrars and ICANN to ensure a smooth transfer process.

Initiation Window:

Transferee initiates transfer once EPP is available

Authorization Email:

Most registrars allow 5 days to approve or decline via email

Registry Processing:

Transfers often complete within 5–7 calendar days if not blocked

60-Day Lock:

ICANN policy may prevent transfer within 60 days after registrant change

Retention Deadline:

Keep records for at least 3 years after transfer

Practical tips for accurate completion

Small accuracy steps reduce rejection rates and speed completion.

Verify WHOIS

Confirm registrant email and contact information match current WHOIS record before requesting the EPP code to ensure authorization messages are delivered.

Use Exact Codes

Copy-and-paste EPP/authorization codes directly from the registrar; codes are case-sensitive and time-limited in some systems.

Agree on Timing

Document expected transfer and DNS cutover windows to coordinate SSL renewal, email MX updates, and hosting transitions to minimize downtime.

Preserve Evidence

Retain signed agreements, confirmation emails, and registrar transaction IDs to support dispute resolution or audit requests.

How agreements play out in practice

The following examples show common transfer scenarios and outcomes when the agreement is clear.

Small Business Sale

A founder transfers three brand domains as part of a company sale

Escrow held payment until DNS control verified
The buyer avoided service interruption by stipulating DNS handoff steps and retained signed proof of transfer for tax and closing records.

Registrar Consolidation

A marketing agency consolidates client domains to a single account for management

Clients sign transfer authorizations remotely
Documented authorization and retained audit trails reduced disputes and allowed rapid bulk transfers with minimal administrative rework.

Frequently asked questions and solutions

Answers to common questions about enforceability, revocation, authentication, and resolving transfer failures.

Need help? Contact support

Can a Domain Transfer Agreement be e-signed?
Yes. Electronic signatures are enforceable under the federal ESIGN Act (15 U.S.C. §7001) and nearly all states' UETA statutes. For consumer-facing records, meet ESIGN consumer disclosure requirements (15 U.S.C. §7001(c)).
Who must sign the agreement?
An authorized registrant or corporate officer must sign; for entities, attach a corporate resolution or proof of authority when a non-officer signs to avoid later challenges.
Is notarization required?
Not typically required for domain transfers. Use notarization or RON only if parties want extra authentication; check state notary fee caps and RON rules if used.
What if the domain is locked?
Request the current registrar to remove the registrar lock and confirm via email before initiating transfer; locked domains are routinely rejected by gaining registrars.
How do I revoke or cancel a transfer?
Contact both registrars immediately; some transfers can be canceled in the authorization window. Document cancellation in writing and retain evidence to resolve disputes.
What supporting documents are helpful?
Include proof of registrant identity or corporate authority, invoices or escrow receipts for payment terms, confirmation emails from registrars, and any prior transfer authorization records.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now