skip to content

News

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

Redl discusses Whois availability at ICANN 61

Domain Name Wire - Mon, 03/12/2018 - 17:07

Head of NTIA reiterates United States’ position on Whois data.

At ICANN 61 in Puerto Rico today, NTIA chief David Redl again called for restraint in changes made to Whois.

Redl and the U.S. government are concerned about the effect that limiting public Whois information will have for law enforcement, intellectual property and security interests.

Here are his comments:

As we look ahead, one of the top priorities for the United States in ICANN is the preservation of the WHOIS service.

As you know, the WHOIS service is an incredibly valuable tool for governments, businesses, intellectual property rights holders, and individual Internet users around the world.

I am pleased to see that ICANN and the community have committed to find a solution that maintains the WHOIS service to the greatest extent possible in the face of data protection and privacy regulations such as the European General Data Protection Regulation.

The United States and other governments in the GAC have stated their commitment to maintaining a WHOIS service that is quickly accessible for legitimate purposes.

With respect to the recently published interim model, we are pleased that ICANN was able to pull from so many different interests and needs expressed by the community. That being said, the United States would encourage revisions to the model that would permits access to the most amount of registration data as possible. We think there is more that can be done to achieve this.

Additionally, the United States remains concerned with how access to WHOIS information for legitimate purposes will be maintained in the period between the date of GDPR enforcement, May 25, and the time in which the community is able to develop and agree to a formal accreditation processes. Plans need to be put in place to ensure that the users behind the already defined legitimate purposes – such as law enforcement, intellectual property enforcement, and cybersecurity – are not stymied in their efforts to serve the public interest.

The United States will not accept a situation in which WHOIS information is not available or is so difficult to gain access to that it becomes useless for the legitimate purposes that are critical to the ongoing stability and security of the Internet. We look forward to working with ICANN and the community to see this through.

One key thing to note is that, by design, the U.S. government is just one voice in this discussion. This design prevents one government from exerting too much control, like the fears Ted Cruz has about China and Russia.

Of course, the U.S. government could pass a law requiring registrars to make information public and put it at odds with the European Union’s GDPR, which is the cause for the Whois overhaul.

A big issue that is coming up is how to determine what legitimate interests are within law enforcement, IP and security groups. There are tens of thousands (if not more) security researchers and companies in existence and millions of intellectual property holders. What qualifies them to get access to Whois data?


© DomainNameWire.com 2017. 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.

© 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. 15%-25% of Domain Names are Registered with Masked Whois
  2. If ICANN and WIPO can’t comply with WHOIS, who can?
  3. Will WHOIS be assassinated?
Categories: Domains

The value of a category killer domain – DNW Podcast #176

Domain Name Wire - Mon, 03/12/2018 - 15:30

After a major business setback, Michael Gargiulo spent close to $1 million to acquire VPN.com.

Imagine creating a website that is generating $1,500-$2,000 a day and then getting hit with a lawsuit claiming trademark infringement and cybersquatting. That’s what happened to Michael Gargiulo. Making things more complicated, he was leasing the domain name from someone else. Despite settling the lawsuit and abandoning the business, Michael looked forward instead of backward. He negotiated to buy VPN.com for close to 7 figures. Hear Michael’s story about buying the domain name and why he thinks this category killer domain name is worth it.

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


© DomainNameWire.com 2017. 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.

© 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 End User Domain Buyers Think – DNW Podcast #134
  2. Paul Nicks of GoDaddy – DNW Podcast #160
  3. Building web businesses with Peter Askew – DNW Podcast #163
Categories: Domains

Insurance company Allianz tries reverse domain name hijacking a domain name

Domain Name Wire - Fri, 03/09/2018 - 18:22

World Intellectual Property Organization panelists have harsh words for insurance giant.

Insurance giant Allianz has been found guilty of reverse domain name hijacking in its attempt to get the domain name AGCS.com.

The company formed a business called Allianz Global Corporate & Specialty in 2006 and, at some point, started referring to this group at AGCS. It subsequently used agcs.allianz.com for the business and registered myagcs.com in 2013.

