skip to content

News

  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.

Ram Mohan named Afilias COO

Domain Name Wire - Wed, 03/06/2019 - 20:27

Long-time employee takes on a new role at Afilias.

Ram Mohan

Apparently it’s a big week for executive appointments.

Afilias has named Ram Mohan as Chief Operating Officer of the company. This is a new position and it appears it will take over a lot of the responsibilities of CEO Hal Lubsen. Most of Lubsen’s reports will now report to Mohan. Lubsen will still oversee finance, mergers and acquisitions and most legal.

Mohan has been with Afilias since 2001 when the firm started in order to launch .info. He has served as the Chief Technology Officer. He’s also very involved with ICANN and Internet Society (ISOC).

He has a BS in Electrical Engineering from Manipal Academy, an MBA from Bharathidasan University and an MS in Computer Science from Drexel University.

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Domain Name News Bytes for Wednesday, July 22
  2. 5 Reasons for Brands to Get Their Own New TLD
  3. .Info and .Mobi get Chinese approval
Categories: Domains

SXSW comes to Austin this week

Domain Name Wire - Wed, 03/06/2019 - 16:33

Annual tech, film and music conference starts this week.

The annual SXSW event starts in Austin this week. SXSW Interactive, which attracts tens of thousands of techies, runs March 8-12.

I reviewed the schedule and it looks like there aren’t any domain name-specific sessions this year. There used to be a handful of sessions, especially when new top level domain names were coming out.

Still, I expect some domain name companies to run marketing during the event, although nothing like in the past. .Co always went big during SXSW and Sedo organized some rather large promotions as well, including a Domain Village. If your company will be on the ground in Austin over the next week, feel free to leave a comment.

If you are coming, please bring your patience. For the first time since it became big, SXSW will not overlap with local schools’ Spring Breaks, including the University of Texas. It will be very congested.

 

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. At least 10 domain name companies heading to SXSW in Austin this week
  2. 5 Tips for your Visit to Austin for SXSW
  3. What to do at SXSW if you’re a domainer
Categories: Domains

L vs. I in domain names

Domain Name Wire - Wed, 03/06/2019 - 14:29

It’s easily confused.

There was a bit of a ruckus yesterday over a typo. NameJet promoted Investor.com for sale, but it turns out the domain was actually Lnvestor.com with an L. As you can see, the font NameJet uses makes a lowercase L look a lot like an uppercase I.

Before I throw stones, I should note that I made the same mistake a few years ago. I backordered Lnternational.com thinking it was International.com.

And that fake domain broker that was trying to sell domains at too-good-to-be-true prices? They used the same L vs. I trick

If you think this is confusing, imagine people who aren’t aware of internationalized domain names who buy something that appears to be a valuable domain, only to find out some of the characters in it aren’t from the Roman alphabet.

NameJet has an option to ‘view upper case’ next to the domains. I realize this is an edge case, but perhaps they should put both cases next to each other by default.

Oh, and be on the lookout. I don’t think I ever renewed Lnternational.com but it has remained in my Enom count anyway. It expires later this month and will make its way through the drops.

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. SnapNames gets Japan Registry, Afternic and NameJet get .buzz business
  2. New York City domain name auction tops $70,000 as RealEstate.NYC sells for $21,300
  3. NameJet sellers at center of shill bidding questions
Categories: Domains

Mormon church switching from 3-letter to 19-letter domain name

Domain Name Wire - Tue, 03/05/2019 - 17:52

Church goes from short to long with domain name switch.

The Church of Jesus Christ of Latter-day Saints is changing its domain name to a much longer domain name.

Visitors will soon go to ChurchofJesusChrist.org rather than LDS.org, which was short for Latter-day Saints.

While most organizations prefer a shorter domain to a longer one, there was a special circumstance here: Jesus said to do it. Well, assuming he foresaw the internet, he would have suggested it.

In a news release about the change, the Mormon church stated:

The Church of Jesus Christ of Latter-day Saints is the name of the Church Latter-day Saints believe came by revelation from the Lord Jesus Christ Himself (see Doctrine and Covenants 115:4). “Jesus Christ directed us to call the Church by His name because it is His Church, filled with His power,” President Russell M. Nelson has said.

