Live data from Hacker News

First .dev Domains Go Live

blog.google

71–80 of 227 posts

Re: First .dev Domains Go Live

#71

Do TLDs even matter? I'm working on building a professional blog, and although a .dev TLD seems appropriate, using a cheaper one like .co or .be, or even .io seems functionally identical and a lot less costly. Paying hundreds or thousands for .dev seems like paying for pure vanity. Is it going to help people reach your site? I kinda doubt it. Will Google use it to index your site differently? Maybe, but I dunno. I ho…

.dev is only prohibitively expensive during the pre-sale. After Feb 28, there will be no extra charge ($0 one-time fee).

Re: First .dev Domains Go Live

#72

> ...it requires HTTPS to connect to all .dev websites. This protects people who visit your site against ad malware and tracking injection by internet service providers The latter is true (it protects against injection), but I'm not sure how the former is. How would it protect against ad malware?

Maybe they mean both the ad malware and tracking are injected by your ISP?

Re: First .dev Domains Go Live

#73

Earlier quoted context omitted.

They get progressively cheaper as we approach February 28. After that, I believe registrations are free with a $12 maintenance cost.

Minor correction, registrations are never free. Come 2019-02-28 16:00:00Z, they will be available at the base price. Registrars set their own prices, so depending on which registrar you're using, expect that to be around $12-20/yr (including the initial year).

Do you happen to have a source for the 16:00 UTC base price switch? I am not seeing a specific time on any of the linked pages.

Re: First .dev Domains Go Live

#77
post #18

Earlier quoted context omitted.

The `.test` and `.localhost` TLDs are already reserved for such purposes: https://tools.ietf.org/html/rfc2606

localhost is reserved for a very different purpose, though .local is a reserved pseudo-TLD for a purpose encompassing much of what was suggest by GP for .dev.

.local is for multicast. Don’t use it for anything else unless you want a headache.

Re: First .dev Domains Go Live

#79

Earlier quoted context omitted.

I used to work for a registry, and ICANN had very strict escrow rules for registrys'. This was for a real TLD but I suspect that there is something similar for vanity domains.

The new gTLDs are just as much “real TLDs” to ICANN as the older gTLDs and ccTLDs.

The new gTLDs are much more "real" than the ccTLDs in the sense that they are actually governed in ways that protect registrants. A ccTLD operator can unilaterally yank any domain they want with no restrictions whatsoever. They aren't contracted parties.

Re: First .dev Domains Go Live

#80
post #63

> ...it requires HTTPS to connect to all .dev websites. This protects people who visit your site against ad malware and tracking injection by internet service providers The latter is true (it protects against injection), but I'm not sure how the former is. How would it protect against ad malware?

My assumption from that sentence is that both "ad malware" and "ad tracking" are injected by some ISPs somewhere between the client and the server. By forcing HTTPS, you'd prevent some amount of this by ensuring the data in transit from client-to-server-to-client is encrypted (and thus mostly tamper-proof) using the .dev domain's public cert.

Also commonly injected by malicious or compromised WiFi routers.
Post reply on HN