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.

Talking UDRP with Gerald Levine – DNW Podcast #201

Domain Name Wire - Mon, 09/10/2018 - 15:30

The author of a book about UDRP discusses cybersquattind dispute trends.

Gerald Levine literally wrote the book on UDRP. His book Domain Name Arbitration is the bible for domain name lawyers. On today’s show, Levine discusses some of the trends he’s seeing in UDRP cybersquatting disputes.

Also: Abry gobbles up Donuts, Namecheap hits 10 million, CentralNic’s purchase, and Google says URLs suck.

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

Related posts:
  1. How to avoid UDRP – John Berryhill – DNW Podcast #170
  2. The challenges of new TLDs with Tobias Sattler – DNW Podcast #177
  3. Sandeep Ramchandani, CEO of Radix – DNW Podcast #183
Categories: Domains

NameJet sales in August up to $57,000

Domain Name Wire - Mon, 09/10/2018 - 14:38

A slow month but some solid sales at NameJet.

August is generally a slow month for domain sales, and that showed at NameJet. The company had 69 sales of $2,000 or more, totaling $339,000. Here are some of the sales that caught my attention:

AMZ.com $57,000 – This non-expiry sale was obviously aided by the similarity to Amazon.com, but it doesn’t seem that Amazon bought the domain.

YouCar.com $9,100 – This used to be part of YouTravel.com.

Genitalherpes.com $7,027 – Names that drug companies can buy are usually good bets.

AutoLife.com $5,647 – This domain can have two meanings; one with life being a generic modifier for a site about cars, the other is auto and life insurance.

Stylism.com $2,800 – I like this name for a clothing seller or style blog.

CustomPrints.com $2,795 – A solid name for customized photo products or designs.

GreatPyramid.com $2,050 – Makes me feel a bit better about EgyptianPyramids.com.

Here’s the full list of NameJet sales over $2,000 last month:

Domain NamePayment Amount amz.com57000 dpn.com32200 xr.net19532 Youcar.com9100 fu8.com8200 genitalherpes.com7027 fede.com6500 hunchback.com6201 autolife.com5647 05c.com5610 ihea.com5200 dure.com5101 plead.com5100 walletshop.com4999 anonymouse.com4800 sexedlibrary.org4600 bathroomfurniture.com4420 cavanagh.com4256 sovak.com4201 w29.com4111 exceltraining.com4100 hillier.com4035 ramped.com3999 b2b.net3800 arabchat.com3700 filk.com3650 parktronic.com3600 dietsupplements.com3360 shitao.com3311 gaojin.com3310 earthfoods.com3190 twox.com3100 asano.com3069 purx.com3000 d82.com2911 t82.com2911 bestex.com2888 alphacity.com2808 stylism.com2800 customprints.com2795 anvis.com2756 bitcoinbuyer.com2655 spin.org2650 infobeat.com2600 meldium.com2600 prbuzz.com2600 xave.com2600 payrollloans.com2599 paax.com2559 watchxxx.com2513 juif.com2501 ultracell.com2501 jaqu.com2401 trackbikes.com2390 marketrate.com2350 coldplanet.com2322 multivision.com2322 mainway.com2322 internalization.com2300 dweebs.com2300 halifax.net2296 irba.com2241 mmorpg.net2222 ranwen.com2099 greatpyramid.com2050 racingpicks.com2036 chugg.com2012 275678.com2009 casabranca.com2000

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

Related posts:
  1. What domain names to buy this week
  2. NameJet sellers at center of shill bidding questions
  3. Here’s what NameJet is doing about shill bidding
Categories: Domains

Spamhaus chimes in on spam-after-GDPR claims

Domain Name Wire - Sat, 09/08/2018 - 19:26

Group says there could be many reasons spam hasn’t increased after GDPR.

Yes, spam is down since the date GDPR caused Whois records to go dark. But anti-spam group Spamhaus says there are many possible reasons for this, and not having Whois information is hampering its efforts.

The back story is this: anti-spam and internet security groups cautioned that domain name registrars hiding Whois information because of the EU’s General Data Protection Regulation could lead to more spam. Since the GDPR went into effect in May, however, spam volumes have actually gone down.

This has led some people to suggest that claims about the impact of hidden Whois records on spam were overblown.

In a blog post, Spamhaus says there are a number of possible reasons spam has dropped since Whois went dark:

1. Legitimate companies have purged their email lists to become GDPR compliant so there’s less “legit” spam.
2. Fewer domains are being flagged as spam because of no access to Whois data; anti-spam systems are flagging less spam as spam.
3. The natural ebb and flow of spam volumes.
4. Bad actors focusing on other types of illegal activity.
5. Few new top level domain specials, so domains are more expensive for spammers to churn through.

The organization says that it’s too early to draw any conclusions. But it also notes that a lack of Whois info is hurting its efforts to connect the dots between domains and spammers.

Spamhaus is a member of Coalition for a Secure and Transparent Internet, a group advocating for public Whois.

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

Related posts:
  1. How to reduce comment spam on your WordPress website
  2. How to import your Whois data into Watch My Domains
Categories: Domains

August’s top domain name stories

Domain Name Wire - Fri, 09/07/2018 - 14:04

Here’s a look back at August on Domain Name Wire. These were the top stories ranked by number of page views:

1. Betsy Riot trolls NRA Lobbyist’s wife with domain name – Anti-NRA gun control advocates successfully defended a domain name in a UDRP that they used to troll an NRA lobbyist’s wife.

2. Living as a Digital Nomad for a month – Many domain investors can live and work from anywhere. Here was my experience setting up camp in Seattle for a month.

3. California.com sells as part of big domain name transaction – The seven-figure transaction included 10 domain names.

4. Allstate is no longer in .GoodHands – Allstate is giving up its .goodhands new top level domain name.

5. Former NFL player Shawne Merriman wanted LightsOut.com, but panelist disagreed – His clothing company tried to get a domain name through UDRP.

And here are links to the three DNW Podcasts published during the month:

#199 – Crowdsourcing (domain) name selection – listen
#198 – New TLD Economics with Colin Campbell – listen
#197 – Top Domain Sales of the Year – listen

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

Related posts:
  1. Living as a Digital Nomad for a month
  2. Former NFL player Shawne Merriman wanted LightsOut.com, but panelist disagreed
Categories: Domains

ICANN surveys domain registrants about trademark claims notices

Domain Name Wire - Fri, 09/07/2018 - 13:14

Survey is well-intentioned but is unlikely to provide good data.

ICANN is requesting feedback from domain name registrants about trademark claims notices from the Trademark Clearinghouse.

Domain name investors that registered new top level domain names are probably familiar with these notices. When you try to register a domain that matches a trademark in the database, you are presented with a notice that your registration might violate a trademark owner’s rights.

The notices don’t prevent you from registering the domain, but they certainly have a chilling effect on people trying to register the domain.

This is despite many of the notices not applying to the use for which the person wants to register the domain. Many of the trademarks are for common or dictionary words such as Texas and fire, and marks registered to game the system such as wedding, money and realestate.

The survey’s goal is to understand how domain registrants responded to the notices and their impact on registrations. The survey’s questions are dead on, but there’s a big problem with the survey: the typical person that tried to register a domain and saw the notice will be unaware of the survey. Even if they are aware, they won’t spend 15 minutes answering questions.

I suspect anecdotal evidence and data from the Trademark Clearinghouse is going to be more valuable than this survey. For example, there was the tech-savvy friend of mine who tried to pre-register a .app domain. He told me “Yeah, I tried to get that one, but there’s some sort of trademark thing on it.” He ditched the registration.

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

Related posts:
  1. How common words like Pizza, Money, and Shopping ended up in the Trademark Clearinghouse for new TLDs
  2. ICANN Extends Public Comment Period for New TLD Guidebook
  3. Four new top level domain name contracts signed
Categories: Domains

More companies should emulate Tucows’ new earnings call format

Domain Name Wire - Thu, 09/06/2018 - 17:11

Format leads to higher quality questions and answers.

Last month Tucows (NASDAQ: TCX) held an unusual earnings conference call. Rather than a live call with analysts asking questions, the company pre-recorded the prepared remarks portion of the call. It then invited analysts and shareholders to submit questions in writing, to which Tucows would respond.

I wrote about the reasons for this last month. Now, I can unequivocally support this model. More companies should do it.

Take a look at the quality of both the questions and answers (pdf).

Noticeably absent are questions with answers already in the financials that analysts just needed a few more minutes to locate.

I’m a bit baffled that no analysts asked about the domain business, but I suppose they view the upside in the Ting mobile and fiber business.

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

Related posts:
  1. Tucows changes domain name price structure
  2. Tucows revenue jumps on Enom acquisition
  3. Digging into Tucows’ annual report
Categories: Domains

Domains used by China’s Top 100 internet companies

Domain Name Wire - Thu, 09/06/2018 - 16:40

Studying these domains will help you understand what types of domains China’s biggest internet companies prefer.

Researching domains used by top Chinese internet companies.

Spectacular domain sales to China have been reported in recent years, and many of them were bought by internet companies, such as 360.com for $17m, JD.com for $5m, and Mi.com for $3.6m. This should not surprise domain investors because internet companies are the new leaders in this internet age.

With China poised to become the largest domain market supported by its 800 million internet population, studying domains used by the best internet companies in China will help investors understand what domains to sell to this market. The opportunity came recently when the “2018 Top 100 Chinese Internet Companies Report (2018年中国互联网企业100强分析报告)” was jointly published by the Internet Society of China and MIIT in July. Based on the report and with help from Baidu search, I have created the following list.

