skip to content

News

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

Pocketbook e-reader company sues over Pocketbook.com

Domain Name Wire - Thu, 09/24/2020 - 17:02

After losing UDRP for Pocketbook.com, e-reader maker tries U.S. courts.

The maker of PocketBook e-readers is suing over the domain name Pocketbook.com. Image from one of Pocketbook’s regional websites.

PocketBook International SA, a company that sells ebook readers, has filed a lawsuit (pdf) to try to get the domain name Pocketbook.com.

This is the company’s second attempt to get the domain name. It lost a UDRP for the domain name last year.

Some of PocketBook’s customers and partners do seem to be confused that they don’t find information about ebook readers at the dictionary term domain name, and it, therefore, thinks it should be the owner of the domain name.

One example in the lawsuit is that it believes traffic to the Pocketbook.com domain name increased when it released a new version of its product. In another example, one of PocketBook’s resellers inadvertently linked to Pocketbook.com instead of Pocketbook.es in an ad. A video linked from the lawsuit filing shows that the reseller showed pocketbook.es as the URL in an e-magazine, but clicking on the link actually sends people to Pocketbook.com.

Of course, the fact that some people might hope to find information about Pocketbook’s products at Pocketbook.com doesn’t negate the fact that Pocketbook is a common term related to purses and money. As an example, I’ve used the term pocketbook several times on Domain Name Wire to refer to paying money.

PocketBook International SA made an odd allegation in its lawsuit that SiteTools, Inc. has “refused to come to an agreement” on selling the domain:

Defendants are well aware that they infringe Pocketbook’s intellectual property rights and are causing significant harm to Pocketbook. Defendants, however, have not resolved or addressed these issues, despite having knowledge, opportunity and means to do so. For example, Pocketbook has offered to purchase the Domain Name from the Defendants, but Defendants refused to come to an agreement by callously offering to sell the Domain Name for “six figures” despite the Domain Name being used only for infringing and illicit purposes.

It actually sounds to me like SiteTools agreed to sell the domain, and it was PocketBook who refused to come to an agreement and meet SiteTools’ asking price.

PocketBook seems to have country code domain names that it uses for each country it offers its products. It does not list the United States as one of those countries on its website.

Post link: Pocketbook e-reader company sues over Pocketbook.com

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Court rejects France’s appeal in France.com case
  2. Lotto Sport Italia and lotto company file dueling motions for summary judgment
  3. Facebook sues domain name registrar OnlineNic
Categories: Domains

How I’m investing in domains these days

Domain Name Wire - Wed, 09/23/2020 - 18:04

I’m planting lots of small seeds and making marginally bigger bets.

There are lots of great domain investors out there. People who make bold investments and great sales.

I am not one of those people. I’m good at it, but not great. (Note that some of the people you think are great at domain investing actually suck, and there are lots of quiet people on the sidelines who are making a mint.)

Here’s how I look at it: Domain Name Wire has been my primary business for a long time. Now, from a revenue perspective, PodcastGuests.com has caught up with it. So I have these two very high margin businesses and then domain investing, which is more capital intensive. Domain investing is something I do as icing on the top; it helps me stay on top of what’s going on in the business, to understand more when I write, and to have fun.

I don’t count on domains for cashflow. In fact, I try to reinvest everything I make selling domains into buying more domains and improving my portfolio.

Over the past few years, I’ve grown my portfolio from about 1300 domains to around 1600. I’ve pruned quite a few over that time, so my total additions is higher.

Most of my adds are low-cost auctions sub $300, and the majority of these are sub $60 including “closeouts” and uncontested expired domain auctions.

These domain acquisitions form the portfolio model of my business. This means I’m buying domains for cheap and selling them for 10x-200x the purchase price — but at median prices below $5,000.

While some of these new additions sell quickly, I look at it more like planting seeds. Most of the sales occur at least a year after I buy the domains.

Those seeds have come to fruition nicely this year. When I look at my BuyNow sales at Afternic, I have 11 sales in the past 3.5 months going back to June. The domains sold for between $495 and $5,800 with a median of $2,300. I’ve made additional sales outside of Afternic.

Lately, I’ve tried to acquire some more marquee names that could make great brands and businesses. I picked up Warmfront.com in an expired domain auction. I just bought Shortbread.com yesterday at GoDaddy Auctions. The Shortbread.com purchase alone cost the same as about 700 closeout domains. But it’s also a domain that has a decent liquid value should I ever need to cash out. The same can’t be said for 700 domains you buy in closeouts.

