skip to content

News

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

Radix publishes second time renewal data for some TLDs

Domain Name Wire - Tue, 11/14/2017 - 14:44

Second-anniversary renewals in three domains were 77%.

Radix Registry, a new top level domain name company with nine top level domain names, has reported second-anniversary renewal rates for its three most popular top level domain names.

The company said that overall renewal rates for the second renewal on .online, .tech and .site domain names registered during the first 30 days of general availability were 77%.

.Site had the highest at 81%, .Tech was 78% and .Online was 75%.

These numbers seem in line with those at other registries. Last year, Rightside (now part of Donuts) reported that 81% of names renewed on their first anniversary were also renewed on their second anniversary.

Domain names tend to have their lowest renewal rate in the first year.

Radix reported that domain names registered during Sunrise and Early Access had even higher renewal rates. Sunrise domains are mostly for brand protection and domains purchased during Early Access had a one-time premium, so renewal costs aren’t as high.


© 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.

The post Radix publishes second time renewal data for some TLDs appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. This week’s new TLDs: A big week for Donuts, Radix
  2. Get .online this week…
  3. .Online is fastest to 50,000 registrations
Categories: Domains

Equifax gets control of 138 Equifax Security domain names

Domain Name Wire - Tue, 11/14/2017 - 14:28

Domain names were registered to take advantage of data breach.

Credit bureau Equifax (NYSE:EFX) has successfully won control of 138 domain names that were registered after it reported a security breach this summer.

In the wake of the breach, the company set up an official site at EquifaxSecurity2017.com. That’s not an easy domain name to remember. Even Equifax’s own employees directed people to the wrong site.

China Capital Investment Limited registered 138 domain names similar to EquifaxSecurity2017.com. Many of them are typos that redirect to parking pages with ads for identity theft protection and credit scores.

Equifax filed a cybersquatting complaint with World Intellectual Property Organization (WIPO). The WIPO panel agreed that this is a case of cybersquatting and ordered the domain names to be transferred to Equifax. The transfer should be complete within ten days.

Douglas M. Isenberg of The GigaLaw Firm represented Equifax.


© 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.

The post Equifax gets control of 138 Equifax Security domain names appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Future Media Architects Prevails Against Equifax for EFX.com
  2. Arena.com Owner Wins Domain Name Arbitration
  3. Louis Vuitton Loses Domain Dispute for Mobile Domain Name
Categories: Domains

GoDaddy files lawsuit to take down Whois spammers

Domain Name Wire - Mon, 11/13/2017 - 19:39

Lawsuit targets people and companies allegedly sending spam and saying they are associated with GoDaddy.

GoDaddy has filed a lawsuit (pdf) in an effort to take down one of the groups that it alleges is spamming offers to domain name owners and pretending to be affiliated with the registrar.

If you’ve ever registered a domain name without Whois privacy, you are probably a victim of the defendants or a similar group.

The lawsuit was filed in U.S. Federal District Court in Northern California against Usman Ghaznavi a/k/a Usman Anis, Salman Ghaznavi a/k/a Salman Anis, Silicon Valley Graphic, LLC d/b/a Silicon Valley Graphics (“SVG”), and Does 1 through 50.

It alleges that the defendants undertook a long and sophisticated scheme to spam domain name registrants to offer them logo services, web animations and more. Many of these spam messages pretended to be affiliated with GoDaddy.

This led to many complaints to GoDaddy. GoDaddy even received a letter from a lawyer threatening to file a class action lawsuit against the registrar for its unsolicited emails.

The defendants allegedly used domain names like g0daddydesigns.com, godaddydesignagency.com and godaddyanimations.com to run the scheme. They also used non-branded domains like route66d.com. (I recall receiving multiple text messages linking to route66d.com.)

GoDaddy was able to uncover the possible identities of the perpetrators by working with WhoisGuard to reveal ownership data of one domain. It looks like the defendants got a little sloppy, too; Godaddy alleges that they registered six of their infringing domain names at GoDaddy.

There are many groups spamming owners of newly registered domain names and pretending to have an affiliation with GoDaddy. This hurts GoDaddy and the recipients of these messages.

While this lawsuit is aimed at just one group, a big success could lead to a reduction in these scams.


© 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.

