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.

Blockchain.io domain owner fights back against Blockchain.com

Domain Name Wire - Tue, 02/12/2019 - 22:17

There is indeed a big elephant in the room.

Paymium, SAS, which owns the domain name Blockchain.io, has asked a court to dismiss a lawsuit brought by Blockchain Luxembourg S.A. & Blockchain (US), Inc., which own the domain name Blockchain.com.

Blockchain Luxembourg S.A. (BL) filed a lawsuit (pdf) in September claiming that Paymium’s use of Blockchain.io infringed BL’s “Blockchain” trademark.

BL even suggested “Except for two letters, Paymium’s URL www.blockchain.io is identical to Blockchain’s URL www.blockchain.info.” Indeed, many top level domains are just a couple of letters off from each other, but that doesn’t give the owner of a second level domain in one extension the right to the same domain in another extension.

In its Motion to Dismiss, Paymium writes:

The deference standards of Twombly and Iqbal do not obscure the elephant in the room – this lawsuit is an improper grab at trademark exclusivity in the word BLOCKCHAIN, perhaps
the hottest technology buzzword on the planet. While Plaintiffs were prescient and resourceful enough to obtain the domain names blockchain.com and blockchain.info, they may not properly leverage that foresight into an anti-competitive and unearned monopoly in the term.

BL filed an amended complaint earlier this month.

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

Related posts:
  1. Donuts challenges .Charity decision
  2. Canadian firm Obero tries to Reverse Domain Name Hijack domain name
  3. Innovation HQ asks USPTO to cancel “Weeds” trademarks
Categories: Domains

Here, let me re-write that for you

Domain Name Wire - Tue, 02/12/2019 - 16:16

A couple of other ways to respond to a perceived “low-ball” offer.

Yesterday, Konstantinos Zournas published his response to an offer from Marksmen for one of his domain names. Konstantinos asked for $12,500 and Marksmen responded with:

Thank you for your email.  Unfortunately, your price is well above our budget for the ********* domain.

We have done some research and cannot find justification to pay that much money for *********.  Godaddy appraises the domain at $1035.

[Link to GoDaddy appraisal]

We would like to offer you $1500 for the domain.  This is our max budget and final offer.  Can you please let me know if this is acceptable and we can have a deal?”

You can read Konstantinos’ response here.

Let me suggest a couple of other responses he could have made.

Response 1: The I-don’t-think-we’ll-do–deal-so-I-won’t-waste-my-time response:

$12,500 is my final offer. Please let me know if you accept or not.

Response 2: The maybe-they-are-just-posturing-so-let’s-talk response:

You probably overlooked it when you sent your first email, but this is Konstantinos Zournas from the blog OnlineDomain. Marksmen is familiar with my blog and has retweeted some of my posts. I understand the value of domain names.

I know you’re aware of the limitations of automated appraisals. If $1,500 is your final offer then we won’t be able to make a deal. My asking price is still $12,500.

Of course, Konstantinos can respond to emails however he’d like. These are just some other suggestions that might work for you.

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

No related posts.

Categories: Domains

Why Domain Reputation matters for email

Domain Name Wire - Tue, 02/12/2019 - 15:02

Services such as Gmail consider a domain name’s reputation when delivering email.

On the DNW podcast yesterday I spoke with Anthony Chiulli of email deliverability company 250ok. One of the topics we discussed was domin reputation.

Mailbox providers (MBPs) and ISPs use a number of cues to figure out which email is good and which isn’t, and domain name reputation is a key component of this.

Previously, most MBPs focused on IP address reputation for scoring email and deciding what to deliver to users. This has shifted in recent years to domain-based scoring, often in addition to considering the IP address. After all, a spammer can easily rotate IP addresses. Also, an IP address can be used by more than one sender and domain name. Companies such as Gmail and Oath (Yahoo! Mail) use domain reputation.

