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.

15 end user domain sales, including to a $49 billion company

Domain Name Wire - Wed, 01/06/2021 - 16:51

Waste Management was among the companies buying domains at Sedo recently.

Sedo released its latest sales report yesterday covering the two-week holiday period. The top sale was Limit.com for $120,000 but it wasn’t an end user sale. Brent Oxley, founder of HostGator and now a domain investor and internet entrepreneur, bought the domain.

The top end user sale I could find had a big buyer behind it. Here are the end user sales (you can view previous lists like this here):

MyWM.com $15,888 – Waste Management, the $49 billion market cap resources and waste company, bought this domain.

AlphaPeople.com $5,950 – Forwards to AlfaPeople.com, an IT service provider that does implementations and supports Microsoft Dynamics 365 business technology. In other words, this is a typo domain to the buyer.

Volten.com €5,800 – Stylish Eve, Inc. is a hair care accessories company. I’m not sure what this purchase is for.

Ansahl.de €4,500 – Ansahl Consulting is a German “green” nutrition and diet consultancy.

MonAlimentation.com €3,980 – This domain was purchased by the Dairy Farmers of Canada. It’s French for “my diet”.

Viomi.de $3,960 – Forwards to IPOS-Gruppe.de. IPOS is a German conglomerate of several companies including a medical supplies distributor, a steel and building material supplier, a temporary employment agency, a training program for construction professionals, and a trucking logistics firm.

Fairclough.net $3,000 – Whois shows the buyer is Fairclough & Co in Great Britain. A Google search leads to a chartered building surveyor company.

ATL.ch €2,990 – ATL Global Holding is a Zurich-based consultant group aimed at building sustainable connections between leading tech companies.

SmarterBot.com $2,600 – This has a coming soon sign posted that says, “Coming soon: Next generation business automation with SmarterBot”.

MGNFY.com $2,595 – Swinque UG bought this domain. It’s a German full-service artist management, booking and consulting agency. This seems to be short for Magnify. If so, they got a discount for not paying for vowels.

PureContent.de €2,500 – A digital agency specializing in AI-based content for web projects, social media activity, press releases and more.

EuroGarden.eu €2,499 – EuroGarden is a Slovenian gardening and landscaping products retailer.

Logos.se €2,000 – Forwards to Logos.dk, the Danish website for the newly merged Logos and NPS companies, now called Logos Payment Solutions.

InfinityBook.com $2,000 – Forwards to the customer login page for Tuxedo Computers. Tuxedo Computers previously bought Slimbook.com through Sedo.

K2Air.com $2,000 – K2AIR bought this domain name. Its an HVAC service provider seeking to improve the indoor air quality of commercial and federal buildings by upgrading existing HVAC systems in order to eliminate airborne particulates, odors, and pathogens. This is pitched as fighting against the spread of Covid-19.

Post link: 15 end user domain sales, including to a $49 billion company

© DomainNameWire.com 2021. 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. End user domain name sales up to $90,000
  2. A dozen end user domain name sales
  3. 11 end user sales up to $160K
Categories: Domains

Pandemic relief bill to nudge governments to .Gov

Domain Name Wire - Wed, 01/06/2021 - 13:55

DOTGOV Online Trust in Government Act will help local governments transition to .Gov.

The pandemic relief bill that outgoing U.S. President Donald Trump recently signed could lead to more domain names ending in .gov.

Government Technology reports that the bill included the DOTGOV Online Trust in Government Act. The act is designed to get more governments in the U.S. to use .gov domain names.

While adoption of .gov is high at both state and federal agencies, local governments often choose .com or other extensions.

.Gov domain names are trickier for fraudsters to get (though not impossible), meaning that there’s a bit more faith that a .gov website is legitimate.

The act will move responsibility for .gov from the General Services Administration to the Department of Homeland Security’s Cybersecurity and Infrastructure Security Agency (CISA). It also mandates CISA to do an outreach program. CISA might be able to waive the $400 registration fees for the domains, too, which is an impediment to getting local governments to choose the domain over a $10 .com web address.

It will be interesting to see if this push also impacts .us, which some states use. For example, all agencies in Texas other than the Department of Motor Vehicles use addresses ending in state.tx.us.

 

Post link: Pandemic relief bill to nudge governments to .Gov

© DomainNameWire.com 2021. 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. Interesting rationale for a city changing its domain name
Categories: Domains

Domain Name Wholesale Exchange switches to subscription model

Domain Name Wire - Tue, 01/05/2021 - 20:01

Domain investor marketplace will charge monthly fee instead of commissions.

Domain Name Wholesale Exchange (DNWE), a marketplace for domainer-to-domainer wholesale transactions, is changing its business model.

