Last updated: March 16, 2026

Domain names can be transferred after death by providing the registrar with a death certificate, letter of testamentary or administration, and court order appointing you as personal representative, then obtaining the AUTH code to complete the ICANN transfer process (typically 5-7 days). For web hosting, you’ll need to transfer cPanel backups, export databases, and manage SSL certificates separately. This guide covers the technical and procedural steps developers and power users need to transfer domain names and hosting after death, including preventing transfer delays with advance planning.

Table of Contents

Understanding Domain Name Transfer Mechanics

Domain name transfers involve moving registration from one registrar to another, or transferring control within the same registrar to a different account. The process requires authorization from the current registrant and cooperation from both the losing and gaining registrars.

ICANN, the governing body for domain names, establishes transfer policies that all accredited registrars must follow. The standard transfer process includes:

  1. Unlock the domain at the current registrar
  2. Obtain the authorization code (also called EPP code or transfer key)
  3. Initiate the transfer at the new registrar
  4. Confirm via email sent to the domain’s administrative contact
  5. Wait for propagation (typically 5-7 days)

For transfers occurring after death, registrars typically require additional documentation beyond the standard authorization code.

Required Documentation for Death-Related Transfers

When a domain owner dies, registrars need proof of death and authority to act on behalf of the deceased. Documentation requirements vary by registrar, but expect to provide:

Some registrars accept alternative documentation like:

Contact the registrar’s legal or customer support department before gathering documents. Policy differences between registrars can affect which documents they accept.

Step-by-Step Transfer Process

Step 1 - Locate Account Credentials

Before any transfer can occur, you need access to or information about the deceased’s registrar account. This includes:

If the deceased used a password manager, check there first. Many developers store registrar credentials alongside other service credentials. If no password manager exists, the registrar may require additional identity verification.

Step 2 - Contact the Registrar

Email or call the registrar’s support team explaining the situation. Use a subject line like “Death Transfer Request - [Domain Name]” and include:

Most registrars have dedicated processes for death-related transfers. GoDaddy calls this a “Trust/Estate” transfer request. Namecheap handles these through their legal department. Cloudflare requires court documentation.

Step 3 - Submit Required Documentation

After initial contact, the registrar will specify what documents they need. Send certified copies rather than originals, they typically don’t return documents. Keep copies for your records.

Expect a processing time of 2-4 weeks for documentation review. Some registrars expedite this for active businesses, but estate transfers rarely receive priority treatment.

Step 4 - Complete the Technical Transfer

Once documentation clears, the registrar will guide you through the technical transfer:

For transfers to a different registrar:

1. Log into the deceased's registrar account (or have support unlock it)
2. Disable domain privacy if enabled
3. Obtain the transfer authorization code
4. Initiate transfer at the new registrar with the authorization code
5. Confirm transfer approval email from the old registrar

For account-to-account transfers within the same registrar:

1. Provide the gaining account ID to the registrar
2. Sign a transfer authorization form (provided by registrar)
3. Wait for registrar to complete the internal transfer

Hosting Account Transfers

Web hosting accounts add complexity because they often contain:

Transferring cPanel/WHM Accounts

If the deceased used cPanel hosting, you have several transfer options:

Full account transfer (recommended for complex sites):

  1. Request a full backup from the host using the deceased’s account
  2. Download the backup archive
  3. Create a new account at your chosen host
  4. Restore the backup to the new account

Partial transfer (for simpler needs):

  1. Use FTP/SFTP to download public_html contents
  2. Export databases via phpMyAdmin or command line: 
    mysqldump -u username -p database_name > backup.sql
  3. Upload to new hosting and reimport databases

Transferring Cloud Infrastructure

For developers using AWS, Google Cloud, or similar providers:

SSL Certificate Considerations

SSL certificates are tied to specific domains and may include the organization name. When transferring:

  1. Export the private key and certificate from the old server: 
    # Apache
cat /etc/ssl/certs/domain.crt /etc/ssl/private/domain.key

# Nginx
cat /etc/nginx/ssl/domain.crt /etc/nginx/ssl/domain.key
  2. Install the certificate on the new server, or
  3. Generate a new certificate using Let’s Encrypt (free) on the new host: 
    certbot certonly --webroot -w /var/www/html -d example.com

New certificates take effect immediately and avoid transfer complications with organization-validated certificates.

Prevention - Setting Up Transfers Before Death

The easiest transfer is one planned in advance. Developers and power users can take several proactive steps:

Enable Transfer-on-Death Provisions

Some registrars (notably GoDaddy and certain TLDs) support transfer-on-death designations. Set this up in the domain settings to bypass probate requirements.

Document Everything

Maintain a secure document containing:

