Key takeaways
- Register the domain to your company, with billing to a monitored address
- DNS and hosting in your business name, developer added as a user
- Own your analytics and Search Console properties
- Granting access is easy and reversible; transferring ownership is neither
- Fix it while the relationship is good, not when it has broken down
- Keep a written record of every account and who has access
This comes up often enough to be worth writing down.
Your domain name, your DNS, your hosting account and your analytics property should all be registered in your business name. Your developer should have access to them. They should not be the owner.
Why it matters
Ownership decides what happens in three situations that are all quite common.
- You want to change supplier. If the accounts are yours, this is an access change. If they are not, it is a negotiation.
- Your supplier stops responding. Businesses close and people move on. If the domain is registered to someone you cannot reach, recovering it ranges from slow to impossible.
- Something breaks urgently. If nobody at your business can reach the DNS or hosting console, you cannot act and you cannot authorise anyone else to.
What good looks like
- The domain is registered to your company, with billing to a company address that is monitored
- DNS is in an account your business controls
- Hosting is in your business name, with the developer added as a user
- Analytics and Search Console properties are owned by your business, with access granted to whoever needs it
Granting access is easy and reversible. Transferring ownership is neither.
If it is already wrong
It is fixable, and it is better done while the relationship is good.
- Ask for a list of every account the website depends on and who owns each
- Transfer the domain to an account in your business name
- Create your own hosting, analytics and Search Console accounts and add the developer
- Write down where everything is and who has access, and keep it somewhere other than one person's inbox
None of this implies distrust. It is the same reason a business holds the lease on its own premises.
Frequently asked
Questions readers ask
Should my web developer own my domain name?
No. If a developer holds your domain, DNS or hosting in their own name, you cannot leave easily and you cannot recover the site if they stop responding. They should have access, not ownership.
How do I take back control of my domain?
Ask for a list of every account the site depends on and who owns each, transfer the domain into an account in your business name, create your own hosting and analytics accounts and add the developer, then write down where everything is.
Is it rude to ask my developer to transfer ownership?
No, and a good developer will expect it. It is the same reason a business holds the lease on its own premises. Reluctance to transfer, or to show you the accounts, is itself informative.





