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.

How domain name registrars can win over domain investors

Domain Name Wire - Wed, 02/21/2018 - 14:33

Here’s what domain name registrars need to do if they want to get domain investors as customers.

I get lots of pitches from domain registrars that have added nifty new features or are offering rock-bottom prices. It takes more than this to win domain investors as customers. It takes a complete package. Here’s what domain name registrars can do if they want to win over domain investors.

You can’t win on price, but you can lose on price. I often get pitches from domain name registrars about how they’re great for domain investors because of their low prices. But when it comes to .com domains, you simply can’t win on price. There are many registrars out there that offer essentially break-even pricing on .com domain names. The only way you can beat your competition is by losing money. Even when it comes to short-term discounts below the wholesale cost, I think most domain investors are smart enough to realize that registrars aren’t willing to lose money in the long run. So you’re not going to win on price (at least for .com), but you can lose on it. If you’re charging more than $9.00 or so, it’s going to be hard to win domain investors.

Security is a must. There are many things at play when it comes to security. These days it’s necessary to offer two-factor authentication, ideally through an app instead of SMS. U2F is even better, and Fabulous offers this.  One of the better security offerings I’ve seen is from GoDaddy, which lets larger domainers enable call-based security before a domain is transferred out. A GoDaddy representative will call the account owner and ask for a pin number before authorizing an outbound transfer.

Then there is the security that you don’t notice as much. It’s hard for me to evaluate if a registrar has good backend security but if they don’t follow visible best practices, I get worried. An example is sending emails to customers that require action and these emails don’t identify the customer by name or another identifier. That makes it more likely someone will fall for a phishing scam in the future.

Make it simple to manage domains. Domainers want lots of account admin features but they also want a good user interface. If a registrar creates something that looks like a programmer designed the front end, then it’s in trouble. Think about the types of actions domain investors need to perform and make it as easy as possible. Bulk actions are a must. Oh, and if you don’t offer bulk auth code downloads for transferring out, then domainers should be wary about transferring in.

Your business is important to us, but please hold. There are two essential elements of support: a good online knowledgebase and great support. Answer the phone quickly with knowledgeable reps. Promptly respond to email. Make chat support available.

Show me the money! OK, so you can’t win on price. Security is a must but it’s more of a disqualifier than a qualifier. And you need a good baseline domain manager plus good support. So far, there’s nothing that can really separate a registrar from the pack. There’s one key thing that can make a registrar truly stand out: help domainers make more money.

It used to be you could do this with a good domain parking program, but that has basically disappeared. Now you need to help them sell domains. That means integrating with AfternicDLS or SedoMLS (preferably both). Help domainers analyze their portfolios. Provide tools that enable them to make renew/drop decisions.

Helping a domainer make more money will far outweight discounted domain prices in terms of value. It might actually help you turn domainers into profitable customers, too.


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

Crypto and Blockchain are registered with the Trademark Clearinghouse

Domain Name Wire - Tue, 02/20/2018 - 17:53

Want to register a new TLD with one of these suddenly hot terms? You’re going to deal with the TMCH.

Remember the Trademark Clearinghouse for new top level domain names?

By getting a mark filed with the Trademark Clearinghouse (TMCH), a company can get first rights to a domain matching the mark when a new TLD goes through sunrise. Also, people that try to register a domain matching the mark get a warning during the start of general availability. This triggers a notification to the trademark holder, too.

I’ve documented how some companies tried to game the system. But with new TLDs coming out with lackluster interest, the concept of premium domains with premium pricing, and new TLDs rolling out slowly now, you don’t hear about it much more.

So you might be surprised to see that Blockchain and Crypto are in the TMCH database.

I might give the crypto trademark owners a break. There are three marks in the database, apparently from two different companies using Swiss trademarks. Their websites are bordotek.com and crypto.ch. I’ll cut them some slack because they are in the crypto-security space, not cryptocurrencies.

But blockchain? A French technology company called Athanor has registered its mark in the TMCH database. Hmm.

There are no registrations for Bitcoin and Cryptocurrency.


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. The new TLD Trademark Clearinghouse is about to get a lot of attention
  2. NCSG challenges ICANN decision to extend Trademark Clearinghouse rights
  3. Sorting facts from fiction in the Trademark Clearinghouse
