Domain and hosting basics

Your domain is your address on the internet, like yourbusiness.com. Hosting is the computer that stores your website and sends it to visitors. They are two separate things, often bought from two different companies, and the most important rule about both is simple: they must be registered to your business, under a login you control.

Most owners never think about domains and hosting until something breaks: the site goes down, email stops arriving, or a former designer will not hand over access. This article covers the domain and hosting basics you need to avoid those days, without turning you into a system administrator.

What a domain is, and who really owns it

When you buy a domain, you do not own it forever; you register it for a period, usually one to ten years, and renew it. The company you register through is the registrar. The person or company listed as the registrant is the legal holder of the domain.

That registrant field is what matters. If your web designer registered the domain under their own name or their own account, they control it, even if you paid for it. Fixing that later can take weeks of emails and paperwork. Check today: log in to your registrar, or ask whoever set it up for a screenshot showing the registrant name.

Choosing a domain

• .com is still the default for US businesses. Customers type it automatically.
• Short and spoken easily. If you have to spell it on the phone three times, it is too long.
• Avoid hyphens and numbers unless they are part of your brand.
• Consider buying obvious variants and misspellings if your name is often mistyped, and point them to the main site.
• Check trademarks before you build a brand on a domain. A quick search can save an expensive rename.

What hosting is, in plain terms

Hosting is rented space on a server that is always connected to the internet. When someone types your domain, their browser asks the server for your pages and the server sends them. Hosting quality affects how fast pages load, how often the site goes down and how well it holds up under traffic spikes.

Common types of hosting:

Builder hosting is convenient, but the site cannot leave the platform as it is. If you ever move, you rebuild. For hand-coded sites and custom CMS projects, hosting and domain are agreed individually with each client, based on the site's needs, and registered in the client's name.

How the pieces connect: DNS, SSL and email

DNS: the address book

The Domain Name System connects your domain to everything else. DNS records say where the website lives (A or CNAME records), where email should go (MX records), and which services are allowed to send email on your behalf (SPF, DKIM and DMARC records). When you move a website, you change some DNS records. When someone changes the wrong one, email stops working.

SSL: the padlock

An SSL certificate encrypts the connection between visitor and site and gives you https:// in the address bar. Browsers warn visitors about sites without it, and forms on unencrypted pages are a privacy risk. Many hosts include free certificates that renew automatically. Make sure renewal actually works; an expired certificate shows a frightening warning to every visitor.

Email on your domain

Business email (you@yourbusiness.com) usually runs on a separate service such as Google Workspace or Microsoft 365, not on the web host. That separation is good: if the website moves, email keeps working, as long as the MX records stay intact. Set up SPF, DKIM and DMARC so your emails and your website's form notifications do not land in spam.

8 checks to do this week

1. Registrant name. Is your business the registrant of the domain?
2. Login. Do you have your own login to the registrar, not a shared one from your designer?
3. Auto-renew. Is auto-renew on, with a card that will not expire next month?
4. Contact email. Does the registrar have an email address you actually read? Renewal and transfer notices go there.
5. Transfer lock. Is the domain locked against unauthorized transfer?
6. Hosting account. Is the hosting in your name, and do you know where it is?
7. Backups. Does someone make backups, and has anyone ever tested restoring one?
8. SSL. Does your site load with https:// and no browser warnings?

If any answer is "I don't know", that is the first thing to find out. My website ownership checklist covers the same ground in more detail, including code and analytics.

Common mistakes that take sites offline

• The expired card. Auto-renew fails, warning emails go to an old address, the domain expires. Your site and email vanish at once.
• The disappearing designer. The designer who held the accounts changes careers or stops answering. Without logins, you cannot change anything.
• The DNS edit. Someone updates records to connect a new tool and deletes the MX records. Email stops, and nobody notices for days.
• The forgotten second domain. An old domain still forwards to your site, then expires and is bought by someone else.

What I set up for clients

When I build a website, the domain and hosting are registered to the client from the start, with the client's own logins. I give myself user access to do the work, set up SSL, map DNS records carefully so email keeps working, and connect Google Search Console. If you already have a domain, I keep it and move the site without changing your address. Moves between platforms are covered on my website migration page, and the web design overview explains how a full project runs.

Not sure where your domain is or who controls it? That question takes ten minutes to answer on a free consultation, and it is one of the most useful ten minutes a business owner can spend.

Related reading: do you really own your website? and how much a website costs in the US.