Guide6 min readUpdated
Domain and Hosting Explained for Business Owners
Domain and hosting explained in plain words: who owns your website, why the domain should be in your name, and what to ask your developer for.
A tailor in Asansol pays a developer to build a website. Two years later the developer stops answering calls. The tailor wants to change a phone number, but does not know where the website lives or who controls the address. This story is common, and it is easy to prevent.
Domain and hosting explained in one line each: a domain is the name people type to find you, and hosting is the place where your website files are stored so that anyone can open them. You need both. This guide explains what each one is, who should own it, and what to ask for.
What is a domain, and what is hosting?
A domain name is the address of your website, such as yourshop.in. You do not buy it forever. You rent it for a period, usually one year at a time, and you must renew it before it expires.
Hosting is the service that keeps your website files on a computer that is always switched on and connected to the internet. When a customer types your domain, the domain points to that computer, and the computer sends the pages to the customer's phone.
Think of a shop. The domain is the address on the signboard. Hosting is the rented shop room. The website itself is the stock and the shelves inside. If the address expires, customers cannot find you. If the rent is not paid, the room is closed.
There is a third part: the website files and the content. These are your pages, photos, text and any enquiry forms. They can be moved from one host to another, but only if someone has a full copy.
Who owns my website?
You own your website when three things are in your control: the domain registration, the hosting account, and a copy of the website files and content. Owning only one of the three is not enough.
Ownership has two layers. The first is legal: what your agreement with the developer says about the design, text and photos. I cannot give legal advice, so write this part clearly in your contract and ask a qualified professional if you are unsure. For the contract side of a design project, see design contract and NDA basics.
The second layer is practical control. Who can log in? Who gets the renewal email? Who can move the website if the relationship ends? Practical control decides whether you can fix a problem on a Sunday night or not.
A good test: if your developer disappeared tomorrow, could you or a new person restore the website within a few days? If the answer is no, you do not yet have full ownership.
Should the domain be in my name?
Yes. The domain should be registered in your name, or your business name, with your email address and your phone number as the contact.
Some developers register the domain for you under their own account to save time. This is often done with good intentions, but it creates risk. If that account is closed, forgotten or in a dispute, you cannot prove the domain is yours, and moving it becomes slow.
Here is the safer way:
- You create an account with a domain registrar, which is a company that sells domain names.
- You buy or register the domain yourself using your own email and phone number.
- You add your developer as a helper, or you share the settings with them when needed.
Use an email address you will keep for many years, not a personal address that you might close. Turn on the extra security step, such as a code sent to your phone, if the registrar offers it.
To choose a good name before you register, read how to choose a business name and domain.
What should I know about hosting for a small business?
Hosting for a small business means choosing a provider that keeps your website online, takes regular backups, and gives you a way to contact support. The right choice depends on how big your website is and how many visitors you expect.
A simple five-page website for a clinic or a boutique has very different needs from an online store with hundreds of products. Prices and plans change often, so check the current plans on the provider's own page and do not rely on old articles.
These are the questions worth asking any hosting provider:
- Are backups taken automatically, and how many days are kept?
- Is there a free security certificate, so that your website shows the padlock?
- Where are the servers, and is the speed good for visitors in India?
- Can I get my files back if I leave?
- How do I reach support, and in which language and hours?
The hosting account should also be in your name, with a payment method you control. Many owners ask the developer to pay and then add the cost to a bill. That is fine, as long as the account itself belongs to you.
What should I ask the developer for?
Ask for access to every account, a copy of every file, and a short written note that explains where everything lives. Do this before you make the final payment, not after.
Use this list when your website is handed over:
- Domain registrar login, or confirmation that the domain is in your name
- Hosting account login, and the renewal date
- Login for the page where you edit content, usually called the admin area
- A full backup of the files and the database, saved on your own drive
- Original photos, logo files and fonts used on the website
- Login for any extra service, such as an email provider or a form service
- A one-page note listing each service, its renewal date and who pays
If you are the one hiring, it helps to say this at the start. A line in the agreement such as "all accounts will be in the client's name" avoids confusion later. For the design side of this list, my guide on what files to ask your designer for covers logos, fonts and source files.
Which job belongs to whom?
Some jobs belong to you, some to the developer and some to the hosting provider. Writing this down once saves many arguments later.
| Job | Who usually does it |
|---|---|
| Paying for the domain and renewing it | You, or the developer on your behalf, from your account |
| Keeping the server running and updated | Hosting provider |
| Taking backups | Hosting provider, checked by the developer |
| Fixing technical errors on the website | Developer |
| Choosing text, photos and offers | You |
| Deciding layout, colours and where buttons go | Designer, with your approval |
The last two rows matter. Technical work can be given to a specialist, but decisions about how your website looks and speaks to customers stay with you and your designer. When I hand over a website design, I explain these decisions so that the next person who edits the site can keep them consistent.
What should I keep safe, and what should I check every year?
Keep one document with every login, renewal date and contact. Check it once a year, and set a reminder 30 days before each renewal.
Store the passwords in a password manager or another safe place, and not in a chat with the developer. Share access only with people who need it, and remove access when a person leaves your work.
Every year, check four things: the domain expiry date, the hosting renewal date, the contact email on both accounts, and whether you can still log in. An expired domain is one of the most avoidable reasons a business disappears from search for weeks.
If you are still planning the project, read the website launch checklist and the website design cost guide so that domain and hosting are part of the budget from the start.
If you want a website where ownership is clear from day one, you can talk to me about website design.
Frequently asked questions
Can I move my website to another hosting provider later?
+
Usually yes, if you have a full copy of the files and the database, and the domain is in your name. The developer or the new provider does the technical move. Ask your developer how long it would take before you sign.
What happens if I forget to renew my domain?
+
The website and any email on that domain stop working after the expiry date. There is often a short grace period in which you can still renew, but do not depend on it. Set reminders and keep your contact email current.
Is it a problem if my developer owns the hosting account?
+
It is a risk, not always a problem. If the developer is reliable and gives you full access and backups, it can work. The safest arrangement is an account in your name with the developer added as a helper.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.