The domain owner acquired the domain name in 2010 due to its value as a four letter domain.

The panel determined that Allianz’s evidence did not show any use of the acronym prior to 2017. Apparently, much of its evidence supported how Allianz (not AGCS) is a well-known brand.

In finding RDNH, the majority of the panel wrote:

…Complainant made numerous allegations concerning its rights in AGCS, and how well-known AGCS has become as referring to Allianz Global Corporate & Specialty SE, that Complainant completely failed to support with any evidence…

…Complainant made no attempt to prove any rights in AGCS prior to May 2010 and only provided evidence of its use of AGCS in late 2017

…Simply put, the facts in this proceeding demonstrate that Complainant clearly ought to have known it could not succeed under any fair interpretation of the facts reasonably available prior to the filing of the Complaint and that basing its Complaint on the barest of allegations without any supporting evidence – such as claiming bad faith registration of the disputed domain name by Respondent with no proof of Complainant’s rights in the AGCS mark prior to May 2010 (and only showing use of AGCS by Complainant seven years after Respondent registered the disputed domain name) – was doomed to fail…


© DomainNameWire.com 2017. 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.

© 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. ECommerce company Eyemagine found guilty of reverse domain name hijacking
  2. Reverse domain name hijacking in HUG.com case
  3. Lack of disclosure leads to Reverse Domain Name Hijacking finding
Categories: Domains

Happy Birthday: Domain Name Wire Turns 13

Domain Name Wire - Fri, 03/09/2018 - 16:05

It’s time to turn rebellious because Domain Name Wire has become a teenager. This site turns 13-years-old today.

Both the domain name business and online publishing world have changed a lot over the past 13 years. I’d like to thank both my readers and sponsors for continuing to make this publication possible through all of the industry’s ups and downs.

I strive to present the latest domain name industry and web presence news in a clear, concise and accurate way. Deciding what to cover is almost as important to me as how I cover it.

Many of my advertisers have been supporting this site for ten years or more. That’s a serious commitment. I’d like to give a special shout-out to my two longest running advertisers, Sedo and DomainCapital. If you’d like to support this site as a sponsor, please contact me at andrew (at) domainnamewire.com for a media kit.

As for the readers…I love every one of you. Even when we duke it out in the comments section. Remember, I’m a moody teenager now…


© DomainNameWire.com 2017. 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.

© 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. Google is now part of Alphabet, uses ABC.xyz
  2. How to invest in domain names through an IRA or 401(k)
  3. .Boston domain names enter general availability today
Categories: Domains

Investment firm to acquire domain name registrar NameSilo

Domain Name Wire - Fri, 03/09/2018 - 15:07

Registrar will likely end up as publicly traded firm after the acquisition.

NameSilo has been acquired for $9.5 million plus earnouts.

A Canadian investment firm has entered into an agreement to acquire domain name registrar NameSilo for $9.5 million plus undisclosed earnouts.

The acquirer, Brisio Innovations, is a publicly traded penny stock on the alternative Canadian Securities Exchange. It plans to spin NameSilo out as its own publicly traded company on a Canadian stock exchange after the transaction closes.

NameSilo had USD $11.1 million in annual recurring billings in 2017, up from $6.9 million in 2016. It has grown its domain names under management from approximately 745,000 domains at the beginning of 2017 to over 1.35 million today. The company boasts a customer retention rate of approximately 87%.

According to the most recent public Verisign filing with ICANN (dating to November), NameSilo had about 850,000 .com domains registered. It had close to 50,000 new .com registrations that month.

Unlike other recent acquisitions of domain name registrars, this one does not represent industry consolidation.


© DomainNameWire.com 2017. 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.

© 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. Afilias acquires 101Domain
  2. Here’s what’s happening at Rightside
  3. GoDaddy made the right move by booting domain name used for white supremacist site
Categories: Domains

10 notable NameJet sales from February 2018

Domain Name Wire - Thu, 03/08/2018 - 17:32

Here are ten sales from last month that caught my attention.