The post GoDaddy files lawsuit to take down Whois spammers appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. NBC Approves Two Go Daddy Ads for Super Bowl
  2. GoDaddy says It’s Go Time: new marketing, improved site
  3. GoDaddy fixes domain forwarding glitch
Categories: Domains

October’s Top 5 Domain Name Wire Stories + podcasts

Domain Name Wire - Mon, 11/13/2017 - 16:59

What made news in the domain name industry in October? Here’s your answer…these were the top five stories on Domain Name Wire last month.

1. Kevin Ham sells domain names to GoDaddy – GoDaddy picked up a portfolio of about 100,000 domains, many of which trace back to Kevin Ham’s businesses. The deal came on the heels of another big acquisition…

2. Here’s why GoDaddy – Donuts deal makes a lot of sense – Analysis of why it made sense for GoDaddy to buy Donuts’ portfolio of (mostly) .com domain names.

3. Who won and lost in .Com? – GoDaddy and Tucows remain at the top of the list.

4. MerryJane.com asks: Is Kush.com worth $3 million? – No, but it could be a nice domain for a marijuana company.

5. Donuts’ numbers show promise for new TLD business model – Donuts shows nice growth in its registration base. What kind of renewal rates will it get when discounted domains come up for renewal?

Podcasts

#158 – How to Sell More Domains with Adam Strong (some good tips in this one!)

#157 – interviews with several domain companies from the Merge conference

#156 – Understand Blockchain with Ken Hansen (it’s like Blockchain for dummies)

#155 – From parked ads to blocking ads with Tim Schumacher


© 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.

The post October’s Top 5 Domain Name Wire Stories + podcasts appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Paul Nicks of GoDaddy – DNW Podcast #160

Domain Name Wire - Mon, 11/13/2017 - 16:30

What GoDaddy has learned by being a domain investor.

This week we talk with Paul Nicks, GM and VP of Aftermarket at GoDaddy. GoDaddy has become a domain investor by purchasing large portfolios of domain names. The company has learned a lot about selling domain names in this role, and Nicks will share some data and tips to help you sell more domains. We also discuss GoDaddy’s roadmap with Afternic/GoDaddy and how it plans to create a seamless experience in the domain aftermarket. Also: Donuts is growing fast, GoDaddy’s $50 million domain buy, bad three-letter domain cybersquatting decision 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.

The post Paul Nicks of GoDaddy – DNW Podcast #160 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. What you need to know from ICA – DNW Podcast #128
  2. How End User Domain Buyers Think – DNW Podcast #134
  3. Chad Folkening – DNW Podcast #154
Categories: Domains

Domain reads: .Com for uptime, .Bank transitions

Domain Name Wire - Mon, 11/13/2017 - 15:03

Domain industry pros should read these two articles.

I read a couple of interesting domain name related stories over the past few days that should be interesting to DNW readers. They give perspectives on domain names from people outside the domain name industry.

The first is a story from social media stream company Stream titled Why Stream Stopped Using .IO Domain Names for Production Traffic.

People in the domain industry often talk about the confusion of using alternatives to dominant top level domain names like .com. But Stream has another reason to choose a mainstream TLD: uptime.

The company uses the domain name GetStream.io for its website and also used a .io domain for its API. But a failure by the .io registry on September 20th made it rethink this.

Verisign talks a lot about its uptime record. Here’s a company recognizing that.

After the registry technical issues, Stream decided to move its production domain name to a .com and will add a .org as a backup.

Some of these catchy country code domain extensions are being snapped up by new companies, but I hope they understand what they are getting. .AI is a country code for a country of 15,000 people. The registry is run by one guy. He might be great at what he does, but he also represents a single point of failure.

Afilias has taken over the .io domain name so its backend should be better going forward (although this latest issue seems to have been when the domain was under its control). Afilias manages the registry backend for .org.

I haven’t heard of any downtime issues with new top level domain names. This might be because some are not used very much. As Stream pointed out in its post, if .com had an issue everyone would be talking about it and it would be fixed quickly.

The second article is about the .bank top level domain name. American Banker author Mary Wisniewski wrote The internet name many banks are afraid to use. It’s friendlier to .bank than the headline suggests.

It points out that many banks just haven’t gotten around to transitioning to .bank. They have lots of other IT projects to handle.

But it also talks about consumer confusion. Consider when Farmers & Merchants State Bank switched its domain name to FM.bank.