The Church is now making changes to many of its communication channels to reflect the faith’s full name and better convey commitment to follow Jesus Christ…

Mormon.org will eventually be merged into the ChurchofJesusChrist.com domain as well.

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

February’s top domain name stories

Domain Name Wire - Tue, 03/05/2019 - 17:16

Here’s a look at the top stories on Domain Name Wire last month, as ranked by views.

1. How I almost lost a domain name this week – Even professional domain owners can let something slip through the cracks. Here’s what happened and how to make sure it doesn’t happen to you.

2. Speaker hit for reverse domain name hijacking – Based on a twitter conversation with the Complainant, he got some bad legal advice.

3. Calm.com domain name is paying dividends – Here’s how a great domain name is helping a $1 billion valuation company.

4. Be careful about this expired domain name metric – Dig into this metric before buying a domain name based on it.

5. Blockchain.io domain owner fights back against Blockchain.com – Paymium responds to domain name dispute.

Also check out last month’s podcasts. Click the link to listen or subscribe on your podcast app.

#225: Rick Schwartz
#224: Blockchain and Domain Names
#223: The Email Episode
#222: NamesCon Recap

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. DOMAINfest Hotel’s Domain is Expired
  2. Calm.com domain name is paying dividends
Categories: Domains

MMX reports strong start to 2019

Domain Name Wire - Tue, 03/05/2019 - 15:04

Domain name company touts topline growth to kick off 2019.

Top level domain name company MMX (Minds + Machines) (LSE:MMX) is reporting a strong start to 2019.

In an investor update issued today, the company said that domain registrations are up 38% year-over-year so far this year to 1.84 million registrations. Billings are up 129%. The company credits the first time contribution from ICM Registry domains as well as strong growth in China.

MMX is seeing a 91% renewal rate on .XXX domains, part of the ICM acquisition.

Donuts co-founder Dan Schindler is now a Special Advisor to the company to help it on its premium domains strategy. Schindler left Donuts a while back and recently resurfaced in the industry. Christa Taylor was also formally announced as the company’s Chief Marketing Officer. Taylor had consulted for the company starting last year and became CMO ahead of NamesCon this year.

The company plans to pay off its outstanding debt early this month.

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. MMX releases 2015 report, discusses go-forward strategy
  2. .VIP gets 75% renewal rate for early registrations
  3. MMX reports earnings: .XXX to help, one-off sales to hurt
Categories: Domains

Public Interest Registry (.Org) hires three new execs

Domain Name Wire - Tue, 03/05/2019 - 14:49

Song-Marshall, Abley and Vora join PIR executive team.

L to R: Judy Song-Marshall, Joe Abley, Anand Vora. Photos from LinkedIn.

Public Interest Registry (PIR), the non-profit that runs the .org top level domain name, has hired three domain name industry veterans to join its executive team. It is still searching for a Chief Financial Officer.

The three hires are:

Judy Song-Marshall, Chief of Staff: Judy comes from Neustar, where she was Director of Registry Services. She also ran product marketing for the company for over seven years and spent over 11 years at the company, according to her LinkedIn profile.

Joe Abley, Chief Technology Officer: Joe worked as Infrastructure Scientist at domain registry Afilias for the past year. He previously worked for Dyn and ICANN. Afilias provides the technical registry operations for PIR.

Anand Vora, Vice President of Business Affairs: Anand joins PIR from its new CEO Jon Nevett’s alma mater, Donuts. This is a round trip for Vora, who interned for PIR when he got his MBA at Goerge Washington University and started his career at the company as a product management specialist and then channel manager for Asia.

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. PIR (.org) makes changes to its sales practices
  2. Public Interest Registry (.Org) tax return provides insight into registrar marketing deals
  3. .Org sticks with Afilias for backend
Categories: Domains

How Instant Pot got its name (and domain)

Domain Name Wire - Mon, 03/04/2019 - 20:39

Inventor created program to find synonyms.

Instant Brands Inc., maker of the popular Instant Pot cooking appliance, is merging with housewares company Corelle Brands LLC.

Ottawa Citizen has the story on how Instant Pot inventor Robert Wang came up with the name for the now iconic device:

He tested recipes with his family and turned to computer science to come up with a name. After writing a program that matched synonyms for “fast” with synonyms for “cooker,” Wang arrived on Instant Pot. Luckily, the domain name was still available.

The story has some other interesting info about how Wang was able to build the business thanks to Amazon.

In an upcoming episode of the DNW Podcast I will interview a company and product namer and discuss some of the tools you can use to create new names.

(Hat tip: Bill Sweetman)

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

DNSSEC – DNW Podcast #226

Domain Name Wire - Mon, 03/04/2019 - 16:30

Domain Name System Security Extensions — what’s it all about?

You’ve probably heard about some recent hacks involving the domain name system. This week we’ll talk about how DNSSEC could help stem these attacks. Matt Larson, who co-hosts the Ask Mr. DNS Podcast and currently works at ICANN will explain what DNSSEC is, what’s required for it to work and the pros/cons.

Also: .Dev, Gandi acquired, Nominet comes to America, MarkMonitor going public and more.

This week’s sponsor: DNAcademy.com. Use code DNW for $50 off.

Subscribe via iTunes to listen to the Domain Name Wire podcast on your iPhone or iPad, view on Google Play Music, or click play above or download to begin listening. (Listen to previous podcasts here.)

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Paul Mockapetris, inventor of the DNS – DNW Podcast #100
  2. New Domain Transfer Policy – DNW Podcast #111
  3. Boost your domain sales chances – DNW Podcast #135
Categories: Domains

New .Com Winners & Losers

Domain Name Wire - Mon, 03/04/2019 - 14:53

NameSilo jumps on monthly list.

ICANN has published the latest official data from Verisign (NASDAQ: VRSN) about the .com namespace. This registrar-by-registrar report covers November 2018.

The only notable movement was NameSilo, which jumped from #10 to #6 on the monthly report. It’s currently the 11th largest .com registrar. You can read an interview with NameSilo’s CEO here.

Here’s how registrars did in terms of new .com registrations.

1. GoDaddy.com* (NYSE: GDDY) 865,438 (893,103 in October)
2. Alibaba (HiChina) 312,227 (204,213)
3. Tucows** (NASDAQ:TCX) 175,148 (183,542)
4. NameCheap Inc. 157,607 (139,033)
5. Xin Net Technology Corporation 152,143 (135,590)
6. NameSilo (CSE:URL) 130,713 (68,758)
7. Endurance+ (NASDAQ: EIGI) 123,087 (130,915)
8. Web.com++ 97,702 (105,815)
9. Google Inc. (NASDAQ: GOOGL) 88,236 (92,312)
10. United Internet^ (FRA: UTDI) 66,501 (71,257)

Here’s the leaderboard of the top registrars in terms of total .com registrations as of the end of November 2018.

1. GoDaddy* 49,370,531 (49,222,603 in October)
2. Tucows** 12,659,835 (12,709,575)
3. Endurance+ 7,179,580 (7,240,990)
4. Web.com++ 6,732,478 (6,730,384)
5. Alibaba 6,192,801 (5,972,559)
6. United Internet^ 5,666,856 (5,675,949)
7. Namecheap 4,515,221 (4,452,551)
8. Xin Net Technology Corporation 2,792,514 (2,639,761)
9. Google 2,057,844 (2,005,816)
10. GMO 1,964,580 (1,975,188)

Many domain companies have multiple accreditations and I’ve tried to capture the largest ones. See the notes below.

* Includes GoDaddy and Wild West Domains
** Includes Tucows and Enom
+ Includes PDR, Domain.com, FastDomain and Bigrock. There are other Endurance registrars, but these are the biggest.
++ Includes Network Solutions and Register.com
^ Includes 1&1, PSI, Cronon, United-Domains, Arsys and world4you

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. .Com Winners & Losers
  2. Google Domains tops 2 million .com domains
  3. .Com’s Top Registrars
Categories: Domains

Wow: Over 64,000 .Dev domain names registered

Domain Name Wire - Fri, 03/01/2019 - 16:13

The .Dev top level domain is off to a strong start.

Google launched the .dev top level domain name yesterday and the domain already has over 64,000 registrations.

