You decide to switch web providers, or you stop paying for a marketing package you no longer need. You ask for your login credentials so you can move your site somewhere else. The answer you get back is some version of "that's not really how it works." Your domain isn't in your name. Your hosting account belongs to them. The platform your site runs on isn't something anyone else can log into anyway.
The direct answer is: it depends on what part of the website you're asking about. A website isn't one thing you either own or don't. It's four separate pieces, and each one can legally belong to a different party. Whether you control your website comes down to who holds each of those four pieces, not whether you paid for the project.
The four pieces, and who holds each one
The domain name. This is your address, the words before ".com" that customers type in or click from a search result. Registering a domain does not mean owning it the way you own a piece of equipment. Domain registration gives you an exclusive right to use the name for a specified time, similar to a contract with a wireless carrier for a phone number. What matters is whose name sits in the registrant field at the domain registrar. A domain is registered through a registrar like GoDaddy, Namecheap, or Cloudflare, and whoever's name is on that registration is the legal owner, so if a web designer registered the domain using their own account, they control it. That means they can technically let it lapse, transfer it, or refuse to release it in a dispute.
The hosting account. This is the server space where your site's files live. If the invoice for hosting goes to your designer or agency and the account is in their name, they are the ones with the power to turn your site off. The hosting account may belong to the client, the agency, or a reseller account; whoever owns it generally controls suspension, though that control does not automatically mean legal ownership of the website living there.
The code, design, and CMS. This is where many business owners get tripped up. Paying for a website to be built does not automatically make you the legal owner of what was built. By default, a website designer or company owns the source code, files, visual design, and CMS customizations unless the client signs a written agreement transferring those rights. If you never signed anything that specifically assigns that intellectual property to you, the person who built it still holds the rights, even after final payment.
The content. Copy, photos, and written material are governed by copyright before any contract even exists. The U.S. Copyright Office explains that copyright attaches to original works automatically the moment they're created and fixed in tangible form, with no registration required. Whoever wrote a page of copy or took a photo holds the copyright to it unless there's a written agreement saying otherwise, regardless of who paid for the work.
Why this stays invisible until you try to leave
None of this matters day to day. Your site loads, customers find you, everything works. The problem surfaces at one specific moment: when you try to make a change and can't, or when you decide to work with someone else and discover you can't take anything with you. When you try to exit an agreement, you may find you don't own your website, and at that moment the site can be taken offline, access to code and files can be lost, or a large fee gets demanded.
The nonpayment version of this is worse. If you stop paying and the hosting account isn't in your name, the person who controls it has real leverage. If an agency owns the hosting account and pays the bill, they can suspend service if payment stops, provided the contract supports it.
Not every web designer who does this is acting unethically. Plenty of agencies manage a domain or host a site as a convenience and hand over full control the moment they're asked. But if you do not have that control by default, talk about it before you sign anything instead of assuming ownership is automatic because you paid the bill.
What to check
If you already have a website, four questions will tell you where you stand:
-
Who is the registrant on your domain? Look up your domain through a WHOIS search or log into the registrar directly. You should be the registrant for your domain name, with your developer listed only as the administrative or technical contact if they need to manage it.
-
Whose name and payment method is on the hosting account? If it's your agency's card on a reseller plan, you don't hold the account, no matter whose logo is on the invoice you get.
-
Does your contract say IP transfers to you? A contract that transfers IP should state that upon final payment, all website elements, including source code, visual design, CMS, and database scripts, transfer to the client. If that sentence doesn't exist somewhere in writing, assume it doesn't apply.
-
Is your site built on a proprietary, closed platform? Some agencies build sites on systems that only they can edit or export, which is a different kind of lock-in than ownership on paper. Many small business sites run on WooCommerce, Shopify, Wix, Squarespace, or WordPress with managed hosting, and if a designer controls that setup, moving the site can feel impossible.
None of these fixes require confrontation. Settle them before a project starts, not after a relationship sours. A written agreement that specifies domain registrant, hosting account ownership, and IP transfer on final payment costs nothing to add and prevents the entire problem.
Key Takeaways
- A website is four separate pieces: domain, hosting, code and design, and content, and each one can legally belong to a different party regardless of who paid for the project.
- Registering a domain gives an exclusive right to use it, not true legal ownership, and whoever's name sits in the registrant field controls it.
- By default, a web designer or agency owns the source code, design, and CMS customizations they build unless a written agreement transfers those rights to the client.
- Copyright on written content and photos belongs automatically to whoever created it the moment it was made, with no registration required, unless a contract says otherwise.
- The safest time to settle domain registrant, hosting account ownership, and IP transfer terms is before a project starts, not after you try to leave.
If you're evaluating a new build or a redesign, ask these questions before signing anything, not after. Mindstate Strategy builds sites where the domain, hosting, and code sit under your name from day one, and our web development process is structured around that from the start. If you want a straight answer about who would control your site during or after a build, get in touch and we'll walk through it with you.
