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.

Public Interest Registry (.Org) tax return provides insight into registrar marketing deals

Domain Name Wire - Wed, 10/24/2018 - 10:09

Latest tax return doesn’t reflect new Afilias contract.

Public Interest Registry (PIR), which manages the .org top level domain, has filed its 2017 tax return (large PDF). It provides fresh insight into the non-profit’s finances for 2017.

It doesn’t include a number that many in the industry are eagerly waiting for: how much PIR is paying Afilias to manage the backend registry services under its new contract.

PIR put the contract out to bid in 2016. It received 20 bids and decided to stick with Afilias.

The new contract didn’t start until 2018, so we don’t yet know how much of a haircut Afilias took under the new agreement.

The 2017 tax return reveals that PIR paid Afilias $37.8 million in 2017, down slightly from $38.0 million in 2016.

Overall, PIR’s program revenue (excluding investment income) was $90.8 million in 2017, up from $85.0 million in 2016.

From a registrar cooperation perspective, PIR paid GoDaddy $1.5 million in marketing fees in 2017, up from $0.8 million in the prior year. Marketing fees are typically paid for placement and rebates.

PIR also paid Name.com $0.5 million in 2017.

In 2016, PIR paid PDR (Endurance International Group) $0.7 million. It didn’t report a payment to the firm for 2017.

The company is changing how it works with registrars starting next year. Learn more by listening to this podcast with interim CEO Jay Daley.

Public Interest Registry is expected to name a new CEO next month.

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

Related posts:
  1. .Org sticks with Afilias for backend
  2. PIR (.org) makes changes to its sales practices
  3. .Org non-profit is looking for new members of Board of Directors
Categories: Domains

Media Options acquires Zoom.com and will launch domain service on it

Domain Name Wire - Tue, 10/23/2018 - 14:38

Media Options has acquired the valuable domain name Zoom.com and is creating a domain service on the domain.

Domain name brokerage Media Options is getting ready to launch a domain name acquisition service on Zoom.com. It acquired Zoom.com last month and I spotted that the company filed for an intent-to-use trademark application for Zoom.

I reached out to Media Options founder Andrew Rosener, who told me that it will be a sort of white glove, high-value domain acquisition and consulting service.

Rosener said:

We have been working on the Zoom Domain Insight Service for over a year now but had not given it a name, but when we got the chance to acquire Zoom.com we jumped at the opportunity because it is perfect. It just says everything we want it to say about what it is we do. Zoom in on your perfect domain name This service goes well beyond domain brokerage and includes exclusive and highly curated domain lists, some of which are not available anywhere else as well as expert appraisals, analysis, defensive purchases & more. We’ll also be making another big announcement in the coming month or two that will complement our new Zoom service, but I can’t share anything about it yet.

The domain was acquired from domain investor Andy Booth. There are a couple of companies that might want to use the Zoom.com service to acquire Zoom.com–I’m thinking about the conference calling service at Zoom.us or PayPal company Xoom.

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

No related posts.

Categories: Domains

Radix discloses premium name data

Domain Name Wire - Tue, 10/23/2018 - 14:02

Top level domain company continues to generate revenue from recurring premium sales as well as one-time sales.

Radix has released more data about its premium domain sales this year.

The top level domain registry for 9 new TLDs has generated $1.5 million through recurring premium sales this year. These domains are sold at fairly low premiums that are paid each year.

Radix has also sold some domains for one-time premiums. Since August, it has sold $137,000 worth of domains with one-time premiums through Sedo as well as some registrar partners.

Notable one-time sales include design.online for $57.5K, king.online for $17.25K, air.space for $17.5K, inner.space for $15K and have.fun for $11.5k.

Last year, Radix reported $1.76 million in total premium revenue through November.

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

Related posts:
  1. Radix releases data on premium domain names
  2. MMX drops expensive renewals on premium domain names
  3. Great premium domain data from Radix
Categories: Domains

WG.de hits €65,000 reserve in Sedo Auction

