Dynadot - new IDN filter

[dynadot]

Thanks for the great ideas! I will definitely pass this on to the team. We are actually working on some upcoming search changes. For now though, I did want to mention that you can set your Dynadot searches to show certain TLDs that you prefer. The settings will apply to all of our searches, but it will help you put the TLDs you're most interested in at the top when you do a search while you're signed into your account. Here are some instructions on how to set that up: https://www.dynadot.com/community/he...earch-settings

[dynadot]

Happy Friday, everyone!

[clipper]

Originally Posted by dynadot

Happy Friday, everyone!

Hey Dynadot, you said you were meeting with Verisign at the end of October.

Here's some data you might want to bring to the table regarding Japanese IDNs, "premium" IDNs and sales thus far. Perhaps you already have it or are aware of it in real time.

This is from about a week ago.

My only reference is your retail price and Japanese .コム, so that's how I've divided these, and the revenue total is registrar gross, since we don't know the wholesale price of these names.

Note that the largest premium tier is the sixth, which comprises over 26,000 names and is roughly 70% ASCII. I have no idea how many have been registered, since you'll only allow me to search 1,000 at a time.

I think that this quick breakdown will give you a decent idea of where the breaking point is for valuing these things going forward. When less than 2% are being sold at a premium price, then the price is too high.


Tier 1 ($30,000):
Total: 656 (All ASCII)
Registered: 13
Revenue: 390,000

Tier 2 ($14,400)
Total: 246 (74 ASCII / 171 Japanese)
Registered: 12 (5 ASCII / 7 Japanese)

Tier 3 ($1,440)
Total: 528 (All Japanese)
Registered: 22

Tier 4 ($720)
Total: 1,123 (All Japanese)
Registered: 52

Tier 5 ($360)
Total: 10,616 (7,632 ASCII, 2984 Japanese)
Registered: 198 (25 ASCII, 173 Japanese)

Gross Revenue: $703,200
ASCII Revenue: $471,000
IDN Revenue: $232,200

ASCII revenue far outpaces native language, but Verisign can't conceivably build its brand on mixed-script names like sex.コム ($1,440). And native-speakers and investors simply aren't willing to pay at these prices.

$360 was the price of some very desirable Japanese premiums that I decided to drop at a loss. (I, in fact, purchased NO names in either Japanese or Korean at premium prices, except for one that was later pulled from me and refunded).

Verisign is right to price ASCII and numbers investors into the stars, but all signs point to us IDN investors (even in a developed market such as Japan) cutting our losses if premium pricing is this high going forward.

It is important to note that Japanese .コム was a great success, largely because it has the most developed economy of all of the countries being represented by Verisign's IDNs. It would be silly to expect the same sort of investment in languages where per capita GDP is 1/3 that of Japan (China - 1/3, India - 1/6, Thai - 1/3). Further, noting that only 1/3 of premium revenue came from IDNs might dissuade them from the tactic in the future.

I have a strong hunch that Korean native language premium numbers are far worse, but I have no list to check.

[idn]

.コム was a great success

?

[clipper]

Originally Posted by idn

.コム was a great success

?

What did it cost? $250k plus personnel/time? For $700k+ in revenue over six months? Yes. In the short term it is a success.

[Drewbert]

Very informative post. Thanks!

[squirrel]

Originally Posted by clipper

What did it cost? $250k plus personnel/time? For $700k+ in revenue over six months? Yes. In the short term it is a success.

Not material to a billion dollars company however

[dynadot]

Thanks. I've passed these ideas onto the team and we will see if this is something that we can implement in the future.

[Drewbert]

Just as an aside, when I get domain offers sent to me via your messaging system, if the offerer has used a currency symbol, it isn't encoded correctly.

Can you have your guys look at your messaging system please, to make sure it's all UTF-8 and not doing any weird encoding?

[dynadot]

I'll ask the team about that, but it may be your browser. What is the browser you're using, Drewbert?

Also, thanks for the info about the Japanese TLD, clipper. I did meet with Verisign and did talk to them about IDN premiums and relayed your feedback. They took it well, but I don't know if they'll make any changes. They also didn't have any dates for any upcoming launches yet. Hopefully they'll announce the dates soon and when they do I will definitely post the info here.

[Drewbert]

I doubt it's my browser. It looks like the classic double-encoded Unicode to me.

http://www.yunker.io/2013/05/18/doub...data-in-mysql/

Have your tech guys check out message ID 82193.

[Drewbert]

IDN search page still brings up ASCII TLD's as default. What's with THAT?

[dynadot]

Thanks, I'll let our engineering team know to look at that message specifically.

As for the ASCII TLDs coming up first, that is based on how we set up our search, but you can actually adjust your settings to see the TLDs that you prefer instead. Here are the instructions on how to do that: https://www.dynadot.com/community/he...earch-settings

[Drewbert]

You don't see the irony in having a special IDN search page, but presenting it with defaults of ASCII TLDS (some which don't even offer IDN) instead of listing all the IDN TLD's for the default?

That's great that you allow account holders to specify their defaults, but I have ASCII and IDN portfolios. When I search for ASCII, its invariably in .com. When I search for IDN, it's in whatever language .com I'm after.