The platform is scrapping commissions in favor of a subscription model. Users will pay a $14.99 per month (or $149 per year) fee to use the system, with early bird pricing of $9.99 per month (or $99 per year). The new model will begin on January 10.

Sellers will no longer pay a 12% commissions on sales. Buyers will pay DAN.com’s 5% escrow and transaction fee when they buy domains.

DNWE is also introducing a non-curated section that will allow users to list domains for sale without passing DNWE’s litmus test for quality/price.

Additional features in the works include customizable email notifications for buyers (e.g., new one word listings, crypto names, aged names, etc.), CSV exports, a purchased/sold section, data improvements and a make offer system.

Josh Reason, who launched the platform last year, told Domain Name Wire that the platform did $60,000 in volume with 61 domains last month. (One of those was an expensive three-character domain, so the typical transaction price is lower.)

Running the math, that would generate a net $4,200 to the platform during the month. I expect the platform will initially generate less on a monthly recurring revenue basis.

Still, the new model will allow the platform to generate stable revenue without worrying about people trying to cut DNWE out of the process to save on commissions.

It’s a somewhat unique model for sales platforms. Efty was the first sales platform I’m aware of that offered its service on a subscription model rather than commission.

“By offering a zero commission solution, we expect DNWE to see an increase in high-end inventory as a result of the huge savings on commission fees,” Reason said. “With our qualified pool of buyers and seamless buying experience through our partnership with DAN.com, I believe there is no better place to sell your domains.”

 

Post link: Domain Name Wholesale Exchange switches to subscription model

© DomainNameWire.com 2021. 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. Donuts’ first new domain names are starting to drop…
  2. Escrow.com acquired for $7.5 million
  3. .App domains are coming: Q&A with Google
Categories: Domains

This is a brilliant landing page strategy for selling premium domains

Domain Name Wire - Tue, 01/05/2021 - 17:41

Sending buyers to LinkedIn has many advantages.

The other day I came across Domaining.com owner Francois Carrillo’s landing page for Faster.com (see image above). It’s a simple landing page that allows visitors to take only one action if they are interested in the domain: contact Francois through his LinkedIn profile.

If you click anywhere on the page it shows a message:

Clicking “OK” brings you to Francois’ LinkedIn profile where you can contact him.

I immediately thought this was brilliant. It weeds out any confused visitors. It forces the buyer to make a least a little bit of effort to contact you. It reveals the buyer’s identity. And even if they try to contact you through other means, they show up on LinkedIn in people who viewed your profile.

I reached out to Francois to ask him about this strategy. He stressed that it makes a lot of sense for premium domains. For lower priced domains he uses a lander with fixed prices. Here are the benefits Francois noted via email:

1) It blocks most low ballers and not motivated people. First because one will see their face, second because it obligates them to log in to LinkedIn, or worse, create an account. 2) You can do “price upon request”. You know who is behind an inquiry, his company, his history, his network …You can discuss before giving any price and this way get an idea of what the buyer is planning to do with the domain and how much he is willing to spend. So you can give a price that better matches the buyer’s possibilities and your expectations. 4) You don’t need to update your landing page or marketplace prices over time. What one is willing to accept today for a domain was maybe previously priced for less or the inverse. With this landing page, you decide the price at the moment and with “due diligence”. 5) If you have a domain that probably should perfectly match the buyer needs (low or no competition) you can always say: Sorry, but this domain is not for sale… now if you have an outstanding offer I am willing to listen. This way you let the buyer tell you what he could/want to pay… it’s a good negotiation start. It’s harder to use that tactic when your landing is already giving a price estimation. 6) If, after seeing the profile of the potential buyer, you estimate he could never buy for your price expectations you can always find a polite exit so he will not insist and waste your time. And if the guy is not polite or harasses you…simply delete the conversation thread, or block him. (I never accept an anonymous friendship connection. I only respond to the note added to the connection request and delete the conversation thread if it was of low interest.) 7) It’s awesome to have a real person in front and negotiate, discuss… marketplaces are so boring and idiotic, it’s like exchanging prices with a wall. Now, it may happen the person you talk to is so nice that a kind of friendship may occur over time, and you may finish selling him your name at a discounted price, but no problem because he gave you so much that in fact, you do it with pleasure! 8) Some domainers do not want to expose their full portfolio for many reasons. People who contact you have no idea if you have one domain or thousands.

Post link: This is a brilliant landing page strategy for selling premium domains

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

Donuts top 20 premium (channel) sales of 2020

Domain Name Wire - Tue, 01/05/2021 - 16:35

Here are the top channel sales of 2020 and how they are being used.

