skip to content

News

  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.

Is Amazon preparing OpenTube to compete with Google’s YouTube as companies spar?

Domain Name Wire - Wed, 12/06/2017 - 14:47

Amazon.com registered domain names related to OpenTube and Alexa Tube.

The Amazo Echo Show

Amazon.com has been fighting with Google in recent months over the inclusion of YouTube on Amazon’s Echo Show devices. Amazon.com might be gearing up to take the fight to another level.

The Echo Show is an Alexa-powered device that includes a screen. We have one in our house and my daughter loves to watch YouTube videos on it. Rather, she did enjoy watching YouTube on it until Google forced Amazon to pull the plug.

Details of the fight are summarized nicely here.

Coinciding with the latest news of YouTube being pulled from the Echo again yesterday, Amazon registered three domain names:

AlexaOpenTube.com
AmazonAlexaTube.com
AmazonOpenTube.com

Is Amazon preparing to create its own free and open competitor to YouTube? Or is it starting an OpenTube initiative to get Google to open up? We’ll have to see.


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

Latest domain news at DNW.com: Domain Name Wire.

The post Is Amazon preparing OpenTube to compete with Google’s YouTube as companies spar? appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

3 Tips to Discover Expired Domains Available at Hand-Registration Fee

Domain Name Wire - Tue, 12/05/2017 - 19:26

[Editor’s note: I’m pleased to have Alvin Brown join as a contributing author on DNW. Brown is a fellow Austinite, domain investor and digital marketer. He posts great tutorials at KickstartCommerce.com, and will be writing posts for DNW that will help domain investors.]

Each day I spend my fair share of time reviewing a vast number of expired domain auctions to share with others and bid on personally.

Although I review a number of aftermarket platforms of expired domains daily, I often use GoDaddy’s aftermarket platform.

I actively bid and secure a growing number of competitively-priced expired domains through GoDaddy’s aftermarket platform every week.

If you use GoDaddy’s aftermarket platform to bid and purchase expired domains, then you’ll want to continue reading as I share 3 tips to discover expired domains available at hand-registration fee (hand-reg fee).

If you are not familiar with the GoDaddy Aftermarket, please allow me a moment to help you get acclimated.

For starters, you’ll need to be a GoDaddy Auctions member ($4.99/yr). Once a member and logged in, the following image is displayed by default and allows the following capabilities:

  • Basic or Advanced Search for domains or keywords
  • Announcement bar with latest offer or auction news
  • Secondary auction navigation consisting of Selling List, Bidding List and Settings options
  • Pre-configured search reports containing Featured, Most Active, Expiring, Ending Soon, Fixed Price, Closeouts, Bargain Bin, A-Z Listings
  • Ability to create, save and manage custom search reports
  • Featured Domains and Most Active domains randomly (displayed/listed on initial page load)

For what I’ll share with you today about discovering expired domains available at hand-reg fee, we’ll focus on secondary auction navigation menu selections: Selling List and Bidding List.

3 Tips to Discover Expired Domains Available at Hand-Registration FeeClick To Tweet Bulk Search Using Didn’t Win Domains

One of the places I frequently visit when on the hunt for available expired domains at hand-reg fee is bulk searching previous expired domain auctions I didn’t win.

I’m amazed at the number of expired domains I didn’t win in auction that are hand-reg available because whomever bought the domain at auction let it expire.

Don’t expect all domains when bulk searching. There may only be a handful, 10 or less, of expired domains you didn’t win in auction that are available at hand-reg fee.

To get started with bulk searching domains not won in auction, click the Bidding List menu selection, and click the Didn’t Win text to display previous expired domain auctions not won in a table.

To download Didn’t Win domains, click the Bidding List menu selection, and click the Didn’t Win green download icon to the right of the text.

This action allows for exporting and download of ALL previous expired domain auctions not won.

Once successfully downloaded, open the download using Excel (Windows) or Numbers (Mac).

Copy the entire row column of domain names, excluding the header row, to the clipboard using Command+C (Mac) or Ctrl+C (Windows) keyboard commands.

With the domains copied to the clipboard, you’re now ready to execute a bulk search.

From the primary menu, click the “Domains” link, and then click “Bulk Domain Search” text link found under the “Find a Domain” section.

Once the page loads and displays the following, paste your entire list of domains not won into the bulk search input texture and click the Go button.

Keep in mind bulk search functionality has a maximum 500 domains per search. If you have more than 500 domains to bulk search, then you’ll need to execute multiple searches.

Once successfully executed, you’ll be shown whether or not domains are available, registered and available, and/or unavailable (registered).

In addition, a “Proceed to Checkout” button is displayed along with functionality to select or unselect all domains, copy all domains, and remove selected domains.

Once proceeding to checkout, the experience is the normal GoDaddy checkout experience.

Bulk Search Using Won Domains

It’s not often I bulk search expired domains previously won in auction. After all, I tend to invest and hold most domain investments for a minimum of 5 years.

But for the case where I’ve intentionally or inadvertently dropped domains won in auction over the course of time, I’ll find a few domain diamonds in the rough to re-invest in.

To get started with bulk searching domains won in auction, click the Bidding List menu selection, and click the Won text to display previous expired domain auctions won in a table.

To download the Won domains, click the Bidding List menu selection, and click the Won green download icon to the right of the text.

Somewhat like Didn’t Win domains, this action allows for exporting and downloading ALL previous expired domain auctions won.

Once successfully downloaded, open the download using Excel or Numbers and perform the same actions as explained with Didn’t Win domains.

Simply copy domains to the clipboard, and paste domains and perform a bulk search as explained in the previous section.

