Google Launches New .dev TLD (betanews.com)
97
Google Registry today announced .dev, a brand new top-level domain (TLD) that's dedicated to developers and technology. From a report: The new .dev TLD comes after the company launched .app and .page, all are protected by HTTPS. Google has already used the TLD for a few of its own projects, such as web.dev and opensource.dev, but now it is being opened up to a wider audience. If you are interested in securing yourself a .dev domain, you can register through the Early Access Program.
my new e-mail address: satan@me.dev (Score:1)
Re: (Score:2)
Register null.dev (Score:5, Funny)
A new upload service. Unlimited, write-only storage.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
I could see some use from this. Especially if it accepts and gives the proper response to different types of connections.
You can use it as redirect on your Honey Pot, so after monitoring who and where, the rest of the IO can be handled by null.dev (And you don't need to (less) worry if your Honey Pot itself is the security hole)
While creating Client/Server Applications you can insure your connection are working correctly. without having to get your Server Side up an running.
A general pingable location to
Re: (Score:2)
Re: (Score:2)
Does it support sharding?
Betanews? (Score:1)
Where's the Google announcement?
$11,500 a pop (Score:1)
Obvious not aimed at actual developers. Thanks google.
Re: (Score:3)
$11,500 + $12/year
New business model: Let's come up with new TLD's to force companies to buy their namesake in this new TLD to prevent squatters or miscommunication/disinformation!
Re: (Score:2)
Still not seeing biz.dev up. Who will be the first to claim this land of gold and honey!
Re: (Score:2)
Looks like some of the resellers have there pricing messed up. GoDaddy seems to have the pricing correct at approx $14 / yr while NameCheap is showing $11,011.00 with a $11.00/year renewal.
Re: (Score:1)
Re: (Score:1)
Obvious not aimed at actual developers. Thanks google.
That's for the first phase of early registration. Then it gradually drops to the regular price of $14/year.
Spam, eggs, sausage, and spam (Score:4, Insightful)
Another TLD I'll probably have to blacklist in my sendmail.conf.
Re: (Score:2)
Another TLD I'll probably have to blacklist in my sendmail.conf.
Why blacklist? This stupidity and the complete and utter lack of meaningful adoption means whitelisting is a perfectly suitable filtering method.
When do they launch .serf? (Score:1)
Is that an IQ test that you fail if you register a domain with Google?
So what happens when they cancel it? (Score:2)
Because if history has told us anything about Google, it's that they will cancel a service just as soon as they get it working correctly.
protected by https? (Score:1)
What does "protected by https" even mean as far as DNS and TLD go?
I could understand if it were DNSSEC, but https? That doesn't even make sense.
Re: (Score:3)
Browser default HSTS lists mandate that all connections to .dev are over HTTPS.
That has nothing to do with the TLD though and everything to do with Google's Chrome monopoly. Quite frankly, this is a great reason *not* to let companies do that: advertise one feature as something when it's actually provided by a distinct unit, and the only reason nobody cares is because it's at monopoly scale.
First .prod, now .dev... .uat next? (Score:1)
It's like Google just wants to screw up everyone's internal domain structures.
ICANN needs to be dismantled (Score:4, Insightful)
There is no organization more corrupt or deleterious to the continued operation of the network than ICANN. They stopped giving a fuck about best interests of the network decades ago.
Today they care only about themselves making money from proliferation of TLDs which serves no useful purpose other than assisting phishers and exposing Internet users to unnecessary risk of collision with common internal naming schemes.
It's time for wholesale change within ICANN. Leadership needs to be replaced with a structure that is accountable to the Interests of the network rather than themselves.
Re: (Score:2)
Re: (Score:1)
How can a company control a TLD? (Score:2)
If the description is correct, this just seems wrong on several levels. A for-profit company shouldn’t have control over a top-level domain.
Re:How can a company control a TLD? (Score:4, Interesting)
ICANN sold out in 2011. There are plenty of corporate owned TLDs now, and it sucks. Where have you been for the past 8 years?
https://www.voanews.com/a/new-... [voanews.com]
Re: (Score:2)
A for-profit company shouldn’t have control over a top-level domain.
Huh? That was never a consideration. The entire premise of gTLDs was a dollar grab priced in a way that only a for profit company could afford it.
Staged Rollout (Score:4, Interesting)
Looks like a staged roll-out with the highest prices for day 1 and decreasing from there. I'm guessing it's letting the ones with deep pockets pickup their preferred domain name while paying a large premium to do so. Godaddy has a pretty good layout of the pricing for each day till it reaching the standard of $14ish for the public.
https://www.godaddy.com/tlds/d... [godaddy.com]
Re: (Score:1)
Are there people stupid enough to preregister their desired domain with Godaddy while registration is already open at a premium?
Google resgistry? Not ICANN? (Score:1)
is larry.page taken? (Score:2)
asking for a friend
Would cost me a ton in early access program (Score:2)
Launching now, but screwing with it for years (Score:1)
Like Google, we used ".DEV" internally to refer to our development servers. However, just about the time ICANN let Google have the DEV TLD, Chrome had already decided that any URL containing .DEV had to go to Google's DNS, which then wouldn't resolve. It wouldn't even check the local DNS, which WOULD resolve, because ".dev belongs to Google!"
We had to come up with a different TLD for internal use, one that Chrome didn't know about, so it would use the local DNS.
Re: (Score:2)
I think all of these new TLDs have to be at least three characters, and ".dv" is not a valid country code, so you could change to use that. It's also one less character to type. I don't think anyone is allowed to register a TLD with hyphens (there might be an exception for xn-- style internationalized names), so ".d-v" could also be valid and safe.
It's unfortunate that you can't start or end a domain name part with a hyphen (I checked RFC1035) or you could do some cool things with a TLD of a single hyphen