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.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.

15+ New Spam Emails, 9 Robocalls, 6 Spam texts within 24 hours of registering a domain

Domain Name Wire - Fri, 01/19/2018 - 15:14

Guy who registers domain name gets an unpleasant surprise.

A GoDaddy customer posted this complaint on GoDaddy’s community forums yesterday. I’m posting it in its entirety with my annotations.

GoDaddy FAIL!!!!!! – Bought A Domain And In 24hrs – 15+ New Spam Emails – 9 Robocalls – 6 Spam SMS’s

This is not the first domain name I’ve purchased, I’ve owned dozens over the years… but this is the FIRST time this has happened with such frequency and inconvenience.

It is getting worse. Out of control. I blame a number of companies that have popped up offering very cheap access to Whois data for newly registered domains and marketing it as a way to get fresh leads.

I don’t care if WHOIS is publicly available, GoDaddy MUST provide a free service to counter the increase in robocalls, spam mail, and spam SMS. I’ve received dozens in less than 24hrs of purchasing a domain name through GoDaddy.

I’ve read the threads and GoDaddy passes the blame on 3rd parties and claims to have no control over this. I say that’s a load of rubbish. GoDaddy should provide, as a FREE service, the ability to use an alias email and phone number for registrars.

While some registrars offer this for free, I bet DomainsByProxy is a big revenue generator. It’s also worth pointing out that running a proxy or privacy service isn’t free. There are some pretty big headaches that come along with operating these services. If GoDaddy or any other registrar offers proxy for free, they will likely increase the prices they charge to register a domain.

GoDaddy is, however, getting ready to mask email and phone numbers from port 43 whois lookups starting January 25. Will this reduce the amount of spam? I hope so.

There is also no clear directions on how to go about removing one’s information from robocallers once your WHOIS information goes public.

Sorry. Once it’s in, you’re screwed. These companies doesn’t respect any Do Not Call lists, either.

I am seriously mad at GoDaddy for wasting my time having to deal with all this and having to write this post. And WHY must a phone number and email address be required in the first place. If it’s a law then that has to change because robocallers and these spamming **bleep**tards are getting more sophisticated and ambitious.

ICANN. But, historically it was never an issue. There are good reasons to have this info public as long as people aren’t abusing it.

I really hope GoDaddy can address this problem so many people are having!!!!

I think the port 43 change will help. GoDaddy also sued one of the spammers.


© 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 15+ New Spam Emails, 9 Robocalls, 6 Spam texts within 24 hours of registering a domain appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. GoDaddy Allows Transfers After Whois Changes
  2. GoDaddy’s 60 Day Transfer Lock Closer to Termination
  3. Namecheap leaps up .com chart as PDR falls
Categories: Domains

MicroStrategy defends its Glory (.com)

Domain Name Wire - Thu, 01/18/2018 - 17:27

Tech company fends off Japanese group that filed cybersquatting complaint.

$1.5 billion dollar tech company MicroStrategy (NASDAQ: MSTR) has successfully defended the domain name Glory.com in a cybersquatting dispute.

MicroStrategy has a vast portfolio of high-quality domain names including alert.com, hope.com, mike.com, speaker.com and voice.com. It’s not clear what it intends to eventually do with many of its domains, but the quality and its unwillingness to sell sometimes attracts challenges.

The company bought Glory.com for $115,000 in 2003.

Glory Ltd. of Himeji, Japan tried to buy the domain name but was rebuffed by MicroStrategy. MicroStrategy offered to sell the domain for more than $10 million in an effort to get Glory Ltd to stop bothering it.

Glory Ltd., which uses the domain Glory.co.jp, filed a UDRP after its efforts failed.

A three-person World Intellectual Property Organization panel determined that Glory Ltd. did not demonstrate that MicroStrategy registered and used the domain in bad faith.


© 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 MicroStrategy defends its Glory (.com) appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Cybersquatting complaint filed against MicroStrategy’s Glory.com domain
  2. Cybersquatting lawsuit filed over domain name registered 16 years before plaintiff’s use
  3. Mrs Jello sues to block Camilla.com transfer
Categories: Domains

I’m bullish on domain names

Domain Name Wire - Thu, 01/18/2018 - 15:49

While other assets are currently overvalued, domain names aren’t.

Asset prices have been quite frothy for a long time. They were high a year ago and then they shot much higher over the past year.

Sure, sentiment might be positive. Asset prices might continue to go up. But when you look at historical valuation metrics of certain assets such as stocks, they are trading at very high prices even when you bake in tax breaks and a rosy outlook. Then there is a virtual currency created as a joke that is valued at a billion dollars.

Regardless of where you think asset prices are headed from here (and which assets will outperform), I feel very comfortable with where domain name prices are. The irrational betting that took place during the Chinese boom has more or less subsided, leaving us with investor prices that are below what end users are willing to pay. The domain market still has the important characteristic of having an investor market and an end user market, with the latter willing to pay more than how much it costs to invest in domains.

This isn’t to say that all domain bets will pay off. Even if you’re selling domains for more than you bought them for you need to consider your holding time and the domains you don’t sell.

But I believe that domain names have an underlying use and value, and I don’t think they are overvalued right now. There have been times I’ve scratched my head at domain valuations but that’s not the case at the beginning of 2018.

I’m bullish on domain names.


© 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 I’m bullish on domain names appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. 2008 Domain Name Wire Survey Now Open
Categories: Domains

20 End user domain name sales including lots of cryptocurrency domains