Bulk Search Using Sold Domains

One of the final places I fish for domains available at hand-reg fee is the Sold section of the Selling List, one of the secondary auction navigation menu selections.

Much like Didn’t Win expired domains, Sold domains are not necessarily expired domains, but public domain auctions or domains listed for sale.

Nevertheless, I’m amazed at the number of times I’ve checked and identified 3-4 domains I’ve previously sold on GoDAddy that the buyers subsequently dropped.

I’ve had success 2 different times re-registering, listing for sale, and selling such domains within 4-6 months of hand registration.

It’s always good times to realize the opportunity in hand-regging and profitably selling the same domain to two distinct domain buyers within a two to three year timeline.

To get started with bulk searching domains sold in auction, click the Selling List menu selection, and click the Sold text to display previous expired domain auctions sold in a table.

To download the Sold domains, click the Selling List menu selection, and click the Sold green download icon to the right of the text.

As expressed in previous sections, this actions allows for exporting and download of ALL previous domains sold.

Once successfully downloaded, open the download using Excel or Numbers and perform the same actions as previous sections, copying domains to the clipboard, and pasting domains and perform a bulk search as explained in the previous section.

Closing Thoughts 3 Tips to Discover Expired Domains Available at Hand-Registration FeeClick To Tweet

Learning to use GoDaddy’s aftermarket to occasionally check Didn’t Win, Won, and Sold domain listings could land you profitable domain investments and future sales at hand-reg cost.

And as an added bonus, I recommend following and tracking the lifecycle of each Didn’t Win domain. Was the domain flipped or leased? If so, at what price (hint, hint: NameBio.com)? Was the domain developed or simply redirected?

These are a few of the thoughts and questions that come to mind when managing my GoDaddy aftermarket activity and profitable domain portfolio growth. That’s all for now!


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

Latest domain news at DNW.com: Domain Name Wire.

The post 3 Tips to Discover Expired Domains Available at Hand-Registration Fee appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. GoDaddy tests new lander for expired domain names
  2. GoDaddy Auctions sells 39,830 domain names in October
  3. Another major registrar is sending expired domains to GoDaddy
Categories: Domains

Tucows sells some domain names to GoDaddy

Domain Name Wire - Tue, 12/05/2017 - 16:57

GoDaddy’s NameFind is buying some domain names from Tucows.

Tucows (NASDAQ:TCX) appears to have sold some of its domain name portfolio to GoDaddy’s (NYSE:GDDY) NameFind.

Today I noticed that some domain names in Tucows’ YummyNames portfolio have undergone a Whois change. While the owner and contact details still point to YummyNames, they have an additional notice at the bottom of the record:

Registration Service Provider:
Namefind LLC, admin@namefind.com
+1.7813736856

See Biologist.com for example.

This is similar to a notice that would appear when one of Tucows resellers manages a domain. It seems that Tucows has sold domain names to NameFind which are, for now, in a reseller account.

I reached out to both GoDaddy and Tucows for comment. GoDaddy VP Paul Nicks responded:

We can confirm that GoDaddy has acquired some additional domain names. The domain names we are acquiring will help anyone looking to make a statement online. We will soon be adding the names to the NameFind portfolio. We will not be disclosing the seller’s identity as they have requested to remain private.

Tucows has not yet responded to the request for comment. Depending on the size of the transaction, it might be disclosed in an upcoming SEC filing.

Tucows has many portfolios including YummyNames and its Mailbank portfolio of surnames. I have not yet detected any movement among the surnames, and only some within the YummyNames portfolio.

This transaction is a bit different from other domain portfolio acquisitions GoDaddy has done. GoDaddy has typically acquired portfolios that haven’t been optimized for sales velocity. GoDaddy then prices the domain at reasonable amounts and adds them to its syndicated network on Afternic. Tucows has already been fairly good at pricing and syndicating its domain listings.


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

Latest domain news at DNW.com: Domain Name Wire.

The post Tucows sells some domain names to GoDaddy appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Tucows: fewer big domain sales, but good numbers on lower priced domains
  2. Rewind: Tucows for $1.00, go-go parking revenue and CreditCards.com
  3. Cancer.info hits $11,000, leading .info domain auction
Categories: Domains

Wow: this is what public Whois could look like in 2018

Domain Name Wire - Tue, 12/05/2017 - 14:38

Good luck figuring out what individual in the EU owns a domain name.

The European Union will begin enforcing its General Data Protection Regulation (GDPR) in May of 2018. As I’ve written about before, this will have a major impact on Whois.

How big? Well, I have jokingly included this image in my August story of what Whois could look like:

Turns out I’m not that far off. Consider what the world’s second largest registrar, Tucows/Enom, suggests that a public record for an individual in the European Union will look like:

Note that this Whois record doesn’t even have a forwarding address for email!

Think of the impacts this will have on domain name investors trying to buy domains or verify ownership. I also wonder how this will work when transferring a domain name. Even Whois updates in which contacts must be emailed will be an issue.

This is what a Whois record might look like in 2018Click To Tweet

The answer might lie in gated Whois. In a blog post, Enom states:

…we plan to provide authenticated access in a specific and limited manner, so that those with legitimate reason to request personal data can access the information they require while the privacy of individuals remains protected.

Who has a legitimate reason? Enom notes a couple of examples:

Think about, for example, an intellectual property lawyer who wants to know the owner of a domain in order to submit a trademark dispute, or a law enforcement officer tracking down the people behind a phishing scheme; they should be able to find out who owns the domain name under investigation.

It will be interesting to see who is considered to have a legitimate reason to view at least some part of the Whois record.

