Who should own your domain and website accounts?

The business should own its domain and every core website account in its own name, under a company email address that more than one person inside the business can reach. Designers, developers and marketing vendors can then be given their own logins with the access the job needs, and removed when the work ends. ICANN's statement of registrant responsibilities says the registrant assumes sole responsibility for the registration and use of the domain name, which is why that name on the record matters.

Ownership problems rarely show up on launch day. They show up years later, when the person who registered the domain has left, the renewal notices go to an address nobody reads, or the business wants to change designers and discovers it cannot log in to its own site.

This page is a planning checklist for owners and marketing leads. It is not legal advice, and contract terms with any vendor are a matter for your own review.

What the registrant record means

ICANN publishes a page on registrants' benefits and responsibilities. It says a domain registration must be subject to a registration agreement with an ICANN-accredited registrar, that the registrant should review that agreement and its updates, and that the registrant assumes sole responsibility for the registration and use of the domain name. It also asks registrants to provide accurate contact information, update it promptly when it changes, and respond to inquiries from their registrar within fifteen days. If the registration renews automatically, the registrant has to keep payment information current.

Each of those duties lands on whoever is named as registrant, and each one assumes that person is reachable. Paying the renewal invoice is not the same as being the registrant. A designer who registered your domain in their own account, with their own email, holds the record even if your business has paid every bill.

The accounts that sit beside the domain

The domain is one account among several. A complete inventory usually includes the following, and each line should name an owner inside the business.

Google's guidance on hiring an SEO offers a useful pattern for vendor access: at the start, grant read access to Search Console rather than write access. The same idea works elsewhere. Owners hold the owner role, and outside help gets the narrowest access that lets them do the work.

Write the inventory down before anything else. Nobody building your site should have to invent which accounts exist or who holds them, because that inventory is business knowledge and it belongs with the business. It should be one of the first documents a build produces, and someone inside the company should review it once a year.

A fictional example: the renewal nobody saw

Consider a fictional bookkeeping firm in Ohio. Its domain was registered eight years ago by a freelance designer, in the designer's own registrar account, with the designer's email as the contact. The firm paid an annual invoice for "hosting and domain." When the firm hires a new web team, it learns it does not control the registrar account, and the designer has moved out of state.

ICANN's registrant transfer FAQ, as read in October 2026, describes the steps that follow. A change of registrant is started by contacting the current registrar, which asks for confirmation through a secure mechanism. Moving the domain to a different registrar requires an authorization code (the FAQ calls it an Auth-Code), and the current registrar must verify the registrant's intent to transfer. Transfer procedures are revised from time to time, so confirm the current steps with your registrar before starting. Every one of those steps runs through the person named on the record. The firm's job became finding the designer and asking for cooperation, which is a worse position than holding the account from the start.

Setting it up right on a new build

Start a build with an access check inside your own company. Put a blunt question to the team: "If our web person disappeared tomorrow, could we renew the domain, change the site, and read our form submissions without them?" If the answer is no for any account, fix that before design work begins.

Use a role address that survives staff changes (for example, a shared web or admin mailbox) as the owner email on registrar, platform and analytics accounts. Keep credentials in a company password manager rather than in one person's browser. Turn on two-step sign-in where the account offers it. Invite designers and developers as users under their own logins instead of sharing the owner password, and write down when to remove them.

Plan the end of the relationship at the start, too. When a vendor's work ends, remove their user access, change any password they knew, and confirm that renewal notices and form submissions still reach a company inbox. Doing this on a calm afternoon takes minutes. Doing it after a dispute, or after the vendor has stopped answering email, can take weeks.

Hudson South builds websites around the same four steps as its content work: Authority Asset gathers approved business knowledge and evidence, Hudson Twenty-One records how the business communicates across 21 dimensions so the writing sounds like it, Market Intelligence researches the buyer questions and the market, and AEO Creation turns those inputs into answer-first content. None of those steps should depend on accounts the business cannot reach.

When you are moving an existing site

Ownership matters most when a site changes platforms. The move touches the domain's DNS records, the old platform's account, the new platform's account and the analytics history at the same time. Confirm owner access to all of them before anything is switched, and keep the old account available until redirects are checked. The steps for protecting search traffic are covered in how to move a website without losing search traffic.

Ownership also belongs in the hiring conversation. The questions to ask a web designer before you hire one start with who will hold each account, and the website builds overview explains the platforms Hudson South builds on.

Start the build with the keys in your hands

On a free 30-minute call, Hudson South compares your site with the competitors your buyers also look at and talks through what a rebuild needs before it starts.

Sources

1. Registrants' Benefits and Responsibilities. ICANN. Read 2026-10-17.
2. FAQs for Registrants: Transferring Your Domain Name. ICANN. Read 2026-10-17.
3. Do you need an SEO?. Google Search Central. Read 2026-10-17.