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.

Sedo lowers minimum offer to $20, nixes min commissions

Domain Name Wire - Mon, 05/06/2019 - 14:21

Changes should add liquidity to domain market.

Sedo is making two big changes to its domain name marketplace. It’s a trial in place until the end of the year for now.

First, it is lowering its minimum bid from $90 to $20. If you complained about receiving $90 offers in the past, then you might want to set up a custom minimum bid for your domains. You can do this through the online system or contact your account rep to make this change.

Second, it is removing the $60 minimum commission on most domain names. (It calls these “Category 1” domains.)

This should add liquidity to the low end of the market. It didn’t make sense to sell a domain for $90 if you only netted $30.

Afternic previously lowered its minimum offer to $20. It charges a $15 minimum commission.

© 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. Report: How to Sell Domain Names on Marketplaces
  2. Files.com Goes for $725,000, But When Did it Sell?
  3. 15 domain names sell in .Club auction
Categories: Domains

GoldenState.com, Rightwing.com among top auction sales

Domain Name Wire - Mon, 05/06/2019 - 13:16

SnapNames lands some whales.

Web.com’s domain name auction platforms NameJet and SnapNames combined to sell 97 domains at $2,000 or more last month, totaling $566,000.

SnapNames led the way with the sale of 9j.com for $60,400. But here are the domains that jump out at me:

  • GoldenState.com $37,100 – It’s the nickname for California. When most people hear this term they think of the Golden State Warriors basketball team. NameJet.
  • Rightwing.com $20,900 – A big political domain that could sell for much more to a conservative publication. I own LeftOfCenter.com and frequently get inquiries on it. Rightwing.com is obviously much bigger. SnapNames.
  • Rezy.com $10,500 – If restaurant reservation site Resy.com didn’t pick up this domain, it really missed out. NameJet.
  • StreetMaps.com $6,601 – A limited pool of buyers but they have big pockets. NameJet.
  • Trendspotting.com – I wish I would have noticed this auction. NameJet.
Domain NameSale PricePlatform 9j.com60400SnapNames goldenstate.com37100NameJet kihls.com30614NameJet woolwarehouse.com29888NameJet rightwing.com20900SnapNames zhongce.com20400SnapNames onebank.com17856NameJet smartick.com15856NameJet uxv.com12500NameJet vestidos.com11488NameJet rezy.com10500NameJet aspx.com9750SnapNames collegeportraits.org9400NameJet sanbruno.com9222NameJet zgroup.com8608NameJet bdsy.com7300NameJet streetmaps.com6601NameJet aghg.com5980NameJet mortgageservices.com5766NameJet paida.com5719NameJet trendspotting.com5301NameJet continente.com5288SnapNames eyeview.com5177NameJet flattery.com5022NameJet asrv.com4655NameJet hedef.com4610NameJet suv.org4600NameJet womenactionmedia.org4600NameJet cavemen.com4540NameJet painmedicine.com4488NameJet complaints.org4400NameJet onroute.com4200NameJet redefiningpower.com4188SnapNames netter.com4089NameJet delfina.com3911NameJet comments.org3875NameJet propertyadvisors.com3755SnapNames sabana.com3736NameJet oomm.com3700NameJet petaware.com3695SnapNames nextjet.com3655SnapNames shetty.com3517NameJet sis.org3422NameJet premiercapital.com3279NameJet achoo.com3200NameJet jiaoyisuo.com3200SnapNames omusic.com3100NameJet compassroserealty.com2995SnapNames mangels.com2956SnapNames 96158.com2942NameJet verbania.com2909NameJet landmanagement.com2889NameJet insureamerica.com2800NameJet foodbag.com2711NameJet mosfet.com2710NameJet actualized.com2700NameJet popgun.com2700NameJet spxpo.com2695NameJet rennen.com2655NameJet globalauto.com2645NameJet btube.com2605NameJet w6w.com2510NameJet 68005.com2500NameJet befamous.com2500NameJet jetengines.com2480NameJet 2-8.com2453NameJet axishealth.com2441NameJet itmarketing.com2433NameJet redcrane.com2427NameJet tu3.com2414NameJet luxurydestinations.com2400NameJet animalauthority.com2395SnapNames creditclean.com2350NameJet y-g.com2334NameJet prun.com2272SnapNames bestskin.com2250NameJet portatil.com2213NameJet 82520.com2200NameJet chicago.info2200NameJet purecoffee.com2200NameJet seedsmart.com2200NameJet techgo.com2110NameJet 67005.com2100NameJet 78728.com2100NameJet focusdata.com2100NameJet opinions.org2100NameJet privacyjournal.net2100NameJet firstcrush.com2089NameJet unec.com2051NameJet pixology.com2021NameJet sockstore.com2016NameJet 23005.com2000NameJet 52113.com2000NameJet 58922.com2000NameJet 62993.com2000NameJet 87119.com2000NameJet 89116.com2000NameJet