Here’s something I didn’t think about: consumers can be confused when a new domain is at the end of a sentence. They think the last dot is part of the domain:

The $1 billion-asset bank also noted some assumed when a sentence ended “.bank.” in its promotional materials, the last period was part of the web address, instead of perfect punctuation.

“We had to rework the sentence,” said J. Marty Filogamo, Farmers & Merchants State Bank senior vice president and marketing manager, chuckling.

Both of these articles highlight experiences people outside the domain industry have had with domain names.


© 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.

The post Domain reads: .Com for uptime, .Bank transitions appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. About those .io domain names…
  2. The accidentally successful top level domain names
  3. Kevin Ham and Mike Mann let these prize-winning domain names expire
Categories: Domains

What is Amazon Harmony?

Domain Name Wire - Mon, 11/13/2017 - 14:21

Amazon.com is registering a lot of domains for Amazon Harmony.

Update: Amazon Harmony is the name Amazon’s is giving to its support reps that work on musical devices. They offer discount codes if you call them:

 

 

Amazon.com has registered a lot of domain names related to Amazon Harmony over the past several days.

Normally when I see a bunch of registrations like this it’s easy to tie it to a new product announcement or acquisition. But when I search for “Amazon Harmony” all I find are links to the Logitech Harmony on Amazon.com.

Adding to the intrigue is a focus on the word “associate” after Amazon Harmony. Associates is the name for Amazon’s affiliate program.

The company has registered AmazonHarmony in a number of extensions. One domain it doesn’t have yet is AmazonHarmony.com. That’s used by a company that sells natural products from Colombia.

Here’s the list of domain names. What am I overlooking? Has Amazon made an announcement that I’ve missed?

amazonharmony.info amazonharmonyassociate.info amazonharmonyassociates.info amazonharmony.net amazonharmonyassociate.com amazonharmonyassociate.net amazonharmonyassociates.com amazonharmonyassociates.net amazonharmony.deals amazonharmony.discount amazonharmony.promo amazonharmony.qpon amazonharmony.shop amazonharmony.shopping amazonharmonyassociate.deals amazonharmonyassociate.discount amazonharmonyassociate.promo amazonharmonyassociate.qpon amazonharmonyassociate.shop amazonharmonyassociate.shopping amazonharmonyassociates.deals amazonharmonyassociates.discount amazonharmonyassociates.promo amazonharmonyassociates.qpon amazonharmonyassociates.shop amazonharmonyassociates.shopping


© 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.

The post What is Amazon Harmony? appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Amazon: Kindle Beats Nook
  2. Is Amazon.com the biggest user of new domain names?
  3. Amazon.com foreshadows AWS re:Invent news with domain name registrations
Categories: Domains

An example of how to reduce domain confusion

Domain Name Wire - Fri, 11/10/2017 - 20:13

This company’s decision to use a .net domain is a mistake.

I was cleaning out my inbox this afternoon when I came across two emails from my daughter’s school about student photos.

The first email announced that school photos were in and we can order copies from the photography company Strawbridge at Strawbridge.com.

Shortly thereafter, the second email arrived stating — oops! — it’s Strawbridge.net.

Strawbridge.com is owned by Macy’s (here’s why).

I think the photography company’s decision to use Strawbridge.net is a mistake. Its formal company name is Strawbridge Studios. They could buy StrawbridgeStudios.com on Afternic for only $1,816. It’s a bit longer but is less likely to lead to confusion.

Even a new TLD choice like Strawbridge.photos is less likely to lead to confusion than using the .net.

Or perhaps, since Macy’s no longer uses the Strawbridge brand, the photography company should try to work out a deal with the struggling department store.


© 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.

The post An example of how to reduce domain confusion appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Tucows’ revenue hit $85 million in Q3, company plans for GDPR

Domain Name Wire - Fri, 11/10/2017 - 17:26

Revenue hits another record as company works to meet EU privacy law deadline.

Domain name, mobile and internet services company Tucows (NASDAQ:TCX) reported earnings after the bell yesterday.

The company reported record quarterly revenue of $85.0 million. That’s up 73% compared to the same quarter last year, with most of the growth coming from the acquisition of Enom this year. Domain revenue jumped from $29.8 million in Q3 2016 to $62.0 million this year.

