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.

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

Podcast guest matching service reaches 10,000-user milestone

Domain Name Wire - Wed, 02/27/2019 - 16:54

Service connects podcasters with thousands of experts for interviews.

Podcasts are exploding. Spotify recently bought podcast producer Gimlet and Anchor for well over $200 million. A company called Himalaya launched with a $100 million investment and is snapping up podcasts.

PodcastGuests.com, a service I started about three years ago, is also growing quickly. This month it hit the 10,000-member milestone.

PodcastGuests.com is a platform that connects podcasters with guests for their shows.

Most podcasts follow a guest format in which the host interviews someone. I started the service because I was trying to broaden my reach as a podcaster and find new experts to interview. There was no central platform for doing this so I created it.

The service has now matched thousands of experts for guest appearances on podcasts. The standard service is free but experts can pay a small monthly fee to accelerate their guest bookings and have podcasters invite them on their show.

Interested in talking about domains, online marketing or your area of expertise on podcasts? Sign up with PodcastGuests.com today.

© 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. Want to get booked on podcasts? Sign up for PodcastGuests.com
Categories: Domains

Namecheap hits 200,000 domain milestone in Namecheap University program

Domain Name Wire - Wed, 02/27/2019 - 15:08

Domain registrar gives free .me domain name and online tools to students.

Domain name registrar Namecheap has hit a big milestone in its Namecheap University program: 200,000 free .Me domain names.

The program offers students and educators a free .me domain name and online tools for one year.

Namecheap launched the initiative in 2014. It is available to all students, teachers, administrators and educators with a .edu email address in North America, the UK and Australia.

The registrar says the program has been integrated into the curriculum of several high school and college computer science classes.

This seems like a smart program for Namecheap. Many technology companies (e.g. Apple, Microsoft) offer student discounts as a way to introduce young people to their products and make them lifelong customers.

© 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. Namecheap search “favorites” is cool. I’m still waiting for better new TLD search.
  2. The Latest .Com Winners & Losers
  3. Court orders Tucows to transfer 3.2 million domains to Namecheap
Categories: Domains

Google Search Console to offer “domain properties”

Domain Name Wire - Wed, 02/27/2019 - 14:22

New feature will combine different domain name variations.

Google is introducing a new concept called “domain properties” to its Google Seach Console.

Website owners use Google Search Console to get insight into their Google search traffic including keyword data, spidering and links. The search giant asks site owners to add all possible variations of their main URL to the service: http, https, www, non-www, m. (people are still doing that?) etc.

But this makes it hard to see all of your site’s data in one location. Enter domain properties, which combines all of these versions of the site into one for easy consumption. A domain property includes all protocols, subdomains, and paths.

Google will automatically create domain properties within the next few weeks for site owners with DNS verification set up.

© 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

Calm.com domain name is paying dividends

Domain Name Wire - Tue, 02/26/2019 - 20:57

Whatever the initial investment was, this domain name is a big asset to mindfulness company.

I took a ten-minute timeout this afternoon to meditate using the Calm app on my iPhone.

I’ve used a few meditation apps, but I recently subscribed to Calm given the traction it’s getting and the quality of the app.

The company also has a great domain name: Calm.com.

Even though Calm is primarily consumed as a phone app, you can bet the domain name is paying dividends. There are two reasons I think this domain is important.

First, Calm.com gives the app credibility. There are lots of meditation apps out there and quality varies. Having this great domain name shows that the company is serious. You need not worry about paying for an annual subscription; it’s not some copycat app.

Second, it’s great for advertising. The company is doing lots of audio advertising lately on podcasts. It can refer people to the Calm.com domain rather than tell them to just download the app. The company gives each podcast a special URL in the format calm.com/name to offer customers a 25% discount. (I bet it gets about the same revenue from its site with a 25% discount than it gets when someone pays full price through Apple’s app store.)

I’m not sure how much the company paid for Calm.com. An old video suggests it was at least high five figures, but it’s certainly worth much more than that. It might have been a lot to pay at the time when the company was small. Now it has raised over $25 million in outside capital and has a value of around $250 million raised over $100 million and has a billion dollar valuation.

© 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

Stolen domain name EQN.com returned to rightful owner

Domain Name Wire - Tue, 02/26/2019 - 16:17

Thief doesn’t show up to defend lawsuit.

Verisign has transferred the domain name EQN.com to its previous owner after a judge ordered the transfer.

Blackshore Properties, Inc. of San Marino, California acquired EQN.com in a NameJet auction in 2011 for $4,950. A thief subsequently stole the domain name from the company and transferred it to Chinese domain name registrar 22.cn in 2016.

Blackshore filed an in rem lawsuit in October last year in U.S. District Court in Virginia where .com registry Verisign is located. The thief (not surprisingly) didn’t show up to defend the domain, so the judge ordered Verisign to return the domain name.

The registrar for the domain switched from 22.cn to Enom around February 1, 2019. Enom doesn’t publish Whois records but the transfer likely indicates the domain has been returned to the legitimate owner.

David Weslow of Wiley Rein represented Blackshore Properties.