© 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. NamesCon auction lifts Web.com sales in February
  2. Web.com aftermarket sales up to $45k
  3. 21 domain names to buy this week
Categories: Domains

ESPN takes down “ESPN Slaughter” website

Domain Name Wire - Sat, 05/04/2019 - 15:50

Army vet set up site to criticize spending on football.

An Army vet set up ESPN Slaughter to provide commentary on spending on football.

Sports network ESPN has convinced a National Arbitration Forum panel to give it the domain name ESPNSlaughter.com.

The domain name was used by a U.S. Army veteran for commentary about the National Football League.

With a name like ESPNSlaughter, you might think it had to do with the damage football causes to players’ brains. But Andrew Shulte has a different gripe: he thinks the money that goes to build stadiums and pay players could be put to better use helping society.

Schulte is a self-professed football fan but suggests a one-year NFL timeout to put money toward other causes. Of course, the NFL couldn’t pay those salaries if it didn’t play for a year, but that’s another story.

ESPNSlaughter.com mimicked an ESPN site and even had a notice “Brought to you by ESPN Media a Disney Co.”

National Arbitration Forum panelist Richard Hill found in the sports network’s favor, ruling that the domain name should be transferred.

Criticism sites are somewhat immune to cybersquatting claims but the site owner wasn’t directly attacking ESPN. He also didn’t respond to the claims.

© 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. Bid.tv domain handed over in UDRP
  2. The CloudInsure.com UDRP has a lot of open questions
  3. HeadKandy.com: why no reverse domain name hijacking?
Categories: Domains

Someone is trying to phish domain name registrars

Domain Name Wire - Fri, 05/03/2019 - 14:46

Criminal is spoofing ICANN.

Hacking individual domain name registrar accounts is so old-school. Why not gain access to an entire registrar or registry?

The Internet Corporation for Assigned Names and Numbers (ICANN) issued an alert that someone is running a phishing scam impersonating ICANN. The emails (so far) come from sales (at) icann.org. The perpetrator is sending them to contracted parties.

ICANN recently sent an email to some contracted parties from accounting (at) erp.icann.org, which it says is a valid email.

Of course, if someone can spoof the sales address then they can probably spoof the other one or typos of it.

ICANN.org has a DMARC record but not a published DMARC quarantine/reject policy.

© 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. ICANN hacked, zone file system among victims
  2. Google Duped Us
  3. Donuts sues ICANN over .web domain
Categories: Domains

GoDaddy disappoints Wall Street in Q1

Domain Name Wire - Fri, 05/03/2019 - 14:31

Numbers fall short of Wall Street’s expectations.

GoDaddy (NYSE: GDDY) reported earnings after the bell yesterday.

The company’s revenue was up 12.1% year-over-year to $710.0 million. That’s the midpoint of GoDaddy’s expectations for the quarter but fell below consensus analyst estimates. Profit also fell below Wall Street’s expectations, causing shares to drop after hours yesterday and this morning.

Bookings hit $870.5 million, up 11.2% year-over-year.

Domains revenue was $319.6 million, up 9.6% year-over-year. It was $314.3 million in Q4 of 2018.

GoDaddy had 78.2 million domains under management as of the end of the quarter. About two-thirds of the domains are .com. The company credits aftermarket growth for some of the gains.

The company expects Q2 revenue of $730 million – $740 million. Full year revenue guidance is unchanged at $2.97 billion – $3.0 billion.

© 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 GoDaddy “uses this one simple trick” to get 56,000 more registration years per month
  2. GoDaddy will continue publishing most domain owner data
  3. Two thoughts from GoDaddy’s conference call yesterday
Categories: Domains

April’s Top Stories

Domain Name Wire - Thu, 05/02/2019 - 18:31

Here’s what happened in domain names last month.

These are the top five stories on Domain Name Wire last month ranked by pageviews.

1. Clothing company tries to reverse hijack domain name – A European clothing brand filed a “factually misleading” cybersquatting case.

2. When you buy a dead person’s domain name – This group had to change its domain name after the founder died and the domain expired.

3. Time is running out to reject unlimited .Org (and other) prices – You’re out of time to comment on .info and .org but .biz is still open.

4. Sheryl Sandberg loses cybersquatting claim over LeanIn.com domain name – Her foundation uses the domain name LeanIn.org and wanted to get LeanIn.com.