NameJet’s February sales include the NamesCon auction results, so the company posted nearly $3 million in sales of domain names over $2,000 for the month. Yes, that means Super.com ($1.2 million) and Great.com ($900,000) closed!

Ignoring NamesCon, NameJet posted 59 sales of $2,000 or more for a total of just over $300,000. Here are some non-NamesCon sales that stood out to me:

PrizeFight.com $9,000 – Yikes! This domain sold for $105,556 on Afternic back in 2006. The sale is in line with more recent comps: PrizeFights.com for $12,000 in 2015 and PrizeFighters.com for $20,000 in 2010.

FishingLure.com $7,600 – Comps can be tricky!

NewJerseyHomes.com $7,500 – The same domain sold for $8,600 on NameJet about a year ago. Most of the top sales of domains ending in ‘homes’ are for city names. FortWorthHomes.com for $34,100 in 2015, AustinHomes.com for $40,000 in 2012.

SuddenlySenior.com $5,350 – You’d think aging was a more gradual process. But as I get older I ask “where did the years go?”

Duffer.com $5,001 – I imagine the buyer is thinking of this as a surname rather than the dictionary definition.

Bismark.com $4,199 – Bought as a typo? Google will only show results for BismarCk unless you tell it you’re sure you want to exclude the C.

GCapital.com $4,188 – The buyer needs to be really careful about what PPC ads they show for this domain.

Infusing.com $2,500 – Infusion would be better, but there’s a good buyer base for this domain.

AirplanesForSale.com $2,355 – I can see some domainers arguing this is worth a lot more because “if you sell just one airplane, you’ve more than paid for the domain!” Yeah, but…

Sacrifice.org $2,299 – This domain could have a religious connotation so .org make sense.

 


© DomainNameWire.com 2017. 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.

© 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 to buy this week
  2. NameJet sellers at center of shill bidding questions
  3. Here’s what NameJet is doing about shill bidding
Categories: Domains

25 end user domain name sales including three big non-.Com domains

Domain Name Wire - Thu, 03/08/2018 - 14:48

A big week for end user domain name sales including non-.com domains.

This week’s end user domain name sales list is notable not only because of its size but also because the first three domain names aren’t .com. There’s a .org sale I previously wrote about, a .co and a .ventures. Two of the three are related to blockchain. Heck, maybe the third is, too.

As I created this list I realized how hard it will be to deliver this information in the future if registrars obscure registrant info. Journalists seem to be left out of discussions about legitimate access to Whois info.

Here are the end user sales I found in Sedo’s sales list:

(You can view previous lists like this here.)

Star.org $225,000 – More on this sale here. It’s a blockchain company.

Nurture.co $45,000 – The domain is still in escrow but this is an end-user price.

Blockchain.ventures $42,000 – Blockchain ventures has created a couple blockchain-based businesses and isn’t afraid of new TLDs. Two of its businesses include coin.dance and blockchain.poker.

New50.com $23,205 – Interesting sale by Frank Schilling. The buyer is the maker of Cologuard, a non-invasive substitute to colonoscopies. You can bet this will be some sort of marketing domain since 50 is when people are supposed to get colonoscopies to check for colon cancer.

CoinLink.com $22,000 – This appears to be an end user sale as the buyer put “coinlink” as the registrant organization. The seller is the owner of CoinWeek.com, a cryptocurrency coin news site.

Avicenna €20,000 – The domain has privacy and isn’t resolving yet. There are a number of trademarks on this term. The price suggests it’s an end user.

NinjaMarketing.com $12,500 – Ninja Marketing Srl bought the .com to go with its NinjaMarketing.it (Italy) website.

VEDP.com $12,000 – Virginia Economic Development Partnership*

MemoPad.com €11,000 – MemoPad will be a content publishing tool. The buyer also owns MemoPad.io.*

ProPop.com $8,600 – Diet Direct, Inc. Perhaps for the name of a low-cal popcorn?

CoinCredit.com €6,900 – The domain has Whois privacy but the buyer has switched nameservers to Cloudflare and is working on building a website.

AITrading.com $4,999 – Tradezam bills itself as “Tinder for Creating Trade Robots”.