Here are some things that can negatively impact a domain name’s reputation in the eyes of a mailbox provider:

  • A lot of the email from the domain is sent to invalid email addresses (i.e. it bounces)
  • The domain is used to send spam to spam traps that MBPs and other companies set up to track spam
  • Lots of people mark email from the domain as spam
  • People don’t engage with emails sent from the domain

If you buy an expired domain or a domain from another person and plan to use it for email marketing or account emails, it’s worth verifying the domain’s reputation before putting it to use. More on how to do this in a later post.

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

No related posts.

Categories: Domains

Extended NamesCon domain name auction ends Wednesday

Domain Name Wire - Mon, 02/11/2019 - 21:27

Most domains haven’t hit reserve yet.

The extended online auction for this year’s NamesCon auction ends on Wednesday. There’s a lot of bidding activity already but most of it is below reserve prices.

CPU.com is the highest at $606,000. There are four bidders at $600k or more, which is somewhat surprising given that the reserve range is between $600,001 and $700,000. Either some people know the reserve and are underbidding or there are several people interested in taking this domain home.

The highest bid on a domain that has met its reserve is LondonFashion.com at $1,333. Other domains that will sell (all under $500 so far) include Tazed.com (be careful how you use that), Plunged.com, JarCandle.com, Akxs.com, BioMedEngineer.com, BioMedEngineering.com, Boater.club, Decriminalized.com, SmartSki.com, YourDate.com, Race.info, and Sciv.com.

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

Related posts:
  1. NamesCon live domain auction results and extended auction info
  2. 10 notable sales on NameJet last month
  3. 10 notable NameJet sales last month
Categories: Domains

The Email Episode – DNW Podcast #223

Domain Name Wire - Mon, 02/11/2019 - 16:30

How email works and why domain reputation matters.

Despite the prevalence of instant messaging, social media and tools like Slack, email remains the primary way people communicate online. And email requires domain names. On today’s show we talk with Anthony Chiulli, Director of Product Marketing for email deliverability and analytics company 250ok. Anthony explains what actually happens from the time you hit ‘send’ to when someone gets your message. We also talk about the role of domain names in email and why domain reputation matters.

Also: Verisign asks ICANN to hike .com prices, Endurance earnings, LongIsland.com, FURY and Google Domains.

This week’s sponsor: Name.com.

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

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

Related posts:
  1. New Domain Transfer Policy – DNW Podcast #111
  2. Big brands and domains – DNW Podcast #140
  3. Country Code Domains – DNW Podcast #208
Categories: Domains

Owner of Zon.Tools sues to get ZonTools.com domain name

Domain Name Wire - Mon, 02/11/2019 - 15:03

Plaintiff claims owner of matching .com is cybersquatting.

The owner of the domain name Zon.Tools filed a lawsuit (pdf) in an effort to get the domain name ZonTools.com.

Zon Tools, Inc offers tools at Zon.Tools to help Amazon sellers with sponsored products bidding. It registered Zon.Tools in July 2017.

The owner of ZonTools.com uses its domain name to offer similar tools as well as other Amazon seller tools such as review management. It registered the domain name in July 2018.

You might ask yourself why Zon Tools didn’t register ZonTools.com when it registered Zon.Tools. The answer is simple: ZonTools.com was registered in back in 2013 but expired in 2018. It went through the entire deletion cycle and then the defendant domain name was registered.

This shows one of the risks of registering a new TLD when you don’t own the “matching” .com. Of course, this can work both ways. If ZonTools.com was the first registered domain, someone could use Zon.Tools in a way that confuses users.

Karl S. Kronenberger is representing Zon Tools, Inc. in the in rem lawsuit. I’m a bit surprised that the lawsuit was filed in California rather than Virginia where .com registry Verisign is headquartered, but the lawsuit notes that Verisign has an office in the jurisdiction where the case was filed.

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

Related posts:
  1. Monte Cahn settles lawsuit against Oversee.net
  2. $50,000 penalty for filing a frivolous UDRP!
  3. AddictingGames.com sues Addicting.com, claiming cybersquatting
