August 8, 2026 · 3 min read
Buying a domain: registrars, ICANN, and WHOIS
What you're actually paying for when you buy a domain, how ICANN accredits the registrars that sell to you, what ICANN Lookup shows about any domain — and why owning a name still doesn't point it anywhere. Part 2 of 5.
← Part 1 — From localhost to a live URL covered getting a free URL with no domain at all. This part is for when you're ready to buy one — what you're actually purchasing, and from whom.
Where we are in the journey
A domain is a lease, not a deed
You don't "own" arytripathi.com the way you own a laptop. You hold an exclusive,
renewable-annually lease on that name, recorded in a global registry. Stop paying, and it
eventually goes back into the pool for anyone to register. That's not a gotcha — it's what makes
the whole system work: there's exactly one arytripathi.com, ever, and the registry is what
guarantees that.
The organization that coordinates this globally is ICANN (Internet Corporation for Assigned Names and Numbers) — a nonprofit, not a company you interact with directly. ICANN doesn't sell domains. It accredits registrars — Hostinger, GoDaddy, Namecheap, and hundreds of others — who compete on price, support, and features while all ultimately answering to the same rules.
Who actually controls a domain name
ICANN never sells you anything directly. It accredits registrars to sell on its behalf — which is why the same .dev or .com name costs slightly different amounts at different registrars, but is governed by the same global rules underneath.
That's why the same .dev name can be $12/year at one registrar and $18/year at another, with
identical underlying guarantees — you're comparing storefronts, not the product.
Registrar vs. hosting — the confusion that costs people hours
Buying a domain from Hostinger does not mean your site is hosted on Hostinger. A registrar sells you the name. Where your site's files actually live is a completely separate decision — and often a completely separate company, as this whole series will show.
Looking up any domain: ICANN Lookup / WHOIS
Every registered domain has a public record — historically called WHOIS, now fronted by ICANN's own lookup.icann.org tool. Paste in any domain and you'll get back something like this:
ICANN Lookup / WHOIS — illustrative record
lookup.icann.orgPlaceholder values — not a real domain. Registrant details on almost every real lookup today show “REDACTED FOR PRIVACY” too: ICANN requires registrars to offer privacy redaction, and nearly everyone takes it. What’s never hidden is the registrar and the nameservers — which is exactly the information you actually need.
A few things worth knowing how to read here:
- Registrar and Name Server rows are never hidden — they're the operationally important facts, and they're what you'd check first if you were debugging why a site isn't loading.
- Registrant details (the actual person or company) are almost always redacted today. ICANN requires registrars to offer privacy protection, and nearly every registrar now applies it by default — partly because of GDPR, partly because unredacted WHOIS became a spam and harassment vector for two decades.
- The expiry date matters more than people think. Domains that lapse get released, sometimes bought within hours by domain resellers. Auto-renew is worth turning on.
What buying a domain does not do
This is the part every beginner gets wrong at least once: buying the domain doesn't connect it to anything. Registration just puts your name in the registry with your registrar attached to it. Nobody typing it into a browser reaches your site yet.
Owning the name is not the same as pointing it anywhere
A registrar record just says who owns the name. Getting a browser from that name to an actual server is a completely separate system — nameservers, which is where Part 3 picks up.
The system that closes this gap — turning a registered name into an address a browser can
actually route a request to — is DNS, and specifically nameservers, which is dense enough to
deserve its own part. Part 3 covers exactly that: what a nameserver is, why we pointed
arytripathi.com and aryantripathi.dev at Cloudflare instead of leaving them on the
registrar's default DNS, and a full animated walkthrough of that migration.