Domain Name Wire - Wed, 01/17/2018 - 20:58

Cryptocurrency prices are fluctuating like mad, but crypto fans are buying domain names in droves.

The cryptocurrency and blockchain boom has definitely had an impact on relevant domain names purchases. Sedo’s sales list this week includes many blockchain related domain names. There were plenty of other crypto domains that I couldn’t tie to an end user.

But the top spot on the end user chart this week belongs to HappyMath.com, a domain name purchased by a Chinese education company.

Let’s take a look at 20 sales that took place at Sedo over the past week with end user buyers:

(You can view previous lists like this here.)

HappyMath.com $35,000 – Chinese education company OneSmart.

Otravo.com $18,500 – Otravo BV says its name stands for Online Travel Organization. Its main website is Otravo.nl.

Singpay.com $10,000 – Beijing singpay technology co., ltd bought the .com to go with Singpay.com.cn.

Kraken.co $10,000 – Bitcoin exchange Kraken bought the .co to go with its .com.

NovaHealthSystem.com $9,850 – Nova Southeastern University.

B00.com €6,300 – This doesn’t look like a domain investor purchase. The owner also has B00.nl, which has a message saying “we will be back soon.”

OfficePhone.com $7,500 – PhoneSpeak bought this category domain name.

MSmotors.com €5,000 – MS Motors in France uses the domain name MSmotors.fr.

TheRepublik.com $5,000 – Marketing firm The Republik Companies owns TheRepublik.net.

Payger.com $5,000 – The company is creating a blockchain payments system.

Zipper.io $4,999 – Another blockchain-based company.

MyHeartMonitor.com $3,900 – CardioNet, Inc sells heart medical equipment.

BitcoinInc.com $3,750 – The domain name resolves to a page that says Bitcoin Inc is “The Crypto Company”.

Rightbase.com $3,500 – Rightbase Limited looks to be starting a real estate website.

IslandRoofing.com $3,500 – The owner of IslandRoofingLLC.com smartly bought the version without LLC.

Bathlux.com $3,500 – Bathlux sells bathroom accessories.

Vinomio.com $3,000 – VinumRegio GmbH is an Italian wine and gourmet food company.

FortressCoin.com $2,650 – Victory Park Capital invests in alternative credit.

IncFast.com $2,495 – Corporate Filings LLC.

Schwartzapfel.org $2,880 – Schwartzapfel Partners P.C. I can understand why their main website is FightingForYou.com instead of the last name.


© 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 20 End user domain name sales including lots of cryptocurrency domains appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. USA Today buys domain for new sports site (and 19 other domains)
  2. What domain names eBay and GoFundMe bought last week
  3. Kasperksy buys Unhackable.com (and other end user domain name sales)
Categories: Domains

RRPproxy launches new domainer focused UI

Domain Name Wire - Wed, 01/17/2018 - 19:38

This is a sponsored post+ from our friends at RRPproxy.

Domain registrar Key-Systems extended the focus of its reseller business RRPproxy particularly to domainers by launching a new responsive web interface optimized for any users with mid-size up to large domain portfolios. Along with the UI change, RRPproxy offers .com domains for $8.13 to new customers until March 31 using the promotion code BRANDnew.

Center of the interface reinvention is a bunch of usability features intended to “bring domain management to the next level“, according to Key-Systems’ CEO Alexander Siffrin. The UI comes up with a customizable dashboard using widgets for different products and processes, right-click functionality, drag&drop, pop-ups, automated processes and extensive dependency handling.

“We used these means, so that customers can reach their destination as fast as possible and then stay as long as needed to carry out their often complex tasks without needing to switch to another destination”, Siffrin explained. Examples for these means are the direct access of filters through right-click in the menu, value dependencies during the registration of TLDs with special regulations, drag&drop for taking over contacts or the automated generation of auth codes for any TLD.

Predefined domain overviews include registered domains, pending transfers, pending owner changes as well as pending restores to avoid the unintended loss of domains. All lists allow the selection of several domains for a bulk update, the definition of column headers and sorting according to column headers or tags. Domain tags consisting of any keywords as well as default or self-defined TLD categories are there to organize domains. Presets are available to specify settings for e.g. contact, name servers, tags, domain period etc. and apply them to domain portfolios.

The interface supports bulk processes for domain search, registrations, renewals, deletions, transfers as well as domain updates, supported by the list and filter options. Monetization includes purchase and sale at Sedo. Furthermore, RRPproxy offers the sale of expiring domains at SnapNames, and domain parking with ParkingCrew as well as a Premium Domain System for fast access to new gTLD premium names.

With the new web interface, RRPproxy also established several security features, among them 2-factor-authentication for login and domain lock, the limitation of IP addresses for API commands and the encrypted display of security related information such as passphrases and auth codes by default.

Being a business unit of the German-based registrar Key-Systems, RRPproxy is part of the Luxembourgian KeyDrive group, to which also the US registrar Moniker belongs. Same as RRPproxy, Moniker recently relaunched their web interface, however strengthening the focus on retail business. “While Key-Systems’ retail portal domaindiscount24 mainly aims at European customers, Moniker is the equivalent for the North American market”, states Key-Systems’ CEO Alexander Siffrin. “From a strategic point of view for the KeyDrive group, RRPproxy is the right address for resellers and domain investors.”

+Sponsored Posts are provided by our supporters. Domain Name Wire’s editorial staff did not contribute to this post.


© 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 RRPproxy launches new domainer focused UI appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

What to do at NamesCon 2018