RankChineseEnglishFoundedDomain 1阿里巴巴Alibaba1999Alibaba.com 2腾讯Tencent1998Tencent.com 3百度Baidu2000Baidu.com 4京东Jing Dong1998JD.com 5网易Netease1997Netease.com 6新浪Sina1998Sina.com 7搜狐Sohu1998Sohu.com 8美团Meituan2010Meituan.com 9三六零(奇虎360)360 Total Security1992360.com 10小米Xiaomi2010Mi.com 11今日头条(字节跳动)Toutiao2012Toutiao.com 12网宿Wangsu2002Wangsu.com 1358集团58.com200558.com 14金山软件Kingsoft 1988Kingsoft.com 15携程Ctrip1999Ctrip.com 16二三四五2345.com20112345.com 17美图Meitu2011Meitu.com 18新华网Xinhua Net1997Xinhuanet.com 19苏宁Suning1990Suning.com 20汽车之家(北京车之家)Autohome2005Autohome.com 21用友网络Yon You1988Yonyou.com 22咪咕文化Migu2014Migu.cn 23三七互娱37 Games201137.com 24凤凰网(天盈九州)Phoenix 2000iFeng.com 25恺英网络Kingnet2008Kingnet.com 26东方明珠Oriental Pearl Group 1991OPG.cn 27昆仑万维Kunlun2011Kunlun.com 28多玩(华多)Duowan2005Duowan.com 29易 车 网Yiche2000Yiche.com 30快 乐 阳光(芒果 TV)Mango TV2006MGTV.com 31鹏博士Dr Peng1985Drpeng.com.cn 32唯品会 Vipshop2008VIP.com 33央视网China Central Television1996CCTV.com 34四三九九(4399)439920024399.com 35凡普金科Finup2016Finupgroup.com 36网龙网络NetDragon Websoft 1999NetDragon.com 37波克城市Poker City2010Pook.com 38米哈游Mi Ha You2014Mihayo.com 39朗玛信息Longmaster2010Longmaster.com 40幻电(哔哩哔哩)Bilibili2014Bilibili.com 41巨人网络Giant Network2004Ga-me.com 42猎豹移动Cheetah Mobile2010CheetahMobile.com 43同程旅游LY.com2004LY.com 44龙采科技Long Cai2004Longcai.com 45科大讯飞Iflytek 1999iflytek.com 4621CN(世纪龙信息)21CN199921CN.com 47泰一指尚Taiyitech2012Taiyiplus.com 48光环新网Sinnet1999Sinnet.com.cn 49竞技世界网络JJWorld 2007JJ.cn 50东方财富Eastmoney.com2005Eastmoney.com 51游族网络You Zu2009Youzu.com 52斗鱼网络Douyu2015Douyu.com 53宜人贷Yirendai2012Yirendai.com 54中钢网Zhong Gang Wang2009ZGW.com 55东软集团Neusoft1991Neusoft.com 56慧聪Hui Cong1992HC360.com 57马鞍山百助Bai Zhu2006BZ.cn 58腾邦国际Tempus1998Tempus.com 59迅雷网络Xunlei2003Xunlei.com 60吉比特G-bits2004G-bits.com 61微贷网Wei Dai Wang2011Weidai.com.cn 62连尚网络Lian Shang2013Wifi.com 63钢银网Banksteel.com2008Banksteel.com 64前程无忧(前锦网络)Qian Cheng Wu You200051job.com 65找钢网Zhao Gang Wang2012Zhaogang.com 66花椒直播 (密境和风)Hua Jiao2014Huajiao.com 67好未来TAL 2003100tal.com 68蜗牛数字Wo Niu (Snail)2000Woniu.com 69游龙网络You Long Wang Luo2012YLWL.cn 70六间房6Rooms20066.cn 71东方网Eastday.com2000Eastday.com 72房天下(搜房科技)Fang2006Fang.com 73艾德Adsage2007Adsage.com 74岚悦科技Lan Yue Ke Ji2013Lanyuekeji.cn 75华云数据Hua Yun2013Huayun.com 76联动优势UMFintech2003Umpay.com 76OFO小黄车(东峡大通)OFO2016OFO.com 78途牛Tu Niu2006Tuniu.com 79创梦天地(乐逗游戏)idreamsky2011idreamsky.com 80思贝克Spek2012Spek.com.cn 81盛天网络Sheng Tian2009Shengtian.com 82梦网科技Montnets2001Montnets.com 83猪八戒网Zhu Ba Jie2006ZBJ.com 84平治信息Anysoft2002Anysoft.cn 85驴妈妈(景域)Lv Ma Ma2007Lvmama.com 86当当网Dang Dang1997Dangdang.com 87趣丸网络Qu Wan201452tt.com 88拓维信息Talkweb1996Talkweb.com.cn 89世纪佳缘Jia Yuan2003Jiayuan.com 90房多多Fang Duo Duo2011Fangdd.com 91天鸽互动Tian Ge2008Tiange.com 92创蓝253Chuang Lan 2532011253.com 93爱酷游Ai Ku You2009le4.com 94不锈钢电子交易中心Exbxg2006Exbxg.com 95沪江网校Hu Jiang2009Hujiang.com 96锐之旗Rui Zhi Qi2013Ruizhiqi.com 97风行网Fung Xing Wan2005Fun.tv 98美柚Mei You2013Meiyou.com 99世纪互联Shi Ji Hu Lian199621vianet.com 100优刻得Ucloud2012Ucloud.cn

First of all, .com is king in China. 86% of the companies use .com and only 13% use .cn. The only non-mainstream extension found is .tv. Also, short domains are preferred as 99% of the domains are 10 characters or less excluding the extension (the median is only 6 characters). So, if you want to sell to corporate users in China, focus on short .com domains.

This study breaks the myth that Chinese companies prefer Pinyin but not English domains. In the list, Pinyin domains account for only 37% of the domains and English domains take up 36%. Here, I’m using the term “English” loosely and treat names such as CTrip, iflytek, and OFO as English. (Acronym has 10% and numeric 7%.)

If you want to sell to corporate users in China, focus on short .com domains of less than 10 characters.Click To Tweet

