I need a dumbed down version of this.
If the 'private' TLD you're using suddenly becomes real, then you can ship off data, every possibly unencrypted data and connection requests to computers you do not control.
11–20 of 290 posts
I need a dumbed down version of this.
If the 'private' TLD you're using suddenly becomes real, then you can ship off data, every possibly unencrypted data and connection requests to computers you do not control.
I need a dumbed down version of this.
1. Buy .intern TLD 2. Sell to scammers. 3. Profit. (I want to appreciate how hard it probably is for ICANN to figure out proper TLDs.)
Earlier quoted context omitted.
Is it not already? https://en.wikipedia.org/wiki/.local
Not by ICANN? https://www.iana.org/domains/root/db
1. Buy .intern TLD 2. Sell to scammers. 3. Profit. (I want to appreciate how hard it probably is for ICANN to figure out proper TLDs.)
Um... no? .intern is not a valid TLD; you can't get any domains with it, nobody has proposed that TLD, and if someone did that issue would be discovered then.
I'd like to think people learned from .dev and such. I doubt any scammer will be able to use it.
I need a dumbed down version of this.
Earlier quoted context omitted.
Um... no? .intern is not a valid TLD; you can't get any domains with it, nobody has proposed that TLD, and if someone did that issue would be discovered then.
If you've got a couple hundred grant laying about, you could probably set up a shell company and acquire .intern through a several-year ccTLD acquisition process. I'd like to think people learned from .dev and such. I doubt any scammer will be able to use it.
EDIT: just saw your comment about Google here
Proposed top-level domain string for private use: ".internal"
Can we get .local or .l added for private-use applications too?
.local is already reserved for mDNS.
So you end up with the IETF standardising .local, because Apple was already using it, but ICANN never did much with that standardisation.
I doubt ICANN will actually touch .local, but they could. One could imagine a scheme where .local is globally registered to prevent Windows clients (who don't always support mDNS) from resolving .local domains wrong.
Earlier quoted context omitted.
If you've got a couple hundred grant laying about, you could probably set up a shell company and acquire .intern through a several-year ccTLD acquisition process. I'd like to think people learned from .dev and such. I doubt any scammer will be able to use it.
Sorry, what happened with .dev? EDIT: just saw your comment about Google here https://news.ycombinator.com/item?id=41205394