Domain Registrar Account After Death: Renewals, Access, And Transfers
A domain registrar account after death can quietly decide whether an important website survives. The domain may point to a family archive, a small business, a professional portfolio, a nonprofit, an online store, or the email address used for invoices, client messages, password resets, and tax records.
That makes a domain different from many ordinary online accounts. If a social profile is neglected, it may sit unchanged for years. If a domain is neglected, renewal dates, payment cards, transfer locks, DNS settings, and registry timelines can create urgent problems. A missed renewal can break the website and email before the family has even finished gathering estate papers.
The safest plan is not to share a registrar password casually. It is to document the domain, keep renewal risk under control, and make sure the right person has legal and practical authority to act.
Start With Renewal, Not Transfer
After a death, many executors think first about ownership transfer. That is understandable, but renewal usually comes first.
ICANN explains that when a domain is registered, the registrant receives the right to use, renew, restore, or transfer the domain name. ICANN also explains that it cannot transfer or return a domain name to someone. If a domain has expired and no one else has registered it, ICANN tells users to contact the registrar immediately to ask what renewal options are available.
That is the key practical point. The registrar is the front line. The estate should identify the registrar, find the expiration date, check whether auto-renewal is enabled, and confirm whether the payment method is still valid.
Do not assume the deceased person's credit card will keep working. A card may be canceled, an estate account may freeze payments, a billing email may be inaccessible, or a renewal notice may go to an inbox nobody checks. If the domain supports business email, losing it can also break account recovery for other services.
What The Registrar Account May Control
A registrar account often controls more than the domain name itself.
It may hold registrant contact records, renewal settings, billing history, privacy controls, transfer locks, authorization codes, DNSSEC settings, nameserver choices, and sometimes the DNS zone itself. In some accounts, the same provider may also sell website hosting, email hosting, SSL certificates, website builders, backups, or security products.
Executors should separate these layers. A domain registrar controls registration. A DNS provider controls records such as MX, A, CNAME, TXT, SPF, DKIM, and DMARC. A host serves the website. An email provider stores mailboxes. Those may be one company or four different companies.
That separation matters because transferring a domain does not automatically transfer every connected service. A domain can remain registered while the website host is unpaid. Email can break if DNS records are changed. A transfer to another registrar may keep nameservers in place, but the estate still needs to know who manages the zone and billing.
Why Password Sharing Is A Weak Estate Plan
It is tempting to write down the registrar password and call the problem solved. For some families, emergency credential access is part of a broader plan. But a password alone is fragile.
The account may require two-factor authentication. The recovery email may be a private mailbox. The phone number may be canceled. The registrar may treat account access after death as an identity and authority issue rather than a simple login issue. If business domains are mixed with personal domains, the wrong person using the login may expose client data or company assets.
The stronger plan is role-based and documented. The owner should list each important domain, registrar, account email, renewal date, billing owner, DNS host, website host, email provider, and intended successor. Business domains should sit in an organizational account when possible, with more than one trusted administrator. Personal domains should have clear instructions for whether they should renew, transfer, archive, redirect, or expire.
What Executors Should Gather
Before contacting a registrar, gather evidence. The exact requirements vary by provider, account type, domain extension, and jurisdiction, but the common pattern is proof of death, proof of authority, proof of identity, and account or domain details.
GoDaddy's published process is a useful example. It says that to access domains or an account after the account holder's death, the requester must be the estate administrator and submit a completed request, legal documentation naming the estate administrator, a copy of the death certificate, and government photo identification.
Other registrars may use different forms or support queues, but the estate should be ready with similar records: death certificate, letters testamentary or letters of administration, court appointment, small-estate affidavit if applicable, government ID, domain names, account email, invoices, and any proof that the deceased person or estate controls the domain.
Do not wait until the domain is one day from expiration. Support review can take time, and registry grace periods are not a substitute for planning.
Transfer Locks And Authorization Codes
Domain transfers have their own mechanics. To move a domain between registrars, the estate generally needs the domain to be eligible, unlocked, and paired with an authorization code, often called an Auth Code, EPP code, transfer code, or transfer key.
Namecheap's transfer-out guidance illustrates the usual steps: check that the domain is eligible, confirm that the domain is old enough and has not recently transferred, disable registrar lock, and get the Auth Code. ICANN's transfer information explains the broader inter-registrar transfer framework for moving domain names between ICANN-accredited registrars.
In estate practice, this means a transfer may not be the first action. If the account is inaccessible, the executor may need account recovery before they can unlock the domain or request the code. If the domain is expired, in a hold status, recently transferred, recently updated, or subject to special country-code rules, transfer timing can be more complicated.
Renew first, stabilize DNS, then transfer when authority and eligibility are clear.
DNS Continuity Is Just As Important
Families often think the domain is the website. Technically, the domain is only the name. DNS tells the internet where the website, email, and verification records live.
Changing nameservers or deleting DNS records can break email, payment processor verification, Google Workspace, Microsoft 365, SSL issuance, analytics, CDN routing, ecommerce checkouts, and password reset flows. If a business depends on the domain, a rushed transfer can create downtime at exactly the wrong moment.
Before any transfer, export or document DNS records. Record nameservers, MX records, TXT records, web host records, subdomains, DNSSEC status, and any provider-specific verification records. If nobody understands the records, leave them alone until a technical administrator reviews them.
Cloudflare And Provider-Specific Account Movement
Some providers combine DNS and registrar services. Cloudflare Registrar documentation says account holders can review expiration date and auto-renew status in domain management. Cloudflare also says that if a domain is registered with Cloudflare Registrar, moving the domain registration between Cloudflare accounts requires a manual request.
That is a useful reminder that account-to-account movement is provider-specific. A registrar may support a simple in-provider push, a manual support request, or a more formal ownership change. Another registrar may require a standard transfer to a new registrar account. Country-code domains may have their own registry rules.
The estate plan should not depend on one generic transfer checklist. It should name the registrar and include that registrar's current support path.
A Practical Planning Checklist
For each important domain, record the domain name, registrar, account email, renewal date, auto-renew status, payment method owner, DNS host, nameservers, website host, email provider, SSL or CDN provider, and business owner.
Then decide the intended outcome. Some domains should renew indefinitely because they support email or a public legacy. Some should transfer to a spouse, company, nonprofit, or beneficiary. Some should redirect to a memorial page. Some old projects can expire after a final archive is made.
For business domains, add operational details: who can approve renewals, who can change DNS, who controls the company email tenant, where invoices go, and which administrator can act if the founder dies or becomes incapacitated.
For personal domains, keep instructions humane and specific. A family blog may deserve preservation. A private project domain may not. A domain used for email should stay active long enough to recover accounts, notify contacts, and migrate records.
What To Do After A Death
First, find all domains. Search password managers, email invoices, bank statements, website footers, WHOIS lookup tools, DNS records, and hosting dashboards. Make a list before changing anything.
Second, protect renewal. Check expiration dates and payment methods. If a critical domain is near expiration, contact the registrar promptly with estate documentation.
Third, preserve DNS. Screenshot or export records. Avoid changing nameservers unless you know where the website and email are hosted.
Fourth, clarify authority. Identify whether the domain belongs to the deceased personally, a company, a trust, a nonprofit, a client, or a joint project. The person with legal authority may not be the person with technical knowledge, so they may need to work together.
Fifth, choose the long-term home. Move the domain into the right account only after renewal and DNS continuity are safe.
The Better Plan While Alive
The best domain estate plan is boring in the best way: renewals work, records are written down, and no critical domain depends on one unreachable inbox.
Use a reputable registrar, enable account security, store recovery information in a secure estate-access system, and keep renewal reminders in more than one place. For business domains, use an organization account or documented admin access. For personal domains, tell your executor which names matter and what should happen to them.
A domain name can be small on paper and enormous in practice. It may be the key to a website, email identity, customer trust, family history, or business revenue. Treat the registrar account as part of the digital estate, and the people left behind will have fewer emergencies to solve when timing is already hard.