Who should own your domain, hosting and logins?

You should. Here is how to check what is registered in your name today, what to ask a vendor before you sign, and what to do if you are already locked out.

This is the least glamorous question in a web project and one of the most expensive to get wrong. We meet businesses who cannot update their own website, cannot move it, and in a few cases cannot prove they own their own domain name, because everything was registered in a vendor’s name and the relationship has since ended.

The rule is simple. Your domain, your hosting, your logins and your files belong to your business. An agency should manage them for you. It should not hold them.

What “in your name” actually means

Four things are worth separating, because a vendor can hand over one and keep the others.

The domain name. The registration should list your business as the registrant, with a contact address your company controls. This matters most: the domain is your address, your email, and increasingly your identity.

The hosting account. The account should be in your business name and billed to you, or transferable to you on request.

The website’s admin access. You should have an administrator login to the content management system, not a limited editor account.

The files and, where relevant, the source code. Whatever was built for you should be available to you.

How to check what you have today

You can do most of this yourself in a few minutes.

For the domain, run a WHOIS lookup. Any registrar’s WHOIS page, or whois yourdomain.com in a terminal, will show the registrant organisation and the expiry date. If privacy protection is enabled the contact details may be masked, but the registrar and expiry will still show, and your provider can confirm the registrant on request.

For hosting, find the invoice. Whoever is billed is usually whoever controls the account.

For the website, log in and look at your own user role. If you cannot add or remove another user, you are not an administrator.

If any of those checks comes back pointing at someone else, that is worth resolving now rather than during an emergency.

What to ask before you sign

Put these in the proposal, not in a conversation:

  1. In whose name will the domain be registered?
  2. In whose name will the hosting account be opened?
  3. Will we receive administrator access, and when?
  4. What exactly is handed over at the end, and is training included?
  5. If we move to another provider in two years, what do we take with us?

A straightforward supplier will answer all five without hesitation, because the answers cost them nothing. Hesitation is the signal.

If you are already locked out

It happens, and it is usually recoverable.

Start with the registrar rather than the vendor. Registrars have a process for disputed or transferred registrations, and a business that can evidence its identity and its prior payments has a reasonable position. Gather your evidence first: invoices, email correspondence, and anything showing the domain was bought on your behalf.

If the website itself cannot be recovered, the domain still matters more than the design. A site can be rebuilt in weeks. An email address your customers have used for years is much harder to replace.

How we handle it

Every domain, hosting account and login we set up is registered in the client’s name, and handed over with training at launch. We look after them, and we say so in writing in the proposal before any work starts. If a client ever leaves us, everything goes with them.

That is not generosity. It is the only arrangement that is defensible, and it removes the single biggest risk a business takes when it hires anyone to build its website.

Questions

How do I check who owns my domain?

Run a WHOIS lookup on any registrar's website, or run whois yourdomain.com in a terminal. It shows the registrant organisation and the expiry date. If privacy protection hides the contact details, your provider can confirm the registrant on request.

Can I move my website to another provider?

If the domain, hosting and logins are in your name, yes. That is exactly why they should be registered to your business from the start.

What if the previous developer will not hand anything over?

Start with the registrar rather than the developer, and gather your evidence first: invoices, correspondence, and anything showing the domain was bought on your behalf. Registrars have a process for disputed registrations.

Related service: Support and maintenance

More guides

  1. Will AI replace developers in 2026?

    The short answer is no, and the longer answer matters more if you are paying someone to build software. What AI genuinely does well, what it still cannot do, and what has actually changed.

  2. How much does a website cost in Nepal?

    What a landing page, a business website and an online store cost, what moves the price up or down, and the costs that continue after launch.

All guides

Want this applied to your business?

Describe how the business runs today and what you would like to improve. The first consultation carries no cost and no obligation.