So that’s my model. It’s been a good year so far, and I hope it continues.

Post link: How I’m investing in domains these days

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. GoDaddy promotes domain investing on its homepage
  2. Those domains you’re sitting on? They will probably never sell.
  3. Domain investing with Logan Flatt- DNW Podcast #235
Categories: Domains

Moderna buys a vaccine domain, Microsoft sells, and more end users

Domain Name Wire - Wed, 09/23/2020 - 13:05

Moderna buys a domain and Microsoft sells one.

Xplore offers “Space as a Service”, helping companies get scientific research projects to space. It bought the domain Trajectory.com at Sedo.

Moderna, a healthcare company trying to create a Covid-19 vaccine, bought the domain ModernVaccines.com at Sedo this past week. It wasn’t the only company picking up domains.

The top two .com sales at Sedo this past week involved a trio of Seattle companies. Xplore, a private space company in the area, bought Trajectory.com. Microsoft sold OneCare.com to a health media company in Seattle.

Here’s a list of some of the end user sales at Sedo this past week. You can see previous lists like this here.

Trajectory.com $50,000 – Xplore, Inc., a private space travel company working to send science missions to space. It hopes to launch its first payloads this year or next. The domain had a previous life as a book discovery site.

OneCare.com $25,000 – OneCare Media, a health media company that runs Testing.com, Help.org and Sleep.org. It bought the domain name from Microsoft, showing that you can obtain Microsoft’s unused domains for a “reasonable” price. Of course, the buyers might have had a personal connection to people at Microsoft.

Fetchcare.com $15,000 – Treadstone Group, an intellectual property acquisition company, likely bought this for one of its clients.

LifeGoals.de €5,000 – This domain has a “Coming soon” page that suggests it will offer personal and business coaching.

BuildBid.com $4,500 – Jay Rutter Construction, a residential construction company servicing southern Louisiana, bought this domain.

ScentCard.com $4,460 – Taylor Technologies, a manufacturer of chemicals and test kits for monitoring water quality. They offer nearly 600 different test-kit configurations, including options for wet-chemistry and dry-chemistry methods, along with microprocessor-based instruments. Perhaps this will be the name for a water test for odors.

WhereBy.com$4,000 – Whereby is an online meeting service similar to Zoom. Its sales pitch is that no apps or installations are required and that the same meeting link can be used every time.

ModernVaccines.com $4,000 – Moderna Therapeutics, a biomed company that has been making headlines as a leader in developing a Covid-19 vaccine. The domain was registered for the first time in December of last year.

CopyBook.com $3,900 – RBS Global Media bought this domain. It’s forwarding it to airport-suppliers.com, a procurement portal for aviation companies.

CitrusClub.com $3,888 – This is the website for The Citrus Club, a members-only golf club at the La Quinta resort in La Quinta, California.

ForkliftRental.com $3,680 – Doggett Equipment Services bought this domain name. It is a North American machinery and construction equipment dealer representing and servicing manufacturers. It also offers construction equipment parts, new and used sales and rentals.

LabMixer.com $2,999 – This domain was bought by Smart2Test BV, a company out of the Netherlands that supplies testing equipment and machines for testing surfaces, materials, sheet metals and corrosion.

TTMotorsports.com $2,899 – TT Motorcycles bought this domain. It is a brand of motorcycles, ATVs and sport recreation vehicles and accessories.

JustWatch.org $2,400 – This domain was bought by the television streaming service JustWatch. The service aggregates all of your streaming services within one app. JustWatch.com is its current website.

Casinocruise .de €2,350 – Mediapool Communications Limited bought this domain for an online gambling website.

Vereinsbesteuerung.info $2,177 – This website provides information and referrals about taxes. It translates to “Association taxation” in German.

Post link: Moderna buys a vaccine domain, Microsoft sells, and more end users

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Microsoft buys ToDoApp.com and 16 other domain name sales
  2. 25 End User Domain Name Sales
  3. 17 end user domain name sales up to $30,000
Categories: Domains

Andy Booth launches Imperial.com for high-end domain brokerage

Domain Name Wire - Tue, 09/22/2020 - 19:54

Second brand aimed at high-end buyers.

Imperial.com, Andy Booth’s latest domain brokerage brand.

If you’re going to sell premium domains, it’s helpful to use premium domains yourself. Or two premium domains.

That’s the strategy domain investor Andy Booth is taking.

He started using Evolve.com for his brokerage last year. Now he’s adding Imperial.com as a high-end brokerage. The idea is to segment customers and attract buyers with six-figure budgets to the Imperial brand. It certainly comes across as a luxury brand (with a luxury logo, too).

