A domain is the name people use to find and identify you online. example.com is a domain name. You can connect it to a website, use it for an address such as [email protected], or create sections such as shop.example.com.

Registering the domain does not create any of those services automatically. It gives you renewable control of the name. You then connect that name to website hosting, an email provider or another online service.

That distinction prevents one of the most common first-time mistakes: paying for a domain and expecting a finished website to appear.

A domain is not a website or web hosting

Imagine a bakery with its own domain. This guide represents that name as example.com, but the name is only one part of the bakery’s online setup.

Term	What it provides	Bakery example
Domain	The public name	example.com
DNS	The records that connect the name to services	Send web traffic to the bakery’s host and email to its mail provider
Website	The pages and functions visitors use	The menu, opening hours and order form
Web hosting	The infrastructure that stores or runs the website	The server or managed platform that returns those pages
URL	The address of a particular resource	https://example.com/menu

The domain is therefore closer to a reusable identity than to a finished website.

The bakery can rebuild its site or move to another host while keeping example.com. It changes the relevant DNS records instead of asking customers to learn a new address.

A domain can also exist without a public website.

A company might register one to protect its name, receive email, redirect visitors elsewhere or reserve it for a future project. ICANN makes the same distinction: a domain name is not the website itself and is not a complete URL.

The parts of a domain name

Let’s consider an address like shop.example.com as an example. Reading the name from right to left:

• .com is the top-level domain, or TLD;

• example is the label directly below .com;

• example.com shows the part a customer would normally register under .com; and

• shop is a subdomain created under that name.

The dots separate labels in a hierarchy. The current technical definition in RFC 9499 describes a domain name as an ordered list of one or more labels. In ordinary use, people usually mean the name they registered, such as example.com, when they say “my domain.”

The IANA Root Zone Database lists the top-level domains delegated in the global DNS. These include generic extensions such as .com and country-code extensions such as .uk.

After registering a domain, you may create subdomains without buying each one separately. The bakery could use:

• www.example.com for its main website;

• shop.example.com for online orders; and

• status.example.com for service updates.

Each subdomain can lead to the same platform or to a completely separate service.

One domain can connect to a website and email

The Domain Name System, or DNS, stores records that tell other systems what to do with a name. Different records can direct different types of traffic.

For the bakery, an A or AAAA record can connect example.com to the server running the website.

An MX record can direct messages for [email protected] to the bakery’s email provider.

Changing the website record does not automatically move the email service.

These are the records a new domain owner is most likely to encounter:

DNS record	Common purpose
A	Connects a name to an IPv4 address
AAAA	Connects a name to an IPv6 address
CNAME	Makes one hostname an alias of another hostname
MX	Identifies the servers that receive email for the domain
TXT	Publishes text used for verification and policies such as SPF or DMARC
NS	Identifies the authoritative name servers for the domain

A careless DNS change can break one service while leaving another untouched. Before replacing nameservers or editing MX records, record the existing values and confirm which service each record supports.

What happens when someone visits the domain

When a customer enters example.com, the browser needs to find the service behind the name.

1. The device asks a recursive DNS resolver for the record. The resolver may already have a cached answer.

2. If it does not, the resolver follows the DNS hierarchy until it reaches the authoritative servers for the domain.

3. The authoritative server returns the relevant record, such as the website’s IPv4 or IPv6 address.

4. The browser connects to that destination and makes an HTTP or HTTPS request for the page.

The DNS lookup finds the destination; it does not download the website. The web server or platform returns the page after the lookup is complete. Email software performs a related lookup for MX records when it needs to deliver a message.

DNS answers are cached for a period defined by their time-to-live value. That is why a record change may appear for some visitors before it appears for everyone else.

A domain is only one part of a URL

Consider this address:

https://shop.example.com/products?color=blue#sizes

• https is the scheme;

• shop.example.com is the host;

• /products is the path;

• color=blue is the query; and

• sizes is the fragment.

The domain appears inside the URL, but the URL identifies a more specific resource and may contain several additional components.

The WHATWG URL Standard defines how browsers parse these parts.

Registering a domain gives you renewable control

People often say they “bought” a domain. More precisely, the registrant receives contractual rights to use and manage the registered name for a defined term, usually one year.

Three roles are involved:

• Registry operator: maintains the registration database and infrastructure for a top-level domain.

• Registrar: sells and manages registrations for customers and communicates with the registry.

• Registrant: the person or organization named as the holder of the registration rights.

ICANN’s registration overview explains these roles. Some sellers operate as resellers for an accredited registrar, while country-code domains may follow policies set by their local managers.

Registration is renewable rather than permanent. Many generic domains can be registered for terms between one and ten years.

If the registrant does not renew, connected websites and email can stop working, and the name may eventually become available to someone else.

Use an ICANN RDAP lookup to check the sponsoring registrar and currently public registration data for a generic domain.

How to choose a domain you can keep using

Start with the name people already associate with the business or project. Say the full domain aloud and ask someone else to spell it.

This exposes awkward word breaks, easily confused letters and numbers that require repeated explanation.

Then check the full cost and risk:

1. Search the web and relevant business directories for confusingly similar names.

2. Check the WIPO Global Brand Database and the trademark registers in the markets where you will operate. Domain availability is not trademark clearance.

3. Compare registration, renewal, transfer and restoration terms instead of judging the offer by its first-year price alone.

4. Confirm eligibility or documentation rules for the extension.

5. Decide which person or legal entity should be named as the registrant.

The .com extension is familiar and works well for businesses serving several markets. A country-code extension can make a local focus clearer. A newer descriptive extension may produce a shorter name, but customers should still be able to recognize, repeat and type it.

ICANN’s Uniform Domain-Name Dispute-Resolution Policy covers certain disputes involving abusive registrations and trademark rights.

Registering an available string does not remove another party’s legal rights.

If you need a longer naming process, use Truehost’s guide to choosing a domain name before searching availability.

Protect the account that controls the domain

Someone who gains control of the registrant account may be able to redirect the website, interfere with email or attempt to transfer the domain.

Treat that account as business infrastructure.

• Use a unique password and enable multifactor authentication.

• Keep the registrant email address and phone number current.

• Use a recovery email that does not depend on the domain being protected.

• Enable auto-renew, maintain a valid payment method and still monitor the expiry date.

• Keep the transfer lock enabled unless you are completing an authorized transfer.

• Give designers and contractors only the access they need instead of sharing the main login.

• Keep registration invoices, renewal notices and a record of DNS changes.

• Ask whether the registrar and DNS provider support DNSSEC for your extension and setup.

ICANN’s domain-security guidance recommends an independent recovery address, a strong password, multistep authentication and a transfer lock.

DNSSEC helps validating resolvers detect forged DNS answers, but it does not replace account security or HTTPS.

When a name passes the spelling, trademark and cost checks, use Truehost’s domain search to check current availability and compare registration, renewal and transfer terms.

Register it under the correct person or organization, secure the account, and then connect the domain to the website and email services you actually need.