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.
  • : 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.

.App continues to soar, sets records at GoDaddy

Domain Name Wire - Mon, 05/07/2018 - 16:50

Domain is headed for biggest new TLD launch yet.

I might sound like a broken record here, but .app continues to outperform essentially all new top level domain name launches to date.

Although it’s not reflected in the zone file, Google’s Ben McIlwain reports that over 7,500 domain names were registered during day five of the early access phase.

That puts all other new TLDs to shame.

I continue to get cancellation notices on pre-orders I placed since the domains are no longer available.

This morning, GoDaddy VP Paul Nicks confirmed to DNW that .App is its biggest new top level domain launch to date in terms of pre-orders at the registrar. Every day of early access has beaten the same day of other new TLD early access periods, and it has more pre-orders than any other domain.

Prior to .App, .Guru was the largest (it was first) and .VIP was second in terms of volume at GoDAddy.

Given these results, you might want to adjust your strategy if you have a pre-order domain. Remember, if more than one person has pre-ordered a domain at GoDaddy then you’ll wind up in an auction. It might be worth paying the day 7 EAP price today rather than risk an auction.

© DomainNameWire.com 2018. 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. Namecheap jumps up .Com leaderboard
  2. GoDaddy has a $12,500 price tag for Donuts’ Early Access Program
  3. GoDaddy (GDDY) reports earnings, domain revenue of $263.3 million
Categories: Domains

Jean-Noël Frydman discusses his France.com saga – DNW Podcast #184

Domain Name Wire - Mon, 05/07/2018 - 15:30

France took his domain after 24 years. Now he’s fighting to get it back.

Jean-Noël Frydman operated France.com for more than two decades before the French government organizations he previously partnered with decided they wanted the domain. They sued in French court and won the domain. Now Frydman is fighting to get the domain back. Hear his incredible story on today’s podcast. Also: MMX acquires ICM Registry, how you can get ready for GDPR and Google’s .App.

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

© DomainNameWire.com 2018. 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. Big companies and domain names – DNW Podcast #112
  2. Panama, Sherpas and the Domain Market with Andrew Rosener – DNW Podcast #180
  3. Meet Erik Bergman, who paid $900k for Great.com – DNW Podcast #182
Categories: Domains

Namecheap jumps up .Com leaderboard

Domain Name Wire - Mon, 05/07/2018 - 14:07

Namecheap gets boost from bulk transfer from Tucows.

ICANN has published the latest official .com data from January.

January is typically an up month for domain name registrations as the year kicks off, and you’ll see that in the data.

Namecheap lept up the top registrar chart to #6 thanks to a massive bulk transfer of domains from Tucows.

In January, these were the top 10 registrars in terms of new .com registrations:

1. GoDaddy.com* 974,020 (842,032 in December)
2. Tucows** 220,521 (167,285)
3. Endurance+ 175,515 (155,589)
4. HiChina Zhicheng Technology Ltd. 143,353 (125,286)
5. NameCheap Inc. 134,155 (117,990)
6. Xin Net Technology Corporation 127,808 (89,455)
7. Web.com++ 105,596 (88,067)
8. Google Inc. 96,020 (73,704)
9. NameSilo 60,280
10. West.cn 55,931

Here’s the current leaderboard of the top registrars in terms of total .com registrations as of the end of December 2017. There were approximately 135.5 million total .com domains registered as of the end of January:

1. GoDaddy* 47,161,126 (46,830,764 in December)
2. Tucows** 13,123,965 (15,578,732)
3. Endurance+ 7,927,353 (8,006,707)
4. Web.com++ 6,684,867 (6,666,853)
5. HiChina 5,129,880 (5,281,736)
6. NameCheap 3,960,861 (1,469,175)
7. 1&1 3,770,121 (3,780,143)
8. GMO 2,171,151 (2,196,043)
9. Xin Net Technology Corporation 1753431 (1,653,909)
10. Google 1,466,445 (1,391,333)

Many domain companies have multiple accreditations and I’ve tried to capture the largest ones. See the notes below and let me know if I’ve missed any large registrars.

* 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

© DomainNameWire.com 2018. 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. A strong month for .com; here are the winners & losers
  2. The Latest .Com Winners & Losers
  3. Namecheap leaps up .com chart as PDR falls
Categories: Domains

.App continues to explode, Coinbase registers nearly 100 .app domains

