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.

My thoughts on Names.Club taking third-party listings, .com

Domain Name Wire - Fri, 01/25/2019 - 14:48

Pay-over-time domain marketplace will let domainers join the party with any TLD.

Names.Club will soon accept .com and other domain listings from domainers.

Names.Club is expanding its payment-plan domain marketplace to allow third parties to list their domain names in all top level domains.

The Dot Club registry originally created the marketplace for new top level domain registries to offer premium domains on payment plans. Buyers make a down payment and get immediate access to use the domain name. They pay off the balance over 60 months.

Opening the service up to domainers and all top level domains is great. I love seeing domain companies innovate. And payment plans are becoming a popular way to close deals when buyers don’t have enough cash.

Dot Club CMO Jeff Sass told me that there will be protections in place to make sure that buyers don’t use domains in a way that could harm the domain’s value. As a seller, you don’t want a  buyer to use blackhat SEO or use a domain to spam, only to stop making payments a few months in.

When a domain sells, the owner will transfer it to a holding account managed by Names.Club at the owner’s registrar. The domain can’t be transferred from this account but the buyer will be able to change the nameserver.

I’ve only done a couple of payment plan deals. Usually, I like to understand how the buyer plans to use the domain before doing the deal.

I also think five years is a long time for payments. Five years makes sense for domain registries that are playing with “house money” on their domains, but it would be nice to be able to offer shorter terms.

Personally, I’d feel most comfortable putting names on Names.Club that won’t break the bank if the buyer does something bad with them.

Another innovative thing about Names.Club is how it integrates brokers into the action. They can offer buyers a discount code and then they get paid when someone they refer buys a domain.

Bottom line: kudos on expanding the marketplace. Some kinks might need to be worked out, but I love seeing stuff like this.

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

Related posts:
  1. Donuts’ first new domain names are starting to drop…
  2. NamesCon acquired by WorldHostingDays
  3. CIRA wants patent for registry “tag” system
Categories: Domains

My two sessions at NamesCon

Domain Name Wire - Thu, 01/24/2019 - 19:51

Join me for discussions about big new TLD sales and .com prices.

I will be both a moderator and panelist at next week’s NamesCon conference. I invite you to come to my sessions on Tuesday.

Making sense of $500k for a nTLD, 11 am Tuesday 1/29 on the RegistryOffice breakout stage

I interview two people who spent $500k on new top level domains: Blake Janover, who bought Home.Loans for $500,000 and Mike Kugler, who paid $500,300 for Vacation.Rentals. We will discuss what gave them the conviction to spend record-breaking amounts on new top level domain names and how the domains have (and haven’t) worked out for them. I interviewed Blake on my podcast a year ago and Mike about 9 months ago. Both have launched their sites and we’ll get an inside look at how their domains and websites are performing.

.Com Price Increase, 1 pm Tuesday 1/29 on the .Global Keynote stage

Derek Newman will moderate a session with me, Tucows CEO Elliot Noss, and Internet Commerce Association general counsel Zak Muscovitch discussing .com prices. In light of the U.S. government giving the green light late last year to .com price hikes, we will discuss the merits of .com price changes and who wins/loses.

I hope to see you at one or both of these sessions.

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

Related posts:
  1. NamesCon acquired by WorldHostingDays
  2. Amazon updates its new top level domain website to prepare for launch
  3. Two scheduling tools to make NamesCon a success
Categories: Domains

ParkingCrew enables SSL on domains that receive HTTPS requests

Domain Name Wire - Thu, 01/24/2019 - 19:24

Domains that get lots of https traffic will get an SSL certificate.

Domain name parking company ParkingCrew is now generating SSL certificates for domain names and serving traffic over https once the domains meet a certain threshold.

Parking companies are struggling to figure out how to cope with browser updates that mark sites as ‘not secure’ if they don’t have an SSL certificate. For example, Last year Undeveloped.com created a solution to issue SSL certificates for domain names.

ParkingCrew won’t issue a certificate for all domains. Instead, it will monitor for how much traffic the domain gets over https to determine which domains need them. If there’s a lot of https traffic hitting the domain, then an SSL certificate will be issued and traffic will be served over https for a period of time.