© 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. Private equity firm sues to recover JPE.com
  2. Lawsuit filed to recover stolen 4-number domain names
  3. Lawsuit filed to recover 6213.com, an allegedly stolen domain name
Categories: Domains

Domain marketplaces should build better search tools

Domain Name Wire - Tue, 02/26/2019 - 15:29

They are leaving money on the table with poor search features.

Sedo’s search leaves a lot to be desired.

Jamie Zoch tweeted a lot of domain aftermarket observations yesterday, and one of them struck a chord with me.

It really surprises me that large domain name aftermarket services mainly rely on 3rd party services to provide tools for finding domain names for their platforms. Most main services have very lack luster domain name search tools. Really basic, little data. #domains #aftermarket

— Jamie Zoch (@DotWeekly) February 25, 2019

There are great third-party tools such as ExpiredDomains.net for buying expired domains. I don’t know that the expired domain services need to recreate these but there could be some benefits.

The sites that do need to recreate tools like this are Sedo and Afternic. It’s very difficult to refine a search on these marketplaces. They might have a competitive reason to not expose their entire inventory to sites like ExpiredDomains.net…but this means they need to make it easier to search on their own sites.

Imagine getting an alert when someone adds a new name to Sedo that matches your criteria: length, number of TLDs the keyword is registered under, number of words, keywords, age, etc.

Even without alerts, wouldn’t it be great to search Sedo’s inventory this way? To be able to sort by your own quality metrics?

There are hidden gems listed for sale on both Sedo and Afternic but domain investors can’t find them.

This is low hanging fruit. The aftermarkets are leaving money on the table.

© 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. Sedo Improves Security of Escrow Process
  2. What domains Kanye West and others bought this week
  3. Boston: the center of the domain name aftermarket
Categories: Domains

Rick Schwartz – DNW Podcast #225

Domain Name Wire - Mon, 02/25/2019 - 16:31

The Domain King talks about his upcoming meetup and the state of domains.

The Domain King is back! Rick Schwartz talks about the domainer meetup he’s organizing in Asheville, North Carolina and why he feels it’s time for this type of meetup. We also talk about how Rick is investing in domains these days, brandable domains, domain estate planning and other domain topics.

Also: GoDaddy and Wix milestones, .Dev, ICANN and GoDaddy people changes, a Whois change and more.

This week’s sponsor: Name.com

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. 5 things Mike Cyger learned – DNW Podcast #196
  2. 48 domains, $114k sales on $3400 investment – DNW Podcast #211
  3. 2019 Predictions – DNW Podcast #218
Categories: Domains

Be careful about this expired domain name metric

Domain Name Wire - Mon, 02/25/2019 - 15:39

The number of TLDs a domain is registered under can be a misleading statistic.

Domain investors use lots of metrics when valuing domain names and figuring out which ones to buy. A common metric is how many other TLDs the second level domain is registered in.

For example, if you’re considering buying example.com, you’ll check how many other TLDs example is registered under.

This makes a lot of sense. Each of the non-.com domain owners is a potential buyer for the .com. The more TLDs the term is registered under the better.

But there are a couple of things you should investigate before putting blind faith in the topline number of domains registered.

First, the same person might be the registrant of more than one TLD. I see this happen a lot with expired domains. The .com, .net and .org are all registered but they’re all registered by the same person and are expiring at the same time. This means the .net and .org owners are not potential buyers.

Registries often offer discounts through registrars when a domain registrant is registering a .com domain, so the registrant adds these domains to their cart at little cost.

Second, the other TLDs might be registered by other domain investors. This is still a signal of value (if domain investors think the .net and .org have value, then the .com probably does) but these are not end-user prospects for the domain.

When filtering expired domains based on TLD registration numbers, keep these two things in mind. It’s not a big deal for low-dollar domains, but before you bid high on a domain, check out who actually owns the matching domains and how they are using them. It’s a great sign if they are using them for websites. It’s not such a great sign if they’re parked.

© 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

Cloudflare domain registrar expands, enables one-click DNSSEC

Domain Name Wire - Mon, 02/25/2019 - 14:11

Registrar is now open to all Cloudflare customers.

The Cloudflare domain name registrar is now available to all Cloudflare customers, the company announced on Friday.

The registrar launched a highly-secure registrar in 2016 and started expanding the registrar in September of last year. It was still only open to select customers until now.

The big hook for the registrar is that Cloudflare doesn’t charge a markup. Customers pay whatever Cloudflare pays the registry and any ICANN fees.

The company is touting another big feature: one-click Domain Name System Security Extensions (DNSSEC). 25% of domains using Cloudflare registrar now use DNSSEC.

Other registrars might follow suit in light of ICANN’s new push to get all domain names to enable DNSSEC.

© 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. Cloudflare announces no-markup domain name registrar
  2. Thousands download fake GoDaddy app in Google Play store
  3. Namecheap hits 10 million domains under management, Q&A with CEO Richard Kirkendall
Categories: Domains

ICANN names Cyrus Namazi VP of GDD

Domain Name Wire - Fri, 02/22/2019 - 14:48

Namazi to take over Akram Atallah’s role.

Cyrus Namazi. Photo from LinkedIn profile.