The two brokerages are distinct from Andy’s brother James’ service at DomainBooth.com.

Perhaps Andy will experience the same “problem” that James did. James changed his brokerage name to Phenom, only to have to change it again when he sold Phenom.com.

Then again, changing brands isn’t a big deal when the price is right.

Post link: Andy Booth launches Imperial.com for high-end domain brokerage

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

Spase.io tries reverse domain name hijacking

Domain Name Wire - Tue, 09/22/2020 - 16:26

A new company goes after domain registered in 2005.

The owner of a business called Spase has been found to have tried reverse domain name hijacking the domain name Spase.com.

Spase is a service that converts photographs into 3D models. The business was just launched last year at Spase.io. The owner of Spase.com registered it in 2005.

In other words, this was a dead-on-arrival UDRP filing. The Complainant could not show that the domain registrant acquired the domain in 2005 to target a business that launched in 2019.

It’s another example of a case that could have been avoided if UDRP providers would ask a simple question on their intake form:

Do you claim trademark rights that predate the current registrant’s registration of the domain name?

If the answer is no, the UDRP provider can explain to the Complainant that they don’t understand the policy and are wasting their time and money.

In this case, the Complainant wasted money filing the UDRP and paying for a three-member panel as requested by the Respondent. The Respondent had to pay for the panel and hire an attorney. It was a waste of both parties’ time.

The Complainant, Sahil Gupta, was internally represented. Greenberg & Lieberman represented the domain owner Mrs. Jello, LLC. William Towns, Knud Wallberg, and Neil Brown decided the case for World Intellectual Property Organization.

 

Post link: Spase.io tries reverse domain name hijacking

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Tambour Ltd filed complaint that was “bound to fail”
  2. Russian car cam company guilty of reverse domain name hijacking
  3. “Unicorn” Nubank is a reverse domain name hijacker
Categories: Domains

GoDaddy fixes domain listing glitch

Domain Name Wire - Tue, 09/22/2020 - 13:27

Two-factor users should no longer get errors when submitting domains through Domain Listing Service.

They fixed the glitch.

GoDaddy has fixed an annoying issue with its Domain Listing Service.

Domain Listing Service allows GoDaddy customers to list domain names on the Afternic network from within their GoDaddy accounts. Customers can also have the system add a GoDaddy-branded for sale lander to their domains.

The glitch was related to two-factor authentication. A user can still be logged in to GoDaddy, but their two-factor authentication for certain services is expired. In these cases, users got an error message when submitting domains through Domain Listing Service.

The only way to fix this was to log out and log in again. Now, when this expiration issue occurs, the system re-engages the login process. Customers can re-enter their credentials and two-factor authentication and the submission process continues as intended.

Post link: GoDaddy fixes domain listing glitch

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Here’s why GoDaddy – Donuts deal makes a lot of sense
  2. This GoDaddy Premium Domain change could help you sell a lot more domains
  3. GoDaddy (finally) integrates Afternic into Domain Manager
Categories: Domains

Bytedance files cybersquatting dispute against TikToks.com

Domain Name Wire - Tue, 09/22/2020 - 04:18

Owners told a newspaper they turned down a $145,000 offer for the domain name.

TikToks.com, soon to be owned by Bytedance.

In June, the Herald Sun published an article about two Melbourne teens who have had success with online businesses. The article stated:

And about six months ago, the pair purchased the domain name TikToks.com for $2000 after predicting TikTok would become the next big social media platform.

They’ve recently been offered $US145,000 ($A209,947) to buy it, but they plan to hold it and launch the world’s first TikTok growth service.

I mentioned on twitter that the two guys gave TikTok Exhibit A for a future UDRP.

These guys just gave exhibit A to Tik Tok whenever if files a UDRP for TikToks .com https://t.co/at94MRAjHv

— DomainNameWire.com (@DomainNameWire) June 7, 2020

Fast forward three months, and TikTok’s parent company Bytedance has filed a cybersquatting complaint under UDRP against the domain. It seems like a slam dunk; the business at TikToks.com is selling followers and likes for the service.

They should have taken the $145,000.

(Thanks Elliot)

Post link: Bytedance files cybersquatting dispute against TikToks.com

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. TikTok wins fight over Ukraine domain name
Categories: Domains

Does the truth matter?

Domain Name Wire - Mon, 09/21/2020 - 19:12

False information does significant damage.

False allegations and stories seem to travel around the internet much faster than the truth. And I’m not just talking about politics.

