Who Really Owns Your Website? Domain, Hosting, and Access in Bangladesh

A website is not one thing. It is three separate things, and owning one does not mean owning the others. Understanding this is the whole subject.
The domain is your address, the name people type to reach you. It is rented from a registrar, usually year by year, and it is registered to a person or company. Whoever is named as the owner controls it.
The hosting is the space where your website files and data actually live. It is an account with a hosting company, and whoever holds that account controls the site’s files.
The website itself is the design, content, and code sitting inside that hosting. Access to change it comes through an administrator login.
A business truly owns its website only when all three, the domain, the hosting, and the administrator access, are in its own name and under its own control. If any one of them belongs to somebody else, that somebody else can, at any moment, decide what happens to your business online.

The problem rarely comes from bad intent. It usually comes from convenience at the start. A business asks a developer or an agency to build a site. The developer, being helpful, buys the domain on their own account, sets up hosting under their own company, builds the site, and hands over a link. The owner is happy. The site works. Nobody discusses ownership, because nothing has gone wrong yet. Years later, one of a few things happens. The business wants to move to a different developer, and the old one is slow to release access, or asks for money to do it. The developer changes career, or moves abroad, or simply stops responding. The developer’s own hosting account lapses, or their company closes. Sometimes the relationship sours over an unrelated dispute and access becomes leverage. In every version, the business discovers it has been building its online presence on land it does not own.

Losing control of a domain is not like losing a file. The domain is the address your customers know, the one printed on your business cards, linked from your Facebook page, and typed into Google. If control of it is lost, everything that pointed to it points to nothing, or worse, to somebody else’s content. Losing hosting access can mean losing the site and its data entirely, including years of content, customer records, and orders. And a website that cannot be updated becomes a slowly dying asset, showing old prices and old information, with no way to fix it. In the worst cases we have seen, a business has had to abandon its established web address, start over with a new one, and rebuild both the site and the search visibility it had spent years earning. All of it, from a decision nobody thought about on the first day.

You do not need technical knowledge to find out where you stand. Ask yourself, and if necessary your developer, these questions.

• Whose name and email address is the domain registered under? A public domain lookup will show the registrar and often the contact details, and you should be able to log in to that registrar account yourself.
• Whose account is the hosting under, and can you log into it directly, with your own username and password, without going through anyone else?
• Do you have an administrator login to the website itself, and does it work?
• Is the billing for domain and hosting in your name, and paid from your account, or does someone else pay and invoice you?

If your developer vanished tomorrow, could you personally get into all three?
If any answer is no, or unclear, or the response is that the developer keeps it all and you do not need to worry, then you do not control your website. That is worth fixing while the relationship is still friendly, because ownership is far easier to transfer during good times than during a dispute.

If you find you do not own your domain or hosting, the first thing to do is not to panic and not to accuse. Most developers hold these things out of habit rather than malice, and most will hand them over when asked plainly. Ask, politely and in writing, for the domain to be transferred into an account in your name, for hosting to be moved to an account you control, and for administrator access to the website. Set up your own accounts at a registrar and a hosting provider first, so there is somewhere for the transfer to go. Keep the request practical and professional: you are not questioning their work, you are putting your business assets in your business’s name, which any reasonable professional understands. Most of the time this resolves quietly. If the developer refuses, delays without reason, or demands payment beyond fair costs to release what you paid for, you have learned something important about that relationship, and you should get the transfer completed before you commission any further work.

The prevention is simple and costs nothing, and it belongs in the first conversation with anyone who builds your site.

• Buy the domain yourself, in your business’s name, with your own email address as the contact. Let the developer use it, not own it.
  Open the hosting account yourself, or insist it is created in your name with your billing. A developer can be given access to it.
• Get your own administrator login to the website, and confirm it works before final payment.
• Write ownership into the agreement: the domain, the hosting, the accounts, the code, and the content belong to the business at the end of the project.
• Note the renewal dates for your domain and hosting somewhere you will see them, because an expired domain can be lost.

A good developer will not resist any of this, because a good developer wants a client who owns their own assets and works with them by choice rather than by capture. Reluctance here is one of the clearest warning signs there is, and it is worth taking seriously, as covered in the Targetiv guide to questions to ask before hiring a web agency.

The mindset shift matters more than any of the steps. In Bangladesh, many business owners treat their developer as the keeper of a mysterious technical world, and treat access to their own website as something granted rather than owned. It is not. The domain is your business’s address. The hosting is your business’s premises. The website is your business’s property. Nobody would accept a shop where the landlord’s cousin held the only key and decided when they could go in. The same standard applies here, and asking for it is not rudeness or distrust. It is the ordinary care any owner takes with anything valuable, and a professional will respect you more, not less, for asking.

• A website is three things: the domain, the hosting, and access to the site itself. You own your website only when all three are in your name and control.
• The usual cause of loss is convenience at the start, when a developer buys the domain and hosting on their own account and nobody discusses ownership.
• The consequences are severe: a lost address customers know, lost data, a site that cannot be updated, and sometimes rebuilding from nothing.
• Check today whose name the domain is under, whose hosting account it is, whether you have an administrator login, and whether you could get in if your developer disappeared.
• If you do not own them, ask calmly and in writing for transfer while the relationship is good. Refusal or delay tells you something important.
• Prevent it by buying the domain yourself, holding the hosting account, getting your own admin login, and writing ownership into the agreement.
• Access to your own website is not a favour from your developer. It is your property, and a good developer will expect you to hold it.