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.

Biohacks GmbH tries reverse domain name hijacking

Domain Name Wire - Fri, 04/09/2021 - 22:12

Panel had a laundry list of problems with the company’s case.

A World Intellectual Property Organization panel has found German company Biohacks GmbH guilty of reverse domain name hijacking.

Biohacks GmbH filed a cybersquatting dispute against Biohacks.com even though the current registrant acquired the domain years before Biohacks GmbH was formed. It doesn’t help the Complainant’s case that biohack is also a generic term.

The three-person panel gave five reasons for finding that Biohacks GmbH filed its dispute in abuse of the policy:

i) the Complainant, through its counsel, should have appreciated the weakness of its case and the fact that the dictionary term “biohacks” encompassed in the disputed domain name could not be exclusively referable to the Complainant, as claimed in the Complaint without any supporting evidence;

ii) the Complainant knew or should have known that the Respondent was not acting in bad faith, especially considering the disputed domain name was registered long before the Complainant acquired trademark rights for BIOHACKS;

iii) the Complainant should have carried out a minimal due diligence that would have disclosed the fact that the Complainant would not have succeeded in any way under any fair interpretation of the available facts before the filing of the Complaint;

iv) the Complaint was brought only after the Complainant failed to purchase the disputed domain name; and

v) the Complainant has failed to demonstrate its use of the trademark BIOHACKS before or after the registration of the disputed domain name and has not even addressed the bad faith registration requirement.

Horak Attorneys at Law represented the reverse domain name hijacker. Zak Muscovitch represented the domain name owner.

Post link: Biohacks GmbH tries reverse domain name hijacking

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. City of Paris ordered to pay $100k for reverse domain name hijacking
  2. Nat Cohen’s Telepathy sues for reverse domain name hijacking
  3. Things aren’t looking so good for Grandma Heidi Powell
Categories: Domains

Former France.com owner continues fight

Domain Name Wire - Fri, 04/09/2021 - 15:38

Man who lost domain name to France files petition for en banc rehearing.

Jean-Noël Frydman isn’t done fighting to regain control of France.com, a domain name he registered in 1994.

Frydman lost control of the domain name in 2018 after the French government presented a Paris Court of Appeals decision to Web.com, and Web.com transferred the domain to France.

The French Republic asserted the exclusive right to use the term “France” commercially, contending that under French law, the name “France” cannot be appropriated or used commercially by a private enterprise because doing so violates the French Republic’s exclusive right to its name and infringes on its sovereignty.

Frydman sued, but successive U.S. courts have delivered blows to his pursuit of getting the domain back. In a recent U.S. Court of Appeals decision, the court agreed that the French government has sovereign immunity under the Foreign Sovereign Immunities Act.

Now, Frydman has petitioned the appeals court for en banc rehearing. An en banc rehearing in appeals court is when the full court considers the case (rather than the three-judge panel) because the decision conflicts with other decisions by that court or a Supreme Court decision.

The new filing (pdf) states:

The Panel’s opinion conflicts with controlling authority and authoritative decisions in other Circuits and raises questions of exceptional importance regarding (1) United States citizens’ ability to enforce trademark rights against foreign sovereigns within the United States, (2) the supremacy of United States law, (3) the role of United States Courts in protecting United States-based property and property rights, and (4) the enforceability of United States intellectual property rights.

Post link: Former France.com owner continues fight

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Entrepreneur Media continues to sue entrepreneurs who use the word entrepreneur
  2. Macth.com owner sues Match.com and CitizenHawk after losing UDRP
  3. Another example of why your company must be the registrant of its domain names
Categories: Domains

Details behind MMX sale to GoDaddy

Domain Name Wire - Thu, 04/08/2021 - 15:42

MMX reveals details behind asset sale.

GoDaddy (NYSE: GDDY) announced yesterday that it is acquiring most of the assets of MMX (London AIM: MMX), aka Minds + Machines, for $120 million. Today, MMX issued a notice to shareholders about its planned sale.

The sale represents approximately 10 pence per sale, about double the closing price yesterday. After transaction costs, it’s about 8.8 pence per share. Shares in MMX are trading up 60% this morning to 7.35 pence.

This is an asset sale, so MMX will consider how to return cash to shareholders after the transaction closes. MMX will still have some activities to undertake, including providing transition services until as late as the end of next year.

GoDaddy will acquire these 28 strings:

.VIP .NRW .CASA .VODKA .XXX .FIT .MIAMI .FISHING .PORN .BEER .SURF .BOSTON .ADULT .YOGA .GARDEN .ABOGADO .WORK .FASHION .HORSE .RODEO .SEX .WEDDING .LUXE .DDS .LAW .BAYERN .COOKING .COUNTRY