5. The .App “junk drop” is coming – The first year anniversary for .app has arrived and you can expect a lot of domain names to expire.

Podcasts:

#234 (listen) – Find out how Drew Wash’s domain development challenge worked out.
#233 (listen) – Learn how to sell with Brian Harbin.
#232 (listen) – Understand .Inc’s high-cost business model.
#231 (listen) – Hear why Trevor Mauch spent $600,000 on Carrot.com.
#230 (listen) – Learn Joshua Schoen’s domain acquisition strategy.

© 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. DOMAINfest Hotel’s Domain is Expired
  2. .App most popular TLD application, .home, .inc, and .art close behind
  3. Top Domain Name Stories from May
Categories: Domains

F**K Intuit, says Intuit

Domain Name Wire - Thu, 05/02/2019 - 14:40

Tax prep company registers derogatory domains as the public dials up the heat.

Millions of Americans just finished filing their taxes. Many of them used Intuit’s TurboTax to figure out how much they owed and file their return.

Over the past month, it surfaced that Intuit and other tax preparation companies lobbied Congress in an effort to get a new bill preventing the IRS from providing free software to calculate taxes. They also hid their free file page from search engines. People don’t like Intuit.

So it might not come as a surprise that Intuit is going on a defensive domain name registration binge. Here are some of the domain names the company just registered:

  • F*ckSasanGodarzi.com (Intuit’s CEO is Sasan Godarzi)
  • HateIntuit.com
  • ScrewTurboTax.com

Registering domain names to keep them out of the hands of haters is an age-old practice. But it’s impossible to register all variations of disparaging terms, especially with hundreds of top level domains to choose from.

Here’s a full list of the domains that Intuit just registered:

f*ckbradsmith.com (former CEO)
f*ckintuit.com
f*ckquickbooks.com
f*cksasangoodarzi.com
f*ckturbotax.com
f*ckuintuit.com
hateintuit.com
ihateintuit.com
sasangoodarzisucks.com
screwturbotax.com
turbotaxexposed.com
turbotaxreport.com
turbotaxreporting.com
turbotaxreports.com
turbotaxscam.com
intuitexpose.com
intuitexposed.com
intuitinside.com
intuitinsider.com
intuitsucks.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. Google Promotes Domain Names to Small Businesses
Categories: Domains

SiteLock sues GoDaddy over troubled partnership

Domain Name Wire - Wed, 05/01/2019 - 20:03

Security company claims GoDaddy didn’t pay what it owes.

Website security company SiteLock has sued domain name registrar and hosting company GoDaddy (NYSE: GDDY) for breach of contract and trademark claims.

The two companies signed a reseller agreement in 2013 under which GoDaddy could sell SiteLock’s website security services. SiteLock charged per subscription and GoDaddy could mark up the price however much it wanted so long as it met a minimum retail price. For example, SiteLock charged GoDaddy $5 per customer for a basic annual site scan service. GoDaddy could sell it for $12 or more per year and keep the difference.

SiteLock claims that GoDaddy only paid it when a customer paid for and activated the service but did not pay if a customer paid for the service but did not activate it. It argues that GoDaddy should have paid even when a customer failed to activate the service. It also alleges that GoDaddy did not provide required reporting in an effort to obscure this.

The relationship soured further after GoDaddy bought SiteLock competitor Sucuri in 2017. GoDaddy transitioned customers to Securi and forwarded pages on its site that used to be for SiteLock products to pages promoting Securi. According to the lawsuit, links on GoDaddy for people to sign up for SiteLock instead forwarded to pages about Securi.

SiteLock is owned by Abry Partners, the same private equity company that owns top level domain company Donuts.

The full lawsuit is 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. Web design company sues GoDaddy over “It’s Go Time” slogan
  2. GoDaddy reports earnings, Domain revenue dips from Q4 but up YoY
  3. Mailbag: What’s Up With GoDaddy’s .Biz Pricing?
Categories: Domains

17 end user domain name sales up to €59,500

Domain Name Wire - Wed, 05/01/2019 - 14:03

A German travel site, several property development companies and a bitcoin trading platform bought domain names last week.

The company that developed The Edge observation deck at Hudson Yards in NYC bought another domain name.

Sedo had a lot of good end user country code domain names over the past week including SeeReisen.de for €59,500.  Also, the company that developed The Edge observation deck at Hudson Yards in New York City bought another domain name.

Here’s the list of end user sales from the past week. You can view previous lists like this here.

SeeReisen.de €59,500 – This domains translates to “Sea cruises” from German and is the top overall sale from last week. It currently forwards to UrlaubsExperte.de which translates to “Travel expert”, a German travel booking site specializing in cruise ship travel.

