Recent Posts
- ICANN got hacked by crypto bots
- Revenue dips as Brexit whacks .eu in 2018
- auDA rejects domaining ban but approves second-level domains
- KPMG dumps .com for dot-brand gTLD
- David and Goliath? DotMusic confirms .music win
- Neustar loses most of its Amazon back-end biz to Nominet
- ICANN takes the reins again as .amazon talks fail
- Italian bank is the latest dot-brand to bow out
- .music update: I’m calling it for Costa
- ICA opposes Aussie domaining ban
- “Just give up!” ICANN tells its most stubborn new gTLD applicant
- Did Roussos pull off the impossible? Google, Donuts, Radix all drop out of .music race
- “Stringent” new online censorship law could affect domain companies
- Looks like .music is finally on its way
- .blog tops 200,000 regs due to WordPress partnership
- .london disaster leads to mixed 2018 for MMX
- ICANN waves goodbye to Adobe Connect over security, pricing
- Donuts raises prices on most TLDs by up to 9%
- .com outsells new gTLDs by 2:1 in 2018
- CentralNic gets 680,000 AlpNames domains for free, kinda
- NameSilo nets $1.5 million profit
- Registry offers “$2,500” in sweeteners for .inc registrants
- Most .uk registrants not interested in .uk
- Australia likely to BAN domaining
- Root servers whacked after crypto change
- XYZ weighs into Epik controversy with .monster fundraising domain
- After NZ shooting, Epik has a Monster PR problem
- Another dot-brand bites the dust
- Whois vacuum AppDetex raises $10 million
- The DNS’s former overseer now has its own domain name
- Tucows splurges $30 million on Ascio
- UDRP complaints hit new high at WIPO
- .vu to relaunch under mystery new registry
- AlpNames could get PAID for abandoning its customers
- O.com might be a one-off for Verisign
- Andruff escalates Disspain feud, asks ICANN to ban him from chair
- Rumors swirl as AlpNames suffers “days” of downtime
- ICANN plays tough over Amazon dot-brands
- Data beats Merdinger to head universal acceptance group
- Radix sees revenue up 30%
- Verisign gets approval to sell O.com for $7.85
- At eleventh hour, most .uk registrants still don’t own their .uk names
- Mohan takes the reins at Afilias
- Trademark posse fails to block Whois privacy policy
- Nevett headhunts top execs from three rivals
- Internet to lose its .co.ck? Cook Islands mulls name change
- Donuts founder replaces Pitts as MMX’s premium guru
- Phishing still on the decline, despite Whois privacy
- Registrars given six months to deploy Whois killer
- Neustar completes .in migration
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.