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.

Intuit missed TurboTaxSucksAss.com

Domain Name Wire - Wed, 07/01/2020 - 17:03

Companies can’t register all domains that can be used to attack them.

Patriot Act’s website calls attention to tax prep software company efforts to hide their free options.

Last year, Intuit registered lots of domain names defensively as reports surfaced about its nefarious tactics with TurboTax. It had lobbied the government not to make its own tax filing software by offering to provide a free option. Then it hid its free option, including blocking it from being indexed by Google.

Intuit registered domains like f*ckintuit.com, turbotaxscam.com, and intuitexposed.com to prevent people from using the domains to attack it.

I’ve long argued that these defensive registration exercises are futile. The choices are endless if someone wants to register a derogatory term with a brand in it. Here’s a case in point: Intuit missed TurboTaxSucksAss.com.

Patriot Act with Hasan Minhaj created a website using the domain. It calls attention to the free file options that tax prep companies try to hide.

You can watch the episode covering TurboTax below.

Post link: Intuit missed TurboTaxSucksAss.com

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. F**K Intuit, says Intuit
Categories: Domains

Here are the domains Amazon registered for the Seattle arena

Domain Name Wire - Wed, 07/01/2020 - 14:27

Amazon registered over 75 domains for the arena it’s calling Climate Pledge Arena.

Photo courtesy Amazon.

I can’t wait to watch a live hockey game again. It certainly won’t be until next year, and it’s likely to be in Seattle’s completely refurbished arena.

Last week, Amazon announced that it bought naming rights to the arena where Seattle’s NHL team will begin play in 2021. Instead of calling it the Amazon Arena, it named it the Climate Pledge Arena.

Some might call it greenwashing, but the name will certainly keep Amazon under the microscope when it comes to its environmental impact.

Amazon.com registered over 75 domain names in conjunction with the naming. Most of these are for defensive purposes. The list is below:

amazon-cparena.com
amazonarena.net
amazonarena.org
amazonautonomouscars.com
amazonbasketballarena.com
amazonbasketballcourt.com
amazoncarbonzeorarena.com
amazoncarbonzero.com
amazonclimatearena.com
amazonclimatepledgearena.com
amazoncparena.com
amazonhockeyarena.com
amazonhockeyrink.com
amazonridehailing.com
amazonridehailingvehicles.com
amazonrink.com
amazonsclimatearena.com
amazonsclimatepledgearena.com
amazonseattlesportsarena.com
amazonsportsarena.com
amazonzerocarbon.com
amazonzerocarbonarena.com
aws-arena.com
awssportsarena.com
climatepledgearena.net
climatepledgearena.org
climatepledgebasketballcourt.com
climatepledgebasketeballarena.com
climatepledgecarbonzeroarena.com
climatepledgecourt.com
climatepledgehockeyarena.com
climatepledgehockeyrink.com
climatepledgerink.com
climatepledgesportsarena.com
climatepledgestadium.com
climatepledgezerocarbonarena.com
codingtoolkit.com
countdown-to-carbonzero.com
countdown-to-netzero.com
countdowntocarbonzero.com
countdowntonetzero.com
cp-arena.com
cparena.com
join-lead-change.com
joinleadchange.com
seattle-cparena.com
seattleclimatepledgearena.com
seattlecparena.com
the-amazon-arena.com
the-aws-arena.com
theamazonarena.net
theamazonarena.org
theamazonbasketballarena.com
theamazonbasketballcourt.com
theamazonclimatepledgearena.com
theamazoncourt.com
theamazonhockeyarena.com
theamazonhockeyrink.com
theamazonrink.com
theamazonsportsarena.com
theawsarena.com
theawsportsarena.com
theclimatepledgearena.net
theclimatepledgearena.org
theclimatepledgebasketballarena.com
theclimatepledgebasketballcourt.com
theclimatepledgecourt.com
theclimatepledgehockeyarena.com
theclimatepledgehockeyrink.com
theclimatepledgerink.com
theclimatepledgesportsarena.com
theclimatepledgestadium.com
theseattleclimatepledgearena.com
climatepledgearena.us
theamazonarena.us
theclimatepledgearena.us

 

Post link: Here are the domains Amazon registered for the Seattle arena

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

Is this domain really worth $30,728?

Domain Name Wire - Wed, 07/01/2020 - 13:37

Kassey Lee explains why this domain, which sold at auction last month, has a bounty of potential buyers.

HuangGuan.com sold for $30,728 on Godaddy Auctions on June 15, and I think it is a good deal for the buyer. Here’s why:

  1. Huang Guan represents a prestigious brand: 皇冠 (crown). A prestigious brand can be worth billions of dollars, so its matching .com will be priceless.
  2. The domain is short, with only nine letters in the name, which appeals to Chinese companies because “short” is loved. Remember the craze for 2-letter domains?
  3. It’s 2-pin, which is the most popular type among Pinyin names. You see 2-pin names everywhere in China, for example Bai Du (Baidu.com), Jing Dong (JD.com), and Mei Tuan (Meituan.com).
  4. There are many potential buyers for this domain. Baidu’s corporate credit database lists more than 100 Chinese companies using “皇冠 (crown)” in their names. Similar results can be found in Crunchbase and Baidu URL search.
  5. Huang Guan has multiple meanings. In addition to “皇冠 (crown)”, Huang Guan has other meanings, too, thus allowing you to create other brands. Some examples are 煌观 (brilliant view), 凰冠 (phoenix hat), and 黄馆 (yellow building).