GoDaddy will also acquire four MMX subsidiaries:

· MMX Bayern (holds .BAYERN)

· MMX China

· MMX NRW (holds .NRW)

· ICM Registry (holds .XXX, .ADULT, .PORN, and .SEX)

The transaction will require lots of approvals. The Chinese government will have to approve the MMX China transfer. MMX had lots of partnerships, including some with first right of refusal, that will also require approvals. (Notably absent from the list of TLDs is the troubled .London partnership, which MMX paid dearly to extract itself from.)

MMX has commitments from owners of 64% of shares to approve the transaction, so it expects the proposed sale to be approved.

Post link: Details behind MMX sale to GoDaddy

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. GoDaddy reports earnings, Domain revenue tops $300 million
  2. .Com Winners & Losers: NameSilo enters top 10 overall
  3. How domain name stocks fared in stock market rout
Categories: Domains

Sedo’s lastest end user domain name sales

Domain Name Wire - Thu, 04/08/2021 - 13:17

A design tech company paid $62,500 to buy the .com to match its .design domain.

Sedo’s top public sale this past week was Spline.com for $62,500. A company that uses a .design domain bought it and forwards it to the .design domain.

Here’s a list of end user domain name sales that were just completed at Sedo. You can view previous lists like this here.

Spline.com $62,500 – Spline is a design tool for 3D web experiences. The company launched on Spline.design and forwards the .com to the .design domain.

Yatoula.com €15,000 – French IT company Hugosoft bought this domain. It forwards to Yatoola.fr, which has a coming soon page.

CottageHealth.com $9,995 – Cottage Health is a not-for-profit health care system operating hospitals, urgent care centers, clinics, and virtual telehealth services in California. It currently uses cottagehealth.org for its website.

Canopia.com $9,900 – Palram Applications manufactures outdoor structure kits such as greenhouses, canopies, awnings, patio covers, gazebos and sheds. Canopia translates to Canopy in Spanish.

Deltatec.net €5,500 – Deltatec is a Belgium technology design firm that uses Deltatec.be for its website.

Finify.com $5,000 – Vertech Solutions Group, a mortgage technology company, bought this domain.

InternationalJournalofSpecialEducation.com $4,999 – First up, yes, this is a 37 character second level domain. It currently points to a page saying “As of the year 2002 the International Journal of Special Education will be published on this website.” This page was active many years ago but disappeared in favor of a parked page before its recent sale. I think it might have expired and the previous owner repurchased it.

Interzero.de €4,350 – Interseroh, a waste technology company, forwards this domain to Interseroh.de.

Couple.io $4,200 – Online dating company Couple.com forwards this domain to its .com site.

FR.at $3,999 – A blockchain company calling itself FRAT says it’s “building a Web 3.0 DeFi platform for the future. Community, DEX, and tools in one place with one token.” Brent Oxley owns Frat.com.

SK-Inc.com €3,900 – SK Co., Ltd appears to be a publicly-traded conglomerate in Korea.

SkaneatelesLakeRealEstate.com $3,500 – The domain forwards to FingerLakesRealEstate.com, the website for Skaneateles real estate in New York. Page Howe sold this domain.

SellMore.ch €2,880 – Sell More is a CRM company. It forwards the domain to SellMore.de.

MultiAction.com $2,500 – Multi-Action Communication Inc. is a label manufacturer.

Post link: Sedo’s lastest end user domain name sales

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. 22 end user domain name sales
  2. ccTLD owners add .com in this week’s Sedo end user sales list
  3. 50 End User Domain Name Sales up to $500,000
Categories: Domains

Breaking: GoDaddy to acquire MMX, .Club, .Design

Domain Name Wire - Wed, 04/07/2021 - 20:45

GoDaddy (NYSE: GDDY) has acquired 28 new top level domains from MMX, as well as the .Club and .Design top level domains.

The company is paying $120 million for the MMX strings. MMX, a publicly-traded new top level domain company had a market cap of £40 million. The MMX transaction will require shareholder approval and approval from some of MMX’s partners on some of the domains.

MMX’s two largest namespaces are .VIP  at 900,000 registrations and .work 650,000 registrations. Somewhat surprisingly, the transaction includes MMX’s adult domains including .XXX.

The acquisition will help MMX get out from the public limelight. The company has struggled to grow registration and revenue numbers over the years as a small public company.

Financial details of the .club and .design transactions were not revealed. .Club was a single-domain TLD operator and .Design was owned by Top Level Design. .club has over 1 million registrations and .design has about 130,000.

GoDaddy entered the domain name registry business with its acquisition of Neustar’s registry business last year.