Microgen.group $4,300 – Microgen is a software company that uses the domain name Microgen.com.

Mzen.com $4,200 – Marketing company Zen Media.

ARM.us $4,000 – Advanced Robotics for Manufacturing Institute (ARM Institute) of the National Robotics Engineering Center.

Assurances.online $3,000 – Humania Assurance in Quebec.

Freedom1.com $2,988 – US 1 Logistics has a subsidiary called Freedom 1 that is “a leading provider of intermodal drayage, long-haul trucking, and freight services.”

Taramar.com $2,888 – Taramar is a beauty products company that uses the matching .is (Iceland) top level domain.

Touch-Table.com $2,500 – Iconic builds an interactive table with a touchscreen. It uses the domain name Touch-Table.co.uk.

Livechat.in $2,300 – LiveChat Software SA

Teppich.tv €2,200 – The buyer is a carpet company that uses the domain messeteppich.at (Austria).

ThisIsAbsurd.com $2,100 – ThisIsAnInteresting domain choice by Manchester Digital Agency.*

GAKorea.com €2,009 – GA Korea Co., which appears to be a resort.

UnbundledLawyer.com $2,000 – Empowered Legal, LLC is a legal lead gen company.

WorldHappiness.com $2,000 – World Happiness Summit, which uses the domain name happinesssummit.world.*

*Sale is from the prior week’s list but wasn’t included because the domain was still in escrow or the nameservers hadn’t been updated.


© DomainNameWire.com 2017. 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.

© 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

Oops: Network Solutions tells customers that their domain is now available

Domain Name Wire - Wed, 03/07/2018 - 16:53

Aftermarket sales email worries customers because of wrong subject line.

Domain name registrar Network Solutions mixed up an aftermarket promotion email blast, accidentally informing its customers that their domain name was available for purchase. It seems that someone used the wrong mail merge token in the subject line of the emails.

The first errant message was delivered on February 27. In my case, the subject line read “astounding.com is now available. Don’t miss this chance!”

I own Astounding.com.

The contents of the email were correct and pitched another domain for sale on the aftermarket:

The same email with the subject line error was sent out yesterday.

Apparently, at least one customer was concerned that they’d lost their domain because Network Solutions sent a follow-up message with the subject line “Our Mistake: astounding.com is safe”.

The message read:

We Hit Send Too Soon

This morning you received an email with a subject line indicating that astounding.com was “available”. This may have caused you concern as this is a domain you currently own. The email’s subject line was a mistake and included your existing domain name instead of an alternate, available name we thought you might be interested in. Please know, your domain is safe and is not available for sale. Network Solutions will never sell or offer your domain name without your prior knowledge or consent. We apologize for any concern this may have caused.

Sincerely,
Network Solutions Customer Support

These aftermarket promotions can be quite effective for selling domains listed on a marketplace’s distributed listing service. So it’s good that Network Solutions markets these…and I imagine they’ll double check these emails before sending them in the future.


© DomainNameWire.com 2017. 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.

© 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. Network Solutions Displays Customers’ Whois Queries to the Public
  2. Web.com to Cut More Network Solutions Employees
  3. Network Solutions files domain privacy patent application
Categories: Domains

Digging into Tucows’ annual report

Domain Name Wire - Wed, 03/07/2018 - 15:35

Some notable items from Tucows’ 10-k.

Tucows (NASDAQ:TCX) filed its annual report yesterday. Here are some things I found interesting:

1. The company now has 558 full-time employees. With $329 million in revenue, that’s about $600k of revenue per employee.

2. Tucows had 22.3M domains under management (DUM) on its own accreditations at the end of 2017 and a further 5.4 million on its platform managed under resellers’ accreditations. That’s a total of 27.7 million DUM.

3. In January, the Company completed a bulk transfer of 2.65 million names to former reseller Namecheap following a court order. As a result of the bulk transfer, the Company will recognize in the first quarter of 2018 $14.6 million of revenue and $14.5 million of cost of goods sold related to previously deferred revenue and deferred prepaid registry fees.

