Key facts
- Every domain name has a registrant of record, the legal owner listed with the domain registrar, and whoever controls that registrar account can renew, transfer, or repoint the domain regardless of who built or manages the website itself.
- Website hosting accounts and domain registration are typically separate services from the website's content management system, so an agency can hold effective control over one, both, or neither, depending entirely on how the accounts were originally set up.
- A domain transfer between registrars or a change of registrant generally requires access to the domain's own control panel or confirmation through the current registrant's contact email, which means whoever holds that access controls the process.
- Website platforms differ in how portable a site actually is; some page builders and website platforms lock content into a proprietary format that doesn't export cleanly to another platform, which adds a second layer of practical hostage risk beyond just domain and hosting.
- A written services contract can specify what happens to access and ownership at the end of the engagement, but a contract's terms only help if you can actually enforce them, which is far easier when you already hold the underlying accounts.
Yes, and Here's Exactly How It Happens
There are three real levers here: domain registration, the hosting account, and the login to your website's own platform or content management system. Each one is independently enough to cause a real problem if the agency alone controls it.
The practical effect is plain. If you can't renew or move your domain, or log into your own hosting, you don't independently control your own website's most basic infrastructure, no matter how the working relationship currently feels.
This isn't a hypothetical or an invented scare. It's a structural fact of how domain names and hosting accounts work, regardless of who's involved.
Check Your Own Setup Right Now, Before There's a Dispute
Look up your domain's registrant record, either directly through your registrar account or through a public lookup, and confirm it lists your business, not the agency.
Confirm you have direct login access to hosting and to the website's own admin area, independent of anything the agency may have set up for their own use only.
Do this now, while the relationship is fine. It's far harder to sort out once a dispute has already started.
If You Find Out the Agency Currently Controls It
Raise it directly and calmly, framed as wanting to correct account ownership, not as an accusation aimed at the relationship as a whole.
Request that the domain be transferred to your own registrar account, and that hosting access be added or fully transferred to you.
If resistance follows, involve a lawyer or a third-party mediator before the relationship deteriorates further. Acting early gives you meaningfully more leverage than acting after a falling-out has already happened.
How to Prevent This With Any Future Agency
Register your own domain, in your own name, before any agency ever touches your website.
Set up hosting under your own account and grant the agency access to work within it, not ownership of the account itself.
Keep a simple record, a document listing your domain registrar, hosting provider, and CMS login locations, so you or anyone else can quickly verify control at any point.
Related questions
Look up your domain's registrant information directly through your domain registrar's account settings, or through a public lookup, which shows the registered contact for most domains. If the listed registrant is your agency rather than your business, that's the exact issue to raise and correct as soon as possible. This check costs nothing and takes only a few minutes, so there's little reason to leave it unconfirmed.
It can raise real legal issues, particularly around contract obligations and business interference, but pursuing that after the fact is slow and costly compared to simply preventing the situation by owning your own domain and hosting from the start. Prevention is far more reliable than a legal remedy after a dispute has already started.
Some platforms and page builders make migration genuinely harder because content doesn't export cleanly to another system. Ask directly, before any dispute, how portable your specific site actually is, and treat a difficult answer as a reason to plan an eventual migration path, even if you're not switching agencies right now.
Yes, it's worth documenting clearly, but a contract clause only helps if you can enforce it, and enforcement is far easier when you already hold the actual domain and hosting accounts. Treat the contract as a backup, not a substitute for owning the real infrastructure yourself from day one. Spell out specifically what happens to access at the end of the engagement, rather than leaving it to be negotiated later.
Often yes, through a domain transfer process, though it generally requires the current registrant's cooperation or specific verification steps depending on the registrar. Start by asking directly for the transfer. If that's refused, a registrar dispute process or legal help may be needed, which is exactly why avoiding this setup in the first place matters so much.
Want a second opinion on your situation?
Get a free, no-obligation proposal. We’ll look at your site and your market and tell you honestly what we’d do — and what we wouldn’t.
Get your free proposal