Although the regulation will only impact individuals in the EU for now, we could see this sort of Whois change apply across the world in the future. Again, from Enom’s blog post:

While the GDPR only applies to EU-local individuals, there are data privacy and protection regulations in many other places around the world, which render a public Whois highly problematic, if not unlawful. With this in mind, what we know for sure is that we will no longer be able to publish personal data for any EU-located individual in the public Whois. What remains an open question is if we will continue to publish personal data for registrants based outside of the EU; we don’t yet have a final answer on that, and we’ll work through this issue over the next few months.

This change is going to have a big impact on almost everyone in the domain name industry.


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

Latest domain news at DNW.com: Domain Name Wire.

The post Wow: this is what public Whois could look like in 2018 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Spamming owners of newly registered domain names
  2. Trans-Pacific Partnership Treaty addresses cybersquatting, Whois
  3. Will May 2018 be the death of Whois?
Categories: Domains

How to use automated domain appraisals

Domain Name Wire - Mon, 12/04/2017 - 17:55

Automated domain appraisals aren’t perfect but smart domainers can use them to their advantage.

I wouldn’t sell SoftwareCareers.com for this price but the appraisal is still helpful.

GoDaddy released its automated domain name appraisal system to the public last week, and quite a few domainers disagreed with the values it provides.

Valuing domain names is very difficult, especially with automated tools. Domain names are unique assets. The sales price of a domain name has a lot to do with how much money the buyer has and how much the seller is willing to hold out for.

Automated domain appraisals provide immense value to domain investors...you just need to know how to use them.Click To Tweet

Still, automated appraisals provide immense value to domain name investors. You just need to know how to use them properly. If you dismiss tools like GoDaddy’s and Estibot’s out-of-hand, I think you’re leaving some great data (as well as profits) on the table. Here’s how I recommend using automated appraisals:

1. Don’t accept appraisals as the definitive answer.

Most domainers won’t have a problem with this. This isn’t limited to automated appraisals, either. Even appraisals by experts are not definitive. They are just a data point. In some cases, they will be very good starting points when you consider the data behind them.

2. Review the rationale.

Both GoDaddy appraisals and Estibot don’t just give you a number. They give you a rationale for the value. In GoDaddy’s case, it spells this out in plain English. In Estibot’s case, it’s a lot of data.

For example, Estibot might show that your .com domain name is also registered in .net and .org. That’s a pretty good sign of value.

Sometimes the rationale behind an automated appraisal will be wrong, so you need to take a look at it.

For example, I ran a domain name through GoDaddy’s tool that had three numbers and a letter in it. GoDaddy appraised it much lower than I sold the domain for this year. The reason was clear when I looked at the comps. My domain was a financial term from the tax code but GoDaddy was comparing it to other domains with three numbers and a letter that didn’t have secondary meaning. I wouldn’t expect an automated appraisal to pick this up easily. Estibot misses on this particular domain as well.

3. Review the comps.

Speaking of comps, comparative sales can be a goldmine. Even if you don’t agree with the value a domain appraisal gives you, comps can be excellent for determining what you think a fair value is.

One of the domains I tested on GoDaddy was AtlantaBodyshop.com. A comp included with the appraisal was KansasCityBodyshop.com. If a buyer tries to tell me I’m crazy for expecting my asking price, I can point to the higher sale of the Kansas City domain to show that it’s not crazy.

One area in which I believe GoDaddy’s appraisals excel is in finding good comps. Keep in mind that GoDaddy probably has more sales data than anyone in the world.

4. Use appraisals for buying.

Think automated appraisals are uniformly low? Then use them for when you buy domain names.

I’ve already used this to my advantage. I recently bought a domain name from someone who used GoDaddy’s appraisal syatem on his own intiative. It gave a reasonable number and he used it as his baseline for an offer. I offered about 60% of the appraisal value and he accepted. Consumers trust GoDaddy and you can use this to your advantage.

5. Find outliers with appraisals.

Every six months I run my entire portfolio through Estibot’s bulk checker. My goal is to find any outliers that I might not have noticed or that have changed in value.

Automated appraisals are good at finding diamonds in the rough that you might have overlooked. Perhaps some other company has recently registered the .net and .org to match your .com. Perhaps search volumes for a domain have spiked. Maybe there have been a lot of recent comp sales. If nothing else, run your domains through Estibot’s bulk checker before letting them drop.

I firmly believe that automated domain name appraisals have value. Are they spot on? Absolutely not. Are they built on great data that can inform your buying and selling decisions? Absolutely.


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

Latest domain news at DNW.com: Domain Name Wire.

The post How to use automated domain appraisals appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Estibot 2.0 is a Domainer’s Dream
  2. 4 subscription domain name services I use
  3. Estibot to launch domainIQ for reverse and historical whois
Categories: Domains

Building web businesses with Peter Askew – DNW Podcast #163

Domain Name Wire - Mon, 12/04/2017 - 16:30

How one domainer has successfully developed premium domain names.

A lot of domainers try to create businesses on their good domain names but run into challenges. This week’s guest, Peter Askew, has developed three great domain names into businesses. He explains some of the challenges and successes he’s had. Each of his businesses is unique, too: a directory biz model on DudeRanch.com, ecommerce shipping a fresh product on VidaliaOnions.com and now a software as a service business at CallTracking.com, which he bought earlier this year for $21,000 on NameJet. Also: Weeds.com hijacking, $40,000 for RDNH, AWS re:Invent and Page Howe appears on HBO.

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


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

Latest domain news at DNW.com: Domain Name Wire.

The post Building web businesses with Peter Askew – DNW Podcast #163 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. What you need to know from ICA – DNW Podcast #128
  2. How End User Domain Buyers Think – DNW Podcast #134
  3. Dynadot CEO Todd Han – DNW Podcast #141