How much can HuangGuan.com be sold to a Chinese company? When it comes to end user pricing, there is no fixed rule. It depends on the desire and also affordability of the buyer, which is illustrated in the stunning $30 million sale of Voice.com to Hong Kong-based blockchain startup Block.One in 2019.

Post link: Is this domain really worth $30,728?

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

State Farm tries (again) to get a State Farm Bowl domain

Domain Name Wire - Tue, 06/30/2020 - 18:52

The insurance giant really wants this domain name.

Earlier this year, insurance giant State Farm lost a UDRP for the domain name TheStateFarmBowl .com.

The owner of the domain argued that he bought it to sell wooden bowls in the outline of states. Get it? State ‘farm bowls’? (His plans seem to have been delayed because he still hasn’t developed the site.)

This loss came on the heels of losing a similar case for the domain BigStateFarmAgent .com because it could be read is ‘big state’ ‘farm agent’.

State Farm was miffed at losing the seemingly football-themed TheStateFarmBowl .com domain to go along with its defensively-registered StateFarmBowl.com. So it filed a second time with National Arbitration Forum to get the domain.

There are limited cases in which a company can file a UDRP a second time. According to the WIPO Jurisprudential Overview 3.0:

Panels have accepted refiled complaints only in highly limited circumstances such as (i) when the complainant establishes that legally relevant developments have occurred since the original UDRP decision, (ii) a breach of natural justice or of due process has objectively occurred, (iii) where serious misconduct in the original case (such as perjured evidence) that influenced the outcome is subsequently identified, (iv) where new material evidence that was reasonably unavailable to the complainant during the original case is presented, or (v) where the case has previously been decided (including termination orders) expressly on a “without prejudice” basis.

For example, had the owner of the domain started selling insurance, then State Farm might have a legitimate reason to refile. But none of the exceptional circumstances applied here, so the panelist declined to render a new decision.

Post link: State Farm tries (again) to get a State Farm Bowl domain

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Sony picks up Walkman.net. But will it do anything with it?
  2. Domainers Will Love This UDRP Decision
  3. Can this one simple step save you in a UDRP?
Categories: Domains

Supreme Court: Booking.com can get its trademark

Domain Name Wire - Tue, 06/30/2020 - 15:25

Court rules that Booking.com can be trademarked.

The Supreme Court of the United States issues its ruling about a trademark for Booking.com.

In an 8-1 ruling, the Supreme Court of the United States ruled today that Booking.com can trademark Booking.com.

For background on the issue, listen to DNW Podcast #285.

Booking.com sought the trademark, only to be rebuffed by the U.S. Patent and Trademark Office, which argued that it’s generic. The USPTO argues that adding .com to a generic term—like adding “Company”—can convey no source-identifying meaning.

The Supreme Court disagreed, writing:

That premise is faulty, for only one entity can occupy a particular Internet domain name at a time, so a “generic.com” term could convey to consumers an association with a particular website.

Furthermore:

Under these principles, whether “Booking.com” is generic turns on whether that term, taken as a whole, signifies to consumers the class of online hotel-reservation services. Thus, if “Booking.com” were generic, we might expect consumers to understand Travelocity—another such service—to be a “Booking.com.” We might similarly expect that a consumer, searching for a trusted source of online hotel-reservation services, could ask a frequent traveler to name her favorite “Booking.com” provider.

So under limited circumstances, companies can trademark a generic term + .com (or perhaps another top level domain).

But that trademark won’t grant the company protection of the generic term of the second-level domain. Booking.com acknowledged that the Booking.com mark would be weak. It will also not allow it successfully go after anyone who uses the generic term ‘booking’ in their mark.

The court wrote:

Guarding against the anticompetitive effects the PTO identifies, several doctrines ensure that registration of “Booking.com” would not yield its holder a monopoly on the term “booking.”

In fact, Booking.com said it would not go after companies such as ebooking.com, or others that use the term in their name or domain name. It seems that the protection this trademark will provide is against someone, say, promoting themselves as booking.com on their website or naming their hotel Booking.com.

The full decision is here (pdf).

Post link: Supreme Court: Booking.com can get its trademark

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

Spa services company tries reverse domain name hijacking

Domain Name Wire - Tue, 06/30/2020 - 14:27

Domain was registered a decade before the spa company started its business.

A spa franchising company has been found to have engaged in reverse domain name hijacking for the domain AccessSpa.com.

Philip Savino, who apparently has some connection to a spa franchiser called Access Spa, filed the dispute with World Intellectual Property Organization.

The owner of the domain name registered it in 2009. Access Spa was created last year, according to the dispute.

It’s impossible that the domain registrant could know that a company was going to use the brand starting ten years later. Therefore, the domain wasn’t registered in bad faith under the Uniform Domain Name Dispute Resolution Policy.

Panelist Warwick Rothnie wrote:

…the long period of several years between the registration of the disputed domain name and subsequent commencement of use of the trademark by the Complainant (and even longer period before registration of the Trademark) should have made it very clear that the Complaint could not succeed. On the record in this case, the Complaint should never have been filed.

Post link: Spa services company tries reverse domain name hijacking

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Timbermate Products guilty of reverse domain name hijacking
  2. Another day that ends in Y, another reverse domain name hijacking
  3. Media Bridge ad agency attempts reverse domain name hijacking
Categories: Domains

A quick expired domains tip for finding valuable domains

Domain Name Wire - Tue, 06/30/2020 - 13:20

Kassey Lee explains how you can find expiring domains that may be valuable both in China and the rest of the world.