Digging deeper, 78% of Pinyin domains are 2-pin (two Pinyin words such as Bai Du). This implies that if you want to invest in Pinyin domains, focus on 2-pin names. For acronym and numeric domain investors, note that no company on this list uses a domain longer than 4L or 4N. This means you have less chance to sell to corporate China if your have 5L/5N or longer domains.

Even though this list contains the best internet companies in China, there are still many of them not following the norm held by global brands of owning brand-matching .com domains. There are issues in brand matching (e.g. Ga-me.com), use of subdomain (e.g. Drpeng.com.cn), and misspelling (e.g. Mihayo.com). This offers great selling opportunities of the right domains.

In summary, if you want to sell to corporate users in China, focus on short .com domains of less than 10 characters excluding the extension. Both Pinyin and English names are fine. For acronym and numeric domains, try not to exceed 4L or 4N.

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

Related posts:
  1. Why you shouldn’t go bananas over Banana.com domain name “sale”
  2. China has been a blessing. Will it be curse?
  3. What China giveth, China can taketh away
Categories: Domains

10 more end user domain names sales

Domain Name Wire - Thu, 09/06/2018 - 14:15

An eCommerce company, virtual reality blog, and investment exchange bought domains last week.

This week’s end user domain buyers run the gamut but feature several travel-related businesses as well as a perfume and beauty products online shop, and a few tech businesses. The top sale at nearly €16,000 went to a universal shopping basket service called Cloud Basket where users can use one account to buy from different websites.

Take a look at some of the end user sales at Sedo this past week, and you can view previous weeks’ lists here.

CloudBasket.com €15,890- Already online and operating as a universal shopping basket service where you can buy from different online shops using one account. The buyer is Q.One Technologies GmbH.

Fragrance.mx – $9,999 Purchased by the owner of Fragrance.com & Fragrance.net. Fragrance.net sells discounted perfumes and cologne along with skincare, makeup and more.

Stak.co €5,000 – A .co name makes the list as this site redirects to pupil.co, which claims to be spatial technology company “capturing and publishing 3D information about real-world interiors on an industrial scale.” So maybe Stak will be a side project or additional product offering.

PersonalWissen.de €4,000 – Translating to Human Resources Knowledge, this site forwards to www.vnrag.de which claims to be one of the ten biggest specialist publishing houses in Germany.

Ektor.com $4,000 – Showing a “Coming Soon” sign and was purchased by Maco Lighting Pty Ltd, an Australian lighting company.

VRHuman.com $3,888 – A virtual/augmented reality blog.

Bonds.de €3,500- Currently up and running as an investment portal where members can interact with other people interested/working with bonds.

Top10Hotels.com €2,999 – Travel search engine mainly focused on hotels.

Bhutan.fr €2,499 – A landing page directing visitors to other Bhutan visitor sites so I imagine this will be a travel site for Bhutan in French.

CaribbeanFlights.com $2,150 – This is an upgrade from the hyphenated caribbean-flights.com. It forwards to the website for a private charter flight company.

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

Related posts:
  1. What domain names Mozilla and others bought last week
  2. What domain names Goldman Sachs and others bought this week
  3. More end user domain name sales
Categories: Domains

CentralNic scoops up tiny domain name registrar with focus on Romania and Brazil

Domain Name Wire - Thu, 09/06/2018 - 12:05

Company believes acquisition will give it a boost in Romania and Brazil.

Domain name company CentralNic (London AIM: CNIC) has acquired GlobeHosting Inc. for €2.56 million. €1.5 million was paid up front with anniversary payments over the next two years making up the difference.

GlobeHosting focuses on Romania and Brazil. It generated €849k in revenue for the twelve months ending July 31 and its EBITDA was €419k.

CentralNic believes the company is well positioned to benefit from changes in Romania’s .ro country code domain:

Romania’s country code, .RO, is undergoing significant adjustment from which GlobeHosting is expected to benefit, with imminent changes to its pricing structure involving all existing .RO users renewing their domains. Internet penetration in Romania is growing with an approximately four per cent increase in 2017. Currently approximately 60 per cent of Romania’s circa 20 million population uses the Internet.

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

Related posts:
  1. CentralNic is on the premium domain hamster wheel
  2. CentralNic scoops up KeyDrive for up to $55 million
  3. Shareholders approve KeyDrive acquisition; deal to close tomorrow
Categories: Domains

Defunct app maker hit with reverse domain name hijacking

Domain Name Wire - Wed, 09/05/2018 - 17:38

App maker files UDRP and then shuts down its business.

The maker of a now-defunct app called Yish has been found to have engaged in reverse domain name hijacking over the domain name Yish.com.

The company used various domain names including yishapp.com, yish.co, yish.app, yish.io and yish.menu. It understandably wanted Yish.com, but that domain was registered by Kevin Ham’s Vertical Axis back in 2001. Yish didn’t file for a trademark and began using the term until 2017.

You can understand why the panel found the app maker to have filed the case in bad faith. But this case is a bit odd: before the decision was reached, the app maker informed World Intellectual Property Organization that it was shutting down its business and asked the panel to terminate the case.

Knowing that it had a slam dunk case and likely reverse domain name hijacking, Vertical Axis (now called Blue Nova) objected to terminating the case. Therefore, the panel completed its review and found reverse domain name hijacking.

Blue Nova was represented by ESQwire.com.

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

