Skip to content

Domains · .dev

.dev — https is not optional, and that is the point

Run by Google Registry and on the browser HSTS preload list, which means every .dev site is reached over HTTPS by design. For engineering teams that is a feature; for anyone planning to serve plain HTTP it is a hard stop.

Rendering of three name tiles reading .com, .io and .dev.com.com.io.io.dev.devRenewal printed firstWHOIS privacy free

Who it suits

When .dev is the right answer.

Not a list of everyone. The cases where this extension is genuinely doing work for you.

Developer tools and documentation
The extension names the audience. Docs, SDKs, CLIs and internal tooling all sit naturally on it.
Personal engineering sites
Portfolios, blogs and side projects, where the name yourname.dev needs no explanation at all.
Staging and demo environments
A separate .dev keeps non-production visibly separate from the production brand, which is worth more than it sounds when someone shares a link.
Teams that already enforce HTTPS
If TLS everywhere is your policy, an extension that enforces it removes a class of mistake entirely.

.dev pricing

$9.49first year

Then $16.49 a year. The second number is the one to budget on.

Registration term
1 year
Register
$9.49/yr
Renew
$16.49/yr
Transfer in
$16.49
WHOIS privacy
Free

A transfer costs the same as a renewal and adds a full year to whatever time is already on the domain, so nothing is lost by moving in.

Registrar prices last checked 2026-09-02. Search re-confirms before you pay.

Search a .dev name

Before you register

Three things about .dev worth knowing first.

The parts that are easy to find out afterwards and irritating to find out afterwards.

HTTPS is mandatory in browsers

.dev is on the HSTS preload list, so browsers refuse plain HTTP to any .dev address. You need a valid certificate from the first request — there is no “set it up later” phase.

It is a general-purpose extension, not a ccTLD

Unlike .io, it is not tied to a territory. No residency or presence requirement, and no country attached to the brand.

The audience is technical

Outside software, most people have never seen it. If your customers are not developers, the extension is doing nothing for you.

Questions

About .dev specifically.

What does the HSTS preload list actually mean for me?
Browsers ship with .dev marked as HTTPS-only, so they will not make an unencrypted request to any .dev address at all — there is no click-through warning to bypass. Practically: have a certificate ready before you point the domain anywhere. Any of the usual automated certificate tools will do it in a minute on a server you control, including the ones you would run on a VPS from us.
Can I use a self-signed certificate on it?
Only for something you alone will visit, and even then the browser will complain. For anything other people load, use a publicly trusted certificate. The requirement is on the connection being HTTPS, but visitors still need to trust the certificate presented.
Is .dev good for a company site?
For a company whose customers are developers, yes. For anyone else it is a needless explanation on every phone call. The extension is precise, and precision only helps when it points at the right audience.

Other extensions

The rest of the shortlist.

Keep reading

Domains, in more detail.