Domain Name Wire - Mon, 10/22/2018 - 17:23

Two letter domain hits reserve with three days to go.

It’s been a while since I’ve seen a high dollar domain hit its reserve in a Great Domains auction a couple of days before the auction ends.

That’s the case with WG.de, which is at €65,000 with nearly three days left to go.

The highest recorded price for a two letter .de domain in NameBio’s database is $69,500, so this domain will set a new record from a public sales perspective.

There are a handful of other two letter .de domains,s in the auction. The highest bid on the others so far is VC.de, but that domain hasn’t hit its reserve.

Other notable domains to meet their reserve include Yal.com at $17,500 and Lovee.com at £7,500.

The auction ends Thursday. Bidder verification is required to bid over $10,000.

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

Related posts:
  1. Next Navigation Sells Pathology.com and More
  2. Moms.com sells for $252,000 in Sedo Auction
  3. Two domain name auctions to watch this week
Categories: Domains

NTIA chief takes jab at Donuts hiring Atallah

Domain Name Wire - Mon, 10/22/2018 - 16:59

Redl suggests cooling off period between ICANN employment and working for domain companies.

David Redl, who heads the U.S. National Telecommunications and Information Administration, took an apparent jab at the outgoing President of ICANN’s Global Domains Division in comments today.

In his prepared comments, Redl stated:

While the community has greatly improved ICANN’s accountability through the IANA stewardship transition process, there are still improvements to be made.

As one example, we need safeguards to ensure that ICANN staff and leadership are not only grounded ethically in their professional actions at ICANN, but also in their actions when they seek career opportunities outside of ICANN.

One potential fix could be “cooling off periods” for ICANN employees that accept employment with companies involved in ICANN activities and programs. This is an ethical way to ensure that conflicts of interest or appearances of unethical behavior are minimized.

The timing of the comments suggests that this is in reference to Akram Atallah leaving ICANN to run new top level domain company Donuts. Donuts hired Atallah after former ICANN CEO Fadi Chehadé’s private equity group acquired Donuts.

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

Related posts:
  1. U.S. Gov: Whois info must remain available
  2. U.S. government asks ICANN to investigate GoDaddy’s Whois policy
  3. NTIA head: No Whois is “unmitigated victory for the spammers and scammers”
Categories: Domains

Talking pork buns with Ray King – DNW Podcast #207

Domain Name Wire - Mon, 10/22/2018 - 15:30

Ray King on why he started PorkBun.com and what he has learned operating a registrar.

Ray King returns to the DNW Podcast for his once-every-100-episodes guest appearance. King (the first guest ever on this podcast) has a long history in the domain business including expired domains, new top level domains and now running a registrar. We talk about why he decided to launch PorkBun.com in such as crowded market, how he is growing the registrar and what lessons he has learned.

Also: No more founders at Donuts, changing of the guard at Media.net, Verisign’s intriguing patent application.

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

Related posts:
  1. Ray King on Marketing Domain Names – DNW Podcast #99
  2. 2017 Predictions – DNW Podcast #116
  3. Top Domain Sales of the Year – DNW Podcast #197
Categories: Domains

Escrow.com adds “Escrow Offer” service

Domain Name Wire - Mon, 10/22/2018 - 12:03

New tool lets buyers make an offer on your domain.

Online escrow company Escrow.com has added a new feature it calls “Escrow Offer“.

The feature enables potential buyers to click a button on your website and make an offer. This is opposed to making a buy now purchase. If a deal is reached, the closing is handled through Escrow.com.

When a buyer clicks the listing’s Make Offer button, it sets up a negotiation between the prospective buyer and seller. The buyer is sent to a form where they submit the initial offer.

The seller is then informed via email. Both parties may view the negotiation history on the offer management page as well as accept, counter, or reject any offer or counteroffer made to them.

Multiple buyers may negotiate with a seller on a given listing during this time. When a seller accepts an offer, the buyer is guided through the payment process. When payment is secured by Escrow.com for the listing, the negotiation is formally closed.

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