EdgeNYC.com $10,000 – The Related Companies, a property development company that develops both commercial and residential properties. This is for an observation deck at Hudson Yards in NYC. It bought EdgeNY.com for $2,000 a couple of months ago.

NGJ.org $8,800 – Forwards to NoGreaterJoy.org for the No Greater Joy Ministries Inc. out of Memphis, Tennessee.

SelfStorage.info $6,999 – It looks like the buyer is setting up a self storage search site.

BitcoinFuture.com $5,960 – A bitcoin trading platform.

RowingBlazers.us $5,900 & RowingBlazers.se €5,000 – Both domains were purchased by Rowing Blazers for their clothing brand founded by Jack Carlson, a former member of the U.S. national rowing team. They currently use RowingBlazers.com as their main site.

Devise.nl €4,900 – Forwards to DeviseAnalytics.com, an analytics software platform catering to ambulance services, hospitals, general practitioners and umbrella organizations in health care. Their current site is in Dutch so it makes sense that they now own the shorter Netherlands ccTLD.

Immobilien.berlin €4,900- Forwards to www.strategis.eu, or “Strategy”, a company providing sales and management solutions within the real estate sector. Immobilien means real estate in German.

M-Tower.com €3,700 – A new high-rise building being developed in Yangon, Myanmar. It forwards to M-Tower.co. This domain was sold via SedoMLS.

MisPro.com $2,999 – Mispro Biotech but the shorter version of its MisProBiotech.com domain.

AllCaps.eu €2,500 – Forwards to AllCaps.be with a message stating that they are “The platform for and by collectors of Champagne capsules” which are the foils covers for champagne/sparkling wine corks.

ShopSosie.com $2,640 – A women’s clothing online shop currently being developed.

ZDL.org €2,288 –  Center for Digital Lexicography of the German Language (ZDL). It forwards to DWDS.de, an online searchable digital dictionary of the German language supported by ZDL.

Führungskraft.de €2,500 – Forwards to FuehrungsKraft.com, a website in German offering workshops and training for executives.

NewMouth.com $2,000 – This was appropriately purchased by Dentistry Brands, LLC out of Orlando, FL.

Sport-Wear.com $2,000- Forwards to TexMarketSports.com, an Italian sportswear company that produces personalized team uniforms, exclusively for retailers.

© 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. 17 end user domain name sales including Hallmark
  2. 13 end user domain name sales from Sedo
  3. End user domain name purchases including State Street and Live Person
Categories: Domains

Endurance International falls 12% on lower forecast

Domain Name Wire - Wed, 05/01/2019 - 12:59

Domain name and hosting company lowers outlook for 2019.

Shares of Endurance International Group (NASDAQ: EIGI) fell nearly 12% in trading yesterday after the company lowered its 2019 forecast. Shares ended the day at $5.53.

  • GAAP revenue guidance lowered from $1.4 billion – $1.6 billion to $1.2 billion – $1.4 billion
  • Adjusted EBITDA forecast lowered from $310 million – $330 million to $300 million – $320 million
  • Free Cash Flow guidance lowered from $115 million – $125 million to $110 million – $120 million

Even the high end of the guidance for each of these numbers is below last year’s results. The company has been going through a reckoning as it digests all the assets it has rolled up.

Still, it had hoped for some leveling out in its numbers this year.

Endurance CEO Jeffrey Fox explained the lower expectations:

Our view incorporates updates to the plan related to timing of advancements in one of our hosting brands and delayed monetization related to certain initiatives in our email marketing and domain segments.

Endurance’s domain brands include BuyDomains, Reseller Club and Domain.com. Its hosting brands include BlueHost and HostGator.

© 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 domain name stocks did on GoDaddy’s IPO day
  2. One domain name stock is actually up today
  3. Domain names are one bright spot for Endurance
Categories: Domains

Missouri dentist tries to reverse hijack domain name

Domain Name Wire - Tue, 04/30/2019 - 18:29

WIPO doesn’t admire dentist’s creative arguments.

A WIPO panel didn’t like what this dentist was offering.

A Missouri dental practice run by dentist Brian Henningsen has been found to have engaged in reverse domain name hijacking over the domain name AdmireYourSmile.com.

Admire Your Smile, P.C. started using the “Admire Your Smile” mark after a dentist in New Jersey registered the domain name. The Missouri dentist later tried to buy the domain name but didn’t get a response. He then threated to take legal action if he didn’t receive a response. He followed up by filing a UDRP cybersquatting complaint with World Intellectual Property Organization.