As an example, an expired domain name that used to have a website secured with SSL may receive inbound traffic from https:// links.

Customers must use ParkingCrew’s nameservers in order to use SSL.

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

Related posts:
  1. Domain inquiries could drop next month. Blame SSL.
  2. Tool makes it possible to park .App domain names
  3. Undeveloped adding SSL to all landing pages
Categories: Domains

Miguel Torres S.A. loses another cybersquatting claim

Domain Name Wire - Thu, 01/24/2019 - 17:08

GDPR and a registrar’s parking ads might have saved it from a second reverse domain name hijacking finding.

A wine company changed its branding to Familia Torres and then went after a family’s domain name FamiliaTorres.com.

Wine producer Miguel Torres S.A. lost another cybersquatting complaint filed with World Intellectual Property Organization (WIPO) and narrowly avoided being found guilty of reverse domain name hijacking for a second time.

In 2001, the company was found to have engaged in reverse domain name hijacking over the domain name Torres.com.

The company filed the new case against FamiliaTorres.com, which is owned by a family with the last name Torres in Miami.

In the wine company’s defense, the Whois record showing the owner was blocked because of GDPR when it made the initial complaint. (Using historical Whois at DomainTools would have uncovered the owner’s identity.) Also, the domain registrant’s registrar was showing wine-related pay-per-click ads on the domain.

But once WIPO revealed the owner’s information to Miguel Torres S.A., the wine company didn’t back down. It doubled down in its amended complaint.

While the Respondent didn’t ask for a finding of reverse domain name hijacking, the panelist considered it:

In this case, the Panel has found the Respondent’s evidence to be compelling in demonstrating long-standing rights and/or legitimate interests in respect of the Domain Name in light of the Respondent’s surname and Hispanic background. At the time the Complainant filed the original Complaint, it was likely not in a position to know of this (given especially that, because of redaction in purported compliance with the GDPR, the Respondent’s identity was not known) and it had seen that (albeit it appears for a limited time, unbeknown to the Respondent) the Domain Name resolved to a parking page featuring pay-per-click links to third party websites including those of competitors of the Complainant.

On the face of it, therefore, the Complainant could argue some justification for filing a complaint, despite the length of time since the Domain Name was registered. On the other hand, it could be argued that by the time the Complainant came to file the amended Complaint it knew the identity of the Respondent and might have anticipated the likely defence on the part of the Respondent. The Panel has also noted that the Complainant was arguably coy about admitting that it had only adopted the ‘Familia Torres’ brand very recently.

However, panelist Ian Lowe decided that the “circumstances are not sufficient” to find RDNH.

I’m a bit surprised by this decision given that the wine company only recently started using the Familia Torres moniker. GDPR and the registrar’s parked page ads might have saved the wine company.

The Complainant was represented by Curell Suñol S.L.P. The domain owner was represented by Muscovitch Law P.C.

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

Related posts:
  1. Master Call Connections is a domain name hijacker
  2. CBNT.com UDRP decision is bad, but domain owner should take some of the blame
  3. Cybersquatting complaint filed against MicroStrategy’s Glory.com domain
Categories: Domains

WordPress.com to use Donuts Relevant Name Search

Domain Name Wire - Thu, 01/24/2019 - 14:00

Donuts gets a new user for its domain search system.

The WordPress.com domain search box

WordPress.com will start using the Donuts Relevant Name Search (RNS) engine for all international-language domain searches, the two companies announced today.

RNS is a domain search tool that returns relevant second level/top level results to domain searchers across all top level domains. It was originally developed inside Enom and adopted by Name.com when the two companies were under common ownership. Name.com is still owned by Donuts.

WordPress.com compared multiple domain search options including its own in-house tool before going with Donuts RNS. However, WordPress.com will continue to use its in-house search tool for English-language queries. This suggests that the internal solution worked best on English queries, at least for WordPress.com’s needs.

Kellie Peterson, registrar general manager for WordPress.com, said, “After months of rigorous testing, we are delighted to select Donuts RNS. It is powerful, delivers top conversion rates, and is tunable to our specific needs – exactly what we need in a dynamic, competitive environment. The data give us high confidence that RNS enables our international users to find the best
domain names to meet their needs.”

