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.

Illinois property tax appeal attorney guilty of reverse domain name hijacking

Domain Name Wire - Tue, 06/19/2018 - 14:03

Anastasia Poulopoulos filed a cybersquatting dispute in bad faith, panelist determines.

The owner of Appealmytaxes.BIZ, which offers a service to challenge property tax assessments in Illinois, has been found to have engaged in reverse domain name hijacking in an attempt to get the domain name Appealmytaxes.COM.

Anastasia Poulopoulos filed the case with National Arbitration Forum arguing that the owner of AppealMyTaxes.com was cybersquatting. The owner of AppealMyTaxes.com registered the domain name before Poulopoulos registered the matching .biz. Poulopoulous subsequently registered a figurative mark made up mostly of text that reads “WWW.APPEALMYTAXES.BIZ OUR ONLY BIZNESS IS LOWERING YOUR REAL ESTATE TAXES”.

Not surprisingly, the panel didn’t find that this trademark was confusingly similar to the domain name AppealMyTaxes.com. It also found that the domain wasn’t registered in bad faith, which was the reason panelist David L. Kreider determined that Poulopoulos had engaged in reverse domain name hijacking.

It appears to the Panel that the Complainant became aware of the Respondent’s registration on May 12, 2008 of the DDN , and within weeks, acted to register her own “appealmytaxes.biz” domain name and file an application with the USPTO on June 23, 2008 to register the trademark WWW.APPEALMYTAXES.BIZ OUR ONLY BIZNESS IS LOWERING YOUR REAL ESTATE TAXES, with the intention of competing in the same professional services business as the Respondent had launched, or at that time, appeared to be preparing to launch.

The Panel concludes that the Complainant instituted these UDRP proceedings knowing that the Respondent was prior in time in registering the DDN and that the Complainant could not possibly establish the element of bad faith registration by the Respondent, which is required under the Policy Paragraph 4(a)(iii).

The Panel finds that the Complainant has engaged in Reverse Domain Name Hijacking.

© 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. Dubai Law Firm Nailed for Reverse Domain Name Hijacking
  3. Telepathy scores $40,000 from reverse domain name hijacking case
Categories: Domains

Mugshots.com defendants face arraignment later this month

Domain Name Wire - Tue, 06/19/2018 - 12:37

Defendants are due in Los Angeles courtroom on June 29 for arraignment.

Sahar Sarid’s mugshot after being arrested in Florida. He faces arraignment in California later this month.

The defendants in a criminal case against Mugshots.com’s owners face arraignment on June 29, according to the Superior Court of California website.

Domain investor Sahar Sarid is among the four people named in the complaint. He faced extradition to California to face the charges brought by the Attorney General there. The extradition hearing in Florida was dropped, apparently after Sarid turned himself in in California.

Sarid faces 51 counts including extortion, money laundering, and identity theft. The Attorney General alleges that he and the other defendants extorted people by charging them to have their mugshot and arrest records removed from the website in violation of the law.

The Mugshots.com website does not currently resolve.

© 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. Sahar Sarid arrested on charges related to Mugshots.com
Categories: Domains

Proeza, S.A. nailed for reverse domain name hijacking for failure to disclose

Domain Name Wire - Mon, 06/18/2018 - 16:11

In a common occurence, company fails to disclose prior corresondence and misleads panel.

Here’s a common pattern in cybersquatting disputes under the UDRP:

A company reaches out to the domain name owner in an effort to either buy the domain or coerce the domain owner into transferring it on the threat of legal action. The domain owner responds and explains why he or she is not cybersquatting, and the complainant lets the matter lie. Then, out of the blue many years later, the complainant files a UDRP and doesn’t mention the prior correspondence between the parties.

Sometimes this is because the people responsible for filing the case weren’t knowledgeable about the prior attempts. Sometimes they were and thought they could slip it by.

In fact, some companies leave out key information or even try to mislead a panel with the hopes that the domain owner won’t respond, so no one will call it on its malfeasance and the domain will be transferred.