Categories: Domains

Domain investor trio acquires DNForum

Domain Name Wire - Tue, 02/20/2018 - 13:37

Three domain investors will be the next to try to restore DNForum to prominence.

Domain name forum DNForum has been sold to three domain name investors who will operate the site and hope to restore it to its former glory. The terms of the deal were not disclosed.

I asked the new owners for a quick overview of who they are. One of the promising things about this trio is its geographic distribution. This gives them more timezone coverage as well as an multinational perspective.

Here are the new owners:

Oliver Hoger
Oliver has been an active trader of high-quality domain names the past 10 years, both as a buyer and seller of domain names and also as a broker for many high-profile clients. Oliver is a well know trader amongst the regulars of the high-end domain aftermarket. Oliver is based in the Euro time zone.

John Nguyen
John has been in the IT consulting business for the past 34 years. 15 years of those in the domain name business as a well-known short name investor. John also has a long and valued history at DNForum.com both as an active member but also as a moderator and administrator. John is based in the US.

Lars Lima
Lars been in the domain name industry for the past 13 years as an independent investor and broker of short domain names at www.DNand.com. He carries an MSc in International business management and has a history in sales and marketing. Lars is based in Denmark.


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Survey: DNForum Tops NamePros
  2. DNForum Now Easier to Access on the Road
  3. DNForum (and its user database) is for sale again
Categories: Domains

Insurance giant AXA loses fight for AXA.org

Domain Name Wire - Mon, 02/19/2018 - 17:51

Company provides the evidence that panel used to dismiss the dispute.

Insurance company AXA has lost a cybersquatting complaint it brought against the domain name axa.org.

The owner of the domain name did not respond to the complaint, yet AXA itself provided the evidence necessary for the panel to reject the claim.

AXA provided evidence that a group called Advocates Across America previously used the domain name. AXA argued that the group was dissolved in 2016 after failing to file annual reports with the State of Arizona.

But to win a cybersquatting case under the UDRP, a complainant has to show the domain was registered in bad faith, not just used in bad faith. The evidence AXA submitted showed that the domain was almost certainly registered in good faith by an organization using AXA to mean “Advocates Across America”, not to take advantage of the insurance giant.

AXA made the argument that AXA wasn’t an acronym for the group despite the common use of ‘x’ to mean across. It also argued that the domain was registered to take advantage of the insurance company. I can’t imagine a reason that a group that advocates for people with learning disabilities would want to trade off the goodwill of an insurance company.

In fact, you could make a good argument that this is a case of reverse domain name hijacking:

1. AXA knew the domain was registered in good faith.
2. It made a bad claim about how AXA is not a reasonable acronym for Advocates Across America
3. It waited over 20 years to bring its claim against the domain, ostensibly because the organization recently dissolved


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. BMW Files Cybersquatting Lawsuit
  2. St. Louis bank sues to take over gripe domains
  3. PCO.com saved in UDRP despite no-show by domain owner
Categories: Domains

Christa Taylor talks domains – DNW Podcast #173

Domain Name Wire - Mon, 02/19/2018 - 16:30

An in-depth discussion on the state of new top level domains.

What makes for a good top level domain name? Well, it starts with the ABIC test. Christa Taylor of dotTBA has helped many companies apply for, plan for and/or launch top level domain names. This puts her in a unique position of seeing new domains at many stages and monitoring different strategies. On today’s show, we discuss what has happened with new top level domains so far as well as what she expects will happen in years to come. We also discuss the challenges of domain names in the Middle East. You’ll also hear about Christa’s ABIC test for determining if a new top level domain name is good. You can actually apply ABIC to other things, too. Also: Much ado about ado.com, Donuts goes travelling, Google Chrome and Verisign’s missing news.

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


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Frank Schilling explains price hike – DNW Podcast #127
  2. How to Sell More Domains with Adam Strong – DNW Podcast #158
  3. Reviewing this year’s predictions – DNW Podcast #161
Categories: Domains

Kitchens To Go tries to reverse domain name hijack KTG.com

Domain Name Wire - Fri, 02/16/2018 - 22:42

Broker offered domain name for sale, which Kitchens To Go used as an opening to get domain below market value.