(Listen to a podcast with Kellie Peterson.)

 

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

Related posts:
  1. Donuts offers free name search technology
  2. Donuts’ first new domain names are starting to drop…
  3. Cost of Donuts’ DPML trademark protection service to soar
Categories: Domains

16 end user domain name sales up to $60,000

Domain Name Wire - Wed, 01/23/2019 - 18:23

A solar energy company, lifestyle brand and a cold brew coffee company all bought domain names this past week.

Sedo’s top public sale this past week is Adika.com, which was purchased by a clothing company. I also like Dossier.com. And check out the deal the buyer of Smudge.com got!

Let’s get to this week’s list. You can view previous lists like this here.

Adika.com $59,999 – Adika is a clothing company.

Dossier.com $27,000 – Dossier Solutions, an international consultancy group focused on aviation, healthcare and government sectors.

GoGoCasino.com £15,000 – The updated Whois record shows LeoVegas Gaming LTD.

Luminaires.fr €10,000 – As the name indicates, this is now being used by a French lamp and lighting online supplier.

SoBlue.com $7,000 – Blue Solar, a solar energy provider out of Australia.

FlashScore.com.mx $6,100 – Forwards to Flashscore.com, an online international sporting event scores forum.

BeePlus.com $6,000 – Bee+ is a China-based lifestyle brand with co-working Spaces.

JavaHouse.de €6,000 – This domain forwards to the European page of JavaHouse.com, a U.S.-based Coldbrew coffee company.

SupportX.com $5,010 – A data center lifecycle management company out of California bought this domain under the company’s moniker.

Smudge.com £4,140 – An app builder called Smudge got a heck of a deal on this domain name.

MyVessel.com $3,999 – This site is currently in development but is for some sort of affordable housing company. The name suggests it will be micro housing or prefab. Whois shows the new owner is Delano Corona Holdings.

Aviaro.com €3,500 – Bought by a Voice Over IP calling solutions provider that focuses on supporting call centers and other businesses in the U.S.

SwissHealthcare.com €3,000 – This domain is still not resolving but was purchased by Swiss Dental Services, which can be found under several listings including Portugal and the UK when searched for on Google.

Pellerano.com $3,000 – Pellerano Nadal Law & Consulting in the Dominican Republic.

Shopify.no $2,600 – I assume that the ecommerce company bought this domain.

Taesang.com $2,000 – Korean based manufacturer of products for wind and nuclear power plants as well as products for the shipbuilding industry. It now owns the .com version of its domain and already operates several different language sites.

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

Related posts:
  1. Forward U.S. bought domain for $1,500
  2. These end users just bought domain names
  3. End user domain name sales up to $90,000
Categories: Domains

CEAT tire company fabricated evidence, panel determines

Domain Name Wire - Wed, 01/23/2019 - 15:26

Panel says that tire company submitted “clearly fabricated” evidence.

The only way to get ads for tires on this page is to enter a tire search term.

Indian tire company CEAT (short for Cavi Elettrici e Affini Torino) has been found to have engaged in reverse domain name hijacking over the domain name CEATE.com.

The company owns the domain CEAT.com, which it won in a 2011 UDRP filing. There was one dissenting panelist in that case, Neil Anthony Brown. Brown was one of the panelists in the case for CEATE.com as well.

According to the World Intellectual Property Organization decision, CEAT manufactured evidence suggesting that the parked domain at CEATE.com showed ads for tires. It did this by entering “ceat tyre company” in the search box on the parked domain.

The three-person panel found that “Complainant’s screenshots showing use the disputed domain name in connection with the Complainant’s trademark submitted as Annex 2 to the Complaint have been clearly fabricated in an attempt to create evidence of the Respondent’s bad faith.”

It found that CEAT engaged in reverse domain name hijacking.

CEAT was represented by DePenning & DePenning, which has represented a client in a reverse domain name hijacking case before. The domain owner was represented by Zak Muscovitch.

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