Even though I live outside China, I still want to include China in my domain investment strategy. This is because I have seen the spectacular rise of the Chinese economy and I want to ride this tidal wave of opportunity.

I know some investors acquire numeric or Pinyin domains in order to target the China market. However, I don’t want to take this route because it limits me to selling to one country; I want to cover the entire world.

In my extensive reading and research, I have found a way to help me target both China and the rest of the world. This can be done by acquiring domains meeting the following three requirements: (1) English, (2) .com, (3) .cn developed.

An English .com domain enables me to sell it to the entire world while its .cn aspect indicates the name has potential in China. Here is how I implement the idea.

Every day, I analyze over 10,000 domains provided by ExpiredDomains.net. To facilitate my work, I have set up a number of filters. If I want to include China in a filter, I turn on the following settings in ExpiredDomains.net.

Section Setting Dictionary Word Domains English Original gTLDs com Name in selected TLD is registered cn

This filter will give me a list of English .com domains with the matching .cn registered. I still need to visit the .cn to determine if it is already developed and by an end user.

By using this method, you can acquire domains that can be sold to both China as well as the rest of the world. Make sure to use a service such as Afternic fast transfer to list the domains so that they are also available in China for easy purchase by the local buyers.

Post link: A quick expired domains tip for finding valuable domains

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. How Long Until China Confiscates Google.Cn Domain Name?
  2. A four character domain for $16,500? Here’s why
  3. Single letter domains in China
Categories: Domains

Reviewing 4-character domains sold in May

Domain Name Wire - Mon, 06/29/2020 - 16:43

Do these four-character domains have upgrade value?

I look at domains from the Chinese perspective because of my background. In this article, therefore, I’ll review some 4-character domains sold in May and also check their corresponding .cn and .com.cn usage.

ZZ88.com sold for $13,750. ZZ88.com.cn is an info portal, covering areas such as recruiting, house rental/sale, and dating. However, most entries are dated. The domain only partially matches the site title, where ZZ stands for Zheng Zhou (郑州). Because of this, an upgrade to ZZ88.com is not very likely. Instead, ZZXX.com would be a better choice.

L0VE.com sold for $3,500. Be careful and note that it is “0” (zero) not “O” (letter O) in the domain. L0VE .com.cn forwards to FD7999 .com which is a simple lottery site. So, an upgrade to L0VE.com is not very likely.

111V.com sold for $3,433. The domain already has a for-sale page with a BIN price of 28,880 yuan or about $4080. However, I don’t see much profit in flipping this domain at the stated price.

MG99.com sold for $2,999. MG99.com .cn forwards to 1081223 .com which has a couple of links to casino sites. So, an upgrade to MG99.com is not very likely.

FH38 .com sold for $1,003. FH38 .com has been developed into a lottery site. The domain only partially matches the site title, where FH stands for Feng Huang (凤凰=phoenix). 38 is a good number because 3 suggests “alive” and 8 is “making a fortune”. However, the site title does not seem to have anything to do with the number. FHCP.com would have been a better choice.

LAB8.com sold for $711. LAB8.cn is a portal of mobile games that can be downloaded. The domain does not match the site title, so an upgrade to LAB8.com is not very likely. Instead, Labi.com or LBSY.com would be better choices.

ZT77.com sold for $703. It already has a for-sale page with a BIN price of 18,880 yuan or $2670.

CA66.com sold for $665. CA66.cn is a simple page with links to other sites such as 中国月饼.公司 (meaning “Chinese moon cake” on IDN extension .company) and 中国浏览.中国 (meaning “China browsing” on IDN extension .china). The domain does not match the site title, so an upgrade to CA66.com is not very likely. Instead, ZGLL.com would be a better choice.

As you can see, most of these purchases do not have a likely upgrade to the existing users of the domains using .cn and .com.cn extensions.

Post link: Reviewing 4-character domains sold in May

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Reviewing 4-character domains sold in January
  2. How to sell domains to China
  3. Three steps to Chinese end user research
Categories: Domains

Are these domains unstoppable? – DNW Podcast #292

Domain Name Wire - Mon, 06/29/2020 - 15:30

Checking in on blockchain domains one year later

Last year I interviewed one of the co-founders of Unstoppable Domains. I’m checking in with another co-founder this week, Brad Kam, to see how it’s going. The company offers blockchain-based domains such as .crypto that it says can’t be censored. We discuss the challenges of operating domains on an alternate root, if offering uncensorable domains has a downside, and compare the domain to blockchain alternatives.

Also: Layoffs at GoDaddy, a record-breaking .ai sale, TrueName and more.

Sponsor: DAN.com

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

Post link: Are these domains unstoppable? – DNW Podcast #292

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Domain name due diligence – DNW Podcast #148
  2. Soeren von Varchmin – DNW Podcast #165
  3. One Word Domains – DNW Podcast #287
Categories: Domains

How to Search GoDaddy Domain Auctions using the “old” API

Domain Name Wire - Mon, 06/29/2020 - 14:38

Alvin Brown provides a tutorial on how to use the GdAuctionsBiddingWS_v2 api to search and retrieve domain names listed on GoDaddy Aftermarket by keyword.

Today’s tutorial is a bit tricky. Why? Well, you’ll need to have access to GoDaddy’s old API: GdAuctionsBiddingWS_v2.

You’re likely not familiar with this API by name, yet if you’ve been around domain investing long enough, then you’ve likely experienced or heard of auction bots and auction bot sniping.

