Sells for $23k at Sedo and makes #3 on the weekly sales chart at DNJournal.
Translation is a great name, but it has very modest traffic numbers: 13,850 according to .de overture.
German IDN are also subject to ASCII traffic leakage. i.e. people typing in ubersetzer without the umlaut.
Nevertheless, a good start to Domains 2.0.
What, if any, protections are in place to address such collisions? Any sunrise periods applied "for those extra periods"? :)
Anyone aware of any arbitration proceedings or trademark infringement cases that have arisen since the addition of IDN domains?
. . . there but for an umlaut or a squiggle go I . . .?
It will be interesting to watch the collisions happening between the pre-IDN verion (the word) and the post IDN verions (word with IDN mark-up) of "same subject websites".
That is a great question... can the new IDN owner argue that their IDN is the correct term and that the non-umlaut domain name is a typo?
As an investor I'd rather stick to non-latin based character set IDN where there can be no confusion. i.e. CKJ and Russian.
That's good news if it's a UDRP precedent. Were the judgements for .com or .de?