Related posts:
  1. Fertilizer company tries reverse domain name hijacking
  2. MomAndMe.com spared in UDRP. Should have been RDNH?
  3. Zak Muscovitch gets reverse domain name hijacking win
Categories: Domains

Scratch Foundation files lawsuit against Scratch.org

Domain Name Wire - Wed, 01/23/2019 - 14:03

Unhappy with asking price for domain, kids entertainment website files cybersquatting lawsuit.

Lawsuit claims this page is infringing the rights of an online games site.

Scratch Foundation, a non-profit that started at MIT, has filed an in rem lawsuit (pdf) against the domain name Scratch.org claiming that the domain is cybersquatting.

The foundation uses the domain names scratch.mit.edu and scratchfoundation.org. Each site contains different content and the latter domain was registered in 2015.

Scratch Foundation reached out to the owner of the domain name in 2015 and offered under $5,000 for the name. According to the complaint, the owner asked for $450,000 and shortly thereafter started showing ads related to credit repair.

The plaintiff says it then offered $10,000 in 2017 and the owner responded asking $650k. It claims that the owner is trying to sell the domain for over 700 times the domain’s appraised value (using estibot’s automated valuation). Note that the plaintiff reached out to the domain owner to inquire about buying the domain, not the other way around.

So how is the owner of Scratch.org using the domain to infringe on the foundation’s trademark? I can’t find any evidence that it is. The lawsuit states:

…the registrant of the Defendant Domain Name may possess an intention to divert consumers from Scratch Foundation’s online locations to a site accessible under the Defendant Domain Name that could harm the goodwill represented by the SCRATCH mark…

…the registrant of the Defendant Domain Name could configure the Defendant domain name to confuse and/or deceive young children…

Note the use of ‘may’ and ‘could’. In other words, there’s no infringement right now. ‘May’ and ‘could’ could be used for just about any valuable one-word domain name to suggest infringement.

The lawsuit also says that, upon information and belief, the registrant provided false contact information when registering the domain name. The very next paragraph says the registrant is unknown because it is protected under privacy.

Scratch Foundation says it is unable to figure out who owns the domain because is protected by Whois privacy. I’m curious how it communicated with the owner of the domain name to make its purchase offers. That communication is not included as an exhibit to the lawsuit, which is odd given that it’s central to the plaintiff’s claims.

Furthermore, at least as of today, there is a phone number and email address on the Scratch.org landing page. I’m not sure if this is for the domain owner or a technical provider.

Nevertheless, it’s clear that the plaintiff was somehow able to communicate with the owner previously.

David Weslow of Wiley Rein is representing the plaintiff. Weslow traditionally represents domain theft victims as well as victims of reverse domain name hijacking. Yet this is a case that could very well be considered reverse domain name hijacking, at least under UDRP rules. Weslow also defended grandma Heidi Powell pro bono. He is also representing the owner of AddictingGames.com in a case filed against the owner of Addicting.com. At least in that case there’s evidence on infringement. While attorneys are free to represent “both sides”, it seems that some of the arguments in this case will contradict defenses made by domain owners in other cases, such as their ability to charge whatever they want for a domain name.

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

Related posts:
  1. Donuts challenges .Charity decision
  2. Canadian firm Obero tries to Reverse Domain Name Hijack domain name
  3. Innovation HQ asks USPTO to cancel “Weeds” trademarks
Categories: Domains

Company says using the word “collusion” in a domain is cybersquatting

Domain Name Wire - Wed, 01/23/2019 - 01:53

Another facepalm moment for law firm Stobbs IP.

A better message would be “Action required. We should review our cases before sending a C&D.”

The Electronic Frontier Foundation is representing the registrant of the domain name collusion.so after he received a threat letter from U.K. clothing company Asos.

The registrant bought the domain name after Rudy Guliani tweeted “#REALNEWS: Woodward says no evidence of collusion.So does Manafort’s team.”

Because Guliani omitted a space, twitter viewed collusion.so as a domain name and linked to it. .So is the country code for Somalia.

The domain registrant forwarded the domain to a site about possible collusion between the Trump team and Russia.

Asos launched a clothing line called Collusion late last year. Apparently, it thinks it now owns the word. It sent a cease & desist letter claiming that the owner of Collusion.so is cybersquatting.