That narrow spread shows how little margin it received on Namecheap domains. However, Tucows did receive expiry and PPC revenue from these domains as well.


© DomainNameWire.com 2017. 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.

© 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. January data show why Rightside sold eNom: Namecheap
  2. Namecheap sues Enom and Tucows, demands transfer of 4 million domains
  3. Court orders Tucows to transfer 3.2 million domains to Namecheap
Categories: Domains

.App domains are coming: Q&A with Google

Domain Name Wire - Wed, 03/07/2018 - 14:39

You’ll soon be able to register whatever.app. Here’s what you need to know.

Google paid $25 million three years ago for rights to run the .App top level domain name and it’s finally ready to offer it to consumers.

While the original application said the domain would only be available to verified app developers, Google has decided to make it open to everyone. I reached out to Google to understand more about the launch.

Right now the domain is in a qualified launch period but, as you’ll see in the questions below, this is an invite-only opportunity. The domain will move to Sunrise on March 29, Early Access on May 1 and general availability on May 8.

DNW: What’s required to get a domain during the qualified launch period?
Google: The qualified launch period is for pioneer registrants who will host .app sites to showcase interesting uses of the .app TLD. Google is reaching out to candidates through various channels, and at the moment we aren’t soliciting direct applications.

DNW: The .app application said it would be limited to app developers. This restriction has been removed, correct?
Google: That is correct. We have decided to no longer have an explicit restriction, but expect that app developers will be amongst the potential registrants that find most value in this new namespace.

DNW: What is the full launch timeline?
Google: See https://registry.google for dates. All phase transitions occur at 16:00 Z.

DNW: How will the early access period work? Will it be a Dutch auction-style or just the same added fee throughout the EAP?
Google: It will be a seven-day Dutch auction style EAP, as many other gTLD registries have adopted. We hope it will allow registrants that are particularly excited about specific names to not miss out on them.

DNW: What price do you expect registrars will offer the domain for? Or, what is your wholesale pricing?
Google: We priced .app with the intention of providing an affordable option to individuals or companies that are interested in the name. While we still don’t have definitive information from registrars, we expect the price to be lower than for our other TLDs, like .how or .soy.

DNW: Will there be premium domains?
Google: Yes, we will offer premium domains with the price applying to both creation and renewal. More details will be available in the weeks leading to launch.

Here’s my take: .app is the most interesting top level domain name to launch in a long time. I think there will be an opportunity for domain investors to play here assuming the premium domain list isn’t exhaustive. Based on pricing for .how and .soy, I expect the wholesale price for .app domains will be around $10-$12, so you can expect to pay around $20 retail for registrations.


© DomainNameWire.com 2017. 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.

© 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. Google open sources domain registry, Donuts collaborates as pressure on registry providers mounts
  2. Donuts chooses Rightside over Google Nomulus
  3. .Boston domain names enter general availability today
Categories: Domains

Redl groups “Right to be Forgotten” with other censorship, calls it “regrettable”

Domain Name Wire - Tue, 03/06/2018 - 17:41

Governments should not try to apply local laws to the borderless internet, Redl says.

David Redl, the head of the U.S. government’s NTIA, has criticized countries that are trying to apply local laws to the control internet. In comments made to the Global Internet and Jurisdiction Conference in Ottawa, Canada last week, Redl said:

In some countries, governments are responding with restrictive and isolationist policies. These include censorship, blocking, demanding a “right to be forgotten,” and requiring localized data storage. These policies seek to maintain the perception that our borderless, open Internet can be managed, bounded, and conformed to fit with local laws.

These actions are understandable, but regrettable. We understand that governments are trying to respond to very real challenges and concerns that their citizens have. They want to both protect and project their sovereignty.

But global companies end up getting caught in the middle of these conflicting policies, and as they work to address competing and inconsistent legal demands, the inevitable result is that users suffer diminished access and benefits from the network.

Many of those global companies are in the United States, e.g. Google.

Redl has previously expressed concerns over plans to hide Whois data in order to comply with the EU’s General Data Protection Regulation, or GDPR.


© DomainNameWire.com 2017. 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.