In addition to acquiring these strings, the company won the backend business for .basketball, rugby, and .ally.

After the acquisitions, GoDaddy will own, manage or operate more than 240 top level domain names.

Post link: Breaking: GoDaddy to acquire MMX, .Club, .Design

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. .Club lands among Top 10 new TLDs on first day
  2. U.S. government asks ICANN to investigate GoDaddy’s Whois policy
  3. PIR (.Org) slashes registry fee to Afilias in half to $18 million
Categories: Domains

One.com loses cybersquatting dispute against 0ne.com

Domain Name Wire - Wed, 04/07/2021 - 16:32

Domain name owner acquired the domain in an expired domain auction last year.

Domain name and hosting company One.com Group AB has lost a UDRP it filed against the domain name 0ne.com, with a zero replacing the o.

Cryptocurrency investor Stanislav Nikolskyi acquired the domain name in a DropCatch.com auction for $2,305 in July 2020. He said he acquired the domain name because wallet address in Ethereum start with the number 0.

A Czech Arbitration Court panelist agreed with One.com that the domain name was confusingly similar to its mark, but found in favor of the Respondent on rights and legitimate interests and registration and use in bad faith.

Panelist Victoria McEvedy noted that using a generic word as a trademark comes with limitations:

No-one can own a number or dictionary word to the exclusion of the rest of the world. They are inherently lacking in the distinctiveness required for trade mark law. Trade marks are badges of origin that enable the public to identify the goods and services of a trader so they can make a repeat purchase safe in the knowledge that the quality should be the same the second time around. An ordinary word or number cannot function in that way for obvious reasons. That is, unless they have what we call “acquired distinctiveness” or secondary meaning so that they are so famous that it is the brand that the relevant public bring to mind and not the dictionary term. That is not really possible with a number or a common word –so that in their original meaning, they remain the property of and available to, all. This forms the basis of the prohibition on descriptive and generic marks which recognises that many traders want to use descriptive terms for their informational values and that no one trader should be able to monopolise them. Those selecting such terms as marks have to tolerate confusion and the Policy reflects this by protecting such as fair or legitimate use. Furthermore, consumers are not easily confused by such terms as they understand they are common ordinary terms, employed by many undertakings, with a low degree of distinctiveness.

In pre-dispute correspondence, Nikolskyi informed One.com Group:

…You can pass these two options to your ‘Client’: a. Offer price and buy it out without wasting time and resources for legal battle (and then eventually loosing [sic] it) b. Start a UDRP claim, I’m in no rush and have resources to defend my name, ‘very similar’ is a weak argument and I had experiences in past, so in both cases I’m pretty confident. Either I get a deal, or I get a win under my belt which only adds value to credibility to the name…

Apparently, he was right.

Advokat Lisbet Andersen represented One.com Group. Cylaw Solutions represented the domain name owner.

Post link: One.com loses cybersquatting dispute against 0ne.com

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Arbitrator Rains on Media Rain’s Parade
  2. RDNH should have been considered in BankWell.com decision
  3. Whoa, this company totally doesn’t understand UDRP
Categories: Domains

.Com finished last year with a bang – updated rankings

Domain Name Wire - Wed, 04/07/2021 - 13:57

A strong month for .com.

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

Registrars had a strong December for new .com registrations. GoDaddy’s brands topped 1.1 million new .com registrations.

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

1. GoDaddy.com* 1,109,061 (NYSE: GDDY) (832,844 in November)
2. Namecheap Inc. 293,601 (263,785)
3. Newfold Digital+ 203,348 (232,929)
4. Tucows** (NASDAQ:TCX) 188,512 (207,024)
5. Alibaba (HiChina) 169,862 (203,286)
6. Google Inc. (NASDAQ: GOOGL) 140,523 (144,030)
7. IONOS^ 112,642 (120,167)
8. CentralNic^^ (AIM: CNIC) 105,075 (80,478)
9. Wix (NASDAQ: WIX) 88,149 (96,220)
10. NameSilo 87,778

Here’s the leaderboard of the top registrars in terms of total .com registrations under management as of the end of 2020.

1. GoDaddy* 55,136,925 (54,735,035 in November)
2. Newfold Digital+  14,582,476 (14,595,094)
3. Tucows** 12,967,927 (12,988,434)
4. Namecheap 7,007,290(6,856,440)
5. Alibaba  6,160,015 (6,133,679)
6. IONOS^ 5,763,174 (5,719,043)
7. TurnCommerce++ 4,582,174 (4,513,069)
8. Google  4,105,308 (4,052,113)
9. CentralNic^^ 2,951,343
10. GMO 2,100,966 (2,149,198)

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