Categories: Domains

Neustar eats its own dog food by switching to .Neustar

Domain Name Wire - Mon, 12/04/2017 - 13:00

Company moves its website from Neustar.biz to Home.Neustar.

Neustar, a company that offers backend registry services as well as top level domain names (TLD) such as .co, has switched its web address to use the .neustar TLD.

The company has been a big proponent of so-called .brand top level domain names that have a brand name to the right of the dot. While it provides backend registry services for generic new domains such as .club, many of its customers are .brands and it is already trying to line up companies to apply for .brands in the next round of domain name expansion.

It’s difficult to sell people on .brand domain names if your own company doesn’t use one. Neustar has been using .neustar to a limited degree already but is now making a wholesale switch. Its home page is now home.neustar and each of its product areas has its own domain: marketing.neustar, security.neustar and risk.neustar.

Employee email addresses end in @team.neustar.

The company is not switching from .com; its previous web address was Neustar.biz. That was an earlier example of the company eating its own dog food because Neustar has the .biz contract.


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

Latest domain news at DNW.com: Domain Name Wire.

The post Neustar eats its own dog food by switching to .Neustar appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. 1 and 2 Character .Biz Domain Names Face Delays
  2. Neustar Offers $10k a Year .Brand Domain Names
  3. From 10-cent domains to revved up marketing and policy changes, .US might finally go somewhere
Categories: Domains

Amazon.com launches .Bot domain names on Tuesday

Domain Name Wire - Fri, 12/01/2017 - 22:05

Bot it won’t be easy to register them.

Amazon.com is making .bot domain names available to the public on Tuesday starting at 6 a.m.

The company has been testing different business models for its new top level domain names and this domain is no exception. Registration of the domain names will be severely restricted.

The company says .bot “is a space specifically for developers and their end customers to find and discover bots”. At launch, Domain names will only be available to people who have published a chatbot through Amazon Lex, Microsoft Bot Framework or Dialogflow. More development platforms will be added in the future.

Registrants will need verify their ownership of a bot on these platforms in order to register the domains. For example, Amazon Lex users will need to create an AWS “cross account role” and provide additional information when registering.

Registrants will begin the process at get.bot, but the domains will be registered through domain registrars.


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

Latest domain news at DNW.com: Domain Name Wire.

The post Amazon.com launches .Bot domain names on Tuesday appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Amazon.com registers .domains domain names for each of its proposed TLDs
  2. Is Amazon.com the biggest user of new domain names?
  3. More Amazon new TLD reg’s and Google’s odd domain names
Categories: Domains

.Com Winners & Losers Update

Domain Name Wire - Fri, 12/01/2017 - 18:05

How registrars fared with .com in the most recent reports.

ICANN published the latest official .com transactions report from Verisign today which includes data by registrar for August 2017.

Here are the top registrars in terms of new .com registrations for August. There were no changes in ranking from July.

1. GoDaddy* 922,658
2. Tucows** 193,081
3. PublicDomainRegistry 135,332
4. HiChina 128,586
5. Namecheap 121,858

When it comes to net inbound transfers (transfer gains minus transfer losses) for registrars open to the public, here are the top five gainers. This list excludes registrars that aren’t open to the public.

1. HiChina +34,959
2. GoDaddy +21,002
3. NameSilo +9,274
4. MAFF Inc (XZ.com) +8,131
5. Google +7,635

On the flip side, these five registrars saw the biggest net outflow of .com domain names due to transfers:

1. EIMS.cn -16,650
2. Domain.com -12,919
3. RealTime Register BV -9,004
4. PublicDomainRegistry -8,334
5. Uniregistry -8,146

*Includes GoDaddy and Wild West Domains **Includes Tucows and Enom


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

Latest domain news at DNW.com: Domain Name Wire.

The post .Com Winners & Losers Update appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Chinese registrars lose of lot of .com, but HiChina picks up domains from others
  2. A subtle (yet big) change in GoDaddy’s ads
  3. .Com domain name winners and losers
Categories: Domains

CentralNic’s .sk purchase moving forward under changed terms

Domain Name Wire - Fri, 12/01/2017 - 15:03

Deal changes from an asset purchase to a share purchase.

Top level domain name operator CentralNic (London AIM:CNIC) announced it was acquiring the .sk (Slovakia) top level domain name on August 25th. It still hasn’t completed the deal and the terms have changed.

The deal was originally created as an asset purchase. Now, CentralNic will acquire the SK-NIC, a.s. legal entity and all associated assets and liabilities.

CentralNic does not expect this to have a material impact on how much it pays for .sk:

The maximum total consideration for the acquisition remains unchanged at €26.12 million, however the initial cash consideration for the acquisition will now be slightly lower, at €20.27 million (previously €21.27 million), and the deferred cash consideration will now be slightly higher at up to €5.85 million (previously up to €4.85 million), and extended in time to cover a period until 2023. The deferred cash consideration is dependent on SK-NIC attaining defined growth targets over the next three years.

The share purchase agreement was entered into yesterday and the company expects the deal to close “in the near future”.


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

Latest domain news at DNW.com: Domain Name Wire.

The post CentralNic’s .sk purchase moving forward under changed terms appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. CentralNic acquires .SK operator for €26 million
  2. CentralNic is on the premium domain hamster wheel
  3. CentralNic adds 14 TLDs but .SK deal delayed
Categories: Domains

Page Howe talks emoji domain names on HBO’s Vice News

Domain Name Wire - Fri, 12/01/2017 - 02:56