Domain Name Wire - Sun, 05/06/2018 - 16:19

Nearly 6,000 .apps are already in the zone.

Google’s .app top level domain name continues to prove itself a winner from a registrations standpoint.

The domain name entered day 5 of its early access program yesterday. This is the cheapest day of early access; the price remains at the current level for days 6 and 7.

Waiting until day 5 of early access meant missing out on a lot of domains. All of my day 5 pre-orders were snapped up in earlier days.

There are about 6,000 .app domain names in the zone now.

Cryptocurrency trading platform Coinbase was particularly active on day 3 of early access, registering nearly 100 domain names. These are mostly for defensive reasons, as you’ll be able to see when reviewing the list.

General availability opens on Tuesday. You can get domains for about $15-$20 starting then…but you’ll be competing against a lot of people.

activetradercoinbase.app advisorcoinbase.app advisorycoinbase.app assetmanagementcoinbase.app basecoincoinbase.app brokeragecoinbase.app brokercoinbase.app browercoinbase.app coinbaseactivetrader.app coinbaseadvisor.app coinbaseadvisorservices.app coinbaseadvisory.app coinbaseassetmanagement.app coinbasebasecoin.app coinbasebroker.app coinbasebrokerage.app coinbasebrower.app coinbasecommerce.app coinbaseconsumer.app coinbasecredit.app coinbasecustodian.app coinbasecustody.app coinbasedappbrowser.app coinbasedapphub.app coinbasedataservices.app coinbasederivatives.app coinbaseexchange.app coinbasefund.app coinbasefunds.app coinbasefutures.app coinbaseindexfund.app coinbaseindexservices.app coinbaseindividual.app coinbaseinstitutional.app coinbaseintelligentmanagement.app coinbaseinvest.app coinbaseinvestor.app coinbaselistings.app coinbasemarkets.app coinbasematching.app coinbasemerchant.app coinbasemining.app coinbaseoptions.app coinbasepayments.app coinbaseportfolios.app coinbaseprime.app coinbasepro.app coinbaserelay.app coinbasesmartwallet.app coinbasestablecoin.app coinbasestrongcoin.app coinbasetrader.app coinbasetradingservices.app coinbasewallet.app commercecoinbase.app creditcoinbase.app custodycoinbase.app dappbrowsercoinbase.app dapphubcoinbase.app dataservicescoinbase.app derivativescoinbase.app exchangecoinbase.app fundcoinbase.app futurescoinbase.app indexfundcoinbase.app indexservicescoinbase.app individualcoinbase.app institutionalcoinbase.app intelligentmanagementcoinbase.app investcoinbase.app investorcoinbase.app listingscoinbase.app marketscoinbase.app matchingcoinbase.app merchantcoinbase.app miningcoinbase.app optionscoinbase.app portfolioscoinbase.app primecoinbase.app procoinbase.app relaycoinbase.app stablecoincoinbase.app strongcoincoinbase.app tradercoinbase.app tradingservicescoinbase.app walletcoinbase.app

© DomainNameWire.com 2018. 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. .App domains are off to a strong start with brands
  2. ShoeMoney Sues Google Employee, Alleging Insider Advantages
  3. Google and Amazon.com backpedal on closed top level domain names
Categories: Domains

April’s top domain stories on Domain Name Wire

Domain Name Wire - Fri, 05/04/2018 - 15:36

Here’s a list of the top stories on Domain Name Wire last month, ranked by pageviews. Also, check out the list of podcasts from the past month — there were some great ones!

1. GoDaddy is closing an expired domain “loophole” – Backorders placed after auctions close will no longer win the domain name.

2. Whois GDPR carnage continues: Afilias to ditch almost all data in Whois on millions of domains – Afilias announced its Whois plans but backtracked shortly thereafter.

3. Vacation.rentals domain name sells for record $500,300. Oh, and it’s ranking on the first page of Google now for “Vacation Rentals”. Listen to the DNW podcast with the buyer.

4. U.S. government asks ICANN to investigate GoDaddy’s Whois policy – Don’t mind the elephant in the room.

5. Original France.com owner sues to recover domain from the country – Every publication in the world wrote about it after me, but I didn’t get any links back.

Podcasts

#183 – Sandeep Ramchandani, CEO of Radix (listen)

#182 – Meet Erik Bergman, who paid $900k for Great.com (listen)