The zone file for .dev on ICANN’s reporting system currently shows about 15,000, so it’s missing many of the domains. Still, based on my review of the zone file, it looks like last name and first/last name combos are popular; individual developers are buying their name ending in .dev. Development terms and company names are also popular.

While these numbers are slightly behind Google’s early success with .app, they are a lot higher than I expected. Google’s cachet with developers and its PR capabilities are certainly driving registrations.

The company is offering a free .dev domain for one year to applicants for this year’s Google I/O conference but this represents only a small part of the 64,000 registrations.

The entire .dev top level domain name is on the HSTS preload list, so .dev domain names need an SSL certificate in order to resolve. (Learn more about this here.)

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Uniregistry to release over one million domains through registrar channel
  2. Domain Connect promises to make connecting domains to web services easier
  3. Donuts chooses Rightside over Google Nomulus
Categories: Domains

Montefiore Investment acquires domain name registrar Gandi

Domain Name Wire - Fri, 03/01/2019 - 13:02

Private equity firm acquires domain name registrar with 2.5 million domains.

Private equity firm Montefiore Investment has acquired domain name registrar Gandi.

In a heartfelt blog post, Gandi CEO Stephan Ramoin explained the origins of the company and its values. One thing that’s unique about Gandi is that is has grown mostly by word-of-mouth; the company didn’t jump into the advertising game like many registrars.

With a private equity backer, Ramoin noted that the company will now look to acquire other businesses for the first time.

Gandi has revenues of over 37 million euros and 800,000 customers. More than half of its sales come from France, where it is located, but other regions have contributed substantially since the company created overseas subsidiaries in 2012. Gandi has more than 2.5 million domains under management.

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. CentralNic acquires Instra for $24 million, sells $3.6M in domains, and plans to raise $15M
  2. Bad guys get Gandi.net’s password to technical provider, redirect domains
  3. Frank Schilling sparked yesterday’s active day for Rightside
Categories: Domains

New TLDs, five years in

Domain Name Wire - Thu, 02/28/2019 - 21:36

 

It was five years ago this month that the first domains under the new top level domain (nTLD) program started rolling out to consumers. The first Latin script general availability domains came out in early February 2014.

Remember .guru? .Plumbing? Yeah, that was a long time ago.

Here’s how I’d sum up the first five years of new top level domains.

Demand and artificial demand

Registration numbers for new TLDs have not met expectations for just about anyone who put money into it. That includes the many registries that spent millions acquiring strings as well as ICANN.

I thought new TLD applicants were very bullish, but even I was surprised when the first sunrises got only a couple hundred registrations.

Applicants should have understood the market size better. People were looking at registrations in .com and predicting market size for new TLD strings but many applicants expected some magic demand to come out of nowhere. The reality is that there are only so many people creating a website at a given time. They’re going to look for a .com or ccTLD name. If they don’t get that then they might consider a new TLD. So new TLD demand for people creating websites is a subset of total site creator demand. Without a catalyst for more people to create websites, demand won’t shoot up.

Of course, if you look at the headline registration numbers, some domains seem to be doing really, really well. .Top has 3.8 million domains in the zone and .XYZ has over 2 million.

But we all know at this point how these numbers were manufactured. A lot of registries took the “fake it til you make it” approach. They boosted their numbers through giveaways (and near giveaways).

This worked in some respects. .XYZ got a lot of attention when companies saw its numbers take off. Some companies used .xyz domains as a result.

Cheap domains have a downside, though. Spammers and criminals churn through domain names so they like cheap ones. There’s a fairly tight correlation between domain price and quality of a namespace. Unfortunately, the bad reputation of some new TLDs has given new TLDs a bad rap overall in security circles.

The reality is that registration and usage growth should be slow. I wish there was a catalyst for domain demand to shoot through the roof but there quite simply isn’t one at this time.

The earlier the better

.Guru still has over 60,000 names in its zone. It would have a fraction of that if it came to market later.

Until .app, .guru has the most pre-orders of any domain at GoDaddy. I don’t think anyone would look at the total pool of new TLDs and suggest that .guru belongs where its numbers put it.

It had first-mover advantage among “generic” new TLDs.

Speaking of which, this might be why some people had unrealistic expectations for new TLD registration numbers. They looked at .co and .xxx and extrapolated. But these names did as well as they did because they had very little competition. They had an advantage that most new TLDs don’t have. The environment has changed.

