← Back to the DNX Blog
Extension guides · 5 min read
What does a .dev domain signal?
.dev tells technical audiences this is a builder’s surface — docs, tools, sandboxes, or the product. Use it when that promise is true.
Summary
- .dev is widely read as “for developers” — documentation, APIs, tools, and technical products.
- Browsers treat .dev as HTTPS-only via HSTS preload expectations; plan certificates from day one.
- Strong for docs portals, staging naming that is public-facing, and developer-first brands.
- Weaker for non-technical consumer brands that need a more general ending.
A `.dev` name sets a tone before the homepage loads: builders welcome. That is an advantage when the site delivers on it — and a mismatch when it does not.
Myth vs. reality
| Claim | Verdict | Plain words |
|---|---|---|
| .dev is only for throwaway staging | Myth | Many serious products and docs sites use it publicly. |
| HTTPS is optional on .dev | Myth | Plan TLS; .dev is associated with HTTPS-only behavior in major browsers. |
| .dev helps you recruit developers | Soft signal | It can reinforce culture; product and writing still do the work. |
- Use .dev for developer docs, changelogs, status for technical users, or the core product if that is the audience.
- Keep customer marketing on .com / .io / .app if the audiences diverge.
- Say the URL out loud — avoid ambiguous spellings.
FAQs
Can I use .dev for a non-developer consumer app?
You can, but the ending may confuse shoppers. Match the extension to the audience.
Is .dev available on DNX?
Yes — confirm current registration and renewal pricing on dnx.com/en/pricing.
From reading to finding