How to buy and connect a domain — step by step, and why it doesn't open right away

Here's an expectations trap. Buying a domain takes five minutes and a few bucks — nothing hard. But "connecting it to a site" sounds like dark magic for sysadmins. In reality, connecting is two lines in your DNS settings plus a bit of patience. And the main surprise, worth reading to the end for: when the site "doesn't open" right after you connect it — that's almost always not a breakage, but normal waiting. Let me lay it out step by step so you don't panic over nothing.

First — what's actually happening

A domain (yoursite.com) is just a nice name. Your site lives on a host's server at a numeric address — an IP, something like 76.76.21.21. DNS is the internet's phone book: it links a name to an address. Buying a domain = renting a name. Connecting it = writing into the book which address the name points to. That's all.

Step by step

1. Pick and check the name. Go to a registrar (Namecheap, Cloudflare, Porkbun, Google Domains successors). Type your desired name — it shows if it's free and the price. Real cost: .com ~$10–15/year, country domains often less. Pick something short, no hyphens — people will read it aloud.

2. Buy it — and check the cart. At checkout, turn on WHOIS privacy protection — otherwise your name, email, and phone land in a public database and the spam pours in. Most registrars include it free; just don't uncheck it. Auto-renew is up to you.

3. Find where to point it. Go to your host (Vercel, Netlify, Cloudflare Pages — wherever the site lives), find "Domains" → "Add domain." The host gives you one of two things: an IP address (for an A record) or a name like cname.vercel-dns.com (for a CNAME record). Note it down.

4. Add the DNS records at the registrar. In the domain panel, find "DNS" / "Records." Add:

   • an A record for the bare domain: name @, value — that IP.
   • a CNAME for www: name www, value — the host's address. If the host gave a CNAME for the root, follow its instructions (some use ALIAS/ANAME). Delete the registrar's old placeholder records so they don't conflict.

5. Turn on HTTPS. The padlock in the address bar. Good news: nearly every modern host issues the certificate itself, for free (Let's Encrypt) the moment it sees DNS pointing at it. Usually you do nothing — just wait for "SSL active" to light up in the host panel.

6. Wait — and don't fidget. DNS changes don't spread worldwide instantly: usually 10–60 minutes, sometimes a few hours. This is called propagation. To check whether it's spread, use dnschecker.org — type your domain and see if servers in different countries can see it.

What you'll get

In an hour or two, yoursite.com opens your site over secure https://, and so does www.yoursite.com. You can read the link aloud and put it on a business card. Congrats — you have a real address on the internet, not project-x7.vercel.app.

The logical next step is to actually be found at that address. That's about SEO and meta tags: how to tell search engines what your site is about. And if the domain is the finale and you just shipped the project, run through the pre-launch checklist so you don't embarrass yourself in front of the first visitors.

How long until the domain works?

Usually 10 minutes to an hour, occasionally up to a day. If it's been over a day — check the records on dnschecker.org and compare them with what the host asked for. The usual culprit is a typo in a record or an old placeholder record left undeleted.

Why does the site open without www but not with it (or vice versa)?

Because those are two different addresses, and each needs its own record: the bare domain via an A record, www via a CNAME. If only one works — add the missing record. The host usually redirects one to the other automatically once both records are in place.

Do I need a paid SSL certificate for https?

No. The free Let's Encrypt certificate is more than enough, and almost all hosts issue it automatically. A beginner doesn't need a paid certificate — that's marketing.