The earlier new TLDs also had an advantage because domainer wallets weren’t tapped out.

Crazy auction prices

I understand companies paying millions of dollars to acquire strings before we had a good idea of registration volumes. But I was perplexed as contention set auction prices continued to soar even after reality set in.

How can anyone justify spending $10M plus on a string that has a possible “real” registration base of 10k-20k domains at modest prices? Some of these acquisition costs will never be paid back. Even on a ten-year payback, that’s a horrible investment.

I realize that registries got cash infusions by losing contention set auctions but it doesn’t make sense to blow that cash (real cash in the bank!) on other strings just because you got a windfall.

What does Verisign think?

As it turns out, new TLDs had little impact on .com. But it was shocking when Verisign sued XYZ for some of the comments it made about .com and how well .xyz was doing. (Verisign lost.)

That lawsuit was the first big indication that Verisign had concerns about the impact of new TLDs on .com. Its messaging changed during the lawsuit when it said actually it was .net that was hurt. I’m still a bit confused what this lawsuit was all about. I’ve heard people say it was Verisign’s effort to shut up new TLD folks that were bashing .com. I don’t know. I don’t understand many of the decisions Verisign makes.

IDN transliterations of .com are a dud

There’s not much to say here. The idea that .com transliterations would make IDN.com domains worth a lot was flat-out wrong.

Amazon’s slow roll

Amazon made several surprising moves with new TLDs.

First is that it applied for so many. 76.

Second is that it didn’t plan to open them up to the public, at least at first. That changed when the community got upset about “closed generics”.

Third is that Amazon has done so little with its TLDs. Why hold these strings only to neuter them with over-the-top restrictions? I realize Amazon is a big company and these domains won’t move the needle, but the company could get an ROI on some of them by selling to other registries. If they don’t have plans for a string in the next few years, why not shop them?

Registry technical service costs fall…a lot

One new TLD operator told me he thinks the technical backend registry cost of first-year creates is headed to zero. He might be right.

There are so many competent companies providing registry backend technology. They bid aggressively to win contracts with cut-rate pricing.

Of course, the registry for .com domains still gets a whopping $7.85 per registration. And that might go up soon.

Donuts

No discussion of the first five years of new TLDs would be complete without mentioning Donuts.

The company applied for over 300 TLDs. It bought Rightside and now has about 240 strings in its portfolio. Last year it was acquired by private equity firm Abry Partners in a competitive process.

Let’s face it; Donuts did it right. It understood how contention sets would be settled and how to play this game. Its massive portfolio approach smoothed out its “bad” TLD choices and its overhead is spread out over hundreds of strings.

Even though I’m sure Donuts didn’t hit its best case forecasts, its founders made the smartest play in this round of domain expansion.

What’s next?

We’ll see more consolidation in the new TLD space. This will speed up as more TLD operators face reality. There will also be another round with some twists and new rules. It will be a while, though.

That’s my take. What do you think?

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Final new TLD objection tally: Donuts 55, Amazon 24, Google 22
  2. Donuts: Verisign trying to intimidate, bully competitors with .XYZ lawsuit
  3. Minds + Machines acquires .XXX top level domain operator ICM Registry
Categories: Domains

Google launches .Dev domain in general availability, free domains for I/O

Domain Name Wire - Thu, 02/28/2019 - 17:51

Google releases its latest top level domain name.

Google’s .dev top level domain name entered general availability today after a Dutch auction early access phase. Most registrars are offering the domains for $15 or less.

Over 2,000 .dev domains were added to the .dev zone file yesterday, bringing the total through sunrise and early access to just shy of 5,000 according to nTLDStats. About half of the domain are registered through Google’s own registrar.

The company is giving .dev domains away for one year to everyone who applied for a ticket to Google I/O 2019. The company declined to disclose to DNW how many domains this possibly represents.

I expect .dev to be popular with individual developers and development teams within companies. I don’t expect it to take off like .app did, though. .App currently has 370,000 domains in the zone.