Domain investor gets primetime interview on popular HBO show.

Domain name investor Page Howe was on HBO’s Vice News tonight talking about emoji domain names.

You can watch a preview of the interview here:

Howe made a name for himself after selling Seniors.com for $1.8 million and Guy.com for $1.0 million.

He believes in emoji domain names but also understands their drawbacks. I tend to see their drawbacks more than the opportunity in them, but I’m always willing to be proven wrong.

Either way, it’s good to see domain names get mainstream attention, especially when it’s not a negative story about cybersquatting.


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

Latest domain news at DNW.com: Domain Name Wire.

The post Page Howe talks emoji domain names on HBO’s Vice News appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Godaddy releases domain name appraisal tool to the public

Domain Name Wire - Thu, 11/30/2017 - 23:18

New appraisal tool will give you a free and quick domain name appraisal.

GoDaddy has made its much-improved automated domain name valuation tool available to the public.

The beta tool allows anyone to enter a domain name and receive an instant appraisal that includes some supporting data. For example, when I entered my domain name AtlantaBodyShop.com, I saw:

The basic valuation tool has actually been available for a little while but not publicized. Until today it did not show the comparative sales and valuation rationale that’s now visible on the right site.

The comps are pretty good, too. For AtlantaBodyShop.com, GoDaddy used KansasCityBodyShop.com, ChicagoTowing.com and PittsburghGarage.com among others. You can view up to 10 comps.

Also, note that the domain name shows up for sale because I have it listed with AfternicDLS.

There is currently no bulk valuation tool available to the public.

Given GoDaddy’s brand recognition, I could see this tool being valuable when negotiating a sale with someone. For example, if you are buying a domain name and offering more than the valuation, giving a link to the appraisal might sway the seller. Likewise, if you are you selling a domain for less than the appraisal the tool could come in handy.

The appraisal tool recently helped me. Prior to the additional data being displayed, a domain seller found the appraisal beta through search. He sent me a valuation for the domain name I wanted to buy. I offered him about 60% of the valuation and he decided it was fair.

Of course, domain sellers might be frustrated when a potential buyer provides a link to a valuation that is much lower than the asking price. That’s when you explain the limitations of automated systems…


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

Latest domain news at DNW.com: Domain Name Wire.

The post Godaddy releases domain name appraisal tool to the public appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. GoDaddy drops Uniregistry domain names due to price hike
  2. It’s official: GoDaddy owns Host Europe Group
  3. GoDaddy gets patent for “Suggesting domain names based on recognized user patterns”
Categories: Domains

Weeds, Inc, which is suing to get Weeds.com, engaged in reverse domain name hijacking

Domain Name Wire - Thu, 11/30/2017 - 21:49

This doesn’t bode well for its lawsuit.

Earlier this week I wrote that Weeds, Inc. filed a cybersquatting lawsuit over the domain name Weeds.com. The lawsuit was filed despite a pending UDRP it filed with World Intellectual Property Organization (WIPO).

WIPO just handed down its decision in that case. Unsurprisingly, it found that Weeds, Inc engaged in reverse domain name hijacking by bringing the case.

Weeds, Inc. did not mention the UDRP in its lawsuit. The lawsuit was filed before the decision was handed down, and the WIPO panel noted the suit in its decision.

The panel determined that the domain name was not registered and used in bad faith. It called into question the timeline of Weeds, Inc’s trademark applications occurring after the current owner purchased the domain. While Weeds, Inc. claimed common law rights it didn’t provide much evidence of them, especially for a generic term. In one of its trademark applications, it even disclaimed the word “weeds”.

The panel noted:

In the Panel’s view, it does not seem probable that the owners of a Caribbean company that purchases and sells generic domain names, and generates revenue from them through relevant pay-per-click advertising links, would be aware of a regional weed-control company and find their brand an appealing target for cybersquatting.

This should be obvious to more than just the panel.

It also turns out that a vice president of Weeds, Inc. inquired about buying the domain name in 2005. It failed to mention this in its complaint.

In finding reverse domain name hijacking, the panel wrote:

The Panel notes that Complainant is represented by IP counsel. Thus is [sic] should have been quite clear from the outset that Respondent had registered a domain name consisting of a common, descriptive, dictionary word, before Complainant filed its application for the WEEDS mark.

In addition, it is well established that invoking a common law mark – as did Complainant – requires providing the Panel with concrete evidence of secondary meaning / acquired distinctiveness, which Complainant failed to submit.

Lastly, while Complainant contended that Respondent registered the disputed domain name primarily to sell it to Complainant, it made no mention of the fact that it was Complainant’s Vice-President who had first contacted Respondent to make an inquiry about the purchase of the disputed domain name.

For these reasons, the Panel finds that the Complaint is an attempt at Reverse Domain Name Hijacking.

Why did Weeds, Inc. file a federal lawsuit when it knew a decision in the UDRP was imminent? You can draw your own conclusion.

Weeds, Inc. was represented by Technology & Entrepreneurial Ventures Law Group, PC. The domain owner Innovation HQ was represented by Zak Muscovitch of Muscovitch Law P.C.

Weeds, Inc. might have a higher legal bill than it expected. While a U.S. court doesn’t have to give deference to a WIPO decision, a judge would certainly question why it should let this case move forward in light of the decision. Some companies have paid for filing reverse domain name hijacking cases.


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

Latest domain news at DNW.com: Domain Name Wire.

The post Weeds, Inc, which is suing to get Weeds.com, engaged in reverse domain name hijacking appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Ardyss Guilty of Reverse Domain Name Hijacking for Going After Distributor
  2. Law Firm Found Guilty of Reverse Domain Name Hijacking After Filing “Astonishing” Case
  3. WallStreet.com: panel rules reverse domain name hijacking
