Website Ownership Transfer After Death
Website ownership transfer after death is usually more complicated than people expect.
What survivors think of as "the website" is often a stack of separate assets: the domain name, the hosting or site platform, the billing account, the admin login, and sometimes the business email tied to that domain.
If even one of those pieces is lost, the site can fail before the family finishes the legal paperwork.
Why the domain is only one part of the problem
Saving the domain matters, but it does not automatically save the whole website.
Official GoDaddy guidance says a domain moved to another GoDaddy account keeps its DNS settings, but connected products like the website or email do not move with that domain transfer. Squarespace likewise separates domain transfer steps from site subscription decisions. That means a family can preserve the address while still losing access to the place where the site is actually managed.
As of 2026-03-28, the official provider documents reviewed for this article point to separate workflows for domain registration, site ownership, and connected services. That is an inference from the sources, and it is the practical reason families should inventory the full website stack before they start transferring anything.
What usually needs to be transferred
For most websites, ownership is really a handoff of several layers:
- the domain registration
- the website platform or hosting account
- the billing method that pays for renewals and plans
- any email account used for confirmations, password resets, or transfer approvals
- backups, DNS records, and admin roles
If the site matters to a family or a business, each layer needs attention.
For related domain-specific continuity risks, see /en/blog/what-happens-to-domain-names-after-death.
What the official workflows suggest
ICANN's current materials explain that a gTLD transfer requires an Auth-Code and that registrars must provide it within five calendar days if the registrant cannot generate it directly. ICANN also requires minimum renewal reminders and a post-expiration renewal notice for many gTLDs.
Those rules help, but they do not create a universal inheritance process for websites.
Provider workflows still vary:
- GoDaddy documents account-to-account domain transfers separately from any connected website or email products
- Squarespace says a transfer away may require unlocking the domain, requesting the auth code, and waiting up to 15 days
- WordPress.com publishes one support path for deceased site owners and another process for transferring a site to a new owner
In other words, "website ownership transfer after death" usually means following multiple provider rules, not one estate-tech shortcut.
A safer order of operations
If the website still matters, a safer order is usually:
- Identify the registrar, site platform, hosting provider, and payment method
- Record the expiration date, DNS settings, and backup status
- Keep the service funded so nothing lapses while paperwork is pending
- Gather the documents the registrar or platform requires
- Use the provider's deceased-user or ownership-transfer workflow
- Update billing, recovery contacts, and admin roles after the handoff is complete
This sequence reduces the chance of a preventable outage in the middle of the transfer.
Planning ahead while the owner is alive
The easiest website transfer after death is the one that was prepared in advance.
That usually means documenting:
- which domain registrar controls the site
- which platform or host runs the site
- who should keep, archive, sell, or shut down the site
- where backups are stored
- who can approve billing and account recovery
Business owners should also treat this as continuity planning, not only estate planning. If the website drives leads, sales, donations, or client communication, the handoff plan needs to be clear before an emergency.
For a broader business continuity checklist, see /en/blog/digital-estate-planning-checklist-for-business-owners.
Conclusion
Website ownership transfer after death is not one transfer. It is usually a coordinated handoff of the domain, the site account, the billing path, and the authority to act.
Families can make that process much less risky by preserving service first, using the platform's official procedures, and leaving better records before a crisis happens. When the site matters, planning the handoff early is often the difference between a smooth transfer and a preventable loss.