I see lots of cease & desist letters fired off based on automated triggers without much human thought. This appears to be one of those. (At least I hope that’s the case.)

Asos is represented by Stobbs IP, a UK law firm that has the dubious honor of being on the wrong end of two reverse domain name hijacking decisions in a single day.

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

Related posts:
  1. “Domainer” and “Domain Parking” hit CNN.com home page
  2. Cybersquatting complaint filed against MicroStrategy’s Glory.com domain
  3. AddictingGames.com sues Addicting.com, claiming cybersquatting
Categories: Domains

The CloudInsure.com UDRP has a lot of open questions

Domain Name Wire - Tue, 01/22/2019 - 19:36

I’m confused after reading this UDRP decision and reviewing the domain’s details

This morning I began writing an article about a UDRP for CloudInsure.com. My general thesis was that this should have been a case of reverse domain name hijacking. Once I started investigating, I had more questions than I had answers.

According to the National Arbitration Forum decision, CyberRiskPartners, LLC filed the case against Drew Bartkiewicz.

National Arbitration Forum Panelist M. Kelly Tillery included this timeline in the decision:

3/17/10 Domain Name First Registered
10/1/11 Complainant LLC Formed
11/14/12 Filing Date TM Application by Complainant
11/30/13 First Claimed Use of Mark by Complainant
2/3/15 Complainant TM Registration on U.S. Supplemental Register
12/17/18 Complainant Filed Complaint

I should note that the 2012 trademark filing was on an intent-to-use basis. Also, note that the registration is on the supplemental registrar.

I checked historical Whois records and verified that the current owner was the 2010 registrant.

Given these facts, this UDRP was dead on arrival; the domain owner registered the domain prior to the Complainant even existing.

But things got confusing when I went to view CyberRiskPartners’ website.

CyberRiskPartner’s website says the company is the holding company of CloudInsure.com, LLC. If you click on CloudInsure.com it forwards to CloudEnsure.org, a name that was just registered on January 8.

Additionally, the Complainant submitted marketing materials and a business card to the USPTO in 2014 that included the CloudInsure.com domain name.

And if you go back to archives of CloudInsure.com, it says it’s a subsidiary of CyberRiskPartners, LLC.

All of this would lead you to believe that the Complainant had control of the domain name at some point. But nothing in the decision alludes to this.

I reached out to both the Complainant and Respondent this morning and did not immediately hear back.

What am I missing?

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

Related posts:
  1. Anteaters Fail to Eat Ant.com
  2. Incumbents Opposed to UDRP Reform
  3. Cybersquatting complaint filed against MicroStrategy’s Glory.com domain
Categories: Domains

Radix premiums generated $1.35 million in second half of 2018

Domain Name Wire - Tue, 01/22/2019 - 14:26

Renewals account for over half of the company’s premium revenue in H2 2018.

Radix premiums generated about $1.35 million in retail revenue during the second half of 2018.

New top level domain name company Radix had a strong finish to 2018 when it comes to premium domain name sales.

The registry estimates about $1.355 million in revenue from both recurring premium fees and one-time premium fees on its portfolio of domain names. This number considers the retail prices paid.

Renewals accounted for more than half of this. 716 premium renewals generated approximately $777k. 566 new registrations generated about $415k. The company also sold 15 domains with one-time premium fees to generate $162k.

Top sales with recurring premium fees include house.store for $16,875, water.tech for $15,000 and edu.online for $10,700.

Top sales with one-time premiums include design.online for $57,500, air.space for $17,500 and king.online for $17,250.

.Online and .Tech were top sellers. Each generated over $100,000 in retail revenue.

51% of premium domains are renewed on their first anniversary and 76% after that. 41% of renewed premium domains are being used. I’m actually surprised this number isn’t higher given the high cost to renew, but keep in mind that not all premiums have high renewal fees. For example, the average price of new premium .website registrations is only $295.

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

Related posts:
  1. Radix discloses premium name data
  2. MMX drops expensive renewals on premium domain names
  3. Radix data show why registrars and registries love the premium model
