Who Should Own a Restaurant Website’s Domain and Hosting?

The short answer

The business owner should control the domain registrar account, the registrant details, and the renewal billing. Use an email address and payment method controlled by the business. Turn on the account security offered by the registrar, keep the contact details current, and make sure someone at the venue can sign in without asking a former employee or supplier.

Your web studio does not need to own the domain to build or maintain the website. Give it delegated or role based access where the provider supports that. The studio can then change DNS records, connect hosting, or complete verification without becoming the only person who can renew or transfer the name.

Hosting is a different decision. You may hold the hosting account directly, or pay a studio to manage hosting for you. Either arrangement can work. The important part is a written answer for who has access, what is backed up, who receives and pays renewal invoices, what happens if the care plan ends, and how the site will be handed over.

Do not bundle five separate parts into one word

People often say a studio “hosts the website” when several different systems are involved. Separate them before you compare a quote:

1. Domain registration: This is the right to use the registered name for the paid registration period. ICANN calls the person or entity holding those rights the registrant. The registrar manages the registration agreement, fees, transfers, and renewals.
2. DNS: The Domain Name System connects the domain to online services. Records can direct website traffic, identify mail servers, and hold verification information. Nameservers tell the internet where the active DNS records are published.
3. Website hosting: This is the service that stores and delivers the website. Moving a site to a new host does not automatically transfer the domain registration.
4. CMS: A content management system is where your team edits pages, menus, photographs, or room information. It may be part of a hosted platform or a separate application on a hosting account.
5. Email: Business email can be provided by a completely different company from the website host. Its delivery depends on DNS records, particularly MX records. A website move should preserve the working email records unless the email service is also changing.

One company may supply several of these services, but they remain separate responsibilities. Ask for the provider and account owner for each one. This simple map prevents a vague promise such as “everything is included” from hiding who can actually sign in, pay, change, export, or cancel.

Who should control the domain registrar account?

Register the domain in an account controlled by the business. Use the venue’s real organisation or owner details as appropriate for the business and registrar, rather than a studio team member’s personal details. Keep the login, recovery method, contact details, and billing under business control.

ICANN explains that the registrant holds the rights to the registered domain name, while the agreement with the registrar governs renewal and transfer. ICANN also warns that a domain must be renewed to keep the website and associated services, including email, working. Current contact information matters because renewal and account notices are sent there.

A sensible setup includes:

• A registrar account created for the business, not inside a developer’s personal account.
• A business controlled email address for notices, plus a recovery route that will still work if the domain itself has a problem.
• Current registrant contact details and a named person responsible for reviewing them.
• Automatic renewal where suitable, a current payment method, and a calendar reminder to check the account before expiry.
• Two step verification or the strongest account security the registrar offers.
• Delegated access for the studio where available, with access reviewed when the project or care agreement ends.

If a studio has already registered the domain inside its own account, ask for a calm, documented plan to move the registration into a business controlled account. Confirm the registrant details, registrar, expiry date, transfer process, and any current transfer lock before setting a deadline. ICANN notes that some transfer restrictions can apply, including a period after initial registration or certain registrant changes.

When managed hosting is a reasonable choice

Managed hosting can remove useful technical work from a busy venue team. A studio can handle deployment, routine maintenance, backups, monitoring, and small website updates under a care agreement. The owner does not need to operate the hosting dashboard every week for the arrangement to be sound.

The difference between useful management and avoidable dependence is clarity. Before launch, record:

• Which company provides the hosting and which plan or service is being used.
• Whether the hosting account is owned by the business or managed inside the studio’s account.
• What access the owner receives now, and what access or account transfer is provided at handover.
• What is backed up, how often backups are made, how long they are retained, and who can restore one.
• What the recurring charge covers, when it renews, who receives the invoice, and what happens if payment stops.
• Which platform licences, paid extensions, or services are included, and which need a new subscription after handover.
• How much notice either side gives to end the arrangement, and what files, credentials, and assistance are included in the exit.

You can keep the domain at one provider and host the website elsewhere. That separation is common and can make the domain less dependent on a hosting relationship. It also means the handover notes must say where DNS is managed and who is allowed to change it.

A quote review checklist before you say yes

A useful website quote names deliverables and responsibilities, not just a total. Our broader guide to what a restaurant website quote should include covers scope and guest journeys. For ownership and infrastructure, ask these questions:

• Who will be the domain registrant, and whose account and payment method will be used?
• Is the domain registration new, transferred, or left where it is?
• Who manages DNS, and how will existing website, email, and verification records be documented before changes?
• Who supplies hosting, who owns that account, and what recurring fee is separate from the build?
• Will the venue receive CMS administrator access and instructions for common updates?
• Who owns or controls analytics and Google Search Console, and will the venue be added with the appropriate permission?
• What backup and restore process is included?
• What happens to the live website if the maintenance agreement ends or an invoice is late?
• What exactly is included in handover, how long should it take, and is migration assistance charged separately?

Google Search Console supports owners and users with different permissions. A venue can remain an owner while giving a studio the access it needs. For a Domain property, Google requires DNS verification, which is another reason to know who controls DNS and to preserve the verification record after setup.

A practical website handover checklist

A handover should leave the venue able to keep the site and its connected services running. Ask for one current account map and work through it together:

• Domain: Registrar name, account access, registrant details, expiry date, renewal setting, billing owner, domain lock status, and transfer instructions.
• DNS: Nameserver details, the provider hosting the DNS zone, a record of the active DNS entries, and a clear note identifying website, email, and verification records.
• Hosting: Provider, account or project access, plan, renewal responsibility, deployment method, and support route.
• Website and CMS: Administrator access, a current export or backup that includes the site files and content needed to restore it, and instructions for routine edits.
• Email: Email provider and administrator contact, with the active MX and relevant authentication records documented. Email passwords do not need to be shared with the web studio.
• Search and measurement: Appropriate access to Search Console and any analytics account, with ownership tokens left intact where they are still required.
• Paid services: Fonts, extensions, booking tools, forms, image services, or other subscriptions that need to continue after handover.
• People: The venue contact, studio contact, and provider support details for urgent domain, DNS, hosting, or email problems.

Test the handover before calling it complete. The owner should be able to sign in to the registrar, identify the hosting and DNS providers, see the next renewal responsibility, open the CMS, and confirm the promised backup exists. Do not wait for a disagreement or an expired card to discover that the instructions are incomplete.

If you are changing studios or hosting providers

Start with an inventory, not a cancellation. Record the registrar, nameservers, DNS entries, hosting project, CMS, email provider, forms, booking links, Search Console users, analytics, and paid services. Take the agreed backup and confirm it can be used for the planned destination.

Protect email while the website moves. Changing a hosting plan does not require changing email, but replacing nameservers can change which DNS zone is active. The new zone needs the correct website, MX, verification, and email authentication records before the old service is removed.

Keep both sides available long enough to verify the new website, forms, booking links, and email route. Then remove access that is no longer needed and update the account map. If the site itself also needs a clearer structure, use the move to define what each page must do rather than copying every old page automatically. The guide to one page and multi page restaurant websites can help with that separate decision.

Sources

• ICANN, The Domain Name Registration Process
• ICANN, Renewing Domain Names
• ICANN, FAQs for Registrants: Transferring Your Domain Name
• Google Search Console Help, Verify your site ownership
• Google Search Console Help, Managing owners, users, and permissions
• Google Workspace Admin Help, DNS basics