What Domains Do Developers Actually Use? Real Data From Hacker News

Domain advice articles are everywhere. They tell you to use .com, consider .io, maybe try .dev. But what do developers actually choose when they launch their own projects?

We analyzed current Show HN submissions — real projects launched by real developers — to see which TLDs, hosting patterns, and domain strategies are being used in practice. The results challenge some conventional wisdom.

The Data: Show HN Domain Choices (March 2026)

Here is a snapshot of domain choices from recent Show HN projects, ordered by community engagement:

Key Finding 1: GitHub Is the Most Common "Domain"

The most striking pattern is that nearly half of Show HN projects use no custom domain at all. They launch directly on GitHub — either as a repository (github.com/user/project) or using GitHub Pages (user.github.io).

This makes practical sense. Open-source libraries, CLI tools, and developer utilities do not need a custom domain. The GitHub URL serves as both hosting and discovery. A README file replaces a landing page.

For projects that DO need a web presence — SaaS tools, interactive demos, consumer-facing products — custom domains become important. But the developer community clearly does not consider a custom domain a prerequisite for launching.

If you are building an open-source project, starting on GitHub and adding a custom domain later is a perfectly valid strategy. We covered this approach in our bootstrapped founder domain strategy guide.

Key Finding 2: .io Remains the Developer Default

Among projects with custom domains, .io is the most represented TLD for developer tools. Unfudged.io, a version control tool that garnered 129 points, exemplifies the pattern: technical product, developer audience, .io domain.

The .io extension has maintained its position as the go-to TLD for developer-focused products despite occasional concerns about its status as the British Indian Ocean Territory ccTLD. Developers choose .io because:

• Signal: It instantly communicates "this is a tech product"
• Availability: Short, memorable names are more available on .io than .com
• Community recognition: The HN/developer community treats .io as a legitimate, respected extension

That said, .io is not cheap — typically $30-40/year. For budget-conscious developers, alternatives exist. Our comparison of .com vs .io vs .ai breaks down the tradeoffs.

Key Finding 3: Unusual TLDs Perform Well

Some of the most successful projects use TLDs that rarely appear in domain advice articles:

.us — nowigetit.us (253 points)

The highest-performing custom domain in our sample uses .us, the United States country-code TLD. "Now I Get It" is a tool that translates scientific papers into interactive webpages, and the .us domain works because it doubles as a sentence: "now I get it, US."

.us domains are:

• Affordable ($8-12/year at most registrars)
• Available (far less saturated than .com)
• Restricted to US persons and entities (which limits speculative registration)
• Rarely discussed in startup domain advice

The restriction to US registrants actually creates an advantage: fewer speculative registrations means better name availability. If you are US-based and want a short, memorable domain, .us is worth considering.

.studio — kuber.studio (20 points)

A terminal-style portfolio site using the .studio TLD. This extension works beautifully for creative and design-focused projects. At $20-30/year, it is affordable and instantly communicates a creative or professional studio identity.

.xyz — smashlanding.xyz (4 points)

.xyz remains popular for experimental and early-stage projects. At $1-10/year (often with first-year promotions under $1), it is the cheapest way to get a custom domain for a project. The trade-off is lower brand perception compared to .com or .io.

Key Finding 4: .com Is Underrepresented

In our sample, only one project used a .com domain (topomaker.com). This contradicts the conventional wisdom that .com is essential for any web project.

Several explanations:

• Availability: Good .com names for developer tools are largely taken
• Price: Aftermarket .com domains are expensive compared to registering on alternative TLDs
• Audience: The HN developer community values product quality over domain prestige
• Culture: Show HN is a launch venue where novel TLDs are not penalized

This does not mean .com is irrelevant — it remains the most recognized and trusted extension globally. But for developer-focused projects targeting a technical audience, the data suggests .com is not a prerequisite for success.

For a broader perspective on choosing extensions, see our complete guide to domain extensions.

Key Finding 5: Subdomains and Creative Structures

Some developers use subdomain structures rather than dedicated domains:

• vote-demo.dapp32.com uses a subdomain of the developer's personal domain
• GitHub Pages projects use user.github.io subdomains

This "launch under a parent domain" approach has trade-offs:

Pros:

• Zero additional cost
• Instant setup
• Groups multiple projects under one identity

Cons:

• Less professional for customer-facing products
• Harder to build brand recognition
• SEO value accrues to the parent domain, not the project

For MVP testing and side projects, subdomains work fine. For anything you want to grow into a standalone product, a dedicated domain is worth the $10-40/year investment.

What This Means for Your Domain Strategy

For Developer Tools and Open Source

Start on GitHub. Add a custom domain when you have traction. When you do buy a domain, .io and .dev are strong choices for the developer audience. Do not feel pressured to buy a .com unless you are targeting non-technical users.

For SaaS and Web Apps

A custom domain matters more here because you are asking users to trust your product with their data and workflow. .com, .io, .app, and .dev all work. Use DomyDomains to search availability across all options simultaneously.

For Creative and Portfolio Projects

Explore niche TLDs. .studio, .design, .art, .photo — these extensions exist specifically for creative professionals and can be more memorable than a generic .com. The kuber.studio example shows that the HN community responds positively to creative TLD choices.

For Budget Projects

.xyz (under $10/year) and .us ($8-12/year) offer the best value for custom domains. Both appear in successful HN projects, proving they do not carry significant stigma in the developer community.

The TLD Hierarchy (According to Actual Usage)

Based on our analysis of real developer launches, here is the practical TLD hierarchy:

1. No custom domain (GitHub/GitLab) — Most common for open source
2. .io — The developer default for products
3. .com — Still strong but less dominant than expected
4. Niche TLDs (.studio, .us, .xyz) — Growing and well-received
5. .dev / .app — Increasingly popular but not yet dominant in our sample
6. Subdomains — Valid for MVPs and multi-project developers

This hierarchy will continue to evolve as new TLDs gain recognition and as the developer community's preferences shift. What matters most is choosing a domain that your specific audience will respect and remember.

The Bottom Line

The conventional wisdom says "always get a .com." The data from real developer launches tells a different story: the best developers choose the domain that fits their project, their budget, and their audience — whether that is .io, .us, .xyz, .studio, or no custom domain at all.

The domain that matters is the one you actually launch on. Search DomyDomains to find available names across 400+ extensions, pick one that feels right, and ship your project. The HN community will judge your code, not your TLD.