dev Domain vs com Domain
For developer tools and technical portfolios, a .dev domain signals insider credibility and enforces HTTPS through HSTS preload. For anything reaching a general audience, .com wins on recognition alone. The deciding factor is whether your users will type, remember and trust the extension you choose.
Best fit once the com is gone
· · fit
Second choice
· · fit
Read this before you buy
First choice
Second choice
Zone type
Worst fit here
The whole shortlist, ranked on your answers
Fit is relative to the best-scoring extension for the four answers you gave — it is a ranking, not a rating out of a hundred. Change one answer and the order moves, which is the honest way to read any tool like this.
What dev Offers That com Does Not
The .dev TLD is operated by Google Registry and sits on the browser HSTS preload list, which means every .dev site is forced to load over HTTPS with no server-level opt-out. This is the same enforcement that the .app extension uses, and it eliminates an entire class of configuration mistakes — no mixed-content warnings, no accidental HTTP fallback, no security headers to remember.
For a developer audience, this technical signal matters. Contributors on Hacker News have discussed .dev as a credible choice for developer tooling, noting that it communicates a product built for technical users. The word dev itself functions as an audience filter: visitors who see it understand the site is aimed at them, while non-technical users may not recognise the extension at all.
The cost trade-off is real. On Hacker News, users have noted that .dev runs at roughly two to three times the renewal price of .com. That premium is manageable for a funded company but meaningful for a solo developer maintaining a side project over several years.
When com Is the Stronger Pick
If your product serves both developers and non-technical decision-makers — a startup founder evaluating your API platform, a marketing lead assessing an analytics tool — .com removes friction. Non-technical users type .com instinctively. They may not know what .dev means, and an unfamiliar extension can create a subconscious hesitation about whether the site is legitimate.
Email is another factor. While .dev does not carry the spam-filter stigma of cheaper extensions, it is newer and less established in corporate email systems than .com. If your business sends invoices, onboarding sequences or support correspondence, .com provides the broadest baseline trust across recipient mail servers.
The practical decision often comes down to availability. If your preferred name is available as a .com, take it — the recognition advantage outweighs .dev's technical signalling for most projects. If .com is taken and you refuse to add a prefix or suffix, .dev is a strong second choice for technical products. Use the TLD chooser to test your specific combination of audience, email needs and budget.
The HSTS preload requirement on .dev is permanent and built into browser source code. It cannot be disabled per-domain.
Next in this cluster
Related domain guides
Sources
-
Google Registry .dev documentation; HSTS preload list (hstspreload.org); Hacker News dev-domain discussion threads (2023–2024)
- HSTS preload list — the
devandappzones are preloaded, so browsers refuse plain HTTP on them: hstspreload.org. - A generic top-level domain is not a ranking factor: Ahrefs glossary; Semrush.
- Practitioner reports on extension reputation, pricing and typo loss, quoted with the thread they came from: Hacker News 23799061, 41163433, 41729526.
- Counterweight on extension reputation — behaviour, not the extension, drives deliverability: Spamhaus.
- Country-code exposure precedent: CircleID on the vb.ly seizure.