Categories: Domains

PodcastGuests.com adds expert guest directory and online one sheets

Domain Name Wire - Thu, 11/30/2017 - 19:08

An exciting announcement about my PodcastGuests.com service.

Over a year ago I created PodcastGuests.com, which is billed as “The HARO for podcasts”. This month I added new features to make it easier for podcasters to find new guests and for experts to get booked on podcasts.

PodcastGuests.com sends a weekly email to over 3,000 podcasters and experts to facilitate booking guests on podcasts. Each newsletter includes a list of podcasts that are seeking guests as well as their guest qualifications. Qualified experts click a button and fill out a pitch form that is sent directly to the podcaster.

The service has already facilitated thousands of guest booking introductions. It’s not uncommon for a featured podcast to receive over 30 guest inquiries when featured in the newsletter.

The rapid growth of the service led to a problem: podcasts had to wait a long time to be featured in the newsletter.

The new PodcastGuests.com expert directory solves this problem while also giving guest experts the ability to get booked on more shows. Now, podcasters can search the directory to find ideal guests for their shows. They can review the expert’s credentials and prior media appearances and then click a button to invite him or her on their podcast.

It’s also a way for experts to have podcasters come to them rather than waiting for the right opportunity to appear in the newsletter.

Guest experts can create a mobile-friendly “one sheet” in the directory. A one sheet is a short overview that experts use to pitch themselves to podcasts. Many experts have created one sheets in a cumbersome .pdf format. PodcastGuests.com offers a mobile-friendly online one sheet with links to prior guest appearances and social media.

While the core PodcastGuests.com service remains free, there’s a small fee for experts to create their one sheet in the directory. Fees start at $9 per month with an option for improved promotion for $29 per month.

Domain Name Wire readers get a 25% discount on monthly fees when they use the coupon code ‘dnw’ at signup.

 


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

Latest domain news at DNW.com: Domain Name Wire.

The post PodcastGuests.com adds expert guest directory and online one sheets appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Want to get booked on podcasts? Sign up for PodcastGuests.com
Categories: Domains

Etsy fails to get domain name Esty.com in cybersquatting complaint

Domain Name Wire - Thu, 11/30/2017 - 14:51

Panel makes the right decision but I understand why Etsy was upset.

Homemade goods and crafts site Etsy.com has lost a dispute it filed with the National Arbitration Forum to get the domain name Esty.com.

The case was doomed because the owner of the domain, PortMedia Holdings, registered it four years before Etsy started.

In ordinary circumstances, I would give Etsy grief for filing the case given that the domain was registered before the company existed. But, although the panel made the right decision because of the dates, I understand why Etsy was upset about this particular domain name.

As I wrote last month, Esty.com was parked and some of the traffic was sent to zero click landers with scams on them. Etsy listed a number of scam pages that the domain was forwarding to.

If you’re running a company and a lot of people intending to visit your site end up on a page that says their computer is infected with malware or they are tricked into downloading toolbars, you’d be very upset.

In this case the domain name owner said it was unaware of the zero click landers and fixed the problem as soon as the case was filed. This is believable; I suspect many domain owners aren’t aware of what parking companies are doing with their domain traffic.

I urge all domain name owners to ask their parking providers if they serve zero click and if there’s an option to turn it off. While zero click makes a lot of sense in theory, it seems that providers haven’t found a way to prevent scammers from using their services.

Jason Schaeffer and Ari Goldberger of ESQwire.com represented the domain name owner.


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

Latest domain news at DNW.com: Domain Name Wire.

The post Etsy fails to get domain name Esty.com in cybersquatting complaint appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Arena.com Owner Wins Domain Name Arbitration
  2. Louis Vuitton Loses Domain Dispute for Mobile Domain Name
  3. Panelist finds East End N.Y. Imports Inc. engaged in reverse domain name hijacking
Categories: Domains

Chinese man sues after his numeric domain names are stolen

Domain Name Wire - Wed, 11/29/2017 - 18:18

Lawsuit claims 11 domain names such as 0001.com were stolen.

Gong Fan of Shenzhen, China has filed a lawsuit (pdf) to recover 11 numeric .com domain names that he alleges were stolen from him.

According to the suit, Gong Fan is the original registrant of 0001.com, 6007.com, 00088.com, 10099.com, 00086.com, 98988.com, 88199.com, 00018.com, 00019.com, 00020.com and 00021.com. He registered the domain names between 1998 and 2004.

His Gmail account was compromised between August 22 and September 20 of this year and the perpetrator stole the domain names, he claims.

The case was filed in U.S. District Court in the Eastern District of Virginia, which is where .com registry Verisign is located. In similar cases, judges have entered default judgments when the thief didn’t respond and have ordered Verisign to transfer the domain names back to plaintiff.

Stevan Lieberman of Greenberg & Lieberman is representing the plaintiff.


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

Latest domain news at DNW.com: Domain Name Wire.

The post Chinese man sues after his numeric domain names are stolen appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Court returns stolen 224.com, 605.com and 452.com domain names
  2. Lawsuit filed to recover stolen OnlineMBA.com domain name
  3. Lawsuit filed to recover 6213.com, an allegedly stolen domain name
Categories: Domains

End user domain name sales up to $275,000

Domain Name Wire - Wed, 11/29/2017 - 17:52

From .com to .de to .Cloud, here are domain names end users bought over the past week.

There are some weeks where I have to really hunt to find the end user sales on Sedo’s sales list. Not this week.

Sedo had a number of great (and easy-to-identify) end user sales. One still has a bit of mystery, though. Who bought Spend.com for $275,000?