Of course, that complaint fell flat on its face. Admire Your Smile, represented by Dunlap, Bennett & Ludwig P.L.L.C., tried to come up with creative arguments why the panel should make exceptions to the language of UDRP that requires a domain name be registered in bad faith, not merely used in bad faith. It even argued that the domain was renewed in bad faith.

Panelist W. Scott Blackmer wasn’t having any of it. In finding that the case was filed in bad faith, he wrote:

The Complaint argued disingenuously that the Respondent (a dentist in a distant state) was a “competitor” who registered the Domain Name “less than two years” before the Complainant began using its mark in commerce and then renewed the registration in 2017 to “disrupt” the Complainant’s business. There is no plausible evidence that the parties actually compete, and the Complainant provided no historical evidence of use of its mark beyond the unexamined claim of “first use in commerce” in its much later trademark application. The Panel found that the Complainant did not, for example, place the mark on its website until the end of 2014, seven years after the Respondent registered the Domain Name, and the Complainant did not possess a registered mark even at the time of the Respondent’s renewal of the Domain Name registration in December 2017…

…This case does seem to reflect an illegitimate domain name acquisition strategy. The Complainant adopted a business name without ascertaining that the corresponding “.com” domain name was already taken. Years later, the Complainant tried to purchase the Domain Name. Years after that, the Complainant obtained a trademark registration and threatened the Respondent. It may be telling that the Complainant did not act on that threat for more than a year. There are obvious gaps in the evidence and argumentation presented in the Complaint, as discussed above, despite signs that the Complainant’s counsel was aware that the third element, bad faith, would appear on its face to be impossible to establish.

© 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. Gesab, S.A. tries to reverse domain name hijack DeskWall.com
  2. CEAT tire company fabricated evidence, panel determines
  3. Tambour Ltd filed complaint that was “bound to fail”
Categories: Domains

Is Fox gearing up for sports betting?

Domain Name Wire - Tue, 04/30/2019 - 18:03

Domain names suggest some sort of sports betting is in the works.

Last year NBC Sports registered many domain names related to sports betting including NBCSportbook.com and NBCSportsSportsbook.com.

It appears that Fox might also be gearing up for sports betting. A company just registered these domain names:

foxbetaccumulator.com
foxbetdailyfantasy.com
foxbetdfs.com
foxbetfantasy.com
foxbetfantasygames.com
foxbetfavorite.com
foxbetmountairy.com
foxbetparlay.com
foxbetpools.com
foxbetpredictor.com
foxbetsdfs.com
foxbetspreads.com
foxbetsyndicate.com
foxbetvirtualhorseracing.com
foxbetvirtualsports.com
foxfantasygames.com
foxfantasysports.com
foxsportspoker.com
foxsportsvegas.com

The domain names were registered at brand protection registrar MarkMonitor using a Whois privacy service. Fox uses MarkMonitor for its domain registrations.

Many states are liberalizing sports betting laws, which could be a boon to networks.

© 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. Supreme Court ruling leads to domain name bonanza
  2. December’s top DNW Stories
Categories: Domains

Scams versus mistakes and why it’s important

Domain Name Wire - Tue, 04/30/2019 - 14:12

Calling a mistake a scam belittles actual scams.

Some people have extreme reactions when something goes wrong at a domain name company: they say they were scammed.

Such was the case last week with the person who thought he’d won a GoDaddy auction, only to find out a network problem caused him to think he’d won when he was really outbid.

Yes, there’s a problem with how GoDaddy’s countdown timer is set up that can lead to this issue. But saying GoDaddy is trying to scam people is very different from what really happened.

Scam is not a word that should be used lightly. The word suggests that someone had malicious intent and purposefully did something. A programming issue is not a scam. It’s a mistake.

Companies should address these issues quickly. They should be held to task if they don’t. Yet, there are two problems with labeling things as scams that aren’t actually scams:

  1. It makes you look hysterical so people won’t pay much attention to the facts.
  2. It belittles actual scams — something we need to be on the lookout for.

 

 

© 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. .Me Domain Name Auctions to Last a Loooong Time
  2. Tips to avoid getting scammed
  3. How a Whois check could have halted a scam
Categories: Domains

Drew Wash project results – DNW Podcast #234

Domain Name Wire - Mon, 04/29/2019 - 15:30

A domain development project runs into challenges.

A year ago Drew Wash set out on an ambitious plan: develop three premium domain names into websites generating $25k a month in recurring revenue. Drew returns to the show with the results. You’ll learn a lot of great domain development tips and lessons on this week’s show.

Also: Verisign stock, domain price hikes, domain renewal robocalls, The Sun and more.

This week’s sponsor: DNAcademy. Use code DNW for $50 off.

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. Drew Wash develops businesses on premium domains – DNW Podcast #187
Categories: Domains

