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.

15 end user domain sales up to $60k

Domain Name Wire - Wed, 01/16/2019 - 17:53

A pet products company, ceramic coatings manufacturer and truck enthusiast website bought domain names this past week.

This week we have end user sales from both Sedo and PerfectName.com. I’ve denoted the PerfectName sales; all others are at Sedo.

The beginning of the year is usually a good time for domain sales so I look forward to seeing a bunch of good end user sales soon.

Let’s get to the list, and you can view previous lists like this here.

RedBarn.com $60,750 – Red Barn Pet Products bought the shorter version of its domain RedBarnInc.com. (PerfectName)

Jujube.com $29,750 – Backpack and accessories store jujube bought this nice upgrade to its ju-ju-be.com domain name. (PerfectName)

Sego.com $16,250 – Bannermate, maker of the SEG popup displays. (PerfectName)

SystemX.com $12,500 – Element 119 sells ceramic coatings under the System X brand. It forwards its new domain to Element119.com. (PerfectName)

Lokalnachrichten.de €10,000 – This domain has a coming soon page and states the site is run by a journalism professor and author. It translates to “local news”.

SaleInTop.com $9,075 – Another top sale for the SedoMLS network, this currently forwards to NorCalMLKFoundation.org. This is the Northern California Dr. Martin Luther King, Jr. Community Foundation, a charitable organization with programs and initiatives in health, civic engagement, social justice, and art & culture. Not sure what this domain will be used for within this organization.

Dartmoor.com $6,875 – Princetown Distillers Ltd is opening The Dartmoor Distillery. (PerfectName)

FileBox.cn $5,385 – FileBox.com, a data cloud storage service, bought the Chinese ccTLD of its domain name.

Noma.de €5,800 – Forwards to Hilfsaktionnoma.de, a German-based charitable organization providing education and prevention activities, such as vaccinations and support against malnourishment.

TruckJunkie.com $5,000 – Based in the Netherlands, this catchy domain now services truck enthusiasts worldwide with parts and accessories.

ZoomDigital.com €5,000- This isn’t resolving yet but Zoom Advertising, a full-service retail focused creative agency out of Chicago that operates from ZoomChicago.com, bought the domain.

PayBit.se €4,999 – Cryptocurrency payment platform that supports all cryptocurrency forms and offers automatic conversions. They operate from the .com of this domain but with this purchase now also own the Swedish ccTLD.

AmericanRubber.com $4,500 – The buyer is a director at United American Healthcare Corporation but has several other ventures, including an investment firm. I suspect this domain is for one of those ventures.

CSCOnline.com $3,000 – CSC is a Lebanese payments company.

Wonders.es €2,000 – This Spanish shoe brand currently forwards to wonders.com but now will own the Spanish ccTLD to be better represented where they’re headquartered.

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

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

How the competitive domain registrar market keeps prices down

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

No matter what Verisign charges them, registrar profits on .com are limited by competition.

Last year the U.S. Government granted the ability for Verisign (NASDAQ: VRSN) to raise prices on .com domain names pending approval from ICANN.

Where does that extra money go? As the sole wholesaler of .com domain names, every penny that Verisign raises the price of .com domain names goes to its bottom line. Domain registrars do their best to pass the price increase on to consumers, but their margins continue to be held down by the competitive market.

Indeed, while domain registrars can charge whatever they want for .com, market forces prevent them from charging much over the wholesale cost.

Take a look at this chart from Tucows’ (NASDAQ: TCX) third quarter investor Q&A:

It shows the revenue that Tucows generates each year from .com sales as well as the gross margin. As you can see, it sells more and more .com domains but it makes roughly the same amount of margin ($8 million) each year.

Tucows CEO Elliot Noss wrote:

… .com has a strange place for us, and I suspect most registrars. It is still by far the largest top level domain. It is still by far the one that end users want as first priority. It still dominates our discussions with resellers. And over time it has become less and less impactful to our gross margin dollars. The data, going back to the launch of OpenSRS in 2000 speaks volumes. The unit volume of .com sold goes up every year. The amount of money we pay to Verisign goes up commensurately. And the amount of money that the competitive registrar market allows us to generate stays flat. Like the prairies. Amazingly flat over now 18 years. And on a % basis it has gone from us making 40% of the .com revenue generated in 2000, all the way down to 12% in 2018. We make a little under $8 million per year on .com. That was true in both 2000 and 2018. They made roughly $19 million from our .com sales in 2000. In 2017 that number was nearly $67 million. This price increase only exacerbates that trend. And of course we believe that registrars do, by far, the lion’s share of the work to generate that revenue.

