Who Really Owns Your Website? Domain, Hosting, and Code

Most business owners answer this question instantly: "I own my website — I paid for it." And then the relationship with their designer ends, and they discover what they actually own is a website-shaped hole in the internet.

Ownership is the single most consequential fine print in any web project, because it's invisible while everything is going well and becomes the entire conversation the moment anything isn't. Designer retires. Designer gets sick. Designer doubles their monthly fee and you want to leave. Agency folds. Every one of these stories ends with the same question — "can I take my site with me?" — and the answer was determined before the first invoice.

Here's the full picture, layer by layer.

Layer one: the domain

The domain — yourbusiness.com — is registered with a registrar like GoDaddy, Namecheap, or Google Domains, and whoever's account it lives in controls it. Not "controls it in a practical sense." Controls it the way you control your email: passwords, billing, the ability to point it somewhere else or let it expire.

The check takes two minutes: look up your domain on a WHOIS search. If the registrant is your business name and your email, you're fine. If it's your designer's name, their studio's name, or an email you don't recognize — you don't own your domain. Your designer does. You're renting the consequences of having it.

This is more common than anyone expects, and it's usually not sinister: designers register domains for clients as a convenience and never transfer them. The problem is that convenience becomes leverage the day the relationship changes. If your designer is unresponsive or hostile, recovering a domain from their account means proving business ownership to the registrar — invoices, correspondence, registration documents — a process that works sometimes and costs weeks.

The standard: the domain is registered in your name, in your registrar account, paid by your card. Your designer may have logins to it; you should have the only billing relationship with it.

Layer two: the hosting

Hosting — the server your site lives on — follows the same logic with one extra trap. Many small studios host client sites on their own accounts: one big server, forty clients, one bill. Efficient for the designer, and it means that if the designer stops paying attention, your site's uptime depends on their credit card.

The questions: whose account is the site hosted in? Can you access the hosting control panel? If the designer disappeared tomorrow, could you move the site — or would you first need to negotiate access to files you paid to create?

The standard: you either host on an account in your name, or you have documented, working access to the hosting control panel. Managed hosting through your designer is a legitimate service — it's how maintenance plans work — but "managed" should mean "they manage it for you," not "they hold it for you."

Layer three: the code and files

The site itself: the code, the design files, the content, the database. On platforms like WordPress, this is a folder of files you can copy and move to any host on earth. On proprietary builders — Wix, Squarespace, and the many agency "platforms" — it's not: the site is a set of entries in someone else's software, and "moving" it means rebuilding it.

That's the trade-off we covered in DIY builders vs. hiring: rented platforms are cheaper and easier until you want to leave, at which point the site you paid for isn't portable. The Facebook-page piece makes the same argument one level up: if you don't own the ground it stands on, you don't own the building. The subscription-model version of this — monthly-fee sites you can never take with you — is worth its own math; see the real cost of "$299/month" websites.

The standard: you can obtain a complete, working copy of your site — files, database, design assets — on request, without a negotiation. Some designers put this in the contract as a "release fee" for leaving. A release fee for your own files is a hostage arrangement with a nicer name.

Layer four: the content and the accounts

The layer people forget until it hurts:

The five-minute audit

Run this checklist on your existing site, today, before you need it:

Any "no" is a project for this month, not for the day your designer retires. If everything is under your designer's control and the relationship is currently good, transferring is a pleasant fifteen-minute conversation. If the relationship is already bad, it's a negotiation — which is exactly why you do it while it's pleasant.

For your next project

Put ownership in the contract before work begins: domain, hosting, and code in your name or transferred at launch; analytics and Search Console in your accounts; a complete site backup delivered at handoff. The launch-side version of this — what you should physically receive on day one — has its own piece: launch day: what a real handoff includes.

Our own arrangement is the simplest version of this: clients own the code, the domain, the hosting account, and the content, outright, with no proprietary platform and no cancellation penalty. Not because we expect you to leave — because the absence of hostage architecture is what "you own it" is supposed to mean.

Questions about what you actually control? We answer every enquiry personally, within one business day.