Related posts:
  1. Reverse domain name hijacking in Hakoba Saree case
  2. Lack of disclosure leads to Reverse Domain Name Hijacking finding
  3. Crypto World Journal tries to reverse domain name hijack CWJ.com
Categories: Domains

Putting the Google Chrome URL news into perspective

Domain Name Wire - Wed, 09/05/2018 - 15:13

What impact could changes to Chrome have on domain names?

Yesterday I wrote about a WIRED story discussing the Google Chrome team’s efforts to change how it displays a site’s identity.

The reaction was pretty strong. Any threat to URLs seems like a threat to domain names.

But let’s take a step back and think more about this.

The idea is to make sure people visiting a website understand the identity of the website. Who runs it? Is it the site I intended to visit? Is it legit?

We can all agree that knowing these answers is a good thing. The question is how to convey this information, and how much of it can be conveyed in the “address bar” of a browser.

Keep in mind that there’s a difference between a URL and a domain name.

I think there’s a lot of value in seeing the entire URL string of a site I visit as it tells me a lot about the page, the section of the site, the content, and sometimes how recent the content is. I can also find other info on the site by changing the URL (e.g. removing the article name to visit a category). Importantly, I can see what sort of tracking information was appended to the URL. For example, did I just click on an affiliate link? If so, should I reconsider the suggestion the site made about buying the product?

But this might not be very valuable to other people.

It can also be difficult to show an entire long URL on a mobile browser. This might explain why Google downgraded the presence of URLs in mobile search three years ago. For example, these search results have the name of the site rather than the domain:

I don’t like this at all and think it’s a security issue. Yes, I know what CBS and The New York Times is, but I’d really like to see at least the second level domain name for “Austin Select Baseball” before visiting the site. Baseball is kind of innocuous, but what if this was a site about credit cards?

The popular @swiftonsecurity account on weighed in with these thoughts:

This is an announcement seeking input on how to move URL understandability forward in the graphical interface, which is currently stupendously dangerous and indecipherable. I’d say don’t jump to conclusions about radical changes, which have been tried before and did not work. https://t.co/MJ95D0RlUM

— InfoSec Taylor Swift (@SwiftOnSecurity) September 5, 2018

Chrome isn’t changing URLs. They’re exploring “how to display identity.” Any changes will be in canary many months before actual users see it, there’s no secret change that will just appear.

— InfoSec Taylor Swift (@SwiftOnSecurity) September 5, 2018

My takeaway is this:

1. The goals that Google says it’s trying to achieve are generally good.
2. Any deemphasis of the second level domain could hurt the importance of domain names. But the answer could be an added emphasis on this domain.
3. Google will be looking for feedback, so provide it to them.

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

Related posts:
  1. Yep, it’s 21st Century Fox
  2. Google nixing domain names in mobile search
  3. Analyzing startup domain names
Categories: Domains

Breaking: Domain name company Donuts Inc. acquired by private equity firm Abry Partners

Domain Name Wire - Wed, 09/05/2018 - 11:00

PE snaps up company that manages nearly 240 top level domain names.

Abry Partners, a private equity firm that has completed $77 billion in transactions since it was founded in 1989, is acquiring new top level domain name company Donuts, Inc. Terms of the deal and the expected closing date were not disclosed.

Donuts operates top level domain names such as .guru, .software and .life. It is the largest new top level domain name operator in terms of the number of TLDs managed with about 240 TLDs. About 4 million second-level domains using Donuts’ top level domains are registered.

The company also owns retail domain name registrar Name.com.

Donuts has raised more than $150 million from investors since it was founded in 2010 by domain industry veterans Paul Stahura, Jonathon Nevett, Richard Tindal, and Daniel Schindler. Paul Stahura was CEO until the beginning of 2017, when he became executive chairman and Bruce Jaffe took over as CEO. Since then Tindal and Schindler have left the company.

The company was one of the savviest applicants for new top level domain names. It understood early on that contention sets would likely be settled in private auctions, helping it refill its coffers by losing auctions for the new domains. Its scale has enabled it to operate profitably despite only modest demand for new TLD registrations.

The acquisition of the majority of shares in the company does not include an additional cash infusion into the company. The deal will allow some of the early investors to exit an investment they made eight years ago.

It’s not surprising that a private equity company would be interested in a business like Donuts. Donuts is essentially a subscription business with a very predictable annual renewal rate and cash flow.

Abry Partners makes communications, media, information and business services investments. Former ICANN CEO Fadi Chehadé is a partner.

This story has been edited to add additional information about Abry Partners.

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

Related posts:
  1. Donuts appoints outside director, new CFO
  2. Google open sources domain registry, Donuts collaborates as pressure on registry providers mounts
  3. Donuts chooses Rightside over Google Nomulus
Categories: Domains

Namecheap hits 10 million domains under management, Q&A with CEO Richard Kirkendall

Domain Name Wire - Wed, 09/05/2018 - 04:01

Namecheap CEO Richard Kirkendall answers questions about Namecheap as it hits a big milestone.

Namecheap CEO Richard Kirkendall

Domain name registrar Namecheap announced that it has eclipsed the 10 million domains under management milestone. This comes after being named to the Inc 5000 with $109.1 million in revenue last year. I reached out to Namecheap CEO Richard Kirkendall to ask questions about the growth, the company’s history as a reseller and what it has planned for the future.