While the price of .com has increased from $6.00 to $7.85 over the past 18 years, the biggest impact on profits is competition amongst domain registrars.

Noss is also pointing out that registrars (not Verisign) do the most work to promote .com’s growth.

If .com prices increase in a couple of years, Tucows will have to pass these costs directly to customers. It will probably still generate a gross margin of about $8 million a year from .com but on a bigger revenue base.

I’ve heard the argument that Verisign should have price flexibility for .com because registrars have complete price flexibility. The difference is that Verisign has a monopoly while the registrars work in a highly competitive market.

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

Related posts:
  1. Google is now one of the Top 10 .com registrars
  2. Namecheap leaps up .com chart as PDR falls
  3. Digging into Tucows’ annual report
Categories: Domains

Create an SPF record to show that your domain does NOT send email

Domain Name Wire - Tue, 01/15/2019 - 16:19

Add an SPF record to prevent spoofing.

Add a SPF record to keep people from spoofing your domain in emails.

When it comes to email deliverability, most people are trying to figure out how to ensure their mail lands in the inbox. But what if you want to tell email providers that they should not accept email from a domain name? This might be the case if you have a parked domain that someone is trying to spoof when it sends email.

One option is to create a Sender Policy Framework (SPF) record that says all mail should be rejected. To do this, go to your domain name registrar and manage the DNS for the domain.

Create a TXT record and include this text:

v=spf -all

This will tell mailbox providers that your domain name should not send any email, giving them an indication that email with your address should be considered spam.

Domain name owners should consider adding SPF records to their parked domains if they don’t use them for email.

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

Related posts:
  1. Understanding SPF, DKIM and DMARC for email
  2. Forget traffic leakage. It’s email that’s most dangerous
  3. In Review: June in the domain industry
Categories: Domains

AddictingGames.com sues Addicting.com, claiming cybersquatting

Domain Name Wire - Tue, 01/15/2019 - 14:38

Addicting.com parked page filled with links for games.

Addicting Games screenshot

The popular online game site Addicting Games filed an in rem lawsuit (pdf) yesterday against the domain name Addicting.com, claiming that the owner of the domain is cybersquatting. Addicting Games is owned by Bill Karamouzis, who was on DNW Podcast #178.

The lawsuit points out that almost all the pay-per-click links on Addicting.com, which is parked at Uniregistry, are related to games. The first link is “Addicting Games”.

One big question is when the current owner of the domain acquired it.

The lawsuit alleges:

On February 21, 2018, the registrant of the domain Addicting.com was changed from Domain Hostmaster, Customer ID : 85528474484681 to Savvy Investments, LLC Privacy ID #735277, and the registrar was changed from Fabulous.com Pty Ltd to Sea Wash, LLC.

Sea Wasp, LLC is just the business name for Fabulous, so the registrar didn’t actually change.

The Whois record is private going back to the end of 2011.

From at least as early as 2004 until the record was private, the domain was owned by a registrant in Vietnam. The domain has been parked with Uniregistry since at least 2013. So I suspect that there was not an ownership change this year, although it’s possible.

There’s a chance that the domain is currently owned by the same entity that owned it since at least 2004, which is before Addicting Games existed.

That said, the links on the parked page (which have been there since at least 2013) are definitely problematic and could present a trademark problem for the domain owner.

It will be interesting to see if the owner of Addicting.com defends the domain name in court.

David Weslow of Wiley Rein LLP is representing Addicting Games.

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

Related posts:
  1. Fight over APE.com lands in court
  2. Battle over vineyards named Wilson goes to court
  3. Mike Mann sues to stop SoundStop.com transfer
Categories: Domains

Don’t respond to “Good luck with that”

Domain Name Wire - Mon, 01/14/2019 - 17:53

It’s just a waste of your time.

Have you ever received this response when you quote a price for one of your domain names?

“Good luck with that.”

It’s a bit of an insult. Like someone is calling you crazy.

It could be tempting to respond to the person and tell them why you aren’t crazy but I don’t think it’s worth it 99% of the time.

For example, this weekend I received an inquiry on CandyCorn.com. I looked up the inquirer and saw that it was a really small business in a really small town. I almost didn’t respond because it didn’t seem qualified. But you never know, so I quoted $35,000.

I got the “good luck with that” response.

I could huff and puff and tell them why I’m not crazy and educate them on the value of domain names…but why? It would be a waste of my time and their time. It’s better to just move on.

The exception would be if someone comes out with a decent starting point offer. For example, if someone who seemed qualified offered $10k for the name but said “good luck with that” to $35k, it might be worth discussing domain value to see if we can close the gap.

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

