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.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.

The Internet of Things – DNW Podcast #167

Domain Name Wire - Tue, 01/02/2018 - 16:30

What is the future of the Internet of Things and how will it impact our business?

In our first episode of 2018, Stacey Higginbotham of StaceyOnIoT.com joins me on the show to talk about the Internet of Things. Understand what it is, what industries it impacts, the easiest way to get started with the smart home, and how the internet of things might impact web usage and domain names.

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 2017. 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.

The post The Internet of Things – DNW Podcast #167 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. The Internet of Things – DNW Podcast #129
Categories: Domains

Phoenix Chinese Cultural Center developer guilty of reverse domain name hijacking

Domain Name Wire - Tue, 01/02/2018 - 16:13

Group tried to take down gripe site.

A developer that recently acquired the Chinese Cultural Center in Phoenix with plans to redevelop it has been found to have engaged in reverse domain name hijacking.

668 North, LLC, which is owned by private equity group True North, acquired the mostly empty mixed-user center last year with plans to redevelop it. Some of those plans irked the local Chinese community, which is concerned about changes the developer plans to make.

Many in the community raised a fuss about the changes and one group registered PhoenixChineseCulturalCenter.com as a way to raise awareness. 668 North filed a cybersquatting complaint against the domain name with National Arbitration Forum.

A National Arbitration Forum panelist ruled that 668 North failed to prove any of the three elements necessary to win its case. The panelist went further, noting that the developer “knew or should have known that it was unable to prove that Respondent lacks rights or legitimate interests in the disputed domain name and that Respondent registered and is using the domain name in bad faith.” For this reason, the panelist found that 668 North, LLC engaged in reverse domain name hijacking by filing the case.


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

The post Phoenix Chinese Cultural Center developer guilty of reverse domain name hijacking appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

#7 in 2017: Attack

Domain Name Wire - Mon, 01/01/2018 - 18:06

This is the fourth in a series covering the top stories on DNW in 2017, as ranked by pageviews.

Coming in at #7 of topics in 2017 is emoji domain names. Specifically, an ICANN security group’s warning against allowing emoji domain names was among the top stories view on DNW.

The warning came after domain investors piled into domain names that have emoji at the second level. Only a few country code top level domains allow registrations such as 🕶.ws and 😀.ws, but domain investors took advantage of low first-year registration prices to place their bets on these domains.

I personally think these domains are a bad investment. They aren’t universally accepted by different devices and they are only available in esoteric top level domains.

Now that cheap .ws registrations are coming up for renewal at higher prices, domain investors have to reconsider their bets. There’s a small amount of aftermarket activity for emoji domains but I haven’t seen end users coming in to buy and use these domains. That spells trouble.

Will the emoji domain fad be a thing of the past a year from now? Or will more top level domains embrace them as a way to generate more interest in their domains?


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

The post #7 in 2017: Attack 🏹 of the Emoji Domains appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. What do I think of Emoji domains? Not much.
  2. I still think emoji domains are a bad investment
  3. Here’s an example of why Emojis are bad for domain names
Categories: Domains

BrandBucket adds bitcoin support and pitches domains to crypto fans

Domain Name Wire - Fri, 12/29/2017 - 16:33

Brandable domain marketplace now accepts bitcoin as payment for domains.

Domain name marketplace BrandBucket is now accepting bitcoin as a form of payment.

To pay with bitcoin, customers checkout as usual and select “Pay With Bitcoin”. They are then given a wallet address and bitcoin conversion amount that’s good for ten minutes. (Given the wild fluctuations in bitcoin-to-dollar value, it makes sense to limit this time period.)

In a newsletter to clients yesterday, BrandBucket pitched domain names as a good investment with many of the characteristics of cryptocurrencies:

Domains: A Hedge Against Wild Fluctuations

Over the past ten years short, pronounceable domain names have increased in value as the number of available names for use in commerce is decreasing.

Historically, the value of domain names transacted in the aftermarket has increased 10% to 30% every year, with little or no downturns. This points to domain names being a stable investment option.

And similar to cryptocurrencies, domain names are easily transferred between parties, can be owned anonymously, and have clearly identifiable premium attributes: length, spelling, pronunciation, and proximity to commonly used words and phrases.

What do you think?


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

The post BrandBucket adds bitcoin support and pitches domains to crypto fans appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Wow: BTC.com domain name sells for $1.0 million to Bitcoin company
  2. BrandBucket sold 801 domain names for $2.4 million in 2015
  3. BrandBucket releases domain name sales data
Categories: Domains

#8 of 2017: Brands lukewarm to dot-brand domain names

Domain Name Wire - Fri, 12/29/2017 - 15:35