.Dev uses HSTS preloading so all .dev domains need an SSL certificate in order to resolve. (Learn about HSTS preloading in this podcast with Google.)

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Domain Stocks Pummeled
  2. Google and Amazon compete on 21 new top level domain applications
  3. Google registers Stories.google domain name
Categories: Domains

Cover.com buys Cover.ca and 15 other end user domain sales

Domain Name Wire - Thu, 02/28/2019 - 15:39

The company that paid $825,000 for Cover.com just bought Cover.ca for $10,000.

This week’s top public sale at Sedo was a new top level domain: buy.game for $29,999. I can’t figure out the buyer but it’s worth noting that buy.gameS was also purchased recently, suggesting that someone is getting ready to start a games website on one of these domains and thought it wise to get both versions.

I can’t be sure this is an end user at this price so I didn’t add it to the list below, but keep an eye on these domains!

Lads.com leads Sedo’s end user list this week, and check out what insurance company Cover paid for the .ca version of its Cover.com domain name.

Here are the end user sales from Sedo last week I was able to uncover. You can view previous lists like this here.

Lads.com €22,999 – I don’t know who the buyer is but I’m going to call this an end user sale because the nameservers changed to Microsoft services at microsoftonline.com. The domain doesn’t resolve yet.

Cover.ca $10,000 – The insurance company that paid $825,000 to buy Cover.com paid a lot less to get Canada’s .ca version of the domain.

2050.org €10,000 – The highest sale via the SedoMLS Reseller network went to a technology volunteer program for Chinese Youth.

Lipoedem.com €6,000 – Forwards to moeller-medical.com/vibrasat.html. Lipoedem is a liposuction device manufactured and distributed by the German company, Möeller Medical.

CarDr.com $5,000 – The buyer remains a mystery due to GDPR, but they have uploaded a logo on the site that suggests some sort of car repair and maintenance service will use the domain.

AMTAuto.com $3,880 – AMT Contract & Leasing is an auto leasing company in the UK.

Gremler.com $3,600 – A guy in Iowa with the last name Gremler. I wish I could buy my last name dot com for so little.

CST.ch €3,000 – That stands for Cargo sous terrain. I believe the buyer is this organization which is creating a goods transport system in Sweden. It uses the domain cargosousterrain.ch.

APCOvernight.com $2,984 – This currently forwards to APC-Overnight.com, a UK-based package delivery service and network. Their domain purchase is an upgrade from the hyphenated version.

PopupVR.com $2,500 – Beatshapers Ltd is a virtual reality game creator.

IconPro.com $2,500 – Forwards to IconPro-AI.com, a German software and consultancy firm providing automation solutions as well as workshops and seminars.

Nordwerk.de €2,380 – Forwards to Nordwerk-Folien.de, a German foil packaging provider.

Society.ai $2,300 – A website in development for the self-proclaimed “Think- & Do- Tank about Artificial Intelligence”.

Avatars.ai $2,000 – Forwards to PR.ai, PRAI: Portal of Robotics and Artificial Intelligence.

Xlink.ai $2,000 – Guangzhou Xlink IoT technology Ltd. in China.

AlliedCloud.com $2,000 – Allied Cloud is an Oracle | NetSuite Alliance Partner that helps companies migrate from legacy software to NetSuite.

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. End user domain name purchases including State Street and Live Person
  2. What domain names Shell and other end users bought last week
  3. A BIG week for end user domain name sales
Categories: Domains

Nominet opens Washington D.C. office, plans to hire 30

Domain Name Wire - Thu, 02/28/2019 - 14:41

North America business will focus on security.

Nominet is opening a U.S. office for its cyber security services.

Nominet, the company that runs the .uk domain name registry, has opened a U.S. office in Washington, D.C.

The office is currently stationed in a WeWork location, but Nominet CEO Russell Haworth told the Washington Business Journal that it could expand to about 30 employees in D.C. in the next two to three years.

Nominet’s D.C. location will give the organization a position in North American to sell its Nominet NTX security solutions. The organization has parlayed its experience with the domain name system into a security business that operates at the DNS level.

In addition to the company’s domain name and security products, Nominet also has a spectrum management business line.

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Nominet to offer second level .uk domain names, with .co.uk owner getting priority
  2. Nominet sets June 10 date for shorter .UK domain names
  3. .UK adds registry lock option