Like most top level domain companies, Donuts sells the best domain names in its portfolio at premium prices. These premiums are usually charged for the initial registration and renewals. Many of these premium domains carry just a slight premium to normal registration fees. Others cost a lot more.

Below is a list of Donuts’ top 20 premium domain name sales through the registrar channel during 2020. This does not include its very best domains, which are sold in negotiated transactions. It also doesn’t include domains that were purchased in prior years and renewed at premiums during 2020.

I believe the wholesale prices for these domains range from about $10,000 at the top of the list to $500 at the bottom. I’ve also noted which domains are being used.

office.furniture
q.creditcard
rip.rip
gpstracking.software
auto.deals
ice.hockey – an online betting site for hockey games
lawyer.attorney
lille.immo – forwards to Lille-Immo.fr, a real estate agency.
shop.attorney
shop.lawyer
x.rip – forwards to an imgur page
18.video
ex.group – Ex Corp develops IT solutions for Esports.
fx.ltd
iq.group
ks.group – this is a password-protected site for Krebs Stamos Group.
prime.mortgage
value.market
cm.studio – Conscious Minds Studios is an ad firm.
dds.dentist

That so few of the names are being used shouldn’t come as a complete surprise. Some were likely purchased for protection, others by domain investors, and the rest by companies that plan to eventually use them. I’m always amazed at how many aftermarket sales I make that never end up being developed.

Post link: Donuts top 20 premium (channel) sales of 2020

© DomainNameWire.com 2021. 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. Donuts has generated $53 million in premium domain revenue
  2. Donuts reveals seven new TLD sales up to $125,000
  3. Radix: $1.36M premium revenue in first half of 2019
Categories: Domains

Wix changes product name from virus to nicotine

Domain Name Wire - Mon, 01/04/2021 - 20:12

Company dumps Covid-sounding brand name.

Wix has changed the name of its web development platform from the Covid-sounding Corvid to Velo.

Each time I got an email this year from Wix (NASDAQ: WIX) about its Corvid web development system, I thought the company is providing an update about Covid-19.

I’m not the only person. Wix has finally decided to change the name of Corvid.

The new brand is Velo. Google ‘Velo’ and you’ll find that Velo is the brand name of a line of nicotine pouches and lozenges. But if you aren’t into sucking on nicotine, Velo is a much cleaner brand than Corvid.

Wix is the latest in a long line of companies that picked decent brand names only to have them take on a second meaning (or, in this case, to be easily confused with something bad). Remember that mobile payments service called ISIS?

Wix published a video making light of the situation:

Post link: Wix changes product name from virus to nicotine

© DomainNameWire.com 2021. 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 to set up URL forwarding with Wix (step-by-step)
  2. Wix reports Q2 2019 earnings, upgrades outlook
  3. Wix has record-setting Q2 thanks to Covid
Categories: Domains

How I decide which domains to renew vs. delete

Domain Name Wire - Mon, 01/04/2021 - 18:15

Some helpful tips for making the keep/delete decision.

I like to spend the final week of the year preparing for the next. This includes reviewing the domains in my portfolio that expire over the next 6-7 months and renewing the ones I want to keep. I ran this exercise last week and documented my process in the hope that it’s helpful to readers.

I currently have about 1,700 domains, which means about 150 are up for renewal in a given month. It takes time to review 6 months’ worth of expiring domains to make decisions, but it’s time well spent.

Here are some resources I use to determine which domains to keep/delete and my thought process.

Afternic leads: If you have a lot of domains at Afternic, they probably get quite a few leads that you never hear about. The buyers don’t end up being qualified, or their offer is nowhere near your floor price. But knowing that a domain receives offers is important when making keep/drop decisions. You probably don’t want to drop a domain that receives real offers, even if they are only $500. Ask your Afternic account manager for a leads report for your portfolio.

Parking revenue: Parking isn’t what it used to be, but the data is still relevant. Some domains (even new top level domains) can still earn their keep from parking alone.

dotDB: dotDB lets you quickly see how many extensions a domain is registered in, as well as how many other domains the keyword appears in. Search for your second level domain to find out how popular it is in domain names. A paid version will show you if the domains resolve to websites.

Estibot: Knock it all you want, but Estibot is a great tool for figuring out if you’re overlooking a valuable aspect of your domains.

After reviewing all of this data, I ask these questions:

1. Will this domain ever sell for a lot of money? Or is the pool of buyers (or their financial wherewithal) too small to make a difference?

2. Was the domain previously registered in a lot of extensions but the owner(s) let them expire? Perhaps I thought there was a lot of demand for the second level domain, but it was really one person who let all of the alternatives expired.

3. Is the singular/plural version of this domain available for hand registration? If so, the domain might not be worth much.