This is the third in a series covering the top stories on DNW in 2017, as ranked by pageviews.

The seventh most-viewed story on DNW in 2017 was about McDonald’s bailing on the new top level domain name program. The company had applied to operate .mcd and .mcdonalds. In the summer it informed ICANN that it no longer wished to operate these two domains.

McDonald’s joined a small but growing list of companies that applied for so-called .brand top level domains but later decided against running them. Other companies that withdrew in 2017 include HTC (.htc), Pampered Chef (.pamperedchef), Richemont Group (.montblanc, .chloe), The Boots Company (.boots) and Orient Express (.orientexpress). Others withdrew in 2016.

#8 in 2017: Brands luckwarm to dot-brand domain namesClick To Tweet

There are two things to consider about these companies’ moves.

First, it’s not surprising that some .brand owners have had second thoughts about new TLDs given the low overall demand for domains registered new top level domains. Like many generic new TLD applicants, some of these companies expected new TLDs to make a bigger splash. They applied thinking they’d be a bigger deal than they ended up being, so it makes sense to re-evaluate the costs of running the domains. Others applied on the mistaken belief that defensive top level domain registrations were necessary.

Second, the withdrawn applications represent just a small percentage of the total .brand applications submitted.

Elsewhere, use of .brand domain names is expanding. Top level domain registry Neustar switched its website to .Neustar and companies like Amazon are promoting sites such as BuildOn.aws.

Another positive sign: companies that didn’t apply for .brands in the first round are asking ICANN to open another round so they can apply. That’s a signal of demand, at least from an applicant perspective.

Like all new domains, .brand top level domain names will only grow in awareness. Whether it makes sense for companies to make the expense required to run them remains to be seen.


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

The post #8 of 2017: Brands lukewarm to dot-brand domain names appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Google and Amazon compete on 21 new top level domain applications
  2. Final new TLD objection tally: Donuts 55, Amazon 24, Google 22
  3. The .ART Premium Name Model: Four Months In
Categories: Domains

#9 of 2017: GoDaddy gobbles up more domain name portfolios

Domain Name Wire - Thu, 12/28/2017 - 18:39

This is the second in a series covering the top stories on DNW in 2017, as ranked by pageviews.

In April 2015 GoDaddy made waves when it acquired Marchex’s domain name portfolio for $28 million. The registrar, which helps domain investors buy and sell domain names, was suddenly a domain investor itself. And it was about to become an even bigger one.

The company has purchased many domain portfolios since then, which suggests that being a domain investor is proving to be profitable for the registrar.

GoDaddy’s acquisition activity heated up again this fall. The company paid $50 million to buy two large portfolios: Donuts sold a portfolio of about 200,000 domain names it inherited from Rightside, and a portfolio linked to Kevin Ham that contained roughly 100,000 domains was also gobbled up.

The company followed up with a small purchase of select name from Tucows’ YummyNames portfolio.

GoDaddy typically buys domain names from portfolio holders who have low turnover and high sales prices. The company then attaches lower fixed prices to the domains and adds them to its AfternicDLS system to increase deal flow.


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

The post #9 of 2017: GoDaddy gobbles up more domain name portfolios appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. GoDaddy has a $12,500 price tag for Donuts’ Early Access Program
  2. GoDaddy auction data provide early indication of new TLD demand and values
  3. GoDaddy sold $1.4 million of domain names from Marchex portfolio last quarter
Categories: Domains

Michael Berkens sues Twitter over hacked account

Domain Name Wire - Thu, 12/28/2017 - 14:18

Popular domain name blogger still doesn’t have control of his account five days after hacking.

Michael Berkens and his company Worldwide Media, Inc. have sued Twitter (pdf) and the unknown person who has control over his @thedomains handle.

On December 22 someone gained access to the @thedomains account and started tweeting. Some of the tweets taunted followers and Berkens about the account being hacked.

Despite numerous reports to Twitter, Berkens still does not have control of the account.

In the lawsuit, Berkens states that he and his company have paid twitter “substantial amounts of money to use and promote the Account, and otherwise have devoted extensive resources and time to using and promoting the Account.”

Whoever hacked the account seems to have a good read on Berkens, as many of the retweets and comments allude to Berkens’ interests.

I suspect the primary goal of the lawsuit is to recover the account, but it also asks for damages and for Twitter to remind its users about available security tools like two-factor authentication, which was only made available this year.

Speaking of which, go turn on two-factor authentication for your account.


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

The post Michael Berkens sues Twitter over hacked account appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Direct visits lead to spectacular domain prices in China

Domain Name Wire - Wed, 12/27/2017 - 17:42

Kassey Lee examines direct navigation in China.