That’s what appears to have been the goal in a case Mexican company Proeza, S.A. filed against the French owner of Proeza.com.

An IT admin at Proeza tried to buy the domain in 2011 and the owner, who uses the domain for email, declined to sell. Then an outside lawyer for Proeza threatened the domain owner in 2012. Proeza seemed to drop the issue when the domain owner clearly explained why it wasn’t a case of cybersquatting.

When Proeza filed its case, it didn’t mention any of the prior communication. When the inside counsel for Proeza referred the UDRP matter to another outside counsel, it’s feasible that he didn’t know about the IT admin’s overture, but he clearly knew about the previous threat communications from prior outside counsel. Here’s what the World Intellectual Property Organization panel wrote about this lack of disclosure:

With this information and with a minimal review of the prevailing standards under the Policy as reflected in panel decisions, it should have been obvious to Complainant at that time that a claim under the Policy would be a dubious pursuit. Nonetheless, and apparently without any additional information or evidence five years later, Complainant initiated this proceeding in 2018 with allegations that Respondent had a “clear intention to take an unfair advantage” of a “recognized trademark.” Fortunately for Respondent, he kept the communications from Complainant and its counsel from five years earlier, and could document the exchanges in his Response. If Respondent had not done so, the Panel in this case might have been left with the false impression that the Parties were total strangers at the time of the Complaint’s filing. Accordingly, the Panel finds it misleading that Complainant omitted this information from the Complaint and aggravated the omission by alleging that Respondent had a “clear intent” to target Complainant’s PROEZA mark.

The fact that outside counsel may not have been told about these letters does not excuse Complainant’s failure to disclose them, especially since Respondent’s response to those letters made the point that “proeza” is a dictionary term (see further below) and that Respondent rebutted the assertion of bad faith registration and use. A party should not be able to avoid the consequences of its conduct by shielding its counsel of knowledge about that conduct. This omission lies at the doorstep of in-house counsel, who should have appreciated the significance of these letters or should have asked outside counsel about them; the Panel does not agree with Respondent that outside counsel is responsible to the extent it failed to inquire about the letters (about which it had no knowledge).

Proeza also tried to slip by the panel that proeza is a dictionary word. The panel pointed out that it wouldn’t have known this if the domain owner hadn’t responded to the case:

In any event, if that was the Complainant’s view, it should have explained this clearly in the Complaint. The Panel finds it troubling that a Mexican Complainant could omit the fact that “proeza” is a dictionary word in the Spanish language – Mexico’s official language. Arguably, if Respondent had not filed a response, the dictionary meaning of “proeza” would not have been brought to the Panel’s attention, the Domain Name more likely would have been transferred, and an injustice would have been done. In the UDRP process, there is no discovery and rarely a hearing: panels rely on the candor of the parties in order to reach a just and fair decision. In this case, Complainant was not candid with the Panel. In sum, the Panel finds that Complainant’s misleading statement about the word “proeza” supports a finding of RDNH.

© 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

MMX completes .XXX ICM acquisition after ICANN approval

Domain Name Wire - Mon, 06/18/2018 - 15:39

ICANN gives nod to adult domain name ownership change.

Domain name overseer ICANN has approved the transfer of the .xxx, .porn, .adult and .sex top level domain names to Minds + Machines (MMX). As a result, MMX (London AIM: MMX) is completing its acquisition of ICM Registry, which controlled the domain names.

MMX paid $10.0 million cash, but the majority of the acquisition is being paid with 225 million shares in the company. At the time of the original acquisition announcement, those shares had a value of $31 million. They are now worth closer to $20 million, which is not surprising given the dilution that will occur with the share issuances. The shares will be issued over time and they have lock-in periods.

© 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. Sex-settlement: Manwin and ICM Registry come to terms
  2. Minds + Machines acquires .XXX top level domain operator ICM Registry
  3. ICANN Board Set to Approve .XXX Domain Friday
Categories: Domains

Three companies using new TLDs – DNW Podcast #190