* Includes GoDaddy, Wild West Domains, Uniregistry and 123 Reg
** Includes Tucows, Enom, Ascio and EPAG
+ Includes PDR, Domain.com, FastDomain, Bigrock, Network Solutions, Register.com, SnapNames registrars, and Crazy Domains/Dreamscape. There are other Newfold registrars, but these are the biggest.
++ Includes NameBright and DropCatch registrars
^ Includes 1&1, PSI, Cronon, United-Domains, Arsys and world4you
^^ Includes Key-Systems, 1API, Internet.bs, TLD Registrar Solutions, RegistryGate, Moniker, Instra

Post link: .Com finished last year with a bang – updated rankings

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Dynadot jumps into top 10
  2. .Com leaderboard gets a shakeup
  3. Top ten domain name registrars, ranked by .com
Categories: Domains

Reverse domain name hijacking in four letter domains case

Domain Name Wire - Tue, 04/06/2021 - 21:20

Panel said Complainant’s representative showed an “alarming unfamiliarity with the UDRP”.

A World Intellectual Property Organization (WIPO) panel has found two Indian companies to have engaged in reverse domain name hijacking. It added some especially harsh words for the Complainants’ attorney.

HSIL Limited, Somany Home Innovation Limited and SHIL Ltd., Brilloca Limited, two related companies, filed the complaint against Get On The Web Limited. They argued that the latter’s ownership of HSIL.com and SHIL.com constituted cybersquatting on their marks.

Never mind that the Respondent registered the domains before the Complainants had rights to trademarks in HSIL and SHIL. And never mind that the Respondent previously used the domain names for its business.

The panel found that the Complainants failed on all three prongs of the UDRP for the domain name SHIL.com, and on the last two for HSIL.com.

The three-person WIPO panel listed five reasons the complaint was reverse domain name hijacking. Summing up the case, it wrote:

In sum, the Complainant’s professional representative betrays an alarming unfamiliarity with the UDRP and the two decades of precedent under it, to the point of including the Registrar as a respondent merely for performing its non-discretionary function of registering an available domain name.  Such conduct in any court would result in a swift dismissal and appropriate sanctions for wasting the parties’ and the court’s time.  This Panel is limited to a find of abuse, which it readily imposes.

Manav Gupta represented the Complainants and John Berryhill represented the Respondent.

Post link: Reverse domain name hijacking in four letter domains case

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Wirecard nailed for Reverse Domain Name Hijacking
  2. Walker Edison is a reverse domain name hijacker
  3. Mechoshade busted for reverse domain name hijacking
Categories: Domains

March’s Top 5: GoDaddy, France.com and more

Domain Name Wire - Tue, 04/06/2021 - 17:32

A look at the top five stories on Domain Name Wire last month.

These were the top stories on Domain Name Wire last month, ranked by pageviews:

1. GoDaddy to remove locks on Brent Oxley’s domains, changes policy – The registrar changed its policy for locking domains that are subject to a legal dispute after an outcry from the domain name industry.

2. Domain investing is changing. It’s time to adapt your strategy – What worked before might not work in the future. Here’s what’s changing and how to adapt.

3. Google among end user buyers at GoDaddy, SelfMade.com sells for nearly $1M – GoDaddy’s October sales included Selfmade.com, which sold for just under $1 million.

4. Anyone can start a club on Clubhouse now. What does this mean for .Club? – More clubs might use .club domains for off-app interactions with fans.

5. Court rules France can keep France.com – Previous domain name owner dealt a blow in court.

 

Miss a podcast? Catch up today:

#331 – Closing domain deals with a contract (Joe Uddeme) – listen

#330 – A different domain model (Arno Vis) – listen

#329 – Verisign’s .com printing press (David Dayen) – listen

#328 – Adapting your domain investing strategy (Logan Flatt) – listen

#327 – Domain investing strategies (Nikul Sanghvi) – listen

Post link: March’s Top 5: GoDaddy, France.com and more

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. April’s top domain stories on Domain Name Wire
  2. August’s top news and podcasts
  3. May’s hottest domain name stories
Categories: Domains

Analyzing HugeDomains’ latest UDRP win

Domain Name Wire - Tue, 04/06/2021 - 16:31

One panelist dissented in a case of a trademark vs. common name.

HugeDomains has successfully defended its domain name Affron.com in a UDRP cybersquatting dispute.

Pharmactive Biotech Products, S.L., a Spanish company that sells a saffron extract under the brand name Affron, filed the dispute against the domain name investment company.

While the Complainant has a trademark for Affron, HugeDomains argued that it’s also a common name and business name to which the Complainant does not have exclusive rights.

HugeDomains acquired the domain name in 2013. The Complainant claims trademark rights dating 2012, although the exact use of its trademark worldwide before 2013 is disputed.