China has stunned the world in recent years. It’s the place where you can expect spectacular prices of domains sold, such as Le.com for $10m, JD.com for $5m, and Vivo.com for $2.1m. Why? One reason may come from consumer behavior: people in China like to directly visit a website for online shopping.

Search engine Baidu publishes visitor data of more than 1.5 million websites it monitors every month. I have aggregated the data to give you a yearly view of the visit patterns.

YearDirect VisitReferralSearch EngineDirectorySocial Media 201239.36%27.74%27.34%4.88%0.68% 201334.79%32.96%24.93%5.72%1.61% 201439.83%33.79%19.86%4.59%1.93% 201540.83%29.96%23.39%3.00%2.82% 201641.95% 29.38%25.66%2.00%1.01%

Visitors to a website can come from one of five sources: direct visit (explicitly specifying a domain in the browser), referral (arriving via a link on another website), search engine (entering a phrase to search), directory (listing of websites by category), or social media (such as WeChat).

By far, direct visits bring the most number of visitors to a website, and the trend is up. This suggests many consumers remember and therefore specify a domain when they want to do online shopping. In view of this consumer behavior, it’s natural that major brands want to use domains that are easy for consumers to remember.

A domain that is easy to remember is a domain which requires the least effort to process in the mind of a consumer. Specifically, this means two characteristics: (1) matching the brand, (2) mainstream extensions (.com and, to a lesser degree, .cn). This is because the consumer already remembers the brand name and most Chinese consumers are familiar with the mainstream extensions.

Some brands in China have discovered this not widely known fact and accordingly have invested heavily in acquiring their brand-matching .com domains. They even try to enhance consumer memory by displaying their domains everywhere.

A good example is Jing Dong (京东), the 3rd largest internet firm in the world by sales. The company used to operate on 360buy.com, a cheap domain which did not match the brand name. In 2012, the company surprised corporate China with the $5 million acquisition of JD.com. It also secured JingDong.com which automatically transfers visitors to JD.com. The result was immediate, reportedly saving the company $20 million a year in search engine advertising.

To maximize the power of the domain JD.com, Jing Dong displays it prominently everywhere: company logo, product packages, store signs, delivery trucks, public walls, bus ads, and many more. Whenever you see the Jing Dong brand, you see the name JD.com which, as a result, has been hard-wired into the brains of millions of Chinese consumers.

Look at the numbers again. The domain JD.com cost $5m, saves the company $20m a year and generated $38 billion dollars in sales last year. Jing Dong spent only 0.013% of its annual sales to acquire this single store in the virtual world of the internet. For this reason, Chinese brands are willing to spend big on brand-matching .com names.

This trend has just begun. The Top 100 Internet Companies or the 2016 Top 300 New Internet Companies in China show many companies are yet to acquire their brand matching .com names. They probably do not realize, as Jing Dong has experienced, the power of direct visit and relevant domains. But, they will. Therefore, the Chinese domain market will continue to amaze the world with spectacular prices in domains sold.

Finally, please note that I use the term “domains” instead of “domain names” in order to align it closer with “stocks” and “bonds” in investment.


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

The post Direct visits lead to spectacular domain prices in China appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

#10 of 2017: Daily Stormer and the role of domain name registrars

Domain Name Wire - Wed, 12/27/2017 - 15:02

This is the first of ten posts counting down the top 10 stories on Domain Name Wire in 2017, as ranked by pageviews.

What is the role of a domain name registrar when it comes to the content of a website? The common answer was tested in 2017.

Traditionally, domain name registrars have tried to stay out of the content policing business. They argue that domain names are merely pointers and that content issues should be handled by web hosting companies.

That’s the initial stand that GoDaddy took with DailyStormer.com, a domain name registered at the registrar that pointed to a racist website hosted elsewhere. The registrar continued to be the registrar for the domain name despite frequent criticism.

#10 in 2017: How DailyStormer.com got domain registrars to change protocolClick To Tweet

That all changed after the White Nationalist rally in Virginia in which a man ran over and killed a counter-protester. Daily Stormer posted a hateful article about the victim. GoDaddy decided enough was enough and said that it was booting the domain name because it violated its policy of not inciting violence.

GoDaddy kicked the problem to another registrar by telling the DailyStormer.com owner that he needed to move his domain elsewhere.

That elsewhere was Google. Why the owner chose Google’s registrar is beyond me.

Google went a big step further than GoDaddy. Instead of telling the domain owner to move, it put the domain in ClientHold status, effectively rendering the domain useless. That’s where it stands today.

The site then moved to some alternative top level domains and even the dark web.

While registrars would like to deflect responsibility to hosts, the mood following the violent Virginia rally made it hard for registrars to ignore. Many free speech groups blasted the registrars for their decisions, and I suspect registrars will reconsider their stances with hindsight when similar cases appear in the future.


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