DNW: For a long time, you were a reseller, so it wasn’t clear just how big Namecheap was. Why did you decide to move your domains under your own registrar creds?

Kirkendall: I’ll start by saying that we’ve had our own registrar backend and our own accreditation for many years now. The sole reason we had continued to work with Enom was because of the partnership we formed with them over the years, and the extremely favorable terms they gave to us to stick around.

That being said, we were under contract with them, and once that contract ran out, we decided it was time to finally branch out on our own. Being on our own allows us to use our scale and leverage our size to work out better deals, and also to form partnerships that directly affect the value we are able to deliver to our customers.

Cutting out the middleman has also allowed us to build better technology, as well as directly affect how quickly and efficiently we serve our customers. It’s been a long time coming and we are excited by the road ahead.

What role have new TLDs played in reaching 10 million domains?

Kirkendall: The new TLDs play a role, but I wouldn’t say they are the only driver to our growth. As you’ve pointed out in some of your blog posts recently, we are one of the largest registrars when it comes to legacy TLDs such as .com and .net as well. Our growth is mainly being driven by our ever-expanding customer base, and that’s what is key here.

We have millions of customers on our platform, and that number continues to expand quickly. I would say, in terms of customers for a single domain registrar, we are the second largest retail registrar in the world. Our strategy from the get-go has always been to focus on many customers with a few domains, rather than a few customers with many domains. It is this same strategy that has allowed us to quickly scale across all TLDs – as we have a wide range of customers with different needs.

(Editor’s note: Namecheap is the 5th largest registrar for .com domains and the 2nd largest for new TLDs.)

What percentage of your revenue comes from domain names compared to other services you offer?

Kirkendall: Currently, it’s about a 60/40 split but I believe that given the size of our customer base, there is a real opportunity to really grow more on the auxiliary products side of our business. We are definitely trending this way in any case.

What is the biggest challenge for Namecheap as it scales past 10 million domains under management?

Kirkendall: The biggest challenge for us, and with our current growth trajectory, will be maintaining the current level of excellent customer support we have always provided to our customers. We are investing heavily on both the technology side, as well as in our people, so I have no doubt that both will combine to rise up to the challenges ahead to meet, and even exceed, on what we deliver now.

What does the ten million milestone mean for Namecheap, and also, you personally?

Kirkendall: First and foremost, this is an opportunity to stop and say thank you to all of our customers that have chosen our company and have stuck with us through the years, because without them, we wouldn’t exist today.

For us as a company, it really is a milestone that marks a lot of hard work and dedication from the many people on our team that have contributed directly to our success by continuously focusing on the needs of our customers.

For me personally, it’s an opportunity to reflect back, and be grateful to have been able to share this journey with such a great group of people I get to call my colleagues every day, and to be able to witness firsthand the effect our company, and the products we are able to deliver has on the way our customers are able to get online and succeed.

Do you have advice or tips for success? How did you manage to grow Namecheap to be more than just a domain registrar?

Kirkendall: I know this sounds like a clichè but it really is as simple as always putting the customer first. If you’re dedicated to your customers, and wake up every day with the intent to solve their problems, you are on a direct path to success.

At Namecheap we use domains as a gateway for our customers. We understand that the first thing people do when they get an idea, or inspiration for a business (or project), is to go and register the domain name. We use this opportunity to not only deliver the domain name, but to also present them with the other tools they will need to get online and succeed.

We’ve done a fairly decent job with this up to this point, but we are only getting started. Our ultimate goal is to be the one-stop shop that delivers everything a customer needs to easily get online, and all in one place. I believe the technology and platform we are building today will deliver on this in more innovative, seamless, and meaningful ways tomorrow. There’s more to come here and this isn’t just marketing speak, so watch this space!

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

Related posts:
  1. Namecheap sues Enom and Tucows, demands transfer of 4 million domains
  2. Court orders Tucows to transfer 3.2 million domains to Namecheap
  3. Digging into Tucows’ annual report
Categories: Domains

Google Chrome team says URLs “kind of suck”, figuring out how to replace them

Domain Name Wire - Tue, 09/04/2018 - 18:40

The people behind the Chrome browser are investigating ways to replace the URL for site identity.

Are URLs a good way to understand site identity? Google’s Chrome browser team doesn’t think so, according to an article published today by WIRED.

Adrienne Porter Felt, Chrome’s engineering Manager, told the publication:

People have a really hard time understanding URLs. They’re hard to read, it’s hard to know which part of them is supposed to be trusted, and in general I don’t think URLs are working as a good way to convey site identity. So we want to move toward a place where web identity is understandable by everyone—they know who they’re talking to when they’re using a website and they can reason about whether they can trust them. But this will mean big changes in how and when Chrome displays URLs. We want to challenge how URLs should be displayed and question it as we’re figuring out the right way to convey identity.

At the same time, Parisa Tabriz, director of engineering at Chrome, said they don’t know what this will look like. But Tabriz said that whatever is proposed will be controversial. “But it’s important we do something, because everyone is unsatisfied by URLs. They kind of suck.”

Some browsers have tried to replace the URL in the past, and those efforts have been unsatisfying. The key thing is to be able to trust the site and content you are viewing. Seeing the URL helps. That’s not to say the site identity in the browser can’t be different than a URL, but you can learn a lot by viewing the full URL of a page. Some previous efforts are akin to just showing a site name, which can be spoofed or copied.

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