The majority of the panel found that the domain was not registered and used in bad faith and that the Complainant didn’t show that HugeDomains lacked rights or legitimate interests in the domain name.

Panelist Alejandro Touriño, a lawyer in Spain, dissented. I often find that a dissenting panelist in a three-person panel is the only one from the same country as the Complainant.

Touriño mostly relied on Pharmactive Biotech Products’ trademark for Affron in arguing that the domain should be transferred. He wrote, “it is likely that the Respondent knew (or should have known) of the Complainant’s trademark when it registered the domain name.”

Even if HugeDomains did know of the trademark, HugeDomains’ argument is that the trademark for Affron did not give it worldwide exclusive rights to the mark outside of its product category.

The oddest thing about this case is that HugeDomains was asking only $5,195 for the domain. Between the lawyers and the WIPO fees, I suspect the Complainant spent more than that to file its case. And it still doesn’t have the domain to show for it.

Post link: Analyzing HugeDomains’ latest UDRP win

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Juniper Networks Loses Case for Juniper.tv
  2. Square Grouper Tiki Bar guilty of Reverse Domain Name Hijacking
  3. Standard & Poor’s loses domain name dispute
Categories: Domains

A downside to “Buy Now” for domain names

Domain Name Wire - Tue, 04/06/2021 - 14:58

Buy Now is easier but you get less data about interest in your domain.

I’m a big fan of setting Buy Now prices on domain names. Most of the domains I sell are for between $1,000-$5,000. I don’t want to waste my time negotiating for sub-$5,000 domains, and a benefit of Buy Now prices is you’re telling the prospective buyer to take it or leave it.

There’s a downside to this, though. By not accepting offers, you’re missing a key signal to determine if there’s demand for your domain.

Even if it’s for much less than your asking price, an offer is a signal that there’s interest in your domain name. A domain with multiple offers gives you more certainty that there’s demand for your domain and a higher likelihood that someone will eventually buy it for your price.

I was reminded of this the other day as I reviewed my domains and considered my strategy for them going forward. For the domains I listed at DAN.com with just a Buy Now or lease option, I had no data signals about potential buyer interest other than traffic (which isn’t always a good signal). I had decent data for domains listed on platforms with the make offer option.

One solution is to leave the negotiating up to someone else. With Afternic, I set a Buy Now price and a floor price. This allows Afternic to negotiate on my behalf. Afternic doesn’t expose data about inquiries in your account, but you can request the data from your account manager.

I still think Buy Now is the way to go for most of my domains. However, it would be helpful if marketplaces captured signals on Buy Now domains and provided these to sellers. For example, it would be helpful if DAN.com showed if someone added a domain to the cart but didn’t check out, or if someone interacted with the domain financing options on a domain.

Post link: A downside to “Buy Now” for domain names

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. You really need to get on the fixed price domain bandwagon
Categories: Domains

NameSilo update: record revenue, acquisition still in the works

Domain Name Wire - Mon, 04/05/2021 - 16:15

Company tops $3 million revenue in March.

Domain name registration company NameSilo (CSE:URL) issued an update on its operations today.

In the release, the company said that monthly revenue exceeded USD $3 million in March for the first time ever. It also paid down nearly $1 million (Canadian) of debt, bringing its outstanding debt to under CAN $5 million.

The company now has 3.82 million domain names under management.

In December, the company announced that it entered into a non-binding letter of intent to sell its assets to WGH Holdings BV for USD $30 million. The idea is to combined NameSilo into a domain registration business in Africa. The release states, “Both parties continue to work towards meeting the conditions to enter into a definitive agreement. More details will be announced when available.”

Post link: NameSilo update: record revenue, acquisition still in the works

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. NameSilo doubles in size in just one year, crosses 2 million domains
  2. NameSilo acquires domain registrar and expired domain company NamePal
  3. NameSilo finds buyer as debt payments loom
Categories: Domains

The “new” NamesCon and Cloudfest – DNW Podcast #332

Domain Name Wire - Mon, 04/05/2021 - 15:30

A look at the future of these two conferences under new ownership.

NamesCon and Cloudfest are under new ownership. On this week’s show, I talk with Christian Jaeger, CEO of the new owner WHD Event GmbH, and Soeren von Varchmin, Chairman of the Supervisory Board. We discuss the history of the events, who now owns the company, and what’s next now that the conferences have been spun out of a large corporation’s control. It has me excited to attend my next in-person event!

Tool of the week: InstantDomainSearch.com.

Also: Big court ruling, three RDNHs, top domain sales and more.

Sponsor: Sav.com

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

