Notes / Siteworks
Who controls your domain, hosting and website accounts?
Keep website control, billing and recovery clear while your agency handles the technical work. A practical guide to accounts, access and handover.
By Edu Rigonato. Published Oct 19, 2026. 11 min read.
Your website is working. The agency makes updates, hosting is covered and inquiries reach your team. You have a login, an invoice and a relationship that feels straightforward.
Then someone asks a practical question: if the person who set everything up became unavailable, who could renew the domain or help another provider take over?
That question does not mean your agency has done anything wrong. It means a website depends on several accounts and services, and their responsibilities are easy to bundle under a phrase like “we handle everything.”
A business should have a clear route to recover critical website assets and authorize changes, even when its agency manages the technical work. The arrangement can include managed hosting and ongoing care. What matters is that the parties understand the access, responsibilities and conditions behind it.
You do not need to learn server administration or start maintaining your own code. You do need to know who can act, what your agreement covers and what a future handover would require. That gives the relationship a useful foundation before there is a problem to solve.
What does controlling your website actually mean?
“We own our website” can describe several different arrangements. A business might control its domain registration, pay an agency for hosting, have access to its CMS and hold rights to some of the site's content. Those things can coexist without being interchangeable.
Start by separating the questions.
Frequently asked questions
Does paying for a website mean I own its code?
An invoice alone does not explain all the rights involved. Account access, copyright, licenses and the ability to run the site elsewhere are separate questions. The <a class="inl" href="https://copyright.gov/circs/circ30.pdf">Copyright Office's work-for-hire guidance</a> describes specific conditions. Ask for a clear explanation of the agreed rights and deliverables; a particular legal dispute needs assessment of the agreement and applicable law.
Can my agency continue hosting the website?
Yes, that can be a reasonable management arrangement. Agree what the service includes, what access and recovery route the business has, and how a future supplier change would be handled. Check platform and plan constraints before assuming that managed hosting can be transferred unchanged.
Does transferring a domain move company email?
Do not assume it does. Domain registration, DNS routing and mailbox services are different components. <a class="inl" href="https://learn.microsoft.com/en-us/microsoft-365/admin/get-help-with-domains/create-dns-records-at-any-dns-hosting-provider?view=o365-worldwide">Microsoft's guidance</a> distinguishes routing new email from moving messages already stored at the former host. Confirm the email scope separately.
Can every website be exported to another host?
No. Export availability and the functions included vary by platform. <a class="inl" href="https://help.webflow.com/hc/en-us/articles/33961386739347-How-do-I-export-my-Webflow-site-code">Webflow documents limits on its code exports</a>, while <a class="inl" href="https://support.wix.com/en/article/can-i-host-a-wix-site-on">Wix explains its hosting dependency</a>. Ask what would be retained, replaced or rebuilt before choosing a migration plan.
What should we check before removing the old agency's access?
Confirm the receiving team's access and the agreed website functions first, then review the old provider's permissions, credentials and integrations. Repository connections and search-verification records may need separate handling. Record what was changed and what remains active; do not treat an account transfer as complete offboarding.
Explore Siteworks