Categories: Domains

Domain auction preview with Monte Cahn – DNW Podcast #220

Domain Name Wire - Mon, 01/21/2019 - 16:30

A look back at previous live domain auctions and what to expect next week in Las Vegas.

Monte Cahn joins on us this week’s podcast to preview next week’s NamesCon live domain name auction. We also discuss what he’s seeing in the domain market and what has happened to the value of certain types of domain names.

Also: DomainTools appeals, interesting data showing registrar competitiveness, and addicting lawsuit and more.

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

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

Related posts:
  1. Domain name due diligence – DNW Podcast #148
  2. Teaching the World About Domains – DNW Podcast #205
  3. Talking pork buns with Ray King – DNW Podcast #207
Categories: Domains

Prince’s estate settles Prince.com fight with Domain Capital

Domain Name Wire - Sun, 01/20/2019 - 15:49

Redacted settlement gives hint that estate will get domain as part of the settlement.

The Estate of Prince Rogers Nelson has settled a legal battle with Domain Capital over ownership of the Prince.com domain name.

The estate sued Domain Capital saying that it was cybersquatting by owning Prince.com. Domain Capital countersued for reverse domain name hijacking and requested that the Prince trademark be canceled.

On June 11, the estate filed a planned settlement agreement in the probate court in Carver County, Minnesota. It’s heavily redacted and does not publicly display terms of the agreement. However, it mentions that there’s an escrow agreement involved. This suggests that the likely outcome is Domain Capital will transfer the domain to the estate and drop its counterclaims in return for a cash settlement.

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

Related posts:
  1. Domain Capital goes after Prince’s estate for reverse domain name hijacking
  2. Domain Capital successfully defends H.co.uk domain
  3. October’s top domain stories
Categories: Domains

How a Whois check could have halted a scam

Domain Name Wire - Fri, 01/18/2019 - 19:52

Victims failed to notice the registration date of the domain name used to initiate the scam.

Note the recent creation date on this domain used in a scam.

A Wendi Deng Murdoch imposter tricked photographers into paying for flights to and photography permits in Indonesia, and a more thorough Whois lookup could have saved the victims from losing money and time.

CNN reports about the scam that duped photographers Henry Wu and Carley Rudd. I must say, it’s much more elaborate than most scams that land in your inbox. It was well-researched and thought out.

The photographers were tricked into flying to Indonesia and buying photography permits for a gig. They later found out it was a scam and pointed out that they overlooked something obvious. The emails they received were from the domain wendimurdoch.com. That led credibility to the scam, but it turns out the domain was registered only recently:

Wu told CNN, “we overlooked the red flags. I did a DNS (search) on the (wendimurdoch.com) domain, overlooked that it had been registered a couple of weeks previously.”

(Hat tip: Name Ninja)

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

Related posts:
  1. Sean Spicer brings more attention to Whois privacy
  2. #5 in 2017: The Chinese trademark scam
  3. June’s top DNW stories
Categories: Domains

Gene therapy company tries reverse domain name hijacking

Domain Name Wire - Fri, 01/18/2019 - 15:05

Company went after domain name used by Houston medical practice.

This Houston medical practice is clearly not cybersquatting on a gene therapy company.

Gene therapy company Regenxbio Inc. tried to reverse domain name hijack the domain name RegenXHealth.com, a National Arbitration Forum panel has found.

RegenXHealth.com is used by a Houston men’s health medical practice.

The two companies have been battling over trademarks at the U.S. Patent and Trademark Office, a fact that Regenxbio failed to disclose in its complaint. It’s also quite clear that the respondent has a legitimate interest in the domain–it’s not like it set up a practice in Houston with signage and branding as an elaborate cybersquatting ruse.

In finding reverse domain name hijacking, the three-member panel wrote:

The Panel concludes that the evidence supports a determination that Complainant engaged in reverse domain-name hijacking. In reaching this determination, the Panel notes that: (1) Complainant asserted that Respondent, through the use of a privacy shield is “unknown” despite ample evidence, including the pending proceedings at the PTO and access to the Respondent’s website, that Complainant knew the Respondent’s identity; (2) Complainant’s argument that the parties are competitors, insofar as they both provide medical-related services, is disingenuous at best, given the highly differentiated nature of the services; and (3) Complainant’s assertion that Respondent’s website uses and displays Complainant’s REGENXBIO mark is not supported by the evidence

