Every website you visit has an address you can type, remember, and share — a domain name like google.com or blogpress.blog. Behind that friendly name is a system that translates it into the numeric address computers actually use. Understanding that system takes about ten minutes, and it clears up most of the confusion beginners run into: the difference between a domain and a website, between a domain and hosting, and why buying a domain does not by itself give you a website.
This guide explains what a domain name is, how the Domain Name System (DNS) turns it into a connection, who runs the system, and what you actually own when you register a name.
What is a domain name?
A domain name is the human-readable address of a website. Computers on the internet find each other using IP addresses — strings of numbers such as 192.0.2.10. Those are hard for people to remember, so the Domain Name System (DNS) was invented to map memorable names to those numbers. A domain name is simply a friendly label that points to the server where a website lives.
When you type a domain into a browser, three things happen in milliseconds: DNS translates the name to an IP address, the browser connects to the web server at that address, and the server sends back the page. Cloudflare describes it plainly: “DNS translates domain names to IP addresses so browsers can load Internet resources.”
A domain name is not the website itself. It is not the hosting server, the WordPress installation, the email service, or the SSL certificate. Those are separate components that must be connected correctly for a website and its associated services to work. The same domain can also appear after the @ symbol in an email address, and it often becomes closely connected with a business’s identity — but the name and the services behind it are different things.
The parts of a domain name
Read a domain from right to left, from the most general part to the most specific. Take blog.example.com:
- Top-level domain (TLD): the ending after the last dot — .com, .org, .net, .in, .co.uk. The TLD decides which registry holds the record and which rules apply, such as eligibility and pricing. There are well over a thousand TLDs in the IANA root zone database.
- Second-level domain: the part you choose and register — example in example.com. This is usually your brand, and it is the part that makes the name yours.
- Subdomain: an optional prefix, such as blog in blog.example.com. Subdomains organise services under your main name — shop.yoursite.com, support.yoursite.com — and you create them yourself as DNS records, each able to point to a different server. The familiar www in www.example.com is technically also a subdomain.
The root or apex domain is generally written as example.com — the name without any subdomain. A website can use the root domain, the www version, or both, provided one is selected as the primary address and the other redirects to it consistently.
How DNS works, step by step
DNS is often called “the phonebook of the internet,” and the lookup chain behind a single page load is worth understanding, because it explains why domain changes take time to take effect.
- Local cache check. The browser and operating system first check whether they already know the answer from a recent visit.
- Recursive resolver. If not, the request goes to a recursive resolver, usually run by your internet provider or a public DNS service.
- Root servers. The resolver asks a root server where to find the servers for the top-level domain, for example .com. There are 13 named root server identities, each served from many locations around the world.
- TLD servers. The .com registry’s servers reply with the nameservers responsible for example.com.
- Authoritative nameservers. Your DNS host — often your registrar, hosting company, or a DNS provider — returns the actual record, such as the IP address of your web server.
- Connection and caching. The browser connects to that IP address, and the answer is cached for the record’s TTL (time to live) so the next lookup is faster.
That cache is why a DNS change can take hours to show up everywhere: resolvers around the world hold the old answer until its TTL expires. It is not a fault — it is how the system is designed.
Who runs the system?
Four roles keep the system working:
| Role | What it does |
|---|---|
| ICANN | The non-profit that coordinates the global domain name system and accredits registrars. |
| Registry | The operator of a specific TLD — for example, the organisation that runs all .com domains — and its master database. |
| Registrar | The company you buy and manage your domain through. Registrars process registrations, collect the registrant’s information, communicate with the registry, and provide the interface for managing renewals, contacts, nameservers, and transfers. Examples include GoDaddy and Namecheap. |
| Registrant | You — the person or organisation in whose name the domain is registered. ICANN defines the registrant as the person or entity that registers the domain and enters into an agreement with the registrar. |
A registrar may also sell hosting, email, and security services, but those are separate from its role as the domain registrar. Buying them from the same company is convenient; it does not make them the same thing.
Domain vs. hosting vs. website vs. URL
This is where almost every beginner gets tripped up. Four different things, one confusing bundle:
- Domain = the address, such as yourname.com. You register the right to use it for a set period, usually one to ten years, and you renew it to keep it. You do not buy a domain outright — you lease the exclusive right to use the name and decide where it points.
- Hosting = the server space that stores your website’s files and makes them accessible. Think of the domain as the street address and the hosting server as the land or building.
- Website = the content itself — the pages, images, and posts that the server sends back when someone visits.
- URL = the exact address of one page on the website, such as https://blogpress.blog/how-to-start-a-blog-from-scratch/. The domain is the first part of it, not the whole thing.
You need both a domain and hosting to run a live site, and you connect them by pointing the domain’s DNS at your host. If you only register a domain, you own an address with nothing built on it. If you only buy hosting, you have a server nobody can find by name.
Domain vs. email
The same domain can power your email: an address like [email protected] uses the domain after the @ symbol. But email runs on separate DNS records (MX records) that point to a mail provider, and a domain can have a website with one provider and email with another. That separation is also why changing your website host does not have to break your email — as long as nobody changes the mail records by accident. If you are setting up business email, change one DNS system at a time and test delivery after each change.
Choosing a domain name
A few practical rules, learned from watching beginners choose badly:
- Keep it short and sayable. If you have to spell it out every time, it is too complicated.
- Avoid hyphens and numbers if you can. They are easy to mishear and mistype, and they make the name harder to remember.
- Prefer .com when it fits. It is still the default people guess. A country ending such as .in or .co.uk makes sense when your audience is mainly in that country.
- Check the name in all its forms. Say it out loud, write it without spaces, and check that it does not read as something else when the words run together.
- Do not pick a name that is someone else’s trademark. A domain that copies a known brand can be taken from you through a dispute process, however much you paid for it.
- Register the obvious variants only if you need them. The .com and one or two alternates are usually enough for a small site; buying every ending is a cost, not a strategy.
What you own — and what you must keep doing
When you register a domain, you own the registration, not the name itself. The registration lasts for the period you paid for, and it lapses if you do not renew. Losing a domain to an expired registration is one of the most common and most painful beginner mistakes, because someone else can register it the moment it becomes available again.
Protect it with three habits: turn on auto-renewal at your registrar, keep the contact email on the registration current (renewal reminders and transfer approvals go there), and turn on registrar lock and two-factor authentication on the registrar account so nobody else can transfer the name away. If your registrar offers it, add the domain to a calendar reminder a month before renewal as well — auto-renewal fails when the card on file expires.
Common questions
Is a domain name the same as a website?
No. The domain is the address; the website is the content served from the hosting behind that address.
What is the difference between a domain and hosting?
The domain is the name people type; hosting is the server where the website’s files live. You need both, and you connect them through DNS.
What do the parts of a domain name mean?
Reading right to left: the TLD (.com) is the most general part, the second-level domain (example) is the name you registered, and any subdomain (blog) is a section or service you created under it.
Do I need a website before I can use a domain for email?
No. Email uses separate DNS records, so a domain can power email addresses with no website at all.
What happens if I do not renew my domain?
The registration lapses, the website and email stop working, and after a grace period the name becomes available for anyone else to register.
The bottom line
A domain name is a human-friendly label that DNS maps to a server’s IP address. Read it right to left — TLD, your name, then optional subdomains. The domain, the hosting, the website, and the URL are four separate things, and you connect the domain to the hosting through DNS. You lease the name for a set period, so keep auto-renewal on and your contact details current, or the address you built your site on can simply disappear. If you are ready to build on it, our start a blog guide walks through the platform, domain, and launch steps in order, and our SSL guide explains the certificate that turns that address into a secure HTTPS connection.