Last week, a Hacker News story made waves when someone suggested that GoDaddy engaged in frontrunning searches; i.e., it saw what a user was searching for and then registered the domain for itself.

The story was easily proven false. The Whois for the domain in question showed that the registrant was in New York. GoDaddy then explained the search history for the term leading up to its registration.

So a false story that was easily proven wrong. But the damage was done. People now recall seeing a story about GoDaddy frontrunning, and they’ll continue to spread that story or at least keep it in mind next time they register a domain.

Don’t believe me? In a follow 0n Hacker News post that links to GoDaddy’s explanation, people still remember bad things about GoDaddy from many years ago. The problem is they are actually thinking of a competitor. One user wrote:

At least at some time in the past, registrars (and IIRC, Godaddy specifically) definitely did do this. To the point you could enter any string of random characters in their search box and it would show up in whois shortly thereafter. Apparently things have changed, but the initial accusation was not far fetched.

If I recall correctly (IIRC)? How about looking this up before saying something false about a company?

What this person is likely recalling is that a competitor did this. Network Solutions briefly engaged in frontrunning in 2008. It was a bad idea with a specific intention. Network Solutions didn’t keep the domain for themselves but reserved it so the person could only register it at Network Solutions. The company said there was frontrunning going on somewhere and did this to counter it. But it had nothing to do with GoDaddy.

Someone else wrote, “Godaddy always did this like for over a decade.”

As someone who has covered the domain name industry since 2005, I can say that this is categorically false.

Another user wrote:

I used to own [myfullname].com. I inadvertently let it expire, and godaddy immediately bought it up and listed it for purchase at multiple thousands of dollars…

When someone questioned how this user knew that GoDaddy bought it, another “helpful” commenter stated:

GoDaddy nameservers will show up in a WHOIS for the domain and GoDaddy uses a branded parking page. Attempting to register the domain would offer it for whatever sum. They don’t really hide it at all.

Anyone who regularly reads Domain Name Wire knows what really happened here. The domain expired, someone else registered it and listed it for sale.

Some helpful people in the Hacker News thread tried to point this out. And at least one person recognizes the absurdity of the whole situation:

The fact that a completely unsubstantiated accusation [1] from a throwaway HN account got an astounding 1,615 upvotes yesterday…

…really saddens me.

Like they say, “a lie gets halfway around the world before the truth puts on it boots.”

I really wish people had higher standards for actual evidence before jumping to conclusions…

Post link: Does the truth matter?

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. GoDaddy Allows Transfers After Whois Changes
  2. GoDaddy Group Registers 30 Millionth Domain Name
  3. Domain search progressing, but still not ready for new top level domain names
Categories: Domains

OneWord.Domains adds great new filtering metric

Domain Name Wire - Mon, 09/21/2020 - 17:15

You can now see how many top level domains a word is registered under.

OneWord.Domains now shows how popular a word is across top level domains.

OneWord.Domains is a site dedicated to helping people find available one word domain names across many different top level domain names.

Not all one word domains are great domains, though. So the site has added a new sorting feature to make it easier to find the best available domains: registered percentage.

This new feature lets you sort lists by the number of top level domains the keyword is registered in. It currently shows the percentage the domain is registered in the top 35 top level domains.

Sorting by registered percentage surfaces keywords like handsome, carefree and celebration, compared to low-registration words like commendably, courageousness, and convincingly.

Previously, you had to sort through long lists of subpar domains. The new feature makes it much easier to surface the best options in any given top level domain.

Post link: OneWord.Domains adds great new filtering metric

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. New site shows available one-word domain names
  2. One Word Domains site releases version 2.0
  3. OneWord.Domains adds more top level domains and features
Categories: Domains

Web businesses during the pandemic – DNW Podcast #304

Domain Name Wire - Mon, 09/21/2020 - 15:30

How are web businesses faring? It depends on the audience.

By now, we have a good idea about what is happening in the domain name industry due to the pandemic. But what about developed websites? The answer, unsurprisingly, is that web businesses are experiencing mixed results. Peter Askew runs three sites: one that sells onions, another that connects ranchers with jobs, and one that helps families find birthday party venues. On today’s show, Askew explains the ups and downs of his businesses during Covid-19.

Also: .Com milestone, Voice.com negotiation details, Ritual.com, crazy UDRPs and more

Sponsor: Donuts

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

Post link: Web businesses during the pandemic – DNW Podcast #304

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. A Viral Onion Story with Peter Askew – DNW Podcast #238
  2. Reviewing this year’s predictions – DNW Podcast #161
  3. Domains in Hollywood – DNW Podcast #282