The post #10 of 2017: Daily Stormer and the role of domain name registrars appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. GoDaddy Allows Transfers After Whois Changes
  2. ICANN officially kills Google’s plan for dotless Search top level domain name
  3. Google and Vint Cerf explain the NTIA transition (video)
Categories: Domains

2 more RDNH: Airtango and Laboratorios del Dr. Esteve

Domain Name Wire - Tue, 12/26/2017 - 18:33

Add two more companies to the reverse domain name hijackers list.

There have been so many reverse domain name hijacking cases over the past week that it’s time to consolidate more than one decision in the same post.

Earlier today I wrote about a reverse domain name hijacking case brought by French clothing company Modz. Here are two more decisions, both published by World Intellectual Property Organization today.

Airtango AG tries to reverse domain name hijack AirTango.com

Live streaming company Airtango AG was found guilty of reverse domain name hijacking for AirTango.com despite the domain owner not responding to the complaint.

The company sent two emails to the privacy email for Airtango.com demanding transfer of the domain name. The first message said:

airtango is aiming to play a major role in the fastest growing digital market, world-wide LIVE / real time video content and in this light offers a platform that manages, organizes and delivers video content through the Internet or via exclusive airtango Live-Points. For further details, please refer to www.airtango.de. Since airtango wishes to even stronger promote and support its global expansion, airtango is in need of the international Internet presence airtango.com.

It filed the UDRP after not receiving a response from the owner.

The problem for Airtango was that the domain was registered well before it existed. (Looking at historical Whois records, it’s quite possible the domain changed ownership since the complainant existed. It seems that the complainant’s legal counsel didn’t look at historical Whois. For the purposes of the case, however, the complainant believed the domain was registered before the company existed.)

Airtango AG, represented by Dr. Meyer-Dulheuer & Partners LLP, Germany, seemed top misquote prior UDRP decisions to imply that the registration date didn’t matter. It lifted a statement from a prior UDRP in which the panel said the registration date didn’t matter, but that referred to the first element of UDRP (whether the domain is confusingly similar to the complainant’s trademark) in which date indeed doesn’t matter.

Laboratorios del Dr. Esteve, S.A. tries to reverse domain name hijacking AdSalutem.com

Spanish pharmaceutical company Laboratorios del Dr. Esteve, S.A. was found guilty of reverse domain name hijacking for its attempt to get the domain name AdSalutem.com.

The domain name is owned by a German company that sells a diet program. It says that “ad salutem” is a form of Latin greeting which means “good health to all”.

The panel found that the complainant, represented by Oficina Ponti, filed the case in bad faith:

The Complainant is professionally represented in this matter and, in the opinion of the Panel, knew or ought to have known that it had no reasonable chance of prevailing in this proceeding for the reasons set out above, including in particular the absence of any evidence of its own use of the term “ad salutem” in commerce. Further, the Panel notes the Complainant’s prior attempt to purchase the disputed domain name from the Respondent, at which time no suggestion of any impropriety on the part of the Respondent was made. The Respondent has also adduced sufficient evidence for the Panel to conclude on balance that the Complainant’s primary motivation in bringing this proceeding was to obtain the disputed domain name for commercial reasons of its own. The Panel finds in all the circumstances that the Complaint was brought in bad faith and constitutes an abuse of the administrative proceeding.


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

The post 2 more RDNH: Airtango and Laboratorios del Dr. Esteve appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Egton loses Patient.com UDRP, but it should have been reverse domain name hijacking
  2. Frank Schilling gets RDNH win on 3 letter domain name
  3. Zak Muscovitch gets reverse domain name hijacking win
Categories: Domains

French clothing company Modz guilty of reverse domain name hijacking

Domain Name Wire - Tue, 12/26/2017 - 18:06

Company left key detail out of cybersquatting complaint against Modz.com.

The owner of Modz.fr tried to get Modz.com through a UDRP.

French clothing company Modz, which uses the domain name Modz.fr, has been found to have engaged in reverse domain name hijacking in its cybersquatting complaint against Modz.com.

The owner of Modz.com registered it for its video gaming connotation and operated a website using the domain name for a year or two after acquiring it in 2008. Now the domain is parked with gaming ads.

That shows rights or legitimate interests in the domain name. It also shows that it wasn’t registered and used in bad faith.

A three person World Intellectual Property Organization panel went a step further, deciding that Modz filed its case in bad faith. The company disclosed a 2016 overture it made to buy the domain name but failed to disclose a $4,000 offer it made in 2009. At that time the complainant did not mention a trademark and the domain owner explained why he acquired the domain name.