The economics of domain name prices

Domain Name Wire - Mon, 04/29/2019 - 15:03

ICANN has a duty to cap renewal prices of domain names.

This might be your reaction to your renewal notice in a couple of years.

Today is the last day to comment on ICANN’s proposal to lift price caps on .org and .info domain names.

If approved, the registries that run .org and .info will be able to raise prices as high as they want on both new registrations and renewals as long as they give notice to the registrars. ICANN has proposed removing price caps on other domains as well.

This is a controversial topic for both domain investors and end users. It’s important to think about the dynamics of domain registration to understand the impact this will have.

Market power at the time of registration

It is technically true that there are a lot of choices when it comes to choosing a domain name. If I want to register example.com, I can choose to register a longer .com, opt for a .net or .info domain, a ccTLD or choose from hundreds of new top level domains such as example .xyz.

But let’s face it, people usually want .com. It has extraordinary market power.

Back in 2008, the U.S. Department of Justice Antitrust Division explained (pdf) this in a letter to ICANN regarding new top level domain names. It stated:

“Our investigation of the proposed .com agreement generated several findings that bear on the likely effect of creating new gTLDs. First, we found that VeriSign possesses significant market power as the operator of the .com registry because many registrants do not perceive .com and other gTLDs (such as .biz and .info) and country code TLDs (“ccTLDS,” such as .uk and .de) to be substitutes…

…We also concluded that existing gTLDS would not become a competitive threat to .com registrations because the network effects that make .com registrations so valuable to consumers will be difficult for other TLDs to overcome. Due to a first-mover advantage and high brand awareness, .com registrations account for the overwhelming majority of gTLD registrations…

Even with the introduction of hundreds of new top level domains since this letter was written, they have barely chipped away at .com’s market power.

Do other TLDs have market power? I’d argue .org does. Charities and non-profits often think of .org first instead of .com. The antitrust department noted:

“Finally, our investigation of the .com agreement found evidence that other gTLD registry operators may possess a degree of market power. The market power inherent in other gTLDs is less than the market power in .com, but is still material.”

In order of power in the gTLD market, I’d argue that .com is highest and .org is second highest. ccTLDs also have market power in some countries.

The presence of market power for initial registrations suggests that prices for some top level domains should be restricted. A non-profit is unlikely to choose .charity over .org unless it is unable to acquire the .org domain. It will usually choose an alternate, longer .org domain before choosing something else. This might not be true in twenty years but it is true in 2019.

For top level domains that don’t have market power and are easy substitutes for each other, controlling initial registration prices is not as important. That’s part of the reason people are complaining more about .org price caps than .info.

High switching costs and market power at the time of renewal

Domain names have immense switching costs. Companies that switch from one domain name to another often spend months planning the move. Some spend years. Some spend hundreds of thousands of dollars.

There are two reasons the switching costs are high.

First is search engines. Google is the lifeblood of many website’s traffic. Even the best-planned domain name transition can have serious traffic (and thus monetary) impacts. When HomeAdvisor switched its domain from ServiceMagic.com it saw a marked drop in traffic and revenue. On its conference call after switching domains, the company stated:

HomeAdvisor domestic revenue was negatively impacted by a 20% decrease in accepted service requests due primarily to the domain name change.

20% from a domain name change!

It took the company a while to regain the search rankings it had before.

Even companies that create and manage websites for a living have to expend significant resources to change domain names.

It can be done but it’s very difficult.

The second reason for high switching costs is email. Companies often have thousands of email addresses tied to their domain name. These email addresses are then tied to many online accounts. Switching domain names means updating all the mailboxes technically and all the accounts associated with them. It means emailing all customers and telling them about the new addresses. It undoubtedly means missing some important emails when the switch happens.

I have an acquaintance who was offered over $200,000 for a domain name he registered in 1997. He declined because he and his family have email addresses tied to the domain. It would mean changing hundreds of account registrations at websites and countless hours of work.

It’s one thing to switch email addresses if the company retains its prior domain name and can forward email to the new one. But if a company has to relinquish an old domain name due to renewal costs, it will miss out on this email forwarding and probably miss important messages.

These high switching costs make domain owners hostages to the registries that operate their domains. They simply have to pay whatever they are charged. The cost to switch is too much.

For this reason, renewal costs must be capped.

How domain registration and renewal costs should be managed

Some top level domains have market power at the time of registration. All top level domains have tremendous power over registrants at the time of renewal.

For this reason, ICANN should consider capping initial registry fees for top level domains that have some level of market power, such as .com and .org.

It should limit prices on all domains at the time of renewal.