Categories: Domains

Saudi Aramco tries to take dead man’s domain name

Domain Name Wire - Fri, 09/18/2020 - 16:42

Company tries to use UDRP to take domain registered in 1997 by now-deceased man.

One of the world’s most valuable companies just plumbed new depths in cybersquatting disputes.

Saudi Aramco, the $133 billion Saudi Arabian oil company, filed trademarks for a new brand called Orizon last year. Naturally, the company would like the domain Orizon.com.

But there’s a problem.

Orizon.com was registered in 1997 by Orizon Multimedia Inc. The company used the domain for its business but then shut down. Apparently, the owner of the business passed away last year.

So Saudi Aramco decided to file a cybersquatting complaint under the Uniform Domain Name Dispute Resolution Policy (UDRP) to try to get the domain.

Here’s the thing: in order to win a UDRP case, a trademark holder must show that the domain was registered in bad faith when it was initially registered.

Clearly, the registrant did not register the domain in bad faith since he used it for his legitimate business. Oh, and he registered it more than two decades before Saudi Aramco decided to adopt it as a brand, so it wasn’t registered to target Saudi Aramco.

World Intellectual Property Organization panelist Nick Gardner correctly ruled that this isn’t a case of cybersquatting. He considered if it was reverse domain name hijacking but, ultimately, gave Saudi Aramco a pass. One of his reasons: since the domain owner is dead, he wasn’t burdened by Saudi Aramco’s filing.

Fish & Richardson P.C. represented Saudi Aramco.

Post link: Saudi Aramco tries to take dead man’s domain name

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Denver Nuggets and Jim Carrey Fight for Domain Names
  2. Can this one simple step save you in a UDRP?
  3. Naturals.com loss is a “win” for Indian law firm
Categories: Domains

Is an app really necessary?

Domain Name Wire - Fri, 09/18/2020 - 16:37

Another company shuts down its app to focus on the mobile web.

“We’ve got have an app!” – businesses everywhere

But do they, really? Or is an app just a lazy way of making a mobile-friendly website?

I was reminded of this earlier this week when TransUnion canned its TrueIdentity app. The app allowed people to lock/unlock their credit report on TransUnion.

The company said it shut down the app because “we’ve focused on building an enhanced mobile experience on our website”.

Google has also started shutting down its apps. The company terminated its Adsense apps to focus on its mobile experience. Google said it makes more sense to focus its resources on one common platform (the web) rather than three (iOS, Android).

That said, businesses might benefit from maintaining apps because it’s like getting a bookmark on customers’ mobile phones. People are more likely to use a service if they see an icon on their phone whenever they use it.

Post link: Is an app really necessary?

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. YouTube Goes Geo
  2. Google Thinks You Like TheDomains.com
  3. Google Adwords’ Ebay Problem
Categories: Domains

SZ.com is latest two-letter domain to sell to China

Domain Name Wire - Fri, 09/18/2020 - 12:51

Another two letter .com domain sale.

The premium domain SZ.com has sold. According to the Whois record at Godaddy where the domain is registered, the domain was updated on September 16 and the owner is located in the Fujian Province of China.

SZ.com was registered in 1995 and I could not find any price information for the domain. Namebio has the following recent sales of two letter domains, so I speculate that the price for SZ.com would be high 6 figures or more.

Domain Price Year OA.com $609,068 2020 TM.com $1,250,000 2019 IJ.com $550,000 2019 RX.com $1,000,000 2019 OL.com $900,000 2019

A lot of two letter domains are owned by Chinese companies or investors, and the reason was explained in my last article Why are 2L (letter-letter) domains so sought after in China?.

Domain Meaning Assistant reports 2660 Chinese phrases which can be represented by SZ as an acronym. Many of the phrases are well-known throughout China, as shown in the following examples.

Pinyin Chinese Meaning/significance Shen Zhen 深圳 City named “Silicon Valley of China” Shi Zhuang 时装 Fashion, category defining name San Zang 三藏 Monk in “Journey to the West” story Shen Zhou 神州 Old name for China Sun Zi 孙子 Author of ancient book “The Art of War”

As I have said many times, two letter domains are sought after by corporate China because they are not only short but can also help Chinese companies go global.

Post link: SZ.com is latest two-letter domain to sell to China

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

Web.com loses WebCentral bidding war despite 80% increase

Domain Name Wire - Fri, 09/18/2020 - 03:28

Australian registrar drops Web.com despite higher bid.