You’ll also notice that a lot of this week’s sales were to companies that own a country code domain name and wanted the matching .com domain name. Domain names are tricky for European companies given the importance of ccTLDs there. Jesper Knudsen and Jochen Kieler explained this on DNW Podcast #146.

Here’s the list of end user domain name sales from the past week at Sedo:

(You can view previous lists like this here.)

Spend.com $275,000 – I don’t know who bought it yet because the domain name is under Whois privacy. However, the buyer has switched the DNS to point to hosting company Linode and has installed WordPress. Keep an eye on this one.

EconomyBooking.com $30,000 – Car rental company Booking Group SIA operates EconomyBookings.com, so this was a defensive purchase for them.

Datenschutzbeauftragte.com €10,000 – This is German for “Data protection commissioner”. It was purchased by the owner of datenschutzvorfall, which is German for “data protection incident”. There’s already an operating website on the domain.

Robotics.cloud €8,950 – Redwood Software Inc offers “Plug & Play Robotics”.

Matt.de €8,800 – MATT optik is an eyewear company.

Limata.com €6,500 – Limata is a company that sells laser imaging systems.

SmarterClick.com $6,000 – Smarter Click Technology Ltd bought the .com to go with its SmarterClick.co.uk domain.

DTAD.com €5,000 – Not to be confused with DSAD.com, DTAD Deutscher Auftragsdienst AG bought the .com to match its DTAD.de domain name.

Jamble.com $4,995 – The domain has Whois privacy but the owner is developing some sort of chat or dating site.

ValleyHospice.com $4,570 – Valley is one of those geo terms that’s generic enough to apply to multiple places. In this case, Valley Health System in New Jersey.

SmartInvestors.com €4,500 – The buyer is creating a site that promises to uncover “Wall Street Gems Before They Become Giants”. I don’t know anything about the owner’s stock-picking prowess, but s/he’s a good domain picker.

Artoz.com $3,883 – Artoz Papier AG bought this domain to go with its Artoz.ch domain name.

BetTicket.com $3,735 – Total Gaming Solutions BV.

Reddit.ch €3,141 – Reddit now owns its Swiss country code domain.

Dadmin.com $3,000 – The buyer has a store selling t-shirts, hats etc. and says dadmin stands for jobs dads do before they can relax.

Denta.com $2,750 – Thiele Capital GmbH.

Alle.co $2,500 – A CSC Corporate Domains customer. I’m guessing Ally bank.

Moonlight.us $2,000 – Moonlight Mountain Gear AS sells skis, headlamps and bindings. It seems to specialize in nighttime skiing.


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

Latest domain news at DNW.com: Domain Name Wire.

The post End user domain name sales up to $275,000 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. 18 end user sales from $750 to $17,500
  2. Big-name end user domain purchases, including a .org for $55,000
  3. End user domain name sales including new TLDs and the ACLU
Categories: Domains

Psst…here’s what Amazon.com is about to announce at AWS re:Invent

Domain Name Wire - Wed, 11/29/2017 - 14:27

Domain name registrations provide a hint of what’s to come.

Yesterday I wrote about some domain name registrations made by Amazon.com that foreshadowed product announcements the company is making at AWS re:Invent. The company registered more domain names today that are likely for announcements that will be made during the remainder of the week. Let’s take a look:

AWS Brimstone – I can’t find anything in Google related to Brimstone, so this new service will likely be announced this week at re:Invent
amazonawsbrimstone.com
amazonbrimstone.com
awsbrimstone.com

AWS Deep Lens – This one has me puzzled.
amazonawsdeeplens.com
amazonawsdeeplenscamera.com
amazonawsdeeplensvideo.com
amazondeeplens.com
amazondeeplenscamera.com
amazondeeplensvideo.com
awsdeeplens.com
awsdeeplenscamera.com
awsdeeplensevideo.com
deeplenscamera.com
deeplearningenabledvideocamera.com
deeplensvideo.com

AWS Fargate – Another new brand name/service that should be announced this week.
amazonawsfargate.com
amazonfargate.com
awsfargate.com

AWS IoT – There are several things in here for IoT, including “1 click”, analytics, and a security product.
amazonawsiot1-click.com
amazonawsiot1click.com
amazonawsiotanalytics.com
amazonawsiotdevicedefender.com
amazoniot1-click.com
amazoniot1click.com
amazoniotanalytics.com
amazoniotdevicedefender.com
awsiot1-click.com
awsiot1click.com
awsiotanalytics.com
awsiotdevicedefender.com

AWS Private Link – I can’t find anything on Google about this yet.
amazonawsprivatelink.com
amazonprivatelink.com
awsprivatelink.com

AWS Rekognition Video – Amazon announced this service for recognizing faces in video a few months ago. Perhaps some new announcements this week.
amazonawsrekognitionvideo.com
amazonrekognitionvideo.com

AWS Sagemaker – Your guess is better than mine.
amazonawssagemaker.com
amazonsagemaker.com

AWS Transcribe – Looks like a transcription and translation service on AWS.
amazonawstranscribe.com
amazonawstranslate.com
amazontranscribe.com

AWS T2 Unlimited – Are unlimited plans coming to EC2 T2 instances?
amazonawst2unlimited.com
amazont2unlimited.com

Amazon AWS Time Sync Service – Likely a small produce announcement.
amazonawstimesyncservice.com
amazontimesyncservice.com

AWS Kinesis Video Streams – Kinesis Streams has been available for a while, but perhaps they are adding new video functionality.
amazonawskinesisvideostreams.com
amazonkinesisvideostreams.com
awskinesisvideostreams.com