Domain Name Wire - Mon, 06/18/2018 - 15:30

Why these three people chose new top level domain names.

How do people learn about new top level domain names? Why do they decide to register them rather than go with a .com? What are their experiences using the domains? On today’s show, we talk with three people who registered new TLDs: Kristi Kohut, an artist who uses KristiKohut.studio, Raluca Comanescu, who sells a planner at TheFeathers.ink, and Dave Rohrer, a digital marketer who uses BusinessOf.Digital for his podcast. Listen to their stories on today’s podcast.

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

© DomainNameWire.com 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 Mike Kugler spent $500k on Vacation.Rentals – DNW Podcast #181
  2. Sandeep Ramchandani, CEO of Radix – DNW Podcast #183
  3. The challenges of new TLDs with Tobias Sattler – DNW Podcast #177
Categories: Domains

Donuts acquires .Fan after registry fails

Domain Name Wire - Mon, 06/18/2018 - 13:08

Donuts, one of the original applicants for .fan, acquires it from failing registry.

The owner of .fan and .fans has failed, and Donuts was more than happy to pick up .fan–a domain name it originally applied for.

Donuts announced today that it has “re-acquired” the .fan top level domain name. Why the “re-acquired” language? Well, Donuts was one of two original applicants for the domain name. It entered into a private settlement with Asiamix Digital in which Asiamix won the contention set. Correction: Asiamix did not apply for .fan. Donuts won the domain and transferred it to Rightside (through a complicated deal) and Rightside later sold it to Asiamix.

.Fan is Donuts’ 241st top level domain under management.

© 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: Hurry up. Verisign: slow down.
  2. This week’s new TLDs: .Golf, .Gold and .Date
  3. Microsoft registers generics as they come off collision list
Categories: Domains

Canadian company GVE Global Vision Inc tries reverse domain name hijacking

Domain Name Wire - Fri, 06/15/2018 - 12:42

Package proofreading firm guilty of reverse domain name hijacking.

A Canadian company has been found to have engaged in reverse domain name hijacking over the domain name GlobalVision.com.

GVE Global Vision Inc (which goes by the name GlobalVision) helps companies like P&G and Coca-Cola with proofreading and inspecting their packaging.

It filed a complaint under UDRP with National Arbitration Forum, arguing that the UK company SDB Organisation Limited was cybersquatting with the domain name.

SDB registered the domain name in 1995, about 23 years ago. This is before GVE Global Vision had any rights in the Global Vision name. The complainant registered GlobalVisionInc.com in 1997.

GVE Global Vision tried to buy the domain from its owner in 2016. When that failed, it filed a trademark in Canada for Global Vision. Then it filed the cybersquatting complaint after getting the Canadian trademark.

Panelist Darryl C. Wilson wrote:

Respondent asserts Complainant and Respondent’s companies co-existed for 21 years without issue until 2016, when Complainant made an attempt to purchase the disputed domain name from Respondent, which Respondent refused on the grounds Respondent is an active company. Respondent asserts Complainant subsequently registered a trademark and engaged a legal team to intimidate Respondent by filing the Complaint to illegitimately gain control over the domain. The Panel here finds that Complainant knew or should have known that it was unable to prove that Respondent lacks rights or legitimate interests in the globalvision.com domain name and that Respondent registered and is using the disputed domain name in bad faith. The Panel thus concludes that reverse domain name hijacking has occurred.

GVE Global Vision was represented by Legal Logik Inc.

© 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. Dubai Law Firm Nailed for Reverse Domain Name Hijacking
  3. Telepathy scores $40,000 from reverse domain name hijacking case
Categories: Domains

Namecheap starts sending expired domains to GoDaddy Auctions

Domain Name Wire - Fri, 06/15/2018 - 01:29

GoDaddy Auctions increases its expired domain footprint.

Namecheap is the latest domain name registrar to send its expired domain name inventory to GoDaddy Auctions.