#181 – Why Mike Kugler spent $500k on Vacation.Rentals (listen)

#180 – Panama, Sherpas and the Domain Market with Andrew Rosener (listen)

#179 – Whois and GDPR with Tim Chen (listen)

© DomainNameWire.com 2018. 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. Top 5 Domain Name Stories from August
  2. Heading to WHD next week? Here are some interesting sessions.
  3. Afilias gets contract for Puerto Rico’s .PR domain
Categories: Domains

Minds + Machines acquires .XXX top level domain operator ICM Registry

Domain Name Wire - Fri, 05/04/2018 - 12:47

New TLD portfolio company adds four domain names to its portfolio.

MMX (also known as Minds + Machines) announced today that it is acquiring ICM Registry, which operates the .xxx, .adult, .porn and .sex top level domain names.

MMX will pay $10.0 million cash plus 225,000,000 shares, which have a value today of $31.0 million. The shares are subject to lock-up periods and will not all be issued at once.

ICM Registry reported net sales of $7.27 million and net income of $3.5 million on its 2017 tax return.

.XXX is a sponsored top level domain name that was introduced in 2011. .Adult, .Porn and .Sex are part of the new top level domain program.

The acquisition concludes MMX’s strategic review, in which it was determining if it made sense to be acquired or to acquire other assets.

Here are some notable points about the deal:

  • ICM Registry founder Stuart Lawley will now be the biggest shareholder of MMX with about 15%.
  • Afilias was a large shareholder in ICM and will now become a notable shareholder of MMX. Keep in mind that MMX recently went with competitor Nominet as the backend for its TLD portfolio. Afilias will continue to be the backend provider for ICM’s four top level domains.
  • The deal will help MMX’s profitability. The company plans to begin a dividend plan within the next 18 months.

© DomainNameWire.com 2018. 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. .VIP hits 200k registrations, $3.2 million within 5 days
  2. .XXX worth more with .Sex in the bag?
  3. .VIP domain hits $5.5 million and 400,000 registrations
Categories: Domains

Domainers: What you need to do NOW to prepare for GDPR

Domain Name Wire - Thu, 05/03/2018 - 16:05

Take these steps to avoid headaches later.

The deadline to comply with the EU’s General Data Protection Regulation (GDPR) is quickly approaching. Domain name registrars are announcing changes and implementing them within the next few weeks. Here’s what you need to do as a domain investor to be prepared.

Transfer your domain names. If you have domain names that you might want to transfer to a new registrar within the next couple of months, do it now. If the personal information in Whois is obscured (as is likely), transferring many domains (including .com) will be hard.

We are likely to see a variety of approaches to handling transfers. The bottom line is that it might be difficult to move your domains between registrars post-GDPR, so do it now.

Add two-factor authentication and lock your domains. A lack of personal data in Whois is likely to increase domain theft and make it challenging to track down stolen domain names. Changes in how some registrars handle domain transfers could also increase the number of domain thefts.

Don’t take any chances. Make sure your security is up-to-date.

Download any Whois data you need. If you use a program like Watch My Domains, now is the time to pull in the latest Whois records about your domain names. This will be very difficult later this month.

Add context to stop an influx of UDRPs. Complainants currently investigate domain name owners before filing UDRPs (cybersquatting complaints). This allows them to determine if the owner might have a legitimate interest in the domain (e.g. a guy named Andrew owns a domain with Andrew in it) and potentially determine why they acquired the domain. This will be difficult without personal information in Whois.

You can do a couple of things to prepare. First, see if your registrar will let you opt-in to having your Whois info displayed. Second, consider changing the content of your parked pages to make sure they reflect a proper use of the domain.

On that note, be sure that people can contact you through your parked page. It will become difficult for them to reach you through your Whois record.

Get a subscription to historical Whois data. While GDPR is going to hurt DomainTools and DomainIQ in the long run, they will actually become more critical to your business for a least the short term.

When you buy a domain name, you’ll want to verify who owns it. If you can’t do that through the live Whois, looking at historical Whois information is going to be creditical.

© DomainNameWire.com 2018. 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. Whois GDPR carnage continues: Afilias to ditch almost all data in Whois on millions of domains
  2. GDPR will make domain name transfers more difficult
  3. Afilias hits pause button on Whois plans
Categories: Domains

Take a look at Google’s 11 sites built on .Google

