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.

Name.com social media guy’s Tesla video goes viral with help of Elon Musk

Domain Name Wire - Thu, 07/05/2018 - 19:40

With a little help form Elon Musk and Tesla, Jared Ewy’s video explodes.

If you’ve never met Name.com’s Jared Ewy before, hopefully you’ve at least seen some of the funny videos he has created for the company.

He just created his most viral video ever and it has nothing to do with domain names and Name.com. With a little help of a retweet by Tesla and a like by Elon Musk, Ewy’s video of him surprising his family with a new Tesla Model 3 has been viewed over 650,000 times. The tweet itself has 16,000 likes.

It’s a fun video. And I really hope the car purchase wasn’t a complete surprise to Jared’s wife, ’cause that crosses a line I wouldn’t dare touch.

That one time I surprised my family with a @Tesla Model 3. pic.twitter.com/sVuAiII5Gk

— Jared Ewy (@Jaredewy) July 3, 2018

© 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. Name.com piggybacks NameCheap.com $.98 Twitter domain offer
  2. Don’t be like a Tesla apologist
  3. Tesla.com is now Tesla’s main domain name
Categories: Domains

June’s top DNW stories

Domain Name Wire - Thu, 07/05/2018 - 16:49

Here’s a rundown of the top stories and podcasts on DNW from last month:

1. Timing is everything: why .XXX dwarfs other adult top level domain names – The .XXX namespace and others recently sold by ICM Registry paint a picture of how difficult it is to market a new TLD in a crowded environment.

2. Yes, your domain name registrar has made it impossible for people to contact you – The general internet public is just learning about the Whois ramifications of GDPR.

3. Man gets 20 years in prison for trying to steal a domain name – A man is headed to prison after an unusual physical attempt to steal a domain name.

4. Web.com to go private in $2 billion acquisition – The final price could be higher if competing offers come in.

5. Namecheap starts sending expired domains to GoDaddy Auctions – Namecheap is the latest domain name registrar to sign up to sell expired domains through GoDaddy.

Podcasts

All About .Me – I chat with .Me registry CMO Natasa Djukanovic about how the .Me domain name came to be.

Three companies using new TLDs – Three individuals who registered new TLDs for their businesses explain why.

The Amazon FBA business model – Learn about FBA, a unique ecommerce opportunity.

John Pollard: How to grow the usage of domain names – Donuts’ EVP of Registry explains how he believes domain names can find new uses.

© 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. .Me Domains Getting Developed…Slowly
  2. Kings of .Com – Registrar Analysis
  3. Minds + Machines acquires .XXX top level domain operator ICM Registry
Categories: Domains

Verisign patents “Methods and systems for creating new domains”

Domain Name Wire - Thu, 07/05/2018 - 14:31

Verisign patents aspects of its TLD creation and management system.

A diagram from Verisign’s patent for TLD management.

When companies started applying for new top level domain names, most of them reached out to existing registry services providers to handle the backend management of those domains. Companies like CentralNic, Neustar and Verisign (NASDAQ: VRSN) were eager to sign contracts with registries.

Managing lots of new top level domain names added to the complexity of existing systems, though. Registries built new management platforms or restructured their existing ones to accommodate the variety or rules these new TLDs came with..

Verisign, the .com registry, just got a patent (pdf) for certain aspects of its TLD management system.

Titled “Methods and systems for creating new domains”, U.S. Patent number 10,015,134 has 21 claims related to its domain management system. Here’s the abstract:

Systems and methods for creating a new domain, such as a top-level domain or a second-level domain, make use of a Domain Manager that enables a user to enter data that is necessary or optional to implement the creation of a new domain. Systems such as, for example, a Registry and one or more Registrars, may use the data defined by the Domain Manager to create a new domain.

Getting the patent has been a long road. It began with 30 claims back in 2011.

CIRA, the .ca domain name registry, has a pending patent for aspects of its TLD management system.

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

Related posts:
  1. VeriSign Withdraws Request for “Domain Name Exchange” Service
  2. VeriSign Loses Money (Sort Of) as .Com and .Net Top 105 Million
  3. .Com/.Net domain base increases just 0.68 million in second quarter
Categories: Domains

Miray Software AG nailed for reverse domain name hijacking

Domain Name Wire - Wed, 07/04/2018 - 18:01