Quarter over quarter, the topline number barely budged. The company reported $84.2 million revenue in Q2 of this year.

On an investor conference call yesterday, Tucows CEO Elliot Noss said that the company continues to invest heavily in engineering to prepare for complying with the European Union’s General Data Protection Regulation (GDPR). (Learn more about GDPR)

The company sent a notice to OpenSRS resellers at the end of October suggesting that they speak with their lawyers about GDPR. The OpenSRS website explains how the company is preparing. It states that it will implement a post-purchase consent request regarding use of personal 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.

The post Tucows’ revenue hit $85 million in Q3, company plans for GDPR appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. As New Domain Registrations Fall, Domain Registrars Get Desperate
  2. .Com Winners & Losers: Big changes ahead
  3. Who won and lost in .Com?
Categories: Domains

Bigfoot says it was swindled in celebrity website purchase

Domain Name Wire - Thu, 11/09/2017 - 21:05

Company expected to gross $1.5 million per year from website but now only makes hundreds.

Michael Gleissner is keeping his lawyers busy.

I’ve written about Gleissner many times due to his questionable trademark and other activities.

This time one of his firms, Bigfoot Corporation, is suing (pdf) over a website it bought in 2014.

According to the suit, Bigfoot entered into an agreement in November 2014 to buy TheCelebrityCafe.com for $775,000, with $573,500 up front in cash. Bigfoot says the sellers represented to it that the site had annual revenue of $1.5 million and profits of $0.95 million.

First warning sign: someone with a site making about a million dollars in profit a year will sell it for only $775,000?

Bigfoot alleges that only a small fraction of the visits to the site were organic traffic. It implies that it did not know this until after it bought the site. In March 2015, for example, 8.5% of the visits were organic and the rest (19 million+ pageviews) were purchased traffic. Because of the purchased traffic, Google started blocking Adsense ads from displaying on the site shortly thereafter. (Google will not show ads on sites that receive low-quality or unnatural traffic.)

Revenue dropped to just “hundreds of dollars” a year after Google stopped serving ads, Bigfoot states.

Bigfoot alleges that the seller committed fraud. It is asking for the $573,750 it already paid for the acquisition to be paid back as well as $950,000 in consequential damages (that’s about how much it expected to earn in a year).

The dollar figures are pretty big compared to what most websites sell for on sites like Flippa. I’m rather surprised that the methods the site used to generate traffic weren’t discovered during due diligence.


© 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.

The post Bigfoot says it was swindled in celebrity website purchase appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Domainer files lawsuit claiming Roxi.com is stolen

Domain Name Wire - Thu, 11/09/2017 - 20:11

Lawsuit seeks to recover Roxi.com.

A domain name investor has filed a lawsuit (pdf) to try to recover Roxi.com, which was allegedly stolen.

John Lee of Precision Telephone Services, Inc. filed the lawsuit. The suit claims that he was the original registrant of the domain name in 1999. The domain name was subsequently hijacked from his account and transferred to another registrar after his email account was compromised.

It seems that Lee did not notice the theft immediately. DomainTools historical Whois records indicate that the ownership change occurred in the middle of 2015.

Lee filed suit in U.S. District Court in Virginia where .com registry Verisign is located. The suit claims that the registration violates the Anticybersquating Consumer Protection Act (ACPA).

Filing a lawsuit under ACPA in Virginia is a common tactic used to recover stolen domain names. The thief won’t show up and the court usually grants a default judgment ordering Verisign to transfer the domain name.

Stevan Lieberman is representing the plaintiff.


© 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.

The post Domainer files lawsuit claiming Roxi.com is stolen appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. John Berryhill gets stolen EHT.com domain returned through UDRP
  2. UDRP panel doesn’t give back OnlineMBA.com, stolen from Moniker
  3. Lawsuit filed to recover stolen three letter .com domain names
Categories: Domains

What domains Domino’s, Mattress Firm and others bought this week

Domain Name Wire - Thu, 11/09/2017 - 17:20

Domino’s gets a Spanish domain name, Mattress Firm buys a nice descriptive domain name and more.

A couple large companies bought domain names on Sedo over the past week, but their purchases weren’t the biggest. The top sale was Mommy.com for $100,000. But as I ask below, is this an end user sale? Should it even be considered a domain name sale?

