Can the letter be e-signed?

Yes. Electronic signatures are enforceable under the ESIGN Act and UETA when intent, consent, attribution, and retention are present; consumer-facing disclosures may be required for certain transactions.

What must match WHOIS records?

The registrant name, administrative contact email, and domain string should match WHOIS exactly. Mismatches frequently trigger registrar verification requests and processing delays.

Is notarization required?

Not typically required for domain transfers. Notarization or witness signatures may be requested in specific circumstances or by certain registrars; verify state notary and witness rules before obtaining notarization.

How long does a transfer usually take?

Most domain transfers complete within about five days under normal ICANN transfer processing, though registry or registrar policies can extend that period.

What if the auth code expires?

Request a fresh EPP/Auth code from the losing registrar. Document the request date in the letter to show due diligence if a dispute arises.

How can I revoke a transfer letter?

Revoke by submitting a signed written cancellation to both registrars and any escrow agent; act quickly and preserve proof of delivery and timestamps.

Electronic Signature
Templates
Miscellaneous
Domain Transfer Letter

Domain Transfer Letter

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

DOMAIN TRANSFER LETTER AND AGREEMENT

Parties and Effective Date

Transferor Name: Transferee Name:

Effective Date:

WHEREAS

WHEREAS, Transferor is the current registrant and lawful owner of the internet domain name identified below and has the full authority to transfer all rights, title and interest in that domain name to Transferee; and

WHEREAS, Transferee desires to acquire and Transferor desires to transfer the domain name subject to the terms and conditions of this Agreement; and

WHEREAS, the parties intend for this instrument to constitute a complete and binding transfer agreement governing the rights and obligations of the parties with respect to the domain transfer.

Scope of Transfer

Domain Name to be Transferred: Transfer Type: Standard Registrar Transfer Transfer via Escrow

Detailed Scope of Work

Transfer Authorization and Deliverables

Transferor hereby authorizes the release of the domain and any required authorization/EPP code to Transferee or Transferee's authorized agent. Authorization/EPP code:

Transferor represents that, as of the Effective Date, the domain is free of liens, encumbrances, security interests, or third-party claims that would materially impair the transfer. Transferor will promptly remove any such encumbrances prior to initiating transfer.

Payment Terms

Purchase Price Payment Schedule Late Payment

If payment is held in escrow, escrow agent instructions and identity:

Term and Termination

Term Start Date: Term End Date:

Either party may terminate this Agreement for material breach that remains uncured after notice. Notice period prior to termination: days. Termination will not relieve obligations accrued prior to termination, including payment and indemnity obligations.

Confidentiality

Each party shall maintain in strict confidence all non-public information disclosed in connection with the transfer, including account credentials, authorization codes, financial terms and negotiation materials. Confidential information shall not be disclosed except to advisors, agents or contractors who have a need to know and are bound by confidentiality obligations at least as protective as this Agreement. This obligation survives termination for a period of three (3) years.

Representations, Warranties and Indemnification

Transferor represents and warrants that it is the rightful registrant of the domain, has authority to effectuate the transfer, and that to the best of its knowledge the domain does not infringe third-party intellectual property rights. Each party agrees to indemnify and hold the other harmless from liabilities arising from breaches of its representations or failure to perform its obligations under this Agreement.

Governing Law and Dispute Resolution

This Agreement shall be governed by and construed in accordance with the laws of: without regard to conflict of law rules. The parties agree that any dispute arising under this Agreement shall be resolved by the exclusive jurisdiction of the courts located in that jurisdiction unless otherwise mutually agreed in writing.

Entire Agreement

This Agreement, including any exhibits or attachments expressly incorporated herein, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior and contemporaneous agreements, understandings and communications, whether written or oral. Any amendment must be made in writing and signed by authorized representatives of both parties.

Notices and Contact Information

Transferor Contact - Legal Entity Transferee Contact - Legal Entity

Additional provisions:

By signing below, each party certifies that the information provided is true and correct, that the signatory has authority to bind the party, and that the party accepts the terms and conditions set forth in this Domain Transfer Letter and Agreement.

Transferor:

By:

Date:

Transferee:

By:

Date:

What a Domain Transfer Letter Is and Why It Matters

A Domain Transfer Letter is a written authorization that documents the transfer of ownership or administrative control of one or more internet domain names from a current registrant to a designated new registrant. The letter identifies the domain(s), current registrar, gaining registrar, authorization code (EPP/Auth code), effective date, and the parties’ contact details and signatures. It creates an auditable record that registrars and escrow agents use to validate direction of transfer and to resolve disputes. Electronic execution under ESIGN and UETA is generally acceptable in interstate transactions when intent, consent, attribution, and retention are satisfied.

Why a Clear, Signed Transfer Letter Helps

A signed Domain Transfer Letter reduces registrar disputes, documents chain of title, and speeds processing. A clear letter with key fields and verifiable signatures provides evidence of authority and a simple audit trail for business, legal, or escrow purposes.

Typical Parties Who Prepare or Receive This Letter

The Domain Transfer Letter is used by registrants, corporate teams, brokers, and registrars when ownership or control of a domain changes hands.

Domain owners and registrants — prepare authorization and confirm registrant details for transfer.
Corporate legal and IT teams — verify entity authority, coordinate WHOIS updates, and preserve audit records.
Domain brokers and escrow agents — hold authorization as evidence and coordinate transfer steps with registrars.

Each role has distinct responsibilities: preparing accurate details, verifying identity, and retaining records for compliance and future disputes.

Essential Sections to Include in a Professional Letter