A Domain Name Wire reader noticed a domain in the GoDaddy Auctions expiry stream today that is for a domain registered at Namecheap. I subsequently ran searches uncovering many more.

Namecheap joins Tucows and Endurance International Group, which have been sending their domains to GoDaddy for a while. This means that GoDaddy Auctions has the expired domain inventory from the #1, #2, #3, and #6 largest domain registration companies (based on their .com registration base).

I predicted that Namecheap would end up in GoDaddy’s stable. Namecheap just had a nasty divorce with Tucows, which operates the competing website NameJet where Namecheap names were previously auctioned off.

(Yes, Tucows sends its expired domain inventory to GoDaddy despite owning 50% of a competing expired domain service. That speaks volumes.)

© 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. Major shakeup: Tucows sending expired domain names to GoDaddy Auctions
  2. Another major registrar is sending expired domains to GoDaddy
  3. Name.com expired domains are now on GoDaddy
Categories: Domains

Man gets 20 years in prison for trying to steal a domain name

Domain Name Wire - Thu, 06/14/2018 - 18:37

Man tried physically force domain owner to transfer the domain name.

A Cedar Rapids, Iowa man will head to prison for 20 years for trying to steal a domain name, the Associated Press reports.

By steal a domain name, I mean physically.

Sherman Hopkins Jr. broke into a man’s home on June 21, 2017 with a handgun and demanded that the resident transfer the domain name DoItForState.com to another account, the AP reports. He shot the man with the gun and used a stun gun, but then the man got control of the gun and shot Hopkins back.

Domain name theft happens all of the time, but rarely does it involve a physical altercation. Usually, it’s a matter of stealing someone’s domain name registrar credentials or hacking into their email.

© 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. DingBats.com Case Discusses Pool.com Lawsuit Over Domain Theft
  2. 8 Clues a Domain Name is Stolen
  3. Mrs Jello sues over stolen domain names
Categories: Domains

Comparing Whois after GDPR

Domain Name Wire - Thu, 06/14/2018 - 17:34

See a limited Whois record through Port 43 as well as GoDaddy’s full Whois records.

Earlier today ICANN continued its battle in German courts over what data domain name registrars need to collect for WHOIS now that the European Union’s General Data Protection Regulation is in effect.

Because of GDPR, ICANN has changed the data that domain name registrars must display in Whois records.

In this video, you’ll see what information domain name registrars need to provide for Port 43 lookups. It also shows what GoDaddy is providing if you do a web-based lookup on GoDaddy.com. GoDaddy continues to provide full Whois records for web-based lookups. Most other registrars limit the data.

© 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. Benefits to keeping Whois open
  2. I just fixed Whois and GDPR
  3. Security vs. Privacy with GDPR
Categories: Domains

ICANN appeals German court ruling as it seeks definitive ruling on GDPR and Whois data collection

Domain Name Wire - Thu, 06/14/2018 - 12:54

ICANN wants to know if collecting certain Whois data is a violation of GDPR.

A court battle in Germany over the impact of the EU’s General Data Protection Regulation (GDPR) continues.

ICANN filed a legal action against EPAG, a registrar owned by Tucows, on May 25–the same day GDPR went into effect. It asked for an injunction after EPAG informed ICANN that it would no longer collect the administrative and technical contacts for Whois.

EPAG’s argument is that these two contact types are not necessary because it’s still collecting the registrant information. In most cases, the admin and technical contacts match the registrant data, and in the other cases EPAG would be holding data on parties it doesn’t have a contractual relationship with.

The German court ruled against the injunction.

However, ICANN notes that the court did not say whether or not collecting the data would be a violation of GDPR. That’s the information ICANN wants, so the group has appealed the ruling.

An English language translation of the appeal has been posted to ICANN’s website.

© 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. GDPR will make domain name transfers more difficult
  2. Will May 2018 be the death of Whois?
  3. ICANN files legal action against Tucows registrar over GDPR
Categories: Domains

Video: How to set up Keyword Locking on Uniregistry

Domain Name Wire - Wed, 06/13/2018 - 14:34