Yeah, I know, I know… This tutorial likely stirs the pot a bit for those who do not have access to the api. That’s not the intention of this tutorial.  Nevertheless, for those that do have access and would like to make use of the API, well, this tutorial is for you.

But no worries for those of you who don’t have access to the original API, I’ve kindly provided a few tutorials for GoDaddy’s most recent API. Read more on how to get started using GoDaddy’s more recent API.

For today’s tutorial, the GdAuctionsBiddingWS_v2 API offers nearly 20 different methods to interact with the GoDaddy Aftermarket, including but not limited to the following:

  • EstimateCloseoutDomainPrice
  • GetAuctionDetails
  • GetAuctionDetailsByDomainName
  • GetAuctionList
  • GetAuctionList2
  • GetAuctionListByAuctionType
  • GetAuctionListByAuctionType2
  • GetAuctionListByAuctionTypeAdultBidsCloseDays
  • GetAuctionListByAuctionTypeAdultBidsCloseDays2
  • GetAuctionListByAuctionTypeAdultFilter
  • GetAuctionListByAuctionTypeAdultFilter2
  • GetAuctionListByAuctionTypeAndDates
  • GetServiceStatus
  • GetTermsOfServiceUrls
  • InstantPurchaseCloseoutDomain
  • PlaceBlackorder
  • PlaceBid
  • PlaceBidOrPurchase
  • PlaceBidWithPurchaseProfile

Today’s tutorial focuses on the following two API methods: GetAuctionListByAuctionType and GetAuctionListByAuctionType2.

In short, both methods allow for searching the aftermarket based on a keyword, auction type, and search type.

The difference between the two is that the GetAuctionListByAuctionType includes beginsWithKeyword and auctionType, whereas GetAuctionListByAuctionType2 includes keyWord, auctionType, and searchType in addition to pageNumber and rowsPerPage used by both methods.

For the sake of time and providing an example script that can be downloaded, I won’t dive into the line-by-line details, but I will provide a high-level overview of the example code.

First things first, you must have access to the GdAuctionsBiddingWS_v2 API. If you don’t, then there is no reason to continue this tutorial. This is the mission-critical step of all.

And for the record, GoDaddy is not allowing or issuing access to anyone else.  However, if anyone does have the midas touch to in managing to gain access, then bottle and package up how you did it and sell it — an army of folks await!

As for the tutorial itself, the first thing to note about the example script, which implements the GetAuctionListByAuctionType2 method, is that the following variables and their respective string values must be defined:

  • pageNumber – value is set to the numeric value of 1.
  • rowPerPage – value can be set to one of the following: 15, 25, 50, 100, 200, 300, and 500.
  • keyword – value can be set to a desired keyword phrase contained in domain names, excluding spaces and special characters, minus hyphens.
  • auctionType – value be set to one of the following: auction or buy now.
  • searchType – value can be set to one of the following: most active, featured, expiring, ending soon, buy now, closeouts, bargainbin, and a-z listings.

The keyword ‘domain’ is used as the keyword variable value in this example, which returns a list of domains in auction containing the keyword ‘domain’.

One thing I was in the dark on are the actual values for auctionType and searchType variables. I cannot confirm those are the actual variables to be used, but guessed based on the values I discovered using Developer Tools to inspect the search elements on GoDaddy’s Aftermarket web page.

If anyone knows with certainty about these values, do feel free to chime in with comments in the comments section below.

Now that variables are defined with their respective values, the SOAP request and response can be made using the GetAuctionListByAuctionType2 method. While PHP provides a SOAP class nowadays to make the request, I’ve purposely chosen to use cURL and handcraft the SOAP header and body request (as shown below).

SOAP 1.2 Request

The above example SOAP is a 1.1 Request. If you’re using SOAP 1.2, then the following request can be used as a start point:

SOAP 1.2 Request

The aforementioned example requests, specifically the SOAP 1.1 body and header, are implemented in the example code.

One thing to note is that GoDaddy API credentials from the most recent API release is needed to authenticate the API request.

In the example code, be sure to replace the X’s in the line of ‘Authorization: sso-key XXXXXXXXXXXXXXX:XXXXXXXXXXXXXXX’ with the proper API credentials.

Once the API credentials are created, the API can be authenticated and request successfully made using the SOAP API WSDL url (see example code to obtain url).

Being well on our way to successfully making a SOAP request, the next thing to prepare for is the SOAP response and how to parse it — see the examples below:

SOAP 1.1 Response

SOAP 1.2 Response

The focal point of the SOAP response is the GetAuctionListByAuctionType2Result element, which contains a string of auction data (see example code below).

<Auction ID=”327387240″ Name=”ROCKETFLY.NET” Traffic=”3″ BidCount=”0″ Price=”$5 USD” ValuationPrice=”$418 USD” TimeLeft=”11H 7M ” RowID=”1″/>

For each domain returned, the aforementioned Auction element is return for each matching domain and contains the following attributes:

  • ID – auction ID
  • Name – the matching domain name
  • Traffic – supposed the number of times a domain is viewed
  • BidCount – the number of bids
  • Price – the current price of domain in auction
  • ValuationPrice – the GoDaddy GoValue or Estimated value of domain
  • TimeLeft – time remaining in auction
  • RowID – the record id or occurrence id of the domain

Again, not diving deep into the details, but to correctly parse the SOAP response, you’ll need to use the following PHP built-in functions: str_ireplace, htmlspecialchars, simplexml_load_string, json_encode, and json_decode.

In short, each aforementioned function helps to clean and transform the SOAP response into XML and into a workable PHP array to access the Auction element attribute data contain specific domain data.