German software company Miray Software AG has been found to have engaged in reverse domain name hijacking over the domain name Miray.com. The company uses the German country code domain name Miray.de.

The owner of the domain name, who is located in the United States, registered the domain name shortly after Miray claims that it went into business in 2000, but before it had any web presence or had filed trademarks. The company essentially admitted that the domain name owner did not register the domain name to target the software company’s nascent business.

Miray Software subsequently tried to buy the domain name but could not come to terms.

On the issue of registration and use in bad faith, the panel noted:

The Panel merely notes that a registrant who has registered a domain name in good faith is entitled to behave as the Respondent has done in this case, namely to publish any or no content at the associated website, to name its price for such domain if approached by an interested party if it is willing to enter into negotiations to sell it, and ultimately to break off communication with a prospective purchaser if suitable terms cannot be agreed.

Panelist Andrew D. S. Lothian heard the case for World Intellectual Property Organization.

© 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. Lack of disclosure leads to Reverse Domain Name Hijacking finding
  2. Insurance company Allianz tries reverse domain name hijacking a domain name
  3. Another day that ends in Y, another reverse domain name hijacking
Categories: Domains

FarFetch paid $12.5 million for Style.com assets

Domain Name Wire - Mon, 07/02/2018 - 17:42

Company got a lot more than domain names as part of the deal, but Style.com is a very valuable domain.

Last year luxury clothing company FarFetch bought the assets of Conde Nast’s ecommerce venture Style.com. The price wasn’t disclosed, but an eagle-eyed DNW reader reviewed a FarFetch filing with Companies House in the UK. It discloses that the total consideration was $12.5 million.

Two of the assets FarFetch received were Style.com and Style.co.uk, which now forward to FarFetch.com. That said, this wasn’t just a domain purchase. The Style.com intellectual property FarFetch bought probably included some customer data.

Perhaps more importantly, FarFetch cemented its relationship with Conde Naste, publisher of target publications like Vogue, GQ and Vanity Fair. It includes content partnerships and potentially product placement. Conde Naste is also an investor in FarFetch, so there’s that.

Clearly, this wasn’t just a domain name deal. But Style.com is a valuable domain name.

(Hat tip: Chris Perrett of hotdrops)

© 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

The domain name reseller business – DNW Podcast #192

Domain Name Wire - Mon, 07/02/2018 - 16:45

Understand the changing market for domain name reseller services.

The business of domain name resellers is constantly changing. This week, we speak with Aditya Arya, the AVP of Business Operations for LogicBoxes. LogicBoxes helps companies manage their own registrar or become a domain name reseller. Learn how this type of business is changing and the impact GDPR has one it.

Also: WP Engine’s acquisition, ICANN goes to Cancun for Spring Break, a nice .Ca sale, Whois 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 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. The challenges of new TLDs with Tobias Sattler – DNW Podcast #177
  2. Sandeep Ramchandani, CEO of Radix – DNW Podcast #183
  3. All About .Me – DNW Podcast #191
Categories: Domains

How Verisign hit its Q1 growth numbers

Domain Name Wire - Mon, 07/02/2018 - 15:55

Verisign called on China to deliver Q1 domain growth.

.Com registry Verisign (NASDAQ:VRSN) provides guidance each quarter for how much it expects its total base of .com and .net domain names to grow. The company hardly misses because it’s quite easy for the company to pull some levers to hit the numbers.

Consider Q1 of this year. Verisign forecasted 1.5 million to 2.0 million net adds for the quarter. The company was pretty far behind at the end of February, as you’ll see:

.Net Domains
End of Q4 2017: 14.95 million
Jan 14.79
Feb 14.75
March 14.73

.Com Domains
End of Q4 2018: 135.03 million
Jan 135.52
Feb 135.78
March 136.83

By the end of February, .Net was down 0.20 million and .com was up 0.75 million based on the official data Verisign provides to ICANN. That meant Verisign had grown the combined base by 0.55 million domains with one month to go, well below what it promised the street. (Verisign has many measures for domains under management, so the numbers here are off slightly from what the company reported to the street.)

What do to? Verisign can throw “marketing dollars” at registrars to move the needle. It can pay them to promote .com and .net domains. What really moves the needle is offering discounts if the registrar hits certain growth targets.