No related posts.

Categories: Domains

Sedo makes expired list downloadable, Name.com changes happy hour

Domain Name Wire - Mon, 01/14/2019 - 16:59

Download lists to look for good domains, and you now have longer to buy discounted domains at Name.com.

Sedo’s expired domain lists are now downlodable.

A couple of quick news items for you on this Monday morning…

Sedo made its expired domain name inventory list downloadable. The marketplace auctions off expiring domain names from registrar 1&1 which is part of the same company as Sedo. But sorting through the list to find good domains is difficult. Now you can download the list and run it through services like Estibot to find the best domains. I also hope this means that expired domain data sites like ExpiredDomains.net start to provide data on these domains.

Also, Name.com has ended its Happy Hour sale concept in favor of monthly specials. The Name.com Happy Hour was a special promo (usually on one top level domain) that ran for a short time on Thursday afternoons. It’s a lot of effort to schedule time to register a domain to save a few bucks. Now, Name.com has a week-long sale each month. The kicker is you need to go to the sale page and get the discount code to get the discount. You’ll pay more if you try to register one of the sale domains and don’t use the discount code.

This month’s sale includes 30 new top level domains, most from Donuts’ portfolio. Donuts owns Name.com.

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

Related posts:
  1. Name.com expired domains are now on GoDaddy
Categories: Domains

WordPress Plugins + 2 more predictions – DNW Podcast #219

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

How to avoid bad WordPress plugins.

This week on the DNW podcast meet Mika Epstein, a WordPress engineer at DreamHost. She explains what to look for in WordPress plugins to make sure you aren’t opening up a backdoor to your website. We also hear predictions from Natasa Djukanovic and Braden Pollock.

Plus: NameSilo acquisition, much ado about ado.com, .homes, domain hijacking, hosting merger, NameBio and more.

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

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

Related posts:
  1. WordPress.com and domain names – DNW Podcast #169
  2. Will Chatbots change the web? – DNW Podcast #153
  3. NamesCon recap with 15 interviews – DNW Podcast #172
Categories: Domains

Newspack could solve one of WordPress’ problems

Domain Name Wire - Mon, 01/14/2019 - 14:21

WordPress-for-newsrooms could help small publishers avoid the IT guy.

There’s a problem with WordPress: it’s too complicated for the typical small business owner. It’s also too complicated for the typical small news publisher.

So it’s exciting to hear that Google (NASDAQ: GOOGL), Lenfest Institute for Journalism, The John S. and James L. Knight Foundation and Civil Media are all contributing financially to an effort by WordPress creator Automattic to create Newspack. Google calls it “a fast, secure, low-cost publishing system tailor-made to the needs of small newsrooms”.

This sums it up nicely:

Journalists should be writing stories and covering their communities, not worrying about designing websites, configuring CMSs, or building commerce systems. Their publishing platform should solve these problems for them. So while Newspack publishers will have access to all the plugins created by the WordPress developer community, the core product is not trying to be all things to all publishers. It is trying to help small publishers succeed by building best practices into the product while removing distractions that may divert scarce resources. We like to call it “an opinionated CMS:” it knows the right thing to do, even when you don’t.

It will be exciting to see the finished product. Hopefully, this is a sign of things to come: easy-to-use installments of WordPress.

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

Related posts:
  1. VeriSign: Google Slowing Domain Name Registration Growth
  2. Final new TLD objection tally: Donuts 55, Amazon 24, Google 22
  3. Google announces .Dev domain launch dates
Categories: Domains

Understanding SPF, DKIM and DMARC for email

Domain Name Wire - Fri, 01/11/2019 - 15:54

A primer on email authentication.

Domain names are necessarily intertwined with email. The domain name connected with an email address is a signal for email services about the sender’s reputation, assisting the mailbox provider (MBP) and ISP when it determines what’s legitimate and what’s junk.

There are a few authentication mechanisms that domain owners can put in place to reduce the chances of phishers and spammers from spoofing their domains. In this post I’ll run through these at a high level; in later posts I’ll go more in-depth and explain how to set these up.

There are three main authentication mechanisms that domain owners can put in place.

Sender Policy Framework (SPF)

Think of SPF as a way to whitelist certain IP addresses that are validated to send email on behalf of your domain. You can tell email providers that only mail from a certain IP address or range of IPs is valid. Email from other IP addresses might be spoofed.

SPF is a way to reduce the chances that phishing and other emails that appear to be from your domain (but really aren’t) make it to the inbox. If you have a domain that you don’t use for email but people continually spoof it, you can add an SPF record that states that no mail should be sent from the domain.