Amazon AWS EKS – Likely “EC2 Container Service for Kubernetes”
amazonawseks.com
awseks.com

AWS Free RTOS – That stands for “real time operating system”
amazonfreertos.com
amazonawsfreertos.com
awsfreertos.com

AWS Signer – AWS already has a lot of signing functionality.
amazonawssigner.com
amazonsigner.com

Amazon Duels – There was only one domain registration for this one, and it doesn’t mention AWS. Perhaps it is Jeff Bezos dueling his neighborn Bill Gates for richest man in the world.
amazonduels.com

Amazon.com also registered additional domain names related to new services I discussed yesterday, including Neptune (with graph analytics) and Elemental.


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

Latest domain news at DNW.com: Domain Name Wire.

The post Psst…here’s what Amazon.com is about to announce at AWS re:Invent appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Telepathy scores $40,000 from reverse domain name hijacking case

Domain Name Wire - Tue, 11/28/2017 - 18:52

HVAC company agrees to pay $40,000 after filing cybersquatting complaint in abuse of the UDRP.

In May 2017, Nat Cohen’s domain name investment firm Telepathy successfully defended its domain name AirZone.com in a UDRP. A World Intellectual Property Organization (WIPO) panel found that Corporacion Empresarial Altra S.L., which owns the domain name AirZone.es, had engaged in reverse domain name hijacking by filing the case.

WIPO panels cannot hand out monetary penalties for reverse domain name hijacking…but courts can. So Telepathy filed suit.

It has entered into a settlement agreement (pdf) with the HVAC company. The agreement requires Corporacion Empresarial Altra S.L. to pay Telepathy $40,000. Telepathy has recovered money for reverse domain name hijacking in other cases, too.

Telepathy finds itself on the receiving end of lots of frivolous UDRPs because of its high-quality portfolio of valuable domain names (including many three-letter .coms). Lawsuits filed against perpetrators should make companies think twice before filing a UDRP against Telepathy.

See more reverse domain name hijacking cases on RDNH.com.


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

Latest domain news at DNW.com: Domain Name Wire.

The post Telepathy scores $40,000 from reverse domain name hijacking case appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Nat Cohen wins reverse domain name hijacking charge against spa for SHA.com
  2. Telepathy Wins Reverse Domain Name Hijacking Charge Against 3-D Company
  3. Nat Cohen sells LGG.com for $175k to company that filed UDRP against the domain name
Categories: Domains

24 domain names bought by end users

Domain Name Wire - Tue, 11/28/2017 - 16:15

List includes a five-figure new TLD sale and more.

I’m a bit late getting out last week’s end user domain name sales report due to the Thanksgiving holiday. But it’s a great list that you’ll definitely want to review.

Sedo had a number of solid end user sales, including one to the $85 billion (market cap) oilfield services company Schlumberger. They also sold a .shop domain for five figures.

This week I also have a handful of sales that PerfectName.com sent to me. Some of these sales took place a month or two ago, but are great end user examples.

Enjoy the list…

(You can view previous lists like this here.)

Sedo

OneStim.com $18,000 – Oilfield services giant Schlumberger (NYSE: SLB) bought this for a joint venture called OneStim.

Container.shop €10,000 – Braun Container Handels-GmbH. This company does not own Containershop.com.

DVSystems.com £9,995 – DV Systems Inc. is an air compressor manufacturer in Canada.

TeMana.com €8,880 – Temana is a “skin brightening” cosmetic sold by Morinda.

GetBioFuel.com $7,000 – Although it’s not immediately clear when you visit the site, the buyer is Growth Energy, a trade group promoting ethanol consumption. It’s a search site to find E15 and E85 fuel.

Kontxt.com €6,700 – RealNetworks bought this for its Kontxt text messaging platform.

MediaSales.com €6,476 – Wedel Software is a media sales software company.

Bventure.com $5,800 – BVenture is short for Business Venture, and it is owned by a consulting company of the same name.

CapitalProductions.com $5,000 – Capital Management Group Inc. is an event planner in Arizona.

ZappingTV.com $4,046 – El Telon is a TV streaming app.

Descargar.org €3,500 – Descargar is Spanish for ‘download’. It is being used for an app download site.

ConstructionLogistics.com $3,300 – O’Neil & Brennan Site Services and Logistics.

La-Vita.com $3,220 – LaVita GmbH is a nutrition service that uses the domain name LaVita.de.

GTC.co $3,000 – Global Tour Creatives bought its acronym in .co.

GVPro.com $2,980 – GVPro sells branded podiums, chairs and scorer tables for sports teams.

OutOf.com €2,750 – Out of s.r.l. in Italy.

GoCougs.com $2,500 – Brigham Young University. Its mascot is the cougars.

PersonalTrainer.net $2,500 – Fred Liberatore is a personal trainer in Australia.

MeritOnline.com $2,200 – Merit is casino company.

PerfectName:

JPJ.com $100,000 – Jackpotjoy Plc, an online bingo company.

CEX.com $100,000 – The Whois is private but there’s now a cryptocurrency exchange on the site.

MSSI.com $20,800- – Medical Staffing Solutions Inc. in Wisconsin.

Knows.com $24,791 – KnowS IT GmbH, which uses Knows.ch.

Super7.com $18,577 – (PerfectName) Super7 Retail, Inc, a site that sells retro goods.


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

Latest domain news at DNW.com: Domain Name Wire.

The post 24 domain names bought by end users appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. 18 end user sales from $750 to $17,500
  2. Big-name end user domain purchases, including a .org for $55,000
  3. End user domain name sales including new TLDs and the ACLU
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.