© 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. Will May 2018 be the death of Whois?
  2. #3 in 2017: GDPR and the death of Whois
  3. U.S. Gov: Whois info must remain available
Categories: Domains

BrandBucket battles cybersquatter

Domain Name Wire - Tue, 03/06/2018 - 17:07

WIPO panel orders two domain names to be transferred to BrandBucket.

Brandable domain name marketplace BrandBucket has won a battle against the cybersquatter who registered the domain names BrandBucket.org and BrandBucket.shop.

The domain name registrant, Ruben Botn-Joergensen, was certainly brazen.

According to the UDRP decision, In June 2016 BrandBucket let its U.S. trademark application lapse. Despite the lapse, it certainly still had common law rights to the mark.

A few months later the respondent registered BrandBucket.org. He reached out to BrandBucket the day after registering the domain to see if they wanted to buy the domain. Over the next couple of weeks, he filed trademark applications in the U.S and Norway for BrandBucket.

Shortly thereafter, BrandBucket became aware of the respondent’s trademark registration and website, which it said was essentially a copy of its websites. It contacted the respondent who took the site down. He wrote:

Regarding your expired trade mark, we have applied for trademark as there is a free and open process, this doesn’t mean we take advantage. Regards to your request, based on a professional respect, we have shut down the website at this stage. Same based on a professional respect, we have offer the domain for you a while ago. One thing we should have clear, as we don’t operate in the same territory or market. However, all things been said, we do respect and appreciate your business, and it may be that we could collaborate with together in the future.

As you can imagine, BrandBucket had not interested in collaborating.


© DomainNameWire.com 2017. 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.

© 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. Twitter finally gets Twiter.com domain it won in dispute
  2. Reverse domain name hijacking in Hakoba Saree case
  3. PCO.com saved in UDRP despite no-show by domain owner
Categories: Domains

Office Depot gets reverse domain hijacking win over Viking.com domain name

Domain Name Wire - Tue, 03/06/2018 - 16:12

Dispute between two parties over Viking.com domain name is clearly outside the confines of UDRP.

A World Intellectual Property Organization panel has determined that Office Depot’s ownership of Viking.com does not constitute cybersquatting. It also found that the complainant Aurelius RHO GTM Development Limited engaged in reverse domain name hijacking by filing a cybersquatting dispute over the domain name.

The complainant acquired Office Depot’s European Viking business at the end of 2016. It claims that the Viking.com domain name should have included in the sale even though it wasn’t listed on the intellectual property list for the transaction. Office Depot claims that the domain wasn’t included as part of the deal.

Backing up Office Depot’s case, Aurelius tried to buy the domain name from Office Depot afterward. It was unsuccessful.

Office Depot says that Aurelius’ UDRP filing was a last ditch effort to try to get the domain and prevent Office Depot from selling it to someone else.

Indeed, the dispute was doomed to fail. It would be impossible to show that Office Depot registered the domain in bad faith since it acquired it for its Viking office products business.

The three-person panel wrote:

Perhaps the most striking deficiency, however, which is sufficient in this Panel’s mind to establish RDNH, is the lack of any allegations in the Complaint as to how the Respondent registered the disputed domain name in bad faith. But looking at the circumstances in their entirety, it is not difficult to understand why there are no such allegations – the facts at hand simply do not provide any basis for them. This disregard of such a striking deficiency in the Complainant’s case is enough to sustain a finding of RDNH, and accordingly, the Panel so finds.


© DomainNameWire.com 2017. 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.

© 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

Michael Ward named EVP Strategic Partnerships for The SSL Store

Domain Name Wire - Tue, 03/06/2018 - 15:42

Ward takes key role with SSL provider.

Michael Ward has joined The SSL Store as EVP of Strategic Partnerships. Ward previously worked with the company in a consulting role.

As its name suggests, The SSL Store specializes in helping companies encrypt with SSL. It’s a timely subject given what browsers such as Chrome are doing for sites that don’t have SSL certificates.

