The hosting account is a different lockout point than the domain
What a hosting account controls that a domain doesn't
You checked, and the domain is registered in your name. Relief, for about five minutes. Then you asked where the site actually lives, and nobody had a fast answer.
It's a fair question with a simple answer, once you know where to look. Most business owners never think to ask it until something forces the issue.
That's not a knock on anyone. Hosting is invisible by design. It runs quietly in the background and never demands attention until the day it stops.
A five-minute check now costs you almost nothing. Finding out the hard way, later, costs considerably more in time and stress.
Put a reminder on your calendar to check this once a year, alongside whatever else you review annually. It takes less time than a single coffee break, and it never turns into an emergency if you keep doing it.
The domain is an address. Hosting is the account where the site's files sit and actually run day to day. You can own the address outright and still have zero control over the account serving the pages behind it.
They're two different products, sold by two different kinds of company, and nothing requires them to share a name or an owner. Confusing the two is common, and it's rarely anyone's fault.
An address and the building it points to are separate things in the physical world too. Nobody assumes owning a street address means owning every building on it. Websites work the same way, even though nothing about the site itself makes that obvious.
The two accounts usually come from entirely different companies, billed separately, with separate support lines. Nothing links them automatically. A change to one has zero effect on the other unless someone manually connects them.
Why a designer might host a site under their own account for convenience
Plenty of designers keep client sites on a hosting account they manage themselves. It's faster to set up and easier to maintain across several client sites at once, and in a lot of cases nobody ever asks whose name is actually on it.
That's not automatically a red flag. It becomes one only when you ask to move the site and hit resistance, or discover the account was never meant to be handed over at all.
The difference between convenience and control is entirely in what happens when you ask to leave. A good arrangement lets you go without friction. A bad one starts finding reasons you can't.
Ask about this arrangement before it becomes relevant, not after a falling-out makes the answer matter more than it should. A short, direct question settles it either way, and settles it early.
Moving a site to hosting you control
Moving hosting means opening an account in your own name, transferring or exporting the site's files and database, pointing the domain's settings at the new location, and confirming everything still works before the old account is closed.
None of these steps are difficult on their own. Together, they take some coordination, and a bit of patience while changes take hold across the internet.
A developer familiar with the platform can usually do this cleanly in a single sitting. It's a routine task for someone who's done it before, even if it feels unfamiliar to you.
Keep the old account active until the new one is fully confirmed working, not just partially set up. Closing it too early is the single most avoidable mistake in this whole process.
Getting admin access to your own website is the login you'll need at both ends of that move, so confirm it works before you start, not partway through.
What temporarily breaks during a hosting move
A hosting move usually causes a short window where the site is either unreachable or showing stale content while domain settings catch up across the internet. It's a known, ordinary side effect, not a sign anything has gone wrong.
Email tied to the domain can be affected too, if it runs through the same account as the site. Plan the move for a quiet period if one exists for your business.
None of this is permanent, but it's worth knowing about before the move starts, not discovering mid-transfer with customers watching and calls coming in. A short heads-up to staff avoids a lot of confused messages during the window, and it takes only a minute to send before the move begins, especially if customers regularly reach the business through the site itself rather than by phone or in person.
Checking whose name and payment method is on the hosting account
Log into the hosting provider directly and check the account details: whose name, whose email, whose card is on file for renewal. Don't take someone's word for it. Look at the account yourself.
If none of those are yours, you don't control the account, regardless of what you were told at launch.
This single check, done once, answers a question that otherwise tends to surface at the worst possible time — mid-dispute, mid-sale, or mid-relaunch.
Write down what you find, with the date you checked it, and keep that note somewhere separate from the account itself. It's a small habit that pays off the one time you actually need it, and it costs you nothing the rest of the time.
Who owns your website covers this alongside the other four control points, and who controls your domain name covers the address side of this same split. If the platform itself won't let hosting and the site separate at all, website platform lock-in is the deeper problem worth reading about before you sign anything new.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go