Related posts:
  1. Survey: Escrow.com Tops for Big Ticket Domain Name Transactions
  2. Impressive domain name stats from Escrow.com
  3. Online escrow companies add new features
Categories: Domains

AppDetex raises another Whois stir, Tucows responds

Domain Name Wire - Mon, 10/22/2018 - 10:26

Brand protection company claims registrars aren’t cooperating, but there are two sides to the story.

Tucows CEO Elliot Noss has responded to claims made by brand protection company AppDetex over access to Whois data.

AppDetex has raised concerns that domain name registrars are not responding to or are denying requests for Whois data when it has a legitimate interest. It made its first claims just before the ICANN conference in Panama this summer and timed its second complaint for just prior to ICANN 63 in Barcelona this week.

In its most recent complaint to ICANN (pdf), AppDetex said that registrars were only “fully complaint” to 2.5% of its requests.

In response (pdf), Noss called AppDetex out for its own non-compliance.

AppDetex has submitted (as of this letter) 1273 requests for Registrant data to Tucows-family registrars. Up until October 9th, 2018, we responded with our requirements template to all of them and had not received a single reply. The claim in their letter of contracted party failures to respond in a reasonable time frame is outrageous as they have failed to further their own requests for months.

Additionally, it seems that Facebook and AppDetex have been submitting automated queries without sufficient human review. Noss points to requests for data on “lincolnstainedglass.com” and “grifflnstafford.com” as examples. These were likely included because they include something visually similar to “insta” in them. Facebook has trademarks for Instagram.

Noss wrote:

We are also concerned that, given the clear lack of human-review and due care presented by the requests we have received from AppDetex, they are simply creating algorithms to identify potential infringements and demanding personal Registrant data for these potentialities wholesale. The examples we have noted above—and many others—could have been easily identified by AppDetex prior to submitting to Tucows if they had included the reason that the domain was suspected to be infringing, rather than the mere assertion that it “misuses one or more of the following trademarks” and then listing seven trademarks. We require that requests for personal data include the reason for the valid request.

Tucows, the second largest domain name registrar, has been one of the registrars leading the discussion on the EU’s GDPR. Earlier this year it launched a site for parties to request access to masked Whois information.

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

Related posts:
  1. Tucows Sells $1M Domain Name Portfolio; Domain Parking Flat
  2. Forbes Explains How Tucows’ CEO Plays Video Games to Become a Better Leader
  3. Consensus be damned: here’s how transfers will work at Tucows after GDPR
Categories: Domains

BTSA.com: Cybersquatting or RDNH? You decide.

Domain Name Wire - Fri, 10/19/2018 - 17:21

WIPO panelist makes a questionable decision.

World Intellectual Property Organization panelist Warwick A. Rothnie has determined that the owner of BTSA.com is cybersquatting and that the domain should be transferred to BTSA Biotecnologias Aplicadas, S.L.

Rothnie’s decision is surprising. You can make a good argument that this was actually a case of attempted reverse domain name hijacking.

It’s a bit convoluted because the domain name is financed by Domain Capital. Rothnie decided that the financing company is the true owner of the domain, which it financed in 2014. But the fact is that the beneficial owner registered the domain in 2003.

Although the Complainant says it existed prior to that, it didn’t register a domain for its website until 2004.

The Complainant has a registered trademark for BTSA BIOTECNOLOGÍAS APLICADAS as a figurative mark. Rothnie found this confusingly similar to the BTSA.com domain name.

What’s quite clear from reading the decision is that the beneficial owner of the domain acquired the domain for its value as a four letter domain, and that is how Domain Capital likely financed it. The decision says the domain was parked but did not show ads related to the Complainant.

That’s not cybersquatting.

The Complainant says it first discovered the use of BTSA.com when it decided to set up a subsidiary in the United States. It tried to acquire the domain and that failed. It then filed the UDRP.

I’d make an argument that this is a case of Plan B reverse domain name hijacking, not cybersquatting.

