Who Owns My Website? Domain, Code & Hosting Explained

Here's the short answer: unless your contract says otherwise, "your" website might not actually be yours. The domain, the code, the content, and the hosting account are four separate pieces of property, and agencies routinely keep control of one or more of them — legally, on purpose — even after you've paid in full. If you don't know who owns each piece, you don't own your website. You're renting it.

This is the question every business owner should ask before signing with any agency, and the one almost nobody asks until they try to leave.

At a glance

• A website has four separately-owned pieces: the domain name, the source code, the content (copy, images, logo files), and the hosting/server account. Each can have a different owner.
• Many agencies register your domain under their own account by default. If they hold the login, they hold your business's front door.
• "We built it, so we own it" is legal in most freelance and agency contracts unless the agreement explicitly transfers IP to you at final payment.
• Lock-in usually isn't malicious — it's just how the contract was written. But it still leaves you stuck paying ransom-style fees to get your own site back.
• Ask for full credential handover (domain registrar, hosting account, CMS admin, source files) in writing before you sign, not after you're unhappy.

The four things people confuse into "the website"

When someone says "who owns my website," they usually mean one specific thing that's currently causing them a headache. It helps to split it into its actual parts.

The domain name

This is the address — yourdomain.com. It's registered through a registrar (GoDaddy, Namecheap, Google Domains successor squarespace, etc.) and renews annually. Whoever's name and email is on that registrar account owns the domain, full stop. It doesn't matter who paid for it or who built the site that sits on it.

The code and design files

This is the actual website — the templates, custom functionality, and design work. Ownership here is a contract question, not a technical one. Some agencies transfer full rights at final payment. Others retain ownership of the underlying code (especially if they built it on a proprietary framework) and only license you the right to use it.

The content

Your logo, product photos, written copy, testimonials — this is usually yours regardless of who built the site, since you either supplied it or paid to have it created for you specifically. But double-check: stock photography and licensed fonts often come with usage restrictions that don't transfer if you switch developers.

The hosting account

This is where the site actually lives and runs. If your agency hosts it under their own master account (common with cheaper, high-volume shops), you don't have direct access even if you technically "own" the code. You're dependent on them to move it, back it up, or hand it over.

Why this becomes a problem

Nobody thinks about ownership on day one. You're excited, you're launching, you sign what's put in front of you. The problem shows up 14 months later when:

• You want to switch agencies and get quoted a "transfer fee" to release your own domain.
• Your original developer goes quiet, stops responding, and your hosting renews under their card — until it doesn't, and your site goes dark.
• You ask for the source files and get told they're "proprietary" or built on a platform you can't take anywhere else.
• Pricing goes up and you have zero leverage, because leaving means starting over from scratch.

None of this requires bad faith. Most of it is just a contract that never addressed ownership explicitly, written by an agency that didn't think it needed to, signed by an owner who didn't know to ask.

The lock-in traps to watch for

Trap	What it looks like	Why it hurts you
Domain registered in agency's name	You never get registrar login credentials	Can't point domain elsewhere, can't verify who really controls it
Proprietary CMS or "walled garden" platform	Site can only be edited/hosted through their system	Site can't be migrated even if you own the code
No source file handover clause	Contract is silent on IP transfer	Default legal position often favors the builder, not you
Hosting bundled with no exit path	"Included hosting" with no separate account	You're a tenant on their server indefinitely
Vague final deliverable language	Contract says "website" but not what that includes	Disputes happen exactly when you're trying to leave

Questions to ask before you sign anything

1. Whose name goes on the domain registration, and can I get admin access day one?
2. Do I own the source code outright at final payment, or am I licensing it?
3. Is hosting under my own account, or bundled into yours?
4. What happens to my site and data if I cancel the monthly plan?
5. Can I get a full file/credential handover in writing, on request, at any time?
6. Is the site built on a proprietary or closed platform, or a standard stack I could take elsewhere?

If an agency hesitates on any of these, that's your answer. A team confident in the value of their work doesn't need to trap you into staying.

How Minuswires handles this differently

We register domains in the client's name, on the client's registrar account, from day one — we never sit between you and your own domain. Code ownership transfers to you at project completion, full stop, no licensing games. Hosting and care plans are month-to-month specifically so the relationship has to earn renewal, not lock you into it. You can see how the build itself works on our process page, and what's included at each pricing tier on our pricing page.

This isn't charity — it's just how Minuswires believes vendor relationships should work. We built Brandlism, our growth intelligence platform, on the same principle: it's infrastructure that makes your site more visible in Google and AI search tools like ChatGPT and Perplexity, but it's built to strengthen your site's authority, not to hold your traffic or data hostage. Ownership and lock-in are different things, and conflating them is how a lot of owners get burned.

If you're comparing what a properly-scoped, ownership-clear build actually costs versus a bargain build with hidden strings, our breakdown on cheap vs. professional websites and our NJ pricing guide both go into real numbers.

What to do if you're already locked in

If you're reading this because you're already stuck, here's the practical path out:

1. Request everything in writing. Domain registrar login, hosting account access, full source files, content assets. Do it via email so there's a paper trail.
2. Check your domain's WHOIS record. Free lookup tools will show you who's actually listed as the registrant — sometimes it's not who you think.
3. Budget for a rebuild if the platform is proprietary. If your site can't leave the agency's closed system, transferring it may cost more than starting fresh on a standard stack. Our custom vs. template comparison explains how platform choice affects this long-term.
4. Get the new agreement right this time. Whoever builds your next site, get ownership terms in the contract in plain language, not implied.

FAQ

Can an agency legally keep my website hostage?

Yes, if your contract allows it — which is the uncomfortable truth. If the agreement doesn't explicitly transfer code ownership and hosting/domain access to you, the agency can legally restrict what you take with you. It's rarely illegal; it's just an unfavorable contract you agreed to without realizing the terms.

How do I find out who owns my domain right now?

Run a free WHOIS lookup on your domain name. It shows the registrant name, registrar, and expiration date. If the registrant isn't you or your business, you don't control the domain — whoever's listed does, regardless of who's paying the renewal invoice.

Does paying in full mean I own everything?

Not automatically. Payment triggers whatever the contract says it triggers. Some agreements transfer full ownership at final payment; others only grant a license to use the site while transferring nothing. Read the deliverables and IP sections specifically — payment alone doesn't guarantee ownership.

What should be in a website contract to protect me?

Look for explicit language on: domain registrant identity, source code ownership at completion, hosting account structure, content usage rights, and what happens on cancellation. If any of these are missing or vague, ask the agency to add clarifying language before you sign — it's a normal, reasonable request.

Is it worth rebuilding a site just to fix ownership issues?

If your current site is on a closed platform you can't migrate off, and the agency won't hand over full access, rebuilding on an open, standard stack is often cheaper long-term than staying locked in and losing negotiating leverage every renewal cycle. It depends on how bad the lock-in actually is — worth an honest cost comparison first.

Get clarity before you sign

If you're evaluating a new build — or trying to figure out what you actually own from an old one — book a call and we'll walk through it plainly. Or check pricing to see exactly what's included, credentials and all, at each tier.