Domain Name Wire - Wed, 01/17/2018 - 17:18

Here are some sessions and events you won’t want to miss.

Group photo from NamesCon 2017. Photo courtesy NamesCon.

This year’s NamesCon event, taking place January 28-January 31 at the Tropicana in Las Vegas, has a slightly different structure than prior years. There’s more activity on Sunday and the conference ends earlier on Wednesday, which is followed by an “Unconference” Wednesday afternoon.

I’ve reviewed the agenda to look for sessions that you won’t want to miss. I’m particularly excited to see so many speakers I’m unfamiliar with. NamesCon has brought in new faces, so it won’t be “oh yeah, I saw this same panel the past three years!”

One quick tip before getting to the sessions: there’s a new restaurant (Robert Irvine’s Public House) at the Tropicana where the sportsbook used to be. This should alleviate a big problem with the Trop–a lack of food.

Also, if you don’t have tickets yet, you can get them for half off.

Women in Domaining Dinner – There are many more women in the domain name industry than five years ago, but it’s still a male-dominated industry. I highly recommend all women attending NamesCon to attend this event. RSVP required. Sunday 5-7pm.

Megadeth’s David Ellefson – You can wake up by 10 am on Monday to see a rock star, right? I am not a rock star, but I will be interviewing Grammy Award-winning Megadeth bassist David Ellefson Monday morning. Ellefson and Megadeth were leveraging the internet to connect with their fan base well before there was such as thing as Facebook or Twitter. In fact, Megadeth was the first band to create a website. Learn about how Ellefson connects with fans on social media and how you can apply these concepts to your business. Monday 10-10:45am.

An actual blockchain use case – There’s plenty of hype around blockchain. I’ve heard many stories about how it can change industries, but these have been light on details. So a session between Donuts’ Tim Favia and Netki’s Justin Newton about how Netki is leveraging DNS for blockchain should be interesting. Monday 12-12:45pm.

Thinking about generations – WPEngine’s Lisa Box discusses how younger generations want their habits to be anticipated. Based on research undertaken by The Center for Generational Kinetics, an awesome company here in Austin. Monday 2-2:45pm.

WaterNight Charity Dinner – Waternight has a different format this year, and tickets are required. Monday 6:30-10:30pm.

Lessons from a big domainer – GoDaddy has become a big domainer, and you can find out what GoDaddy GM Paul Nicks has learned now that the company owns so many domains. Or, listen to my podcast about it. Tuesday 11-11:45am.

Top domain brokers – Last year Escrow.com presented awards to the top ten individual brokers based on transactions facilitated by Escrow.com. It will be interesting to see who wins this year. Tuesday 3:30-4pm.

Going once, going twice – It’s always worth stepping in for the domain name auction. Just don’t plan on it starting on time…they never do. Tuesday 4pm-7pm.

ICA Dinner – You should go. Tickets are still available. Tuesday 6-9pm.


© 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 What to do at NamesCon 2018 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. NamesCon domain name conference may sell out
  2. NamesCon acquired by WorldHostingDays
  3. Two scheduling tools to make NamesCon a success
Categories: Domains

How to grow your audience with an Amazon Giveaway

Domain Name Wire - Mon, 01/15/2018 - 19:33

Amazon has a simple and low-cost way to grow your audience.

One of the lesser-known but more affordable ways to promote your business and grow your audience is to create an Amazon Giveaway.

An Amazon Giveaway is a sweepstakes in which you create the parameters and Amazon handles the winner selection and fulfillment. Here’s how to set one up.

1. Visit the product page on Amazon that you’d like to offer in your giveaway. You can select just about any product on Amazon. Then scroll down to the link to “Set up an Amazon Giveaway”:

This will bring you to a page in which you fill out the contest details. Here are the most important elements:

Giveaway type: My suggestion is for Amazon to randomly select one entrant at the end of the seven day contest. However, you can also choose: first x entrants win, every x entrants win, or random instant win.

Entry requirements: This is the point of creating the giveaway. Currently, you can ask entrants to:

  • Follow you on twitter
  • Tweet a message (that includes a link to the giveaway)
  • Watch a video short or YouTube video
  • Follow an author (great for authors with books on Amazon)
  • Answer a poll

For example, let’s say I want to get more people that read DNW to follow me on twitter. I would create the giveaway and require that people follow me on twitter in order to be entered to win.

Discoverability: This is one of the most important decisions you’ll make. You can decide to keep your giveaway private or make it public on Amazon’s site.

If you want to just get a lot of numbers even if they are low quality, then choose to make it public. You’ll get a lot of people to follow you on twitter or watch your video.

However, if you want quality, you might want to make it private. In my DNW example, I’d make it private and post about it on the site. Then anyone who saw the message on my site could enter the contest if they followed me on twitter, but I wouldn’t get a lot of random sweeptakes junkies following just to have a chance to win.

The decision to make it private/public depends a lot on your goals and your audience.