If nothing else, it’s not a clear case of cybersquatting and I believe Rothnie made the wrong decision.

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

Related posts:
  1. Defunct app maker hit with reverse domain name hijacking
  2. Reverse domain name hijacking in Hakoba Saree case
  3. Flying Dog Brewery tries to hijack domain name
Categories: Domains

Will Trump Administration give the green light to higher “tax-like” fees on domains?

Domain Name Wire - Fri, 10/19/2018 - 12:27

With the Cooperative Agreement expiring next month, U.S. businesses could face higher tax-like fees on .com domains.

The price consumers pay for .com domain names have been kept in check by an obscure agreement between the U.S. Department of Commerce’s NTIA and Verisign (NASDAQ: VRSN), the company that operates .com.

This so-called “Cooperative Agreement” expires at the end of next month and we still don’t know what’s going to happen. Will the NTIA extend the agreement? If it doesn’t, the only real check on the wholesale price of .com domains will go away. That almost certainly means price increases. And while the typical business only owns a handful of domain names, the cost to businesses overall would be high.

Internet Commerce Association (ICA), a group that advocates for domain name owners, sent a letter (pdf) to NTIA head David J. Redl yesterday explaining why it’s important to extend the group’s oversight of .com. It succinctly lays out the facts:

  • Letting the agreement expire will almost certainly lead to price increases, akin to a billion dollar+ tax on businesses and individuals over time
  • Domain name regulator ICANN can’t be relied upon to keep .com prices in check and has an incentive to let Verisign increase prices
  • Verisign’s financials and compensation already reflect a company with a monopoly contract on an important piece of the internet
  • Other companies would likely operate .com at less than half the price Verisign currently charges
  • .Com domains are still the gold standard and considered a necessity by most businesses

There’s one thing the letter doesn’t mention that a reader recently pointed out to me. Companies must now disclose their median pay, and Verisign’s is among the highest of all public companies. In 2017 it was $171,615.

ICA also has a website about the Cooperative Agreement with more details at StopThePriceIncreaseOf.Com.

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

Related posts:
  1. How much would .Com domains cost if .com went out to bid?
  2. As .Com registrations surge, is Verisign a good buy?
  3. The .Com Cliff is .Coming
Categories: Domains

CrowdSignal is PollDaddy’s new name

Domain Name Wire - Thu, 10/18/2018 - 20:23

The CrowdSignal mystery is solved.

Automattic’s PollDaddy is being rebranded as CrowdSignal.

Last week I wrote about how Automattic, the company behind WordPress, was getting ready to launch a new polling/survey service called CrowdSignal.

That was sort of right. The company will indeed soon have a service called CrowdSignal but it turns out that it’s a rebranding of the company’s PollDaddy service.

The rebrand will occur on Monday. It doesn’t sound like there will be any major changes; just the rebranding and some small cosmetic changes.

Existing PollDaddy.com URLs will forward to CrowdSignal.com URLs, although some users might need to whitelist domains used with the service.

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

Related posts:
  1. VaultPress drops its price for WordPress security and backup
  2. Automattic readies CrowdSignal survey platform
  3. WP Engine acquires StudioPress, maker of the Genesis framework for WordPress
Categories: Domains

11 end user domain name sales up to $250k

Domain Name Wire - Thu, 10/18/2018 - 17:34

A Romanian Casino, a Space Engineering firm and a language app all bought domain names last week.

It was the week of “2” last week with the top sales at Sedo across all categories (.com, ccTLD and “other”) repeating this digit within their sales prices. And even more unusual was a .RO (Romania) ccTLD purchase beating out the other sales and taking top honors with its €220K ($250k USD) price tag.

Take a look at some of the end user sales at Sedo this past week, and you can view previous weeks’ lists here.

Casino.ro €220,000 – Given the price, you can expect this Romanian ccTLD to be developed by what would qualify as an end user.

Jobster.com $200,000 – Jobster was an online recruiting business that didn’t pan out. Someone is rebirthing it. The site says, “Jobster.com Soon to be unleashed again, The jobster.com team”.