Part of Ward’s role will be working with hosting companies, registrars and resellers to offer SSL certificates to their customers. He’s well positioned for that role given his long career in the hosting and domain space. Over the past two decades, he’s held positions with Verisign, Public Interest Registry, Parked.com, DirectNic and Uniregistry.

He will be at CloudFest in Germany next week.


© DomainNameWire.com 2017. 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.

© 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

February’s Top 5 Domain Name Stories

Domain Name Wire - Mon, 03/05/2018 - 20:51

Here’s a recap of the stories that were most popular on Domain Name Wire last month, as measured by pageviews.

1. WIPO panel screws Domaining.com owner Francois Carrillo out of Ado.com – Thankfully, he’s not done fighting.

2. GoDaddy “for sale” tweak leads to 41% more aftermarket sales revenue – New “For Sale” messages are drastically increasing sales of aftermarket domain names.

3. Google is upping the ante on SSL – The Chrome browser will begin showing “not secure” on non-SSL sites, even those without forms.

4. Back from NamesCon — here’s my take. It was a good conference. If you missed it, here’s a great summary of the keynotes.

5. Analyzing startup domain names – Most of the startups selected for MassChallenge’s inaugural Texas class use .com, but not all of them.

And these were the podcasts from last month:

Protecting Domains with Kathy Kleiman

Christa Taylor talks domains

NamesCon recap with 15 interviews


© DomainNameWire.com 2017. 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.

© 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

Sex cam website owner nailed for reverse domain name hijacking

Domain Name Wire - Mon, 03/05/2018 - 17:20

Company’s claimed dates don’t add up.

A World Intellectual Property Organization panel has found Brentwood Holding Group Inc, the operator of NudeLive(dot)com, guilty of reverse domain name hijacking.

The company filed a cybersquatting complaint under UDRP against the domain name NudeLive(dot)net.

Brentwood claimed trademark rights dating to 1998 and submitted the registration date of its domain name as proof. However, the company’s trademark registration states first use in 2015. This is the same year that Michael Berkens sold the domain name for $6,000 at Uniregistry.

This drew the suspicion of the panelist. It seems that the complainant in this case acquired the domain name after the respondent acquired his domain name in 2012, and tried to use the original registration date of the domain as proof of rights dating to 1998.

In fact, the owner of the .net might have a more legitimate beef in this case. It submitted evidence showing a big drop in traffic when the .com came online. There’s a lesson here: if you own the .net domain, someone could get a lot of your traffic by opening a similar site on the .com.


© DomainNameWire.com 2017. 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.

© 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. Dubai Law Firm Nailed for Reverse Domain Name Hijacking
  3. Telepathy scores $40,000 from reverse domain name hijacking case
Categories: Domains

Big companies and domain names with Elisa Cooper – DNW Podcast #175

Domain Name Wire - Mon, 03/05/2018 - 16:30

Elisa Cooper discusses what’s important to big companies when it comes to domain names.

Remember when The New York Times’ domain name server settings were hijacked to point the site somewhere else? It could have easily prevented this from happening by using Registry Lock. On today’s show, Elisa Cooper of Brandsight talks about domain protection. We discuss corporate domain name management and how big companies have needs that are different from domain investors and small businesses. Also: A Star.org is born, GoDaddy bump, Qurate and more.

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


© DomainNameWire.com 2017. 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.

© 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

Name.com expired domains are now on GoDaddy

Domain Name Wire - Mon, 03/05/2018 - 14:24

Expired domain deal came with portfolio acquisition last year.

In October 2017, Donuts sold about 200,000 domain names to GoDaddy. These domains were in a portfolio that Donuts inherited when it acquired Rightside.

GoDaddy was after more than just the domains. It also wanted access to Name.com’s expired domain name portfolio.

Those expired domains were flowing through NameJet. That made sense because Rightside, which owned Name.com, was a 50/50 owner in NameJet. But Rightside sold that interest to Tucows as part of the sale of Enom.

GoDaddy got the expired domain deal along with the portfolio acquisition. A Domain Name Wire reader noticed that the Name.com domains have now started to flow through GoDaddy’s expired domain auctions.

