This happens more often than anyone admits. A business pays for a website, the designer sets everything up under their own accounts, and three years later the relationship ends. Suddenly the business cannot access its own domain, its hosting, or its email inbox.
The Domain Is Your Address, Not a Subscription
Your domain is the one piece of your online presence that no host can take away, provided it is registered in your name. Register it yourself, with your own email address as the registrant contact.
If someone else registered it for you, ask for the registrar login today. Not the DNS records. The actual account. If they hesitate, that is the answer you needed to hear.
If you do not control the registrar account, you do not own your domain, no matter what you paid.
Hosting Can Move, Email Cannot Be Recreated
Hosting is replaceable. If a host raises prices or performs poorly, you export your files and move. That is a weekend task. This is why a website built as clean files rather than a locked database is so much easier to move.
Email is different. Years of customer correspondence, invoices, and password resets live in that inbox. Losing access to business email is losing business records. Always use a business email on your own domain, in an account you control, rather than a free address tied to a personal phone number.
Business Email Builds Trust Immediately
A message from name@yourbusiness.com lands differently than one from a random Gmail address with numbers in it. For a customer about to send money, that difference matters.
It also protects you when staff change. A shared info@ address can be handed to a new team member, while a personal address walks out of the door with them.
A Simple Checklist Before You Pay Anyone
Confirm the domain will be registered in your name, with your email as the contact. Confirm you will receive the registrar and hosting login details at the end of the project. Confirm the business email is set up on your own account, not the designer's.
Ask what happens if you want to move hosts in two years. A good answer describes a normal process. A reluctant answer tells you everything.
What Proper Handover Looks Like
At the end of a build you should hold: the registrar login, the hosting or deployment account, the domain records, the email admin account, and the source files. Everything should be documented in one short handover note.
If any of those is missing, the project is not finished, no matter how good the site looks today.