Start reading
Web Updated March 28, 2026 13 min read

What Is a Domain Name? The Internet Address Book Version

A beginner-friendly explanation of domain names, DNS, registrars, hosting, records, and why a domain is not the same thing as a website.

A clean address bar shape with map pin and soft connected route path
A domain name — the address that helps browsers find a destination.

A domain name is one of those internet things that feels simple until someone asks you to explain it.

Then suddenly you are saying words like “registrar,” “DNS,” “nameserver,” “A record,” and “propagation,” and everyone in the room starts looking for a window to escape through.

So let’s make it less dramatic.

A domain name is the human-friendly address of a website.

Something like:

janedecodes.com

It is the name people type, remember, share, print on business cards, put in emails, and occasionally buy at 1:13 AM because an idea felt brilliant at the time.

Not that I know anything about that.

But here is the part beginners often miss:

A domain name is not the website itself.

It is not the files.

It is not the hosting.

It is not the design.

It is not the server.

It is the name that points people in the right direction.

Think of it like the sign on the front of a building.

Very important.

Not the building.

The simple version

A domain name is a readable internet address that points to online resources.

Most commonly, people use domain names to open websites.

Instead of typing a numeric IP address like:

203.0.113.42

you type a name like:

example.com

Humans prefer names.

Computers prefer numbers.

DNS is the system that helps those two preferences stop arguing.

When someone opens a website, the domain helps the browser find the right server. I explained the full behind-the-scenes process in what happens when you open a website, but the short version is this:

The domain is the name. DNS finds where it points. The server sends the website.

That is the basic chain.

Name → address → server → website.

Not magic.

Just several systems politely passing the request along before anyone notices.

Domain vs website vs hosting

This is the confusion I see most often.

People say:

“I bought a website.”

But often what they actually bought was a domain name.

Or hosting.

Or a website builder plan.

Or all three.

These are different things.

Domain name

The domain is the address.

For example:

janedecodes.com

It is what people type into the browser.

Website

The website is the content people see.

Pages, images, text, styles, scripts, articles, buttons, forms, all the visible and functional parts.

Hosting

Hosting is where the website lives.

It is the server or service that stores the website files or runs the website application.

Here is the house analogy, because the internet becomes less annoying when we turn it into real estate for five minutes:

  • Domain name = the street address.
  • Hosting = the land/building where things live.
  • Website = the actual rooms, furniture, signs, doors, and slightly questionable decorating choices.

If you own a domain but have no hosting or website connected, you have an address pointing to nowhere useful.

If you have a website but no domain, people may still access it through some temporary or technical address, but it is not very friendly.

If you have hosting but no website files, you have an empty building.

Congratulations, you have digital real estate with no chairs.

What happens when you buy a domain

When you buy a domain, you are not buying it forever in the same way you might buy a spoon.

You are registering the right to use that domain for a period of time.

Usually one year or more.

You register it through a domain registrar.

A registrar is a company allowed to sell and manage domain registrations.

When you register a domain, you usually choose:

  • the domain name;
  • the extension, such as .com, .net, .org, or another TLD;
  • the registration period;
  • contact details;
  • privacy settings, if available;
  • DNS or nameserver settings.

After that, the domain belongs to your account for as long as you keep renewing it.

This is important:

If you forget to renew a domain, you can lose it.

Domains can expire.

Expired domains may enter grace periods, redemption periods, auctions, or become available for someone else later.

That is why people who care about a domain usually enable auto-renewal.

A domain expiring is the internet version of forgetting to pay rent on your address.

The furniture may still exist, but now nobody knows where to send visitors.

What is a TLD?

TLD stands for top-level domain.

It is the ending part of a domain name.

For example:

  • .com
  • .org
  • .net
  • .io
  • .dev
  • .ai
  • .co
  • .info

In janedecodes.com, the TLD is:

.com

The main name is:

janedecodes

Together, they form the domain:

janedecodes.com

Some TLDs are general. Some are associated with countries. Some are popular in certain industries. Some are trendy for a while and then start appearing in pitch decks with too many gradients.

The TLD can affect how a domain feels.

