Why the domain name is a separate ownership fight from the website itself

What a domain registrar account actually is

"Who technically owns yourbusiness.com?" is a question a surprising number of business owners cannot answer, even years after their site went live and started generating real revenue. It sits quietly in the background until the day it stops working.

A domain name is purchased and renewed through a registrar, a company whose entire business is selling and managing domain names for other people. The account created there, not your website's design or hosting, is what actually controls the name. Whoever holds the login to that registrar account controls whether the domain renews, where it points, and who can transfer it elsewhere.

This is a completely separate account from wherever your website's files live. A beautiful, fully custom site can sit on hosting you fully control, while the domain pointing to it sits in a registrar account belonging to somebody else entirely. Neither account knows or cares what the other one is doing.

A registrar account is closer to a bank account than a filing cabinet. It renews on its own schedule, charges a card on file automatically, and answers only to whoever's name and login sit on the account. Nothing about a beautifully designed website changes any of that.

Why a designer might have registered it under their own account

Registering a domain takes minutes, and a designer moving fast through a project setup will sometimes register it through their own existing registrar account rather than walking a client through opening a new one. It is a convenience decision in the moment, not usually a scheme.

Some designers register domains under their own account on purpose, as a way to keep control over an unfinished invoice or a client relationship that has gone sideways. It gives them something to hold onto if a client stops paying midway through a project. Both explanations land you in the same place either way: a domain you rely on, controlled by someone else's login, not yours.

Neither situation is necessarily malicious on its face. What matters is finding out which one applies to you, and fixing it, before it becomes the reason you cannot make a single change to your own site.

It is also worth asking the question early precisely because it costs nothing to answer. A quick text or email asking "which registrar is our domain with, and whose name is on the account" rarely offends anyone who has nothing to hide about it.

Checking whose name is actually on your domain

A public WHOIS lookup, available through any domain lookup tool online, shows a domain's registrar and, depending on privacy settings, sometimes the registrant's contact details directly. It is a fast first check and it costs nothing to run.

A more reliable check is simply asking to log into the registrar account yourself, right now, today. If you cannot get a straight answer about which registrar the domain sits with, or you get access but the account email is not yours, that is worth resolving immediately rather than filing away for later.

Doing this check early, before there is any tension in the relationship, is far easier than doing it after a dispute has already started. Waiting costs you options you do not get back.

A calendar reminder tied to the domain's renewal date is a cheap habit worth building. Checking who the registrant is once a year takes a couple of minutes and catches a problem long before it turns into an emergency.

Moving a domain into an account you control

If the domain sits in someone else's registrar account, it can be transferred into an account under your name and payment method. Most registrars support this directly through an authorization code and a confirmation step sent to the current registrant on file.

The transfer itself is usually straightforward once both sides cooperate with the process. Getting that cooperation is the part worth planning for well in advance. A handover clause that names the domain specifically, rather than vaguely referring to "all project assets," gives you something concrete to point to if a transfer request meets resistance later.

Once the domain is confirmed in your name, keeping the login somewhere you and anyone who might need it later can actually find matters just as much as securing it in the first place. A password only you know is not much better than one nobody knows.

A shared password manager, or a note kept somewhere a trusted second person can access, closes that gap. It sounds like a small habit. It is the difference between a five-minute fix and a locked-out business the day you need that login and cannot remember where it lives.

The domain and the hosting behind it are two separate things

The domain is the name. Hosting is the account where the actual site files or database live, connected to that name through a setting called DNS. They are billed separately, controlled through separate logins, and can sit with two completely different companies without anything breaking.

This distinction gets missed constantly, even by people who have run a business for years. A business owner who confirms they "own the website" often means they have access to one of these two accounts, not necessarily both. The full picture across every control point, not just the domain, covers what a clean handover actually requires from start to finish.

Hosting ownership carries its own separate risks, distinct enough from domain ownership to deserve a full answer of its own. Backend admin access to the site itself, the part that lets you actually edit pages, is a third and separate thing again, and worth checking on its own terms before you assume it is covered.

More from the blog

All posts