Domain Name Wire - Thu, 05/03/2018 - 14:12

Google has developed 11 websites that use .Google domains.

Google is getting a lot of press this week thanks to its launch of .App, but .App is just one of dozens of new top level domains that Google controls.

During the 2012 round of top level domain name expansion, many companies applied for top level domains that match their brand names, e.g. .google. While applicants for these domains have been slow to build sites on them, the number of developed websites on dot-brand domains is steadily increasing.

Google has developed 11 of the 17 domains it has registered under the .Google top level domain name. Here’s a look at these 11 sites:

Google Design – Design.Google

A cooperative effort led by a group of designers, writers and developers at Google.

Grow with Google – Grow.Google

Educational resources for people to learn new skills.

Environment.Google

Houses information about sustainability at Google.

Google Domains – Domains.Google

Google’s fast-growing domain name registrar.

Google Registry – Registry.Google

Speaking of domain names, this is the home for Google Registry, which is about the launch .app.

Google AI – AI.Google

Information about Google’s artificial intelligence work.

Gradient Ventures – Gradient.google

Gradient Ventures is Google’s venture fund investing in AI companies.

The Keyword – Blog.Google

Google’s blog The Keyword about Google stuff.

Diversity – Diversity.Google

Information about diversity at Google.

Crisis Response – CrisisResponse.Google

Resources for first responders and local authorities on how Google can help them with emergencies.

Pride.Google

Information about LGBTQ+ issues.

© DomainNameWire.com 2018. 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. Google announces top level domain applications including .lol, .docs
  2. Google and Amazon compete on 21 new top level domain applications
  3. 4 new TLD applications withdrawn
Categories: Domains

End user domain name sales including a $60k .bio sale

Domain Name Wire - Wed, 05/02/2018 - 18:25

Take a look at these strong end user domain name sales.

Sedo had a strong week for end user domain name sales including a huge new TLD sale: My.bio for €49,900, which is about $60,000 USD.

The company also had a three-character .com end user sale, a couple of cryptocurrency related sales and more.

Here’s a list of end user sales I found:

(You can see previous lists like this here.)

YCoin.com $50,000 – The owner of YeahMobi, a mobile marketing program.

My.bio €49,900 – AllMyLinks LLC pulls all of your social media data into one account. A rebrand or a new service?

VRK.com €40,000 – This appears to be an end user sale of a three-letter domain. VRK is a tech products company.

SysAdmins.com $24,010 – It must be the same company that paid $55,000 for SysAdmin.com.

Styrosoft.com €16,000 – HKSDK, which bought SafetyShoes.com for $5,000. There’s no mention of this term on the company’s website so it’s probably a forthcoming name for one of its materials.

Stracon.com $13,000 – Stracon is a mining company in Peru.

ConsultSpace.com $8,900 – The law firm Nutter, McClennen & Fish, LLP bought this domain. It looks like it bought it for a company called Catalant, which is running a pilot project called ConsultSpace.

CyberX.com €5,000 – CyberX is a cryptocurrency trading platform.

Remix.ca $4,999 – Transit planning company Remix uses the domain name Remix.com. It is forwarding the .ca domain to the .com.

VitaminCFoundation.com $4,799 – The Vitamin C Foundation promotes and sells Vitamin C. It uses the matching .org domain for its web address.

Mast-Group.com €3,900 – Mast Group Ltd uses the domain MastGrp.com.

SmartMike.com $3,000 – Speech Processing Solutions GmbH in Vienna. How’s this for a domain: they own Speech.com.

OpenSouth.com $2,875 – OpenSouth helps IT vendors grow their business in Latin America.

SafetyManagement.com $2,400 – Baldwin Aviation is an aviation safety provider.

© DomainNameWire.com 2018. 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. What domain names Mozilla and others bought last week
  2. What domain names Goldman Sachs and others bought this week
  3. More end user domain name sales
Categories: Domains

Sex.app and Music.app among first .App domain names registered

Domain Name Wire - Wed, 05/02/2018 - 15:07

Customers pay stiff premiums to register domains early.

Google released the .app domain name to the general public yesterday–if they were willing to pay a hefty fee.

The so-called Early Access Period (EAP) for .app domain names started at 16:00Z yesterday. This Dutch auction starts with high registration fees that drop ever time.

Most registrars were asking for at least $10,000 to register a domain during the first day of EAP. That’s on top of the normal and premium registration fees.