Post link: The “new” NamesCon and Cloudfest – DNW Podcast #332

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Domain name due diligence – DNW Podcast #148
  2. Soeren von Varchmin – DNW Podcast #165
  3. Top Domain Sales of the Year – DNW Podcast #197
Categories: Domains

ICA hopes for in-person meetup this year

Domain Name Wire - Fri, 04/02/2021 - 18:40

Get vaccinated. Get together!

I’m hopeful that in-person domain name industry events can reconvene sometime this year. Internet Commerce Association, a trade group for domain name owners, is trying to make one happen.

The organization sent a survey to its members today asking if they’d consider attending an in-person meetup this year. It’s targeting September 19-20 for the event but has asked members if other days would work better.

That should be enough time for any adult living in the U.S. to be vaccinated.

ICA is pitching four possible locations: Chicago, Las Vegas, Miami and Oklahoma City. (I imagine the latter is on the list because it’s the home of Digimedia.) Members can suggest other locations in the survey.

Members are encouraged to check their email for a link to the survey.

Membership in Internet Commerce Association starts at just $25 per month.

Post link: ICA hopes for in-person meetup this year

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Domain Name Companies Spend $2M Lobbying Washington
  2. 2020 Lonnie Borck Memorial Award nominations are open
  3. Nominations now open for ICA’s 2021 Lonnie Borck Memorial Award
Categories: Domains

Court overturns VisitQatar.com UDRP decision

Domain Name Wire - Fri, 04/02/2021 - 13:29

Judge agrees that owner of VisitQatar.com is not cybersquatting.

United States District Judge Daniel D. Domenico has ruled in favor (pdf) of the owner of VisitQatar.com in a cybersquatting suit.

Qatar National Tourism Council won a UDRP against Teymur Mehdiyev, the owner of the domain name, in 2019. It was a complicated case and Mehdiyev filed a lawsuit to stay the transfer.

The decision to rule in favor of Mehiyev in court was easier than the complicated UDRP because of a key difference between UDRP and the Anticybersquatting Consumer Protection Act (ACPA).

Someone registered VisitQatar.com in 2004, and Mehiyev acquired the domain name in 2016. Qatar National Tourism Council began developing a trademark for Visit Qatar in 2015, between the registration date and Mehiyev’s acquisition.

UDRP panelists usually consider the date of the current owner’s acquisition of the domain when determining if it was registered in bad faith. While some courts haven’t settled the matter, most consider the original registration date the key date for determining if a domain registration is cybersquatting. In this case, what matters is that 2004 is before the tourism council began using the term as a trademark in 2015.

In making his ruling, Judge Domenico compared a domain name acquisition to a real estate:

There is no dispute here that Mr. Mehdiyev’s predecessor registered prior to the Council’s mark becoming distinctive, and was thus not cybersquatting. And there is no dispute that Mr. Mehdiyev legally acquired the predecessor’s legal interest in the domain. Acquiring another’s legal interest in property (intellectual or otherwise) is not squatting…

…And this raises a final policy point. While § 1125(d)’s obvious purpose is to prevent cybersquatting, it also helps provide those who own or are developing potentially distinctive marks an incentive to either choose marks that are not similar to domains that are already registered, or, perhaps, to purchase those domains before they expend significant goodwill creating their similar marks. Allowing a mark owner to undo an otherwise valid, pre-existing registration by calling it cybersquatting would be akin to building a house on land subject to another’s lien and calling the lienholder a squatter. The incentives created by allowing that possibility undermine the broader purposes of the Act, and are not necessary to prevent true cybersquatting.

Post link: Court overturns VisitQatar.com UDRP decision

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Lawsuit filed over Celluvation.com after UDRP decision
  2. The wild story about how the domain name CM.com was just registered
  3. XYZ files opening brief in request for Verisign to pay $1.6 million
Categories: Domains

Reverse domain name hijacking in Shaktiman.com dispute

Domain Name Wire - Thu, 04/01/2021 - 20:45

India firm tries reverse domain name hijacking.

A World Intellectual Property Organization panelist has found Tirth Agro Technology Private Limited to have engaged in reverse domain name hijacking for the domain Shaktiman.com.

“Shaktiman” is a generic word in the Hindi language that means “strength” or “might”. It’s used by many companies and is also the title of a popular Hindi television show featuring a superhero protagonist under the name of “Shaktiman”.

Historical Whois records show multiple registrants since the domain was registered in 2000, but it seems that it’s really the same company. Tirth Agro didn’t put forth any evidence (or argument) otherwise.