4. Did I reduce the price substantially last year and it still didn’t sell? If it was priced below $500 and didn’t sell, it’s probably time to cut it.

5. Does this domain have a big/important/valuable subject matter, but it wouldn’t ever make sense for a company to use this domain for a website? The two aren’t always correlated.

6. Have I sold domains that are similar to this one? Some domainers invest in ‘themes.’ If none of my domains within that theme have sold, the market is telling you something. Likewise, have I received inquiries/leads on any of the similar domains?

7. How long ago was this domain registered? If it was a long time ago, resist the urge to think about sunk costs. Why hasn’t it sold?

I ended up turning off auto-renew on about 80 domain names, so roughly 10% of the domains due to renew in the next 6 months. This is more than usual. But I figure the cost of renewing domains is only going up, and perhaps I should have cut some of these domains years ago.

Post link: How I decide which domains to renew vs. delete

© DomainNameWire.com 2021. 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. Comparing expired domain drop catching prices
  2. Comparing the GoDaddy Auctions model vs. NameJet model
  3. Sedo improves expired domain auction search
Categories: Domains

NielsenIQ and domain names – DNW Podcast #319

Domain Name Wire - Mon, 01/04/2021 - 16:30

What’s NielsenIQ, and why did it acquire NIQ.com?

Nielsen — the company you probably know for TV ratings — is really much more than that. This year, the company is splitting into two. On today’s show, I interview Jacqueline Woods, Chief Marketing Officer of NielsenIQ. We discuss the split, what NielsenIQ does, and how it chose its domain. Jacqueline also explains why the company decided to acquire the three-letter domain NIQ.com.

Also: Donuts completes acquisition, GoDaddy phishing fury, reverse domain name hijacking.

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: NielsenIQ and domain names – DNW Podcast #319

© DomainNameWire.com 2021. 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. Interviews at SXSW – DNW Podcast #76
  2. Why ConvertKit rebranded as Seva – DNW Podcast #194
  3. Top Domain Sales of the Year – DNW Podcast #197
Categories: Domains

How to use LinkedIn to contact corporate executives in China

Domain Name Wire - Mon, 01/04/2021 - 14:42

Kassey Lee explains how he uses LinkedIn to contact decision markers in China. It’s relevant for connecting with people around the world.

I joined LinkedIn in 2016 upon recommendation by long-time domain investor Howard Fellman. In these four years, I have made over 30,000 connections including 8,000 CEOs. A large number of them are from China. I use LinkedIn almost every day to write about domains and exchange ideas. It is truly a global network.

LinkedIn has a significant presence in China. It entered the Middle Kingdom in 2014 and currently has 50 million Chinese users according to Baidu. As far as I know, LinkedIn is the only foreign social network allowed in China. It provides an easy way for westerners to contact corporate executives in China.

To be able to contact any LinkedIn user in China, you need to have a large network. In 2017, I wrote an article on LinkedIn detailing how I acquired 3,000 CEO connections. Unfortunately, it is written in Chinese but you can still read it with the help of Google Translate. Here is the link to the article. If you don’t have time to build up your network, you can sign up as a paid member, which allows you to message anyone on LinkedIn regardless of whether they are on your network or not.

Finding a company is straightforward. As an example, let’s use the Chinese company “Singlera” which I came across recently during my end user research. Use the search box prominently displayed across the top of every LinkedIn page and enter “singlera”.

LinkedIn shows a number of listings, including the CEO, COO, and CTO of Singlera. There is also a link to the company’s LinkedIn page from which you can find even more executives of the company.

If you are not a paid member, be aware that you may be stopped if you do too many searches at one time. To get around it, I often use Google search by entering “linkedin singlera ceo” or something similar.

LinkedIn provides a function which is very handy: connection request. I use this function to send a message to an executive I want to contact. To use this function, make sure you are viewing the profile page of the executive (otherwise no message box will appear later). First, click the Connect button on the page.

The following dialog box appears.

Be sure to click “Add a note”, then you’ll see the following dialog box.

Enter a message, up to 300 characters. I try to be very short and get straight to the point.

What about the language issue? No problem. You can use Google Translate or another translation tool. I know an investor in China who wants to expand his network beyond China. He joined LinkedIn early this year and has been very active even though he does not know much English. He just uses a translation tool when writing messages on LinkedIn.

Final word: use the connection request sensibly and write a message which truly has value to the recipient.

Post link: How to use LinkedIn to contact corporate executives in China

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

Happy New Year. Here’s to a better one!

Domain Name Wire - Thu, 12/31/2020 - 18:51