Categories: Domains

Speaker hit for reverse domain name hijacking

Domain Name Wire - Fri, 02/08/2019 - 17:42

A keynote speaker and business coach filed a UDRP after failing to buy a domain name. It appears he got bad advice.

Darryl Davis Seminars, Inc has been found to have engaged in reverse domain name hijacking over the domain name PowerAgent.con. A domain investor owns the domain name.

A World Intellectual Property panel determined that Darryl Davis Seminars, Inc did not show that the domain was registered in bad faith. The three-member panel decided that it was a “Plan B” reverse domain name hijacking case in which Davis filed a cybersquatting complaint under UDRP after failing to buy the domain name for a price he wanted to pay.

A couple of years ago he inquired about buying the domain name and received a quote of around $70,000. He responded to it by saying he had been “advised by his attorneys that he had a viable claim to recover the domain name via the UDRP” and offered $375.

The domain owner responded to that letter explaining why the case would fail under UDRP and would be considered reverse domain name hijacking. The Respondent heard nothing more until the UDRP filing, according to the decision.

After the Complainant filed the UDRP, the Respondent tried to contact the Complainant again to remind him “on the off chance that the Complainant had not disclosed to its counsel the existence of the Respondent’s previous warning letter and that as a result, the Complaint was brought in error as a misadventure. The Respondent called and sent an email to the Complainant’s counsel and offered the Complainant a final opportunity to withdraw the Complaint with prejudice but received no reply.”

The panel listed four reasons for finding reverse domai nname hijacking:

i) the Complainant, which is represented by counsel, should have appreciated the weakness of its case and the fact that the term “power agent” encompassed in the disputed domain name cannot be exclusively referable to the Complainant, as claimed in the Complaint without any supporting evidence;

ii) the Complainant’s case is based on the argument that using a common/descriptive domain name in connection with a pay-per-click website and offering it for sale to the highest bidder, independently of any awareness of the Complainant, is of itself evidence of bad faith. The Panel finds that the Complainant should have contemplated that it could not succeed with such an argument;

iii) the Respondent’s response to the letter received by the Complainant before the filing of the Complaint highlighted the weakness of the Complainant’s case, but the Complainant omitted to address the issues raised by the Respondent and even to disclose the existence of such correspondence; and

iv) the circumstances of the case clearly show that this is a speculative “plan B case” launched by the Complainant after its failure to purchase the domain name from the Respondent.

Carter, DeLuca, Farrell & Schmidt, LLP represented the Complainant. Muscovitch Law represented the domain owner. The WIPO panel included Luca Barbero, Martin Schwimmer and Adam Taylor.

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

Related posts:
  1. VirtualExpo.com Virtually Reverse Hijacked
  2. Brazilian company guilty of reverse domain name hijacking
  3. MomAndMe.com spared in UDRP. Should have been RDNH?
Categories: Domains

Verisign begins price increase talks with ICANN

Domain Name Wire - Fri, 02/08/2019 - 13:42

Verisign is negotiating with ICANN to bake price increases into current .com registry agreement.

.Com registry Verisign (NASDAQ: VRSN) has begun negotiations with ICANN to add price increases to its current contract to run .com domain names.

Verisign CEO James Bidzos discussed the updated Cooperative Agreement with the U.S. Government and how it applies to its contract to operate .com on the company’s earnings conference call yesterday.

The agreement allows for price increases of 7% per year in the last four years of each six-year contract extension. Also, the Cooperative Agreement does not require Verisign to get approval for future price increases as long as they are limited to the 7% per year/last four years agreed to in the current Cooperative Agreement, he said. The agreement can only be modified by mutual consent of both the U.S. government and Verisign, which suggests that future administrations would not be able to curtail price increases through the Cooperative Agreement.