Implementing SPF at its most basic level is quite easy. It requires adding a TXT record to the DNS.

DomainKeys Identified Mail (DKIM)

DKIM is more complicated than SPF and allows the sender to digitally sign certain components of the email.

With DKIM, the domain owner publishes a key in the public DNS. The outgoing email server signs the message. The recipient mail server uses the public key to check the signature and make sure it is valid. If so, then it shows that the signed fields have not been altered in route and passes DKIM.

Domain-based Message Authentication, Reporting & Conformance (DMARC)

DMARC is a way for email senders to tell mailbox providers what action to take if an email fails authentication under SPF or DKIM and provides a reporting channel from mailbox providers back to senders.

A sender can tell the email recipient server what to do if a message fails authentication: let it pass through, quarantine it in the junk folder or reject the message.

Implementing DMARC is a journey, with companies typically publishing a DMARC policy with a ‘none’ policy setting to take inventory of mailstreams coming off their domain and gather reporting back from the participating mailbox providers. Once organizations have a clear understanding of legitimate vs. illegitimate mail coming off their domain, they can take action with their DMARC policy setting by selecting either a ‘quarantine’ or ‘reject’ policy.

Even if a company uses DMARC but tells the recipient server to take no action against mail that fails SPF or DKIM (policy=none), it will still benefit by using DMARC. That’s because email services will begin providing reports to the sender about the email it processes. This data includes IP addresses, rDNS, sending domain and other information helping senders track down either incomplete SPF or DKIM records or sources trying to spoof the company’s domain.

Like SPF and DKIM, DMARC involves a DNS record.

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

Related posts:
  1. Forget traffic leakage. It’s email that’s most dangerous
  2. In Review: June in the domain industry
  3. Marriott’s poor choice of domain for email notification
Categories: Domains

Registry to relaunch .Homes top level domain

Domain Name Wire - Thu, 01/10/2019 - 18:41

Company changes its strategy to make it easier (and less expensive) to register .homes domains.

Dominion Registries is relaunching .homes with lower prices, no eligibility requirements and more registrars.

Dominion Registries is relaunching the .homes top level domain next week with a new strategy.

The registry for .homes (and also .autos, .boats, .yachts, and .motorcycles) originally launched its domains with restrictions and pricing that turned off both registrants and registrars.

Dominion Enterprises (parent of Dominion Registries) is a publishing company that owns Boats.com, Homes.com, Franchise.com and many other sites. Its original goal was to control the registrations of domains at the second level and sell them to their existing clients.

Onerous registrar requirements meant that few registrars carried the TLDs at launch. Also, registrants had to show a connection to the industry and verification could take 1-2 weeks before they were able to use .homes domains. (Listen to a podcast with Dominion’s Jim Schrand that was recorded when the restrictions were in place.)

As a result, the domain hasn’t taken off. .Homes has just a few hundred domains in the zone.

Last year the company removed restrictions on .boats and tried to re-engage with the registrar channel.

Now it’s doing the same with .homes and it seems to be having success getting registrars on board. Notably, GoDaddy will carry .homes domains.

Promotional first-year rates should be around $15 retail with standard and renewal prices around $35 or so.  This compares to over $100 previously.

The relaunch is scheduled for Monday, January 14 at 16:00 UTC.

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

No related posts.

Categories: Domains

NameSilo acquires domain registrar and expired domain company NamePal

Domain Name Wire - Thu, 01/10/2019 - 15:40

Deal will give NameSilo more tools to target domain investors.

NamePal’s Fetch is a domain backorder aggregation service.

Domain name registrar NameSilo (PINKSHEETS: NTCEF, URL:CSE) has acquired NamePal, a small domain name registrar with an expired domain backorder platform.

The all-equity deal is for up to a 1.75% interest in NameSilo, with the equity payments not starting until 6 months after completion of the acquisition. At today’s market cap, that’s only a few hundred thousand dollars. However, NameSilo is picking up NamePal’s team, so there might be employment agreements as part of the deal.

In a release, NameSilo touts NamePal’s Fetch! Product as a big reason for the acquisition. Fetch is a multi-platform backorder aggregator. According to a product page, Fetch allows you to place backorders on a central dashboard and manage your purchased domains through a central location as well:

Tired of using dozens of registrar platforms for your backorder domains? Multiple logins and different control panels can waste your time and cause delays that cost you money and customers. NamePal’s new Fetch! is here to solve your problems, our proprietary Backorder Platform will consolidate and make managing your backorders faster and convenient. Capture domains across multiple popular catch services, manage your remote domains and participate in auctions across the web, all in one location.

The page notes that the product is coming soon.