The panel considered this a case of “Plan B” reverse domain name hijacking in which a company files a UDRP after failing to acquire a domain name via commercial means.

The domain owner was represented by John Berryhill. The reverse domain name hijacker was represented by Marion le Marchard Avocat.


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

The post French clothing company Modz guilty of reverse domain name hijacking appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. $50,000 penalty for filing a frivolous UDRP!
  2. Zak Muscovitch gets reverse domain name hijacking win
  3. Canadian firm Obero tries to Reverse Domain Name Hijack domain name
Categories: Domains

2018 DNW Predictions Episode – DNW Podcast #166

Domain Name Wire - Tue, 12/26/2017 - 16:30

Pull our your crystal ball.

It’s time for the annual DNW predictions episode! You’ll hear from 17 people across the domain name industry about what they predict in the domain name space in 2018. You’ll hear from: Brian Cute (PIR/.org), Christa Taylor (dot TBA), Michele Neylon (Blacknight), Shane Cultra (DSAD.com), Lori Anne Wardi (Neustar), Giuseppe Graziano (GGRG.com), Zak Muscovitch (Muscovitch Law Firm), Jochen Kieler (BrandIT), Paul Nicks (GoDaddy), Braden Pollock (Legal Brand Marketing), Matt Overman (Donuts), Kamila Sekiewicz (Internet Commerce Association), Mike Carson (Park.io), Sandeep Ramchandani (Radix), Roland LaPlante (Afilias), Michele Van Tilborg (.Club) and Tobias Flaitz (Sedo). Enjoy and Happy New Year!

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 2017. 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.

The post 2018 DNW Predictions Episode – DNW Podcast #166 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Paul Nicks of GoDaddy – DNW Podcast #160
  2. Reviewing this year’s predictions – DNW Podcast #161
  3. Building web businesses with Peter Askew – DNW Podcast #163
Categories: Domains

Thousands download fake GoDaddy app in Google Play store

Domain Name Wire - Tue, 12/26/2017 - 15:10

GoDaddy is suing unknown creator of fake GoDaddy app.

A fake GoDaddy app was available in the Google Play store earlier this month and GoDaddy believes that thousands of people downloaded the app.

The app, called GoDaddy Mobile, was available in the store from December 12 to December 15. GoDaddy informed Google of the app on December 15 and it was quickly removed.

This is the listing in the store for the fake app:

The description stated:

“[w]e are happy to introduce cPanel App for you webmasters powered by GoDaddy. You can also access your Account Products using the ‘My Account’ section from the slider!”

People who downloaded the app left negative reviews for it and didn’t realize it was not a real GoDaddy app.

GoDaddy has filed a lawsuit (pdf) in Federal District Court in Arizona to try to uncover the identity of the app’s creator. The lawsuit seeks damages for trademark infringement, false designation of origin, false advertising and registered trademark counterfeiting.


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

The post Thousands download fake GoDaddy app in Google Play store appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. How GoDaddy “uses this one simple trick” to get 56,000 more registration years per month
  2. It’s official: GoDaddy owns Host Europe Group
  3. Godaddy releases domain name appraisal tool to the public
Categories: Domains

13 end user domain name sales up to €50,000

Domain Name Wire - Fri, 12/22/2017 - 15:34

A social app, video job search platform and florist bought domain names last week.

Sedo had a couple of big domain name sales last week including Hornet.com and Goldi.com. We don’t know for sure yet if Hornet.com was an end user purchase, but Goldi was. Details about Goldi.com and other end user sales at Sedo this past week are below:

(You can view previous lists like this here.)

Goldi.com €50,000 – Video job search platform Goldi bought this domain and forwards it to Goldi.com.

Jokerstar.com $13,455 – Kling Automaten GmbH sells gambling machines. Its logo looks like a joker and a star.

Intana.com $8,000 – Intana & Co. is a jewelry seller.

Bookstore.ca $7,000 – Second Bind is a second-hand textbook store.

Friendo.com $5,657 – Friendo is a social app that lets you send questions about yourself to friends to see how well they know you.

Bestware.com €5,000 – tronic5 Holding GmbH is a holding company. Its companies all seem to sell computers and other tech toys. Bestware is a reasonable name for a new brand.

Supreme.co.uk £4,000 – Supreme Imports bought a nice upgrade to Supreme-Imports.co.uk.

EssexFlorist.com $3,500 – Essex Florist & Greenhouses bought the .com to match its .net domain name.

Cylance.uk £2,999 – Computer security company Cylance Ireland Limited.

Smart-spas.com €2,999 – Whirlpools World Outlet GmbH in Germany.

WhatAWoman.com $2,888 – Braya is a marketing firm that does event management, PR and more. This domain name might be for a client.