Here are some ways you can use Amazon Giveaways:

  • Make people watch a short video about your product/service
  • Get people to tweet a message promoting your company (note: it will be labeled #giveaway with a link to the giveaway)
  • Promote a product or book you created
  • Answer a poll question

See these currently-running contests to get some inspiration.

 


© 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 grow your audience with an Amazon Giveaway appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

WordPress.com and domain names – DNW Podcast #169

Domain Name Wire - Mon, 01/15/2018 - 16:30

Kellie Peterson talks about what WordPress.com is seeing as a domain name registrar.

WordPress.com operates a domain name registrar with a unique characteristic: almost all of the domain names it registers are for end users that put them to use with a live website. Kellie Peterson, who manages the registrar, explains what she is seeing with both new top level domains and .com and discusses user behavior. Also: .Web is (maybe) a go, GoDaddy changes Whois, Equifax domains and more.

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


© DomainNameWire.com 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 WordPress.com and domain names – DNW Podcast #169 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. How End User Domain Buyers Think – DNW Podcast #134
  2. Paul Nicks of GoDaddy – DNW Podcast #160
  3. Building web businesses with Peter Askew – DNW Podcast #163
Categories: Domains

Voys B.V. tries to hijack Voys.com domain name

Domain Name Wire - Mon, 01/15/2018 - 15:34

Company that uses Voys.nl tried to get Voys.com through a UDRP.

A Dutch telecom company has been found to have engaged in reverse domain name hijacking for bringing a cybersquatting complaint against the owner of Voys.com.

A three-person World Intellectual Property Organization panel determined that it filed its case in abuse of the policy. Among other things, Voys B.V. failed to mention three overtures made by the company or its representatives to buy Voys.com before filing the UDRP.

The panel took particular offense to Voys B.V.’s allegation that:

The domain name voys.com has never been used by Respondent after its registration. Since 2007, this domain name is even offered for sale. A copy of the webpage is provided as Annex 6. From this, it is evident that Respondent does not have a legitimate interest in the domain name voys.com.

To which the panel replied:

This is an extraordinary statement. It incorrectly assumes that (1) non-use of a domain name of itself prevents the registrant from acquiring a right or legitimate interest and (2) registration of a domain name for no reason other than to sell it necessarily deprives the registrant of a right or legitimate interest.

The owner of the domain name is an investor that specializes in four-character domain names, which is why he owns the domain name. The panel found no evidence that he targeted the complainant when he purchased Voys.com.

Perhaps one of my Dutch-speaking readers can chime in, but I get the impression from Voy’s website Voys.nl that it is in favor of internet and telecom freedom. This makes its decision to file an RDNH case quite surprising.


© 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 Voys B.V. tries to hijack Voys.com domain name appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. $50,000 penalty for filing a frivolous UDRP!
  2. Zak Muscovitch gets reverse domain name hijacking win
  3. Canadian firm Obero tries to Reverse Domain Name Hijack domain name
Categories: Domains

Sandeep Ramchandani named CEO of Radix

Domain Name Wire - Sun, 01/14/2018 - 21:18

Sandeep Ramchandani replaces Bhavin Turakhia as CEO.

New top level domain name registry Radix has named Sandeep Ramchandani as its CEO. He was previously the vice president and business head for business.

Bhavin and Divyank Turakhia founded and funded the company. Bhavin was acting as CEO until now.

Radix operates nine top level domain names that generated over $12 million in total revenue in 2017. The company’s domain names include .online, .store, .tech, .website, .space, .press, .site, .host and .fun.


© 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 Sandeep Ramchandani named CEO of Radix appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Radix serving up Grilled Cheese at SXSW
  2. See .Online ads in San Francisco
  3. Radix to “rent” some premium domains by the month through Undeveloped
Categories: Domains

This GoDaddy Premium Domain change could help you sell a lot more domains

Domain Name Wire - Sat, 01/13/2018 - 18:07

GoDaddy is testing how it displays domain names listed for sale through Afternic/GoDaddy Premium Listings.

I received an offer on Sedo for one of my domain names this morning. Whenever I receive an offer on a domain, my first stop is GoDaddy where I search for the domain to see if I have a “buy now” price on it. Searching for the domain at GoDaddy informs me if I have a GoDaddy Premium Listing or Afternic listing with a buy now price.

Whenever a domain is listed with a buy now price through GoDaddy’s network, it shows up as available at the top with a premium price. It usually looks something like this:

But when I searched today I found that some of the listings looked like this:

It appears GoDaddy is split testing premium domain notices to see which works better. I also saw some that looked like the old lander but had a phone number as well.

This updated notice pulls in some info from GoDaddy’s new appraisal tool to explain why the domain name is valuable. It also has a prominent phone number in case people have questions about buying the domain. It also has a link to this video that explains why premium domains are worth more.

I think this new for sale notice will perform much better than the old one, but it’s wise of GoDaddy to split test this to make sure.


© 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 This GoDaddy Premium Domain change could help you sell a lot more domains appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Here’s why GoDaddy – Donuts deal makes a lot of sense
  2. GoDaddy adding 435 TLDs to domain name aftermarket
  3. How GoDaddy “uses this one simple trick” to get 56,000 more registration years per month
Categories: Domains

Notable NameJet sales from December

Domain Name Wire - Fri, 01/12/2018 - 18:18

Here are some domains that sold on NameJet last month that caught my eye.

NameJet sold 141 names for $2,000 or more last month, totaling nearly $860,000 in sales. Some of the better names came courtesy of Tucows’ domain portfolio. Tucows is a part owner of NameJet.

Here are some of the notable sales from last month.

Protege.com $52,000 – This will be a great brand for a company at some point and it will sell for a lot more. It’s a fair price for a competitive domain investor auction.

Creek.com $39,088 – I’m sure a lot of companies use a name with Creek in them. Not as strong as Protege.com but still good. This domain was sold by Tucows.

Veggies.com $22,088 – At first blush this domain seems limited to produce companies and industry groups that have horrible domain names. That’s a pretty long list, though.

MoneySmart.com $21,100 – This 1995 expired domain has lots of potential buyers. Google it and you’ll see that both the U.S. and Australian governments have programs called Money Smart, as do many private companies.

Locomotion.com $13,555 – Wow, this was a true deletion from a domain Sony previously owned.

Blocking.com $6,701 – Did the blockchain craze boost the price of this domain? A great domain for a blockchain-focused site.

Aerodynamic.com $4,999 – A solid one-worder with a positive connotation.

Tufts.com $4,988 – This domain came from Tucows’ NetIdentity portfolio. The buyer is forwarding it to Tufts.edu.

DrugWar.com $3,499 – This will never be a company brand, but so many journalism and entertainment companies might want to buy this domain.

www.ws $2,600 and ip.ws $2,515 – These are notable for the top level domain and presumably traffic they get.


© 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 Notable NameJet sales from December appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. A great week for domain sales. Here are some you might want to buy
  2. 10 notable NameJet sales from last month
  3. 10 notable NameJet sales last month including PuffDaddy.com
Categories: Domains

GoDaddy to start masking some Whois data through Port 43

Domain Name Wire - Fri, 01/12/2018 - 14:26

Masking should limit phone calls, texts and emails based on Whois information.

GoDaddy sent a notice to customers today notifying them that it will start masking some Whois data when it is requested through Port 43 Whois lookups. Port 43 is often used for bulk Whois lookups and is how many of the Whois spammers get their data.

The registrar will begin masking a registrant’s first name, last name, email and phone number.

It’s important to note that this information will still be available if you go through GoDaddy’s web-based Whois. It will also be available for people who have whitelisted Port 43 access with GoDaddy. Also, customers can opt-out of having their information masked.

The move is designed to cut down on the amount of spam GoDaddy customers receive. GoDaddy recently filed a lawsuit against a group of people it says are spamming its customers with offers of web services.

I suspect there will be some pushback from groups that use this data who will argue that GoDaddy is required to provide full Port 43 access. The reaction will be particularly interesting in light of ICANN’s decision to be lax on contractual Whois requirements due to the European Union’s General Data Protection Regulation.

The masking will begin January 25.


© 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 to start masking some Whois data through Port 43 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. How GoDaddy “uses this one simple trick” to get 56,000 more registration years per month
  2. Godaddy releases domain name appraisal tool to the public
  3. Tracking Whois Searches to Decide Domain Renewals
Categories: Domains

Namecheap leaps up .com chart as PDR falls

Domain Name Wire - Thu, 01/11/2018 - 19:23

There was movement on the top .com registrars rankings in the most recent ICANN report.

ICANN has published the latest official .com transactions report from Verisign, which includes data by registrar for September 2017.

Here are the top registrars in terms of new .com registrations for September. Namecheap lept to #3 on the chart. It registered its typical number of .com domains but PublicDomainRegistry’s registrations plummeted, pushing Namecheap up the list.

1. GoDaddy* 886,189
2. Tucows** 184,234
3. Namecheap 125,162
4. HiChina 120,405
5. Bizcn.com 109,715

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 +126,111 (compared to +34,959 in August)
2. GoDaddy +11,482
3. MAFF Inc (XZ.com) +8,277
4. Epik +7,746
5. NameSilo +6,450

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

1. Ename -49,243 (I assume this accounts for some of HiChina’s inbound transfers)
2. EIMS.cn -17,497
3. Domain.com -13,512
4. DNS.com.cn -12,676
5. PublicDomainRegistry -8,418

*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 Namecheap leaps up .com chart as PDR falls appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. .Com Winners & Losers Update
  2. Chinese registrars lose of lot of .com, but HiChina picks up domains from others
  3. The Latest .Com Winners & Losers
Categories: Domains

DNW Top Stories of December

Domain Name Wire - Thu, 01/11/2018 - 17:33

Miss something on Domain Name Wire during the holiday madness? Here are the top five stories published last month, ranked by views:

1. Thousands download fake GoDaddy app in Google Play store – A fake GoDaddy app was available for only a few days, but GoDaddy says thousands of people downloaded it.

2. DowDuPont will likely name its agriculture business Corteva – The company registered lots of domain names for Corteva.

3. Is Amazon preparing OpenTube to compete with Google’s YouTube as companies spar? – Before the company applied for trademarks it registered domain names suggesting a rival service.

4. Amazon launches .Bot – It’s restricted to verified bot developers.

5. Court orders Tucows to transfer 3.2 million domains to Namecheap – The registrars are fighting over the correct method to transfer domains from Enom’s reseller platform.

And these are the podcasts I published last month:

#163 – Building web businesses with Peter Askew
#164 – Domain investing with Shane Cultra
#165 – Soeren von Varchmin
#166 – 2018 DNW Predictions Episode


© 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 DNW Top Stories of December appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Equifax registers domains for new credit locking services

Domain Name Wire - Thu, 01/11/2018 - 16:34

Company that exposed personal data gears up for new credit protection products.

Equifax, the company that handed your personal credit data to hackers, has registered at least 100 new domain names related to credit locking services the company plans to offer.

On its website, Equifax promises a new “Lock & Alert” service that will launch at the end of this month. The company’s domain registrations give more insight into what it plans to offer.

Its Lock & Alert service will be free for life, the company promises. But I suspect it will be somewhat like Transunion’s credit lock service: the goal is to eventually extract more money from you for additional services.

Consider domains like equifax2bureaulock.com and equifax3bureaulock.com that suggest you’ll be able to order a credit lock at all three bureaus through Equifax.

The company also registered domains for comparing credit locks vs. credit freezes, e.g. equifaxfreezeversuslock.com. Perhaps the company wants to offer the free freeze service so that it can charge again for its locking service.

Here’s a list of 100 domains Equifax registered:

Domain 2blockequifax.com 2bureaulock.com 2bureaulockequifax.com 3blockequifax.com 3bureaulock.com 3bureaulockequifax.com creditalertequifax.com creditalertsequifax.com creditalertserviceequifax.com creditalertservicesequifax.com creditfreezeequifax.com creditlockandalert.com creditlockandalertequifax.com creditlockandalerts.com creditlockandalertsequifax.com creditlockequifax.com creditlockprotectionequifax.com creditreportlockequifax.com equifax2block.com equifax2bureaulock.com equifax3block.com equifax3bureaulock.com equifaxcreditalerts.com equifaxcreditalertservice.com equifaxcreditalertservices.com equifaxcreditlock.com equifaxcreditlockandalert.com equifaxcreditlockandalerts.com equifaxcreditlockprotection.com equifaxcreditreportlock.com equifaxfreecreditlock.com equifaxfreelock.com equifaxfreelockforlife.com equifaxfreezeandalert.com equifaxfreezeandalerts.com equifaxfreezecreditreport.com equifaxfreezemycredit.com equifaxfreezeversuslock.com equifaxfreezevslock.com equifaxfreezeyourfile.com equifaxhowtolockyourcredit.com equifaxlock.com equifaxlockalert.com equifaxlockalerts.com equifaxlockandalert.com equifaxlockandalerts.com equifaxlockandfreeze.com equifaxlockcreditreport.com equifaxlockforlife.com equifaxlockmycredit.com equifaxlocknalert.com equifaxlocknalerts.com equifaxlockversusfreeze.com equifaxlockvsfreeze.com equifaxlockyourcredit.com equifaxmultibureaulock.com equifaxwhycreditlock.com equifaxwhyfreeze.com equifaxwhylock.com equifaxwhylockmycredit.com freecreditlockequifax.com freelockequifax.com freelockforlife.com freelockforlifeequifax.com freezeandalert.com freezeandalertequifax.com freezeandalerts.com freezeandalertsequifax.com freezecreditreportequifax.com freezemycreditequifax.com freezeversuslock.com freezeversuslockequifax.com freezevslock.com freezevslockequifax.com freezeyourfile.com freezeyourfileequifax.com howtolockyourcredit.com lock4lifeequifax.com lockalertequifax.com lockalerts.com lockalertsequifax.com lockandalertequifax.com lockandalerts.com lockandalertsequifax.com lockandfreeze.com lockandfreezeequifax.com lockcreditreportequifax.com lockforlifeequifax.com lockmycreditequifax.com locknalert.com locknalertequifax.com locknalerts.com locknalertsequifax.com lockversusfreeze.com lockversusfreezeequifax.com lockvsfreeze.com lockvsfreezeequifax.com lockyourcreditequifax.com multibureaulock.com multibureaulockequifax.com securityfreezeequifax.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 Equifax registers domains for new credit locking services appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Department of Justice closes investigation on Verisign running .web

Domain Name Wire - Thu, 01/11/2018 - 16:05

Verisign believes ICANN will now sign the .web contract with Nu Dot Co, and then transfer the domain to Verisign.

Verisign has announced that the antitrust investigation into the company’s plans to run the .web domain name has been closed, apparently without taking action. In an SEC filing, the company stated:

As the Company previously disclosed, on January 18, 2017, the Company received a Civil Investigative Demand from the Antitrust Division of the United States Department of Justice (“DOJ”) requesting certain material related to the Company becoming the registry operator for the .web gTLD. On January 9, 2018, the DOJ notified the Company that this investigation was closed. Verisign previously announced on August 1, 2016, that it had provided funds for Nu Dot Co’s successful bid for the .web gTLD and the Company anticipates that Nu Dot Co will now seek to execute the .web Registry Agreement with ICANN and thereafter assign it to Verisign upon consent from ICANN.

Verisign backed Nu Do Co’s winning $135 million bid for .web. Other applicants for .web believe that ICANN incorrectly overlooked changes at Nu Dot Co and asked for the auction to be set aside. Runner-up Afilias asked ICANN to honor its second-place bid while Donuts wanted the result tossed with the hopes of having a private auction in which the losers split the proceeds.

Concurrently, the U.S. government looked into antitrust issues with the .com operator also running .web. It’s possible they were looking into if the company’s bid for .web was merely a way to quash the domain, which many new TLD operators think could be the best new TLD. It could have also looked into if owning .com and .web would allow Verisign to dominate the market (more than it already does with .com).

Despite the U.S. government’s clearance, there’s still a dark cloud over .web. Donuts sued ICANN and the case was thrown out but Donuts appealed. The appeals court is currently considering the matter.


© 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 Department of Justice closes investigation on Verisign running .web appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. ICANN files motion to dismiss Donuts’ .Web lawsuit
  2. Verisign to .Web losers: stop griping and carry on
  3. Donuts files opening brief in .Web appeal
Categories: Domains

Tracking Whois Searches to Decide Domain Renewals

Domain Name Wire - Thu, 01/11/2018 - 15:11

Alvin Brown provides this tutorial for discovering how many Whois searches have been performed on your domain names registered at GoDaddy.

Deciding which domains to renew can be quite challenging for domain investors, especially for newly minted domain investors.

Personally, I use a number of factors to help me decide whether or not to renew a given domain.

Often times my decision comes down to domain age, traffic, parking revenue, search relevance, and a longer list of details I’ve picked up along the way.

In fact, I often feel like I’m Google and its 200+ search ranking factors as I’ve accumulated a growing number of varying renewal factors used to gauge a domain’s renewal status.

But one in particular I’d like to share today is tracking and using GoDaddy’s Whois searches as a factor in deciding domain renewals.

Note that this step-by-step tutorial in no way should be used as the SOLE factor to determine a domain’s renewal worthiness or value.

Why? Well, some of the Whois searches tracked by GoDaddy are often automated lookups, which could complicate things a bit when attempting to understand human and non-human Whois searches.

Nevertheless, if you register domains with GoDaddy, then I believe using Whois searches could help to understand and gauge relative interest in a given domain.

For instance, a domain could have 70 Whois searches performed on it while another domain has 2 Whois searches within a given month. Personally, I would give a bit more weight to a domain with 70 searches than I would a domain with 2 searches as this may be an indicator of people interested in buying the domain name

Used in conjunction with age, search relevance, and few more weighty factors, could help to establish a baseline for what types of domains remain in a portfolio each annual renewal period.

Let’s get started!

How to Track GoDaddy Domain Whois Searches

Open a web browser and log in to your GoDaddy account. Once in your account, find “Domains” section listed on “My Products” page and select “Manage” to be taken to the “Domain Manager”.

Once the “Domain Manager” page is displayed, select specific domains or choose to complete a Whois search report for all domains.

In today’s tutorial, I’ve elected to use a test account where I have a single domain: kscdev.xyz.

To create a Whois search report, hover over the “More” icon and select “Export List”.

Next, the simple “Create Exportable List” popup window appears displaying 3 steps. Enter a name for the report. I’ve selected to use “20171227-Domains” as the report name.

Once a report name has been entered, select the type of “Domain list” from the following options:

  • Folder Options: if domains are organized via folders, then this option allows access to domains within a given folder
  • All Domains: all domains associated with the account in its entirety
  • Backorders and Monitoring: all domain backorders and monitoring associated with the account in its entirety
  • Premium Listings: all domains associated with account and listed in GoDaddy’s Aftermarket as Premium listings
  • Expired domains: all expired domains associated with the account in its entirety
  • Auctions: all auctions associated with the account in its entirety
  • Pending Transfers: all domains in pending transfer status associated with the account in its entirety

For simplicity, choose “All domains” and click “Next”.

In Step 2 of the “Create Exportable List” form, the desired data columns to be returned and viewed within the report need to be selected. The following options are available:

  • Domain Name (checked by default)
  • Expiration Date (checked by default)
  • Status (checked by default)
  • Nameservers
  • Forwarding URL
  • Auto Renew Status
  • Create Date
  • Folder Memberships
  • Internationalized Domain Name
  • Registrants Contacts
  • Administration Contacts
  • Technical Contacts
  • Billing Contacts
  • Hosts
  • Whois Searches – Previous Period
  • Whois Searches – Current Period

To return the Whois searches for previous and current periods, scroll to the bottom and check the box for both options.

Once both check boxes have been selected for Whois Searches, click “Next”.

The third and final step of the “Create Exportable List” form is selecting the “File Type”. GoDaddy offers both CSV (Comma Separated Values) and XML (Extensible Markup Language).

By default, CSV is selected and GZ is the download output, meaning that the CSV report will be zipped or compressed into a .gz file.

If “None” is selected, then the CSV report will NOT be zipped or compressed into a .gz file.

Although I chose GZ, I recommend selecting “None” and clicking “Finish” once ready to submit the report for creation.

Once the “Create Exportable List” report has been successfully submitted, the following notification is displayed to indicate the request is processing and email notification will be sent upon report completion.

Note: each report created is available for download ONLY 7 DAYS. Don’t think the report will exist forever because it won’t!

Should an email notification not arrive in your inbox, then go back to the “Domain Manager”, and hover over the “More” and select “Manage Exportable Lists”.

 

Clicking on “Manage Exportable Lists” displays the “Exportable List Manager” and a list of reports created via a table with the following headings:

  • Name
  • Create Date
  • Status
  • Size
  • List
  • File Type

In the “File Type” column, note that there are two distinct icons, one with a downward arrow indicating download the report and the other a circle containing a “x” indicating delete the report.  Click the icon with the downward arrow to download the report.

If the report were passed the allotted 7 days, then the report would no longer be visible and the following screen would be displayed if there were no reports.

It’s worth noting that managing and creating reports can also be executed from the “Exportable List Manager” as indicated with the “Create New List” button and “Add Export” text link.

Nevertheless, once the desired report has been downloaded, then open report using Microsoft Excel, Mac Numbers, or a text editor of your choice (first two options recommended).  I’ve chosen to open my Whois search report using Mac Numbers.

For the sake of keeping this tutorial simple, I’ve hidden most of the columns with the exception of the “DomainName” column and following columns:

  • WhoisCountsPrevDay – the current number of Whois counts for the previous day
  • WhoisCountsPrevWeek – the current number of Whois counts for the previous week
  • WhoisCountsPrevMonth – the current number of Whois counts for the previous month
  • WhoisCountsCurrDay – the current number of Whois counts for the current day
  • WhoisCountsCurrWeek – the current number of Whois counts for the current week
  • WhoisCountsCurrMonth – the current number of Whois counts for the current month

Although I monitor and record all columns on a monthly basis via a database, I pay close attention to the monthly Whois search numbers over a rolling 12-24 months when considering domain renewals.

And that’s it for this tutorial!

Closing Thoughts

Again, take Whois searches with a grain of salt when considering your own domain portfolio renewal process.

As I stated earlier, Whois searches often included automated lookups, which makes it difficult to understand human and non-human Whois searches.

Also, results may vary depending on TLD. .Com and .net domains operate on a “thin Whois” system in which Whois lookups have to ping the registrar (in this case GoDaddy). Some other TLD lookups don’t involve the registrar so GoDaddy might not have the data.

In addition, it’s worth noting that hand-registered domains, newly acquired domains, and transferred domains likely have spikes in Whois searches the first 1-2 months, which is why I prefer and recommend reviewing data over a rolling 12-24 month period.

Nevertheless, tracking Whois searches for your domain portfolio could prove to be a value-add activity executed in conjunction with varying renewal factors used to gauge a domain’s renewal status.

Do you track Whois searches for your domain portfolio, or use Whois searches as a determining factor for renewing?


© 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 Tracking Whois Searches to Decide Domain Renewals appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. GoDaddy Allows Transfers After Whois Changes
  2. Domain name revenue barely budges at GoDaddy
  3. New domains and ccTLDs also benefiting from Pokemon Go craze
Categories: Domains

18 end user domain sales up to $75,0000

Domain Name Wire - Wed, 01/10/2018 - 19:42

Here are some domain names that end users bought this past week.

Sedo had a solid domain name sales week headlined by the sale of Publica.com. End user buyers included a company buying its acronym in .co, a medical cannibas company buying a shorter version of its domain name, and a company that has previously been found to have engaged in reverse domain name hijacking buying a domain name that matches its brand.

Here are the end user sales that I identified: (You can view previous lists like this here.)

Publica.com $75,000 – The domain name is still in escrow but there are lots of potential buyers, including one that applied for a trademark for Publica in September.

Block-chain.com $30,000 – The buyer is using Whois privacy but has put up a “coming soon” page.

GroupPay.com $19,999 – GroupPay Inc., an Ontario startup, had registered Group-Pay.com. Getting the unhyphenated version was a good idea.

Conciergerie.com €9,990 – Bien-Etre Assistance is a French firm that provides corporate concierge services. Conciergerie is French for concierge.

Agrima.com $8,500 – Medical cannabis company Agrima Botanicals. It is forwarding the domain to its existing site at agrimabotanicals.com.

CMR.co £6,999- Cambridge Medical Robotics Ltd bought its acronym in .co.

GreenRabbit.com $6,500 – The domain has Whois privacy but a coming soon page promises “Fresh Stuff Fast” so it will likely be a delivery service.

Mikes.pub $5,000 – Mikes Hospitality GmbH owns Mike’s Urban Pub.

MedScout.com $4,750 – DeuMedi Deutsche Medizin Service Gesellschaft GmbH is a German company that uses the domain name MedScout.org.

IMtec.com $4,000 – The domain name forwards to Park Dental Research’s website, which indicates that IMtech is a trademark of 3M. It appears that IMtec is a dental implant system.

DotFund.com $3,988 – Dot Funding Ltd upgraded from DotFund.co.

PrestigeTitle.com $3,888 – Prestige Title Agency, Inc. in New York uses the domain name PresTitle.com.

AdaptHealth.com $3,000 – Ocean Home Health is a health supply (e.g. wheelchairs, medical equipment) company in New Jersey.

Self-Learning.com $3,000 – JEI is a chain of tutoring services that specializes in self-learning.

CryptoAdviser.com $2,388 – Exchange Traded Fund (ETF) provider Reality Shares.

AloYoga.store €2,000 – This is interesting. Reverse domain name hijacker Color Image Apparel, Inc., which owns Alo Yoga, paid for a trademark domain after filing a baseless complaint against ALO.com. I guess the price played a factor.

SMIMed.com $2,000 – SMI Holding GmbH in Germany.

BioSoundLab.com $2,000 – The site is in Korean, but it looks like the buyer operates under the name BSL at bsl.co.kr.


© 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 18 end user domain sales up to $75,0000 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. 20 end user domain sales from Sedo
  2. 18 end user domain name sales up to $50,000
  3. End user domain name sales, including one by a $25 billion company
Categories: Domains

Nicolai Bezsonoff to lead Neustar’s registry business

Domain Name Wire - Wed, 01/10/2018 - 16:55

Bezsonoff will take over for Sean Kaine.

Nicolai Bezsonoff is shifting roles at Neustar.

Neustar announced today that Nicolai Bezsonoff will now lead its Registry Solutions business as VP and General Manager.

Bezsonoff was co-founder and Chief Operating Officer of .co, which Neustar acquired in 2014. His previous role at Neustar was VP and GM of Security Solutions.

He’ll replace Sean Kaine, who is leaving the company in a few months.

Neustar’s top level domain business took a big loss last month when Afilias won a contract to take over the .au domain name that a Neustar company has been operating for 15 years. There are about 3 million .au domains under management.

The company’s domain registry focus lately has been on getting companies excited about applying for .brand domain names in the next round of top level domain expansion.


© 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 Nicolai Bezsonoff to lead Neustar’s registry business appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. From 10-cent domains to revved up marketing and policy changes, .US might finally go somewhere
  2. Neustar (NSR) to go private in $2.9 billion deal
  3. UDRP filed against Circus.com
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.