Related posts:
  1. Google is now part of Alphabet, uses ABC.xyz
  2. How to invest in domain names through an IRA or 401(k)
  3. .Boston domain names enter general availability today
Categories: Domains

Selling social media handles – DNW Podcast #200

Domain Name Wire - Tue, 09/04/2018 - 15:30

Learn about buying and selling social media handles on episode #200 of the DNW Podcast.

It’s the 200th episode of the DNW Podcast!

To celebrate, I’m bringing on one of my most popular repeat guests, Bill Sweetman of Name Ninja. This week Bill will explain the process of buying and selling social media handles, how much they usually sell for and if there’s an opportunity to invest in them.

Also: Paging Larry.Page, Afilias comes to America, a cryptocurrency auction and a new Whois bill?

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

No related posts.

Categories: Domains

Domain name registrars and .Com, by the numbers

Domain Name Wire - Tue, 09/04/2018 - 15:07

ICANN publishes latest .com data.

ICANN has published the latest official data from Verisign (NASDAQ:VRSN) about the .com registry. This registrar-by-registrar report covers Maay 2018.

There was little change on the charts. For new registrations, NameSilo lept above West.cn for the month. On the top 10 total registrations leaderboard, Xin Net swapped places with GMO.

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

1. GoDaddy.com* 951,994 (960,904 in April)
2. HiChina Zhicheng Technology Ltd. 210,854 (246,804)
3. Tucows** 207,430 (203,219)
4. Endurance+ 136,328 (153,352)
5. NameCheap Inc. 125,428 (127,855)
6. Xin Net Technology Corporation 125,152 (113,107)
7. Web.com++ 109,876 (103,385)
8. Google Inc. 98,618 (92,671)
9. NameSilo 67,446 (62,017)
10. West.cn 61,649 (74,741)

Here’s the leaderboard of the top registrars in terms of total .com registrations as of the end of May 2018:

1. GoDaddy* 48,305,409 (48,088,605 in April)
2. Tucows** 12,875,098 (12,932,547)
3. Endurance+ 7,592,640 (7,725,154)
4. Web.com++ 6,709,055 (6,713,143)
5. HiChina 5,426,366 (5,298,573)
6. NameCheap 4,243,582 (4,222,952)
7. 1&1 3,744,506 (3,760,259)
8. Xin Net Technology Corporation 2,076,944 (2,010,000)
9. GMO 2,064,482 (2,089,800)
10. Google 1,728,215 (1,663,836)

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

* Includes GoDaddy and Wild West Domains
** Includes Tucows and Enom
+ Includes PDR, Domain.com, FastDomain and Bigrock. There are other Endurance registrars, but these are the biggest.
++ Includes Network Solutions and Register.com

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

Related posts:
  1. Kings of .Com – Registrar Analysis
  2. A strong month for .com; here are the winners & losers
  3. .Com’s Top Registrars
Categories: Domains

XYZ asks court to make Verisign lawsuit documents public

Domain Name Wire - Tue, 09/04/2018 - 13:13

Company that runs .xyz domain wants to make documents from legal battle public.

XYZ wants to make documents from long battle with Verisign pubic.

XYZ.com, LLC, the company that operates the .xyz top level domain name, has asked a court (pdf) to let it make certain documents from a lawsuit with Verisign (NASDAQ:VRSN) public.

Verisign, the registry that operates the .com and .net top level domains, sued the .xyz operator in early 2015 alleging false advertising. Basically, Verisign said XYZ inflated its success and disparaged Verisign’s domains.

After extensive discovery, a judge tossed out Verisign’s suit on summary judgment. XYZ then asked the court to require Verisign to pay its $1.6 million legal bill, but that was put on hold as Verisign appealed the lower court’s ruling to an appeals court.

The appeals court ruled against Verisign and then the lower court considered the request for fees. It denied the request other than about $57,000 in discovery fees.

XYZ appealed the court’s decision to not award legal fees and the appeal is ongoing.

On Friday, XYZ asked the court to let it make a number of documents from the original suit public. They were originally filed under seal as “attorneys eyes only”.

XYZ argues that the public has a basic right to access court documents, particularly those that are key to understanding a court’s judgments and decisions. It says the documents it wants to file publicly are key evidence in XYZ’s forthcoming renewed motion for attorney’s fees.

XYZ wants to make portions of three deposition transcripts as well as a dozen documents public. The company admits these documents might be embarrassing to Verisign, but says they do not contain “highly sensitive business and financial information”.

The transcripts include depositions of Verisign SVPs Pat Kane and Scott Schnell.

Depending on what’s in the documents, Verisign might have an interest in keeping them private due to its current negotiation with the U.S. government over the Cooperative Agreement to run .com as well as the ongoing fight over .Web.

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

Related posts:
  1. Breaking: Verisign loses appeal in .XYZ lawsuit
  2. Verisign sues CentralNic and .XYZ over .Theatre, .Protection and .Security
  3. Donuts: Verisign trying to intimidate, bully competitors with .XYZ lawsuit
Categories: Domains

Do these Jack Ryan domain name registrations make sense?

Domain Name Wire - Fri, 08/31/2018 - 15:12