“But mine is bigger than his!”

It looks like Web.com’s planned acquisition of Australian domain name company WebCentral isn’t going to happen after all.

Web.com offered AUS 10 cents per share ($12.2 million total) for the company in July. An Australian internet company, 5G Networks, then made an all-equity acquisition offer. Web.com increased its bid to 15 centers per share, and then 18 cents, but WebCentral determined that the 5G Networks offer is better. This is despite the Web.com offer being more than the 5G Networks offer at today’s share price.

WebCentral’s justification for accepting the lower price is that the equity in 5G Networks will allow shareholders to realize upside to the business, and it should be easier to close the 5G Networks offer compared to the Web.com deal.

Web.com will receive a $500,000 breakup fee for its troubles.

Post link: Web.com loses WebCentral bidding war despite 80% increase

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Web.com scoops up Aussie domain business Webcentral for AUS $12.2 million
  2. Web.com ups offer for WebCentral by 55% after competing bid
  3. Web.com buys Dreamscape for USD $73 million
Categories: Domains

How Microstrategy got its domains and sold Voice.com for $30 million

Domain Name Wire - Thu, 09/17/2020 - 19:40

CEO tells the Voice.com story.

MicroStrategy sold the domain name Voice.com for a record-breaking $30 million.

MicroStrategy (NASDAQ: MSTR) is both domain famous and bitcoin famous.

The company acquired lots of great domain names early on, such as Alert.com, Courage.com, Mike.com and Usher.com.

Then, last year, the company sold one of its domains for a record amount: Voice.com for $30 million.

Voice.com sold to a cryptocurrency company. MicroStrategy then went big on bitcoin, buying $425 million of bitcoin.

MicroStrategy CEO Michael Saylor was on The Pomp Podcast this week.  He talked about why his firm acquired so many great domains and gave details on selling Voice.com.

It’s a great interview. Saylor explains that the first offer was for only $150,000, and he kept ignoring them. He told them not to bother him until it was at least $10 million.

The embed below starts at the point he begins discussing domains.

Post link: How Microstrategy got its domains and sold Voice.com for $30 million

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Record breaker: Voice.com domain name sells for staggering $30 million
  2. Yes, Voice.com is the most expensive (publicly announced) domain ever sold
  3. Top stories: a record-smashing domain sale
Categories: Domains

Denmark firm tries reverse domain name hijacking Mountaintop.com domain

Domain Name Wire - Thu, 09/17/2020 - 18:28

Panel determines the case was “dead on arrival”.

Mountain Top ApS, which manufactures covers for pick up truck beds, has been found to have engaged in reverse domain name hijacking over the domain name Mountaintop.com. The company uses the domain Mountaintop.dk for its website.

The owner of the domain registered in 1995. The Complainant argued that there was a transfer in ownership in 2012-2013 and that this should count as the registration date. But the transfer was merely a change of registrant name involving the same owner. Even if it was a transfer, the new owner used Mountaintop in its brand, showing rights or legitimate interests in the domain. (Mountain Top claims common law trademark rights dating to 2002, hence its desire to show a transfer date after it claims rights).

The domain owner has used the domain for a personal blog and email.

While the Complainant could not find the owner’s full details in Whois at the time it filed its case, it was made aware of them during the verification phase and did not withdraw the case. A bit of additional research before filing the case would have shown the domain’s use over the years, too.

A three-person World Intellectual Property Organization panel ruled that this was a case of reverse domain name hijacking even though the domain owner didn’t ask for it.

…This Complaint was dead on arrival and likely would have been denied had there been no Response. The Complainant’s entire case on bad faith is that the Respondents registered the Disputed Domain Name intending to sell it to the Complainant. Not only is this allegation supported by no evidence at all, the charge is grounded on a theory of constructive notice that has long been held to be inadequate for Policy purposes (see WIPO Overview 3.0, section 3.2.2) and the obviously spurious statement that “mountaintop” is not a common term. The Complainant, which bears the burden of proof on each Policy element, did at best minimal due diligence once it learned the identity of the Respondents – enough to find that the Respondent Business used the term in its business name, something that normally constitutes bona fide use. “Ordinarily if the face of the complaint itself demonstrates a settled reason why the complaint must be denied, a panel may make a finding of RDNH.” Tarheel Take-Out, LLC v. Versimedia, Inc., WIPO Case No. D2012-1668, quoting from Liquid Nutrition Inc. v. liquidnutrition.com/Vertical Axis Inc., WIPO Case No. D2007-1598.

