The .dev domain is a generic top-level domain (gTLD) operated by Google Registry, aimed at software developers, tools and projects. It is open to anyone, and every .dev site must use HTTPS because the whole extension is on the browser HSTS preload list.
.dev at a glance
Source: IANA root zone database & registry data · methodology
Where to register a .dev domain
Prices are indicative and set by each registrar; renewal rates may differ from first-year promotions. Links may be sponsored. tldlist.us is an independent reference and not a registrar.
What does .dev mean?
The .dev extension is a plain-spoken label for one thing: development. It reads as short for developer or development, and that is exactly the audience Google had in mind when it brought the domain to general availability in 2019. Engineers had already used dev for years as an informal hostname for local builds and staging servers, so when a public TLD appeared carrying the same three letters, it slotted straight into the way developers already think about their work.
What makes .dev genuinely different from most extensions is a security decision baked into the registry from day one. The entire .dev zone is on the HSTS preload list that ships inside Chrome, Firefox, Safari, Edge and other browsers. In practice that means a browser will refuse to load any .dev address over plain http:// — it silently rewrites the request to https:// before it ever leaves your machine. There is no insecure version of a .dev site to misconfigure, no downgrade attack to worry about, and no "not secure" warning if you set things up properly. For an extension aimed at people who build software, shipping HTTPS-by-default is a fitting touch.
Who uses .dev?
.dev is the home turf of software developers, open-source projects and developer-tooling companies. Google itself publishes its web-performance and standards resource at web.dev, and the React team documents the framework at react.dev — both of which signal that the extension is taken seriously by the engineering community rather than treated as a novelty. Beyond the big names, .dev is popular for personal developer portfolios, internal documentation hubs, API landing pages and side projects where the owner wants the address to say "this is technical" at a glance.
It is a poor fit for a non-technical small business or a high-street brand, simply because the word "dev" means little to a general audience. If your visitors are developers, .dev communicates instantly; if they are not, a .com or a descriptive extension like .tech will read more clearly.
.dev registration rules and requirements
Registration is fully open. You do not have to prove you are a developer, hold any credential, or be based in a particular country — anyone may register an available .dev name on a first-come, first-served basis through ordinary registrars. The one non-negotiable condition is technical rather than legal: because the extension is HSTS-preloaded, your site must serve a valid TLS certificate. Practically every host and CDN now issues free certificates automatically (Let's Encrypt, Cloudflare and the like), so this is a small step, but it is a step you cannot skip. The usual ICANN contact-data policies for gTLDs apply as well.
How much does a .dev cost?
A .dev domain sits around $13 per year at mainstream registrars. Pricing is fairly honest by new-gTLD standards: the first-year and renewal prices are usually close, so you are unlikely to be ambushed by a renewal that is many times the intro rate. Cloudflare passes the wholesale price through at cost, while Porkbun and Namecheap cluster in a narrow band around it.
| Registrar | Typical .dev price (per year) |
|---|---|
| Cloudflare Registrar | At wholesale cost (~$12) |
| Porkbun | ~$12/yr |
| Namecheap | ~$13–15/yr |
| Premium names | Higher, registry-set |
Is .dev good for SEO?
It is SEO-neutral, like every generic TLD. Google and Bing rank a .dev page on the same footing as a .com or .io — the extension confers no algorithmic boost and no penalty. The mild indirect benefit is audience fit: if your readers are developers, a memorable .dev address can lift click-through and recall within that crowd. The mandatory HTTPS is also a quiet plus, since secure connections are a baseline ranking expectation and .dev guarantees you meet it. For a broader view of how extensions stack up, see our TLD comparison guide.
.dev vs alternatives
Among developer-friendly extensions, .dev's closest siblings are .app (the other HTTPS-only Google Registry domain, pitched at applications rather than developers), .io (the long-standing startup and SaaS favourite) and .ai (now ubiquitous for machine-learning products). Broader options such as .tech read clearly to a non-technical audience too. Pick .dev when "this is for developers" is exactly the message you want, and weigh the others when you need wider recognition.
.dev pros and cons
Pros
- HTTPS is mandatory and automatic — secure by default, no downgrade risk.
- Instantly understood by developers as a technical address.
- Run by Google Registry with stable, near-flat renewal pricing.
- Far more short, available names than the crowded .com space.
Cons
- You must install a valid TLS certificate before the site will load at all.
- The word "dev" means little to a non-technical audience.
- Slightly pricier than bargain generics like .xyz or .online.
- Less universally recognised than .com for a mainstream brand.
Example .dev websites
- web.dev — Google's own resource for web performance, best practices and modern standards.
- react.dev — the official documentation home of the React JavaScript library.
- yourname.dev — the popular pattern for developer portfolios and personal technical sites, where the extension signals the owner writes code.