CampAmerica.net $2,800 – American Institute for Foreign Study is a study abroad company. One of its programs is called Camp America. It doesn’t own CampAmerica.com.

Tex.co €2,500 – The buyer runs a site at TeXblog.net about TeX, a typesetting program.


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

The post 13 end user domain name sales up to €50,000 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. End user domain name purchases including State Street and Live Person
  2. 36 End User Domain Name Purchases
  3. What domain names Time Inc. and others bought at the end of the year
Categories: Domains

Another hour, another reverse domain name hijacking case

Domain Name Wire - Thu, 12/21/2017 - 19:16

Inspectorate America Corporation guilty of reverse domain name hijacking.

Tired of reading stories about reverse domain name hijacking? Well, I’m tired of writing them. Yet, here’s another.

Inspectorate America Corporation has been found to have engaged in reverse domain name hijacking over the domain name loams.com. The company has a software program called LOAMS, which stands for Lube Oil Analysis Management System.

The domain owner, Netcorp, said it registered the domain name because it’s a typo of “loans”. Netcorp owns several other typos of dictionary words.

(Side note: when you search google for Inspectorate America Corporation loams it says “Showing results for Inspectorate America Corporation loans“.)

The complainant reached out to the domain owner before filing its UDRP. Domain attorney John Berryhill responded with a very persuasive argument that the complainant was wrong and should drop the issue. It decided to file a UDRP anyway.

Berryhill represented Netcorp in the response. He didn’t ask for a reverse domain name hijacking finding, but the World Intellectual Property Organization panel unanimously agreed that it was warranted:

This Complaint was doomed before it was filed. Complainant, who was represented by counsel, should have known this. The Domain Name was registered back in 2003, and the content of the website to which it resolved bore no relationship to Complainant’s goods and services, or those of a competitor of Complainant, or to anything even remotely close to such goods and services.

More importantly, in pre-dispute correspondence, Respondent plausibly denied having had any knowledge or awareness of Complainant’s mark, spelled out its motivation for registering the Domain Name, confirmed that it had been using the Domain Name for years in pursuit of its legitimate business purpose, and supplied authority to Complainant and its counsel for the proposition that Respondent’s activities were not in bad faith. Nonetheless, Complainant could not take “No” for an answer, and chose to launch its foredoomed Complaint.


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

The post Another hour, another reverse domain name hijacking case appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Egton loses Patient.com UDRP, but it should have been reverse domain name hijacking
  2. Frank Schilling gets RDNH win on 3 letter domain name
  3. Zak Muscovitch gets reverse domain name hijacking win
Categories: Domains

Stobbs IP gets two reverse domain name hijacking losses in the same day

Domain Name Wire - Thu, 12/21/2017 - 17:01

One firm, two RDNHs in the same day.

Over the past twenty-four hours, I’ve written about two reverse domain name hijacking cases at World Intellectual Property Organization.

A reverse domain name hijacking finding means a case was filed in bad faith as an abuse of the Uniform Domain Name Dispute Resolution Policy (UDRP).

Both of these cases were filed with the help of Stobbs IP, a UK intellectual property law firm. Both the decisions were handed down on December 11. I can’t recall any law firm getting hit with reverse domain name hijacking with two different clients in the same day.

In these two cases, Stobbs IP represented Informa Business Information for PinkSheet.com and Virgin Enterprises for VirginLiving.com.

Stobbs IP also represented University of Cambridge in a 2015 case it lost against the domain name Cambridge.com. Although that panel declined to find reverse domain name hijacking, it said the filing “seriously misdescribed” the contents of the Cambridge.com website.

So, in addition to helping a client file a case in which a panel said it “seriously misdescribed” a key element of its case, panelists have now written these comments about cases it filed:

“The Complainant attempted to mislead the Panel on several occasions by presenting information as fact, which at closer examination was misleading or untrue.”

“The Complainant was legally represented and should have known that it would be unable to satisfy all the elements required under paragraph 4(a) of the Policy.”

“…the Complainant was likely aware that it did not have a legitimate case against the Respondent, and filed the Complaint with the primary intent of obtaining the transfer of the disputed domain name in bad faith against no consideration.”

“With the benefit of experienced intellectual property advisors, the Complainant should have been aware that, in these circumstances, its Complaint could not succeed.”

Ouch.


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

The post Stobbs IP gets two reverse domain name hijacking losses in the same day appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

HUGE win: HugeDomains gets reverse domain name hijacking win against Virgin Enterprises

Domain Name Wire - Thu, 12/21/2017 - 16:32

Virgin takes the low road and is nailed for reverse domain name hijacking.