Of course, the actual contract to run .com is with ICANN. Bidzos said that ICANN historically deferred to the U.S. government on .com pricing. (In the 2012 renewal ICANN originally agreed to 7% increases but pulled that back when the U.S. government essentially vetoed it. The dynamic has definitely changed now, though, so it will be interesting to see how ICANN responds to the new Cooperative Agreement.)

Regarding working with ICANN to incorporate price increases into the current agreement that runs through 2024, Bidzos says Verisign has started negotiations with ICANN:

There’s a process for moving changes from the DOC to the Cooperative Agreement into the .com Registry Agreement. ICANN has historically as I mentioned deferred to the U.S. government on matters relating to com pricing.

But ICANN and VeriSign have an agreement to cooperate and negotiate — there’s a written agreement to operate — cooperate and negotiate in good faith to amend the com registry as may be necessary for consistency with changes to the Cooperative Agreement.

So we have begun that process with ICANN to amend the agreement to make these changes including pricing. And I don’t think I can comment further to process. We’ve been through it a few times. It may take a number of months to work through it, but we’ll update you as appropriate.

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

Related posts:
  1. O.com might be coming, along with other single letter .com domain names
  2. Verisign made domain aftermarket arguments in July
  3. Donuts files opening brief in .Web appeal
Categories: Domains

Verisign reports 2018 results

Domain Name Wire - Thu, 02/07/2019 - 21:31

9.5 million .com/.net registrations in Q4, operating margin continues to grow.

.Com registry Verisign (NASDAQ: VRSN) reported Q4 and full-year 2018 results this afternoon.

For the year, GAAP net income increased from $457 million in 2017 to $582 million in 2018. Non-GAAP income increased from $492 million to $620 million. These numbers include a one-time boost of $52.0 million (GAAP) and $42.8 million (Non-GAAP) from selling its security business to Neustar.

Verisign processed 9.5 million new .com and .net domain name registrations during Q4 2018. That increased the base of .com and .net domains by 1.29 million to 153.0 million.

The company’s already healthy operating margins got even better. GAAP operating margin for the year increased from 60.7% to 63.2%. Non-GAAP operating margin increased from 65.3% to 67.5%.

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

Related posts:
  1. Verisign credits Super Bowl for strong quarter
  2. Verisign files patent app for Thick Whois with privacy compliance
  3. .Com/.Net base grew by 1.47 million in Q3
Categories: Domains

End user domain name sales topped by a .DE

Domain Name Wire - Thu, 02/07/2019 - 17:19

A martial arts site, an IT service provider and medical device company bought domains this week.

At €12,500, a .de domain tops this week’s end user sales list – FullService.de was purchased by a German IT service provider. There were several domain purchases this week by German and other European-based companies.

Here are the end user domain sales. You can view previous lists like this here.

FullService.de €12,500 – Forwards to ITService.de, a German IT service provider for medium to large-sized companies.

Piggy.eu €8,500 – This catchy moniker is being used for a savings and discount program out of the Netherlands.

SmartPortal.com $6,250 – A Swedish technology company called Smart bought this domain with the claim of providing innovative digital solutions to “increase your company’s revenue, reduce spending and simply create a better customer experience”.

BetterBusiness.com $5,500 – This domain is not resolving yet…did the Better Business Bureau buy it?

CleverHealth.com $4,500 – Durable Medical Equipment (DME) ordering and management company Clever Health.

Parametrik.com $3,000- Forwards to Parametrik.net, an outsourced reprocessing service provider for cleaning and sterilization of flexible endoscopes and lumened instruments.

MartialArtsLife.com $2,888 – Forwards to KarateLife.com, a martial arts apparel online shop in development.

NKitchen.com €2,500 – Forwards to Nobilia.de, a German brand of high-quality kitchen construction materials for new construction, remodels and renovations.

Home-E.com $2,100 – This currently forwards to HomeEOnDemand.com for HOMEE, an online network provider of pre-screened, background-checked home improvement service providers.

Firmenauktion.ch €2,000 – This German company now owns the Swiss ccTLD for their consultancy business that supports entrepreneurs in starting their own businesses or assisting in buying or selling companies.

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

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