In view of the above, the Panel concludes that this proceeding was brought in bad faith and warrants a finding of reverse domain-name hijacking under Rule 15(e).

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

Related posts:
  1. Frank Schilling gets RDNH win on 3 letter domain name
  2. Zak Muscovitch gets reverse domain name hijacking win
  3. Illinois property tax appeal attorney guilty of reverse domain name hijacking
Categories: Domains

Revamped team to give Topcoin a go

Domain Name Wire - Thu, 01/17/2019 - 23:00

With a full-time staff, Topcoin is ready for new life.

A new team is taking a stab at Topcoin, the cryptocurrency-based customer loyalty program for digital goods.

While some of these people have been involved for a while, the company officially announced that Josh Metnick, Michael Blend, Ammar Kubba and John Detjen are part of the team working on relaunching Topcoin. Detjen is the CEO.

Uniregistry announced last month that it was dropping support for Topcoin. It was the biggest company issuing and redeeming Topcoin, so it was a big blow to the business.

Now Topcoin is doubling down.

“Topcoin has never, until now, had a full-time staff,” Detjen explained. “It has always been a part-time endeavor with no resources. Now we have six people working on it, with five devs.”

The company will launch a wallet app at NamesCon. It will also have five people on site to reach out to merchant partners.

In theory, Topcoin’s 21,000+ wallet holders could be a boon to companies that accept Topcoin. But they’ll need to offer meaningful redemption of the cryptocurrency.

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

Related posts:
  1. Topcoin plans ICO with goal of being loyalty program for digital goods
Categories: Domains

VPN.com owner launches domain brokerage

Domain Name Wire - Thu, 01/17/2019 - 20:59

He spent $1 million on VPN.com. Now he wants to help other people sell domains.

When it comes to the power of good domain names, Michael Gargiulo puts his money where his mouth is.

Gargiulo bought VPN.com for close to $1 million in 2017 to launch a VPN comparison site. Since then he has been singing the praises of category-killer domain names through a Forbes column and other marketing.

Now he’s teaming up with Sharjil Saleem to launch a domain brokerage. Saleem has brokered a lot of top sales including ETH.com for $2 million.

Gargiulo has ambitious plans for 2019 and vows to broker over $25 million of domains this year.

While the domain brokerage field is crowded, it will be interesting to see if Gargiulo’s experience as a premium domain buyer helps convince other buyers about the value of great domain names.

You can listen to Gargiulo on DNW Podcast #176.

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

Related posts:
  1. VPN.com buyer wants to be the Hotels.com of VPN services
Categories: Domains

DomainTools appeals injunction decision in .NZ case

Domain Name Wire - Thu, 01/17/2019 - 17:51

Cyber security service wants injunction thrown out.

Whois data and security service DomainTools has appealed a preliminary injunction brought against it by .NZ registry Domain Name Commission Limited (DNCL).

DNCL sued DomainTools in June 2018 over DomainTools’ collection and publication of .NZ Whois data. It argued that DomainTools’ actions violated DNCL’s terms of service, which are provided with each Port 43 Whois query result.

A Federal District judge granted an injunction that ordered DomainTools to not collect any more .NZ Whois records and to remove any previously published records while the lawsuit proceeded.

DomainTools appealed the decision to the Ninth Circuit Court of Appeals.

In its opening brief (pdf), DomainTools argues that DNCL’s terms of service were not binding on DomainTools because of how the terms of service were published. Including the terms with each Whois result is considered a “browsewrap” agreement; the other party does not check a box or make any other affirmative action to agree to the terms.

DomainTools notes that “The lower court acknowledged that so-called “browsewrap” agreements like DNCL’s terms of use are not enforceable unless “the user has actual or constructive knowledge of the [terms of use].” In the court’s view, however, DomainTools’ repeat queries established sufficient knowledge.”