Still, some people lined up to register domains.

A company called Axonic GmbH registered Sex.app, Music.app and Hotel.app. These domain names no doubt have an annual premium on top of the Early Access fee.

One letter domains were also popular. A.app, T.app, and D.app were snapped up by people in China.

Qurate, the new name of the company that owns QVC, registered Q.app. The company’s website is Qurate.com.

I’m a bit surprised that Overstock hasn’t registered O.app at the time of publication.

In addition to the early access fee, single letter .app domains have an annual registration fee of $2,000 at GoDaddy.

The big European company Bosch picked up Bike.app. Ringler Informatik AG registered Tax.app.

Some of the other day one registrations include Diet.app, Premiere.app, VPN.app and Well.app.

The second day of Early Access is quite a bit cheaper, with upcharges of about $2,500. Or you can wait until May 8 when domains are available for general registration at about $15-$25.

Just don’t try to register domains at Google Domains. The registrar is not participating in its own company’s Early Access Period.

© DomainNameWire.com 2018. 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

Consensus be damned: here’s how transfers will work at Tucows after GDPR

Domain Name Wire - Wed, 05/02/2018 - 13:48

Tucows will follow TechOps subcommittee recommendation for domain transfers as ICANN figures out what to do.

Here’s the thing about GDPR and domain name registrars/registries: if they wait for ICANN to figure out how to address GDPR, it will be too late to make the necessary changes to comply with the law. GDPR enforcement goes into effect in just 23 days.

One registrar that has been at the forefront of making changes to comply with GDPR (and has been stating them publicly) is Tucows (NASDAQ: TCX), which owns both Enom and OpenSRS. It is the second largest domain name registrar in the world behind GoDaddy.

The company recently posted about changes it will make to its domain name transfer process as a result of GDPR.

As I’ve written about before, if you can’t access a domain registrant’s email address, you can’t do a transfer under the current methodology mandated by ICANN.

Tucows is adopting the proposal put forth by the TechOps subcommittee of the Contracted Party House inside GNSO. It removes the gaining registrar’s Form of Authorization requirement.

Today, if you were to transfer a domain name to a Tucows registrar, you would provide the transfer authorization code to Tucows. Tucows would then send a Form of Authorization email to the current registrant listed in Whois to verify that they authorize the transfer.

Once this verification is complete, the losing registrar begins its process. This includes sending an email to the domain registrant to ask if they’re OK with the transfer. If they don’t respond within 5 days, the transfer is completed.

Tucows is eliminating the first Form of Authorization. Once you provide the authorization code, Tucows will skip directly to sending the transfer request to the losing registrar.

This creates a security risk because of how losing registrars are currently required by ICANN to respond to transfer requests. If they send an email to the registrant and the registrant doesn’t respond, the transfer goes through.

The TechOps committee has proposed a solution to this. It would allow the losing registrar to deny the transfer if the domain owner doesn’t affirmatively confirm the transfer.

How many registrars will start denying transfers like this starting May 25? It’s hard to tell. Big ones might, but small registrars are mostly unprepared for GDPR changes.

Of course, there are common sense security measures that domain owners can take to protect their domains as Whois and the domain transfer system is in flux.

Be sure to set transfer lock on your domains and add two-factor authentication to your domain name registrar account. Also, check to see if your registrar offers added transfer protection.

© DomainNameWire.com 2018. 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. Tucows changes domain name price structure
  2. Tucows expects $20 million EBITDA/year from “opportunistic” eNom acquisition
  3. Two Tucows execs are leaving
Categories: Domains

Tucows changes domain name price structure

Domain Name Wire - Tue, 05/01/2018 - 14:40

New pricing structure draws ire of some customers.

Tucows (NASDAQ:TCX), owner of the dominant reseller domain name platforms Enom and OpenSRS, is introducing new pricing on both of its platforms. The pricing is not uniform across the brands.

The pricing structure looks somewhat like an airline mileage club, requiring a minimum annual spend and number of new transactions in order to get the best pricing.

For example, the top Platinum Plus plan on Enom requires an annual domain spend of $100,000 and 1,000 new registrations or inbound transfers. That plan offers $9.00 .com domains and $12.00 .biz, .info, .net and .org domains.

The baseline Enom account will now pay $13.50 for .com domain names and $17.00 for .biz, .info, .net and .org.

