Recent Posts
- Alibaba, Name.com among new RDRS opt-ins
- The Swiss can register .swiss domains from next week
- .ai up to 425,000 domains
- A million “free” .music domains up for grabs
- D3 to get $5 million in crypto to apply for .ape gTLD
- Alibaba hit with ICANN breach notice
- New Vegas conference “Davos for Web3 interoperability”
- ICANN content policing power grab may be dead
- Cable company unplugs its dot-brand after acquisition
- Germany crosses 10,000 dot-brand domains milestone
- Founders out as Com Laude gets equity injection
- PIR’s Diaz to leave domain industry
- Some registrars have already quit ICANN’s Whois experiment
- ICANN opens $217 million Grant Program
- Internet could get one-letter gTLDs (but there’s a catch)
- .ai registry fights deadbeats with tweaked auction rules
- Amazon and Google among .internal TLD ban backers
- .ai registry advises buyers not to use GoDaddy
- .post liberalizes with new sunrise period
- Team Internet spends $41 million on content farm
- Epik backtracks on Kiwi Farms claim after legal threat
- .austin names launch on blockchain
- Freenom shuts down 12.6 million domains — report
- GoDaddy’s next .xxx contract may not be a done deal
- GlobalBlock blocking 2.5 million domains
- Microsoft moving its cloud apps from .com to .microsoft
- ICANN 79: anonymous trolls and undercover lawyers
- ICANN scores win in single-letter .com lawsuit
- Cosmetics brand terminates its gTLD
- Up to 70 jobs on the line at Nominet as .uk regs dwindle
- Governments back down on new gTLD next round delay
- Private auctions could be banned in new gTLD next round
- ICANN meeting venue “insensitive and hurtful”
- GoDaddy to start selling graphic.design domains
- GAC spinning up new gTLD curveball at ICANN 79?
- GoDaddy’s GlobalBlock supports blockchain names
- Police .uk domain takedowns dive in 2023
- GoDaddy wants to cut the bullshit from .xxx
- Dueling domain blocking services to launch at ICANN 79
- Freename tries to bridge DNS and blockchain
- Olive retires from ICANN
- Whois policy published without life-saving disclosure rule
- UK gov takes its lead from ICANN on DNS abuse
- Tucows reports 2023 results
- Twitter “completely unresponsive” on clickable domains
- ICANN spends $5 million more than planned in first fiscal half
- .art takes a million domains off its premium list
- KeyTrap ‘the most devastating vulnerability ever found in DNSSEC’
- Freenom settles $500 million Meta lawsuit and will exit domain business
- New gTLD lottery to return in 2026
- First GlobalBlock prices revealed — they ain’t cheap
- Domain universe grows on new gTLDs despite .com shrinkage
- D3 signs up crypto gTLD client number five
- GoDaddy reports strong domains growth
- How to qualify for a $40,000 gTLD
- Registry service provider evaluation handbook published
- WebUnited inks deal to “mirror” country’s TLD in the blockchain
- GoDaddy project unveils brand-blocking calculator
- Report: Monster “misappropriated” millions from Epik
- .com is shrinking but Verisign raises prices again anyway
- D3 announces fourth crypto new gTLD client
- Donald Trump loses second UDRP case
- UK cybersquatting complaints hit record low
- No excuses! PIR to pay for ALL registries to tackle child abuse
- ICANN insists it is working on linkification
- Namecheap sues ICANN over .org price caps
- GoDaddy offers free Ethereum blockchain integration
- Epik reveals who is running the company
- Epik gets acquired again! The plot thickens…
- Airline gTLD crashes and burns
- First chunks of new gTLD Applicant Guidebook drop
- Epik to reveal its owners soon
- Another crypto firm to apply for a new gTLD
- Monster and Royce are NOT involved in Epik?!
- Nominet to overhaul .uk registry, turn off some services
- Russia blames DNSSEC, not Ukraine, for internet downtime
- Team Internet says revenue beat estimates
- Sold for over $20k, insure.ai and dog.ai back in .ai’s expired names auction
- .ai helps UDRP cases rise in 2023, WIPO says
- Freenom’s domains land at Gandi after termination
- .ru domains fly off the shelf as Western sanctions bite
- ICANN picks its first ever Supreme Court
- Lebanon’s ccTLD going back to Lebanon after ICANN takeover
- ICANN picks the domain it will never, ever release
- ICANN approves domain takedown rules
- Has Epik gone “woke”?
- First bits of new gTLD Applicant Guidebook expected next week
- ICANN bans closed generics for the foreseeable
- You can’t use money to buy .box domains
- After 14 years, ICANN practices what it preaches on IDNs
- Weak demand for private Whois data, ICANN data shows
- .ing doing way better than .meme
- DNS Women barred from ICANN funding?
- Dev releases free open-source TLD registry platform
- INCO flips a gTLD to Identity Digital
- Anguilla fears the .ai junk drop
- Five more gTLDs get launch dates
- $10 million of ICANN cash up for grabs
- Almost 50,000 .ai domains sold in a quarter
- ICANN threatens to regulate your speech [RANT]
- Life insurance company kills dot-brand
- ICANN finds new home for Lebanon’s TLD after founder’s death
- ICANN begs people to use its new Whois service
- Shiba Inu outs itself as crypto new gTLD applicant
- Over 50,000 .ai domains sold in three months
- Amazon planning new push into registrar market?
- Registries and registrars vote ‘Yes’ to new DNS abuse rules
- ICANN predicts flattish 2025 for domain industry
- Fast-growing Gname buys another 150 registrars
- GoDaddy service to let you block domains in over 650 TLDs
- Did I find a murder weapon in a zone file?
- ICANN drops the “man” from Ombudsman
- Have your say on police domain takedown powers
- Most registrars are shunning ICANN’s new Whois system
- Nominet to take over .gov.uk
- ICANN picks Istanbul for 2024 meeting
- ICANN’s private Whois data request service goes live
- .au regs slide on 2LD anniversary
- ICANN accused of power grab over $271 million auction fund
- A registrar is getting blamed for an Israeli war propaganda site
- Two more dot-brands bite the dust
- Google sells five-figure AI domain and six-figure .ing hack
- .blackfriday is still a bit rubbish
- Internet Naming Co acquires five more gTLDs
- Domain universe grows despite .com drag
Rejected Bulgarians want ICANN appeal
Kevin Murphy,
November 29, 2010, 19:36:18 (UTC),
Domain Registries
A handful of Bulgarian internet users have asked ICANN for the right to appeal the rejection of .бг, the proposed Cyrillic country-code top-level domain.
ICANN has received five emails from from the country in the last week, all expressing frustration that .бг (.bg) was turned down with no public explanation and no right to reply.
The string was rejected in May due to what ICANN determined was its confusing visual similarity with Brazil’s ccTLD, .br.
Polls of the Bulgarian people have been unable to find consensus on a suitable alternative, and the government has repeatedly said it would like to apply again or appeal.
Whether to introduce a right of appeal for rejected applicants is one of the topics ICANN is currently soliciting comments on as part of the review of its IDN ccTLD Fast Track program.
Bulgarian freelance developer Stoyan Danev wrote in his comment:
The Bulgarian community has clearly demonstrated that selecting another string is unacceptable and if the proposed one is not approved, Bulgaria will remain WITHOUT an IDN ccTLD. This is really against the ICANN policy of making Internet accessible to everyone.
He questioned whether .бг really is confusable with .br, linking to the Unicode web site, which suggests that б can be confused with 6 but not b, to prove his point.
Another commenter suggested that that the .бг registry could make it a matter of policy to only accept registrations at the second level that include at least one uniquely Cyrillic character.
Is really Bulgarian Cyrillic .бг (.bg) similar to other Latin ccTLDs?
Bulgaria has proposed for an IDN ccTLD the string .бг (Cyrillic for .bg, or U+0431 U+0433), but the proposal was turned down by the ICANN DNS Stability panel in May 2010 without any arguments or an option for appeal.
The proposed string is composed of two characters:
U+0431 CYRILLIC SMALL LETTER BE (б) and
U+0433 CYRILLIC SMALL LETTER GHE (г)
Reading the tables, provided with Unicode Technical Standard #39, (http://www.unicode.org/Public/security/revision-04/confusables.txt) I see that confusable characters are only:
0431 ; 0036 ; SL # ( б → 6 ) CYRILLIC SMALL LETTER BE → DIGIT SIX #
0433 ; 0072 ; ML # ( г → r ) CYRILLIC SMALL LETTER GHE → LATIN SMALL LETTER R #
As a result, we see that the applied string .бг could be confused only with the string .6r, which does not exist.
The Russian case
Opponents to the Bulgarian proposal say that Russia first wanted to apply for .ру (Cyrillic for .ru), but then selected another one, because .ру was found to be confusingly similar with the Paraguayan ccTLD .py , and because of this, Bulgaria must be obedient and select another IDN string.
Looking again at Unicode Technical Standard #39, I see that:
0440 ; 0070 ; ML # ( р → p ) CYRILLIC SMALL LETTER ER → LATIN SMALL LETTER P #
0443 ; 0079 ; ML # ( у → y ) CYRILLIC SMALL LETTER U → LATIN SMALL LETTER Y #
We have absolute similarity here! Very different than the Bulgarian case with 50% similarity.
Russia selected and received the .рф (Cyrillic for .rf) string. Looking for a third time at Unicode Technical Standard #39, I see that:
0440 ; 0070 ; MA # ( р → p ) CYRILLIC SMALL LETTER ER → LATIN SMALL LETTER P #
0444 ; 0278 ; ML # ( ф → ɸ ) CYRILLIC SMALL LETTER EF → LATIN SMALL LETTER PHI#
What do we have here? One similar character, and one not similar to a Latin basic character. So, how is this different from the Bulgarian case? Its the same! How the Russian string was approved, and the Bulgarian – not???
The DNS Stability panel rankings
[6] Both characters are visually identical to an ISO 646 Basic Version (ISO 646-BV) character.
[5] One character is visually identical to, and one character is visually confusable with, an ISO 646-BV character.
[4] Both characters are visually confusable with, but neither character is visually identical to, an ISO 646-BV character.
[3] One character is visually distinct from, and one character is visually identical to, an ISO 646-BV character.
[2] One character is visually distinct from, and one character is visually confusable with, an ISO 646-BV character.
[1] Both characters are visually distinct from an ISO 646-BV character.
The panel said that Bulgaria fails under [4] or [5], so the string is not accepted, because rank [4] or more is not good.
But, from my findings here, the Bulgarian (as the Russian) strings fail under [2] or [3], and its perfectly fine to be approved.
Security proposals
As another participant in the public comment forum said, two security proposals must be implemented:
“1. All names in the .бг (.bg) IDN ccTLD must be registered only with Cyrillic letters.”
“2. All names in the .бг (.bg) IDN ccTLD must contain at least one letter, which can be visually distinguished from the Latin alphabet (one of the letters: б, г, д, ж, и, й, л, п, ф, ц, ч, ш, щ, ъ, ь, ю, я).” (“г“ may fail off this list, because of my findings.)
Examples
There must be really conservative people in the DNS Stability panel, who don`t like seeing domains like:
– раурал.бг because people would confuse it with paypal.br
Come on, раурал.бг and paypal.br ? Compare with paypal.it and paypal.lt ?
Others are afraid of seeing:
– руса.бг and pyca.br (whatever this means in Brazilian Portuguese) – check the second security proposal. The first domain can`t exist.
– – – – –
Dear DNS Stability panel members, what is wrong here?
Dear ICANN Board members, Bulgaria needs an appeal procedure!
Cheers,
George Todoroff
[…] Rejected Bulgarians want ICANN appeal […]