Kitchens To Go, LLC has been found guilty of reverse domain name hijacking for a cybersquatting complaint it brought against the domain name KTG.com.

The owner of KTG.com died and left the domain names to his sister. His sister then hired a domain broker to try to sell the domain names, and the broker contacted Kitchens To Go to see if it wanted to buy the domain. Kitchens To Go uses the domain name KitchensToGo.com but also owns K-T-G.com.

A World Intellectual Property Organization panel determined that Kitchens To Go did not meet any of the three elements necessary to win the case. The panel neatly summarized Kitchens To Go’s actions:

The facts point clearly towards the Complainant, having taken no steps in respect of the disputed domain name since it was first registered in 2001, taking the opportunistic view that, once it had been offered the disputed domain name for sale for a sum greater than the likely costs of registration, it could force the Respondent to sell it for a sum which was less than its market value. Failing that, that it could try to apply further pressure by bringing an unmeritorious claim under the Policy which made exaggerated accounts of rights and sweeping and unsupported assertions of bad faith against the Respondent.

Kitchens To Go was represented by Tressler LLP, which doesn’t appear to have specific experience with IP or domain name disputes.

The domain owner was represented by Zak Muscovitch of Muscovitch Law P.C.


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Mirabella Beauty Products Guilty of Reverse Domain Name Hijacking
  2. UDRP complainant shoots self in foot with supplemental filing
  3. Telepathy scores $40,000 from reverse domain name hijacking case
Categories: Domains

Video: Talking Domains

Domain Name Wire - Fri, 02/16/2018 - 15:11

Joe Styler interviewed me about the domain name business. Here’s what I had to say.

Last year at NamesCon I sat down with Joe Styler of GoDaddy to do a video in conjunction with NamePros. It took NamePros a year to edit and publish the video, but I think it turned out well. Thankfully, I didn’t make bad predictions about what would happen in 2017, and I think it’s still relevant.

We discuss:

* What I like more about investing in domains than in stocks
* How new top level domains can become more popular
* Why large companies sometimes have limited budgets for domains

Enjoy:


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

Domain names Amazon and other end users bought

Domain Name Wire - Thu, 02/15/2018 - 18:24

Huge companies buy domain names along with cryptocurrency companies.

Two very large companies made domain name purchases at Sedo over the past week. Amazon.com bought a generic and Statoil, a $74 billion market cap energy company, bought a domain corresponding to one of its projects.

Of course, there were lots of cryptocurrency related purchases as well, led by Bitkey.com for $25,000.

Here are a baker’s dozen end user sales from Sedo:

(You can view previous lists like this here.)

Bitkey.com $25,000 – The domain is in escrow but I can’t imagine it being anyone other than the owner of Bitkey.io.

Potpourri.com $22,500 – What a deal for Potpourri Group, Inc., a direct-to-consumer merchandiser. It upgraded from PotpourriGroup.com to Potpourri.com for a low price.

HiChat.com $16,800 – It looks like this will be used for a chatting app, but the buyer’s identity is unclear.

UOTC.com $5,299 – A “coming soon” page says it will be a cryptocurrency trading platform.

DoggerBank.com €3,450 – Energy giant Statoil acquired the domain name for one of its offshore wind farm investments.

SBTP.com £2,800 – SBTP Group Ltd is a newly formed company in London. The domain doesn’t resolve yet.

BWYS.com $3,500 – Bluewater Yacht Sales bought its acronym.

LuisFer.com $3,500 – This is short for the personal name Luis Fernandez.

OneDayGroup.com $2,495 – OneDayGroup in China owns the domain name one-day.cn.

AudioLibri.it €8,600 – Amazon bought this descriptive domain which means “audio book”.

DrGrammer.org $8,540 – Stands4 LTD owns Abbreviations.com.

WANDX.com $3,000 – WANDX is a cryptocurrency exchange that uses the domain WANDX.co.

Cakewalk.co $2,000 – This service helps you find and book event space.


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. What domain names Mozilla and others bought last week
  2. What domain names Goldman Sachs and others bought this week
  3. More end user domain name sales
Categories: Domains

Tutorial: Domain Availability Search Using GoDaddy API and PHP

Domain Name Wire - Thu, 02/15/2018 - 16:18

Alvin Brown provides a tutorial on using GoDaddy’s API.