I can see value in a service like Fetch, especially if users can manage their purchased domains from one dashboard rather than logging into each registrar account.

A 2017 presentation explains NamePal’s plans to target domain investors with tools and services, including a domain “afterlife” program that lets domainers share in income received from a domain after it is sold to another user.

Arthur Poghosian founded NamePal. He also was CEO of BackorderZone.com, which he sold to Web.com in 2016.

The most recent domain data report at ICANN from September shows that NamePal.com has 26,000 .com domains under management at its main registrar, plus 40,000 at affiliate registrars that were likely set up for dropcatching.

The acquisition signals that NameSilo continues to beef up its domainer-targeted offerings.

 

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

Related posts:
  1. NameSilo hits $20 million in bookings for 2018
  2. Investment firm to acquire domain name registrar NameSilo
  3. NameSilo doubles in size in just one year, crosses 2 million domains
Categories: Domains

Ado.com domain dispute settled

Domain Name Wire - Thu, 01/10/2019 - 14:41

Settlement overturns bad WIPO decision.

A World Intellectual Property Organization (WIPO) wrong has been righted.

In February 2018, a three-member WIPO panel made an atrocious ruling that ADO.com should be transferred to a Mexican bus company.

Ado.com is owned by Francois Carrillo, the owner of Domaining.com.

Carrillo subsequently sued to halt the transfer of the valuable domain name.

Last month the parties settled. The settlement order (pdf) reads:

…In light of the Parties’ agreement that (i) Plaintiff’s interests in respect of the ado.com domain name are legitimate; (ii) Plaintiff did not register or use the ado.com domain name in bad faith; (iii) Plaintiff’s registration and current use of the ado.com domain name do not violate Defendant’s rights under the Anticybersquatting Consumer Protection Act, 15 U.S.C. §§ 1114, 1125(a) and 1125(d)…

So the settlement overturns a mistake by the WIPO panel. That said, the court order states that each party will bear its own costs and attorneys’ fees. If indeed Carrillo came out of pocket on legal costs to settle the claim, then the wrong has been only partially righted.

Update: I connected with Carrillo today via email:

Now that the case is settled, what are your plans for the domain?

No special plans. Sell the domain if I receive an appealing offer, or use it myself further if I have a service idea that can benefit of this brand.

The settlement says that both parties are paying their own attorneys’ fees. How much did it cost you to defend your domain?

All court cases are expensive ( in comparison defend an UDRP case is insignificant), and this case was no exception. But, I thought it was important to not only make sure that I kept ado.com but to also obtain a court order clearing me of any suggestion that I violated the UDRP. This has been done!

What advice do you have for domain owners who lose a wrongly-decided UDRP?

Talk to an attorney who has handled court cases following wrongly-decided UDRP decisions so that you know your options. But, more importantly, get involved with the ICANN Working Group that is currently reviewing the UDRP so that it can be improved to lessen the chances of finding yourself in a similar situation.

(Hat tip: GOTW.com)

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

Related posts:
  1. How to lose a $175,000 domain name in a UDRP
  2. WIPO panel screws Domaining.com owner Francois Carrillo out of Ado.com
  3. A troubling connection in a UDRP
Categories: Domains

Infusionsoft loads up on domains as it plans for Keap

Domain Name Wire - Thu, 01/10/2019 - 14:26

Company acquired Keap.com, filed for trademarks, and recently loaded up on Keap-related domains.

The Keap logo, as filed with the U.S. Patent and Trademark Office

CRM and marketing platform Infusionsoft has registered a lot of domain names as it prepares to launch Keap.

What is Keap? I can’t tell for certain, but based on the company’s recent trademark filings and domain registrations, it’s very possible that the company is rebranding as Keap. At a minimum, it is about to launch a new product called Keap.

In August or September 2018, Infusionsoft appears to have acquired the domain name Keap.com from Frank Schilling’s Name Administration.

Then late last year the company filed for nine trademarks involving the brand. The services it filed under seem a lot like what Infusionsoft currently offers.

Over the past two days, dozens of keap-related domain names have been registered:

cancelkeap.com
dontkeap.com
getkeap.com
ihatekeap.com
infusionkeap.com
iusekeap.com
keapalternative.com
keapblows.com
keapcreep.com
keapcrm.com
keapersoft.com
keapfails.com
keapinsoft.com
keapischeap.com
keapiscrap.com
keapisgarbage.com
keapisshit.com
keapme.com
keaponkeapingon.com
keapons.com
keaponsoft.com
keapsoft.com
keapstinks.com
keapus.com
keapyou.com
teamkeap.com
usekeap.com
youkeap.com