For example, with time running out, Verisign could go to its Chinese domain name registrars and offer them steep discounts if they hit certain registration targets for the quarter. The registrar then informs top customers (which are sometimes the registrar itself) and passes a discount to them.

Presto–lots of last-minute registrations and the numbers hit.

Take a look at the three Chinese registrars that landed in the top 10 in terms of new .com registrations in March based on the final tally Verisign provided to ICANN.

In March, these were the top 10 registrars in terms of new .com registrations. (Keep in mind that there were three additional days in March than in February.)

1. GoDaddy.com* 975,008 (846,327 in February)
2. HiChina Zhicheng Technology Ltd. 252,159 (81,015)
3. Tucows** 217,900 (206,361)
4. Xin Net Technology Corporation 173,893 (52,388)
5. Endurance+ 170,700 (149,255)
6. NameCheap Inc. 131,423 (117,911)
7. Web.com++ 109,275 (103,383)
8. Google Inc. 96,621 (87,990)
9. West.cn 81,838 (not in top 10)
10. NameSilo 65,566 (60,550)

Do you think that demand in China for new .com domain names suddenly tripled? Or was it pushed?

Verisign’s official domain growth in Q1 was 1.91 million, neatly tucked into the high end of its forecast.

As for where registrars ended up at the end of Q1, here’s the current leaderboard of the top registrars in terms of total .com registrations as of the end of March 2018. :

1. GoDaddy* 47,815,002 (47,490,250 in February)
2. Tucows** 12,960,646 (13,014,976)
3. Endurance+ 7,793,869 (7,844,339)
4. Web.com++ 6,721,816 (6,705,866)
5. HiChina 5,156,343 (4,999,217)
6. NameCheap 4,195,705 (4,085,262)
7. 1&1 3,771,035 (3,766,579)
8. GMO 2,097,311 (2,111,351)
9. Xin Net Technology Corporation 1,928,276 (1,778,658)
10. Google 1,603,663 (1,534,162)

Many domain companies have multiple accreditations and I’ve tried to capture the largest ones. See the notes below.

* Includes GoDaddy and Wild West Domains
** Includes Tucows and Enom
+ Includes PDR, Domain.com, FastDomain and Bigrock. There are other Endurance registrars, but these are the biggest.
++ Includes Network Solutions and Register.com

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

Related posts:
  1. The .Com Report: Uniregistry winning in transfers
  2. .Com Winners & Losers: A slow month
  3. Namecheap leaps up .com chart as PDR falls
Categories: Domains

Lawsuit filed to recover 6-digit domain names

Domain Name Wire - Mon, 07/02/2018 - 14:22

Complaint alleges that five domain names were stolen.

A person in China has filed a lawsuit in an effort to recover domain names they allege were stolen from their domain name registrar account.

Xiaomei Chen filed the in rem action against the domain names 789365.com, 402013.com, 402014.com, 402015.com, and vip999365.com. It also names Lin Bing Jun, but the plaintiff believes the Whois information is fake.

According to the complaint (pdf), the domain names have generated $6,000 in revenue and 325 visits on average each month. The domains were acquired in 2016.

The plaintiff believes the domains were stolen around October 7, 2017 and moved from their GoDaddy account. Most of the domains are still at GoDaddy and one is at NameSilo.

© 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. Lawsuit filed to recover stolen education domain names
  2. Lawsuit filed to recover stolen domains: 5678.com, 26266.com and Manhua.com
  3. Lawsuit filed to recover stolen $100,000 domain name
Categories: Domains

Australia’s .Au domain names are now managed by Afilias

Domain Name Wire - Sat, 06/30/2018 - 23:28

Handover to Afilias is now complete.

It’s already July 1 in Australia, and that means that Afilias is now the backend registry service provider for over 3 million domain names ending in .Au.

.Au domain overseer auDA put the contract for managing .au out to bid, and in December of last year announced that Afilias won the contract, which had been handled by rival Neustar.

Transitioning a 3.1 million-domain namespace is unprecedented. The previous record for the size of a registry transitioned was .org back in 2003. At the time it had 2.4 million names under management. The gaining registry in that case was also Afilias.

As a result of the .au transition, Afilias now helps run 200 TLDs and more than 22 million domain names.

© 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. auDA drops Neustar, to transition 3 million .au domain names to Afilias
  2. Afilias plans to raise $100 million, warchest will help in new top level domain auctions
  3. Domain name registry Afilias dumps planned IPO