Grab a beverage, put your “coding” hat on for the for the journey ahead. Why? Today we’re tackling a simple coding tutorial.

That’s right, we’re coding a bit today as we aim to create a custom domain search feature with a bit of PHP, HTML, and GoDaddy’s Application Programming Interface (API).

Before diving into this tutorial, be sure you have the following:

  • A web host environment or localhost environment, preferably Linux hosting
  • A GoDaddy Developer account (sign up)
  • GoDaddy API Credentials (see here)
  • A text editor (Notepad++, Sublime, TextWrangler, Dreamweaver, Notepad)

If you encounter issues setting up or logging into your GoDaddy Developer account, then watch this video.

You’ll also need to become familiar with learning to use PHP curl to execute GoDaddy API calls.

NOTE: This tutorial is a “quick and dirty” approach that uses procedural programming and not object oriented programming (which I highly recommend).

I’m using procedural programming as this tutorial considers someone who does not come from nor have they ever had any experience with software development in general.

Once procuring the aforementioned items, then you’re ready to proceed with the tutorial.

Create Domain Search Form Using HTML and PHP
Open the text editor of your choice, naming and saving the following PHP file: dnsearch.php.

The first thing to do is to create a HTML5 form using a bit of HTML, inline CSS (I know it’s bad), and a bit of PHP.The code below is all the HTML you’ll need to create the domain search form (as shown in the image above).

Within the code, notice the following PHP variables echoed: $msg and $_POST[‘domain’].

The $msg variable is used to display success or failure text when executing a search.

The $_POST[‘domain’] variable is the name of the input field receiving input (the domain name to be searched) from the user when executing a search.

Notice the @ symbol proceeding the $_POST[‘domain’], which suppresses an errors, yet displays the domain name entered into the domain form field by the user upon form submission.

Click to enlarge image.

Create Logic to Sanitize and Validate Domain Search Using PHP

NOTE: This tutorial is simply an example and not one I deem using for production-ready environment. This tutorial is only meant to show how you might use the GoDaddy API in conjuction with PHP.

Now that you have the domain search form created, you’re ready to add a bit of logic to search, check, sanitize and validate the domain’s availability using PHP.

One of the first things to do is define an empty $msg variable. The $msg variable, as mentioned in the previous section, is used to display success or failure text when executing a search.

Once the $msg variable is in place, then we’re ready to establish whether or not the submit button has been pressed and if its value equals “Search” using an if statement.

Within the if statement, assume and define an error message as the default message using the $msg.

Next, create a few string replace and trim functions for the $_POST[‘domain’] form field using PHP’s built-in str_replace and trim methods.

I’ve also include the use of filter_var to sanitize and validate the url (i.e., FILTER_SANITIZE_URL) or domain entered is valid.

As a side note, it’s ALWAYS good to check, sanitize, and validate user input as this reduces, if not eliminates, the risk of SQL injections and cross-scripting attacks.

Categories: Domains

Tucows’ CEO Elliot Noss on domains as an asset class

Domain Name Wire - Wed, 02/14/2018 - 20:57

Elliot Noss explains how domain name portfolios can be treated as an asset class.

Tucows (NASDAQ:) held its investor conference call this morning to discuss Q4 and full year results.

During the call, Tucows CEO Elliot Noss referred to the deal the company did with GoDaddy (without mentioning GoDaddy) last quarter to sell some of its domain names. GoDaddy paid $2 million and acquired about 10% of Tucows’ portfolio excluding the surname portfolio.

An analyst asked about the deal and how big deals like this come about. Noss explained that domain names are an asset class:

So when it’s portfolios as opposed to individual names, then it does tend to be people looking to deploy capital. Domains are an asset class. They are an extremely obscure class with a small pool of investors, but it’s an asset class that performs like any other. You have people who sort of pay attention to different elements of the asset class and who deploy capital for different reasons. In our case, we’re very plugged in the industry. It’s known where we are when somebody wants to deploy capital or somebody wants something else from us, there may be some portfolio transactions that go along with that. So I think that — what would I describe it as, you close the seven-figure deals irregularly, but you discuss them constantly.

That “something else” Noss referred to was a deal for GoDaddy to resume selling Tucows’ expired domain name inventory.