The Complainant’s allegation that the Respondents acquired the Disputed Domain Name to sell it to the Complainant has no evidentiary support. It is wholly inconsistent with the fact, documented in the Response, that the Respondents have never offered or invited offers to sell the Disputed Domain Name and did not respond to the Complainant’s offer to purchase the Disputed Domain Name for that reason.

The Complainant also failed to demonstrate that it had been targeted by the Respondents or provide any evidence to support a conclusion that an individual or organization in the United States was likely to be aware of the use of the Trade Mark (a common English word mark) by a Danish automotive parts supplier.

The Panel considers the Complainant likely launched the proceeding either in anticipation of a default or, more likely, to encourage the Respondents to engage in negotiations with the Complainant to sell the Disputed Domain Name. Either such motive belies the Complainant’s undertaking, required by paragraph 3(b)(xiii) of the Rules, “that this Complaint is not being presented for any improper purpose”…

It appears that Mountain Top’s interest in the domain might be because it’s opening a production plant in the U.S. it announced the plant yesterday.

Elmann IPR Law Firm represented the Complainant. John Berryhill represented the Respondent. The panelists were John Swinson, Andrew Lothian, and Richard Lyon.

Post link: Denmark firm tries reverse domain name hijacking Mountaintop.com domain

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Another day that ends in Y, another reverse domain name hijacking
  2. Tambour Ltd filed complaint that was “bound to fail”
  3. “Unicorn” Nubank is a reverse domain name hijacker
Categories: Domains

This should have been reverse domain name hijacking

Domain Name Wire - Thu, 09/17/2020 - 16:30

This UDRP should have never been filed.

OSRAM GmbH, a German lighting company, has lost a UDRP against a Vietnam-based cloud services consultancy. Even though the Respondent didn’t reply to the dispute, this seems like a clear cut case of reverse domain name hijacking.

The lighting company filed the dispute against OSAM.cloud. The domain name is one letter off from its trademark, and this could be a case of cybersquatting under very different circumstances.

OSAM.cloud forwards to OSAM.io, the website for a cloud consulting company in Vietnam. It clearly uses the domain name for a real business.

The lighting company offers some cloud services and connected services, hence its argument for cybersquatting. But its complaint is way off the mark.

OSRAM argued:

Respondent’s choice of the disputed domain name, which is identical to the well-known Complainant’s registered trademark ‘OSRAM’, clearly indicates bad faith intent to register and use of the disputed domain name. Apart from the above, the Respondent has not attempted to make any bona fide use of the disputed domain name. […] It is obvious that the Complainant’s famous trademark is being used in order to attract potential buyers to the website to which the disputed domain name resolves. Here, the Respondent practically using the Complainant’s trademark color and stylization knows about the worldwide well-known Complainant’s trademarks ‘OSRAM’.”

To suggest that the Respondent is using the domain to confuse OSRAM customers strains credulity.

In denying OSRAM’s case, panelist Scott Blackmer wrote:

As noted in the factual discussion above, the Respondent’s website reflects a registered and fully functioning consultancy business operating since 2017 with a website at “www.osam.io”. The Domain Name is a relevant addition to the Respondent’s domain name portfolio, as its gTLD “.cloud” is pertinent to the cloud services business in which the Respondent is engaged. The Respondent advertises consulting to assist clients in using AWS-hosted cloud services, and the Respondent is indeed listed as a partner by AWS since 2017. The Respondent appears in multiple media articles and directories, consistent with the story told on the Respondent’s website. On the face of it, there is nothing on the Respondent’s website that mentions the Complainant or competes with its business. There is simply an unrelated business with a name that differs from the Complainant’s mark by one letter. On this record, the Panel does not find persuasive evidence to support the Complainant’s inference that the Respondent chose the name of its business and the corresponding Domain Name in an attempt to misdirect Internet users for commercial gain.

OSRAM also argued that the logo on OSAM’s website was similar. The panelist (rightfully) noted that this is not the case.

Blackmer deserves kudos for doing his simple research of the Respondent in light of no response. I think he should have gone a step further and found reverse domain name hijacking.

Post link: This should have been reverse domain name hijacking

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Seinfeld Isn’t Laughing about JerrySeinfeld.com
  2. Bespoke.com saved in UDRP, but no RDNH and unbelievable dissent
  3. Nirvana gets domain names from Australian man who demanded $1.5 million
Categories: Domains

You can still pick up Pinyin domains from the drops

Domain Name Wire - Thu, 09/17/2020 - 15:15

Good quality Pinyin domains drop every day.