A well-structured Domain Transfer Letter groups information into clear sections so registrars can act without follow-up: party IDs, domain details, transfer mechanics, authentication, representations, and signatures.

Authorization

A concise statement authorizing the transfer and naming the gaining registrant or registrar; specifies scope and any limitations.

Domain Details

List each domain name exactly as registered (including TLD). Avoid shorthand or incomplete lists to prevent processing delays.

Transfer Instructions

State whether the registrar should unlock the domain, provide auth codes, or accept push transfers and include expected timelines.

Authorization Code

Provide the EPP/Auth code if available and note its issuance and expiration if known to prevent rejects.

Representations

Short warranties: current registrant confirms authority to transfer and that domains are not subject to undisclosed encumbrances.

Signatures & Date

Signature blocks for authorized signatories with printed names, titles, dates, and contact emails and phone numbers.

Step-by-Step: How to Complete and Use the Letter

Follow a short sequence to prepare, sign, submit, and confirm the domain transfer to minimize delays.

01

Prepare Letter: Populate all fields and attach supporting ownership documents if available.
02

Verify Authority: Confirm the signer has corporate authority or is the WHOIS-listed registrant.
03

Execute Signature: Sign electronically or on paper; include witness or notarization only if required.
04

Submit to Registrar: Send to current/gaining registrar and escrow or broker as applicable; request confirmation.

Where to Send the Completed Letter and How It’s Processed

A completed letter should be routed to the parties and systems that manage registrar actions and recordkeeping so that transfer steps proceed without ambiguity.

Registrar Submission: Provide the letter to the current registrar or its support channel for verification.
Provide Auth Code: Include the EPP/Auth code to enable an automated transfer initiation.
Gaining Registrar Action: The gaining registrar submits the transfer request and tracks status.
Recordkeeping: All parties retain the executed letter and audit trail for future proof of ownership.

Digital Workflow Settings for Online Completion

Configure a digital workflow to reduce manual steps: choose signature type, authentication level, templates, and reminders.

Setting	Configuration
Signature Type	Electronic signature with audit trail
Authentication	Email + SMS code or stronger ID verification
Template Use	Save a reusable letter template for repeat transfers
Auto-reminders	Set periodic reminders until signature completed

Technical Requirements for eSigning and Storage

Use a platform that supports common document formats, secure transport, and robust audit trails for legal defensibility.

File Formats: PDF or DOCX supported
Integrations: Salesforce, NetSuite, Google Workspace
Security: TLS in transit, AES-256 at rest

Security and Compliance Features to Look For

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest

Audit Trail: Detailed timestamps, IP, and action logs

ESIGN & UETA: Compliant for interstate electronic records

HIPAA BAA: Available when protected health data involved

21 CFR Part 11: Support for FDA-regulated workflows

SOC 2 / ISO: SOC 2 Type II and ISO 27001

Key Risks If the Letter Is Incorrect or Incomplete

Transfer Delays: Registrar rejects or requests more info

Registrar Rejection: Mismatched WHOIS causes refusal

Loss of Domain: Unauthorized changes risk ownership disputes

Legal Disputes: Counterclaims over authority or consideration

Financial Exposure: Escrow or sale funds held pending resolution

Compliance Breach: Improper PHI handling risks HIPAA penalties

Common Mistakes to Avoid When Preparing a Transfer Letter

Using an abbreviated or informal registrant name that does not match WHOIS records, which often prompts registrar verification and delays.
Providing an expired or incorrect EPP/Auth code or failing to request the code from the losing registrar before initiating transfer.
Neglecting to confirm signer authority for corporate entities or omitting printed name and title, which can create legal uncertainty.
Failing to preserve an auditable copy (signed PDF with timestamp and metadata) and to route it to escrow or legal records.

Common Timelines and Expected Processing Steps

Domain transfers follow several predictable steps; track dates for code issuance, requests, and registrar actions to avoid expiry and delays.

Request EPP/Auth Code:

Request before initiating transfer; codes can expire in days

Unlock Domain:

Ensure domain is unlocked at the current registrar prior to transfer request

Initiate Transfer:

Gaining registrar submits transfer request once auth code provided

Registrar Processing:

Transfer commonly completes within 5 days under ICANN processes

Update WHOIS:

Confirm WHOIS and billing contact updates after completion

eSignature Pricing and Feature Snapshot for Executing Letters

Comparison of starting price and key capabilities across common eSignature vendors. signNow appears first per vendor ordering rules.

	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	Yes, 7-day trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently Asked Questions About Domain Transfer Letters

Answers to common questions about execution, eSignature validity, notarization, revocation, and registrar interactions for transfer letters.

Need help? Contact support

Can the letter be e-signed?
Yes. Electronic signatures are enforceable under the ESIGN Act and UETA when intent, consent, attribution, and retention are present; consumer-facing disclosures may be required for certain transactions.
What must match WHOIS records?
The registrant name, administrative contact email, and domain string should match WHOIS exactly. Mismatches frequently trigger registrar verification requests and processing delays.
Is notarization required?
Not typically required for domain transfers. Notarization or witness signatures may be requested in specific circumstances or by certain registrars; verify state notary and witness rules before obtaining notarization.
How long does a transfer usually take?
Most domain transfers complete within about five days under normal ICANN transfer processing, though registry or registrar policies can extend that period.
What if the auth code expires?
Request a fresh EPP/Auth code from the losing registrar. Document the request date in the letter to show due diligence if a dispute arises.
How can I revoke a transfer letter?
Revoke by submitting a signed written cancellation to both registrars and any escrow agent; act quickly and preserve proof of delivery and timestamps.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now