.com still feels familiar and standard to many people.

.org often feels nonprofit or community-oriented.

.dev feels technical.

.ai feels modern and AI-related.

Country-code domains like .de, .fr, .uk, or .jp can suggest region or market.

The TLD does not automatically make a site trustworthy.

A bad website can live on a nice domain.

A good website can live on an unusual domain.

But the domain ending does shape first impressions.

And first impressions are annoyingly powerful.

DNS: the address book part

DNS stands for Domain Name System.

This is the system that helps connect a domain name to the correct server or service.

When your browser needs to open a domain, DNS helps answer the question:

Where does this domain point?

DNS records are the little instructions behind the domain.

They tell the internet what to do with requests.

Common records include:

  • A record
  • AAAA record
  • CNAME record
  • MX record
  • TXT record
  • NS record

This is the part where beginners often feel like the website has turned into a filing cabinet.

Fair.

DNS is not glamorous.

But it is extremely important.

If DNS is wrong, your website may not open, email may not work, or visitors may end up in the wrong place.

DNS is the quiet infrastructure that nobody thinks about until it breaks.

Like plumbing, but with more acronyms.

The most common DNS records

You do not need to memorize every DNS record on day one.

But knowing the common ones helps.

A record

An A record points a domain or subdomain to an IPv4 address.

For example:

example.com → 203.0.113.42

This is one of the most common ways to point a domain to a server.

AAAA record

An AAAA record points to an IPv6 address.

IPv6 addresses are longer and look more dramatic, as if an IP address joined a science fiction franchise.

CNAME record

A CNAME record points one name to another name.

For example:

www.example.com → example.com

It is often used for subdomains.

MX record

An MX record tells the internet where email for the domain should go.

If your domain email is not working, MX records are one of the first places people look while quietly developing a headache.

TXT record

A TXT record stores text information.

It is often used for verification and email security settings like SPF, DKIM, and DMARC.

TXT records are the internet equivalent of leaving a note that says:

Yes, this domain is allowed to do this.

NS record

An NS record tells which nameservers are responsible for the domain’s DNS.

Nameservers are the systems that hold and answer DNS records for the domain.

If DNS is the address book, nameservers are the people holding the address book and insisting they know where everything is.

What is a subdomain?

A subdomain is a part added before the main domain.

For example:

blog.example.com
shop.example.com
app.example.com
support.example.com

In these examples, blog, shop, app, and support are subdomains.

Subdomains can point to different parts of a website or even different services.

For example:

  • www.example.com might show the main website.
  • shop.example.com might show an online store.
  • app.example.com might show a web application.
  • help.example.com might point to a support platform.

Subdomains are useful because they let one domain organize different areas.

But they also need DNS settings.

A subdomain does not automatically work just because you thought of a cute name for it.

Unfortunately.

The internet still wants records.

What is “www”?

The www part is technically a subdomain.

That means:

www.example.com

and:

example.com

can be treated as different addresses unless configured to work together.

Many websites make both versions work.

Usually one redirects to the other.

For example:

www.example.com → example.com

or:

example.com → www.example.com

Which one should you use?

For most small websites, it does not matter much as long as you are consistent.

Pick one as the main version and redirect the other.

Consistency helps users, search engines, analytics, and your own sanity.

I personally like fewer unnecessary letters, but www has been around long enough that it probably deserves a chair.

DNS propagation: why changes take time

When you update DNS records, the change may not appear everywhere instantly.

This is called DNS propagation.

The word makes it sound like DNS records are tiny plants spreading across the internet.

Not quite.

The delay usually happens because DNS answers are cached.

Different systems may remember old records until their cache expires.

That cache time is influenced by something called TTL, which stands for Time To Live.

A shorter TTL can make updates refresh sooner.

A longer TTL can make old answers stick around longer.

This is why you might update a domain, check it from one device, and see the new site, while another person still sees the old one.

Everyone is not losing their mind.

Probably.

They may just be seeing cached DNS.

Propagation can take minutes, hours, or sometimes longer depending on settings and providers.