HugeDomains has successfully defended its domain name VirginLiving.com against an attack by Virgin Enterprises, and Virgin has been found guilty of reverse domain name hijacking in the case.

Virgin failed to prove any of the three elements required to win a cybersquatting case under UDRP.

HugeDomains.com successfully argued that Virgin doesn’t have complete control over every word attached to Virgin. HugeDomains owns 750 domain names that begin with the word “virgin” and over 1,600 domain names that end with the word “living”, all of them being combinations of two dictionary terms.

Virgin Enterprises recently filed an intent-to-use trademark application for Virgin Living and then discovered that HugeDomains owns the domain name and has it listed for sale for $4,795.

Rather than buying the generic domain name, Virgin filed a UDRP with misleading evidence and stated that “no one party can legitimately own over 3.5 million domains. The Respondent is a cybersquatter on an industrial scale.”

The panel found that, indeed, a company can legitimately own 3.5 million domain names. It also found that Virgin submitted misleading evidence about HugeDomain’s portfolio of domains that being with “virgin”:

In this case, the Panel considers that the Complainant must have realized that the disputed domain name was one out of many combinations of descriptive words which the Respondent in its capacity of a domainer registered. The Complainant cannot monopolize all combinations of dictionary words with the term “virgin”, for which reason the Complainant filed the Application, which is identical to the disputed domain name, shortly before submitting the Complaint. The Complainant attempted to mislead the Panel on several occasions by presenting information as fact, which at closer examination was misleading or untrue. For instance, the Panel found the Complainant’s allegation that the Respondent has in actual fact registered over 1,000 domain names containing the Complainant’s VIRGIN brand which would constitute evidence of a pattern of bad faith, to be untrue as the list submitted by the Complainant in support of the allegation consisted mainly of combinations of the term “Virginia” with another dictionary word, while the domain names which include the term “virgin” seem generally to use the term in the dictionary sense of a person who has never had sexual intercourse. Also, the Complainant’s claim that “no one party can legitimately own over 3.5 million domains. The Respondent is a cybersquatter on an industrial scale” was unsupported and as such made an unjust connection between the ownership of domain names as such and cybersquatting, which the Complainant could not show.

The lack of convincing evidence and the Complainant’s failure to fully address the requirements under paragraph 4(a) of the Policy demonstrate that the Complainant was likely aware that it did not have a legitimate case against the Respondent, and filed the Complaint with the primary intent of obtaining the transfer of the disputed domain name in bad faith against no consideration. This is supported by the fact that the Complainant only filed the Application with the intention to use, but not after having it used and without any proper explanation why the Complainant would need this mark just before the Complainant filed the Complaint. The Panel is of the opinion that the Complainant did this in a misguided attempt to bolster or lend legitimacy to the Complaint. The Complainant was legally represented and should have known that it would be unable to satisfy all the elements required under paragraph 4(a) of the Policy


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

The post HUGE win: HugeDomains gets reverse domain name hijacking win against Virgin Enterprises appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Frank Schilling gets RDNH win on 3 letter domain name
  2. comScore gets Reverse Domain Name Hijacking win
  3. Telepathy gets another Reverse Domain Name Hijacking win
Categories: Domains

Court orders Tucows to transfer 3.2 million domains to Namecheap

Domain Name Wire - Thu, 12/21/2017 - 16:14

With deadline looming, injunction forces Tucows to transfer domains.

A Washington State court has ordered Tucows to transfer 3.2 million .com and .net domain names to Namecheap, and an appeals court has denied (pdf) Tucow’s motion for an emergency stay.

The dispute stems from Namecheap’s termination of its reseller relationship with Enom, which Tucows (NASDAQ: TCX) acquired in January. Namecheap was a long time reseller on Enom’s platform but its exclusivity deal with Enom for .com and .net domain name registrations ended last year. This year, Namecheap requested Tucows to transfer domain names on Enom’s platform to Namecheap’s registrar credentials.

Namecheap is using its own registrar credentials for new registrations and wants to consolidate all registrations under its credentials. Between the domains registered directly with Namecheap and those on Enom’s platform, Namecheap has 8.5 million domains under management.

Namecheap’s contract with Enom allows for it to request the transfer of the domain names, but Tucows balked at Namecheap’s request this year to do the transfer through a “Bulk Transfer After Partial Portfolio Acquisition”, or BTAPPA. Namecheap already has approval from .com/.net registry Verisign to do a BTAPPA transfer of the 3.2 million .com and .net domains.

The alternative to BTAPPA is to require each of Namecheap’s customers to do individual domain transfers. This would be troublesome because these customers don’t understand that their domains are actually registered on the Enom platform. It would also require EPP codes and a one-year renewal upon transfer.