(On a side note, Noss is recuperating from double hip-replacement surgery and I wish him a speedy recovery.)


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

WebMD can keep its IVI.com domain, panel rules

Domain Name Wire - Wed, 02/14/2018 - 17:18

Infertility company fails in cybersquatting claim for IVI.com.

A World Intellectual Property Organization panel has ruled against Spanish infertility medical company Equipo IVI SL in a dispute over the domain name IVI.com. Equipo IVI argued that WebMD was cybersquatting by owning the domain name.

WebMD did not respond to the cybersquatting complaint. Despite this, the panelist determined that WebMD did not register the domain in bad faith. This was primarily because the complainant did not show that it had trademark rights in IVI at the time IVI.com was registered in 1992.

It’s not clear when WebMD acquired the IVI.com domain name. The company was not founded until 1996 and DomainTools’ oldest historical record for the domain is from 2001. This record shows WebMD as the owner.

Had WebMD bothered to respond, it could have poked a lot of holes in Equipo IVI SL’s case. Here is one of the more laughable arguments in Equipo IVI’s filing:

The Respondent, by rejecting the Complainant’s offers prior to the filing of the Complaint and by keeping the disputed domain name inactive since the date of registration, is engaging in passive retention, clearly jeopardising the Complainant and preventing it from providing the products or services corresponding to its business activity;


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

Donuts acquires .Travel domain name

Domain Name Wire - Wed, 02/14/2018 - 14:00

Donuts acquires a sponsored top level domain name for the travel industry.

Top level domain name company Donuts announced today that it has acquired the .travel top level domain name from Tralliance Registry Management Company.

It is the 239th top level domain name that Donuts will operate, but this one is very different from the others.

.Travel is a sponsored top level domain name that was authorized by ICANN in 2005, well before the recent domain expansion took place. As a sponsored domain, it has restrictions not found in new top level domain names. While these restrictions have been watered down over time, registering a .travel domain requires more work than the other domains Donuts sells.

Registrants must have an affiliation with travel. Before registering a domain name they need to obtain a member number from the .Travel registry. This number must be provided to the registrar when registering a domain name.

Perhaps because of this added friction, many large registrars such as GoDaddy do not offer .travel domain names.

As of the end of October, EnCirca and Name.com were the top two registrars for .travel with 3,397 and 2,770 names respectively. There were about 18,000 .travel domains registered at the time.

I suspect that Donuts will work to remove the member number requirement and move fully to a post-dispute model in which people can challenge registrants for not meeting eligibility.

The acquisition should end the saga that .travel and its ownership have gone through over the past decade. It puts it in the hands of a well-capitalized registry that has many travel-related domain names such as .flights, .holiday, .tours and .vacations.


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Donuts’ new TLD renewal rates range from 55% to 72%
  2. Inside new top level domain company Donuts
  3. Donuts (finally) wins .Charity dispute, clearing path to .charity domain names
Categories: Domains

Cryptocurrency domains are no longer trending

Domain Name Wire - Tue, 02/13/2018 - 23:34

From total domination to “where did those go?”.

Verisign released its latest report of the top trending keywords in new .com domain name registrations, and something is noticeably absent for January: cryptocurrency terms.

For months, domain names including terms such as coin and crypto have been on the trending list. But this month none of the top ten spots include these terms.

There are a couple possible reasons for this.

First, the trending terms list looks at the percentage month-over-month increase in domains registered that contain the word. It’s harder to grow percentage-wise as the base gets bigger.

Second, crypto-related domain names have been largely picked over.

You might also argue that interest in cryptocurrencies is starting to wane with price drops, but I wouldn’t write that on a blog like this and have crypto bettors fill up the comments with hate comments.

So what took over for crypto? Take a look:

1. near
2. cell
3. dispensary
4. stem
5. claim
6. centers
7. hole
8. residential
9. nano
10. cane


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. For VeriSign, it’s 2009 all over again
  2. Trump drops, Bots soar in latest .Com report
  3. The .Com Cliff is .Coming
Categories: Domains

Donuts is shutting down HotKeys next week

Domain Name Wire - Tue, 02/13/2018 - 18:02

Parking company gets the axe.

Donuts is shuttering domain parking company HotKeys next week, the company announced in an email to clients today.