Categories: Domains

Google Adwords no more

Domain Name Wire - Fri, 06/29/2018 - 18:53

Google is changing the name of its iconic Adwords advertising service.

For those nostalgic about the old days of online advertising, we’re almost at the end of an era.

Google Adwords is rebranding its service as merely Google Ads in the coming weeks.

The rebranding makes sense. Adwords started out as an ad program made up of only text ads but has grown to include display ads, video ads and more.

Still, I can’t help but feel a bit nostalgic. I was an early advertiser with the pioneer in text ads, GoTo, which later became Overture and was then acquired by Yahoo. Adwords was Google’s answer to GoTo.

I remember placing ads on the system in the early days when you had to bid on a CPM basis rather than clicks.

While Adwords has changed a lot over the years, one thing that hasn’t changed is its moniker.

Until now.

© 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. Is Direct Navigation Too Expensive?
  2. Google AdWords Now Supports Internationalized Domain Names
Categories: Domains

Yes, your domain name registrar has made it impossible for people to contact you

Domain Name Wire - Thu, 06/28/2018 - 17:04

Many registrars have removed all means for people to contact you.

I received an anonymous voicemail yesterday from an Enom customer who was frustrated that the Whois records for his domain names had been replaced with “fake” information. Here’s what he said:

I was just calling to see if you had heard anything about Enom changing everybody’s contact information to completely false information without their permission. I guess trying to comply with the European thing, but it’s a pretty sloppy way to do it. The address is a fake address, doesn’t forward, all the information is fake, there’s no way to contact anybody about technical issues or anything and they changed every one of mine for hundreds of domain names. I don’t know if they did everybody or not.

Here’s what a Whois record for one of my domains at Enom looks like:

The only way to reach someone about this domain through the Whois record is to email Enom’s abuse address.

Whois is in flux because of ICANN’s last-minute decision on how to handle Whois thanks to the EU’s General Data Protection Regulation (GDPR).

Technically, registrars must provide a way for people to contact the domain name owner via email or a web form. That might take some time to implement, though. It will essentially be like anonymized emails addresses used in Whois privacy and proxy products.

Also, the registrar must give customers the option to publish their contact information. But the deadline for this is “as soon as commercially reasonable”. Here’s the relevant section from the temporary specification:

7.2.1. As soon as commercially reasonable, Registrar MUST provide the opportunity for the Registered Name Holder to provide its Consent to publish the additional contact information outlined in Section 2.3 of Appendix A for the Registered Name Holder.

Here’s what’s in section 2.3 of Appendix A:

Registry Registrant ID
Registrant Name
Registrant Street
Registrant City
Registrant Postal Code
Registrant Phone
Registrant Phone Ext
Registrant Fax
Registrant Fax Ext

Additionally, the registrar may (but is not required) provide customers with the opportunity to publish admin, tech and other contacts.

We’re in a rough period right now. ICANN is suing an affiliate of Enom over the company’s interpretation of GDPR as it relates to Whois data. Some registrars, like GoDaddy, continue to publish the data.

It’s going to take months for this to all shake out. And that might be optimistic.

© 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. GoDaddy will continue publishing most domain owner data
  2. Whois GDPR carnage continues: Afilias to ditch almost all data in Whois on millions of domains
  3. Tucows responds to ICANN legal action related to GDPR
Categories: Domains

UDRP after GDPR: challenges without Whois

Domain Name Wire - Thu, 06/28/2018 - 13:53

Lack of public Whois makes filing a UDRP a two-step process.

GDPR is impacting the Uniform Domain Name Dispute Policy process. Without public Whois, companies that believe someone is cybersquatting on their domain might have to “go blind” into a UDRP filing; they won’t know who the domain name registrant is.

This is one of the things World Intellectual Property Organization is grappling with, and it has an FAQ for complainants that explains how this works.

Once a complaint is filed, WIPO gets the registrant’s information from the registrar and passes it along to the complainant. The complainant has a chance to amend its complaint at this point.

The complainant can also drop the case at this point based on what it learns about the registrant. According to WIPO, 20% of cases are settled before a panelist is assigned to a case. (I suspect most of these are cases in which the domain owner voluntarily hands over the domain.)