Store this in a password manager with emergency access enabled, or in a secure physical location known to your executor.

Use Multi-User Access

If using services like Cloudflare or GitHub, add team members or organizations. This provides automatic access continuation without transfer processes.

Register Domains Through a Business Entity

Registering domains through an LLC or corporation can simplify transfers if the entity survives the owner. The domain becomes an asset of the business rather than personal property.

Transfer Checklist for Executors

When handling domain transfers after death, use this checklist:

Domain - __________________________
Registrar - ______________________
Transfer Status - ________________

Documentation:
 Death certificate (certified copy)
 Letter of testamentary/administration
 Court order appointing personal representative
 ID verification of requester
 Any existing transfer-on-death designations

Technical Steps:
 Locate all registrar accounts
 Find associated email addresses
 Identify all domains under each account
 Check for active renewals or subscriptions
 Download any domain configurations/DNS settings

Communication:
 Initial contact with registrar's legal team
 Submit documentation (keep copies)
 Obtain transfer authorization codes (EPP)
 Initiate transfer at receiving registrar
 Confirm transfer approval via email
 Verify propagation after 5-7 days

Post-Transfer:
 Update DNS records if changed
 Verify website accessibility
 Check email forwarding
 Update nameserver settings if needed
 Export all configuration for records

Registrar-Specific Procedures

GoDaddy - Requires notarized letter of testamentary and certified death certificate. Processing time: 2-3 weeks. Contact their Estate & Trust department.

Namecheap - Accepts letters of administration. Can usually process in 1-2 weeks. Requires scan of government-issued ID plus estate documentation.

Cloudflare - Stricter requirements. Requires full probate documentation and court order. May require 4+ weeks for processing.

Google Domains - Recently acquired by Squarespace. Check current procedures via their registrar support, as policies may change.

Email and DNS Impact During Transfer

Transferring a domain can disrupt email and DNS resolution if done incorrectly. To prevent service interruption:

  1. Before transfer: Export current DNS records from the old registrar 
    # If you have access to APIs or DNS manager:
dig @ns1.old-registrar.com domain.com ANY

  2. During transfer: Keep the domain locked at the old registrar until transfer initiates at the new registrar

  3. After transfer: Immediately import DNS records at the new registrar 
    Option A: Use zone file import if available
Option B: Manually recreate each DNS record
Option C: Point nameservers to original provider (keeps DNS intact)
  4. Verification: Test DNS resolution 
    nslookup domain.com
dig domain.com MX # Check mail records
dig domain.com TXT # Check verification records

Handling Subdomains and Email Services

When transferring domains with existing subdomains or email services:

For Gmail, Yahoo, or other email services accessing the domain:

Verify email records before transfer
dig domain.com MX
dig domain.com TXT | grep "v=spf1"

Cost Considerations

Domain transfers have financial implications:

Budget 2-4 weeks and $15-50 per domain for straightforward transfers, potentially more if hosting is included.

Long-Term Planning for Digital Assets

Prevent future transfer delays by establishing these practices now:

  1. Digital asset inventory: Create a document listing all domains, registrars, and credentials
  2. Passwords: Store in a password manager with emergency access for heirs
  3. Transfer authorization: Pre-authorize trusted individuals as account contacts where possible
  4. Beneficiary instructions: Leave clear written instructions for digital asset handling
  5. Regular updates: Review and update the inventory annually, especially after changing registrars

Store this inventory with other critical documents (will, financial accounts) or designate a trusted executor with secure access.

Frequently Asked Questions

How long does it take to transfer registrar accounts?

For a straightforward setup, expect 30 minutes to 2 hours depending on your familiarity with the tools involved. Complex configurations with custom requirements may take longer. Having your credentials and environment ready before starting saves significant time.

What are the most common mistakes to avoid?

The most frequent issues are skipping prerequisite steps, using outdated package versions, and not reading error messages carefully. Follow the steps in order, verify each one works before moving on, and check the official documentation if something behaves unexpectedly.

Do I need prior experience to follow this guide?

Basic familiarity with the relevant tools and command line is helpful but not strictly required. Each step is explained with context. If you get stuck, the official documentation for each tool covers fundamentals that may fill in knowledge gaps.

Can I adapt this for a different tech stack?

Yes, the underlying concepts transfer to other stacks, though the specific implementation details will differ. Look for equivalent libraries and patterns in your target stack. The architecture and workflow design remain similar even when the syntax changes.

Where can I get help if I run into issues?

Start with the official documentation for each tool mentioned. Stack Overflow and GitHub Issues are good next steps for specific error messages. Community forums and Discord servers for the relevant tools often have active members who can help with setup problems.

Related Articles