Path.net $22,000 – The top sale for the “other” category was purchased by a technology firm offering internet analytics and uptime monitoring services.

Earth.co $15,000 – A travel media company called Earth is using this domain for a travel website.

Trope.com $10,000 – Forwards to TropeReader.com, a new publishing platform who will produce films, books & periodicals on a variety of subjects annually.

Capeesh.com $8,600 – A cleverly-branded company that offers language courses. I wonder if people know how to spell this word.

PoianaBrasov.ro $5,632 – Another .RO purchase – this time it’s for Poiana Brasov, the “largest and most famous mountain resort in Romania”, also voted the most accessible ski resort in Europe by telegraph.co.uk.

EliteSA.com $5,000 – The SA in this domain refers to “Surgical Associates”, a company out of Houston providing development and management services for surgery center operations.

EPay.me $5,000 – A payment processing company run by the Narula Institute of Technology, which is made up by a group of academic institutions.

Enspace.com €2,900 – Enspace has some rather complex terminology on its page…something about satellites and ion propulsion. I’m sure rocket scientists will understand what the company does.

Soar.tech $2,399 – A Scottish tech company specializing in Apps, Web Applications, and Enterprise Scale Software Systems bought this domain name. This name has good potential for an upcoming campaign or product launch, or for a client.

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

Related posts:
  1. What domain names Mozilla and others bought last week
  2. What domain names Goldman Sachs and others bought this week
  3. More end user domain name sales
Categories: Domains

Verisign files intriguing domain backorder patents

Domain Name Wire - Thu, 10/18/2018 - 16:37

Patent describes way to sell future rights to domain names through “encoding domains.”

Verisign (NASDAQ: VRSN) has filed two patents related to buying future rights to domain names for if they become available. The process is rather unique and it makes me wonder what Verisign (which manages the .com registry) has up its sleeve.

Only one of the patent applications has been published so far. Application number 15/488984 for “Domain Name Registration Reservation Through the Use of Encoding Domain Names” was filed on April 17, 2017 and published today (pdf). The application notes that an application for “Domain Name Registration Reservation Through the Use of Encoding Domain Names for Pools” was filed at the same time, but it has not been published.

The published application describes a system for backordering domain names should they become available due to a certain event, such as their expiration on a certain date or the current domain owner relinquishing the domain registration.

This would be accomplished by registering an “encoding domain”. This encoding domain might have information about the domain right purchased or refer to a database that manages the rights. The rights could be to a specific domain name or to a pool of domain names. Here are two examples from the application:

For example, an encoding domain name that reserves a right to register example.com upon its deletion on Mar. 28, 2017 may be written as, for example, “dn–example-20170328.com”

An encoding domain name that reserves a first-priority right to select and register any domain name deleted on Mar. 26, 2017 may be written as, for example, “dp–20170326-1.com

These rights could potentially be transferred like other domains. For example, if I had the first right to register example.com if it expires, I could sell and transfer that right to someone else by merely transferring the encoding domain to them.

There could also be multiple ranked rights to the same domain. Someone could have the second right to register example.com if the first person does not exercise her option.

This is an intriguing idea but begs a lot of questions. What is Verisign, which controls the lucrative .com contract, up to?

I can think of a lot of things. The answer might also be disclosed in the other patent application that hasn’t been published yet.

1. Verisign wants to insert itself into the current expiration game to capture some of the profit. This would be the most controversial and surely face regulatory challenges.

2. It wants to bring order to the existing expiration process. Instead of having all the registries ping it to capture deleted domains, it could grant each registrar a set number of encoded domains for each day, giving them ranked rights to domains that expire that day. Verisign has been investigating ways to change the drop process.

3. It could be an idea stemming from new top level domains. The application mentions that new top level domains have pools or reserved domains that could be allocated. It could also be a way to allocate ranked selection of domains on the day the top level domain is released.

