Domain name ideas for your next project

"Give me some domain name ideas" is one of the most common things a founder types into Google — and one of the worst ways to actually get a name. Idea lists rot in a year; what works is a repeatable approach: pick a naming style, draft a small set of candidates, and verify availability directly against the registry before you fall in love with any of them. This guide walks through both.

The seven naming styles that actually work

Almost every good developer-domain name fits one of these seven categories. Pick the category first; the candidates shorten dramatically.

  • Brandable — coined names with no prior meaning. Examples: Vercel, Stripe, Clerk. Hard to find, but the strongest long-term choice because you own the namespace.
  • Keyword-based — direct, descriptive names. Examples: fastapi, dotenv, mailgun. Easiest to draft, hardest to register short.
  • Portmanteau — fused words. Examples: netflix, Mailchimp. Constraints help: pick two short words, force the merge, drop letters.
  • Minimal — short, often two or three letters. Examples: sh, ln, hx. Almost always aftermarket at this point.
  • Command-style — imperative verbs. Examples: getscreen, bumpversion, render. Reads naturally in a terminal context.
  • Authority-style — conceptual, aspirational. Examples: Vercel (from "vertical" and "excel"), Loom, Coolify. Subjective; needs a small story.
  • Tool-style — names ending in -hub, -box, -kit, -io. Examples: Semverhub, Kitbox. Easy to draft, but the suffixes are saturated — expect to compromise.

Ideas by project type

Startups and SaaS

Pick brandable first, keyword-based second. Use .io as the default TLD — it is still the strongest "I am a software company" signal in 2026. Run a name through the choose-a-domain-name checklist before you commit.

Developer tools, SDKs, and libraries

Command-style or keyword-based, under .dev. Short is critical here; engineers type these names into terminals and URLs. Two-syllable command-style names (bumpversion.dev) outperform longer brandable names for tool adoption.

APIs and SDKs

Keyword-based names under .dev or .io. The name should describe what the API does, not the company behind it — engineers search by function, not by brand, when evaluating integrations.

CLIs and shell tools

Short command-style or minimal names under .sh. The name is the install command — if your installer is curl yourtool.sh | sh, the name does half the marketing.

Portfolios and blogs

Brandable or minimal under .dev. Personal portfolios have more lenient naming — your name or a clearly personal coinage works fine. The audit here is: does the name feel like a person's site, not a company's?

Open source projects

Keyword-based or tool-style under .dev. Pattern: name = function + suffix. Avoid brandable names for OSS — it makes the project feel like a company's product rather than a community one.

Web3 and crypto

Brandable or minimal under .xyz. The community reads .xyz as the modern home for on-chain projects; the convention is established.

How to generate ideas in practice

Three options, in order of effort:

  • Brainstorm with constraints — pick a naming style from the seven above, write 20 candidates in 5 minutes, then run them through the checklist.
  • Use namebox.dev — describe your project in plain language, pick 1–2 naming philosophies, and get 12 candidates per search, each verified available via RDAP against the registry in real time.
  • Mind map with peers — best for brandable names. Trade off rounds until one clicks.

The step that kills most name ideas

More than 80% of drafted names turn out to be already registered, and most "is this free?" tools lie — they check DNS, not the registry. A name can be registered without DNS, parked without DNS, or DNS can be stale. The only authoritative source is the registry itself, queried via RDAP (RFC 7483).

That is what namebox.dev does internally. Each candidate shown as available has been verified against the authoritative registry at the moment of your search. Try a search and the first 12 results you see are real — at this moment — not stale.

Next steps

Find a verified-available domain name for your project.