There is a moment we have seen too many times to count. A Korean business owner decides to switch web vendors — the old one is slow, or overpriced, or just stopped answering KakaoTalk. Routine business decision. Then the discovery: the domain, the address every customer knows, the address on the takeout menus and the business cards and the bank paperwork, was registered years ago under the old vendor's account. Suddenly a routine vendor switch becomes a hostage negotiation. This article is about the ten-minute decision, made on day one, that determines whether that day ever comes for you.
Your domain is not part of the website. It is the ground under it.
Owners naturally think of the domain as a component of the website project — the vendor builds the site, the vendor sorts out the address, one package. Legally and technically it is the opposite: the domain is the one asset everything else stands on. The website lives at the domain. Your email — every address @yourbusiness.com — works only while the domain resolves. Your Google rankings, built over years, attach to the domain. Whoever controls the registrar account where that domain lives controls all three. Not influences. Controls.
How the trap gets built (usually without malice)
Here is the frustrating part: this rarely starts as a scheme. Day one of a web project, the vendor needs the domain to exist so they can work. Registering it in their own account takes two minutes; walking a busy, non-technical owner through creating a registrar account takes an hour. So 'I'll just grab it for now' happens, with real intentions of sorting it out later. Later never comes. Years pass. And then the relationship changes — a price increase you refuse, a slow redesign, a vendor who retires or gets sick or simply stops replying — and the structure built carelessly on day one reveals what it always was: your business's front door, in someone else's name.
What the vendor holds the day things go wrong:
- Your website: they can point the domain to a blank page, a 'this site suspended' notice, or nothing at all — while you watch, locked out.
- Your email: the moment the domain stops resolving, every @yourbusiness.com address dies — invoices, customer replies, bank notifications, all of it.
- Your Google rankings: years of SEO equity are attached to that domain. Starting over on a new domain means starting over, period.
- Your leverage: any dispute over money is now negotiated with your entire online existence sitting on their side of the table.
- Your continuity even without conflict: if they vanish or let the domain lapse, it can expire and be bought by a stranger or a squatter.
This is not rare. It is one of the most common disputes we see.
Talk to anyone who works with small businesses on the web side and they will tell you the same thing: domain-control disputes are a steady, recurring category — and in immigrant communities they are worse, because so much business runs on personal referral and verbal trust. The vendor was a friend from church. A cousin's classmate. Of course nobody discussed registrar accounts. Trust is a beautiful basis for a relationship and a terrible substitute for a structure: the whole point of putting the domain in your name is that it keeps working even when trust runs out — and it costs the trusting relationship nothing while things are good.
The ten-minute setup that prevents all of it
Do this at the start of any web project, or this week if your site already exists. Open your own account at a major registrar (GoDaddy, Namecheap, Squarespace Domains, Cloudflare — any of them) using your business email and your credit card. Buy the domain there, or transfer it there. Turn on auto-renew and add a second contact email so it can never silently expire. Then give your web vendor delegate or DNS-level access to do their job — that is normal and necessary. The line is simple: the vendor works inside your property; they do not own the property. Ten minutes. That is the entire insurance policy.
What an honest vendor contract looks like
The cleanest test of a web vendor is whether they put your ownership in writing before you ask. When we drafted the ZOE LUMOS service agreement, we wrote the clause in plain language: the domain is registered in the client's name, in the client's registrar account, from day one — along with the hosting account and the code. Not because regulation demands it, but because we have sat across from too many owners who found out the hard way what the alternative costs. A vendor confident in their work does not need to hold your keys to keep you. If a contract is silent about who owns the domain, that silence is the answer.