(While the encoded domain examples above use .com domains, the patent explains that the encoded domains can be in a different TLD than the one for which rights are granted. This might be required when a new TLD hasn’t launched yet.)

4. The idea could apply to the domain aftermarket. Someone could register an encoding domain for a set price for a domain name, and then the domain owner could be contacted asking if they want to relinquish their right to the domain for a certain price. If they do, the encoding domain right is exercised.

Certain aspects of this patent are certainly intriguing but should also cause concern for registrars, domain investors and dropcatching companies.

I had another thought about Verisign’s overall patent strategy while reading through this patent application. In 2013, Verisign discussed monetizing its patent portfolio. It has dropped that discussion (at least publicly). It would be a huge risk for Verisign to go after other registries while it works to hold onto its .com contract.

But…once is clears the Cooperative Agreement with the NTIA, one option would be to sell its portfolio to a group that grants a license back to it. That way Verisign can continue operating, get a profit from selling the patents, and be arm’s-length from any actions the buyer takes.

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

Related posts:
  1. Breaking: Verisign loses appeal in .XYZ lawsuit
  2. O.com might be coming, along with other single letter .com domain names
  3. U.S. Antitrust Division investigating Verisign running .Web
Categories: Domains

Domain Capital goes after Prince’s estate for reverse domain name hijacking

Domain Name Wire - Thu, 10/18/2018 - 14:13

Musician’s estate sued financing company over Prince.com domain name. Domain Capital is fighting back.

Domain name financing company Domain Capital has responded (pdf) to a cybersquatting lawsuit brought by the Estate of Prince Rogers Nelson. That’s the musician Prince, who later changed his stage name to a symbol.

The estate sued Domain Capital over its ownership of the Prince.com domain name, claiming it was cybersquatting.

Domain Capital loaned money to the previous owner of Prince.com. That owner defaulted and Domain Capital took over the name.

Of course, it’s silly for any one entity to claim exclusive rights to the dictionary word “Prince”, and Domain Capital calls out the estate in its response. The financing company is asking for the estate’s trademark for Prince to be canceled and is also asking for penalties under reverse domain name hijacking.

Domain Capital is represented by Jason Schaeffer of ESQwire.com.

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

Related posts:
  1. Domain Capital successfully defends H.co.uk domain
Categories: Domains

Jon Nevett leaves Donuts

Domain Name Wire - Wed, 10/17/2018 - 19:40

Nevett completes co-founder exodus from Donuts.

Donuts co-founder Jon Nevett has stepped down from the company but will remain an advisor.

Jon Nevett, one of four co-founders of top level domain name Donuts, has stepped down. He was the last remaining founder in a full-time role at the company. He will remain an advisor to the company.

Nevett ran policy for the company and helped it navigate the new top level domain application, objection and contention set settlement process.

Abry Partners acquired Donuts last month, creating a liquidity event for some shareholders. Since then, the company announced that it hired Akram Atallah from ICANN to be its new CEO. I expect there will be some more management shifts at the company in the coming months.

In the case of Nevett, he’s spent the last eight years handling policy for the company. He’s been working on new top level domains for about a decade.

Should he choose to stay in the domain industry, there are plenty of domain companies in his backyard in the Washington D.C. area.

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

Related posts:
  1. Objection Panel goes Rogue and Kills .Hospital domain name
  2. Donuts appeals ridiculous .hospital objection
  3. Donuts’ application for .Charity lives again
Categories: Domains

How to use GoDaddy appraisals to your advantage

Domain Name Wire - Wed, 10/17/2018 - 17:02

Here’s how to handle GoDaddy valuations in domain transactions.

GoDaddy’s domain appraisals are very controversial. Some people love them, some hate them. They’ve been both helpful and hurtful to my negotiations but I think you can turn them around to your advantage.

On the buy side, the GoDaddy appraisals helped me on a recent acquisition of two domains. In order to justify his price, the seller pointed to GoDaddy’s appraisals and asked a number in the same ballpark. The price was fair for how I intended to use the domains and I closed on the deal.