Other end user purchases this past week include a .co for nearly five figures and a four letter .com that is also a word in Indonesian.

Let’s get to the list…

(Like this end user list? You can view previous lists like this here.)

Mommy.com $100,000 – Can we call this an end user sale? Can we even call it a domain name sale vs. a website sale? The Whois record is private. There’s an operating site that has information for parents, but there was a similar site before the transaction. Sedo broker Dave Evanson told NamePros that the deal was for the domain name only, but that doesn’t mean the buyer did not value existing SEO value from the previous content.

LegacyLife.com $30,000 – The domain name is still being transferred but the price suggests it’s an end user. My guess is the buyer is one of the many life insurance companies that use the name Legacy Life.

Raise.co $9,500 – RAISE is a French firm that invests in mid-sized companies. It uses the domain name RaiseFrance.com.

MinCoins.com $5,000 – The email address used to register the domain links to Tomin Group, a company that specializes in water filtering.

AstraDirect.eu €4,999 – AstraDirect Leasing und Service GmbH in Germany.

BestSleep.com $4,500 – Mattress Firm, a large mattress chain.

GEContracting.com $4,260 – Green Energy Contracting, LLC. I wonder if the GE conglomerate will take issue with this domain?

Ilmu.com $3,395 – Ilmo is Indonesian for Science. The Whois record is private but a holding page says a site is coming soon. The buyer got a good deal.

Axerc.com $2,999 – Axelrod Capital is a cryptocurrency investment firm.

Technium.net €2,500 – DMG MORI is a Japanese technology firm. I can’t find a reference to Technium on its website.

Dominos.es €2,200 – The Domino’s pizza chain.

CoreData.eu €2,000 – AI Corenet Limited in Cyprus. From its website: “Core Data Services (CDS) is a data and statistics provider with an emphasis on low-latency, real-time sports data feeds.”


© 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.

The post What domains Domino’s, Mattress Firm and others bought this week appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. 18 end user sales from $750 to $17,500
  2. Big-name end user domain purchases, including a .org for $55,000
  3. End user domain name sales including new TLDs and the ACLU
Categories: Domains

Domain name company Donuts tops Deloitte’s 2017 Technology Fast 500

Domain Name Wire - Thu, 11/09/2017 - 15:13

Three-year revenue growth tops 59,000%.

A lot more Donuts than a few years ago.

New top level domain name company Donuts ranked #1 on this year’s 2017 Technology Fast 500 from Deloitte.

Rankings were based on three-year revenue growth from 2013-2016. The timing worked out great for Donuts. It launched its first new top level domain names in early access and general availability in early 2014, but sunrise and some brand protection offerings began in 2013. It had a small base of revenue to work off of.

Still, its 59,000% growth rate is impressive. The minimum revenue required in 2013 to qualify for this year’s Fast 500 was $50,000. Even at the minimum, that means Donuts’ 2016 revenue was about $30 million. But the number is certainly much higher than that.

In May of 2016, the company disclosed to me that its premium domain sales were generating $9 million in annual revenue and represented 15% of sales. Assuming sales is in line with revenue, this suggests about $60 million in annual run rate near the beginning of 2016. Given the growth in sales during the remainder of 2016, I suspect the number is much higher than $60 million.

The margins on this revenue are substantial, too. The company had about 40 employees at the beginning of the year and other expenses are minimal.


© 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.

The post Domain name company Donuts tops Deloitte’s 2017 Technology Fast 500 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. MMX releases 2015 report, discusses go-forward strategy
  2. Divyank Turakhia sells Media.net for $900 million
  3. Topcoin plans ICO with goal of being loyalty program for digital goods
Categories: Domains

Valuable IMI.com domain name lost in UDRP

Domain Name Wire - Wed, 11/08/2017 - 15:59

Bad decision in a three-letter .com UDRP.

I just wrote about PCO.com being saved in a UDRP despite the domain name owner not responding. This was before I saw a similar case in which a three-letter domain name was lost in a UDRP.

National Arbitration Forum panelist Neil Anthony Brown QC has ordered the domain name IMI.com transferred to Irving Materials, Inc.

Brown generally provides a nuanced and well-reasoned opinion in UDRPs, and I’m surprised by the result here.

To be fair, the domain owner didn’t respond. Still, a quick look at the facts of the case strongly suggest this was not cybersquatting and the domain was not registered in bad faith.