This is also why “I changed DNS five minutes ago and it still does not work” is a very common sentence in web work.

A sentence usually spoken with emotional damage.

Domain privacy and ownership

When you register a domain, ownership details may be connected to registration records.

Depending on the domain extension and registrar, some contact information may be protected or hidden through privacy services.

This matters because domains are valuable.

A domain can represent a brand, business, project, identity, or long-term idea.

If you lose access to the registrar account, forget renewal, or let someone else control the domain, you can create serious problems.

A few practical habits help:

  • use a secure registrar account;
  • enable two-factor authentication;
  • keep renewal active;
  • use an email address you control;
  • keep payment details updated;
  • do not let random people register critical domains for you;
  • document where DNS is managed.

That last one sounds boring until you are trying to fix email at 11:40 PM and nobody remembers where the DNS lives.

Documentation is not glamorous.

Documentation is future-you being less angry.

Common beginner mistakes

Domains are simple in concept but easy to mismanage.

Here are mistakes I would avoid.

Mistake 1: Thinking the domain and website are the same thing

They are connected, but not the same.

You can own a domain with no website.

You can build a website before connecting a domain.

You can move a website to new hosting while keeping the same domain.

The domain is the address.

The site is what visitors see.

Mistake 2: Changing DNS without knowing what existing records do

This is how email disappears.

A person points the domain to a new server, deletes old records, and suddenly nobody receives mail.

DNS records may control the website, email, verification, analytics, and other services.

Before changing DNS, take a screenshot or backup of existing records.

Tiny boring habit.

Huge future benefit.

Mistake 3: Forgetting about www

If www does not work, some visitors may think the website is broken.

Set up both the root domain and www, then redirect one to the other.

Mistake 4: Not checking HTTPS

A domain pointing to the right server is not the whole job.

The site should also have HTTPS configured.

Without a valid certificate, browsers may show warnings.

Browser warnings are not exactly the warm welcome most websites are going for.

Mistake 5: Forgetting renewal

If a domain matters, enable auto-renewal.

Also make sure the payment method works.

A domain expiring because of an old bank card is the kind of avoidable chaos that deserves its own tiny villain soundtrack.

A tiny glossary

Domain name

A domain name is a human-readable internet address, such as example.com.

Registrar

A registrar is a company where you register and manage domain names.

TLD

A TLD is the ending of a domain, such as .com, .org, .net, or .ai.

DNS

DNS is the system that connects domain names to the correct servers or services.

DNS record

A DNS record is an instruction that tells the internet how to handle part of a domain, such as where the website or email should go.

A record

An A record points a domain to an IPv4 address.

CNAME record

A CNAME record points one domain name to another domain name.

MX record

An MX record tells the internet where email for the domain should be delivered.

Nameserver

A nameserver is a server that stores and answers DNS records for a domain.

Subdomain

A subdomain is an extra part before the main domain, such as blog.example.com.

DNS propagation

DNS propagation is the delay that can happen while DNS changes update across different systems and caches.

HTTPS

HTTPS is the secure version of HTTP. It helps protect the connection between a browser and a website.

My take

A domain name is not the website.

It is not the hosting.

It is not the files.

It is the name that helps people find the right place.

That sounds small, but it is one of the most important parts of having anything online.

A good domain is memorable.

Good DNS settings make it work.

Good hosting gives it somewhere to point.

A good website gives visitors something worth seeing when they arrive.

The beginner-friendly chain is:

domain → DNS → server → website

Once that chain makes sense, a lot of web setup becomes less mysterious.

Still occasionally annoying.

Still full of acronyms.

Still capable of making grown adults whisper “why is email broken” into the night.

But no longer magic.

Just names, records, servers, and a browser trying very hard to make the internet look simple.

Jane Calder, writer behind Jane Decodes

Jane Calder

I'm Jane Calder, the writer behind Jane Decodes. I research AI, crypto, 3D, web technology, and strange science rabbit holes, then turn them into plain-English explanations for people who like learning but dislike being attacked by jargon.

Usually powered by coffee, browser tabs, and the stubborn belief that almost anything can be explained better.

Related posts