The sell side can be a bit trickier. When someone points you to a lower GoDaddy valuation, that’s when you need to explain the limits of an automated system.

Elliot Silver recently showed a great way to paint the picture for buyers. GoDaddy asks for higher prices on many of its domains than the GoValue. That says a lot.

There are other powerful ways to use automated appraisals, and I believe GoDaddy’s tool has been good for the industry. You just need to think about how to use it to your advantage.

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

Related posts:
  1. GroupValuation.com Offers Domain Appraisals from Peers
  2. How to use automated domain appraisals
  3. Selection bias and domain name appraisals
Categories: Domains

My three most recent domain sales

Domain Name Wire - Wed, 10/17/2018 - 15:23

They’re all a little bit different.

I mostly invest in domain names that sell in the sub-$10,000 range. There are people who are very successful at buying domains for five figures and selling them for six or more. That’s not my game, and I suspect that’s the case with most domain investors. (I’m in awe of some of the risks people take and how they work hard to make the risks pay off.)

Given that most investors don’t have a lot of six-figure domains to sell, I thought I’d run through the three domain sales I’ve made over the past three weeks. Three is a small sample size, but I think these anecdotal data points might be interesting and more typical of the experiences readers have had.

As a general practice, I don’t say what domains I sold out of respect to the buyers. I’m comfortable mentioning the price without the domain.

Sale 1: A three-word .com domain.

I acquired this domain as a closeout on GoDaddy Auctions in March of this year. It was originally registered in 2003. I had a buy now price of $7,275 on the domain at Afternic. A Canadia company bought it through the network and it required a manual transfer.

Sale 2: A .Work domain name

I registered about a dozen .work domain names when they first became available in early 2015. They only cost about $5 to register and renew so I figured it was worth the risk. I thought I had sold one .work name last year through Afternic but the buyer never paid. I had a $995 buy now price on another .work domain and it sold through Afternic this month. It sold through the network and required a manual transfer. To date, my only new TLD sales are .cloud and .work, and none for more than $2,000.

Sale 3: A domain I hand registered in 2005.

My third sale was for a domain I hand registered in 2005. This inquiry came directly via email from someone who looked me up in Whois. (That’s one of the reasons I like having domains at GoDaddy since you can make your Whois public.) We negotiated over a couple of days and settled on $4,000. The person chose to wire the money to me directly rather than use an escrow service.

Of course, during this time I have also rejected offers. Some of them were crazy low and others were close, but not quite close enough.

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

Related posts:
  1. Survey: Sedo “Most Innovative” Domain Aftermarket Company
  2. 27 end user domain buyers including 23 And Me and Indiegogo
  3. End user sales are part of Afternic’s big $2.1 million sales week
Categories: Domains

DigitalTown sells Appointment.com

Domain Name Wire - Tue, 10/16/2018 - 14:36

Company sold Appointment.com business earlier this month to unknown buyer.

DigitalTown sold Appointment.com earlier this month.

DigitalTown (OTC: DGTW) has sold its Appointment.com business.

The company disclosed the deal in its 10-Q filed yesterday. The SEC filing reveals little information about the transaction that occurred subsequent to quarter end:

“On October 9 2018, the Company sold its appointment.com division to an arms length third party.”

The domain was transferred to GoDaddy and has Whois privacy.

The 10-Q also provides details on how an investment the company received in May has fallen as cryptocurrencies have faced headwinds.

Catena Fund One, LP invested $1.659 million in the company in May in the form of 1.05 million RChain Coins (RHOC), which were valued at $1.58 USD. The company immediately started selling these coins for cash, but the price of RHOC started falling precipitously. In the second quarter of this year, the company sold what it had left for $518,181, which was $580,435 lower than the value when the cryptocurrency was received.

The move ended up being smart, though: RHOC currently trades for less than 20 cents.

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

No related posts.

Categories: Domains

Donuts loses appeal in .Web case

Domain Name Wire - Tue, 10/16/2018 - 13:35