I thought most meaningful Pinyin are already owned by Chinese investors because there are over 900 million internet citizens and a large pool of investors in China. These Chinese domain investors even triggered the global domain boom in 2015/2016.

Therefore, it amazes me to see Pinyin domains dropping regularly in the last few months. For example, the following 10 Pinyin domains are now available for registration as of this writing.

Domain Pinyin Chinese Meaning Haidiou.com Hai Di Ou 海地鸥 Gull of sea and land Hongshuli.com Hong Shu Li 红薯里 Sweet potato neighborhood Longyishun.com Long Yi Shun 龙一瞬 Dragon, in the twinkle of an eye Jinxingchang.com Jin Xing Chang 尽心尝 Try wholeheartedly Wogeke.com Wo Ge Ke 握个客 To grasp individual customer Aidatan.com Ai Da Tan 爱打探 Love to scout out Fengmidi.com Feng Mi Di 蜂蜜帝 Emperor of honey Gushutang.com Gu Shu Tang 古书堂 Hall of ancient books Jingfuxin.com Jing Fu Xin 静福心 A heart with tranquility and happiness Kailanna.com Kai Lan Na 凯蓝娜 Triumphant, blue, elegant

As you can see, many of these Pinyin domains are quite short –- fewer than 10 characters. Imagine investing just $10 to acquire a domain such as Fengmidi.com to develop it into a business empire supplying honey to 1.4 billion consumers in China. The opportunity is unmeasurable!

The interesting thing is that I do not deliberately look for Pinyin domains. In fact, I mainly invest in English-based domains but somehow Pinyin names just come across my desk as I scan domains provided by ExpiredDomains.net every day.

Post link: You can still pick up Pinyin domains from the drops

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. A four character domain for $16,500? Here’s why
  2. These Chinese companies use English brands and domains only
  3. A quick expired domains tip for finding valuable domains
Categories: Domains

How Ritual.com got its domain name

Domain Name Wire - Thu, 09/17/2020 - 01:33

The company made a unique trade to get the domain it wanted.

This week on This Week in Startups with Jason Calacanis, Ritual founder Katerina Schneider explained how her company got the domain name Ritual.com.

Schneider explained the importance of having a great domain name. When it comes to vitamins, trust is key. And owning a great domain like Ritual.com gives instant credibility to her company.

Right off the bat, she knew she wanted her company to be known as Ritual, not Ritual Vitamins.

So she contacted the owner of Ritual.com. He wasn’t willing to sell for a price she was willing to pay. But in talking to him, she found out that the Ritual.com owner really wanted Jolt.com for his business and couldn’t get it. So Schneider worked out a deal where she acquired Jolt.com for some cash and equity, and then traded this to the Ritual.com owner.

It’s a fascinating story. See the clip below and the full episode here.

In this week’s episode,

Categories: Domains

Bodis dumps shady zero click programs

Domain Name Wire - Wed, 09/16/2020 - 20:56

Enough is enough, Bodis founder says.

Domain name parking company Bodis announced today that it has punted six zero click ad partners from its network.

Zero click ads monetize domains by directly forwarding a domain visitor to an advertiser’s page. No clicks are required, hence the term “zero” click.

The idea is good in theory. Unfortunately, zero click networks are rife with scammy landing pages. Instead of someone who visits your travel-related domain being forwarded to a travel website, they are often forwarded to fake virus notices, sites that trick users into downloading a plugin, and other scams.

It’s a difficult problem to solve. Advertisers on zero click networks a safe URL to get approved. Then they will forward the safe URL to a bad URL after the ad network stops paying attention.

Zero click ads will sometimes bounce between several URLs before landing on a final destination.

The final straw for Bodis was an incident today in which a zero click forward went to a fake tech support site.

Bodis founder Matt Wegrzyn wrote:

What once started as a valuable monetization channel has recently turned into a battle for the bottom, with our partners bidding on traffic as cheaply as possible with little to no concern over what is shown on your domains.

We have tried to police ads to the best of our ability, using 3rd party tools to do so, but we no longer believe that the vast majority of ZC partners have you, the domain owners, best interests at heart.

Domain name company CentralNic recently entered into the zero click market with its acquisitions of Tonic and (soon) ZeroPark. I hope that CentralNic can take the lead in making sure that zero click is clean, and thus a viable monetization option.

Post link: Bodis dumps shady zero click programs

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Direct nav company files patent application for bidding on domain parking traffic
  2. Just how much traffic do .Cm typos get? A lot…
  3. CentralNic’s gutsy acquisition will transform the company
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.