Amazon Prime just released a new Prime Original series Tom Clancy’s Jack Ryan. Amazon has been promoting this on Prime Video for months.

Yesterday, the company registered these domain names:

jack-ryan-tv.com
jack-ryanseries.com
jack-ryantheseries.com
jack-ryantv.com
jackryan-tv.com
jackryantv.com
tom-clancys-jack-ryan.com
tomclancys-jackryan-tv.com
tomclancys-jackryanseries.com
tomclancys-jackryantheseries.com
tomclancys-jackryantv.com
tomclancysjackryan-tv.com
tomclancysjackryantv.com
tomclanys-jackryan.com

Amazon always makes a slew of defensive domain name registrations when it launches a new product. But some of these seem way over the top, including the typo tomclanys-jackryan.com.

Also, with Amazon promoting this new series for a long time, why register these domains just now?

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

Related posts:
  1. Google and Amazon.com backpedal on closed top level domain names
  2. Amazon.com foreshadows AWS re:Invent news with domain name registrations
  3. #8 of 2017: Brands lukewarm to dot-brand domain names
Categories: Domains

You need to hire a specialist lawyer for domain name disputes

Domain Name Wire - Fri, 08/31/2018 - 14:01

Another example of a UDRP case gone wrong that might have gone the other way with different arguments.

“Maybe we should read Gerald Levine’s book about UDRP before filing.”

Would you hire a personal injury lawyer to file a trademark application? I hope not. You should hire an attorney who specializes in trademarks.

When it comes to cybersquatting claims, it’s important to hire someone who has direct experience with the Uniform Domain Name Dispute Resolution Policy. It’s not enough to even hire an intellectual property or trademark specialist.

There’s a lot of nuance to UDRP, and if you hire someone who’s not an expert in cybersquatting, your results will vary. You’ll also likely pay that person to research stuff that other lawyers already know.

I was reminded of this in a case just decided at National Arbitration Forum. Geo Global Partners, LLC failed to win its case against Gardenique.com, and it’s possible the outcome would have been different if the case was argued differently.

The case mostly hinged on dates. The domain was registered in 1996. Geo Global Partners’ attorney tried to argue common law rights but not did make arguments sufficient enough to qualify in a UDRP case. Furthermore, even the common law rights claimed were after 1996.

Here’s the thing: based on historical Whois records at DomainTools, it appears the current owner of the domain acquired it in late 2016 or early 2017. That changes things.

Perhaps the Complainant still would have lost for other reasons. But it’s a reminder that you should hire counsel that is experienced with the type of proceedings you are filing. Someone who has filed or defended many cases and has read many more to understand the nuance of these cases.

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

Related posts:
  1. Porsche.me: Money Down the Drain
  2. Bank of America Gets Split Decision in Domain Name Dispute
  3. EA loses domain dispute for SSX.com for upcoming SSX launch
Categories: Domains

Pilot Fitness, LLC tried reverse domain name hijacking

Domain Name Wire - Fri, 08/31/2018 - 13:22

Fitness website for pilots tries to get the .net to match its .com but is found guilty of reverse domain name hijacking instead.

“Do you think we should hijack this domain name?”

Pilot Fitness, LLC, a company that helps traveling professionals stay fit, has been found to have engaged in reverse domain name hijacking over the domain name PilotFitness.net. The company uses PilotFitness.com for its website.

PilotFitness.net is owned by a pilot who teaches fitness. He has forwarded the domain name to his website since at least 2013 (based on Archive.org) and registered the domain in 2012. Pilot Fitness, LLC bought its domain name sometime later through HugeDomains.

PilotFitness, LLC has a stylized trademark for a logo “Pilot Fitness Elevate Your Health”.

Panelist Neil Anthony Brown found that the domain name was not confusing similar to this mark, and the Pilot Fitness part was descriptive.

He also determined that the Complainant didn’t even make a prima facie case against the domain name owner that he lacks rights or legitimate interests. Brown noted:

The term used is essentially generic or descriptive, being made up of two generic words with widely understood meanings over which no-one has an exclusive entitlement and they have, on the unchallenged evidence, been used by Respondent on his website within their generic meaning, namely to offer services relating to the fitness of aircraft pilots and others who may want the same standard of fitness services. Indeed, the totality of the evidence shows that it is extremely unlikely that Respondent used the words because they were in Complainant’s trademark or that he even knew of the existence of Complainant, its business or its trademark at the time he registered the domain name. After all, he registered his domain name before Complainant came into existence and, consequently, before Complainant applied for or registered its trademark.

Brown further found that the domain wasn’t registered in bad faith, primarily because the domain was registered before Pilot Fitness, LLC existed.

This is a rare trifecta reverse domain name hijacking case in which the complainant not only failed on all three elements of UDRP, but failed to even make a prima facie case on the rights or legitimate interests prong.

It’s possible this is because the Complainant wasn’t represented by counsel. Instead of listing a lawyer, the decision states that the Complainant was represented by Lauren Dils. She’s listed on the PilotFitness.com website as a personal trainer.

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

Related posts:
  1. Non-Profit Urban Logic Guilty of Reverse Domain Name Hijacking
  2. Telepathy scores $40,000 from reverse domain name hijacking case
  3. Insurance company Allianz tries reverse domain name hijacking a domain name
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.