The .dev domain is a generic top-level domain run by Google Registry and aimed at developers and tech projects. Its defining feature: the whole extension is on the browser HSTS preload list, so every .dev site must serve over HTTPS — there is no HTTP fallback. Anyone can register one.
Most extensions are just labels. .dev is unusual because it ships with a security policy enforced by the browser itself. That makes it a natural fit for developer tools, documentation and portfolios — and a small adjustment for anyone used to spinning sites up over plain HTTP.
What is the .dev domain?
A .dev domain is any name ending in .dev, such as example.dev. It is one of Google Registry’s new generic TLDs, opened to general registration in 2019 after a brand and early-access period. The branding speaks to development: it reads naturally for engineering teams, open-source projects, API docs, demos and personal developer sites.
A developer-oriented generic TLD operated by Google Registry. Because it is HSTS-preloaded, browsers require HTTPS for every .dev address.
The HTTPS-only rule, explained
This is the headline feature. HSTS (HTTP Strict Transport Security) is a mechanism that tells browsers “only ever connect to this site over HTTPS.” A domain can opt in, but an entire TLD can also be added to the browsers’ built-in preload list — and .dev is. The result: when anyone types a .dev address, the browser silently upgrades the request to HTTPS and will not load it any other way.
For the modern web, that is a feature, not a hurdle. It means a .dev site is encrypted by default, with no risk of accidentally serving insecure pages. It does, however, mean you must have a working TLS certificate before the site will load at all.
HTTPS is free and easy now
Free certificates from Let’s Encrypt, plus automatic HTTPS on hosts like Netlify, Vercel, Cloudflare and GitHub Pages, make the .dev requirement a non-event for most projects. You usually just toggle HTTPS on.
Who is .dev for?
The extension is unrestricted, but it self-selects a clear audience: software developers and teams, open-source maintainers, API and documentation sites, technical blogs, developer-tool startups, and engineers building a personal brand. The name says “technical” before a visitor reads a word, which is exactly the point.
It is especially common as a home for developer relations and documentation — a company might keep its marketing site on .com while putting its docs, API reference and developer portal on a matching .dev. That split lets each audience land somewhere that speaks their language, and the secure-by-default nature of .dev suits documentation and dashboards that engineers will use directly. For an individual engineer, a clean name.dev also makes an unmistakable, on-brand portfolio address.
.dev vs .io vs .app
| Extension | Type / operator | HTTPS forced? | Reads as |
|---|---|---|---|
| .dev | gTLD — Google Registry | Yes (HSTS preload) | Development / engineering |
| .app | gTLD — Google Registry | Yes (HSTS preload) | Apps & products |
| .io | ccTLD (British Indian Ocean Territory), used globally | No | Tech / startups |
If forced HTTPS and a development tone appeal, .dev is the pick. For consumer apps, .app shares the security model with friendlier branding. For a broader startup feel without the HTTPS mandate, .io is the classic choice.
What does choosing .dev mean in practice?
Practically, almost nothing changes except that you must enable HTTPS from day one. Register through any registrar, point DNS at your host, and make sure a certificate is in place — on modern platforms this is automatic. After that, a .dev behaves like any other domain.
When should you choose .dev?
Choose .dev when your project is technical and you want the name to broadcast that; when secure-by-default HTTPS is a benefit rather than a chore (it usually is); and when a clean, available, on-brand name beats chasing a long-gone .com. Avoid it only if your audience is non-technical and the word “dev” would confuse them.
★ Key takeaways
.devis a Google Registry gTLD aimed at developers, public since 2019.- It is HSTS-preloaded, so every
.devsite must use HTTPS — no HTTP fallback. - It is open to anyone; you just need a TLS certificate (free and easy today).
- Ideal for dev tools, docs and technical brands; the TLD is SEO-neutral.
Frequently asked questions
Why does .dev require HTTPS?
The entire .dev extension is on the browser HSTS preload list. That means major browsers refuse to load any .dev address over plain HTTP and force an encrypted HTTPS connection. The rule is baked into the browser, not just the server, so you cannot opt out.
Who can register a .dev domain?
Anyone. Despite the developer branding, .dev is an unrestricted generic TLD — you do not have to be a programmer or a company. You register it through any accredited registrar like any other extension.
Do I need an SSL certificate for a .dev domain?
Yes — because browsers force HTTPS on .dev, you must have a valid TLS/SSL certificate for your site to load at all. The good news is that free certificates (for example via Let’s Encrypt) and one-click HTTPS from most hosts make this routine.
Is .dev good for SEO?
The TLD itself is SEO-neutral. Indirectly, the forced HTTPS is mildly helpful: secure connections are a (small) positive signal and a baseline expectation, so a .dev site is secure by default. Content and links still decide rankings.
Who runs the .dev domain?
.dev is operated by Google Registry, Google’s domain-registry arm, which also runs extensions like .app and .page. It was opened to the public in 2019.
Can I use a .dev domain for local development?
You can register and use a real .dev domain, but be careful using .dev for local-only hostnames. Because the whole TLD forces HTTPS in browsers, made-up local .dev addresses without a valid certificate will fail to load. For purely local testing, a reserved name like .localhost or .test avoids that headache.
Sources & further reading
- IANA — Delegation record for .dev
- Google Registry — get.dev
- HSTS Preload List (the mechanism that makes .dev HTTPS-only)
- Related: .app explained, .io explained, new gTLDs, what is a gTLD?, .tech domain