Tirth Agro claims trademark rights dating to 1961, but the Respondent and panelist questioned this date. The Complainant did not explain its connection to the early trademarks registered under a different company name. Nor did it explain how a first use date in a later trademark was from 1999 even though the company wasn’t incorporated until 2000. The complainant provided evidence of use since 2000 but did not submit anything for before that year.

In finding reverse domain name hijacking, panelist Harini Narayanswamy wrote:

Taking into account the entire set of facts in this case, the Complainant or its counsel ought to have known of the lack of relevant evidence, which would prove to be a hurdle to establish that the Respondent had registered the disputed domain name to target its mark.

Post link: Reverse domain name hijacking in Shaktiman.com dispute

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Owner of Corediagnostics.in Guilty of Reverse Domain Name Hijacking
  2. JetGo guilty of RDNH after filing “seriously misleading” case against Frank Schilling
  3. Pickleball cybersquatting dispute ends in kitchen violation
Categories: Domains

Lawyer who filed a reverse domain name hijacking case says so what?

Domain Name Wire - Thu, 04/01/2021 - 16:24

Lawyer thinks it’s no biggie that a panel found that he filed a misleading UDRP complaint.

A lawyer who filed a RDNH case says, “…RDNH label from the UDRP has no weight anywhere. Might as well stick thumb in mouth and cry…”

Yesterday, I wrote a story encouraging people to hire a domain name attorney when faced with a domain dispute of some kind. One person took exception to this suggestion: a lawyer who recently filed a reverse domain name hijacking case.

Nathan Brown, attorney at Brown Patent Law, filed a UDRP against the domain name ITDC.com, which is owned by Internet Tool & Die Company. The Complainant was found guilty of reverse domain name hijacking for a number of reasons. A critical one is that the complaint said the domain registrant didn’t exist at the address it listed, even though the Complainant knew the domain owner was a subsidiary of a business that did exist at that address.

In response to the suggestion that you hire a specialist (the story was unrelated to the ITDC.com decision), Brown tweeted:

So you win the domain but then get hammered in Federal Court; and eventually lose everything? #bigpicture

Domain disputes are such a very small part of the equation; risking your entire business on a “specialist” in domain disputes is a fool’s game. https://t.co/QXrqTI2Mwk

 

— Brown Patent Law (@PatentlyCurious) March 31, 2021

That didn’t make much sense to me. I asked him to explain. To which he responded:

I see only two purposes of the UDRP, and that is to force early discovery on the other side or to obtain an optimal jurisdiction after the decision. https://t.co/H2zAsloZTq

— Brown Patent Law (@PatentlyCurious) April 1, 2021

I’m not sure what the optimal jurisdiction argument is. You can file a lawsuit anywhere you have jurisdiction. If you file a UDRP, you’re also submitting yourself to the jurisdiction of either the domain registrar’s location or the domain owner’s location. In this case, the Complainant and its lawyer are in Arizona. Neither the registrar (Enom) or the Respondent are located there.

If you have a good case then UDRP is a great way to get the domain back fast and cheap. If you have a bad case then you’ll get hit with reverse domain name hijacking

— DomainNameWire.com (@DomainNameWire) April 1, 2021

I wish it was that simple. Lastly, RDNH label from the UDRP has no weight anywhere. Might as well stick thumb in mouth and cry. Equal weight.

— Brown Patent Law (@PatentlyCurious) April 1, 2021

Well, he has a point there. There’s no fine for RDNH in a UDRP. But even if a court doesn’t have to give deference to a UDRP decision that showed that the Complainant misled the tribunal and that it’s not a case of cybersquatting, I have to think those make for good opening arguments against any lawsuit brought against the domain. Oh, and if found to have tried reverse domain name hijacking in court, there can be some stiff costs associated with that.

I can’t find out much about Brown’s legal practice. The website in his twitter bio leads to a 404 error. He has a Facebook page that has a few posts from several years ago. I found one other UDRP he filed in 2018.

Post link: Lawyer who filed a reverse domain name hijacking case says so what?

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Owner of Corediagnostics.in Guilty of Reverse Domain Name Hijacking
  2. JetGo guilty of RDNH after filing “seriously misleading” case against Frank Schilling
  3. RDNH: A domain has to be registered in bad faith
Categories: Domains

I might be Biased, but this should be reverse domain name hijacking

Domain Name Wire - Thu, 04/01/2021 - 14:22

Owner of Unbiased.co.uk takes another crack at Unbiased.com.

The owner of Unbiased.co.uk has failed for a second time to get the domain name Unbiased.com through a UDRP.

The company, which helps people find financial advisers, mortgage brokers, solicitors and accountants, filed a UDRP against Unbiased.com in 2015. It lost that case because the panel determined that it was likely that the domain was acquired due to its generic value, not to target Unbiased.co.uk.