The new top level domain company acquired HotKeys when it bought Rightside last year.

The service hadn’t been marketed to domainers in a long time and mostly monetized large portfolios from direct relationships as well as Rightside’s own domain portfolio.

After Donuts sold the domain portfolio to GoDaddy, it probably didn’t make sense to continue operating the parking company.

Michael Blend founded HotKeys in 2001 and sold it (along with a portfolio of great domain names) to DemandMedia, which later spun out Rightside.

HotKeys is the second business that Donuts acquired from Rightside that it has announced will close. Last month it announced it was closing RegistrarStats, which had been on life support for many years.

The company is referring clients to Sedo.


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. HotKeys: The Domain Parking Service You Don’t Know Yet
Categories: Domains

Much Ado about Ado.com: Carrillo sues bus company after bad UDRP decision

Domain Name Wire - Tue, 02/13/2018 - 16:06

Domaining.com owner sues to retain ownership of Ado.com and asks for a finding of reverse domain name hijacking.

Francois Carrillo, the owner of domain blog aggregator Domaining.com, has sued (pdf) Mexican bus company Autobuses dr Oriente ADO, S.A. de C.V. after a UDRP panel ordered his domain Ado.com transferred. He is seeking the UDRP to be overturned and is asking for a penalty for reverse domain name hijacking.

The World Intellectual Property Organization UDRP decision came as a shock as the panelists handed over a valuable three-letter domain name to a Mexican company that Carrillo, who lives in France, said he hadn’t heard of when he bought the domain name. The decision also had misstatements about pricing of domain names.

The suit questions claims made by the bus company in its UDRP complaint such as the existence of U.S. trademarks. It also points out that the bus company’s lawyer in the UDRP was also an accredited UDRP panelist, suggesting potential bias by the three peer panelists. The ability for lawyers to serve as counsel in UDRP cases while also being accredited panelists is a big issue for UDRP fairness.

David Weslow of Wiley Rein LLP is representing Carrillo. Weslow has handled several similar cases that resulted in the original UDRP complainant paying to settle the case.

The case was filed in Denver because the bus company agreed to submit itself to jurisdiction there when it filed the UDRP; it is the location of NameBright, which is the registrar of record for Ado.com.


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Wow: check out this panelist’s scathing finding of Reverse Domain Name Hijacking
  2. Brazilian company guilty of reverse domain name hijacking
  3. Weeds, Inc, which is suing to get Weeds.com, engaged in reverse domain name hijacking
Categories: Domains

Bank files lawsuit after domain owner forwards domain to UDRP decision

Domain Name Wire - Mon, 02/12/2018 - 21:55

Marathon Savings Bank lost a UDRP for MarathonBank.com, so it’s trying a federal lawsuit instead.

Marathon Savings Bank, located in Wisconsin, has sued (pdf) Affordable Webhosting, Inc. for cybersquatting after losing a UDRP to get the domain name MarathonBank.com. The bank uses the domain name MarathonSavingsBank.com.

It filed a UDRP against Affordable Webhosting on September 27. A single-member WIPO panel determined that the bank “has not proved by a preponderance of evidence” that the domain was registered in bad faith.

After the UDRP decision, Marathon says that the defendant forwarded the domain to a website that featured Donald Trump’s tweets.

Marathon sent a cease & desist letter to Affordable Webhosting on January 26, 2018. At that point, the company decided to forward the domain name to the WIPO UDRP decision in the case.

The bank says “Such actions were clearly intended to annoy and harass Marathon”.

That’s an interesting claim to make given the result of the UDRP.

It’s worth noting that federal lawsuits are different from UDRP and the bank will have the opportunity to depose the domain owner.


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. WorldWide Media Sues to Retain SmoothMove.com
  2. Why BuyDomains’ lawsuit over FACI.com makes sense
  3. Lawsuit filed after Materia.com UDRP, and it’s an interesting case
Categories: Domains

Tips to avoid getting scammed

Domain Name Wire - Mon, 02/12/2018 - 16:00

Here are some tips to limit the chances you fall for a scam.

Domain investor Richard Dynas posted a story on NamePros yesterday about getting scammed in a domain name transaction. He paid for a domain name that a scammer didn’t own.