Web host uptime in 2018

Domain Name Wire - Thu, 02/07/2019 - 16:19

32 shared hosting platforms ranked by uptime.

A new study compares uptime at shared web hosts.

Web hosting uptime is an interesting thing. You don’t think about your host when things are working properly. You curse their name when your site is down.

HostingStats.com created test sites on 32 shared hosting platforms last year to see which ones had the best uptime. It measured outage minutes, longest outages and average site speed.

I’m a bit surprised by the results. Many of Endurance International’s platforms (including BlueHost and HostGator) performed very well. MidPhase was the winner with the least downtime. Four hosts had total downtime of more than 1,000 minutes during the year (ouch).

I use a few different web hosts for my sites, and downtime seems like less of an issue now than it did years ago.

Check out the uptime results for all 32 hosts tested.

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

No related posts.

Categories: Domains

Endurance International Group reports declining numbers as it simplifies

Domain Name Wire - Thu, 02/07/2019 - 14:44

Roll-up’s numbers slip as it simplifies its business.

Endurance’s subscriber base continues to drop.

Endurance International Group (NASDAQ: EIGI) reported fourth quarter and full year 2018 earnings this morning.

Revenue, adjusted EBITDA and subscriber numbers were all down quarter-over-quarter and year-over-year.

2018 revenue was $1,145.3 million, compared to $1,176.9 million in 2017. Q4 revenue dropped from $294.2 million a year ago to $282.4 million in Q4 2018. Adjusted EBITDA dropped from $350.8 million in 2017 to $338.1 million in 2018. Q4 adjusted EBITDA dropped from $94.4 million in 2017 to $79.3 million in 2018. The subscriber base dropped from 5.051 million to 4.802 million at the end of 2018.

The drop was expected. Revenue was in line with the company’s expectations for the year and adjusted EBITDA topped forecasts. It’s all part of the company’s reckoning of a roll-up that became unwieldy.

Endurance rolled up much of the shared hosting market, acquired domain name companies and bought email marketing platform Constant Contact. It was a lot to chew on. Now the company is focusing on core brands and simplifying the business.

On the domain name side, the company is focusing on the Domain.com brand as well as BuyDomains and ResellerClub (which came with the Directi acquisition). Endurance is the third largest domain name registrar in terms of .com domains under management.

Domain revenue and customers fell slightly in 2018 although adjusted EBITDA flipped from negative to positive.

Its web presence business includes BlueHost and HostGator. Numbers were down across the board in 2018 in its hosting business although average revenue per subscriber ticked up slightly.

E-mail marketing–primarily ConstantContact–increased its revenue despite losing subscribers.

The company is hoping for a turnaround in revenue in 2019. It is guiding to $1.14 billion to $1.160 billion. However, it expects adjusted EBITDA to fall to $310 million to $330 million.

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

Related posts:
  1. Domain names are one bright spot for Endurance
  2. Canadian firm Obero tries to Reverse Domain Name Hijack domain name
  3. Innovation HQ asks USPTO to cancel “Weeds” trademarks
Categories: Domains

Andrew Hazen acquires LongIsland.com website

Domain Name Wire - Wed, 02/06/2019 - 18:37

Hazen acquires a website he’s wanted for a long time.

Andrew Hazen acquired LongIsland.com.

Domain investor, website developer, and bobblehead seller Andrew Hazen has purchased the website LongIsland.com.

According to a story on LongIsland.com, Hazen tried the buy the website (a directory at the time) in an auction a decade ago. His $250,000 bid wasn’t enough; the site sold for $370,000.

The buyer continued to build out the site and grow its traffic. Hazen met with the owner recently and mentioned he was still interested in owning the site. That turned into a deal that closed last month.

Hazen’s other businesses include running co-working locations LaunchPad Long Island and bobblehead business BobbleBoss.com.

I have reached out to Hazen for more details.

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