See how to lock keywords for your domain name.

The recent DVT.com UDRP decision was a good reminder of how parking a domain name can be helpful in a cybersquatting case…IF the ads are related to the dictionary context of the name rather than a trademark owner’s goods and services.

If you park your domain names and let the system determine the correct keywords, you could find yourself in hot water.

Uniregistry has a tool that lets you set keyword topics for your domains to make sure they target the right concepts.

This video walks you through how to set a keyword topic for your domain names parked at Uniregistry.

© 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 set a keyword category on Uniregistry parked domains
  2. First signs of Google’s new domain parking client identification program…
  3. Domain inquiries could drop next month. Blame SSL.
Categories: Domains

Hilton’s next hotel brand will be Motto

Domain Name Wire - Wed, 06/13/2018 - 12:41

Company registers domain names for Motto hotel brand.

In 2015 I scooped that Hilton (NYSE: HLT) was getting ready to launch a new hotel brand called Tru because of domain names it had registered. The company is now getting ready to launch a hotel brand called Motto.

Yesterday, Hilton registered these domain names:

HiltonMotto.com
hiltonmottohotels.com
mottobyhilton.com
mottochicago.com
mottodallas.com
mottohilton.com
mottohotelchicago.com
mottohoteldallas.com
mottohotelnewyork.com
mottohotelorlando.com
mottohotels.com
mottohotelsanfrancisco.com
mottonewyork.com
mottoorlando.com
mottosanfrancisco.com

While the domain names tip the company’s hand, a keen observer of trademark filings would have picked up on this earlier. In April, Hilton filed an intent-to-use trademark application for Motto for “Rental of temporary accommodation; reservations of temporary accommodations; hotel, motel, bar, café and restaurant services.”

© 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

Supreme Court ruling leads to domain name bonanza

Domain Name Wire - Tue, 06/12/2018 - 20:27

Punters register domain names for sports betting.

Last month the U.S. Supreme Court handed down a decision that effectively allows states to legalize sports betting. This is a huge economic opportunity, and some people see value in registering sports betting domain names.

According to .com domain name registry Verisign, these were the top ten “trending” keywords in .com registrations last month:

1. sports
2. bet
3. apple
4. bets
5. escort
6. gambling
7. betting
8. adverts
9. bookie
10. opportunity

At least six of the domains are directly related to sports betting.

Verisign calculates the trending keywords based on which terms had the highest percentage increase in registrations from one month to the next.

I haven’t noticed an uptick in domain sales related to sports betting yet, but I expect this will happen as more states legalize sports betting.

© 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

.LLC and .INC domain names are on their way

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

With .Inc acquisition, we’ll finally see two of the better corporate identifier domains this year.

It’s been a long wait, but two of the best “corporate identifier” top level domain names are coming to the market.

Afilias’ .LLC domain name is in the trademark sunrise period until July 5. A landrush will run from July 9-20, followed by general availability on July 23. Regular retail pricing is in the $30 range.

Another company, Intercap Holdings Inc, has acquired rights to run the .INC top level domain name. It plans to run a sunrise in October, a 7-day early access period in November and also enter general availability in November. .INC domain names will come with a hefty $2,000 suggested retail price.

Neither domain has registrant restrictions, but the price of .INC domains will limit the buyer pool.

A couple of lesser-known corporate identifier domain names have already come to market. .GMBH has about 20,000 names in the zone file and .LTDA has fewer than 1,000.

© 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. Mortgage.info for $250? There’s a Small Catch.
  2. Next week is colorful for new TLDs: 5 Schillings, Afilias colors, and a bit of buzz
  3. Afilias gets contract for Puerto Rico’s .PR domain
Categories: Domains

DVT.com case shows the right way to park a three letter domain name

Domain Name Wire - Mon, 06/11/2018 - 16:42

Parked page ads help show rights or legitimate interests in the domain.