The domain names use a registrar’s Whois privacy service, but it’s the same corporate registrar at which Infusionsoft.com is registered.

The pattern shows a good practice in corporate branding: first, acquire the domain name. Then file the trademarks. Finally, pick up ancillary domains that might be useful (or detrimental) to the brand.

Expect an announcement from Infusionsoft soon.

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

No related posts.

Categories: Domains

25 end user domain name sales up to $250K

Domain Name Wire - Wed, 01/09/2019 - 18:34

A tax service provider,  a video game company and soccer forum all bought domain names recently.

Sedo published a new sales list that covers a few weeks of sales over the holidays, so we have a bonanza of end user sales to report this week.

Let’s get right to it, and if you like this list, you can view previous lists like this here.

Taxes.com $250,000 – Sedo sold this high value generic key term to the international tax services and consulting firm Ryan, which is headquartered in Dallas. They currently utilize Ryan.com as their main site but with this purchase, they will certainly receive more traffic.

FinalGoal.com $68,000  – This domain is being used for a soccer forum.

Zuj.com €10,099 – This valuable 3L .com was purchased by Redfox Ventures, a branding agency, presumably for one of its clients.

Eat.fr €7,000 – A food takeout and delivery service bought this French ccTLD.

EliteDerm.com $7,000 – Forwards to EliteDermatology.com, a Houston-based dermatology practice.

Keramik.com €6,500 – This is German for ceramics. A “coming soon” message on the domain points to eQuarz, a granite, quartz and ceramic countertop seller.

Küchenheld.de €5,950 – A German construction company specializing in kitchen renovations.

Data4life.de €5,900 – Redirects to GesundheitsCloud.de, a German service provider that lets you manage personal medical information such as healthcare providers, medical institutions, etc.

RentBerry.com.br $5,600 – RentBerry, a home rental company, bought the Brazilian ccTLD to match its .com. for its business after purchasing the Canadian ccTLD several weeks ago. It bought Rentberry.ca for $8,888 a few weeks ago.

Shopee.in $5,000 – Shopee is an E-commerce platform headquartered in Singapore that launched in 2015.

Wikisoftware.com $5,000 – Electronic Forms LLC, which operates from EForms.com, is an online provider of legal documents and contract forms for business, real estate and estate planning.

Elyps.com $4,001 – A site in development for a new app for real-time mobile Blockchain payments.

CubeWorld.com $3,900 – Game developer Picroma, which as a game called Cube World.

Paul-Valentine.cn $3,800 – Redirects to .com version of this online jewelry and accessories shop.

Controlar.com €3,700 – Controlar, a Portuguese auto electronics and software company that operates on Controlar.pt.

Aeroe.com $3,500 – A New Zealand company called Aeroe Ltd.

DentalFox.com €2,900 – German dental equipment company Dental Fox, which uses DentalFox.de,

Med-Link.com $2,750 – Med-Link helps accident victims with their medical treatment.

SymetraLifeInsurance.com $2,568 – Symetra Life Insurance of Bellevue. It uses the domain Symetra.com

Damascus.net €2,500 – Purchased by the Catholic Youth Summer Camp organization to be used for their Damascus campus in Centerburg, OH.

Claneo.com €2,420 – Claneo GmbH, a German Digital Marketing agency who that uses the German country code domain Claneo.de.

Optival.com €2,350 – Digital marketing agency Optival uses the domain name Optival.co.

CMCX.com $2,300 – Redirects to Content-Marketing-Conference.com, so this is a shortened domain for the CMCX European Content Marketing Conference hosted in Munich.

Datack.com €2,000 – Redirects to Datack.FR which looks to be a French website in development for some sort of marketing agency with the slogan, “Deploy your identity, Activate your communities, Influence your sector”.

Mountainhardwear.es $2,000 – Presumably purchased by Mountain Hardwear, a subsidiary of Columbia Sportswear who specializes in apparel, accessories and equipment primarily for mountaineering enthusiasts and outdoor athletes.

 

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

Related posts:
  1. End user domain name purchases up to $350,000
  2. Bitcoin company among end user buyers at Sedo last week
  3. What domains Microsoft, HBO and others bought last week
Categories: Domains

A prediction: new TLD registrations will drop in 2019

Domain Name Wire - Wed, 01/09/2019 - 17:12

A drop in total registrations will be a healthy sign of a maturing market.

A drop in new top level domain registration numbers would be a health thing.

This week I published my annual predictions podcast episode featuring 19 predictions for 2019.

Here’s another prediction for 2019: the number of registered domain names in new top level domains will decrease. But this is actually a good thing, as I’ll explain.

