Recent Posts
- ICANN going back to Puerto Rico for a third time
- Montreal airport thinks DI is porn
- DI Leaders Roundtable #2 — Should we kill off “Whois”?
- Former NTIA chief Redl now working for Amazon
- Neustar’s .co contract up for grabs
- US official Heineman joins GoDaddy
- Web.com got pwned
- Surprise! ICANN throws out complaints about .org price caps
- Somber mood as ICANN 66 opens in Montreal
- America has Amazon’s back in gTLD fight at ICANN 66
- New (kinda) geo-TLD rules laid out at ICANN 66
- Emoji domains get a 😟 after broad study
- Industry veteran Jay Daley tapped to lead IETF
- Verisign likely to get its billion-dollar .com pricing windfall
- ICANN enters talks to kill off Whois for good
- Form an orderly queue: New Zealand wants a new back-end
- Brexit hell: .eu suspension plan put on hold
- DI Leaders Roundtable #1 — How many new gTLDs will be applied for next time around?
- Now you don’t have to live in the EU to register a .eu domain, but there’s a catch
- Spam is not our problem, major domain firms say ahead of ICANN 66
- Crunch time, again, for Whois access policy
- Google quietly launches .new domains sunrise
- After .org price outrage, ICANN says it has NOT scrapped public comments
- Hindu god smites Chrysler gTLD
- Top ICANN advisor Tarek Kamel dies at 57
- Three big changes could be coming to .uk
- Introducing… the DI Leaders Roundtable
- After killing the cows, what does the new Tucows logo remind you of?
- Radix acquires another gTLD
- .whoswho survives!
- Correction: the 10 most-used dot-brands
- Nominet raises .uk prices
- Registrar suspended over dodgy transfers
- Mediocre .vote gTLD drops restrictions
- ICANN’s babysitting fund goes live
- Claims auDA boss quit after he was busted for “falsified” law degree
- .bond domains could cost a grand each
- PIR’s “new” .org domain is just temporary. Help it pick another new one!
- MMX switches porn TLDs from Afilias to Uniregistry
- Argentina will use a lottery to decide 2LD landrush
- Sixty gTLD registries not monitoring security threats
- ICANN must do more to fight internet security threats [Guest Post]
- Bumper batch of dot-brands off themselves for Friday 13th
- .org price cap complaints more like “spam” says Ombudsman
- Botterman is new ICANN chair
- Another victory for Amazon as ICANN rejects Colombian appeal
- Kafka turns in grave as ICANN crowbars “useless” Greek TLD into the root
- Sorry, you still can’t sue ICANN, two-faced .africa bidder told
- Why you should never let a pizza joint apply for your billion-dollar dot-brand
- More than 1,000 new gTLDs a year? Sure!
India to have SIXTEEN ccTLDs
While most countries are content to operate using a single ccTLD, India is to up its count to an unprecedented 16.
It already has eight, but ICANN’s board of directors at the weekend approved the delegation of an additional eight.
The new ccTLDs, which have yet to hit the root, are .ಭಾರತ, .ഭാരതം, .ভাৰত, .ଭାରତ, .بارت, .भारतम्, .भारोत, and .ڀارت.
If Google Translate and Wikipedia can be trusted, these words all mean “India” in, respectively, Kannada, Malayalam, Bengali, Odia, Arabic, Nepali, Hindi and Sindhi.
They were all approved under ICANN’s IDN ccTLD Fast Track program and will not operate under ICANN contract.
India already has seven internationalized domain name versions of its ccTLD in seven other scripts, along with its vanilla ASCII .in.
National Internet Exchange of India (NIXI) will be ccTLD manager for the whole lot.
India may have as many as 122 languages, according to Wikipedia, with 30 spoken by more than a million people.
It is “Bharat”. All of those. Another word for “India”.
Or Indian registrants could just use .desi…
You’d think that, with only 2 million or so registered names on the English script, there were enough names available for nearly everyone. Unless there’s a grand plan (conspiracy?) to make IDNs the way of the future, I don’t see how this helps anyone.
More and more people are speaking English now…so good luck with that!!!
The Arabic and Sindhi ones are misspelled:
https://www.google.com/search?q=bharat+in+arabic
As I have no knowledge of either of these scripts I cannot confirm or deny that. I simply copied them from ICANN’s board resolution. I expect they’re correctly spelled in the DNS.