Pricing for other TLDs at Enom hasn’t been adjusted yet but that will change in the future, the company stated on its site.

Despite being owned by the same company, OpenSRS has named its tiers differently and they come with slightly different prices.

Price changes like this are relatively easy for domain name investors — they can just move to another registrar. Many registrars offer .com domains for less than $9.00 to volume customers. I suspect many domain investors will leave Enom as a result of the price change.

But domain resellers are a bit more sticky. Moving to a new reseller platform is challenging and requires a technical investment. Plus, with both Enom and OpenSRS now owned by the same company, that really just leaves Endurance International Group’s ResellerClub as a big option. (GoDaddy also offers a reseller platform but it historically hasn’t been as flexible.) (See the comments for a list of other reseller registrars.)

ResellerClub has price tiers based solely on how much money is deposited, and it starts out very low. The baseline .com price is $9.99 and .coms are $8.89 with a $3,000 deposit.

I’m sure Tucows has done a careful calculation of how many customers it expects to lose from the price change and the resulting impact on its bottom line.

Here are some reactions on Twitter to the price change:

Bye bye @OpenSRS, @eNom and thus @Tucows . It was fun while it lasted; increasing all my pricing across the board is not something I can do to my customers. The move is going to be a pain, too.

Categories: Domains

Domain names are one bright spot for Endurance

Domain Name Wire - Tue, 05/01/2018 - 13:39

Revenue dips overall but domain business grows.

Endurance International Group (NASDAQ: EIGI) reported first quarter earnings before the bell this morning.

Revenue dropped year-over-year from $295.1 million in Q1 2017 to $291.4 million in Q1 of this year. Its subscriber base fell from 5.304 million to 5.011 million.

The rollup of hosting, domain and email marketing companies was hard hit in the web presence business. Its hosting companies, which include BlueHost and HostGator, lost 8% of their subscriber base over the past year. Revenue dropped from $164.0 million in Q1 2017 to $155.0 million in Q1 2018. Numbers were also down quarter-over-quarter.

Endurance has traditionally paid very large affiliate referral fees to keep its hosting business growing. It will be interesting to see if it changes this strategy.

While year-over-year email marketing revenue was up, it was down in Q1 compared to Q4 2017. Subscriber numbers also fell year-over-year, so the revenue bump came from higher revenue per subscriber.

The lone bright spot was the domain name business, which includes Domain.com, BuyDomains, ResellerClub and many smaller brands. Revenue ticked up $0.6 million in Q1 compared to Q1 last year, and $0.8 million compared to Q4 2017. Q1 is traditionally a strong quarter in the domain name business.

With all of its brands combined, Endurance is the third largest domain name registrar with about 12 million domains registered.

© DomainNameWire.com 2018. 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. One domain name stock is actually up today
  2. Endurance International acquires Constant Contact for $1.1 billion
  3. GoDaddy made the right move by booting domain name used for white supremacist site
Categories: Domains

Sandeep Ramchandani, CEO of Radix – DNW Podcast #183

Domain Name Wire - Mon, 04/30/2018 - 15:30

Radix CEO explains the company’s strategy.

This week we talk about new top level domain names with Sandeep Ramchandani, CEO of Radix. Radix is a portfolio new TLD company that focuses on generic extensions such as .online and .site. Sandeep reveals the company’s results so far, talks about how to value a top level namespace, discusses premium domains, and explains how he plans to grow his business. Also: Square buys Weebly, Verisign earnings, Cooperative Agreement, Google’s domain patent app, France.com, privacy, .web and more.

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

© DomainNameWire.com 2018. 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. Why Mike Kugler spent $500k on Vacation.Rentals – DNW Podcast #181
  2. How End User Domain Buyers Think – DNW Podcast #134
  3. The challenges of new TLDs with Tobias Sattler – DNW Podcast #177
Categories: Domains

Security vs. Privacy with GDPR

Domain Name Wire - Mon, 04/30/2018 - 13:34

There’s a real security issue with ditching public Whois. Do the benefits outweigh the costs?

I’ve written a lot about GDPR and how the domain registrar/registry ecosystem is responding to it. Privacy advocates are using this as an opportunity to push for privacy across the board, and I think this is a bad idea.

