Here is a question most small business owners can't answer, and don't find out they can't answer until the worst possible moment:
If your website went down tonight, do you have the logins — and the legal ownership — to get it back up?
Not your web designer. Not a former business partner. Not "the person who set it up." You.
Your website rests on three separate things: the domain name, the DNS, and the hosting. They are often held by three different parties, on three different accounts, and many owners control none of them. When access and ownership are unclear, the site can go down with nobody able to fix it — and this is one of the most common, most preventable emergencies in small business technology.
Why website ownership problems stay invisible until they're urgent
In one recent week, three different businesses came through advising sessions with their websites effectively gone — not hacked, not obsolete, just unreachable.
One site was down with a hosting error, and fixing it was tangled in a harder problem: the domain had been registered during a past business partnership, and nobody could say for certain who owned it now. One site went dark from a DNS problem, which meant every online sale stopped — for a business that had no other sales channel. And one site had been timing out for so long that the only path forward was migrating the whole thing to a different platform.
Three different businesses. Three different technical causes. One underlying condition: in every case, the technology existed, but the owner didn't hold the access, the ownership clarity, or the control to act on it.
That's the pattern worth sitting with. The problem was never that a solution didn't exist. The problem was that the owner couldn't hold the solution they had — and having a tool is not the same as being able to use it.
What are the three things you must own?
Your website is not one thing. It's three, and each can be held by a different party.
The domain name
The domain is your address — yourbusiness.com. It's registered with a company called a registrar, it renews on a schedule, and it belongs to whoever controls the registrar account. Not whoever paid for it. Not whoever uses it. Whoever holds the account.
This is where partnership history gets dangerous. If a former partner, an old agency, or a defunct email address holds the registrar account, you may be running your entire business on an address you cannot renew, transfer, or point somewhere new.
The DNS
DNS is the directory that tells the internet where your address leads — which server holds your website, where your email gets delivered. It usually lives with the registrar or the host, but not always, and that "not always" is exactly where businesses get lost.
When DNS breaks or is misconfigured, your site and often your email simply stop, even though nothing is wrong with either one. And only the person with access to the DNS settings can fix it.
The hosting
Hosting is the building your website lives in — the server where the actual files and database sit. It's a separate account, with separate billing, often opened by whoever built the site. If your host has chronic problems, you need the access to leave. If the site goes down, you need the access to restore it.
Why "my web person handles that" is not an answer
None of this means you have to manage servers or learn DNS records. It means the accounts must be yours.
There's a difference between delegating the work and surrendering the ownership. A good web professional works inside accounts that belong to you, as a user you've granted access to. A risky arrangement is the reverse: everything lives in their accounts, and your business is a guest on its own infrastructure.
People retire. Agencies close. Partnerships end, sometimes badly. Every one of those ordinary events becomes an infrastructure crisis when the accounts walk out the door with the person.
Your website is your digital home base — the one piece of your online presence you're supposed to control outright, the ground everything else you build online stands on. A home base someone else holds the deed to isn't a home base.
How to take ownership, starting this week
The work is not technical. It's an inventory, and most owners can complete it in under an hour.
First, find your three accounts. Where is the domain registered, where does the DNS live, and where is the site hosted? If you don't know, your web person, your email receipts, or a lookup of your own domain will tell you.
Second, confirm whose name and email are on each. The recovery email matters most — if it's an old address or someone else's, account recovery fails exactly when you need it.
Third, get each account into the business's hands: your email, your billing, your recovery methods, with collaborators granted access rather than holding the keys.
Fourth, write it down somewhere that outlives your memory — which account, which login, which renewal date. Infrastructure that lives only in someone's head is infrastructure you don't have.
If any of the three can't be traced, or ownership is genuinely ambiguous, resolve it now, while nothing is on fire. Ownership disputes are hard conversations; they are much harder conversations during an outage.
The quiet cost of not knowing
The businesses in those three advising sessions weren't careless. They were normal. Somebody set things up years ago, it worked, and there was never a reason to look underneath — until the day there was.
What an outage costs is obvious: lost sales, lost bookings, days of scramble. What unclear ownership costs is quieter: every future decision about your website — redesign, migration, new tools — runs through an access question you can't answer, so decisions stall, and dependence deepens on whoever happens to hold the keys.
Owning your infrastructure isn't a technical achievement. It's a business capability, and it transfers the same way any capability does: by making the invisible visible, once, on purpose.
Frequently asked questions
What does it mean to own your website?
Owning your website means the domain registrar account, the DNS, and the hosting account are all controlled by you or your business — your email, your billing, your recovery methods — with helpers granted access rather than holding the accounts themselves.
Who owns a domain name — the person who paid for it or the account holder?
In practice, the domain belongs to whoever controls the registrar account it sits in. That's why domains registered under a former partner, an old agency, or a dead email address are a serious business risk.
What's the difference between a domain, DNS, and hosting?
The domain is your address, DNS is the directory that tells the internet where that address points, and hosting is the server where your site actually lives. They can be held in three different accounts by three different parties.
Can my web designer keep managing my site if I take ownership of the accounts?
Yes — that's the healthy arrangement. The accounts belong to your business; your designer or developer works inside them as a granted user. Delegate the work, never the ownership.
Ready to check your own three accounts? The inventory above is the work, and it takes under an hour. If what you find raises more questions than it answers, that's exactly what the next step is for: find your starting point.