The organization has stated that registrants have some protection because they can renew domains for up to ten years at current prices before price hikes take effect.

There are two problems with this.

First, the registries must notify the registrars of the price increase. It’s up to the registrars to notify customers. Busy customers might overlook these notices or not have the cash to renew for ten years today.

Second, and most importantly, this just kicks the can down the road. What does a company do ten years from now when it has to pay the new rates.

© 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. Donuts demands $22.5 million for .Web domain name
  2. Here’s what happened to ICANN on Capitol Hill yesterday
  3. Gleissner firm backs down in fight against Expensify over “Concierge”
Categories: Domains

Verisign stock tops $200 per share

Domain Name Wire - Fri, 04/26/2019 - 17:45

It’s not quite the dot.com boom, but Verisign’s share price has hit a key number.

Verisign’s (NASDAQ: VRSN) stock price has eclipsed $200 per share for the first time since the dot com boom. Shares briefly traded for above $250 in March 2000 before the bubble burst.

The company’s market cap is about $24 billion. It peaked at nearly $40 billion in 2000. Verisign’s market cap has tripled since January 2017.

Shares are up 6% today after the company announced earnings yesterday.

While revenue growth is slow, operating margins hovers near 70%. Investors are also hoping that the company will be able to increase prices on .com domains starting in a couple of years. This would give the company a jolt of additional revenue at 100% margin.

 

© 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 sells security business to Neustar for up to $120 million
  2. Breaking: Verisign loses appeal in .XYZ lawsuit
  3. Verisign patents “Methods and systems for creating new domains”
Categories: Domains

Verisign posts earnings, nearly 70% operating margin

Domain Name Wire - Fri, 04/26/2019 - 14:18

Results continue to tick upward as company pushes for price increases.

It’s good to be the king.

.Com registry Verisign (NASDAQ: VRSN) reported first quarter earnings yesterday afternoon.

It generated $306 million revenue for the quarter and a 69.4% non-GAAP operating margin. The business created $187 million in operating cash flow.

People registered 9.8 million .com and .net domain names in the first quarter of the year, resulting in net growth of 1.82 million in the domain base for these two top level domain names.

The company narrowed its guidance for the year by removing the lower end. It now expects $1.220 billion to $1.235 billion in revenue. It expects the .com/.net domain base to increase by 2.5% to 4.25% by the end of the year.

On the conference call, most analysts wanted to understand the status of .Web (it’s in arbitration between Afilias and ICANN but Verisign wants to join the arbitration) and .com price increases (Verisign is working through a process with ICANN to get the price increases that the NTIA approved.)

© 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 patents “Methods and systems for creating new domains”
  2. How much would .Com domains cost if .com went out to bid?
  3. Verisign sells security business to Neustar for up to $120 million
Categories: Domains

Glitch causes GoDaddy auction confusion

Domain Name Wire - Fri, 04/26/2019 - 13:03

You won the auction! Or not.

A glitch caused a GoDaddy auction bidder to think he’d won an auction, only to end up the runner up.

The bidder sent a screenshot to Domain Name Wire showing that he’d won the auction for OrganicFlowers.com:

But the bidder was in for a surprise. He wrote:

Notice I won the auction fair & square, then someone else won it 5 minutes later, so shortly after I logged into my GoDaddy account to see the 2nd screenshot below and I was absolutely shocked because they were saying I didn’t win the auction, nor did they even give me the opportunity to win the auction AGAIN after I had already won it.

Here’s the second screenshot:

I reached out to GoDaddy to find out what caused this. Aftermarket GM Paul Nicks stated:

We have identified an issue that could cause the auction countdown timer to continue running even though the connection between the user’s computer and the server times out. This can happen from network latency anywhere along the path. Our team is working to resolve the issue now. To be on the safe side, we recommend customers refresh their browsers as auctions are ending. We apologize for any inconvenience this has caused to our auction participants.

Especially in major auctions, it seems that refreshing the browser might be a good proactive move until this problem is fixed.

© 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. GoDaddy tests new lander for expired domain names
  2. Expired domain report: Mangos, Drones and more
  3. HuaGao.com at $20k and other expired domain name sales
Categories: Domains

How to keep your domains from being stolen (2019 edition)

Domain Name Wire - Thu, 04/25/2019 - 20:38

Consider these eight safeguards to keep thieves away from your domain names.

If you own domain names–particularly good names–you are at risk of having your valuable assets stolen from you.

Thieves will try to compromise your domain registrar account (sometimes by first compromising your email account) and transfer the domains to another registrar. Sometimes they won’t change your nameservers, so you might not realize the domain name is stolen until much later. This makes it harder to recover the domain name.

