What is a domain name?

A domain is your address on the internet

Think of a domain name like the name of a shop on a high street. "Tony's Pizza" is easy to remember and tell a friend. But the postal service doesn't deliver to "Tony's Pizza" — it delivers to 14 Market Street. The name is for humans; the address is for the machinery behind the scenes.

The internet works the same way. Computers find each other using IP addresses — strings of numbers like 192.0.2.4. Nobody wants to type that, and it can change over time. So we layer a memorable name on top: example.com. That name is the domain. Its only job is to point reliably at the right numbers so you never have to.

That's the whole idea — a friendly name standing in for an address. Everything else in this article is just the plumbing that keeps the name pointing at the right place.

The anatomy of a domain name

Domains are read right to left, from the most general part to the most specific. Take blog.example.com:

The combination of the second-level domain and the TLD — example.com — is what's unique and registrable. Once it's yours, blog.example.com, shop.example.com, and mail.example.com are all yours to create at no extra cost. There's a deeper rabbit hole here (every TLD sits under an invisible "root" represented by a trailing dot), but for everyday purposes, right-to-left is all you need.

How a name becomes a website

When you type example.com and hit Enter, your domain has to be translated into an IP address before anything loads. That translation is the job of DNS — the Domain Name System, the internet's address book.

1. Your device asks a resolver. "What's the IP for example.com?"
2. DNS looks it up. The query walks from the root, to the .com servers, to the servers responsible for example.com, which hold the actual answer.
3. You get an IP back — say 192.0.2.4 — and your browser connects to it. The whole round trip usually takes a few thousandths of a second.

The domain is the question; DNS provides the answer. If you want to watch that translation happen for any name, our DNS lookup tool shows you exactly which records a domain resolves to. For the full story of how that address book works, see What is DNS? and What is an IP address?

Who's actually involved

A domain feels like a single thing you "buy," but four different parties keep it working. Here's the cast:

• The registry — runs an entire TLD and keeps the master database of every name under it. Verisign runs .com; PIR runs .org. There's exactly one registry per TLD.
• The registrar — the company you actually buy from (Namecheap, Cloudflare, GoDaddy…). They're an accredited middleman between you and the registry. See What is a domain registrar?
• ICANN — the non-profit that coordinates the whole namespace and accredits registrars, so the system stays one global, non-colliding directory.
• You, the registrant — the person or organization with the right to use the name for as long as you keep renewing it.

One honest detail people are often surprised by: you don't truly "own" a domain — you rent the exclusive right to use it, typically a year at a time. Let the renewal lapse and the name goes back on the market. (More on the registry/registrar split and the different TLD families in Top-level domains explained.)

Where WHOIS fits in

Because every registration is recorded, there's a public-facing way to ask "who registered this name, and when?" That's WHOIS (and its modern successor, RDAP). It can show the registrar, the creation and expiry dates, and the name servers a domain uses — handy for spotting a soon-to-expire domain, checking who runs a site, or troubleshooting.

These days most personal contact details are redacted for privacy, so WHOIS reveals less about individuals than it used to — but the operational facts are still public. You can look up any domain with our WHOIS tool, and we go deeper in What is WHOIS?

Domain vs website vs hosting (they're not the same)

This trips up almost everyone, so let's be clear. These are three separate things you can buy from three different companies:

You can own a domain with no website at all (parked, or pointed at email). You can move a website to new hosting without changing the domain. Keeping them mentally separate makes everything from migrations to troubleshooting far less confusing.

Choosing a good domain

If you're registering one, a few field-tested rules:

• Short and sayable beats clever. If you can't read it over the phone without spelling it, reconsider.
• Avoid hyphens and numbers where you can — they get lost in conversation and look less trustworthy.
• The TLD is a signal. .com is still the default people assume; a niche TLD can work but expect to repeat it.
• Check the WHOIS history of a previously-owned name before buying — a domain with a spammy past can carry baggage.

That's the whole system in one breath: a memorable name, rented through a registrar, recorded in a registry, translated by DNS, and queryable through WHOIS. Once you can see those moving parts separately, the rest of the domain world — TLDs, transfers, name servers — stops being mysterious and starts being just a series of steps.

Related reading: Top-level domains (TLDs) explained · What is a domain registrar? · What is WHOIS? · A brief history of domain names · What is DNS?

References: ICANN — What does ICANN do? · IANA Root Zone Database · RFC 1034 (Domain Concepts)