Three letter domain names are extremely valuable. That’s one of the reasons you see so many cybersquatting complaints under UDRP against these domains. When quoted with a “high” price to acquire the domain, the complainant decides to try its luck with an inexpensive UDRP filing.

That was the case with DVT.com. A South African company called Dynamic Visual Technologies (Pty) Ltd filed a UDRP against the domain owner, who acquired it as an investment last year.

The complainant’s use of the acronym predates the registrant’s ownership of the domain, but the case fell apart (in part) because the complainant didn’t show that the domain owner lacked rights or legitimate interests in the domain.

It helped that the domain owner parked the domain and it is showing ads related to deep vein thrombosis. It would have been troublesome for the domain owner if the ads on the page were related to the products and services that the complainant sells.

If you park an acronym domain, it’s best to lock the keywords to relate to a “generic” meaning of the acronym.

© 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

The Amazon FBA business model – DNW Podcast #189

Domain Name Wire - Mon, 06/11/2018 - 15:30

How to create a business on Amazon.

Ecommerce is a huge business opportunity, but owning a business with physical inventory can be overwhelming. Our guests this week run ecommerce businesses in which Amazon handles the hard stuff for them, including fulfillment of the product. Noah and Adam Weitzman of the AMZ Answers Podcast run what’s called ‘Fulfillment by Amazon’ businesses, or FBA. You’ve probably seen some of these listed for sale on Flippa before. Noah and Adam will explain what FBA is, how to get started, and if it’s the panacea that it sounds like.

Also: Tiered Access, reverse domain name hijacking 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 below 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 End User Domain Buyers Think – DNW Podcast #134
  2. The challenges of new TLDs with Tobias Sattler – DNW Podcast #177
  3. Sandeep Ramchandani, CEO of Radix – DNW Podcast #183
Categories: Domains

Notable NameJet sales from May

Domain Name Wire - Fri, 06/08/2018 - 17:59

Here are some of the more interesting sales at NameJet from the past month.

NameJet sold 94 domain names for $2,000 or more in May for a total of $416,000. Here are ten sales that stuck out to me, plus the full list below.

BitcoinSecurity.com $6,900 – I think you could hand reg a domain with bitcoin, coin, or crypto in it, get it into an expired domain auction and see it sell for a lot these days. (This particular domain was registered in 2011.)

Criminology.com $15,100 – This domain sold on Sedo for $24,000 in 2011.

Builds.com $6,100 – This is an interesting one. In general, the plural makes it much less valuable than the singular. But could someone turn this into a brand? Or maybe use it for “software builds”?

StudyGuides.com $3,054 – I like this domain, especially at this price. Lots of opportunity here.

ThatsAwesome.com $2,600 – Is it?

MovingSucks.com $2,000 – Yes it does.

Domain NamePayment Amount yig.com16100 pate.com16000 criminology.com15100 zoma.com11200 raincloud.com11102 brevard.com10988 psyweb.com9999 kuikui.com9311 compas.com9255 aditi.com7978 bitcoinsecurity.com6900 intellisys.com6389 grafica.com6301 builds.com6100 flowering.com5999 cancunrealestate.com5988 96315.com5809 58852.com5699 18823.com5599 myvehicle.com5560 equipo.com5305 rohe.com5099 myrussia.com5019 suitors.com5001 netguard.com5000 18812.com4799 bourbon.net4701 98817.com4599 18813.com4599 98823.com4599 18821.com4599 98829.com4599 18825.com4599 98831.com4599 96629.com4599 76689.com4599 18826.com4599 98832.com4599 18827.com4599 identy.com4095 dotnetblogengine.net4010 zamu.com4000 lightstick.com3945 perpendicular.com3877 cslib.org3832 h52.com3600 gum.net3499 yuwen123.com3487 cordlessdrills.com3188 aicomputer.com3109 optimiser.com3105 studyguides.com3054 mbgroup.com3033 pennie.com3002 h0.net3000 marsh.net2907 jdhome.com2900 koros.com2800 cantos.com2702 zspc.com2700 thatsawesome.com2600 lalinea.com2600 cotton.net2599 commercialsearch.com2599 ikinci.com2578 aracnet.com2520 awaw.com2510 tm2.com2502 wallstreetnews.com2500 babydevelopment.com2500 688866.com2500 17003.com2400 pcgroup.com2400 namesys.com2400 minecrypto.com2399 wealthwatch.com2366 vaku.com2322 hellofood.com2322 textbook.net2215 indiasports.com2202 awtar.com2200 icep.com2200 8chain.com2200 robocare.com2149 ladao.com2111 66949.com2109 58002.com2100 63787.com2100 dttd.com2100 purefaces.com2003 expressmoney.com2001 78112.com2000 movingsucks.com2000 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