I think that the world is generally becoming a better place as the years go by. But 2020 was a real stinker, even for someone like me. Nothing will magically change as the clock strikes midnight tonight, but surely 2021 can’t be any worse than 2020?

As we reflect on the past year, my heart goes out to all those who truly suffered this year. Many people suffered economically due to shutdowns. While economic hardship is painful, many people also suffered in an ultimate way — their health.

If you’ve been fortunate enough this year to avoid both an economic shock and a health one, please consider giving back. Help out a neighbor in need or donate to a worthy cause. Even if you take the standard deduction, U.S. taxpayers can deduct up to $300 in charitable cash donations this year. Take advantage of this and chip in to an organization in need before the clock strikes midnight.

Post link: Happy New Year. Here’s to a better one!

© 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

2020 in Review: Price hikes on the way

Domain Name Wire - Thu, 12/31/2020 - 14:32

Domain investor costs are about to increase.

This is the fifth in a series of posts about the domain name industry in 2020. Read the others here.

.Com prices are going up.

ICANN agreed to a contract extension with Verisign (NASDAQ: VRSN) in 2020. The extension allows Verisign to increase the wholesale price of .com domains by 7% per year in the last four years of each six-year contract extension. The first year for potential price increases began in October.

Verisign has postponed rate hikes during the pandemic but says it plans to enact the first price increase by October 2021.

7% might not seem like much, but it adds up. The owner of 1,000 domain names can expect to pay about $2,400 per year in additional renewal fees by the fourth increase.

And to Verisign, it’s a lot of money. There are 151.75 million .com domains registered. Upon renewal, the first 7% increase adds over $80 million of pure profit to Verisign’s bottom line.

(Domain owners will likely face price hikes in other extensions, too. ICANN lifted all price restrictions on most top level domains in 2019, including .org, .info, and .biz.)

And thus continues the love/hate relationship between domain investors and Verisign. Domain investors spend time propping up the value of .com on domain blogs and in forums, all the while fighting against price increases.

Just a handful of years ago, Verisign wined and dined domain investors. Then it threw them under the bus.

But Verisign has also taken steps to try to placate registrars and big investors this year. This year, it ran marketing promotions that discounted the price of .com domains that were just dropped, padding the profit of drop catchers.

One thing is certain: expect Verisign to take full advantage of the price hikes it has been afforded. And that means rising costs for domain name owners.

Post link: 2020 in Review: Price hikes on the way

© 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 stocks doing very well this year
  2. 4 things Verisign said on its investor conference call
  3. ICANN is about to give Verisign its .com price increases
Categories: Domains

The scariest thing about that GoDaddy phishing test story

Domain Name Wire - Wed, 12/30/2020 - 16:23

A lot of employees apparently fell for it.

GoDaddy has been taking a lot of heat for a phishing test email it sent to many of its employees right before the holidays.

The email told recipients that they were receiving a $650 holiday bonus and asked them to click a link in order to receive the bonus.

The bonus wasn’t real. It was a test to see if employees would fall for a phishing attack.

I understand why some employees are upset about the test. But I’m more concerned that 500 people reportedly failed the test.

I’m not sure what “failing” means here. Does that just mean they clicked the link? Or did they divulge passwords?

Regardless, that’s a lot of people failing a test in a company of about 7,000. (That assumes everyone received the test email, too.)

I suspect fewer people would have been duped if they were in an office setting rather than working from home. Word would have quickly spread around the call centers, “don’t click that link!”

But it’s clear that GoDaddy needs to continue to educate and test its employees. It holds the keys to valuable assets and people are trying to steal them or trick GoDaddy employees into making critical changes.

Former GoDaddy employee Tony Perez, who sold his company Securi to GoDaddy, opined:

Employee’s being mad about “tone-deaf” phishing tests by a company, and the media’s hunger to amplify that message, highlights the uphill battle CISO’s and security teams are faced with. Bad actors don’t care about your feelings.

— Tony Perez (@perezbox) December 29, 2020

Hurt feelings aside, I hope GoDaddy continues to run these tests until it’s unable to dupe any of its employees.

Post link: The scariest thing about that GoDaddy phishing test story

© 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. Register.com Home Page is a Winner
  2. How to Save Money on Your Domain Renewals
  3. 1&1 begins pre-registration, and new TLDs are getting much more confusing
Categories: Domains

2020 in Review: Domain aftermarket innovation

Domain Name Wire - Wed, 12/30/2020 - 14:57

Aftermarket companies introduced new features to help domain investors sell more domains.

This is the fourth in a series of posts about the domain name industry in 2020. Read the others here.

2020 started with concern about GoDaddy acquiring Uniregistry, consolidating a low-cost domain aftermarket platform. But I’d argue that 2020 was actually a great year when it comes to investor choice and features in aftermarket platforms.