ICANN has appointed Cyrus Namazi as the Senior Vice President of the Global Domains Division (GDD). It’s a new title that replaces the President role that Akram Atallah held at ICANN before he left to be CEO of Donuts.

Namazi has been filling in as ICANN searched for a replacement, so now he’s officially the replacement (just with a different title). He will report to ICANN President and CEO Göran Marby.

The GDD was created in 2013 as ICANN geared up for new top level domain names.

Namazi joined ICANN in 2013. He has served as the Vice President of the group’s Domain Name Services & Industry Engagement activities.

© 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. ICANN hires new COO, moves Atallah
  2. GoDaddy Allows Transfers After Whois Changes
  3. What the new RAA means for YOU, the domain registrant
Categories: Domains

Uniregistry makes Whois opt-in

Domain Name Wire - Thu, 02/21/2019 - 23:07

New Cayman Islands law forces Uniregistry to change Whois policy.

Domain name registrar Uniregistry is making the publication of Whois data opt-in for registrants.

The move is in response to a new Cayman Islands Data Protection Law. Think of it as the Cayman Islands’ version of the EU’s General Data Protection Regulation.

Many of Uniregistry’s clients are domain name investors who want their information disclosed in Whois and they will be able to opt-in to doing this.

Technically, ICANN requires all registrars to provide a way for their customers to opt-in to have their information published in Whois but few have enabled this capability.

For domains with masked Whois records, Uniregistry will provide a form for people to contact the domain owner.

Most (but not all) other big domain name registrars began masking Whois data carte blanche after GDPR went into effect in May even though the law doesn’t cover non-EU citizen/resident data.

© 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 domain name winners and losers
  2. GoDaddy vs. Uniregistry – the Great Debate
  3. Frank Schilling unveils marketplace during keynote
Categories: Domains

Nelson Mandela Foundation wants Mandela.org domain name

Domain Name Wire - Thu, 02/21/2019 - 19:37

Organization files cybersquatting complaint under UDRP with World Intellectual Property Organization.

Nelson Mandela Foundation Trust has filed a cybersquatting complaint against the domain name Mandela.org.

The organization was established in 1999 when Nelson Mandela stepped down as President of South Africa. It was created for Mandela to do charitable work such as building schools, HIV/AIDS work and research. It now also handles the legacy of Mandela.

It uses the domain name NelsonMandela.org.

A Brazilian man owns Mandela.org. Prior to that, the domain name was owned by domain name investment company Internet REIT.

For a long time Mandela.org has resolved to a scarcely populated website that says it is under construction.

© 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. “Domainer” and “Domain Parking” hit CNN.com home page
  2. Cybersquatting complaint filed against MicroStrategy’s Glory.com domain
  3. The CloudInsure.com UDRP has a lot of open questions
Categories: Domains

End user domain name sales up to £30,000

Domain Name Wire - Thu, 02/21/2019 - 16:44

A German telecom company, tire distributor, and a Mexican paint brand bought domains last week.

This week’s top end user sale has an unknown buyer, but we will surely find out their identity soon. In addition to .com many ccTLDs made their way to the list: .de, .co, .ch and .it

Here are some end user sales from Sedo last week. You can view previous lists like this here.

DuoBank.com £30,000 – The Whois changed from someone in Korea to Scalar IT, a CDW company. I assume that’s outsourced IT for the buyer. When I search ‘duo bank’ I get a result for an investment firm that uses DuoBank.com.br.

Berel.com $8,200 – A Mexican paint brand and manufacturer.

Heuro.com €4,800 – Forwards to Heuro.ca, a Canadian resource and treatment program provider for those suffering from a brain injury.

Toniton.com $4,300 – Brand protection company Brimondo bought this domain name, ostensibly for a client.

CashOnly.com $4,000 – The domain name forwards to StaffOnly.com, which says “We help startups turn ideas into compelling products.”

Cannaflower.com $3,888 – Forwards to BerkshireCBD.com, a wholesale distributor of hemp flower plants.

MyBoardingHouse.de €3,750 – Forwards to MyBoardinghouse.net, a German apartment rental listing site.

Hiring.co $3,553 – Great keyword domain in development as a job listing site for the New York City area. Currently, they’re only showcasing security jobs but it’s hard to tell if that will be their sole focus.

3imedia.com $3,500 – Forwards to 3imedia.de/de/ – a German Telecom Firm that now owns the .Com of their domain.

Doc-Doc.com $3,300 – A Spanish language online portal and app of professional doctors available by chat, video consultations and home visits.

Kirchenaustritt.ch €2,990 – Forwards to mgqrmryww.cyon.link, which appears to be a template in development. It translates to roughly “leaving the church” in German.

Fritzreifen.com $2,500- Forwards to Fritzreifen.de, which has a literal translation of “Fritz tires” and is a German distributor of motorcycle and various types of commercial vehicle tires.

CorsoTrading.it €2,100 – MoSEO SrlS is an Italian web developer and SEO company. Its address is Corso Roselli, so this might be a domain for one of its clients or a project it is building.

© 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. Forward U.S. bought domain for $1,500
  2. These end users just bought domain names
  3. End user domain name sales up to $90,000
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.