.app
Also operated by Google's registry arm and also requires HTTPS by default, but aimed more broadly at products and apps than at developer-facing tools and docs.
.dev is a generic top-level domain operated by Charleston Road Registry Inc., a Google subsidiary that runs it commercially as Google Registry. It was delegated to the root zone in November 2014 and opened for public registration in March 2019, marketed toward software developers, tools and technical documentation sites.
Anyone can register a .dev name, there are no eligibility checks, and pricing runs in the same band as other Google-run gTLDs. The one binding rule is mandatory HTTPS: browsers will refuse to load a .dev site without a valid certificate, so factor that into your setup before you buy.
verified against the linked source not verified, not inferred from another extension sources disagree
| Provider | Registration | Renewal | Transfer |
|---|---|---|---|
| OpenproviderNon-member prices | $23.981 year totalChecked 2026-09-12 | $23.981 year totalChecked 2026-09-12 | $23.98Transfer fee · confirm termChecked 2026-09-12 |
| AI VikingsPublic price list | $11.12Listed price · confirm termChecked 2026-09-12 · source 2026-09-12 | $14.84Listed price · confirm termChecked 2026-09-12 · source 2026-09-12 | $14.16Transfer fee · confirm termChecked 2026-09-12 · source 2026-09-12 |
| OpusDNSBusiness customers | Check dashboard pricingBusiness customers only | Check dashboard pricingBusiness customers only | Check dashboard pricingBusiness customers only |
| PorkbunPublic API prices | Check providerNo current public quote | Check providerNo current public quote | Check providerNo current public quote |
Advertised prices for standard names, not an availability check. USD as published; taxes and final fees are confirmed at the provider. How we compare All 28 extensions
Dig into the IANA delegation record and you'll find Charleston Road Registry Inc. named as the sponsoring organisation for .dev. Same company shows up as operator of record on the ICANN registry agreement, signed 16 October 2014, according to ICANN. Charleston Road Registry is a Google LLC subsidiary, trading commercially as Google Registry. The administrative and technical contacts on the IANA record are still listed under Google Inc., per IANA. Name servers run on Charleston Road Registry's own infrastructure, no third-party backend provider anywhere in the dossier.
Three layers sit between Google and whoever registers a .dev name. The registry, Charleston Road Registry trading as Google Registry, writes the rules (mandatory HTTPS being the big one) and keeps the master database for every .dev domain in existence. Below that sits a registrar, one of the accredited companies you actually hand your money to, which deals with billing, DNS records and support tickets. Then there's you, the registrant, holding registration rights under the registry's policies and whatever terms your registrar bolts on top. Google doesn't sell .dev names to the public directly. It works through accredited registrars, the same registry-registrar split ICANN uses across the board.
.dev has no eligibility restrictions. Anyone can register, individual or company, anywhere in the world, with no geographic, professional or documentation requirements, according to GoDaddy's registrar guidance. You don't need to prove you're a developer or that you work in tech to buy one.
The one rule that applies across the board isn't really about eligibility at all, it's technical: the registry requires registrars to disclose, before purchase, that HTTPS is mandatory on .dev, because the extension sits on the HSTS preload list, per the .dev Registration Policy. Skip the certificate and your site simply won't load in a standard browser. There's also a specific rule for anyone registering a two-character letter/letter name: you have to confirm it doesn't falsely imply government or country-code affiliation. On top of that, reserved-name provisions carried over from ICANN's new gTLD programme protect names tied to the IOC, the Red Cross and various IGOs.
Past these registry-level rules, individual registrars can bolt on their own commercial practices, things like account or payment verification, but that's a business decision, not an eligibility gate set by the registry.
.dev domains change hands between registrars the same way almost every gTLD does: under the standard ICANN Transfer Policy. The losing registrar hands over an authorisation code, the registrant confirms with the new registrar, and the transfer goes through unless something blocks it, a dispute, say, or a lock placed after a recent registration or transfer. Nothing here is specific to .dev; it's the general ICANN transfer mechanism at work.
Every registrar checked offers a one-year minimum term (INWX, Dynadot, DNSimple). The maximum term is where things get messy: Dynadot, Gandi and DonDominio all allow registrations of up to ten years, yet one registrar's page caps it at a single year. Nothing in the available documentation explains the gap, and it's probably down to individual registrar policy rather than any registry-wide rule.
Google Registry's pricing policy gives a domain 45 days of auto-renew grace after expiry, and a registrar can still delete the name in that window to dodge the renewal charge. Delete it, and a 30-day redemption grace period kicks in, during which the name can only be restored, not renewed, and restoration comes at a price. That price swings a lot by registrar: roughly €70 at DonDominio versus $190 at DNSimple. Google doesn't publish its own wholesale restore fee, so registrars seem to be marking up whatever they're charged and calling it their retail rate. After redemption comes a short pending-delete window, a few days by most registrars' accounts, before the name finally drops back into the public pool.
.dev carries an explicit developer association because Google Registry markets it that way and requires HTTPS by default across every registration. That signal matters in some contexts and does nothing in others.
Scenario one: a solo developer wants a home for a portfolio, changelog or API reference. A .dev name fits comfortably here. HTTPS is trivial to arrange on any modern host, and the extension's association with tools and documentation, visible in the examples on Google's own .dev showcase, matches the likely audience.
Scenario two: a startup wants its primary commercial site, aimed at non-technical buyers, on .dev. We'd call this a weaker fit. The name reads as "built by developers" rather than "for everyone," and the mandatory HTTPS requirement, not hard to meet, is still one more configuration step a general-audience marketing site has no real need to take on.
Scenario three: a company wants a short, memorable domain for a specific tool, SDK or API, kept separate from its main .com site, in the pattern of stripe.dev or web.dev. This works well. The naming convention is already familiar to the engineers it targets, and the domain sits alongside the primary brand rather than trying to replace it.
Across all three, the same pattern holds. .dev suits technical audiences and technical content, and its main practical cost is the HTTPS requirement, not price or eligibility, since registration itself is open to anyone.
Also operated by Google's registry arm and also requires HTTPS by default, but aimed more broadly at products and apps than at developer-facing tools and docs.
A long-standing default among startups and technical products generally, without any HTTPS or registry-imposed security requirement, though it runs under different ccTLD administration.
A generic gTLD marketed at the wider technology sector rather than developers specifically, with no mandatory HTTPS condition attached to registration.
The default choice for a primary commercial or general-audience site, with no security precondition and the broadest existing base of registered names.
Yes. .dev sits on the HSTS preload list baked into every major browser, which means a .dev site without HTTPS simply will not load. No warning page, no workaround, it just fails. The registry makes registrars spell this out to buyers before they hand over any money, as part of its registration policy.
Sources: registry.google, get.dev
According to the IANA record, Charleston Road Registry Inc. holds the sponsoring organisation slot and signs the ICANN contract, though everyone just calls it Google Registry, which is how it trades commercially. Google Inc. shows up as both the administrative and technical contact on the delegation record.
No. Anyone anywhere can register, first come, first served. There's no vetting for profession, location or organisation, and nobody's going to ask you to prove you're actually a developer.
Sources: godaddy.com
The picture is messier than it should be. Dynadot, DonDominio and Gandi will all let you register a domain for up to ten years, but at least one registrar's own page caps it at one year. Whichever registrar you use, though, the minimum stays the same: one year.
Sources: asiaregistry.com, inwx.de
The registry gives you a 45-day auto-renew grace period. Miss that window and your registrar can delete the name outright rather than eat the renewal charge. After that comes a 30-day redemption period, your last chance to get the domain back, but it'll cost you. Restore fees aren't set by the registry, they're set by whoever your registrar is, and the price swings wildly from one to the next.
Sources: registry.google, gandi.net
Facts on this page were checked against the sources below on 2026-09-12. Prices come from the public sources described in the methodology and carry their own check dates. Registry facts and retail prices are refreshed on different schedules.
HostList does not sell domains and earns nothing from the provider links on this page. Report a correction.