If you load the file to a web server and view it via a web browser, then you should see a list of domain names likely containing the ‘domain’ keyword or keyword you set, if any domains are available for the defined keyword.

And that’s the tutorial folks!

Closing Thoughts

Of course, that’s not really the tutorial in its entirety. That’s just all we have time for today.

This tutorial could be extended in a number of ways. For example, one of the ways to extend this tutorial is adding the ability to parse and then store data in a database for analytics purposes — if you’re all about data-driven domain investing.

Now it’s worth mentioning that searching for domains can be easily completed using GoDaddy’s Saved Search functionality, including a daily email of your saved searches right to your inbox.

However, this type of search is only a snapshot for the time in which it is taken, whereas the API can be automated to run on the minute, hour, day, week, etc — year-round if you will.

Emails are forever locked in your inbox until you take action, unlike the exponential flexibility of scripting and automating against the API, which could operate with and without us — sleeping or awake, busy or bored.

If you have questions or comments about this tutorial, chime in below in the comments section.

Thanks and that’s all for now!

[ DOWNLOAD EXAMPLE SCRIPT ]

Post link: How to Search GoDaddy Domain Auctions using the “old” API

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. 3 Tips to Discover Expired Domains Available at Hand-Registration Fee
  2. Sedo and Pool Explain Employee Policies for Bidding
  3. EDR: A look at 150 expired domain name auctions from the past week
Categories: Domains

Reviewing recent 4-letter domain sales

Domain Name Wire - Fri, 06/26/2020 - 13:45

Kassey Lee investigates Chinese end users for these recent four-letter domain purchases.

Here are some 4-letter domains sold in May, viewed from the angle of finding end users in China for domain upgrades. Remember that I always check both .cn and .com.cn as both are popular in corporate China.

TTMJ.com sold for $7,000. TTMJ.com.cn is for sale and its owner has suggested the following Chinese meanings which I do like: Tian Tian Mei Ju (天天美剧=good theatrical work in play, opera, TV series, etc every day), Tian Tian Mei Ju (天天美居=good residence every day), and Tian Tian Ma Jiang (天天麻将=Majong every day). The domain can be used in a variety of business fields.

KRKR.com sold for $2,288. KRKR.cn seems to be a B2B business portal. The site claims to have daily visits by tens of thousands of companies to find business partners. Unfortunately, the domain does not match the site title (中国雾机网=Zhong Guo Wu Ji Wang). ZGWJ.com would be a better upgrade possibility.

MJCP.com sold for $1,712. It already has a sale page with a BIN price 58,880 yuan (about $8,300). The domain may have many Chinese meanings, such as Mei Jin Chao Piao (美金钞票=US bills), Mai Jin Che Piao (买进车票=buy bus/train ticket), and Meng Jing Cai Piao (梦境彩票=dreamland lottery ticket).

DXZB.com sold for $1,072. DXZB.cn is a site that provides funding to startups. The company name is CDX Partners so the domain does not match the brand. Because of this , an upgrade to DXZB.com is not very likely. CDX.com would be a better upgrade possibility.

SFST.com sold for $1,200. SFST.com.cn may be a video app or gaming platform but I could not see details of the home page likely due to geo-blocking.

WYFC.com sold for $1,200. WYFC.com.cn is a real estate legal site but the domain only partially matches the site title, where FC stands for Fang Chan (房产=real estate). Because of this, an upgrade to WYFC.com is not very likely. FCLS.com would be a better upgrade possibility.

CPJD.com sold for $1,055. CPJD .com.cn may be a lottery site but the domain only partially matches the site title, where CP stands for Cai Piao (彩票=lottery ticket).

Post link: Reviewing recent 4-letter domain sales

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Reviewing 4-letter domains sold in April
  2. Reviewing 4-character domains sold in April
  3. This four letter domain sold for a high price
Categories: Domains

20 end user domain name sales up to $108,000

Domain Name Wire - Thu, 06/25/2020 - 16:09

A pet food company, an artificial intelligence company, and a water filtration company bought domain names.

There were many good end user sales at Sedo this past week, including the Expert.ai sale I wrote about on Tuesday.

Here’s a list of some of the end user domain name sales from the past week. You can review previous end user sales lists here.

Expert.ai €95,000 (about $108,000) – Expert System SpA bought this domain. It uses the domain ExpertSystem.com.

JBCapital.com €15,000 – JB Capital Markets is an investment firm focused on international institutional investors and investment opportunities within Spanish markets. It forwards the domain to JBCM.com.

VAFO.com $13,500 – VAFO PRAHA is a privately-owned family company in the Czech Republic that produces and distributes premium pet food.

JetLuxe.com $12,500 – JetLuxe is a private jet charter company.

Nomadism.com $12,499 – The domain name forwards to design studio Mad/Studio. The domain might be for a client.

SplinterWorks.com $7,000 – Splinter Works Ltd A UK design company that produces sculpture-like pool slides, freestanding bathtubs that look like hammocks, and more. It currently uses Splinterworks.co.uk for its website.

HearingAidClinics.com $5,000 – This domain is used as a lead-gen site to connect users to hearing care providers in their area.

BHI.co $5,000 – Barrow, Hanley, Mewhinney & Strauss, LLC, is an investment firm in Dallas that is focused on institutional investors, mutual funds, etc. It currently uses BarrowHanley.com as its website.

Moodly.com $5,000 – Bosstab makes tablet kiosk stands and Point of Sale equipment for businesses. Moodly sounds like a good brand for one of those kiosks that asks how happy you are with the service.