No related posts.

Categories: Domains

Canada’s .CA domain registry now operating on Fury Platform

Domain Name Wire - Wed, 02/06/2019 - 15:06

.CA country code domain name transitioned to Fury platform.

Canadian Internet Registration Authority (CIRA) is now eating its own dog food: The registry for .CA domain names has transitioned backend services to its in-house Fury Registry Platform.

CIRA started offering the platform to other registries starting in 2016, picking up both .kiwi and .sx as clients.

Transitioning .CA to the platform took some time because there are 2.8 million .CA domains registered and 140 registrars sell them.

Fury uses a patent-pending tag system to assigning rules to domains.

During a session on .com pricing during NamesCon last week, CIRA President and CEO Byron Holland said that the company can offer registry services for between $1-$4 per domain.

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

Related posts:
  1. CIRA wants patent for registry “tag” system
  2. Canada Leading the Way with Whois Changes
  3. Muscovitch: Canadian ccTLD Registry Rules in Need of an Overhaul
Categories: Domains

Domain Name Rewind: domains in January

Domain Name Wire - Wed, 02/06/2019 - 14:54

CNBC’s The Profit, Prince settlement and great domain investor data were top stories last month.

The top story on DNW last month was a domain name lesson on The Profit.

Here are the top five stories on Domain Name Wire in January, as well as the DNW Podcasts for the month. The stories are ranked by views.

1. A domain name lesson on CNBC’s The Profit – Marcus Lemonis helped a toy shop upgrade from .net to .com as part of his investment.

2. Great domain investing data from Paul Nicks (GoDaddy) at NamesCon – Paul Nicks digs into domain investment approaches and returns.

3. Prince’s estate settles Prince.com fight with Domain Capital – It looks like Prince’s estate will get Prince.com in return for cash.

4. “Domain Name” is a pay-to-play search term on Google – There are no organic results (other than Wikipedia) above the fold.

5. How a Whois check could have halted a scam – a Wendi Deng Murdoch imposter tricked some photographers and a clue was in Whois.

Podcasts:

#221 – Google’s Ben McIlwain

#220 – Domain auction preview with Monte Cahn

#219 – WordPress Plugins + 2 more predictions

#218 – 2019 Predictions

You can listen to the podcasts by visiting the pages or downloading them on your phone’s podcast app.

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

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

No reverse domain name hijacking in VDG.com case

Domain Name Wire - Tue, 02/05/2019 - 17:26

Complainant loses cybersquatting dispute but panel doesn’t find RDNH.

Van der Graaf Inc. lost a UDRP cybersquatting dispute over the domain name VDG.com, but the panel stopped short of finding the company guilty of reverse domain name hijacking.

A three-person World Intellectual Property Organization panel determined that Van der Graaf did not show that the domain was registered and used in bad faith. When it filed the case it believed the domain name transferred owners after the company started using its trade name in 2018. The respondent proved that he registered it in 2017.

Even if he had registered it afterward, the panel would have considered the value of the domain name as a three letter domain. Van der Graaf tried to argue that VDG was unique to its company:

Moreover, the Respondent would have been aware that VDG is neither a descriptive term, nor a common three-letter acronym used by many third parties for a variety of services, but the specific trademark in which the Complainant had established rights. A simple search of the Canadian trademarks database reveals that the Complainant is the only applicant for the VDG trademark. Similarly, a search of the European Union trademark database reveals that the Complainant is one of only two registrants of the VDG trademark for unrelated goods and services, while a search of the United States trademark database reveals that besides the Complainant there are only two registered owners of the VDG trademark for unrelated goods and services. According to the Complainant, these circumstances show that the Registrant had targeted the VDG trademark of the Complainant.

This argument undermines the idea that it is the sole owner of VDG. The are other companies using VDG. When I search on Google in the U.S., the first page of results relate to two other firms that use the acronym VDG.

Ultimately, the panel cited the change in Whois record and the Complainant’s belief that the domain had changed hands after it starting using its name as a reason for not finding reverse domain name hijacking.