Categories: Domains

MarkMonitor parent Clarivate going public through merger deal

Domain Name Wire - Wed, 02/27/2019 - 18:43

SPAC gobbles up Clarivate Analytics, the company that owns MarkMonitor.

Brand protection domain name registrar MarkMonitor will soon be part of a public company.

MarkMonitor parent company Clarivate Analytics is merging with Special Purpose Acquisition Company (SPAC) Churchill Capital Corp. Churchill raised $690 million in an IPO last September, the most raised in a SPAC IPO last year. A SPAC is created with the specific purpose of acquiring another company.

Private equity and asset management firms Onex and BPEA carved out Clarivate from Thomson Reuters in 2016. They will roll 100% of their existing equity in the firm into the deal.

Clarivate had $968.5 million in revenue in 2018, up from $917.6 million in 2017. 82% of 2018 revenue was subscription-based.

The deal gives Clarivate an initial enterprise value of approximately $4.2 billion. That values it at about 12x adjusted revenue.

Once the deal is final, Clarivate plans to be listed on the New York Stock Exchange under the symbol CCC.

© DomainNameWire.com 2019. This is copyrighted content. Domain Name Wire full-text RSS feeds are made available for personal use only, and may not be published on any site without permission. If you see this message on a website, contact copyright (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Frank Schilling sparked yesterday’s active day for Rightside
  2. It’s official: GoDaddy owns Host Europe Group
  3. Rightside reports $14.4 million revenue in Q1, new TLD revenue stalls
Categories: Domains

Google publishes their TLD registry software: Nomulus

Domain Name News.com - Tue, 10/18/2016 - 09:42

Google announced this morning that they are releasing their TLD registry platform, Nomulus, which is written in Java, under an Apache 2.0 license. The company uses the software to run their own registry for their TLDs. Portfolio TLD applicant Donuts has partnered with Google and contributed to the source code – they will also be running a public test instance of the system, which is geared towards being run on the Google Cloud Platform. So far, Rightside (NASDAQ: NAME) has been operating Donuts’ registry backend.

Also covered by:

Here’s the full press release:

Introducing Nomulus: an Open Source Top-Level Domain Name Registry

Date: Tuesday, October 18, 2016 8:00am PT

Author: Ben McIlwain, Software Engineer

Today, Google is proud to announce the release of Nomulus, a new open source cloud-based registry platform that powers Google’s top level domains (TLDs). We’re excited to make this piece of Internet infrastructure available to everyone.

TLDs are the top level of the Internet Domain Name System (DNS), and they collectively host every domain name on the Internet.  To manage a TLD, you need a domain name registry — a behind-the-scenes system that stores registration details and DNS information for all domain names under that TLD. It handles WHOIS queries and requests to buy, check, transfer, and renew domain names. When you purchase a domain name on a TLD using a domain name registrar, such as Google Domains, the registrar is actually conducting business with that TLD’s registry on your behalf. That’s why you can transfer a domain from one registrar to another and have it remain active and 100% yours the entire time.

The project that became Nomulus began in 2011 when the Internet Corporation for Assigned Names and Numbers (ICANN) announced the biggest ever expansion of Internet namespace, aimed at improving choice and spurring innovation for Internet users. Google applied to operate a number of new generic TLDs, and built Nomulus to help run them.

We designed Nomulus to be a brand-new registry platform that takes advantage of the scalability and easy operation of Google Cloud Platform. Nomulus runs on Google App Engine and is backed by Google Cloud Datastore, a highly scalable NoSQL database. Nomulus can manage any number of TLDs in a single shared instance and supports the full range of TLD functionality required by ICANN, including the Extensible Provisioning Protocol (EPP), WHOIS, reporting, and trademark protection. It is written in Java and is released under the Apache 2.0 license.

We hope that by providing access to our implementation of core registry functions and up-and-coming services like Registration Data Access Protocol (RDAP), we can demonstrate advanced features of Google Cloud Platform and encourage interoperability and open standards in the domain name industry for registry operators like Donuts. With approximately 200 TLDs, Donuts has made early contributions to the Nomulus code base and has spun up an instance which they’ll be sharing soon.

For more information, view Nomulus on GitHub.

No related posts.

Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.