The reason for the anticipated drop is a shift in business model at Famous Four Media, which is now Global Registry Services Limited, aka GRS Domains.

The domains under management in this portfolio were built on very cheap (sometimes free) domain registrations. That’s why .loan is the third (or second depending on who you ask) biggest top level domain in terms of volume. nTLDstats shows 2.2 million .loan domain names.

John McCormac, who runs HosterStats.com, has been tracking .loan and other former Famous Four Media domains and says renewal rates for these domains are dismally low when renewal prices are higher. He calculates that renewal rates for 2017 registrations was under 1% through the first three quarters of 2018. So over 99% of those domains dropped.

Historically, these would be replaced by people registering new domains. But GRS Domains started charging higher prices toward the end of last year. Retail prices for .loan domains are now $10+. Here are HosterStat’s new registration calculations for .loan through the first day of each month:

01 Jan 2018: 224,502
01 Feb 2018: 98,624
01 Mar 2018: 205,863
01 Apr 2018: 397,069
01 May 2018: 353,244
01 Jun 2018: 37,968
01 Jul 2018: 705,787
01 Aug 2018: 110,583
01 Sep 2018: 57,174
01 Oct 2018: 46
01 Nov 2018: 93
01 Dec 2018: 78

There’s little demand for .loan without steep discounting.

McCormac notes that the increased wholesale price of .loan and other domains is scheduled to last until February 2019. If prices stay higher, then we can expect few new .loan registrations this year.

But…this is a good thing. New TLD registration numbers have been inflated by cheap domain registrations. Dirt cheap domain registrations are a bad thing: there’s a very real correlation between the price of a domain and its abuse rate. Scammers and spammers keep their costs down with these cheap domains. Paying less than a buck for a domain instead of $10 adds up when you register thousands.

Spamhaus publishes a list of the 10 most abused top level domains. Guess what’s at the top? Yep, .loan.

There is simply no legitimate reason that certain top level domains have as many registrations as they do. The only reason they are so high is because people are using them for bad stuff. That kills the TLD. Legitimate domain users will avoid a TLD if it has a bad reputation. Some people have blocked emails from all .top domains because of the amount of spam.

A financial company would be much wiser to use one of Donuts’ .loans domains than .loan because of the reputation of these domains.

So assuming GRS Domains sticks with its current approach (and I hope it does), we can expect the number of registered domains under new TLDs to fall in 2019. This is a good thing.

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

Related posts:
  1. .VIP hits 200k registrations, $3.2 million within 5 days
  2. .Boston domain names enter general availability today
  3. Minds + Machines acquires .XXX top level domain operator ICM Registry
Categories: Domains

Hostway and Hosting.com to merge

Domain Name Wire - Wed, 01/09/2019 - 14:42

Two hosting companies are merging.

Austin-based Hostway and Denver-based Hosting.com are tying the knot, the companies announced.

Emil Sayegh, who currently heads Hostway, will be the company’s CEO and president.

The two companies combine to have 14 data centers in five countries across three continents. They have about 1,000 employees.

Hostway is primarily a Windows Azure shop. Hosting.com, which actually goes by the generic name Hosting, focuses on AWS. They manage services on these public clouds as well as provide their own hosting infrastructure.

Both companies were founded in the late 1990s at a time when the hosting business was dramatically different than today.

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

No related posts.

Categories: Domains

December’s top DNW Stories

Domain Name Wire - Tue, 01/08/2019 - 20:16

Happy New Year!

December was a slow month in the domain name business but there was still a bit of news. Here are the top five stories on DNW last month.

1. NBC registers domain names for sports betting – is NBC getting ready for sports betting or were these domain registrations just defensive?

2. Marriott’s poor choice of domain for email notification – Email-Marriott.com looks like a phishing email to many people.

3. GMO is sending expired domains to GoDaddy Auctions – GoDaddy picked up another top 10 registrar. I wonder if Enom will transition in 2018 now that Tucows sold off its share of NameJet to Web.com.

4. GoDaddy tests new branding on Afternic landers – The GoDaddy logo is front and center.

5. Four ways to improve the GoDaddy aftermarket – GoDaddy has the dominant domain name aftermarket. It could be better.

And here are the DNW podcasts from December:

#213 – Understanding .Brand domains

#214 – Domain predictions – who was right?

#215 – 7 reasons companies need a great domain

#216 – The Fake Domain Broker

#217 – 2018 in Review

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

Related posts:
  1. NBC launching SeeSo streaming service?
  2. Supreme Court ruling leads to domain name bonanza
  3. Marriott’s poor choice of domain for email notification
Categories: Domains