It appears the current owner is the original registrant from 1994. Its business was originally called Internet Marketing, Inc., hence the domain name choice IMI.com. It subsequently moved its business to PartnerVision.org.

IMI.com resolves to a page headlined “Internet Marketing Inc a PartnerVision venture”. It says the company has changed domain names and then says “Searching for other IMI Companies, try these:” followed by a list of other companies that use the IMI acronym. These links are clearly not paid links, despite the complainant arguing that they are pay-per-click links leading to companies that compete with the complainant.

The complainant latches on to a page on the site that says the domain names are for sale. It states:

PartnerVision Ventures is winding down IMI’s liquidation sale. All of the company’s patents and other intellectual property are now gone. The only assets left within the company are it’s popular domain names (www.IMI.com) and (www.IMI.info).

With brand identity coming at a premium these days, you can image what the value of such a name will bring. If you are interested in purchasing this domain, please contact us.

Note: Offers less than two million dollars will not be considered.

Selling domain names you used for your company is a perfectly legitimate activity.

Again, it didn’t help that the domain owner didn’t show up to defend its property. My guess is the owner isnt’ even aware of the complaint. Still, the panelist in this case is well aware of the differences between pay-per-click and other links and also understands the value of domain names. I’m shocked by the decision. It’s this type of decision that gives companies the hope of getting valuable domains through UDRPs, creating a sort of vicious cycle.

Hopefully the owner will fight this decision.


© 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.

The post Valuable IMI.com domain name lost in UDRP appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

PCO.com saved in UDRP despite no-show by domain owner

Domain Name Wire - Wed, 11/08/2017 - 15:41

PCO.com owner doesn’t defend its property but panel makes the right decision.

A World Intellectual Property Organization panel has denied a UDRP cybersquatting complaint brought by PCO AG of Kelheim, Germany against the domain name PCO.com. Panelist Adam Taylor made the correct decision even though the owner of PCO.com did not respond to the complaint.

PCO AG argued that the acronym PCO was unique to its business, standing for “Pioneer in Cameras and Opto-electronics”.

But Taylor noted that “…the term “PCO” is far from uniquely-identified with the Complainant. And the Complainant has overstated its case when it claims that there is no conceivable good faith use to which the disputed domain name could be put.”

The domain name does not resolve. Had it resolved to a parked page with ads related to the complainant, this case could have turned out differently.

You can read Taylor’s full reasoning 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.

The post PCO.com saved in UDRP despite no-show by domain owner appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Facebook says real estate firm is cybersquatting on 30 domain names
  2. True Religion jeans company sues over TrueReligion.com domain name
  3. Another Gleissner company loses a UDRP, this one to Qualcomm
Categories: Domains

GoDaddy paid $50 million for two latest domain portfolio acquisitions

Domain Name Wire - Wed, 11/08/2017 - 14:24

Company picked up about 300,000 domain names for $50 million.

Last month GoDaddy (NYSE:GDDY) bought two domain name portfolios: Donuts’ portfolio of about 200,000 domains and a portfolio linked to Kevin Ham that had about 100,000 domain names.

The company disclosed in its latest 10-Q filing with the SEC that it paid $50 million combined for these domains:

In October 2017, we completed two domain portfolio acquisitions for aggregate cash consideration of $50.0 million, including $4.2 million payable upon expiration of the contractual holdback periods.

That comes out to about $167 per domain name.

The filing does not break down how much was paid for each portfolio, nor do I expect any future filings to contain this information.

For comparison purposes, the company paid $35.5 million for Michael Berkens’ portfolio.


© 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.

The post GoDaddy paid $50 million for two latest domain portfolio acquisitions appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. GoDaddy acquires Marchex’s domain name portfolio for $28 million
  2. Major shakeup: Tucows sending expired domain names to GoDaddy Auctions
  3. Shills, Insiders, & Front Runners – 5 Bidding Scandals
Categories: Domains

AXA uses its dot-brand domain name and blockchain for new insurance product

Domain Name Wire - Tue, 11/07/2017 - 19:59

Fizzy launched on fizzy.axa a couple months ago.

This September insurance company AXA introduced a new test insurance product called Fizzy. The company launched it on its own .brand domain, Fizzy.axa.

