Guide
Beyond .com for builders shipping many projects
You’re shipping more than one thing. Each project needs a name people can type, remember, and trust — often before the product is finished.
.com is fine when it’s short and affordable. Most of the time it isn’t. This guide is the short version of what matters: enough domain literacy to decide fast, then a clear bias toward creative extensions — the same craft we collect on curated.domains.
01 — Basics
What a domain is
A domain is the human-readable address of a site (curated.domains), not the hosting and not the full URL. Hosting is where files live; DNS is how the name points there.
The three parts
blog.curated.domains = subdomain · main name · TLD (extension). You register the main name + TLD. Subdomains are free once you own the domain.
blog
.
curated
.
domains
What a TLD is
The ending — .com, .io, .fyi, .ai. Generic, country-code, and newer niche endings all carry different associations. The ending is part of the brand people say out loud.
DNS in one breath
Type a name → resolver asks nameservers → IP comes back → site loads. Change nameservers at your registrar (Cloudflare is a strong default). Propagation: minutes to a day.
You don’t need more theory. You need a naming system that scales across projects.
02 — Buying
Buy for the renewal, not the first year
Intro pricing lies. Check multi-year cost, WHOIS privacy, lock and transfer rules, and support before you pay.
Compare once, then move on
Side-by-side (Domcomp / TLD-List) → verify renewal + privacy → register → point DNS. Don’t over-optimize while the product waits.
01 Compare renewals
02 Register
03 Point DNS
Registrars (principles, not a forever ranking)
Beginner-friendly + predictable renewals
Transparent low renewals for experiments
At-cost + best DNS if you already live in Cloudflare
Portfolio hygiene
One vault: domain → project → registrar → renew date → DNS
Auto-renew only on names you’d be sad to lose
Park or redirect leftovers
Prefer endings you can reuse as a studio pattern (.fyi, .supply, .wtf families)
03 — Beyond .com
When to skip .com
Skip when good .com is taken or absurdly priced, when the extension adds meaning (.ai, .app, .fyi), or when a short creative name beats a long exact-match .com. Keep .com when short, clean, and within reason.
Extensions as brand signal
phrase completed by TLD
openrol.es / someo.ne
Patterns that work
1. Wordplay / phrase — TLD finishes the sentence
2. Category stamp — extension announces the job
3. Studio system — same ending across projects
4. Short over clever-long — under ~12 characters typed
How to pick (fast)
1. Say the full name out loud
2. Check availability + renewal on 2 registrars
3. Scan real usage
4. Commit and ship
Premium names
Pay up only when the name is the product surface; otherwise ship on a strong creative TLD.
Domains are part of product design. For multi-project founders, the win is repeatable naming taste: clear signal, short strings, extensions that work as hard as the brand.
curated by aaali.xyz