What 2018’s poor stock market return could mean for domain names

Domain Name Wire - Tue, 01/08/2019 - 16:33

If the economy heads south, be ready with cash on the sidelines.

The S&P 500 total return (including dividend reinvestment) was negative last year. That’s the first time this has happened since the bottom fell out in 2008.

We can’t predict the future but people tend to use the recent past as guidance. This means 2019 could be a challenging year.

I’ve talked to several friends recently who said, “Well, it looks more and more likely we’re heading into a recession soon”. It’s true that the stock market isn’t the economy and the job market is great, but people see all sorts of challenges ahead: whipsawing asset prices, a dysfunctional and unpredictable government, tapering of fiscal and monetary expansion, etc.

And when perceptions go negative, people pull back, bringing the economy with them.

Broader economic conditions play a role in the domain name business. Some can be countercyclical, such as people starting a new online business when they lose their job. Others, such as reduced VC funding, can lead to fewer big domain purchases.

When a domain investor’s fortune wanes, this can present a buying opportunity. Cash is king in downturns.

I have no idea if 2019 will be a tough year, one where we tread water, or maybe the good times return. But the old adage is always true: buy low, sell high.

 

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

No related posts.

Categories: Domains

Beware the imposter domain broker

Domain Name Wire - Tue, 01/08/2019 - 15:01

An imposter pretended to be another domain broker. Here are some tips to avoid becoming a victim.

On Christmas Eve I published a podcast with Bill Sweetman of Name Ninja. Bill told the story of how someone pretending to be domain name broker Tracy Fogarty of eNaming tried to dupe him out of $10,000. Bill didn’t bite.

Since publishing that podcast, I have learned that this imposter reached out to at least three people total. The scammer pitched a handful of domain names with a lower case L replacing the upper case I at the beginning of the word. A reverse Whois report at DomainIQ shows that these pointed to the nameserver doneritehosting.net. The names include lncorporate.com, lnnovate.com, lnsurers.com, lnsuring.com and lnvested.com.

All three of the people I’m aware of being contacted are sophisticated domain experts and wouldn’t fall for a scam like this.

Here’s a summary of some of the suggestions Bill made on the podcast (with some of my additional tips) to avoid becoming a victim of a scam like this.

  • Double check the domain name to make sure it’s not faked (or an internationalized domain name). Copy and paste the domain into a plain text word editor.
  • Check the email address that sent the domain. Does it match what you’d expect? Try emailing the person at their normal email address rather than replying to the email. In the imposter case, the email address was @fakedomain.com, which is unusual. Sweetman noted, “The main brokers representing domains for sale rarely, rarely will use that domain name for their email address.”
  • Think if the offer is it too good to be true.
  • Check the signature file on the email. Does it have a phone number or other contact method? “Typically, brokers make themselves available to be reached, especially by phone,” Sweetman said.
  • Is the seller in a real hurry to get the deal done? While there might be a legitimate reason, be cautious if someone makes you move fast.
  • Use an escrow service and be wary if the other party doesn’t want to. “That’s why using an escrow service is so important because it protects all the parties,” Sweetman said. “It protects the buyer, it protects the seller. It to some degree protects the domain.”
  • Check the domain owner listed in a purchase agreement and make sure it matches who you think owns the domain. Do a Whois lookup if possible.
  • Check the domain history including Whois history for the ownership history.

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

Related posts:
  1. The Chinese trademark domain name scam in its entirety
Categories: Domains

Year in review: Scientology, Mugshots, Dropbox and GoDaddy

Domain Name Wire - Mon, 01/07/2019 - 17:45

More top stories from 2018.

I have reviewed the top stories on DNW in 2018 over the past couple of weeks. Most of these were based on high-level topics but there were some one-off stories that also landed at the top. Here they are:

Take a look at The Church of Scientology’s domain names – The controversial organization registers a lot of domain names of both its leadership and its detractors.

Sahar Sarid arrested on charges related to Mugshots.com – The domain investor is in hot water after the California Attorney General filed charges.

How Dropbox got the Dropbox.com domain name – It wasn’t easy! Dropbox co-founder Drew Houston explained the story to Tim Ferriss.

This GoDaddy Premium Domain change could help you sell a lot more domains – GoDaddy expanded the promotional real estate for premium domains. It added valuations and reasons why a domain is premium. GoDaddy also closed an expiring domain loophole last year.

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

Related posts:
  1. Panama, Sherpas and the Domain Market with Andrew Rosener – DNW Podcast #180
  2. John Pollard: How to grow the usage of domain names – DNW Podcast #188
  3. 2019 Predictions – DNW Podcast #218
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.