Launching the test product on a dot-brand domain name means the company didn’t have to invest in buying an existing domain name. However, if Fizzy takes off the company might need to change names or pay more to acquire the matching domain. Fizzy.com is currently used by a game company.

Adding to the interest: Fizzy is based on the Ethereum blockchain. Insurance purchases are recorded on the blockchain so they are tamperproof. Payments are automatically made whenever a contract should pay off; in this case, if a flight is 2+ hours late.

AXA notes that the product can be trusted because the decision mechanism has been delegated to an independent, tamper-proof network. I think this would be a selling point for smaller insurers but I’m not sure how important this is for a company of AXA’s size.

Using a .brand domain to spin up a test idea can make a lot of sense, but companies also need to consider if they will want to change the domain name and brand if the product advances beyond a test.


© 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.

The post AXA uses its dot-brand domain name and blockchain for new insurance product appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Is Amazon.com the biggest user of new domain names?
  2. Famous Four Speaks: cheap domains, brand protection and more
  3. The languages of new top level domains
Categories: Domains

This was a perfect opportunity to use a domain name forward

Domain Name Wire - Tue, 11/07/2017 - 17:27

Typing in a YouTube video address is not fun. Use a domain forward instead.

The Economist magazine often includes ads promoting luxury real estate. This week there’s a full page ad for Chateau Pompadour De Menars in France. This 130,000 square foot property has 62 bedrooms (each with their own bathroom) on 35 acres. The seller is seeking offers until January 15.

Take a look at the ad:

The main calls to action are to view a YouTube video and send an email.

That’s a lengthy and complicated URL to a YouTube video. I know because I messed up four times trying to type it in my browser. This would be a perfect opportunity to use a descriptive domain as a forward, whether it’s a .com domain or a new TLD such as .video, .house or .luxury. It would also be nice to have a professional email address rather than a gmail account.

To be fair, I don’t think the seller is going to lose out on offers because of this lack of professionalism and ease of viewing the video. Someone who actually has the money required to acquire this property who is intrigued by the ad will go through the hassle to learn more. Still, a little professionalism goes a long way.

I’ll make it easy to view the video by embedding it in this post.


© 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.

The post This was a perfect opportunity to use a domain name forward appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

GoDaddy reports earnings and domain revenue growth

Domain Name Wire - Tue, 11/07/2017 - 14:33

Domain name business keeps growing.

GoDaddy (NYSE:GDDY) reported earnings after the bell yesterday.

Total revenue for Q3 was $582.2, up 24% year-over-year. That represents growth of about 12% if you exclude the additional revenue from acquiring Host Europe Group.

The domain name business contributed $271.5 million and the company says most of the 15% year-over-year growth was organic. For comparison, the domains business line contributed $263 million of revenue in Q2 of this year. GoDaddy now has about 73 million domain names under management.

The company did not disclose details of either of its two domain portfolio purchases this year in its press release, presentation and conference call. Both of these purchases took place subsequent to the end of Q3. I’m hopeful that a high-level number will be disclosed in the company’s 10-Q filing with the SEC.


© 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.

The post GoDaddy reports earnings and domain revenue growth appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. GoDaddy is buying NamesCon
  2. GoDaddy (GDDY) reports earnings, domain revenue of $263.3 million
  3. GoDaddy releases earnings, picks GDDY ticker
Categories: Domains

CentralNic sells $3.4 million of domain names

Domain Name Wire - Tue, 11/07/2017 - 14:20

Company comes through on its promise to bolster numbers by selling domain name inventory.

CentralNic (London AIM:CNIC) has sold $3.4 million of domain names from its domain inventory, the company revealed today.

The deal doesn’t come as a big surprise. The company sold £3.555 million of domain names to one buyer in the second half of last year. It needed to repeat this performance in 2017 to keep its revenue numbers in line with market expectations.

When the company reported its first half results in September it noted that it expected premium domain sales to “contribute significantly to profits in the second half.” Without more premium domain sales its revenue numbers would decline from last year.

While this worked for 2017, the question remains: what happens when the company runs out of valuable .com domain names to sell?


© 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.

The post CentralNic sells $3.4 million of domain names appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. CentralNic reports earnings, numbers decline from last half
  2. CentralNic closes $4.5 million domain portfolio sale
  3. CentralNic acquires .SK operator for €26 million
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.