Web Hosting Account After Death: Keeping A Site Online
A web hosting account after death can be the difference between a website that quietly keeps serving people and a site that disappears at the worst possible time. The account may host a creator portfolio, a family blog, a nonprofit page, a small business site, a shop, a professional archive, or a public memorial.
The website may look like one thing from the outside. Behind the scenes, it can depend on many separate pieces: hosting, domain registration, DNS, email, SSL certificates, content management, ecommerce, payments, backups, analytics, plugins, deployment keys, and billing.
That is why families and executors should not start by guessing the password. They should start by keeping the site stable, identifying who has authority, and understanding which provider controls which layer.
What Makes Hosting Different From A Social Account
A social account can be memorialized, removed, or left alone in many cases. A hosted website is often operational. It can collect orders, publish public notices, receive donations, host client information, display business hours, route forms, or provide the domain used for email.
If the hosting subscription fails, the site can go offline. If the domain renews but hosting expires, visitors may see an error. If DNS changes, email can break. If the wrong plugin or payment integration is disabled, a shop or donation form may stop working.
The practical question is not only who inherits the website. The first question is what must keep working this week.
Map The Website Stack
Before making changes, map the stack.
Find the hosting provider or platform. It might be Squarespace, Wix, WordPress.com, Shopify, GoDaddy, Bluehost, SiteGround, Vercel, Netlify, AWS, or a custom server. Then identify the domain registrar, DNS host, email provider, payment processor, CDN, backup system, and any third-party services used by forms or ecommerce.
These may not be the same company. A domain can be registered at GoDaddy, DNS can run through Cloudflare, the website can be hosted on Shopify, email can be in Google Workspace, and payments can settle through Stripe or PayPal.
Write down the site URL, account email, billing email, renewal dates, payment method owner, admin users, backup location, and any person who has technical knowledge.
Stabilize Billing First
Billing is often the fastest failure point.
Squarespace's deceased-owner guidance is blunt about this. A relative or executor can request billing access to a deceased website owner's site. With billing permissions, the person may keep the site published by updating billing information or take it offline by canceling the subscription. Squarespace also says that, due to privacy concerns and restrictions, it cannot provide full administrative control or the ability to edit the deceased customer's site.
That distinction matters. A provider may help keep the site paid without giving the family full control of the content. For a grieving family, that can feel frustrating. For privacy and security, it is also understandable.
Executors should therefore separate urgent billing continuity from deeper ownership transfer. Update payment only when the estate has authority and the site should remain public. If the site should not stay public, preserve what is needed before canceling.
Provider Access Is Not Uniform
Each platform has its own process.
WordPress.com asks people reporting a deceased site owner to email support with account details if known, the site URL, an explanation, and the desired action, such as making the site private or transferring it to another owner. If someone wants to transfer ownership, WordPress.com asks for a death certificate plus a legal document showing authority to act, or a notarized statement with relationship and requested action.
GoDaddy's process for gaining access to domains or accounts after an account holder's death requires the estate administrator to submit a request, legal documentation naming the estate administrator, a copy of the death certificate, and government photo identification.
Those examples point to the same planning lesson: the executor should be ready with identity, authority, death proof, site details, and account details. A support team cannot safely guess who should control a website.
Ownership Transfer Works Best Before A Crisis
Many platforms support ownership transfer while the owner is alive and able to initiate it.
Wix says transferring a site to another Wix account transfers site ownership and future subscription payments to the new owner. Shopify documents a store ownership transfer process in which the current owner enters the new owner's email and the new owner accepts. WordPress.com says a site transfer can move ownership, plans, paid upgrades, and domains registered on the site to the new owner.
Those tools are much cleaner before death than after death. The current owner can invite the successor, confirm the transfer, explain what goes with the site, and keep a role if appropriate.
For businesses, this should be part of ordinary operations. The site should not sit in a founder's personal account with no second administrator, no documented billing, and no backup plan.
Do Not Break DNS While Trying To Help
DNS is where good intentions can cause real downtime.
Nameservers and DNS records tell the internet where to send website traffic and email. A single change can affect the website, contact forms, Google Workspace, Microsoft 365, Shopify verification, payment processors, SSL certificates, newsletters, and password reset messages.
Before any transfer or cancellation, record DNS settings. Save nameservers, A records, CNAME records, MX records, TXT records, SPF, DKIM, DMARC, DNSSEC status, and subdomains. If the site uses a CDN or edge host, document that too.
If nobody understands the records, do not change them casually. Bring in the web developer, host support, or a technical administrator.
Backups And Exports Come Before Cancellation
Cancellation can be final in practice even when a provider offers limited recovery.
Before canceling a hosting plan, export the site or create a backup. For WordPress, that may mean content exports, database backups, uploads, theme files, plugins, and configuration. For website builders, it may mean provider-specific export limits, page screenshots, downloadable media, invoices, and a written record of settings. For static sites, it may mean repository access, build settings, environment variables, and deployment logs.
For shops, preserve product listings, order history, customer support records, tax documents, payout records, gift cards, subscriptions, and refund obligations before changing ownership or shutting down.
The estate should also consider privacy. A site may contain private drafts, client data, health information, family photos, unpublished writing, or contact forms that still collect personal information. Keeping a site online is not always the right answer. The point is to decide deliberately.
Special Issues For Online Stores
An online store is not just a website. It can include inventory, subscriptions, customer accounts, payment processors, shipping tools, tax settings, chargebacks, app subscriptions, and legal obligations.
If the owner dies, the executor should stop and map the business before transferring anything. Who owns the business entity? Who can fulfill orders? Who can issue refunds? Who receives payouts? Who can access tax records? Are there subscriptions or digital products that customers still expect?
Shopify's ownership transfer documentation is useful for planning because it shows how central the store owner role is. Store owners should set up business continuity before a crisis, including proper staff permissions, organization ownership, payment documentation, and instructions for whether the store should continue, pause, sell, or close.
What Website Owners Should Document
A useful website estate plan should include the hosting provider, account email, domain registrar, DNS host, renewal dates, payment methods, site administrators, developer contacts, repository links, backup locations, and recovery methods.
It should also state what should happen. Keep the site online for one year? Transfer it to a spouse? Move it into the company account? Archive the writing? Replace the homepage with a memorial note? Cancel the store after fulfilling open orders?
The more specific the instruction, the less the family has to improvise.
For creators, include copyrights, licensing, newsletter access, ad networks, affiliate accounts, and monetized content. For businesses, include legal owner, company officers, customer obligations, service providers, and operational passwords. For nonprofits, include board authority, donation forms, and public messaging.
What Executors Should Do After Death
First, avoid panic changes. Keep the site paid if it matters and if the estate has authority to spend funds for that purpose.
Second, identify the platform and account owner. Look at invoices, password managers, bank statements, developer emails, DNS records, and site footers.
Third, gather documents: death certificate, letters testamentary or administration, government ID, site URL, account email, business records, and provider forms.
Fourth, preserve evidence and content. Take screenshots, export data, download invoices, and document DNS.
Fifth, choose the outcome. Keep online, transfer, archive, make private, or cancel. The right answer depends on business needs, privacy, cost, security, and the deceased person's wishes.
The Best Time To Fix This Is While Alive
The most reliable hosting succession plan is quiet and practical. Use a durable account structure, keep billing current, add appropriate administrators, store emergency instructions securely, maintain backups, and document exactly what should happen.
For a personal blog, that may be a simple instruction: keep it online for two years, then archive it. For a business, it may mean multiple admins, company-owned domains, documented deployment, and a named successor. For a nonprofit, it may mean board-controlled accounts and clear donation-form ownership.
A website can be both memory and infrastructure. Treat the hosting account as part of the digital estate, and the people left behind can make thoughtful choices instead of racing against renewals, passwords, and outage notices.