Developer Tool Domain Name: .dev, .io or .com?
Published 2026-10-04 · Updated 2026-11-05 · By Aaron Kempf
Startups .COM Developer Domains Planning TLD
A developer tool's name gets typed more than it gets said. It appears in install commands, import statements, config files and error messages. So a developer tool domain name has a different job from a consumer brand: it has to be short, easy to type without a typo, and match the package name people will install.
Start with the package name, not the domain
Before you look at domains, check the places developers will actually type your name:
- Package registries such as npm, PyPI, crates.io or RubyGems, depending on your language.
- GitHub, for the organisation and repository name.
- Your command name, if it's a CLI. Short commands get typed hundreds of times a day.
If the package name is taken, the domain doesn't help much. People will install the wrong thing. Find a name that's free in the registry first, then look for a matching domain.
Choosing the extension
.dev is run by Google Registry and is on the HSTS preload list, so every .dev site must use HTTPS. It tells visitors straight away that this is for developers. It's a natural fit for documentation and tools.
.io has been the default for developer startups for years and is widely recognised. It has some open questions about its long-term status, covered in our .io vs .com guide.
.com is still the safest if you plan to sell to managers or companies outside engineering. Procurement teams and executives type .com by habit.
Many teams use a .dev for the docs and keep a .com for the company. A TLD Sweep shows all three at once for up to 10 names.
Naming a developer tool domain name that lasts
- Keep it under eight characters if you can. It'll appear in commands like
npx yourname init. - Avoid letters that look alike in monospace fonts: l, 1 and I, or O and 0.
- Avoid hyphens. Some registries and languages handle them differently; underscores and hyphens get mixed up in imports.
- Make it searchable. A common English word is easy to type but hard to find in search results. "Grain" is lost; "grainctl" is findable.
- Don't name it after the language unless it's only ever for that language. "Pyfast" is awkward if you add a Go version.
A worked example
A small team (invented for this example) is building a CLI that checks database migrations before deploy. Their first idea is free on GitHub but taken on npm. Their second, a six-letter invented word from the Pronounceable generator, is free in npm, PyPI and GitHub. The .dev is open, the .com is parked. They use the .dev for docs, put the install command on the home page, and note the .com to revisit later.
What to check before you commit
- Is the name free in every package registry you'll publish to?
- Does it look unambiguous in a monospace font?
- Can you search for it and find your project, not a dictionary?
- Is the matching GitHub organisation free?
Common mistakes
Registering the domain first. The package name is the one people type.
Choosing a dictionary word. Easy to say, impossible to search for.
Ignoring the CLI. A long name becomes a long command. People will alias it, and your brand disappears.
Related reading
- Open Source Project Name: Pick One and Check the Domain
- SaaS Domain Name Ideas That Outlast the First Feature
Frequently asked questions
Does a .dev domain need HTTPS?
Yes. .dev is on the HSTS preload list, so browsers only load it over HTTPS.
Should the domain match the package name exactly?
Ideally, yes. If it can't, keep the package name exact and add a short word to the domain, like "get" or "use."