After Tucows resisted the BTAPPA transfer, Namecheap sued Enom and Tucows in Federal District Court in Seattle at the end of August. It subsequently dropped the case because it was concerned it wouldn’t get jurisdiction. It refiled the case in Washington State Superior Court.

Namecheap believes the deadline for doing the transfer is the end of 2017, so it asked the court for an injunction forcing Tucows to comply in a timely manner. The court agreed and demanded that Tucows comply with the transfer.

Tucows asked the court for a stay and was denied. It subsequently asked the Washington State Court of Appeals to stay the order.

The appeals court, considering expert testimony from former ICANN staffer Tina Dam who said the BTAPPA was appropriate for this circumstance, determined that Namecheap was likely to prevail in the lawsuit and an injunction was appropriate. It also considered that Enom previously did a BTAPPA transfer of 400,000 .biz domain names to Namecheap when Enom was still owned by Rightside. It denied Tucows’ motion to stay.

Namecheap represents a large portion of Enom’s revenue, historically accounting for about 25% of Enom’s domains under management. While margins on the registrations slim, Enom gets to keep 100% of expired domain revenue and all parking revenue during registrations and during the expiration cycle.

This gives Tucows an incentive to delay the transfer as long as possible. At the same time, it risks bad will with reseller customers who will now question how they will be able to transfer off the platform should they want to in the future.


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

The post Court orders Tucows to transfer 3.2 million domains to Namecheap appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Tucows acquires eNom from Rightside
  2. Tucows expects $20 million EBITDA/year from “opportunistic” eNom acquisition
  3. Namecheap sues Enom and Tucows, demands transfer of 4 million domains
Categories: Domains

Informa Business Information guilty of reverse domain name hijacking

Domain Name Wire - Wed, 12/20/2017 - 21:45

Company filed UDRP against dictionary term in reverse domain name hijacking attempt.

Informa Business Information, a company that publishes information about the biopharma industry called The Pink Sheet, has been found to have engaged in reverse domain name hijacking for the domain name PinkSheet.com.

The decision isn’t surprising; when I saw the domain name I immediately thought of the dictionary term of Pink Sheets referring to investments.

A three-member World Intellectual Property Organization panel determined that the domain’s owner did not register and use the domain in bad faith. It also decided that it was very unlikely the domain was registered to target the complainant.

The panel ruled that Informa Business Information filed the case in bad faith:

Although the Complainant maintains that the true date of registration of the disputed domain name was unclear (and the Panel notes the Complainant’s change of position in this regard), there is no evidence on the record that the Respondent set out to target the Complainant. With the benefit of experienced intellectual property advisors, the Complainant should have been aware that, in these circumstances, its Complaint could not succeed. However and presumably in an effort to acquire the disputed domain name with minimal cost, it proceeded with the claim regardless. This is an abuse of the Policy and the Panel therefore finds this to be a case of reverse domain name hijacking.

Informa was represented by Stobbs IP Limited. This isn’t the first time Stobbs has been on the wrong end of a reverse domain name hijacking case. In a case for Cambridge.com, the panel found that the complainant “seriously misdescribed” the contents of the website.

The decision includes additional language about the fair price for domain names that should be well received by domain investors:

Since acquisition by the Respondent or its associated group entities, the disputed domain name appears to have resolved to a place keeper site that features an invitation to purchase the disputed domain name. As the Respondent is in the business of domain name broking, this is hardly surprising. Neither is the fact that the Respondent requested a purchase price of USD 100,000 following the Complainant’s unsolicited enquiry of it in August 2017. As in any market for commodities, domain name broking is about matching supply with demand; in the absence of any indicia of bad faith, there is nothing wrong per se with what the Complainant characterises as an “excessive offer.”

The domain owner was represented by Wiley Rein LLP.


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

The post Informa Business Information guilty of reverse domain name hijacking appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Mason Cole joins Perkins Coie as Internet Governance Advisor

Domain Name Wire - Wed, 12/20/2017 - 15:15

After nearly six years at Donuts, Mason Cole moves to law firm.

Mason Cole

Mason Cole has joined the law firm Perkins Coie as Internet Governance Advisor in its Trademark, Copyright, Media & Brand Protection practice. He will work with Partner Fabricio Vayra, who leads the firm’s ICANN activities.

Cole is not a lawyer but has been active with ICANN for more than 17 years.

He recently left his role as VP of Communications and Industry Relations at Donuts. There, he joined the company’s four founders to help it apply for hundreds of top level domain names and build a portfolio of about 200 new extensions.

Prior to that, Cole worked for Oversee.net and SnapNames.

Cole will be based in Perkins Coie’s Portland office.


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

The post Mason Cole joins Perkins Coie as Internet Governance Advisor appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

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