The WIPO FAQ does not address a common argument made by complainants: that the domain owner acted in bad faith by using a Whois privacy service. Item 3.6 of the WIPO Overview of WIPO Panel Views on Selected UDRP Questions, Third Edition explains what panels infer from the use of a privacy or proxy service. There are plenty of legitimate uses for privacy that don’t include hiding a cybersquatter’s identity.

But with GDPR, the privacy/proxy argument is effectively dead. Whois is masked by default at most registrars now and some are using their Whois proxy services to do this. It’s not up to the registrant.

I still expect some complainants to make this argument, probably cutting-and-pasting from their argument database. But the argument is null and void.

© 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. Guest Article: How Do I Become a UDRP Arbitration Panelist?
  2. ScotiaBank Loses Case for Caribana Festival Domain Name
  3. A troubling connection in a UDRP
Categories: Domains

End user sales: Canadian companies spend $50k on .ca domain name

Domain Name Wire - Wed, 06/27/2018 - 16:55

Loyalty program partnership puts .Ca domain on top of the leaderboard.

Royal Bank of Canada and WestJet recently announced a new loyalty platform, and they paid dearly for the associated domain name: Ampli.ca for $50,000.

This was Sedo’s top reported sale for the past week. There are some notable sales that we don’t know the buyer for yet. Firehose.com sold for $35,000. This domain reminds me of Shane Cultra’s BlowTorch.com. It will make a great brand.

Also, SongExchange.com sold for $25,000.

Here are the domains I was able to determine sold to end users at Sedo during the past week:

(You can view previous lists like this here.)

Ampli.ca $50,000 – Royal Bank of Canada. This domain is for a new loyalty program between RBC and WestJet. Ampli.com is owned by a company that sells portable sound systems.

TheLocal.fi €19,000 – The Local is a website with news in Finland written in English.

Orchesto.com $5,500 – Technology company Zebware launched Orchesto, a multi-point object storage gateway compatible with Amazon S3 cloud storage, earlier this month.

Reason.co £4,000 – Reason calls itself a “digital product and service studio.”

Jam.net $3,990 – WildWorks is the gaming company behind Animal Jam.

Strenia.com $3,500 – Strenia Solutions is a tech company with offices in Australia, Germany and South Africa. It uses the domain name StreniaSolutions.com.au.

RealtorNow.com $2,950 – I hope the guy who bought this domain has rights to use the Realtor trademark.

Laramie1.com €2,900 – Laramie County School District No. 1 in Wyoming.

GotCramps.com $2,000 – Avadim Technologies is a life sciences company. One of its products, called Theraworx Relief, helps prevent foot and leg cramps.

© 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

Reverse domain name hijacking in AquaFX.com case

Domain Name Wire - Wed, 06/27/2018 - 13:08

Panel says case was a Plan B attempt to get the domain name.

A three-person National Arbitration Forum panel has found Aqua Engineering & Equipment, Inc. to have engaged in reverse domain name hijacking over the domain name AquaFX.com.

The company failed to convince the panel that it met any of three necessary points of UDRP: that the domain was confusingly similar to a mark in which it has rights, that the domain owner lacks a legitimate interest in the domain, and that the domain was registered in bad faith.

Aqua Engineering & Equipment relied on a stylized trademark for “Aqua Fx The Leaders in Reverse Osmosis”. Furthermore, this mark was registered after the respondent registered the domain name.

The panel determined that this was a “Plan B” reverse domain name hijacking attempt.

The domain owner was represented by ESQwire.com.

In a different National Arbitration Forum decision today, panelist Calvin A. Hamilton declined to find reverse domain name hijacking for the domain name shippingquestscams.com. His reason: he found that the domain was confusingly similar to the complainant’s trademark. That’s unfortunate; panels should discourage complainants from filing complaints against non-commercial gripe sites.

© 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

WP Engine acquires StudioPress, maker of the Genesis framework for WordPress

Domain Name Wire - Wed, 06/27/2018 - 12:48

WordPress hosting company acquires maker of popular framework for building WordPress sites.

WordPress hosting company WP Engine has acquired StudioPress.

StudioPress is the creator of the Genesis framework for WordPress site design/development. Domain Name Wire is built on the Genesis framework.

This marks the first acquisition WP Engine has publicly announced since Silver Lake Partners bankrolled the firm with $250 million earlier this year.