The company says that the lower court’s view should not apply because all of DomainTools’ Whois queries were “conducted by an automated program on a dedicated computer-to-computer channel acting without human intervention.”

It also says that the terms were written in a way that didn’t suggest that DomainTools’ use of the data violated the terms.

DomainTools wants the court to weigh the negative impact to DomainTools’ customers against the impact on .NZ registrants whose information is published.

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

Related posts:
  1. New Zealand’s .Nz namespace gets preliminary injuction against DomainTools
  2. $50,000 penalty for filing a frivolous UDRP!
  3. Domainers: What you need to do NOW to prepare for GDPR
Categories: Domains

Does this domain registration drop a hint about A Quiet Place 2?

Domain Name Wire - Thu, 01/17/2019 - 14:43

Paramount makes an odd domain registration for A Quiet Place.

Is the sequel to A Quiet Place really a prequel?

One of last year’s biggest movie hits was A Quiet Place, which follows a family surviving after aliens invade earth.

A sequel is definitely on tap, but it might not be a sequel in a traditional sense. One idea based on director John Krasinski’s recent comments on a podcast is that it will follow other people surviving post-invasion.

But Paramount Pictures made an odd domain name registration today that got me thinking. The company registered 2aQuietPlaceMovie.com.

This is kind of weird. Wouldn’t it be AQuietPlaceMovie2.com?

That domain isn’t registered. Why put the 2 in front?

One idea is that the 2 is a play on ‘to’, and the sequel will actually be a prequel. The first movie picks up well after the invasion, and there’s a big storyline before the first movie even begins.

While I like this idea, I should note that ToAQuietPlaceMovie.com isn’t registered, and I’d think the studio would want this domain if ‘2’ really is a play on ‘to’. Of course, since this domain registration is so fresh, they could just be getting around to it now.

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

No related posts.

Categories: Domains

My favorite domain names in the NamesCon auction

Domain Name Wire - Wed, 01/16/2019 - 19:01

These are some of the most compelling names in the auction (for the price).

This year’s NamesCon live domain name auction is less than two weeks away. Prebidding is already underway with many domains already at 10+ bids.

Most of the names in the auction have a reserve. So far, the most expensive domain to meet its reserve is Multiplexer.com at $2,100.

I reviewed the list to find my favorite domains at the reserve range. There are obviously better names in the auction than many of the ones I selected, but given the reserve ranges, these are the ones I find most compelling.

Give.com (reserve > $1 million) – This domain sold for $500k in 2015. It reminds me a bit of Great.com and Super.com, which sold last year for about a million dollars each. Depending on how high over a million this domain is, it has good potential.

Lucky.com (> $1 million) – Between Lucky.io selling for $67k on park.io a few months ago, online gambling, and brands that use this name, it’s a winner.

Piano.com ($400k-$500k) – I’m thinking more as a brand than as an instrument site.

Document.com ($300k-$400k) – Files.com just sold for $750k. Document.com has more uses.

Athlete.com ($200k-$300k) – I’m including this one because it sold for $122k in the 2008 TRAFFIC auction. I’m curious if it can fetch near that amount ten years later.

Leukemia.com ($100k-$200k) – I realize this is difficult to spell but probably not for people who are fighting this horrible cancer. Health Union bought the .net last year for $9k. They build lots of sites on .net, but it might be worth spending a bit more for the .com in this case. Otherwise, perhaps a charity or drug maker can use this domain.

Adverbs.com ($5k-$10k) – I like this as a brand, but would prefer the singular version. The domain sold for $1,800 in 2011.

Bullied.com ($5k-$10k) – Perfect for a bully prevention organization or help group. This domain sold for $3,400 in 2007.

Wipeout.com ($5k-$10k) – I don’t know what you’d use it for…maybe a game? Even though it has a negative connotation, I think it’s a fun name for the right site.

The auction takes place January 28, 2019 at the Tropicana Hotel in Las Vegas and online. It is presented by Right of the Dot in conjunction with NameJet.

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

Related posts:
  1. NamesCon auction was a coming out party for new TLDs
  2. These domains have met their reserves for next week’s NamesCon auction
  3. My Thoughts on Today’s Rick Latona Auction
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.