What Is a Domain, Explained Without the Jargon

A domain is the website address a person types into a browser: example.com, lix.li, mysite.co.uk. It exists for a simple reason. Computers don't find each other by name — they use numbers like 93.184.216.34. Nobody wants to memorise numbers, so names were invented.

The easiest comparison is the contacts list on your phone. You tap "Mum" and the phone dials a number. A domain works the same way: you type a name, and the internet supplies the number.

And here's the thing worth knowing up front: a domain is not sold forever. You take it for a term, usually a year at a time, and renew it. Stop paying and the name leaves you — it can end up belonging to somebody else.

Below: what the parts of an address are, how to pick an extension, what actually happens after you buy, what to do when a service asks you to "add a record", and what to look for if you need a domain for short links.

What the parts of an address are

Take blog.example.com. You read an address like this from right to left, general to specific.

• com is the extension. You don't invent it, you pick it from an existing list: com, org, co.uk, shop and hundreds of others.
• example is the name itself. This is the part you buy from a registrar. You check whether it's free and take it.
• blog is a prefix. The domain's owner invents this one. The technical word for it is a subdomain, and you'll meet that term in control panels.

That third point is the one most people don't know, and it saves money. Prefixes don't need buying. The moment you bought example.com, you also got blog.example.com, shop.example.com, go.example.com and any others you fancy. They're created in your settings in a minute and cost nothing.

Incidentally, the familiar www is a prefix just like blog. It's simply a historical one: in the nineties that was how you marked "the website lives here". Today it changes nothing, and example.com without the www works exactly the same.

How to pick an extension

Extensions come in two kinds, and the difference isn't only about looks.

Country ones are tied to a country: co.uk, de, fr, in. They read clearly as "we operate here" and usually earn more trust from local visitors. The drawback: some countries attach conditions — proving you live there, for instance, or that you have a company registered locally.

Generic ones are tied to nothing in particular, or to a meaning: com, org, net, app, shop, blog. They suit everybody.

Three pieces of advice that spare you the usual disappointments:

• read more than the first-year price. The promotional figure is bait; renewal often costs several times as much, and you'll be paying it every year;
• check the extension's rules, not just whether the name is free. A lovely short name in an exotic extension sometimes demands paperwork you don't have;
• be careful with "cheap" extensions. Spammers have made themselves at home in some of them, and mail filters and messaging apps treat them with suspicion. For a small company website that's tolerable; for links in a newsletter it isn't.

What you're actually buying

Not the name for keeps, but the right to use it for a while. Think of it as a subscription: pay for a year or several and the name is yours, and you can keep renewing indefinitely.

Three things people trip over most often.

The term runs out quietly. Nobody phones you. An expired domain first simply stops working — the website and any email on it vanish. Then comes a window where you can still get it back, but at an inflated price. After that it's released and anyone can buy it. So turn on auto-renewal, and keep an eye on the mailbox the domain is registered to: every warning goes there.

The owner's contact details go into a public database. Anyone can look up a phone number and address. Most registrars offer free or cheap privacy protection — switch it on straight away.

You can't transfer a domain immediately after buying it. If you want to change registrars you'll have to wait: transfers are normally locked for the first two months after a purchase or after a previous move. That's a general rule, not your registrar being awkward.

How a domain turns into a website

Names are looked after by a worldwide directory service, known as DNS. It holds several records for every domain, and you don't need to understand all of them. Four are enough — the four you'll actually see in a control panel.

That last line is behind nearly every bout of "I entered everything and nothing works". Records only take effect where NS points. If the domain was bought from one registrar and you're editing records at another, they simply won't do anything — you're writing in a notebook nobody reads. Work out which panel is the live one first, and edit only there.

The second cause of panic: changes don't take effect instantly. The old answer lingers in the memory of providers and browsers for a while — usually minutes, sometimes a few hours. If you did everything right and nothing has changed, wait before redoing it. Redoing it halfway through is what creates genuine confusion.

A service asks you to "add a CNAME" — what to do

Standard situation: you're connecting a domain to some service, and it asks you to add a record. Here's the order.

1. Log in to the panel of whichever registrar or host manages your domain (see NS above).
2. Find the section called something like "DNS records" or "Zone management".
3. Create a record of the type the service asked for, and copy the value exactly as given — a stray space or a dropped dot at the end breaks the whole thing.
4. Save, then wait. Check back in a few minutes rather than immediately.

One detail can catch you out. A CNAME record can't be placed on a name with no prefix — that is, on example.com itself. On go.example.com, fine; on example.com, no. The reason is technical: the bare name already holds the domain's own administrative data, and a CNAME demands that nothing else sits alongside it. Those two requirements don't combine.

What to do if you're in that position: use a prefix (go.example.com instead of example.com), which is usually what services suggest anyway. Or add an A record with a server number, if the service offers that route. Some DNS providers have their own workarounds named ALIAS or ANAME — they work, but they're a quirk of that particular provider, and they won't come with you if you move.

What "domain connected" means

From outside it looks like a single button. In fact a domain passes through several states, and it helps to know which one it's in.

First it's awaiting setup: the service has it on file, but the name doesn't point at the service's servers yet. The service keeps checking the directory to see whether the right records have appeared. As soon as they match, the domain becomes working. If something breaks later — records overwritten, the domain not renewed, a move to a different provider — it drops into error. The fourth state, disabled, is when it's been switched off by hand or has fallen outside your plan.

The HTTPS padlock is a separate matter. The certificate behind it is issued automatically, but only once the records are already in place. Hence the correct order: records first, padlock second. It doesn't work the other way round.

And the most practical conclusion of the lot: a green "working" tick means everything was fine as of the last check. It is not a promise about the future. A domain somebody forgot to renew will drop off — and take every link that lived on it with it.

If you need a domain for short links

This is its own job, and the criteria aren't the ones you'd use for a website.

• length matters more than beauty. The domain goes into every single link. With a thousand links out there, every extra character gets seen a thousand times;
• a prefix on a domain you already own is the simplest route. go.yoursite.com is set up with one record, needs no new purchase, and looks familiar straight away to anyone who knows you;
• find out the name's history. A domain that was released may have sent spam in a previous life and landed on blocklists. Short links are especially sensitive to this: messaging apps and mail filters look at the domain, not at where it leads;
• the padlock is non-negotiable. A link without HTTPS puts people off more than a long address does.

How to connect your own domain here, and what you'll see in the stats afterwards, is on the custom domain for short links page. What changes in trust and in the numbers once you move to your own name is covered in the article on custom domains.

Common mistakes

• editing records in a panel that doesn't actually manage the domain;
• redoing the setup after a minute, without waiting for the old answer to expire;
• copying a record's value with an extra space, or without the trailing dot;
• forgetting to renew, because the warnings went to a mailbox nobody opens any more;
• buying a name on a promotion and discovering the renewal price a year later;
• trying to put a CNAME on a name with no prefix and concluding the service is broken.

In short

A domain is a name you take on for a term, not something you buy outright. In blog.example.com, the extension com is picked from a list, example is bought, and the prefix blog is created free and in any quantity you like. Records only work in the panel that NS points to, and they don't update instantly. A CNAME lives on a prefix but not on the bare name — which is exactly why short links usually hang off something like go.yoursite.com. And a green "domain working" tick reports the last check, not a guarantee that it will stay that way.

What happens to the link itself once the domain is up is covered in the piece on how URL shorteners work.