Kahraba.com $4,900 – El Sewedy Industries Group bought this domain. It is an electrical manufacturing company based in Cairo, Egypt. Kahraba means Electrified in Arabic.

TalentCare.com $4,500 – Forwards to talentcare2020.wpengine.com, a site in development for a job services and recruiting firm.

Aquamor.com $4,500 – TST Water has changed its name to Aquamor. It provides water purification products and services.

Properly.net $3,500 – 3MD Solutions, LLC, a transportation and fleet management company in Illinois. I’m not sure what they will use the domain for.

ProESports.com $3,499 – Pro Esports Gaming is an online gaming site.

SanLuisPotosi.com $3,300 – COMMET, an international supplier of a wide range of non ferrous, precious and minor metals, metal residues, ores and concentrates, bought the domain. It is based in San Luis Potosi, Mexico.

TheArt.Net $2,700 – This is interesting. It forwards to an Instagram page selling original artworks, sculptures and prints under the name The Arts Net, Inc.

Zener.nl €2,640 – Zener provides installation and maintenance services for telecommunications and renewable energies.

DasLab .de €2,500 – This website will be used for Covid-19 testing. Das means ‘the’ in German.

SEOBase.com $2,000 – This domain was purchased by Apilayer GmbH, a German software company that develops a suite of APIs & cloud-based SaaS applications.

ThreeHouse.com $2,000 – This website is still in development with a logo, an “Opening soon” message and “Hotel Apartment Home”.

Post link: 20 end user domain name sales up to $108,000

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Two weeks of end user domain sales at Sedo
  2. These end users just bought domain names
  3. Kasperksy buys Unhackable.com (and other end user domain name sales)
Categories: Domains

2008 vs 2020: Analyzing domains in a global recession

Domain Name Wire - Thu, 06/25/2020 - 13:30

[Editor’s note: The world has entered into a recession for the first time since the great recession. The causes are very different, but one thing is certain: uncertainty. In this post, Bala GR, Head of Business Intelligence at Radix, evaluates what happened to domains during the last recession and what might happen this time.]

A lot has already been spoken about the strange turn of events that have kept the global economy on the hook this year. Sure, we expected a recession; it was a long time due. What we didn’t expect was a pandemic and a worldwide self-quarantine for months on end. A few years from now, we will be looking back at 2020 with awe and absurdity in equal measure.

Talking of looking back, this year opens up the perfect opportunity to examine the 2008 recession. After all, that’s our only benchmark in these uncertain times. While a decade has since passed, there are trends that could help us make a fair prediction of what lies ahead of us this time around.

Making sense of the past

For the new domains industry, this is the first-ever experience of an economic downturn. As far as we and our new-domains-registry friends are concerned, looking at the legacy domain trends immediately before and after 2008 can be quite suggestive at this point.

So, that’s exactly what we did. We looked at whatever relevant data we could find for years before and after 2008. Was it useful? To a large extent, yes.

 