Piasetzki Nenniger Kvas LLP represented the Complainant. Wiley Rein LLP represented the domain name owner.

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

Related posts:
  1. Incumbents Opposed to UDRP Reform
  2. Domain name owner loses UDRP, sues, gets $7,500
  3. Registering a trademark doesn’t let you refile a UDRP
Categories: Domains

Q&A with NameSilo CEO Kristaps Ronka

Domain Name Wire - Tue, 02/05/2019 - 16:18

NameSilo CEO explains the background of the fast-growing registrar.

NameSilo seems to have come out of nowhere.

The domain name registrar doubled its domains under management in just one year. It is usually among the top ten registrars each month in terms of new .com registrations.

So where did the registrar come from and how has it grown so quickly? I asked CEO Kristaps Ronka some questions to find out the story.

DNW: What’s the history of NameSilo? Who created it and when?

NameSilo was created by a trio of entrepreneurs in Phoenix Arizona who started the business in 2010. Through their hard work and dedication, they built the platform on their own from scratch and got accredited with ICANN. Having set the foundation and having looked at the domain name registrar landscape, they saw their opportunity in building a business focused on providing the lowest-cost domains, so as to deliver the maximum value possible for customers. Over the next couple of years, the platform grew, both in domain count and functionality. Not only did the team build out value-added services such as domain parking, e-mail forwarding as well as account security features like domain defender and 2-factor authentication, but also started to expand beyond solely domain name registration by building out a low-cost Marketplace to allow customers to buy and sell NameSilo domains.

It took some time for the business to hit its stride and for word of mouth to spread across the industry but by August of 2017, NameSilo joined the top 1% of ICANN accredited domain registrars with over 1 million active domains under management. And since then, the growth has only amplified – today, NameSilo is now one of the fastest growing domain name registrars in the world with over 2.5M active domains under management.

DNW: What is Brisio Innovations and when did it come into the picture?

Brisio Innovations (now NameSilo Technologies) is an investment issuer and a Canadian public company (CSE:URL). We purchased NameSilo through Brisio. NameSilo was the first deal of its kind for Brisio where, instead of investing in the company, we fully acquired the entity. The business opportunity and potential synergy became apparent between the team members and the deal was structured to provide ample resources, both financial and human capital, for NameSilo to continue the current growth trajectory. The acquisition was completed in August 2018 and the team has been rolling since.

DNW: Who is NameSilo’s target customer?

NameSilo’s target customer is anyone seeking low-cost domain name registration services without compromising on quality or support. Generally, the user will be savvy about domain names and prefers the DIY approach. They would have an extensive domain name portfolio, making the cost savings gained through us that much more substantial. An exemplification of this target customer would be someone or a Small/Medium Business providing hosting services – they use us for their domain name registrations and focus their time on actually building the hosting service and customer base.

DNW: The domain registrar business is cutthroat. What differentiates NameSilo?

We have built our business on providing the lowest everyday pricing while not compromising on the quality of our platform, features or support. This customer-first approach has enabled us to achieve the success we’ve managed thus far, so we don’t want to sway too far from it. We have had exceptional growth through word of mouth. We continue to strive for improvements in all our products and services on a daily basis. Our feeling is that as long as we’re delivering on these fundamental offerings, success and growth will follow.

DNW: Are you part of Sedo MLS or Afternic DLS?

Yes, we are a part of SEDO MLS & Afternic DLS to provide additional avenues for our customers to buy and sell domain names.

DNW: Are the original founders still with the company? Who leads it now?

The founders are now in an advisory role.

My background is the following: I co-founded a company called AdParlor in 2008. We were a social media advertising company offering a third cost model – cost per acquisition on Facebook. We sold in 2011 to a company called AdKnowledge out of Kansas City. I am an entrepreneur, developer, advisor.