Yes, GoDaddy has a strong lock on the registrar channel for aftermarket sales, followed by Sedo. But upstarts are offering solutions to help sell domains in other ways.

Dan.com introduced a bunch of new features this year, including flexible domain financing. It also announced partnerships with Bodis to generate parking revenue and MediaOptions to help close more sales. Dan.com is becoming the aftermarket stack.

Efty introduced a marketplace and partnered with Dan.com for closing sales. DomainAgents reported a huge uptick in offers. DNWE came onto the scene, giving domain investors a way to offload domains at wholesale prices while continuing to market them to end users are full fare.

But I’d say the most (and fastest) innovation came from SquadHelp. SquadHelp helps businesses select names. Until this year, domain investors could only use the platform by giving SquadHelp an exclusive and paying a 30% commission. In 2020, SquadHelp introduced white-label marketplaces. Think of it as the ability to create your own domain store and use SquadHelp’s landing pages and transaction system to close sales.

With 7.5% commissions, the ability to tap into SquadHelp’s marketplace for logo designs, remarketing ads, and live chat, SquadHelp has a lot to entice domain owners. It also iterates quickly in response to feedback, with features such as Google Sheets editing, adding new features, and negotiating options.

Ultimately, these companies are giving domain investors more choice. Yes, investors still need to go through GoDaddy’s Afternic or Sedo to get into the registrar purchase path, but they have lots of options for selling their domains through other channels.

Post link: 2020 in Review: Domain aftermarket innovation

© 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. We’re seeing innovation in domain sales
  2. Uniregistry adds GoDaddy branding to landers
  3. 2020 in Review: Consolidation
Categories: Domains

Donuts completes Afilias acquisition

Domain Name Wire - Tue, 12/29/2020 - 19:42

Donuts now owns Afilias.

Top level domain name company Donuts has completed its acquisition of Afilias, the company announced today.

Donuts’ CEO Akram Atallah said, “We expect no changes in the short term, and ample notice on any changes that are decided. Security, stability and reliability continue to be our top priorities.”

Those changes could be a rationalization of two different registry platforms. Donuts will likely tread carefully in order to not upset the registrar channel.

It will also be interesting to see which employees stay with the combined company. There is significant overlap between the two companies, which was surely part of the equation when Donuts determined how much it was willing to pay for Afilias.

ICANN staff apprised its board of the transaction, likely because of the involvement of ICANN’s former CEO, but did not take any action to prevent the transaction.

Post link: Donuts completes Afilias acquisition

© 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. .Green and .Wedding contention sets settled in multi-million dollar auctions
  2. This week in new TLDs: $150k/domain? Plus .black, .hiv, and .creditcard
  3. Donuts is acquiring Afilias
Categories: Domains

Owner of Gainvest.co tries to hijack Gainvest.com

Domain Name Wire - Tue, 12/29/2020 - 16:00

Company files cybersquatting complaint against domain registered nearly two decades before it existed.

A World Intellectual Property Organization panelist has found that Gainvest Legal Corporation tried to reverse domain name hijack Gainvest.com.

Gainvest Legal Corporation uses the domain name Gainvest.co for its business services company.

John Sozanski of Gainvest, LLC registered the domain name in 1999, about 20 years before the Complainant existed. Hence, it was impossible that the Respondent registered the domain name to target the Complainant and it’s clear that it was not registered in bad faith.

Gainvest Legal Corporation first tried to buy the domain name. It rejected the Respondent’s $10,000 asking price, noting that “we are a poor startup that just started in March 2019.”

It subsequently filed the UDRP.

Panelist Robert Badgley noted that Gainvest Legal Corporation was represented by counsel and should have known better. (The decision states that the company was
internally represented, but it appears that the company’s CEO is an attorney.)

Badgley wrote:

This Complaint was doomed to fail, given Respondent’s apparently continuous ownership of the Domain Name long before Complainant had any trademark rights. There is absolutely no reason to doubt Respondent Sozanski’s denial of ever having heard of Complainant or its trademark prior to August 2020, when Complainant’s representative Ali approached Respondent about a purchase of the Domain Name.

The fact that a complaint under the UDRP is doomed to failure, however, does not necessarily compel a finding of Reverse Domain Name Hijacking (“RDNH”). A claim of RDNH should be evaluated under the particular circumstances of each case in which it is raised. One factor sometimes tending to support a finding of RDNH is if a complainant is represented by counsel. In this case, Complainant was indeed represented by counsel.