Assumptions and Data Details:

  • Legacy gTLDs include .com, .net, .org, .info and .biz
    • New Registration data for .COM & .NET in ICANN Reports start from April 2007, hence data from 2003-2006 is estimated based on Blended Retention Ratios and Q1 2007 is based on Quarterly Ratios
    • New Registration data for .ORG & .BIZ in ICANN Reports start from January 2007, hence data from 2003-2006 is estimated based on Blended Retention RatiosAll data taken from ICANN Monthly Registry Reports (https://www.icann.org/resources/pages/registry-reports)

As detectable in the table above, from 2004 up to 2008, the DUMs were increasing by at least 20% YoY. However, in 2008, the YoY growth slowed down to 12%~, and further down to 6%~ YoY in 2009.

Assumptions and Data Details:

And as can be seen here as well, the first year renewals dipped to 45% in 2009, from a much higher average of ~58% in the previous years. This could be attributed to the overall market sentiment during that period, the quality of the names, and the general pressure on businesses.

What does it mean for us? Three words: Proceed with caution

Based on publicly available data, the domain industry, on the whole, has reported a surge in domain name registrations since February 2020. Legacy gTLDs’ new registrations have seen a 5%~ jump in March 2020 and 10%~ jump in April 2020 when compared to the average monthly registrations for 2019. (Refer to table below)

This is great news for our industry. In fact, we have seen a rise of 15-20% in registration volumes at Radix too. This is not limited to standard domain registrations; we saw a 22% increase in premium domain registrations as well and a 15% increase in premium domain revenue in March-May vs the previous 6 months.

While .online saw a 45% increase in premium registrations and a 38% increase in revenue, .store saw a 70% increase in premium registrations and a 93% increase in revenue. This is clearly an indication of the urgency across industries to go online with meaningful, brandable names.

It’s too early to celebrate, though. While we expect these registrations to be backed by meaningful usage, we have to take into consideration that this surge could be a result of knee-jerk, reactive reasons. So, obviously, we ought to be cautious when predicting the renewal rates for the next year.

However… and it’s a big however

We cannot ignore the fact that times are vastly different now when compared to 2008. The society is more dependent on the Internet today than ever before. And if that wasn’t enough, the pandemic has further accelerated the transition from offline to online for businesses across the board.

This is a unique situation for our industry. As more and more businesses, institutions, and even next-door services are going online and speedily evolving their technology usage, our industry stands to play a crucial role in this mix.

So, our guess is as good as yours when it comes to expecting the future. At Radix, we live and breathe data! And yet, at an interesting juncture like this, there isn’t any data that we can rely on 100%. For what it’s worth, we have looked at the past. As for the future, it seems to be hanging on that big “however” we spoke of above.

Post link: 2008 vs 2020: Analyzing domains in a global recession

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. A recession is coming
Categories: Domains

I’m struggling with this UDRP decision

Domain Name Wire - Wed, 06/24/2020 - 20:01

Is EveryFamily.org confusingly similar to Everytown?

I’m having a difficult time digesting a decision in a National Arbitration Forum UDRP.

Everytown for Gun Safety Action Fund, Inc. filed the dispute against the domain EveryFamily.org. The Complainant uses the domain EveryTown.org.

Let me note at the outset that:

1. I’m sympathetic to the Complainant’s cause
2. The domain owner didn’t bother to respond to the dispute
3. It’s possible that the domain owner isn’t legit or is trying to take advantage of the Complainant.

All of that said, I don’t see how you can argue that EveryFamily.org is confusingly similar to Everytown’s mark.

The Complainant says that the EveryFamily.org domain is being used to mislead people into donating to a different group. It claims that the Respondent copied photographs and text from the Everytown.org website.

I wasn’t able to find the copied text and photographs but it’s possible they’ve been removed.

The panelist, Nicholas J.T. Smith, determined that “every” is the dominant part of the Complainant’s mark. He compared it to a case in which the ADP WORKFORCE NOW mark was determined to be confusingly similar to workforce-now.com.

These seem like entirely different levels of confusing similarity.

Smith points to section 1.15 of the WIPO Overview of WIPO Panel Views on Selected UDRP Questions, Third Edition:

1.15 Is the content of the website associated with a domain name relevant in determining identity or confusing similarity?

The content of the website associated with the domain name is usually disregarded by panels when assessing confusing similarity under the first element.

In some instances, panels have however taken note of the content of the website associated with a domain name to confirm confusing similarity whereby it appears prima facie that the respondent seeks to target a trademark through the disputed domain name.

Such content will often also bear on assessment of the second and third elements, namely whether there may be legitimate co-existence or fair use, or an intent to create user confusion.

That’s a fair point.

I just don’t think you can argue that ‘Everytown’ and ‘EveryFamily’ are confusingly similar.

Smith ordered the domain name to be transferred.

Post link: I’m struggling with this UDRP decision

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Arbitrator Rains on Media Rain’s Parade
  2. UDRP panel gets AustinPain.com decision wrong
  3. Tambour Ltd filed complaint that was “bound to fail”
Categories: Domains

PIR calls for nominations for .Org Impact Awards

Domain Name Wire - Wed, 06/24/2020 - 17:36

10 organizations that use .org domains will take home a total of $85,000.

Public Interest Registry, the registry that manages .org domains, has opened nominations for its 2020 .Org Impact Awards.

This year’s awards are a bit different from last year. Due to Covid-19, the awards will be announced online in “The Ten Days of .ORG”, starting November 30, rather than at an awards gala.

There will also be an award for an organization combatting coronavirus.

The ten award categories include:

  • Combatting Coronavirus
  • Fighting Hunger and Poverty
  • Championing Equality, Equity, Inclusion
  • Promoting Education
  • Advancing Environmental Sustainability
  • Promoting A Safer Internet
  • Innovation Award
  • Outstanding Volunteer
  • .ORG Newcomer of The Year
  • .ORG of The Year

The .Org of the Year will win $30,000 and the coronavirus winner will get $15,000. The other eight winners will each pocket $5,000.

Organizations must use a .org domain name to qualify.

Nominations are open until September 4.

Post link: PIR calls for nominations for .Org Impact Awards

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. .Org wholesale price to increase to $8.25
  2. Jon Nevett named new CEO of PIR (.Org)
  3. My thoughts on .Org
Categories: Domains

GoDaddy plans layoffs and is closing Austin offices

Domain Name Wire - Wed, 06/24/2020 - 14:27

Company struggles with outbound sales and social media products.

GoDaddy’s (NYSE: GDDY) revenue is topping expectations, but the company is laying off employees and restructuring its business because Covid-19 is impacting part of its business.

The company expects Q2 revenue to top its previous $790 million guidance by approximately 1%.

The restructuring is due to significant challenges with outbound sales efforts and its GoDaddy Social product, which is facing severe headwinds as its customers remain closed or in crisis mode.

814 employees — about 10% of its workforce — will be impacted, but many of them will be offered new roles.

The biggest impact will be in Austin, where the company plans to close both offices. GoDaddy entered the city with its acquisition of Main Street Hub, a do-it-for-me social service. The Main Street product is a higher ticket item than GoDaddy’s self-service tools. GoDaddy makes social media posts on behalf of companies. Many of those small businesses are now closed or significantly cutting back expenses.

331 sales employees in GoDaddy social will be let go. Additionally, the company is reducing the size of its Social Fulfillment and Customer Success teams by 120 team members.

GoDaddy is also shifting its sales efforts to a single office in Gilbert, Arizona. This will impact 134 salespeople in Iowa, who will be offered relocation to Arizona. Some will be offered the opportunity to move into inbound sales in Iowa.

The company is offering a generous exit package to those leaving the company. They will no longer work effective today but will be paid through September 1. They will then get at least four weeks of severance, and people who have worked at GoDaddy for three years or more will get additional severance. GoDaddy will pay healthcare costs through the end of the year for the impacted employees.

GoDaddy is taking a $15 million pre-tax restructuring charge for the payment of severance and related benefit costs and has determined that certain lease assets with a book value of approximately $58 million are impaired.

Post link: GoDaddy plans layoffs and is closing Austin offices

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. GoDaddy sets IPO range, plans to raise $400M at up to $3B valuation
  2. Aman Bhutani NamesCon live blog
  3. Godaddy expects $25-$30 million revenue hit in Q2 due to Covid-19
Categories: Domains

Donuts’ TrueName service offers brand protection to registrants

Domain Name Wire - Wed, 06/24/2020 - 13:12

Donuts has announced TrueName, a registrant service that automatically blocks registrations of homographs of registered domains.

When a customer registers a Donuts TLD such as .guru, .money or .live, Donuts will block registrations of lookalike domain names that substitute letters or numbers with characters from Latin, Greek, and Cyrillic script tables for the purpose of malicious activity.

This is a clever way to add value to new top level domain names, providing registrants with an added brand protection benefit compared to registering non-Donuts domains. Other than technical implementation, it doesn’t cost Donuts anything to block these domains but it adds value to the end user at no additional cost.

Donuts tested TrueName marketing on its Name.com registrar and reported higher conversions and better metrics across the board. Presumably, other registrars would also see a lift by including branding/marketing related to the service. (See the image for an example of TrueName branding during checkout at Name.com.)

Post link: Donuts’ TrueName service offers brand protection to registrants

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Rightside Registry offers its own Domain Protected Marks List
  2. This week’s new TLDs: .WhosWho and 4 EAPs
  3. Donuts’ first new domain names are starting to drop…
Categories: Domains

Verisign gets domain search ranking patent

Domain Name Wire - Tue, 06/23/2020 - 19:37

Patent describes way to personalize domain search results.

The U.S. Patent and Trademark Office has granted patent number 10,693,837 (pdf) to Verisign (NASDAQ: VRSN) for System for and method of ranking domain names based on user properties.

The patent describes a way to use personal information about the registrant to personalize domain search results. From the patent:

Some embodiments provide novel approaches for ranking (e.g., sorting) domain names on a personalized basis. Such personalization may be specific to an individual user, such as a potential registrant. The domain names may be ranked according to a prediction of how interested the particular user might be in registering such names. Note that, because the rankings are personalized, two potential domain name registrants may be given different presentations/orderings of the same set of domain names.

In more detail, some embodiments employ machine learning techniques based on properties of the user, such as gender, hobbies, country of residence, etc., as well as properties of domain names, e.g., length, language, top-level domain, etc., as well as contextual properties, e.g., the potential forum of the sale. The rankings may take into account prior domain name purchasing behavior of individuals that are determined to be similar to the user. Such embodiments provide for more relevant names being more prominently presented to the potential registrant, thus increasing overall registrations for, e.g., a registrar.

I believe some registrars already do certain elements of this when presenting search results.

Verisign applied for the patent in 2017. The patent names Swapneel Sheth, Director of Research Engineering, and Andrew West, Principal Research Scientist, as inventors.

Post link: Verisign gets domain search ranking patent

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Verisign gets IDN suggestion patent
  2. Verisign jumps in on .Web dispute, here’s what it could mean
  3. Verisign tries to discredit ICANN commenting period process
Categories: Domains

Expert.ai domain sells for record €95,000

Domain Name Wire - Tue, 06/23/2020 - 15:35

.Ai has a new record-holder.

Sedo has brokered the sale of Expert.ai for €95,000 (about $108,000), a record for a publicly-disclosed .ai domain name sale.

According to Whois records, the Italian firm Expert System SpA bought the domain name. Expert System is a publicly-traded artificial intelligence company that uses the domain name ExpertSystem.com.

.Ai is the country code domain name for Anguilla but has been adopted for use by many artificial intelligence companies.

According to NameBio, the previous high water mark for a .ai domain name was Music.ai, which sold for $101,500 in 2018. The next highest publicly-disclosed sale was Analytics.ai for $50,000 in 2019.

 

Post link: Expert.ai domain sells for record €95,000

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Revolution.org Sells for $120,000
  2. Moviles.net Domain Name Sells for $35,000
  3. 20 end user domain sales from the past week
Categories: Domains

Michael Rodenbaugh sues UDRPSearch owner David Lahoti

Domain Name Wire - Mon, 06/22/2020 - 17:14

Attorney sues after UDRPSearch owner forwards website to other site with derogatory comments.

Attorney Michael Rodenbaugh has filed a lawsuit (pdf) against David Lahoti, owner of the UDRP search site UDRPSearch.com.

For the past few weeks, Lahoti has forwarded UDRPSearch.com to websites with unfavorable comments about Rodenbaugh and another attorney, David Weslow.

Currently, UDRPSearch.com forwards to mikerodenbaugh .com with a message questioning his billing of meeting room costs and calling him a “fraudster”.

According to the lawsuit, Rodenbaugh represented Lahoti in previous legal matters but not since 2015.

Rodenbaugh’s lawsuit claims ACPA cyberpiracy, cybersquatting, defamation, and unfair competition.

The suit also names Lahoti’s company VirtualPoint and one of Lahoti’s brothers, Ravi. I don’t believe Ravi is involved in David’s businesses. In fact, the brothers seem to have had a falling out.

Post link: Michael Rodenbaugh sues UDRPSearch owner David Lahoti

© DomainNameWire.com 2020. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Certipost Pays to Settle Domain Dispute
  2. UDRPSearch owner sues after UDRP filed against one of his domains
  3. Parties agree to overturn UDRP decision and transfer domain for $40,000
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.