Our CMO, Endrit Muca, joined NameSilo from AdParlor shortly after we took over the business. Our new COO is Arthur Poghosian and our new CTO is Eugene Melnichenko. Both have joined us from NamePal.

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

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

XYZ files three trademark applications

Domain Name Wire - Tue, 02/05/2019 - 15:11

New TLD company files for three trademarks on existing TLDs; readies two more namespaces.

XYZ.com is launching .Monster in sunrise this month.

New top level domain name company XYZ.com LLC filed three trademark applications last week that match the slogans it uses to market three top level domain names.

The applications are for:

  • Express your passion  (.theatre)
  • Advancing online security  (.security)
  • Claim your space  (.storage)

XYZ.com has 10 registered trademarks.

The company is getting ready to launch/relaunch two top level domain names this year: .Monster and .Baby. It acquired .Monster from jobs company Monster Worldwide and will launch it in sunrise this month. It acquired .baby from Johnson & Johnson.

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

Related posts:
  1. XYZ.com wins .college top level domain auction
  2. One year in: .XYZ and new top level domain names
  3. Smart and timely marketing from .XYZ
Categories: Domains

How I almost lost a domain name this week

Domain Name Wire - Mon, 02/04/2019 - 20:14

Follow these two tips to avoid having the same thing happen to you.

I almost lost a good domain name due to expiration this week. I learned some lessons, so I’m recounting what happened to make sure this doesn’t happen to you.

I won the domain name in a NameJet auction nearly a year ago and the domain was at Register.com. It’s a fairly good domain name; I had two different inquiries on the domain last year including one from a large company.

Yesterday I received a DomainTools registrant alert that showed that the domain changed from my company name to Perfect Privacy, LLC. That’s the proxy service for Web.com registrars Register.com and Network Solutions.

Concerned, I went to my Register.com account and saw that the domain expired three days ago.

I do not recall receiving any of the ICANN-mandated notices from Register.com about my domain expiring. This doesn’t mean they didn’t send them. Most email from Register.com lands in my spam box because they send so much promotional email–one per day!

These promotional emails often start with “Urgent” or “Alert” even when it’s not important. It’s just a sales pitch for search engine optimization. So it’s easy to overlook them.

Regardless of whether they sent the notices or not, here are two tips to make sure this doesn’t happen to you.

1. Use an alert service like DomainTools or DomainIQ to get notifications when your Whois changes. Unfortunately, GDPR means your info isn’t always in Whois, but you can also track domain status changes that will alert you that your domain has expired.

2. Transfer domains you win in expired domain auctions to your main registrar on a regular schedule. For example, set up a once-a-quarter reminder on your calendar to transfer domains.

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

No related posts.

Categories: Domains

NamesCon Recap Podcast – DNW Podcast #222

Domain Name Wire - Mon, 02/04/2019 - 16:30

Hear from 16 people who were at NamesCon Global.

NamesCon Global 2019 is in the books, and this week we’ll catch up with 16 people who attended NamesCon. After discussing some of the week’s news you’ll hear from:

Matt Barie, Freelancer.com
Marcus Glaad, DotKeeper
Margot Bushnaq, BrandBucket
Darpan Munjal, SquadHelp
Page Howe, domain investor
Deanna Camacho, GoDaddy
Stevan Lieberman, Escrow.Domains
Peter Askew (whose latest venture is BirthdayParties.com)
Ray King, Top Level Design
Kate Buckley, Buckley Media
Andrew Rosener, Media Options
Ryan McKegney, DomainAgents
Jeff Sass, Names.club
Burkay Yapağcıoğlu, Hosting Talk
Christa Taylor, MMX
Jim Schrand, Dominion Domains

Enjoy the show!

This week’s sponsor: DNAcademy. Use code DNW to save $50.

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

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

Related posts:
  1. NamesCon recap with 15 interviews – DNW Podcast #172
  2. Checking in with Escrow.com – DNW Podcast #195
  3. Crowdsourcing (domain) name selection – DNW Podcast #199
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.