Google Launches .dev TLD Now in Early Access Period

Forum Moderators: buckworks & webwork

Message Too Old, No Replies

Google Launches .dev TLD Now in Early Access Period

engine

10:30 am on Feb 22, 2019 (gmt 0)

Google Registry is launching its .dev TLDs for developers currently in the early access period, February 19 - 28, 2019, with general availability from 28 February, onwards.

Starting today at 8:00 a.m. PT and through February 28, .dev domains are available to register as part of our Early Access Program, where you can secure your desired domains for an additional fee. The fee decreases according to a daily schedule. Beginning on February 28, .dev domains will be available at a base annual price through your registrar of choice.

[blog.google...]

tangor

3:41 pm on Feb 22, 2019 (gmt 0)

One can hope that their desired dev domain survives the first round of pricing ... wait long enough and the cost will settle to $17.50/yr.
[theregister.co.uk...]

topr8

9:04 pm on Feb 22, 2019 (gmt 0)

well i went to the page of sellers ... and after looking at

domainname.com

which as of today, 22 feb 2019 has a landing page saying:

DomainName.com
IS COMING SOON!

made me smile anyway.

pupidu

6:17 am on Feb 23, 2019 (gmt 0)

considering number of closed, dropped and abandoned "dev" projects, flaws, security issues and business attitude, goog is last to launch .dev

graeme_p

4:45 pm on Feb 25, 2019 (gmt 0)

They are also using Chrome to push this, in that people who have been using .dev internally without https will find it no longer works.

tangor

6:03 pm on Feb 25, 2019 (gmt 0)

who have been using .dev internally without https will find it no longer works.

Creating a new revenue stream. :)

koan

5:51 am on Feb 27, 2019 (gmt 0)

graeme_p, yeah I lost many hours to this, all my sites ran locally with a .dev TLD for development purposes, one day Chrome stopped being able to access them. After figuring out, I considered replacing to .test but that wasn't really appropriate (what if one day I needed a test version in addition to local development), so I settled with .localhost. Not as pretty and succinct but I don't think I'll ever have to change that one again.

graeme_p

10:38 am on Feb 27, 2019 (gmt 0)

If you use zeroconf all machines appear as name.local provided the right ports are open.

You are safe with .localhost as its on the list of TLDs that will not be used. I prefer to keep .localhost for the current machine

jmccormac

6:10 am on Feb 28, 2019 (gmt 0)

Another great Google success? Just like Google Plus, Google Buzz and all the rest?

Regards...jmcc