Silver Lake was one of the three private equity firms to invest in GoDaddy in 2011. WP Engine is a direct competitor to GoDaddy.

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

Related posts:
  1. VaultPress drops its price for WordPress security and backup
  2. How to reduce comment spam on your WordPress website
  3. WP Engine banks $250 million from PE that bought GoDaddy
Categories: Domains

ICANN selects Cancun, Kuala Lumpur and Hamburg for 2020 meetings

Domain Name Wire - Tue, 06/26/2018 - 14:30

Spring break in Mexico, anyone?

The ICANN board has selected its meeting locations for the group’s 2020 meeting slate.

The first stop will be the Cancun International Convention Center in Mexico for meeting #67 from March 7-12, 2020. You might notice that those dates coincide with some schools’ spring breaks. I predict a few snarky headlines about ICANN heading to Cancun for a Spring Break boondoggle.

The 2020 Community Forum, ICANN 68, will be held at at the Kuala Lumpur Convention Center in Malaysia June 22-25, 2020. It is being hosted by Dr. Suhaidi Hassan of the Internet Society Malaysia Chapter.

ICANN 69 will be in Hamburg, Germany at the Congress Center October 17-22, 2020. It will be hosted by eco association, DENIC and the City of Hamburg at the Congress Center Hamburg.

© 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. Colombia Faces Uphill Battle to Host ICANN Meeting in December
  2. ICANN Travel Survey – Poll FAIL
  3. Which ICANN sessions domainers should attend
Categories: Domains

Supplement makers sue LegitScript

Domain Name Wire - Tue, 06/26/2018 - 14:17

LegitScript, which has gone after domain name registrars in the past, is sued by supplement makers.

Three supplement makers have sued LegitScript, a company that helps web service providers and banks screen for illegitimate pharmacies and questionable supplements.

SanMedica International LLC, Novex Biotech, LLC, and Carter-Reed Company, LLC allege that LegitScript is wrongfully flagging its products, which is preventing the companies from promoting the products on websites.

Domain name companies are familiar with LegitScript because the group, funded in part by pharmaceutical companies, has gone after registrars that it says were allowing illegitimate online pharmacies to register domain names with them.

In its lawsuit, the plaintiffs say that LegitScript has turned its attention to supplements after mastering the process of taking down bad online pharmacies. They believe that LegitScript uses the wrong criteria to determine if a supplement should be added to its blacklist that is used by companies like Facebook, Google and Visa.

The full lawsuit is here (pdf).

© 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

All About .Me – DNW Podcast #191

Domain Name Wire - Mon, 06/25/2018 - 15:30

Learn about the origins of the .Me domain name.

You’ve surely seen .me domain names and might even own some in your domain name portfolio. Today you’re going to learn about how the .me domain name came to be and why it has been successful when we talk to Natasa Djukanovic, the CMO of the .Me registry.

Also: Web.com takeover, RDNH bonanza, Mugshots.com update 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 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. NamesCon recap with 15 interviews – DNW Podcast #172
  3. The challenges of new TLDs with Tobias Sattler – DNW Podcast #177
Categories: Domains

Another day that ends in Y, another reverse domain name hijacking

Domain Name Wire - Mon, 06/25/2018 - 15:20

Verdant Services of Seattle guilty of reverse domain name hijacking.

Well, it’s another day that ends in ‘y’, so I have another reverse domain name hijacking case to report.

This time it’s Verdant Services, Inc. of Seattle trying to reverse domain name hijack Verdant.com. It owns the domain VerdantServices.com.

The domain name is owned by VRDT Corporation, which goes by the name Verdant. VRDT was the company’s ticker symbol when it was previously publicly traded.

The respondent bought the domain name for $80,000 in 2012. As you can see by going to Vergant.com, the domain forwards to VRDT.com, which is a website with details about the respondent’s company.

Here’s one of the curious arguments made by the complainant:

Complainant tried to buy the Domain Name from Respondent in 2017, without success. Because Complainant sought to acquire the Domain Name, Respondent knew that Complainant existed and had an interest in the trademark corresponding to the Domain Name.

Hello, Plan B reverse domain name hijacking!

Here’s part of what World Intellectual Property Organization panelist David H. Bernstein wrote in finding Verdant Services, Inc. guilty of reverse domain name hijacking:

On its face, this Complaint did not state a claim for transfer under the Policy. Complainant’s evidence established that Respondent had made a bona fide use of the Domain Name in the past, that Respondent’s acquisition of the Domain Name in 2012 therefore could not possibly have been in bad faith, and that Respondent was not in fact defunct (since Respondent responded to Complainant’s emails as recently as November 2017). The Complaint was also legally deficient to the extent it was essentially arguing for retroactive bad faith, a concept that has firmly been rejected as set out in the WIPO Overview 3.0. Alternatively, if Complainant did not intend to argue for retroactive bad faith (since that part of the Complaint is somewhat unclear in its reasoning), then the Complaint was devoid of any allegations whatsoever establishing bad faith registration. And, the Complaint included no facts that establish bad faith use.

The weakness of the Complaint was all the more apparent once Respondent responded, with evidence not only of its good faith registration and its legitimate interest in the VERDANT mark, but also with evidence of its business interests that continue to operate under the name. These are facts that should have been readily apparent to Complainant, had Complainant investigated Respondent’s use prior to filing the Complaint. In light of the Complainant’s knowledge of Respondent’s prior bona fide use of the Domain Name and the other facts discussed above, it was improper for Complainant to file a challenge and claim that Respondent was defunct without adequate investigation of the true facts.

The complainant was represented by Carstens & Cahoon, LLP, an intellectual property law firm.

© 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. UDRP complainant shoots self in foot with supplemental filing
  2. Telepathy scores $40,000 from reverse domain name hijacking case
  3. Insurance company Allianz tries reverse domain name hijacking a domain name
Categories: Domains

New TLD data leads onlookers astray

Domain Name Wire - Mon, 06/25/2018 - 14:49

You need context in order to understand the data.

There are many good sources for new top level domain name data out there. Sites like nTLDStats.com and namestat.org do a good job presenting data.

But without context, it can mislead onlookers. Onlookers would think that .top is the most popular top level domain and HiChina is absolutely crushing it with new TLD sales.

Of course, insiders know the reason .top has more domains registered and HiChina is a top seller.

Consider a post on SeekingAlpha this morning titled “GoDaddy Is Unprepared For The Future Of Domain Names”.

(Upfront, I should mention that basically anyone can write stock analysis for Seeking Alpha and they get paid based on the traffic those articles drive. The person who submitted this article has only written two other articles for the site and they are about bitcoin and a South American Bank.)

The author of this article, Ben Holden-Crowther, argues that GoDaddy is overvalued. he might be correct; GoDaddys stock has been on a meteoric rise. Its market cap has ballooned from $4 billion in early 2016 to $12 billion today.

But the article’s thesis is that GoDaddy is overvalued because it’s behind the game in new TLDs. It points to the “missed opportunity” of GoDaddy appling for and selling its own top level domain names, and references the top new TLD charts on nTLDStats. Quote:

With 23 million domain names registered under these new gTLDs since 2013, the new extensions are clearly playing an increasingly important role in the success of a domain name business.

OK, there are 23 million registrations. But we all know most of those are giveaways or dollar domains. Especially the top domains on the chart.

The writer points out that Uniregistry owns and sells its own new TLDs, cutting out the middleman. Well, ask Uniregistry how new TLDs are turning out for it compared to expectations.

The author also points out that GoDaddy is #3 in market share for new TLDs. (It’s #1 in domains overall.) Missing here is that same quality question: you can be #1 for new TLDs if you focus on selling domains for pennies.

If I had to benchmark new TLD preparedness, there are only a handful of registrars I’d put at or above GoDaddy. One is Name.com, which is owned by a major new TLD registry and has a big incentive to push new TLDs.

This Seeking Alpha article is just the latest example of how people can be misled by new TLD metrics. New TLDs will continue to exist and sales of the domains to end users will continue to grow over time. But there’s a lot of noise in the numbers. In fact, I could counter the entire article by showing that new TLD registrations have dropped from a peak of about 30 million a year ago. That ignores the context, though. The reason for the drop is free and penny domain promotions being throttled back.

Context is key when it comes to domain data. Without context, we’ll continue to see articles like the one published today on Seeking Alpha.

© 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. GoDaddy lets customers “watch” new TLDs
  2. GoDaddy gets sixth patent for “Adwords for Top Level Domains”
  3. GoDaddy auction data provide early indication of new TLD demand and values
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.