Name.com joins Endurance International Group and Tucows in sending their expired stream to GoDaddy. Yes, Tucows, despite being a 50/50 owner in NameJet, resumed sending its domain names to GoDaddy after a test with NameJet.

There’s only one explanation for that: GoDaddy auctions must have significantly outperformed NameJet.


© DomainNameWire.com 2017. 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.

© 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. Major shakeup: Tucows sending expired domain names to GoDaddy Auctions
  2. Another major registrar is sending expired domains to GoDaddy
  3. Here’s what’s happening at Rightside
Categories: Domains

Tucows gets RDNH ruling against Bosch after sloppy UDRP filing

Domain Name Wire - Mon, 03/05/2018 - 13:21

Hopefully this was incompetence rather than malicious intent.

This is definitely not a PPC parking page.

Manufacturing company Robert Bosch GmbH has been found (pdf) to have engaged in reverse domain name hijacking for bringing a UDRP cybersquatting complaint against Tucows over the domain name bosch.net.

Looked at in the best possible light, this was due to extremely inept lawyers.

Bosch.net is one of Tucows’ domains in its RealNames portfolio. RealNames offers email addresses at surnames. For example, if your name is Jeff Bosch, you can use jeff@bosch.net for a fee.

Bosch used the law firm DePenning & DePenning in India. The filing states:

It is also clear that the Respondent is using the domain “www.bosch.net” as a Pay-Per-Click website that links consumers to various goods and services. On entering the search term ‘www.bosch.net’, the user is directed to spam links offering virus contents in such links. It is obvious that the Respondent is trying to create confusion in the market by wrongfully representing that the Complainant, being in the automotive industry, are involved in such businesses.

This is untrue. Why did the complaint state something so obviously untrue?

Well, Tucows’ attorney John Berryhill noted that Bosch selected representatives based in India to act for it in filing the Complaint even though the case has nothing to do with India. He suggested this is because India is a jurisdiction where legal counsel cannot readily be held to account for making untrue statements.

But the complaint also discusses Bosch’s activities in India even though the case has nothing to do with India. Perhaps that was lifted from a prior complaint for Bosch.in. As the panel notes:

The only real possibility the Panel can envisage that was not the result of a deliberate decision to mislead, is an incompetent “cutting and pasting” of the relevant text from an earlier complaint with different facts.

I’m going to go with the latter here.

So in the best possible light, the lawyers screwed up. That’s egregious but it gets worse. Why didn’t they withdraw the case after the response was filed and they realized their error? The panel writes:

It is also in the Panel’s opinion appropriate to note that if the Complaint had included these types of allegation as a result of some sort of mistake, the Panel assumes the Complainant and/or its representatives would have realised this mistake when they saw the Response, which presumably they have read and considered.  It would have been possible at that stage to take steps to withdraw the serious and misplaced allegations that the Complaint makes.  However nothing was done.

I hope this is a case of lawyers not relaying their error to their client. Or not paying attention.

Both are inexcusable.


© DomainNameWire.com 2017. 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.

© 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. Dubai Law Firm Nailed for Reverse Domain Name Hijacking
  3. Telepathy scores $40,000 from reverse domain name hijacking case
Categories: Domains

Domaining Europe to transition to NamesCon Europe

Domain Name Wire - Sat, 03/03/2018 - 00:00

NamesCon will take over the event, which has been rebranded NamesCon Europe.

Domaining Europe, a ten-year-old domain name conference, will become NamesCon Europe beginning with this year’s show in June.

Show founder Dietmar Stefitz will manage the 2018 show with the help of NamesCon. In subsequent years, Stefitz will be an advisor to the show. The deal was not an acquisition.

This certainly makes sense for NamesCon and should help elevate awareness of the show. NamesCon’s marketing engine and brand name will help boost attendance from people in Europe and elsewhere.

NamesCon Europe takes place in Valencia, Spain June 7-9. Tickets are available starting at €423.50.


© DomainNameWire.com 2017. 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.

© 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. Domaining Europe to take place in Berlin in May
  2. Domaining Europe to return to Valencia in 2018
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.