Dynas is embarrassed, and when you read his story you will understand why. There was not just a single red flag in this transaction; there was a sea of red flags. Burning hot red flags.

But we’ve all been scammed, suckered, or made a bad deal in life.

One story I tell is being duped out of twenty bucks in San Francisco. I was in line to enter a parking lot and the lot attendant was collecting the $20 entrance fee. The three cars in front of me paid, then it was my turn. I pulled up, he handed me a yellow dashboard ticket and asked for $20, and I handed it over.

As I was parking I saw the official parking lot company van pull in and the “attendant” ran off.

What just happened? That guy was the attendant. He had an official-looking windbreaker on. He had the yellow tickets. Everyone else paid him.

But we’d all been duped by some random guy who made $80 in about five minutes.

It was only $20 bucks, but you get that nasty feeling in the pit of your stomach when you get duped. And you learn lessons from it to make sure it doesn’t happen again.

So kudos to Dynas for posting his story. And here are some of my tips to reduce the chances that you get scammed in a domain name transaction:

1. Look at historical Whois. This is a must, especially when the domain has Whois privacy as in this case. Had Dynas looked at the historical records he would have seen a mismatch with the person he was dealing with. Perhaps the person would have explained away the difference…which is why, if the dollar amount is more than a threshold you’re comfortable with losing, I strongly recommend contacting the prior owner of the domain.

Many years ago I almost bought a stolen domain. Before I completed the transaction I viewed the historical Whois and contacted the prior owner. He told me that the domain was stolen.

I realize that DomainTools is expensive. But you can also get historical Whois records from DomainIQ for much less money. The money is worth it.

2. Understand that email addresses can be faked. Anyone can send email from many unprotected domains. The scammer in this case was clever; they sent “proof” from an email address at the domain that started with noreply@, so sending a message to it would likely bounce. Make sure you can send an email to the person’s email address hosted on the domain.

3. Talk on the phone. Talking to someone on the phone doesn’t prove that the person isn’t lying, but it can often tell you that the person is!

Perhaps the person you’re dealing with claims to be a woman who lives in Florida. They are a really a man who lives in Asia. When you ask to talk to them on the phone, they will decline because they know it will give it away.

I have a friend who owns vacation rental properties in Austin. His #1 tip to avoid getting scammed when renting a home on AirBnB or HomeAway is to talk to the person on the phone.

He told the story of someone who thought they had rented one of his houses for SXSW through Craigslist. The person had been duped, and he explained that if they insisted on talking to the scammer on the phone before “booking” the house, they likely would have avoided the scam.

4. Use Escrow, unless… Everyone has their own threshold on when to insist on using an escrow service. I disagree with the claim that you always need to use an escrow service. But 99% of the time it makes sense.

The exception is if you’re dealing with a large company and have a signed contract. You still might want to use an escrow service. After all, it’s very cheap. But large companies might have legal reasons for not using domain escrow services.

This brings up another point. I know one person who insists on signing a contract whenever he buys a domain, even when using escrow. It can add other protections. It’s a good idea…again, it’s a question of your threshold. If someone asks me to sign a contract when I sell her an inexpensive domain, I’ll weigh if it’s worth my time. But when the dollar amount is high, it’s a completely reasonable ask.


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Top Domain Name News Stories – March 2008
  2. #5 in 2017: The Chinese trademark scam
Categories: Domains

Newtek domain theft has major impact on customers

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

Customers have to make quick switch to avoid security risk and potential outages.

I frequently write about domain name theft. Usually, the only loss in the theft is the domain name. But it can be much worse.

Three domain names belonging to Newtek Business Services Corp. (NASDAQ:NEWT) were recently stolen, as Brian Krebs explains in a post today. Unfortunately, customers used these domain names to access and point to their web services, potentially leading to outages and leaked information.

Krebs details Newtek’s bungled response in his post, but let’s dig a bit deeper into the domain theft.

The three stolen domains were webcontrolcenter[dot]com, thesba[dot]com, and crystaltech[dot]com.

Looking at historical Whois records at DomainTools brings up many interesting points.

First, Newtek is a Tucows reseller and managed all of these domains through its reseller account. I wonder if it also helped customers register domains through its reseller account and if any customer domains were also susceptible to the hack.