Another aspect of this case that supports a finding of RDNH is that Complainant, through counsel, not only brought a doomed case, but made a series of utterly frivolous allegations along the way. For instance, Complainant asserts, with no argument or evidence, that Respondent’s “primary purpose” vis-à-vis the Domain Name was to disrupt Complainant’s business. Complainant also chides Respondent for registering the Domain Name in 1999 but failing to adopt a corresponding business name until 2008. This argument misses the vital point that Complainant itself did not exist and was not using GAINVEST as a trademark for another 11 years after 2008. Complainant then asserts that “it can be implied that the domain name was registered by Respondent primarily for cybersquatting, to disrupt the business of Complainants while obtaining payment for that disruption.” These (and other) arguments raised by Complainant are specious, and support a finding of RDNH.

The best that can be said in defense of Complainant’s motives here is that Respondent never made much, if any, actual use of the Domain Name for more than 20 years. Even so, the accumulation of frivolous arguments, including those noted above, by Complainant are sufficient to tip the balance in favor of a finding that this Complaint was brought in bad faith.

Post link: Owner of Gainvest.co tries to hijack Gainvest.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. Owner of Corediagnostics.in Guilty of Reverse Domain Name Hijacking
  2. JetGo guilty of RDNH after filing “seriously misleading” case against Frank Schilling
  3. Square Grouper Tiki Bar guilty of Reverse Domain Name Hijacking
Categories: Domains

2020 in Review: .Org sale

Domain Name Wire - Tue, 12/29/2020 - 14:50

A top story this year was the sale of .org falling through.

This is the third in a series of posts about the domain name industry in 2020. Read the others here.

One of my predictions for 2020 was that Ethos Capital’s deal to acquire Public Interest Registry would go through despite widespread outrage. I was wrong.

Ethos Capital and Public Interest Registry (PIR), which operates .org, announced the deal in November 2019. Ethos Capital agreed to buy the non-profit for $1.135 billion with plans to turn it into a for-profit venture.

Internet Society controls PIR and generates substantially all of its funds through the sale of .org domain names. It viewed this as an opportunity to exchange future cash flows from domains for one lump sump, derisking potential negative changes to the market for .org domains.

I remember receiving a call the day the deal was announced. The caller asked, “Do you think Fadi Chehadé is behind this deal?”

My initial reaction was no. Chehadé, the former CEO of ICANN, made a splash in 2018 when he led a deal by Abry Partners to acquire top level domain company Donuts. But why would he try to buy .org through a different firm?

But the caller pointed out that Chehadé’s name was in Whois for the registration of a domain name related to Ethos Capital. It turns out this caller was right; Chehadé was involved.

It’s still unclear to me why Chehadé and Abry partner Erik Brooks left Abry ostensibly to pull off this deal. Did Abry not want to be connected to the controversy? Did Chehadé and Brooks just see a bigger opportunity?

There was lots of pushback against the deal. EFF was particularly active in opposition. Six lawmakers — including Democratic presidential hopeful Elizabeth Warren — urged ICANN to reject the deal.

Still, history suggested the deal would go through…

Until California’s Attorney General spoke up.

In his role as Attorney General, Xavier Becerra oversees non-profits in the state. ICANN is incorporated in ICANN.

Becerra’s initial letter delayed the deal. It appeared ICANN was ready to approve the transaction in April but scuttled the approval when Becerra sent a more forceful letter.

At the end of April, ICANN’s board of directors voted to reject the sale.

The non-profit community is breathing a sigh of relief. And ISOC will have to settle for about $70 million a year rather than a $1.135 billion lump sum.

Post link: 2020 in Review: .Org sale

© 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. Ethos paid $1.135 billion for .Org
  2. My thoughts on .Org
  3. Breaking: ICANN rejects .org sale to private equity company
Categories: Domains

Spase, Inc. found to have tried reverse domain name hijacking a second time

Domain Name Wire - Mon, 12/28/2020 - 19:34

What’s the definition of insanity, again?

A National Arbitration Forum panelist has found that Spase, Inc., committed reverse domain name hijacking for a second time.

The company uses Spase.io for its service that turns product photos into 3D digital files.

It filed a UDRP against Spase.com with World Intellectual Property Organization earlier this year.

The three-member panel found that it was a case of reverse domain name hijacking; the domain owner Mrs Jello, LLC acquired the domain well before Spase, Inc. existed.

Spase founder Sahil Gupta went on a twitter tirade after the decision.

Apparently still not understanding what’s required to win a cybersquatting case under UDRP, Gupta filed another UDRP against the domain at National Arbitration Forum.

Mrs Jello, LLC didn’t respond to the dispute but panelist Dawn Osborne found reverse domain name hijacking:

As a result of the WIPO Case the Complainant must have been aware that the Domain Name could not have been registered in bad faith as the Complainant lacked the relevant rights in the SPASE name at the time of registration of the Domain Name. As such the Panel has no alternative but to hold that this Complaint is a case of Reverse Domain Name Hijacking.

Post link: Spase, Inc. found to have tried reverse domain name hijacking a second time

© 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. Spase.io tries reverse domain name hijacking
  2. Square Grouper Tiki Bar guilty of Reverse Domain Name Hijacking
  3. Cyber security company tries to steal domain name through UDRP
Categories: Domains

2021 Predictions Episode – DNW Podcast #318

Domain Name Wire - Mon, 12/28/2020 - 16:30

Here’s where 22 domain industry pros think we’re headed in 2021.

Bring out the champagne, 2020 is almost over! It has certainly been an eventful, life-altering year.

We’re concluding 2020 with our annual predictions episode. I asked people in the domain name industry to reflect on 2020 and make predictions for next year. You’ll hear from 22 people representing investors, domain brokers, registries, and other organizations. Enjoy!

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: 2021 Predictions Episode – DNW Podcast #318

© 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. Domain leasing, selling domains and more – DNW Podcast #308
Categories: Domains

2020 in Review: Consolidation

Domain Name Wire - Mon, 12/28/2020 - 14:28

Two major registries were among the domain name businesses gobbled up in 2020.

This is the second in a series of posts about the domain name industry in 2020. Read the others here.

If you want to make a guaranteed prediction about the future of the domain name industry, just predict that there will be more consolidation.

2020 was another year of big acquisitions in the domain name business.

It started with GoDaddy (NYSE: GDDY) announcing the acquisition of Uniregistry (the registrar business, not the registry) and Frank Schilling’s domain name portfolio for something less than $200 million.

GoDaddy followed up by entering into the wholesale registry business in a big way by acquiring Neustar’s registry business for $218 million.

Donuts is acquiring Neustar’s archrival Afilias in a deal that should close by the end of the year.

CentralNic (London AIM: CNIC) continues to roll up the domain industry and has expanded its horizons to online advertising after acquiring Team Internet in 2019. It bought CodeWise for $36 million this year.

Web.com acquired New Zealand domain name registrar FreeParking after losing a planned acquisition of WebCentral, which went to Australian company 5G Networks instead.

There’s continuing consolidation among new top level domains, too. XYZ has been particularly acquisitive.

And, although it’s not technically consolidation, Clearlake Capital Group’s $3 billion acquisition of Endurance International Group (NASDAQ: EIGI) shows that private equity is still very interested in the domain name space.

Which brings us to the acquisition that didn’t happen. More on that in the next post.

Post link: 2020 in Review: Consolidation

© 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. .Com Winners: Some shakeup in the top 10
  2. .Com winners and Losers: Dynadot stays hot
  3. CentralNic acquires .SK operator for €26 million
Categories: Domains

Can you remember this 5N corporate domain of a top company?

Domain Name Wire - Thu, 12/24/2020 - 21:23

Probably not.

Shi Ji Kai Yuan (世纪开元) was founded in 2001 as a platform to offer one-stop printing solutions. The company claims to have 20 million regular users on its website. It features a variety of services based on the consumer-to-business (C2B), consumer-to-machine (C2M), and supplier-to-business-consumer (S2B2C) models. Shi Ji Kai Yuan ranks No. 98 of the Top 100 internet companies (2020) in China.

When I was researching this company, I naturally thought that its corporate domain would be the brand-matching ShiJiKaiYuan.com, acronym domain SJKY .com, or their equivalents in the .cn extension. No, these domains are either not active or still available for sale. Shi Ji Kai Yuan can be found at 36588.com.

Can you remember 36588.com easily? For Chinese, it is no problem. As far as I can see, the domain consists of two numbers: 365 and 88. The number 365 refers to the 365 days in a year, which basically means “everyday”. 8 means “making a fortune” and 88 just repeats it twice, which is quite common in the Chinese culture. Together, they mean “making a fortune everyday”.

I see two issues here. The first one is that 36588 does not suggest anything related to printing. I even thought it was a gambling site. Also, I wonder how non-Chinese clients can remember this domain when one day the company decides to go global. One solution that many Chinese companies take is the use of their matching acronym domain – SJKY.com in this case.

In my opinion, 5N or longer numeric domains are not suitable for application in corporate China, so I do not expect their widespread use. These domains are mostly traded among investors. Another point is that long domains are difficult to remember, which offers an opportunity for an upgrade to an acronym domain. If your domain happens to be the acronym of a Chinese company name – as in the case of SJKY.com – your domain may be very valuable because of its upgrade possibility.

Post link: Can you remember this 5N corporate domain of a top company?

© 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
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.