Court of Appeals agrees that covenant not to sue is valid.

The United States Court of Appeals for the Ninth District has ruled against top level domain name company Donuts over the .Web domain name.

Donuts was one of the applicants for the .web domain name. Nu Dot Co won the auction for $135 million after Verisign (NASDAQ: VRSN) struck a deal with it to transfer the ICANN agreement for .web to it after the auction.

Donuts was upset that Nu Dot Co wouldn’t participate in a private auction for the domain name. Instead, Nu Dot Co pushed it to an ICANN “auction of last resort”. Had the auction been private, Donuts would have received about a $22.5 million payoff for losing.

Donuts went through ICANN’s normal appeals channels. When that failed, it sued ICANN in District court. The judge tossed out the suit because the application for new TLDs included a clause that the applicants would not sue ICANN. Donuts argued that this agreement not to sue is invalid.

The Appeals Court agreed with the lower court that the covenant not to sue was valid (pdf) in a decision published yesterday.

.Web still doesn’t have a green light, however. Afilias was the runner-up in the .Web auction and it is fighting the auction result through ICANN’s appeal processes.

While Donuts was upset about missing out on a payday by losing the auction, Afilias was upset that it didn’t win. Regardless of the outcome, both may benefit and get some satisfaction out of the delay they are causing Verisign. After all, Verisign did all it could to delay the launch of new top level domain names.

It will be interesting to see if Donuts’ strategy around .web changes when Akram Atallah takes over as CEO. Either way, Donuts’ fight against .web might be over. It will probably just hand the baton off to Afilias.

 

 

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

Related posts:
  1. Verisign to .Web losers: stop griping and carry on
  2. Department of Justice closes investigation on Verisign running .web
  3. Donuts’ appeal means .Web is a long way off
Categories: Domains

BidPal hit for reverse domain name hijacking

Domain Name Wire - Tue, 10/16/2018 - 13:21

Company with a history of cybersquatting claims is found to have filed a case in abuse of the UDRP.

OneCause’s parent company has been found guilty of reverse domain name hijacking.

BidPal, Inc., a company that helps charities raise money under the name OneCause, has been found to have engaged in reverse domain name hijacking over the domain name OneCause.org. The company has a history with UDRP and cybersquatting challenges.

The company lost a UDRP it filed in 2012 to get the domain name BidPal.com. It then hired a new layer and filed a federal lawsuit in 2014 in another effort to get the domain. That suit was settled  and BidPal got the domain name.

Then, late last year the company filed a UDRP to get the domain name OneCause.com. The case was withdrawn and it appears the parties settled as BidPal now uses OneCause.com.

This year it filed a UDRP against OneCause.org, and it was for this case that the company was found to have filed the case in abuse of the policy.

The current domain owner registered the domain in 1999. BidPal didn’t file for a trademark until this year. It also inquired about buying the domain first. In other words, it was a classic Plan B reverse domain name hijacking case.

Panelist Fernando Triana wrote:

In the present case, the disputed domain name was registered in 1999, for Respondent to express to storage his documents, use the email service and maintain a blog, which was described to be his “one cause”.

Complainant registered its trademark in 2018 before the USPTO, and before the first use of the trademark, Complainant offered Respondent to buy the disputed domain name, thus, demonstrating knowledge of the previous existence of the disputed domain name.

Furthermore, Complainant failed to file any evidence concerning lack of rights or legitimate interest and bad faith.

Moreover, Complainant tried to confuse the Panel regarding Respondent’s bad faith, as the Complaint asserted that Respondent is profiting from Complainant’s reputation, which is not evidenced and probably nonexistent as the trademark ONECAUSE was recently registered.

This makes me wonder what the circumstances of the OneCause.com case were and what the settlement was.

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

Related posts:
  1. Non-Profit Urban Logic Guilty of Reverse Domain Name Hijacking
  2. Zak Muscovitch gets reverse domain name hijacking win
  3. Canadian firm Obero tries to Reverse Domain Name Hijack domain name
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.