Top Domain Name Stories from May

Domain Name Wire - Thu, 06/07/2018 - 16:01

A whole lot of GDPR.

Here’s a look at the top stories on Domain Name Wire last month, ranked by pageviews:

1. Google has already GDPR’d its Whois records – Google Registry began limiting the data in Whois records well before the May 25 deadline.

2. ICANN files legal action against Tucows registrar over GDPR – And it didn’t get the answer it wanted.

3. GoDaddy will continue publishing most domain owner data – In news welcomed by many people in the domain name ecosystem, GoDaddy decided to keep most Whois information public for people outside the EU.

4. Here’s why it’s going to be hard to sell your .App domain names – .App came out with a roar in May. But selling domains is going to be difficult because of a lack of public Whois (see story #1) and because you have to install an SSL certificate in order for a .app domain to resolve. Some services have come to the rescue.

5. Sahar Sarid arrested on charges related to Mugshots.com A domain investor connected to Mugshots.com got his own mugshot.

If you missed any podcasts, take some time this weekend to listen:

#187 – Drew Wash develops businesses on premium domains – Listen

#186 – Building an Ecommerce business on your domain name – Listen

#185 – Jen Sale of Evergreen – Listen

#184 – Jean-Noël Frydman discusses his France.com saga – 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. The state of the domain name industry
  2. Namecheap leaps up .com chart as PDR falls
  3. ICANN files legal action against Tucows registrar over GDPR
Categories: Domains

Donuts acquires BudURL, rebrands as BL.INK

Domain Name Wire - Thu, 06/07/2018 - 13:00

Acquisition will increase awareness and use of new top level domain names.

Domain name registry Donuts has acquired link management company BudURL and rebranded it as BL.INK.

Donuts quietly completed the acquisition of the Austin, TX company last year. Since then, it has been enhancing the system and developing a way for registrars to offer it to their customers as a value-added service.

Like many link shortening services, BL.INK enables customers to create shortened links based on their domain name or to use system domains. What makes BL.INK interesting is that it taps into Donuts’ inventory of over 240 top level domain names* to create contextually-relevant links.

For example, when I shorten this URL for a story about Wonder Woman 2 domain names, it gives me these link options:

 

With Twitter expanding its character count, the length of a “short” link is no longer a restricting factor. Donuts is betting that links will perform better when they are relevant to the page topic. The company commissioned a survey to understand which types of links people prefer to see, and most prefer short links with real words rather than character strings, the company says.

The acquisition makes sense for Donuts. BL.INK will certainly introduce more people to new top level domain options.

Donuts can also leverage its existing domain name registrar channel to sell the product. Registrars hungry for higher-margin products can offer a white label version of BL.INK to get additional subscription revenue and sell more domains, or they can get paid for referring customers directly to BL.INK.

BL.INK also has a number of enterprise clients that provide stable recurring revenue. Clients include Coca-Cola, Target and Airbnb.

A free plan (including the ability to connect a custom domain) is available. Paid plans with higher limits and more features start at $12 a month.

(* It’s worth noting that .INK is not one of Donuts’ 240 top level domains. .INK is owned by Top Level Design.)

© 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’ new TLD renewal rates range from 55% to 72%
  2. Inside new top level domain company Donuts
  3. Donuts acquires .Travel domain name
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.