Straight answers for local service businesses
Whoever is listed as the registrant on the domain and whoever can log into the registrar account controls your domain name, no matter who paid for it. The website files are separate: they live in a hosting account or on a platform, and whoever owns that account controls them. Spend five minutes looking up your domain and logging into your registrar. If you can't get in, you don't own it yet, and the time to fix that is now, not when you're fighting with someone.
Every few months a contractor calls us in a panic. The guy who built his site stopped answering. Or they fell out over an invoice. Or the nephew who set it all up moved to Arizona and changed his phone number. And the question is always the same: can he really hold my website hostage?
Usually, yes. For a while. Let's make sure that's not you.
The person or company listed as the registrant on the domain record owns it. Practically speaking, whoever can log into the registrar account controls it, because they can change the registrant.
Paying for the domain does not make it yours. If your web guy registered medfordplumbingco.com under his own name and his own GoDaddy account and bills you $20 a year for it, that's his domain. You're renting.
This is not usually malicious. Most small web shops set things up under their own account because it's faster. They never think about what happens if the relationship ends. But it means your business name on the internet sits inside someone else's login.
Three checks, five minutes total.
One thing that trips people up: if you have domain privacy turned on, the lookup will show a proxy service instead of your name. That's normal and fine. Privacy hides your info from spammers, it doesn't change ownership. The login test is what matters.
No, and this is where most of the confusion lives. They're two separate purchases from two separate places.
You can absolutely own your domain and not own your site. Or the reverse. A painter can have full control of his domain at Namecheap while his actual website sits in a builder account that belongs to a marketing agency three states away.
Depends entirely on what it was built with.
WordPress or a custom-coded site on normal hosting: yes. The files and the database can be downloaded and moved to any other host. This is real portability.
Wix, Squarespace, GoDaddy Website Builder, and similar: no, not really. Those sites only run on their platform. You can copy your text and download your photos, but there's no package to hand to a new developer. Moving means rebuilding.
That's not a reason to avoid those platforms. Plenty of good small business sites run on them. Just know what you're actually holding. If someone promised you a site you "own" and built it on a closed builder, what you own is the content, not the construction.
Five accounts. Write them in a password manager or, honestly, on a piece of paper in your filing cabinet. Both beats neither.
Ask. Today. While everybody still likes each other.
Say it plainly: "I'd like the domain moved into an account in my business name. Can you help me set that up?" Most honest web people will do it the same afternoon. It's a normal request.
Here's how the transfer actually works, so you know whether you're being stalled:
If they refuse outright, your leverage is limited but not zero. ICANN has a dispute process. If the domain is your registered business name and they're holding it to extract money, that's a trademark conversation. Both are slow and annoying, which is exactly why you check this while things are calm.
You don't need a contract from an attorney. One paragraph in the proposal or the email thread does it:
The domain is registered to [Your Business LLC] with [owner] as the registrant. Client holds the registrar login. On completion or termination, the developer provides full site files, database export, and admin access to all hosting and platform accounts.
Anyone good will sign that without blinking. The reaction to that paragraph tells you a lot about who you're hiring.
Go do the five-minute check. Most owners find out everything's fine and they just never knew where the keys were. The ones who find out otherwise are very glad they looked on a quiet Tuesday instead of in the middle of a fight.
Not necessarily. Ownership follows the registrant record and the registrar account login, not the invoice. You can pay a web developer every year for a domain that is legally registered to him.
No. Domain privacy replaces your contact info in the public record to cut down on spam, and it doesn't affect who owns the domain. What matters is whether you can log into the registrar account.
Not as a working website. Those sites only run on their own platform, so you can export your text and download your images, but a new developer will have to rebuild the site. Your domain, though, can always be moved separately.
Usually five to seven days once the domain is unlocked and you've entered the authorization code. Transfers are blocked for 60 days after a domain is first registered or after a previous registrar change.
No. You should be the primary owner and anyone helping you should be added as a manager. Managers can do the work and you can remove their access instantly if the relationship ends.
We build it, launch it, and handle everything. $499 one time, live in minutes.
See how it works