What Is a Domain Name?

A domain name is a readable label for a place on the internet. When someone types makerlaunch.com into a browser, DNS (the internet's address book) figures out which server actually hosts the site. Humans remember words; computers remember IP addresses and hostnames — domains bridge the two.

You do not own a domain forever. You register it yearly through a registrar — companies like Namecheap, Cloudflare, Google Domains, or Porkbun. Think of it like renting a street address: you pay to keep the name pointed at your building (your app on a host).

The part after the dot is called a TLD (top-level domain): .com, .io, .dev, .app, and hundreds more. The part before the dot is yours to choose, as long as nobody else already registered it.

First launches almost always use a free subdomain from your host: yourproject.vercel.app, yourproject.up.railway.app, or similar. That URL is a valid, shareable launch address. You do not need to buy a domain to go live.

Domains matter when you want a professional brand, easier sharing, or email at your own address. Investors, customers, and press expect myproduct.com more than myproduct-7f3a2.vercel.app — but many successful products started on host subdomains and added custom domains weeks later.

If you do add a custom domain, your host and framework need to know about it. Django's ALLOWED_HOSTS, Next.js config, and cookie settings may need updates. SSL certificates (the padlock in the browser) must be active. Skipping these steps causes 'site can't be reached' or certificate errors even when your app works fine on the default host URL.

Planning ahead saves confusion: decide your canonical URL (www or non-www), document which DNS records your host requires, and test in an incognito window after propagation.

Imagine you built a recipe app with Cursor and deployed it to Vercel. Right now your live URL is tastyrecipes.vercel.app. Friends can use it today — no domain purchase required.

You buy tastyrecipes.com from Cloudflare for about $10/year. In Vercel's dashboard, you add the domain and Vercel shows DNS instructions: usually a CNAME record pointing www to cname.vercel-dns.com, plus an A record for the root domain.

You paste those records into Cloudflare's DNS panel. After 15 minutes to 48 hours (propagation), tastyrecipes.com loads the same app as tastyrecipes.vercel.app. You update any hardcoded URLs in emails or OAuth redirect settings to use the new domain.

Until propagation finishes, keep sharing the vercel.app URL. Both addresses can work simultaneously once DNS is correct.

A host subdomain is free and instant. Vercel, Railway, Render, and Netlify generate one when you deploy. It includes HTTPS automatically. Limitations: long URLs, less brand control, and the hostname reveals your host.

A custom domain costs money annually but looks professional. You control the name, can switch hosts later (by updating DNS), and can add email (hello@yourapp.com) through services like Google Workspace or Fastmail.

Many makers follow this path: launch on the free subdomain → gather feedback → buy a domain when sharing outside close friends → connect DNS on a quiet afternoon → redirect old links if needed.

Step one: buy the domain at a registrar. Step two: in your hosting dashboard, add the custom domain. Step three: copy the DNS records your host provides into your registrar (or use the registrar's nameservers if the host manages DNS). Step four: wait for propagation and verify the padlock icon.

Some hosts (Vercel, Cloudflare Pages) offer integrated domain purchase. That reduces copy-paste errors but is not required — any registrar works if you enter records correctly.

Keep your registrar login in a password manager. Domains expire if payment fails, and expired domains can be snapped up by someone else.