Security journalist Brian Krebs wrote an excellent Q&A on Friday explaining the trade-offs that come with no public Whois. He gives concrete examples of how he (and security researchers) have used Whois to track down bad guys. Many people reading this blog have also used Whois for the same purpose, such as tracking down stolen domains.

It’s the last two paragraphs of Kreb’s post that I think are most important:

If opponents of the current WHOIS system are being intellectually honest, they will make the following argument and stick to it: By restricting access to information currently available in the WHOIS system, whatever losses or negative consequences on security we may suffer as a result will be worth the cost in terms of added privacy. That’s an argument I can respect, if not agree with.

But for the most part that’s not the refrain I’m hearing. Instead, what this camp seems to be saying is if you’re not on board with the WHOIS changes that will be brought about by the GDPR, then there must be something wrong with you, and in any case here a bunch of thinly-sourced reasons why the coming changes might not be that bad.

It is frustrating to read advocacy pieces from groups that downplay the damage that hidden Whois will have. It’s true that there will be some good things that come from hiding registrant information. I’d argue the bad outweighs the good.

© DomainNameWire.com 2018. 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 investors risk being left out of Whois discussion
  2. Whois GDPR carnage continues: Afilias to ditch almost all data in Whois on millions of domains
  3. I just fixed Whois and GDPR
Categories: Domains

Coffee shop tries the old “renewed in bad faith” argument

Domain Name Wire - Sat, 04/28/2018 - 14:00

A domain name can’t be renewed in bad faith under UDRP.

A chain of coffee shops has tried (and failed) to use the “renewed in bad faith” argument in a cybersquatting dispute.

Revelry Partners, LLC, which runs coffee and wine bars by the name Ascension Coffee, filed a UDRP against AscensionCoffee.com.

The complainant claimed rights back to 2012, but the current owner registered the domain name in 2010.

Represented by Lisa Greenwald-Swire of Fish & Richardson, P.C., the coffee company made the argument that the domain owner renewed the domain name in bad faith last year.

Actually, she got a bit more creative than that. The National Arbitration Forum decision indicates that the argument was that the respondent reregistered the domain after allowing the domain registration to lapse.

The respondent didn’t reply to the assertions, so the panel reached out to GoDaddy to inquire what the circumstances were for the 2017 renewal. GoDaddy responded:

A review of ASCENSIONCOFFEE.COM shows that the domain was auto-renewed on December 8, 2017 per the settings in the account.

The domain expired on December 3. So the domain might have been renewed during the grace period, perhaps after updating a payment method. But no matter; this domain was continuously registered by the respondent since 2010.

The three-person panel found in favor of the respondent because the dates precluded a finding of bad faith registration.

© DomainNameWire.com 2018. 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. Porsche.me: Money Down the Drain
  2. EA loses domain dispute for SSX.com for upcoming SSX launch
  3. Nintendo loses domain dispute for WiiU.com domain name
Categories: Domains

Mining Available Domains via GoDaddy’s Watching List

Domain Name Wire - Fri, 04/27/2018 - 16:16

Alvin Brown shares a way to find hand-reg domains to register.

I shared 3 tips to Discover Expired Domains Available at Hand-Registration Fee at the end of last year.  As a follow up, I’m sharing another method to discover available domains using GoDaddy’ Watching feature.

It’s not really a “new” feature as some of you may recall a brief experiment by GoDaddy to display Watcher data on auction landing pages. Nevertheless, you may discover a profitable opportunity exists using Watching export data as a method to bulk search for available domains.

In addition to providing a daily list of GoDaddy expiring domain auctions for the general public to peruse, I “watch” quite a large number of GoDaddy expiring domains each day. Prior to providing a daily list for the general public, I never used the export feature for Watching domains.

But for the last two years and counting, I download this list of expiring domains daily as I strategize about which domains I’m going to actively bid and at what cost — via GoDaddy’s Watching download (see image below).

I also use it as a tool to test my ability to guess what a domain auction is likely to close at, adding an extra column next to the bid Price column with my own estimated auction close value. I then check the auction close prices from the previous and compare the value with the value I assigned to each of the domains I tested against. But I digress.

There are thousands of expiring and closeout domains contained in the daily Watching exported CSV file. Some of the domains have bids while a good percentage have 0 (zero) bids at the time of export.

Nevertheless, I move each daily exported Watching CSV files to a storage drive at the end of every week. It was this action of “digital” spring cleaning that uncovered over 2 years worth of exported daily expired domain data.

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.