Live data from Hacker News

How did .agakhan, .ismaili and .imamat get their own TLDs?

data.iana.org

71–80 of 177 posts

Re: How did .agakhan, .ismaili and .imamat get their own TLDs?

#71

All it takes for a TLD these days is a vaugely-legitimate use and about a million dollars[1]. This isn't hard for a large company or state actor to fund; Why would a mid-large religion not be able to? [1] https://newgtldprogram.icann.org/en/resources/faqs#6

And a time machine. Applications were due in 2012. A new round is starting soon, but it's not clear if it's going to be continuous, or if it will be a single application period again.

Re: How did .agakhan, .ismaili and .imamat get their own TLDs?

#72
post #60
post #58

Earlier quoted context omitted.

Amazon/AWS use them (.aws), so does Google (.google) but I agree, it is pretty funny how many companies seemed to get on board (out of fear of being left out?) and then...didn't use them for some reason?

Google does use theirs for public-facing landing pages even [1], just not uniformly, but that's very on-brand for Google as an org. Where have you seen .aws in use though? [1] e.g. https://quantumai.google/

AWS uses the TLD internally

Re: How did .agakhan, .ismaili and .imamat get their own TLDs?

#73

Earlier quoted context omitted.

> Think limited number of taxi medallions or street vendor or liquor licenses. Those are not particularly compelling examples in favor of such a thing.

I’m not making an argument for quotas, just explaining why they usually are included. It’s a cheap way to add “market” value to something aka scarcity. The issue would occur in the suggested system when ICANN decides to one day stop creating 250 domain names down to 25 domain names or some such change that increases the value of the gtlds to ridiculous numbers only the wealthy/well-connected can afford.

Why is the goal to artificially increase the value of tld's?

Re: How did .agakhan, .ismaili and .imamat get their own TLDs?

#74
post #40

Presumably way the same as .google and all the other special-purpose organization-specific domains. Blame ICANN for allowing any public or private organization who can meet the requirements to buy and operate a gTLD back in 2012: https://newgtlds.icann.org/en/applicants/global-support/faqs... And as per another comment in this thread, they’re doing another round of this in 2026: https://news.ycombinator.com/item?id=4…

The fact that private entities can monopolize gTLDs, including words that aren't even made-up or reasonably copy-written (e.g. the MAN group in Europe owns .man) was an embarrassing and dishonorable decision by ICANN. I'm all for having tons of weird, awesome gTLDs, and I'm even for brand-specific gTLDs like .google, but the cost these entities should incur by asking for one to be created is: Anyone can use it. 1. A…

The cost for a gTLD used to be $1-2 million USD. I wonder if it is still the same pay-to-play racket for rich people and corporations.

Re: How did .agakhan, .ismaili and .imamat get their own TLDs?

#76

Earlier quoted context omitted.

If you pay ICANN hundreds of thousands of dollars, you can get basically any .word domain. I believe the only actual requirement is that it has to be 3 characters or longer, as two characters are reserved for countries.

Application fee with ICANN: $185k, non-refundable, Yearly fee: $25k Technical backend with Verisign: $200k per year Add maybe $100k of lawyer fees.

What happens when a company goes under and the yearly fee can no longer be paid? Has a gTLD ever been resigned?

Re: How did .agakhan, .ismaili and .imamat get their own TLDs?

#79
post #65

Earlier quoted context omitted.

If icann sells www as a tld domain then your use of www as a machine name you may refer to unqualified is a risk because virtually every piece of software in the world respects public issuance until you delete it all if you can. The DNS naming confusion was largely dealt with by having a small number of TLDs and rarely referring to complex things like partially specified subdomains, but every once in a while a fool n…

You might want to look at the "domain" directive of resolv.conf and the concept of "split horizon DNS".

I've done plenty of interesting things but a distributed correction attempt for ICANN's incompetence is never going to be adequate. You can read their own work on gTLDs in the past to know they understand this.
Post reply on HN