Here are some tips to protect yourself from domain theft:

  1. Use two-factor authentication at your domain name registrar. Any reputable domain name registrar offers two-factor authentication. A thief then needs access to a secondary device (such as your phone number) if they want to crack into your account.
  2. Use secure email with two-factor authentication. A common way thieves get into your registrar account is by compromising your email. Once they have access to your email they can reset the password at your registrar. I’ve heard some advice that suggests you shouldn’t use free email services for your domain accounts. I disagree; web-based email services can be some of the most secure options. Consider using Gmail with a physical security key as secondary authentication.
  3. Use a different email address for your registrar account than Whois. While many registrars have masked email addresses in Whois, some still show it. Thieves use the email address on a Whois record as a starting point. They try to hack that email account to access the registrar account. One way to stump them is to use a different email address for your registrar account.
  4. Use a password manager. Another way thieves get into your registrar account is by phishing. They use your email address from Whois to ask you to log in to a fake site. They grab your credentials when you do this. Two-factor authentication (see #1) can stump them even if they have your username and password. Using a password manager can stop you from falling for the phishing scam because it won’t allow you to auto-fill your credentials on the wrong site.
  5. Remember that Whois privacy is a double-edged sword. While thieves use public Whois info to try to break into your account, masked Whois records aren’t always better. After all, if your domain is stolen it might not be reflected in the public database. It will be more difficult for you to discover that your domain is stolen.
  6. Use GoDaddy’s domain transfer verification services. This only applies to GoDaddy customers that have Premier Services account managers. The minimum to be considered is 300 domains but there are other qualifications, too. (Here are the qualifications from 2013.) With this added service, your account representative will call you to verify all domain transfers that aren’t Afternic fast transfer sales. It slows down the process but it’s a very good layer of additional security.
  7. Add transfer lock to your domains at your registrar. 
  8. Track your domains. Use a service like DomainTools to track your domains. You’ll get alerts when a domain is unlocked, transferred to another registrar, etc.

Feel free to comment about additional safeguards you take to protect your domain name portfolio.

© 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. GoDaddy Gets Stolen Domain Name Back to Owner
  2. Company sues over stolen domains after losing UDRP
  3. Lawsuit filed to recover stolen 4-number domain names
Categories: Domains

Clothing company tries to reverse hijack domain name

Domain Name Wire - Thu, 04/25/2019 - 15:56

Company was “factually misleading” and committed “egregious overreaching”.

The company that operates this website at Incanto.eu was found to have filed a cybersquatting case in bad faith.

Brooksburnett Investments Ltd, which sells clothing under the Incanto brand, has been found to have committed reverse domain name hijacking in a dispute over the domain Icanto.com.

The company uses the domain name Incanto.eu.

A three-person World Intellectual Property Organization panel did extra research to figure out if the Complainant was providing the entire truth. It decided that the Complainant didn’t show that the domain owner registered the domain in bad faith and didn’t prove that the owner lacked a legitimate interest in the domain.

Amusingly, the Complainant pointed to another UDRP filed against the domain owner as proof that he was a cybersquatter–but the panel in that case found in the domain owner’s favor.

The panel wrote:

The Complainant’s first Supplemental Filing acknowledges that the “Complainant began to optimize the business recently, began to increase the efficiency of assets. The Complainant has plans for the US market, so drew attention to the problem of respective domain names and filed this Complaint.” This does seem to be a “Plan B” filing, after the Complainant recently tried without success to purchase the Domain Name from the Respondent some 16 years after the Respondent added the Domain Name to his portfolio. The Complaint made sweeping assertions about the Complainant’s business and trademark rights and recognition that simply did not match the facts in 2003 when the Domain Name was registered and offered little or no evidence to support its claims for the “worldwide” fame of the trademarks in 2003. It required two rounds of Supplemental Filings and additional research in public record sources for the Panel to reconstruct the circumstances in 2003. The Complaint was factually misleading and had little prospect of establishing bad faith in particular, given the very limited and localized use of the mark in 2003 by the Complainant’s predecessor in interest and the generic meaning of the term “incanto”. The Complainant contended repeatedly, with no basis, that this was a “coined” term associated distinctly with the Complainant. Arguing the Respondent’s “pattern” of bad faith based on a UDRP decision that actually found in favor of the Respondent is simply one more example of the egregious overreaching in the Complainant’s approach to this proceeding.

© 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. City of Paris ordered to pay $100k for reverse domain name hijacking
  2. Turkish restaurant chain guilty of Reverse Domain Name Hijacking
  3. Nat Cohen settles Reverse Domain Name Hijacking Case
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.