Second, the thief or thieves moved the domain names to three different registrars: P.A. Viet Nam Company Limited, INET Corporation and GMO Internet, respectively. There are a few possible reasons for this:

  • There were multiple thieves
  • The domains were moved to multiple registrars to make it more difficult to recover them quickly
  • Three different registrars were used to reduce the chances of detection during the theft

Third, the theft of at least one domain occured a couple weeks ago and went undetected. DomainTools has a historical record for CrystalTech[dot]com dated January 31, 2018 that shows the domain had already been transferred to GMO.

Companies (especially web service providers) should always track their registrations through a service such as DomainTools or DomainIQ to be alerted if their domains change.

Fourth, all three domains had the same registrant contact email. This could have been a source of the hack, although NewtekOne.com, the company’s main domain name, was not stolen and used the same address.

Amazingly, Newtek’s stock opened up to begin the day. It has been relatively quiet about the domain theft, but it’s something investors should dig into to understand its impact.


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. DingBats.com Case Discusses Pool.com Lawsuit Over Domain Theft
  2. 8 Clues a Domain Name is Stolen
  3. Mrs Jello sues over stolen domain names
Categories: Domains

Google is upping the ante on SSL

Domain Name Wire - Fri, 02/09/2018 - 14:48

“Not Secure” will show on sites even if people aren’t filling out a form field.

Google is upping the ante on SSL to nudge more websites toward moving to https://

Take a look at the graphic above. The top image currently shows in the address bar in Chrome for websites that use http:// (i.e., they don’t have an SSL certificate).

The second image currently shows on sites that don’t have SSL whenever someone enters information into a form field on the page.

Starting in July, the latest version of Chrome will show the second notification for sites that don’t have SSL even if someone is not inputting information into a form field.

I’m not sure how many people notice the “not secure” label. But my guess is the next step after this will be to make it more obvious, perhaps in a red color. So it probably makes sense to suck it up and upgrade to SSL now.

It would be nice if Google made this a little easier. Two things it could do are 1) create a one-click WordPress plugin to change to https once a certificate is installed and 2) make it so you don’t have to create a separate instance in Google Webmaster Central when you switch to https.


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Type a new TLD in Chrome, and the browser will ask you if you really meant it
  2. SSL comes to landing page tools, but at a price
  3. Google adds more of its top level domains to HSTS preload list
Categories: Domains

Verisign results: Tax law implications and two topics that weren’t discussed

Domain Name Wire - Fri, 02/09/2018 - 14:13

Tax law will have big implications for Verisign.

Verisign (VRSN) reported fourth quarter and full year earnings after the bell yesterday.

Of note, the .com/.net base increased by 0.57 million domain names to 146.4 million. The company forecasted growth of 0.4 to 0.9 million for the quarter. For Q1, it forecasts 1.5 million to 2 million growth in the base.

Verisign has perfected its art of hitting at least the minimum growth prediction. It’s fairly easy for it to manipulate this with marketing dollars and specials across .com and .net to push registrations.

Because of the recent U.S. tax law changes, the company plans to repatriate $1.1 billion of cash that it has stashed in overseas subsidiaries. Despite having so much cash, the company has regularly borrowed money to buy back shares while keeping the cash safely offshore, outside the hands of the U.S. government.

It will now have to pay tax on money earned by these overseas entities because of the tax law changes. This will increase Verisign’s annual tax expense. Its interest deduction from borrowing money will also be limited. So the company is evaluating its entire capital structure.

It was the absence of discussion of a couple topics on yesterday’s conference call (and in recent quarters) that really struck me.

First, no one is asking about Verisign’s IDNs. It’s clear by now that those are a bust.

Second, all of that talk about monetizing intellectual property has disappeared. I suspect Verisign has decided to not ruffle feathers on IP and instead continue to work on ways to increase the price of .com domain names. Increasing prices slightly will have a bigger impact on its bottom line than a bit of IP wrangling.

Keep in mind that Verisign hired Phil Corwin last year. Corwin spent the last decade arguing against .com price increases on behalf of the Internet Commerce Association. Coincidence?


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

Latest domain news at DNW.com: Domain Name Wire.

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

Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. As .Com registrations surge, is Verisign a good buy?
  2. The .Com Cliff is .Coming
  3. .Com/.Net base grew by 1.47 million in Q3
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.