It filed another case in January but apparently didn’t bring anything new to the table. The three-member World Intellectual Property Organization panel declined to consider the refiled case.

Panelist Neil Anthony Brown concurred with the majority opinion that the case should be dismissed and said this is a case of reverse domain name hijacking. Brown pointed out that Unbiased.co.uk didn’t mention its first failed attempt at securing the domain in a UDRP when filing the second dispute and chose a different venue (National Arbitration Forum and then WIPO).

He wrote:

This is therefore the classic case where it can be said that the Complainant must have intended to harass the Respondent and put it to timewasting expense to defend this claim for the second time, as it knew it could not succeed without good cause being shown why the case could be commenced. If ever there were a case showing the wisdom of the Canadian rule that in an appropriate case the panel may award part of a respondent’s costs against an offending complainant, this must be it. But in the absence of power to award costs against a recalcitrant complainant, making a finding of RDNH is the only sanction that can be imposed.

While Unbiased.co.uk doesn’t have a good argument to win a UDRP, the domain name owner should seriously consider removing links to financial services on its parked page.

Post link: I might be Biased, but this should be reverse domain name hijacking

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. RDNH should have been considered in BankWell.com decision
  2. Tambour Ltd filed complaint that was “bound to fail”
  3. Is this trademark infringement or cybersquatting?
Categories: Domains

FSM.com just sold for $162k. Let’s look at LLL .com domains:

Domain Name Wire - Thu, 04/01/2021 - 13:03

Nine three letter .com domains have sold this year, and five of them for $100k or more.

Domain name investor Greg Ricks has struck again, this time selling FSM.com for approximately $162,000 through Afternic. Whois shows the buyer is in Kansas.

This makes nine public three-letter .com sales in 2021:

Zag.com $450,000 – upgrade for Zag-Inc.com
FTA.com $400,000
FSM.com $161,719
PLP.com $117,500 – Preformed Line Products, which uses the domain Preformed.com
GWI.com $105,000 – Trendstream Limited, which uses GlobalWebIndex.com
CTX.com $46,000
AAF.com $45,050
AQS.com $31,387
LGW.com $26,500

I’ve noted the buyer when known. AAF.com and AQS.com were DropCatch sales, so these were likely domain investor sales. In my mind, any end user sale of a three letter domain with solid Western letters should be six figures at this point.

Post link: FSM.com just sold for $162k. Let’s look at LLL .com domains:

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. FTA.com domain name sells for $400,000
  2. Stat Check: How is Domain Aftermarket Doing?
  3. Businesses Continue to Buy and Use 3 Letter Domain Names
Categories: Domains

Don’t just hire a lawyer. Hire a specialist

Domain Name Wire - Wed, 03/31/2021 - 15:28

Hire an attorney who specializes in the type of dispute you have.

A common mistake I see people make when faced with a legal challenge is hiring a lawyer who doesn’t specialize in the legal area. When you have an estate issue, you hire an estate attorney. When you set up a company, you hire a corporate attorney. So when you have a domain name issue, you hire an attorney that specializes in domain names. Don’t just use the attorney you used to set up your business.

If you hire an attorney specializing in several things, they probably aren’t specialized enough to handle a domain name dispute. Even some trademark attorneys aren’t the right lawyer for a UDRP or cybersquatting dispute; you should hire someone who has already handled many such cases.

Earlier today, Nat Cohen tweeted:

Telepathy is fortunate to have been represented by several of the top minds in domain name law, including Zak Muscovitch (@DNattorney) , Ari Goldberger (@esqwire), Jason Schaeffer (@TLDadvisor), John Berryhill (@Berryhillj) and David Weslow (@DavidWeslow). /2

— Nat Cohen (@domainarts) March 31, 2021

Nat has seen his share of spurious claims against his domain names because he has such a valuable portfolio. He turns to attorneys who have deal with domain disputes to help him defend his domain assets.

There are several reasons to hire an attorney who has a lot of history with domain disputes if you ever face a challenge to one of your domains. If you hire a lawyer without deep existing knowledge of this specialty, then:

1. You are paying the lawyer to learn this area of law. You will rack up billable hours of them researching how UDRP or cybersquatting laws work.

2. They won’t understand the nuance of these cases. Skilled UDRP lawyers know the right buttons to push — and just how far — when arguing a case.

3. They don’t know the history by memory. Lawyers with UDRP experience understand the individual panelists and which cases to refer to. They either have a database or know which cases to cite by memory.

Most importantly, a good domain attorney can tell you whether you have a good case or not!

Post link: Don’t just hire a lawyer. Hire a specialist

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Complainants should hire domain name attorneys, too
  2. Brand owners: please, hire a domain attorney
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.