skip to content

News

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

Grow your business with podcasts – DNW Podcast #246

Domain Name Wire - Mon, 07/29/2019 - 15:30

A step-by-step walkthrough of how to leverage podcast guest appearances to grow your audience.

Want to grow your audience and business? One of the hottest things to do right now is to be a guest on podcasts. On today’s show, I’ll explain step-by-step how to leverage podcasts. This is a great opportunity for domain name companies and domain investors, as well as people who have built an online business. Learn more in this podcast guest guide.

Also: Verisign’s earnings, Whois spat resolved, private jet, and Web.com’s acquisition

This week’s sponsor: NameSilo. Use coupon DNWPod for $1 off your next domain.

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

© DomainNameWire.com 2019. 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. All about China with Raymond Li and Simon Cousins – DNW Podcast #95
  2. Paul Mockapetris, inventor of the DNS – DNW Podcast #100
  3. 7 ways to sell your domains – DNW Podcast #229
Categories: Domains

Royal Caribbean Cruises loses UDRP against James Booth for RCC.com

Domain Name Wire - Fri, 07/26/2019 - 15:46

Company uses RCCL.com for corporate email and some email was misdirected.

Picture of Royal Caribbean ships from the company’s website. The company lost a cybersquatting case it filed to get RCC.com.

Royal Caribbean Cruises has lost a cybersquatting claim it filed against domain broker James Booth of BQDN.com over the domain name RCC.com.

Booth has bought/sold about 250 three-letter domain names and acquired this domain with similar plans. A couple of years after acquiring the domain, he turned on an email catchall and found that people were emailing sensitive information intended for the cruise line to RCC.com. Royal Caribbean uses RCCL.com for its email addresses.

It was at this point that things get a bit confusing. Even though Booth is a broker himself, the case states that Booth hired a broker to contact Royal Caribbean about the misdirected email and inviting them to buy it. That overture stated:

“Do you want me to continue to forward these emails? / I think you have a major problem here, not just because of the confusion from your customers not getting their emails answered but also email security. At some point RCC.com is going to sell and the new owners may not be as nice to forward your info. / Let me know if you have time to talk this week.”

Booth admitted that it was “an arguably ill-considered solicitation.”

Of particular concern to Royal Caribbean is that Booth shared the emails with an apparent outside party (the domain broker). That’s a bad idea.

Still, the panel found that the domain was likely not registered to target Royal Caribbean, and instead because of the acronym value of RCC.com.

Zak Muscovitch represented Booth in the UDRP.

© DomainNameWire.com 2019. 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. Kevin Ham Wins Reverse Domain Name Hijacking Charge
  2. BuyDomains defends UDRP brought by Academy Sports
  3. Dialoga Servicios Interactivos, S.A. tries reverse domain name hijacking
Categories: Domains

Verisign .com/.net domain base increases by 1.34 million

Domain Name Wire - Fri, 07/26/2019 - 13:31

More cash in the coffers for .com registry Verisign.

Verisign (NASDAQ: VRSN) reported earnings for Q2 2019 yesterday.

The company had $306 million in revenue and $148 in net income. The operating margin was 65.9%, up from 63.8% in the same quarter last year.

.Com and .net domains increased by 1.34 million during the quarter, bringing the combined domain base to 156.1 million. 10.3 million new .com/.net domains were registered during the quarter, up from 9.6 million in the same quarter of 2018.

Renewal rates are trending slightly down, however.

Verisign narrowed its guidance for the year by shaving off the low end of its previous guidance.

On the investor conference call yesterday, analysts inquired about three things:

1. The status of .web – Afilias’ Independent Review continues to work through the process, and Verisign would like to participate despite not being a party to it. Verisign won .web in an auction through a deal with one of the applicants. Afilias was the runner-up.

2. .Com price increases – Verisign continues to negotiate with ICANN to try to incorporate the price increases the U.S. government granted into its existing .com contract.

3. .Org price increases – This was an interesting one. An analyst asked if ICANN’s approach to lifting price caps signals that it might relieve pricing controls further on Verisign. Verisign CEO Bidzos noted that he can’t speculate on what this means when .net comes up for renewal. He also noted that .com is a different animal because of the Cooperative Agreement with the U.S. government.

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

Related posts:
  1. Verisign: 9.2 million new .com and .net registrations last quarter
  2. Verisign announces another .net price hike
  3. How is .Com? Verisign discusses, and signs 11 IDN contracts
Categories: Domains

Tutorial: How to update DNS Records using GoDaddy API

Domain Name Wire - Thu, 07/25/2019 - 19:26

Alvin Brown provides a tutorial on how to use GoDaddy’s API to retrieve and update DNS records for a given domain with specified Type and Name.

Lately I’ve been experimenting with listing domain names for sale from my GoDaddy account using Sedo, one of the domain industry’s largest marketplaces for buying and selling domains.

While adding my domains to their system for listing is quite trivial, I quickly encountered how cumbersome Sedo’s ownership verification process is for each domain.

Ownership verification is likely not a problem when only listing a handful of domains at one time. Simply add a DNS record for each domain at your domain registrar, and that’s it.

However, if you’re adding more than 5 domains to Sedo, then you’ll want to rethink how you go about Sedo’s ownership verification process.

Most people opt for bulk updating name servers for bulk domains entered into their Sedo account. But what about those of us that don’t care to change name server settings or don’t want to park our domains with Sedo?

Today’s tutorial will help address this very question by showcasing how to use GoDaddy’s API to update DNS records for a given domain with specified Type and Name.

By the end of this tutorial, my hope is that you’ll be able to create your own bulk update tool for Sedo ownership verification if your domains are managed by GoDaddy.

Getting Started with GoDaddy API

Before diving into the details, I won’t spend much time, if any at all, covering how to get started with GoDaddy’s API.

If you’re new to using GoDaddy’s Developer Portal and API, then I recommend reviewing the following resources:

Let’s get started!

Methods for Adding and Replacing GoDaddy DNS Records

As displayed in the image below, a number of methods are shown for adding and replacing DNS Records for a given GoDaddy Domain using the API.

This tutorial focuses on the following method (as shown below in the image) for replacing all DNS records for the specified Domain with the specified Type and Name.

I chose this method due to Sedo’s ownership verification requiring that a TXT or CNAME record be created using a verification ID as provided by Sedo.

Today’s tutorial instructs you how to add a TXT, although you could easily change to CNAME too, record to a GoDaddy managed domain for Sedo to verify your ownership.

Setting up required and optional variables

Open a text editor, name and save the following file: dns-recorder.php.

The first action is to create a variable (i.e., $domains) containing an array (i.e., see examples below) of your GoDaddy domains listed at or soon to be listed at Sedo.

$domains = array(
“mckinneydigital.com”,”dallasdigital.com”,”austindigital.com”
);

If only one domain, then the code would be as follows:

$domains = array(
“mckinneydigital.com”
);

Next, create a foreach statement to iterate over each of the array values in the $domains variable. The foreach statement ensures that a DNS record is added to each domain instead of only the first domain.

foreach($domains as $domain){

//additional code here

}

Within the foreach statement, your GoDaddy API credentials must be defined as variables as well as the domain, and necessary DNS Record variables and their respective values.

It’s essential to add your respective API Key and Secret, or else this tutorial is dead in the water.

As for defining variables for DNS records, the following variables and their values should be defined:

$dns_domain – using PHP’s strtolower method, pass the $domain variable as its argument, which ensures all domains are lowercased.

$dns_type – set the value to TXT or CNAME; additional values are: Nameserver, A, MX, SRV, AAAA, CAA.

$dns_name – set the value to @.

$dns_data – set data value to your Sedo verification id.

$dns_port – set port value to 80 or 443.

$dns_priority – set priority value to 10 or an increment of 5.

$dns_protocol – set a protocol string value; set to ’string’ for this tutorial as its not required.

$dns_service – set a service string value; set to ’string’ for this tutorial as its not required.

$dns_ttl – set til value to be 600 or any one of the following: 1/2 hour, 1 Hour, 12 hours, 1 Day, 1 Week, Custom.

$dns_weight – set this value to 10 or an increment of 5.

With aforementioned variables defined and values set, define and set the value of one last variable: $dns_records.

The $dns_records variable contains the last seven variables as a json object or string (see below).

$dns_records = “[{\”data\”: \”$dns_data\”,\”port\”: $dns_port,\”priority\”: $dns_priority,\”protocol\”: \”$dns_protocol\”,\”service\”: \”$dns_service\”,\”ttl\”: $dns_ttl,\”weight\”: $dns_weight}]”;

Making the call to add DNS Record

With necessary variables and values set, we’re now ready to instantiate the GoDaddy API call to add the DNS record using a user-defined function named addDNSRecord.

Define a variable named results and set it equal to addDNSRecord. This addDNSRecord function does the heavy lifting to make the GoDaddy API call based on passing the following four variables passed as arguments in their respective order: $dns_domain, $dns_type, $dns_name, and $dns_record.

$results = addDNSRecord($dns_domain, $dns_type, $dns_name, $dns_records);

Error checking the addDNSRecord function

The final step of this tutorial is adding a bit of error checking. While you can choose to dive deeper in providing greater detail, I’ve chose to display a simple pass or fail text message based on whether or not the results variable returns a value.

if(!$results){
echo “All good in hollywood for the following domain: $dns_domain
“;
} else {
echo “Houston, we have a problem with the following domain: $dns_domain!”;
}

If a value is returned when the API call is made, then the success message is displayed and reads as follows:

All good in hollywood for the following domain: < your domain displayed >

If API call is made in error, then the fail message is displayed and reads as follows:

Houston, we have a problem with the following domain: < your domain displayed >

If API call is successful, then you should be able to view the newly added DNS record containing Sedo verification id for your respective domain(s) in GoDaddy’s Domain Manager.

When putting the code together in its entirety, not including the functions section for addDNSRecord, there are roughly 40 lines of code.

And that’s all there is to this tutorial.

addDNSRecord function

The addDNSRecord function is the sole function executing the heavy lifting to add DNS records to a given domain.

One thing to note is the following GoDaddy API url used:

https://api.godaddy.com/v1/domains/$DNS_domain/records/$DNS_type/$DNS_name

In addition, this tutorial uses the PUT request method unlike previous tutorials that have used GET and POST request methods.

You can likely use this function in the future and simply make minor modifications to url value and request type variables.

Closing thoughts

I encourage you to download the tutorial code, make necessary modifications, and see where this tool takes you.

DOWNLOAD dns-recorder.zip for GoDaddy Domains API

This tutorial can easily be modified to add a simple HTML form interface likely using Bootstrap or basic HTML5.

Please don’t hesitate to leave comments should you have questions or encounter technical challenges implementing tutorial.

Thanks and that’s all for now!

© DomainNameWire.com 2019. 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. Sedo expands distribution partnership with Go Daddy
  2. Sedo does the promotion that domain registrars should do
  3. Tutorial: How to retrieve a list of your GoDaddy Domains
Categories: Domains

Whois API removes .NZ records to settle lawsuit

Domain Name Wire - Thu, 07/25/2019 - 14:18

Whois data seller quickly folds after facing lawsuit.

Domain Name Commission (DNC), which manages New Zealand’s .NZ namespace, has dropped a lawsuit it filed against Whois API after the parties quickly settled the matter.

Domain Name Commissioner Brent Carey released this statement to Domain name Wire:

We are very pleased to announce that WhoisAPI and DNCL have been able to settle their dispute without the need for ongoing litigation.

Our agreement has resulted in WhoisAPI deleting all historical .nz WHOIS records and any related data or records that were formerly stored in its database or otherwise retained in its systems.

This is good news for .nz registrants and protection of their domain name privacy rights. WhoisAPI will not publish any non-current .nz WHOIS data.

We commend WhoisAPI on their open dialogue and good faith negotiations which led to the settlement. We hope more companies will take domain names owners privacy as seriously as WhoisAPI has now done.

That last sentence is obviously directed at DomainTools. DNC filed a lawsuit against DomainTools last year that is still dragging on in court.

© DomainNameWire.com 2019. 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. Appeals court affirms injunction against DomainTools
  2. DomainTools appeals injunction decision in .NZ case
  3. .NZ domain manager sues Whois API
Categories: Domains

15 recent end user domain name purchases

Domain Name Wire - Thu, 07/25/2019 - 13:32

A snowboard accessory brand, a company that builds bunkers, and a gardening company bought domain names.

Attention all preppers: one of this week’s end user domain buyers will help you build a fallout shelter. Hardened Homes bought its matching domain name.

There are some other nice sales, and the seller of the top end user domain did quite well.

Here’s a look at sales to end users that recently closed at Sedo. See prior end user lists here.

GreenCarpet.com €33,000 – The top overall sale of the week forwards to MesseTeppich.at, an Austrian company called The Carpet Company.

Mondia.com $30,000 – Mondia uses the domain name Mondia.io. It forwards the .com to the .io. It takes a while to understand what the company does based on its website, but it seems to help companies connect with their customers by creating games and other digital experiences.

Tinka.com $25,000 – A TransIP customer acquired the domain. Perhaps MJR Brands?

HardenedHomes.com €6,000 – Need an underground bunker? Bomb shelter? Hardened Homes, which uses the domain name HardenedStructures.com, bought this domain. The company will help you fortify your home.

GRS.be €4,750 – GRS is a gardening company. It uses the domain name GRS.nl.

Campings.se €4,000 – This site is still in development for a tourism company focused on camping and the now ever-popular glamping. It owns a lot of relevant domains such as Camp.uk.

RydeOn.com $3,950 – Eaziie, Inc. bought this domain. It’s a startup in the ride sharing arena whose platform allows hotel employees to arrange a taxi, limo, or a shuttle for their guests with a single click.

PropertyAdviser.in $3,900 – An Indian real estate property site.

EnerBuild.com €3,900 – This Swiss company specializes in energy-efficient building design and construction.

Squidy.com $3,350 – Purchased by Progressive Print, a printing and mail advertisement company.

ProteoGenix.com $3,000 – A French medical company, ProteoGenix, bought this domain. It currently uses the domain ProteoGenix.science. That’s how .science should be used, but the top level domain’s previous owners sold out to spammers to pump up domain registration numbers.

MyBasic.eu €2,500 – An e-commerce site for a children’s clothing brand based in Poland.

Astrologie.eu €2,000 – Forwards to Wahrsager.de, a German astrological purveyor of books, card sets, jewelry, gems and more.

MedicCenter.de €2,000 – Forwards to Medic-Center-Nuernberg.de, a medical care facility in Nuremberg, Germany.

TremblingGiant.com $2,000 – Trembling Giant is a brand of snowboard bags and gear. “Trembling giant” is a nickname for the Aspen tree.

© DomainNameWire.com 2019. 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. 17 end user domain name sales including Hallmark
  2. 14 End User Domain Name Sales
  3. 17 end user domain name sales up to €50,000
Categories: Domains

It’s time to take PrivateJet.com off of all of those domain sales lists

Domain Name Wire - Wed, 07/24/2019 - 20:06

It shouldn’t have been on any lists to begin with.

According to a lot of lists of top domain sales, PrivateJet.com sold for $30 million in 2012.

They’re basing it on this press release.

Smart people didn’t log this domain sale that was for cash and equity. You can put any value you want on equity.

But the sale might not have happened at all, equity or not.

Take a look at a new lawsuit filed by Don’t Look Media. (Lawsuit file) The company that allegedly sold the domain for $30 million back in 2012 says it still owns the domain, and it’s suing another party for allegedly not holding up its end of the bargain in a development/monetization deal.

The dollar numbers involved in the form of guarantees are small potatoes for a $30 million domain name.

The bottom line: the same company that owned the domain before the 2012 “sale” still owns it. So you can cross this domain off your list if you haven’t already.

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

Wix reports Q2 2019 earnings, upgrades outlook

Domain Name Wire - Wed, 07/24/2019 - 15:45

Company upgrades outlook for the rest of the year after topping its own forecast for Q2.

Website builder Wix (NASDAQ: WIX) reported earnings today and raised its financial outlook for the rest of the year.

For the second quarter of 2019, Wix reported revenue of $185.4 million, above its forecasted range of $182-184 million and up 27% year-over-year. Its collections (which are essentially cash receipts) hit $199.6 million in the quarter, up 25% year-over-year.

The company added a net 132,000 paying subscribers in the quarter, bringing its total to 4.3 million. It also added 5.7 million registered users. Most registered users use the product for free; about 3% are paying users.

The net adds number is well below the 180,000 it added in the first quarter of the year, which is usually a good quarter for people starting websites. But it’s also a lot lower than its results in Q2 of last year when it added a net 205,000 paying customers. That might be because it eliminated its least expensive plan, which let customers connect a domain name to a site for $5 a month. The cheapest plan is now $13 a month

I built Comptroller.com on Wix. You can read about my experience here.

© DomainNameWire.com 2019. 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. Wix posts $146.1 million revenue, 205k net new paying customers in Q2
  2. Wix nets 180k paying subscribers in Q1
  3. Catching Up with Weebly Cloud’s Chris Sheridan
Categories: Domains

This JUUL cybersquatting case is interesting

Domain Name Wire - Wed, 07/24/2019 - 15:19

The vaping company lost a challenge to a website reselling its products.

JUUL failed to take down a site that resells its products. Picture from Juul.com.

JUUL Labs, Inc., which manufactures and markets vapor nicotine products, has lost a cybersquatting dispute it brought against a company that sells Juul products at BuyJuul.com.

It filed the case with National Arbitration Forum and the majority of the panel found in the Respondent’s favor.

The case is interesting for two reasons.

First is the question of using a trademarked name in a domain name when a company resells the trademark owner’s product. In this case, site owner Direct Eliquid LLC is not an authorized reseller of Juul. Instead, it says it buys its products from an authorized distributor and resells them online.

Writing about such cases, the panel notes:

A respondent’s use of a Complainant’s trademark in a disputed domain name in the resale of a complainant’s products constitutes a bona fide offering of goods or services in accord with Policy ¶ 4(c)(i) where the respondent actually offers the goods or services at issue, the respondent uses the site to sell only the legitimate trademarked goods, the site accurately discloses the registrant’s relationship with the trademark owner, and the respondent does not try to corner the market in all domain names.

Juul claimed that the website was selling “unauthorized” or counterfeit versions of its product. It also claimed that it might be a phishing site that doesn’t actually sell products at all. But Juul provided no evidence of this and the domain owner vehemently denied it.

Second, one of the three panelists wrote an odd dissenting opinion. He seemed to take issue with how prominent the site’s disclaimer about its relationship with Juul Labs should be displayed. That may be OK, but the end of his complaint is not:

Finally, I note that the Respondent is not re-selling harmless consumer products. The Respondent is re-selling the highly addictive nicotine drug. Although I would find the Respondent’s disclaimer inadequate for any re-seller’s website, an effective disclaimer is particularly imperative for consumers to make informed judgments as to the risks associated with making purchases from non-authorized merchants of addictive products.

The majority of the panel pointed out that this is not an acceptable position for a UDRP panelist to take:

Our dissenting colleague’s concern for the health of the consumers of the Complainant’s products is shared by the Majority. However, at this time, such products are legal to be sold anywhere in the U.S. (except San Francisco[i] and Livermore, CA, so far) and the parties’ sites appear to comply with current FDA rules regarding nicotine addiction warnings. A UDRP Panel is not empowered to make moral, medical, scientific, political judgments regarding legal goods or services.

The majority also pointed out that Juul has been running full-page ads in the New York Times with tiny disclosures that it paid for the ads, which is a bit ironic.

© DomainNameWire.com 2019. 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. Cybersquatting lawsuit filed against AnnualCreditReport.com typos
  2. More cybersquatting cases but fewer domains at WIPO in 2018
  3. Farrer & Co law firm loses cybersquatting dispute
Categories: Domains

Web.com buys Dreamscape for USD $73 million

Domain Name Wire - Wed, 07/24/2019 - 12:11

Registrar buys registrar with big presence in Australia.

Web.com bought the company that owns CrazyDomains

Web.com is bolstering its business Down Under.

The domain registrar and hosting company is buying Dreamscape Networks Limited (ASX: DN8) for AUS $105.2 million, or about USD $73 million. The company employs 600 people.

Dreamscape is known for its flagship registrar CrazyDomains, which focuses on the Australian market. It also owns Singapore’s Vodien, which it bought for USD $23 million in 2017.

The company had total 2018 fiscal year revenue of $61.6 million and a net profit after tax of $2.7 million. It reported an adjusted EBITDA of $10.3 million. For the second half of calendar year 2018, the company had revenue of $35.5 million.

Its revenue is split fairly evenly between domain names and hosting services.

The acquisition price is at a 32% premium to the closing price of Dreamscape shares on July 19.

The companies hope to close the transaction by October.

© DomainNameWire.com 2019. 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. New TLDs (.XYZ?) boost Web.com’s bookings
  2. Web.com gets Whois Privacy patent
  3. Web.com to go private in $2 billion acquisition
Categories: Domains

Namecheap files reconsideration request over removing .Org, .Info price caps

Domain Name Wire - Tue, 07/23/2019 - 18:48

Company asks ICANN to reconsider its decision to remove price caps on some legacy top level domains.

One of the largest ICANN-accredited domain name registrars has filed a Reconsideration Request (pdf) with ICANN over its decision to remove price caps in its renewed contracts for .org and .info domain names.

Namecheap filed the request as a party that will be adversely affected by uncontrolled price increases. It also says it’s filing on behalf of domain registrants.

The complaint outlines what many people have already stated: removing price caps from legacy TLDs adds extreme uncertainty to domain registrants, switching costs for domains are high, and ICANN seemingly ignored public input. The company wrote:

Namecheap is submitting this reconsideration request to protect the rights and interests of Namecheap’s customers and the entire internet community. Price caps for legacy TLDs have been an integral longstanding foundation for the domain name marketplace, and removing them will result in uncertainty and confusion at a minimum, and in the worst case, increased costs for domain registrants worldwide.

I suspect that legal action or an antitrust lawsuit will be required to get ICANN to actually reverse course.

Based on the timing of the filing, it’s possible that ICANN’s board will have to vote on the Board Accountability Mechanism Committee’s recommendation on the request at the end of the ICANN meeting in Montreal this November. I’m sure the price hikes will be a big discussion during that meeting.

© DomainNameWire.com 2019. 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. .Org Domain Name Prices to Jump 10%
  2. Court orders Tucows to transfer 3.2 million domains to Namecheap
  3. Digging into Tucows’ annual report
Categories: Domains

A quick fix to GoDaddy invalid request errors

Domain Name Wire - Tue, 07/23/2019 - 15:56

Getting invalid request errors? Trying going incognito.

I’ve recently run into a few errors at GoDaddy that required a call to my account rep, and I’ve learned a quick tip that can help resolve the errors.

When clicking through links to confirm contact updates while receiving domain names from another investor, I kept getting errors that read “Given request is invalid. If you feel this is incorrect please try again.”

I tried a couple of things to get it to work, including resubmitting my original request. But there’s a simpler solution to try first: use a private browsing window.

Apparently, these errors can be caused by caching. If you copy the link in the email to a private browser window, such as incognito in Google Chrome, it usually resolves the problem. It worked for me.

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

Related posts:
  1. GoDaddy auction data provide early indication of new TLD demand and values
  2. Domain name revenue barely budges at GoDaddy
  3. .Com slips at GoDaddy
Categories: Domains

A synopsis of new top level domains

Domain Name Wire - Tue, 07/23/2019 - 14:32

PIR’s take is simple but on point.

Like other new TLDs, .ngo domains aren’t exactly flying off the shelf.

What is the future of new top level domain names? Is there a tipping point when they go mainstream? Is it just a matter of time? Or, perhaps, they will continue to be sideline players in the domain name ecosystem.

Last week I wrote about Public Interest Registry’s (PIR) annual report. The non-profit operates .org, as well as a handful of new top level domains: .ngo, .ong, and several internationalized domain names.

On the one hand, it’s a lot like Verisign in that promoting the inherent value of legacy top level domains is to its benefit. On the other hand, it made a bet on new top level domains that hasn’t panned out.

.Ngo and .ong have just over 3,000 registrations each. Its internationalized domain names have even fewer.

PIR had big ambitions for new top level domains. And it’s current CEO was the founder of the biggest new TLD company, Donuts.

But like others, PIR has been disappointed with the adoption of new TLDs.

It’s with this background in mind that I found PIR’s take on new top level domains in its report interesting. After providing background on new TLDs and that they have been available for many years, the report states:

It must be noted, however, that relatively few of these new gTLDs have achieved significant market share.

Even amongst the relatively large new gTLDs, a number of these relied on free registrations to grow their base of domains under management (“DUM”). In many cases, as each registration anniversary passes a significant percentage of their base does not renew. Not only does this put pressure on the new registry operators, it also raises doubt about the long-term value of many new top-level domains–which in turn depresses registrations and renewals, further straining the viability of these extensions.

That’s a fair take from a company that bet on new top level domains.

 

© DomainNameWire.com 2019. 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 Registry/Registrar Sales Channel with Jay Daley – DNW Podcast #202
  2. Battle Erupts Between Domain Registries and Registrars
  3. .Org Eyes Leadership Role in IDN Top Level Domain Names
Categories: Domains

Feds start forfeiture proceedings against 500 domains used in prostitution ring

Domain Name Wire - Mon, 07/22/2019 - 21:20

Whois and registrar records connect the dots between domain names used in prostitution crime.

The United States government has filed an in rem action against 500 domain names for forfeiture that it says were used in prostitution and sex trafficking ring.

Over a period of six years, the conspirators paid over $25,000 to register the domains through Domain.com, the suit states. I reviewed the list of domains and found that they were almost all registered at either Domain.com or HiChina.

It’s interesting to read about how the FBI connected the dots between the domain names. It used as much publicly available Whois information as it could, while also connecting the dots using DomainTools and records from the registrars and hosts. Here’s the description from the FBI about how it uncovered the domain names used in the ring:

On or about November 2018, the FBI accessed publicly available information regarding twenty-five domains associated with the email address supermatchescort@gmail.com.

Using Domaintools—an open source tool that queries WHOIS records, passive Domain Name Service (DNS) data, IP addresses, hosting data, and other DNS information—
investigators learned that the twenty-five domains were hosted on IP address 64.50.176.48, along with hundreds of other domains.

Records from Domain.com revealed that for all twenty-five domain names, the subscriber was Weixuan Zhou, with an email address of rastait_mz@hotmail.com, a telephone number of 213-431-0920. The billing information for this account showed the card holder name as Weixuan Zhou and a billing address: ti yu lu no. 613 Guang Zhou, China.

Most of the other hundreds of domains hosted on the same IP address shared the same or similar registration information: registered to Weixuan Zhou through Domain.com, LLC, with historical registrant email information identified as bata_intl@hotmail.com or rastait_mz@hotmail.com.

Credit card activity shows Weixuan Zhou paying Domain.com for these domains from August 2012 to June 2018. Finanacial records for Zhou, from August 16, 2012 through June 1, 2018, show payments made via credit card to Domain.com totaling $11,202.04. One specific example shows that Zhou’s Wells Fargo credit card made multiple payments to Domain.com in September 2014. This credit card’s September 2014 balance was paid down from Weixuan Zhou’s Wells Fargo checking account. The source of these funds originated from cash deposits at banks in Texas, Colorado, Oregon, Washington, and California.

80. Records from PayPal showed that beginning on or around February 15, 2018, and continuing through October 10, 2018, the PayPal account linked to rastait_mz@hotmail.com sent
147 transactions totaling $6,150.14 to Domain.com. The subpoena return also showed on or around January 31, 2016, and continuing through September 2017, the PayPal account linked to bata_intl@hotmail.com sent 169 transactions totaling $10,241.74 to Domain.com. The total payments sent to Domain.com from Zhou’s two PayPal accounts were approximately $16,391.88

 

 

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

Avoiding stolen domains with Josh Reason – DNW Podcast #245

Domain Name Wire - Mon, 07/22/2019 - 15:30

A cautionary tale about stolen domain names.

Buying a stolen domain name can lead to a heap of legal trouble, not to mention losing a lot of money. In this episode, I chat with domain investor Josh Reason about a stolen domain name he almost bought. He explains the due diligence that raised several red flags and how he confirmed the domain was stolen. Fortunately, the story has a happy ending.

Also: Patriotic domains, lawsuit update, .London, Afilias’ .org deal, and .GOP

This week’s sponsor: Name.

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

© DomainNameWire.com 2019. 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. Meet Erik Bergman, who paid $900k for Great.com – DNW Podcast #182
  2. Sandeep Ramchandani, CEO of Radix – DNW Podcast #183
  3. Building Great.com with Erik Bergman – DNW Podcast #236
Categories: Domains

Facebook takes down fake cryptocurrency domain as Libra looms

Domain Name Wire - Mon, 07/22/2019 - 15:05

Site was used in phishing scheme.

Facebook has successfully taken down a fake site passing off as Facebook claiming to offer a cryptocurrency. The move comes as Facebook prepares its Libra cryptocurrency.

The company filed a cybersquatting complaint against FacebookToken(.)org and ICO-Facebook(.org).

While neither currently resolve to a website, Facebook’s attorneys noted that the first domain previously resolved to a website that showed Facebook’s logo with the words:

The future is now – FACEBOOK TOKEN – FACEBOOK ICO!

FACEBOOK present FACEBOOK, the representative cryptocurrency of the FACEBOOK Blockchain.”

The domains were registered last year before Libra was announced.

It seems that FacebookToken(.)org was used as a phishing site and some browsers blocked users from visiting it.

© DomainNameWire.com 2019. 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. USPTO Grants Extension to Facebook in Fight with American Farm Bureau over FB
  2. Facebook Close to Settling Long Running Dispute Over “FB”
  3. Facebook Registers FBPAC Domains Previously Owned by American Farm Bureau
Categories: Domains

Cayenne Sex: Porsche tries to take down escort’s website

Domain Name Wire - Fri, 07/19/2019 - 15:02

Car company was upset about escort’s website that referred to Porsche’s SUV.

The car company Porsche filed a cybersquatting complaint against an escort service’s website but ended up flaccid.

Porsche was upset that an escort service used the domain name CayenneSex(.)com. Porche makes an SUV called the Cayenne. And it was clear that the sex service’s owner thought about the car company when creating the site. An archive of the site (translated into English) notes “Hot as the Porsche & Sharp like the Chili Pepper!!!”

But World Intellectual Property Organization panelist John Swinson determined that Porsche didn’t show that the escort service lacked rights or legitimate interests in the domain. He said the reference to Porsche was fairly nominal and perhaps the chili pepper was more important.

Swinson had some fun with this case, doing some of his own research into peppers and sex:

The Panel notes that, while the term “cayenne” is indeed a trade mark owned by the Complainant, perhaps even a well-known or famous one, it is also a type of chilli pepper which is known for being particularly hot or spicy. (It is even apparently believed by some that the aphrodisiac power of hot chilli peppers can be somewhat amazing.)

Even though it lost the case, Porsche might have succeeded in its goal. The domain name no longer resolves to a website.

© DomainNameWire.com 2019. 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. FIFA wins FIFA.net cybersquatting claim
  2. Defunct app maker hit with reverse domain name hijacking
  3. BTSA.com: Cybersquatting or RDNH? You decide.
Categories: Domains

Appeals court affirms injunction against DomainTools

Domain Name Wire - Fri, 07/19/2019 - 12:40

DomainTools must take down .NZ Whois records while lawsuit proceeds.

The United States Court of Appeals for the Ninth Circuit has ruled in favor of .NZ domain manager Domain Name Commission in a fight against DomainTools.

Domain Name Commission (DNC) sued DomainTools last year for harvesting New Zealand’s .NZ Whois records for its service. A Federal District Court granted a preliminary injunction against DomainTools that prevent DomainTools from collecting more .NZ Whois records and required it to remove previously published records while the lawsuit proceeded.

DomainTools appealed against the injunction, but the appeals court just affirmed (pdf) the lower court’s decision. This means that DomainTools will have to comply with the injunction while the lawsuit proceeds.

DNC recently filed a similar lawsuit against Whois API.

© DomainNameWire.com 2019. 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. DomainTools appeals injunction decision in .NZ case
  2. New Zealand’s .Nz namespace gets preliminary injuction against DomainTools
  3. .NZ domain manager sues Whois API
Categories: Domains

MMX settles .London deal, plans share buyback

Domain Name Wire - Thu, 07/18/2019 - 15:46

Company can finally put .London fiasco behind it.

MMX, aka Minds + Machines Group Limited (AIM: MMX), announced preliminary results for the first half of 2019 today. It also made two big announcements.

Cash inflows in the half were $8.6 million compared to $6.3 million in the same period last year. The company received $1.6 million from losing top level domain auctions. It also says that the ICM Registry portfolio of domains (adult domains including .xxx) has stabilized and the company believes it can make them grow going forward.

Looking beyond the numbers, MMX made two big announcements.

First, it has made an agreement on one “legacy contract” that should settle it once and for all. While the company doesn’t identify which TLD the contract covers, it’s an open secret that it’s .London.

The company will make a one-time payment of $5.1 million to cover all of its liabilities on the .London contract. That’s better than its current estimated liability of $7.9 million. .London will go down as one of the worst new TLD deals ever, and having it behind the company will be a big boost.

Second, the company is going to use up to £1 million of its cash reserves to buy back shares. This should help put a floor on the share price for a while. Shares have traded at about 5.0-6.5 pence for the past six months.

© DomainNameWire.com 2019. 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. MMX releases 2015 report, discusses go-forward strategy
  2. .VIP gets 75% renewal rate for early registrations
  3. Domain company MMX reports earnings
Categories: Domains

Marketing a Teenage TLD

Domain Name Wire - Thu, 07/18/2019 - 13:30

[Editor’s note: This is a sponsored post by Lori Anne Wardi of Neustar]

Hi, my name is Lori Anne Wardi and I’m a domain junkie.

I’ve been buying, selling, studying, developing, dreaming about, promoting and preaching the bible of domain names since 2000. With many years as a domain investor under my belt, I got the opportunity to join the founding team of .CO Internet in 2009 as the Director of Marketing. From 2010 through today, it has been amazing to watch .CO grow from 28,000 domains under management to well over 2.2 million – and become the domain of choice for many of the world’s leading innovators, entrepreneurs and startups.

In 2014, when .CO Internet was acquired by Neustar, this born and bred New Yorker was given the chance to serve as the General Manager for the launch of New York City’s .nyc domain.  Working with the Neustar team to help turn the greatest city brand in the world into the one of the greatest city TLDs in the world was beyond rewarding, amidst all of the excitement and novelty of the new gTLD program.

Launching a brand and building a community around a domain extension is the best kind of challenge – it pushes your creative and strategic brains at the same time and forces you to think outside the box. But not every domain extension has the luxury of starting with a blank slate. Let’s take the .US domain, for example.  With 17 years under its belt, it’s hardly a brand new, baby namespace. So exactly how does a teenage TLD, like .US, stand out in a marketplace with more than 1,000 shiny new competitors?

Keeping .US fresh after 17 years

I know that the topic of .US marketing has occasionally inspired some very, shall we say, “spirited” commentary by domain investors. I mean, I read all the domain blogs too!  I get it, and it’s for good reason. As investors, we want to know that the TLDs we invest in are being well managed and marketed, and are building an engaged, loyal customer base of end-users in today’s increasingly crowded and complex marketplace.

After 17 years as the .US Administrator, there are a host of different strategies and tactics that Neustar’s marketing team uses to keep .US fresh, relevant and in demand by end-users. I could rattle on about how we use things like programmatic advertising, paid search, influencer marketing, retargeting, content marketing, and the like. But don’t worry, I won’t bore you with all the gory details. My goal today is just to give you a quick flyover view of our approach to defining and engaging with the .US target market.

’Micro-targeting’: The many faces of .US

It is marketing 101 that you need to clearly define your target market for any product, service or brand. As the country code domain extension for the United States of America, our most obvious end-user target market is, you guessed it, American businesses, organizations and individuals.

While “Americans” are obviously a cornerstone of our marketing, if our marketing whizzes had just written “America” next to “target audience” and patted themselves on the back for a solid day’s work, I suspect our marketing campaigns would go over like a led balloon.  Luckily, that has not been the case.

Instead, our team has developed a ‘micro-targeting’ approach; essentially, breaking our audience down into niche segments that each have unique and interesting motivations for using .US domains – and then building creative, relevant campaigns for each of these groups.

Some of these groups are attracted to the national pride and patriotism of the .US domain, others we’ve reached by thinking laterally about the TLD and leaning into the use of the word “us” to build special campaigns to represent community, connection and relationships.

More than just registrations, the ultimate goal of our micro-targeting is to ensure that there is genuine, meaningful usage of the .US domain, which ultimately is one of the best barometers for domain registries in assessing the health and viability of any namespace. Here are just a few examples of the unique end-user target markets we engage with as part of the .US community.

Small businesses – Dream with .US

SMBs in the USA are the bread-and-butter for .US domains. More than just a domain, .US supports small and medium sized businesses with tools and resources to help business owners launch and manage their websites, including step-by-step guides on topics ranging from choosing a domain, to lead generation, to social media and SEO. To spread the .US message to SMBs, we participate in a variety of business focused tradeshows and events, and leverage popular promotional channels like podcast advertising, social media and search engine marketing, among other things.

Political & civic engagement – Campaign with .US

Democrat or Republican, liberal or conservative, or everything in between, for political candidates, advocates and activists in the US of A, the .US domain is clearly a perfect match. Our “Campaign with .US” initiative helps these highly-engaged and passionate people and groups connect their cause(s) with their country through a .US domain.  Since there are so many options available for ad targeting based on job title, group association and user search history that indicates political involvement, we have the opportunity to be hyper focused in our approach and deliberate in our messaging.

Engaged couples – This is .US

One example of how we have used the concept of “us” to market the .US domain is by tapping into the wedding website market. Our “This is .US” campaign encourages newly engaged couples in the United States to create their wedding website on a .US domain, and to grow their website as their relationship and family develops. There is a wealth of behavioral and interest targeting data available to identify those preparing for an upcoming wedding, so we can be sure to reach the right people at the right time with our message.

Families – Thankful for .US

Again, emphasizing the word ‘us’, our “Thankful for .US” campaign encourages American families to secure their personalized family web address on .US domain.  A family web address can be a place to share your family story or a platform to keep in touch with long-distance or extended family members whether through building a website or creating a family email group. There’s a strong case that family websites and emails are more personal, accessible and private than many popular social media sites, which let’s face it, are increasingly being criticized for harvesting our personal family data in sometimes mysterious (and often unwanted) ways.

 

The Story of .US

At the end of the day, the best kind of marketing is the kind you don’t do yourself: word of mouth. Building a sense of community, ownership and loyalty around the .US domain enables us to let our satisfied customers tell their stories — promoting .US in the process.

Our recent “Story of .US” video campaign featured real .US customers from a wide array of backgrounds showcasing their businesses and brands – and explaining their affinity for the .US domain in their own words. From the multi-billion dollar tech behemoth Zoom.US, which just had the most successful IPO of 2019, to a group a high-schoolers who have started their own web development business — it’s extremely gratifying for us to see and hear real customers enthusiastically sharing their .US stories with the world.

Please take some time to watch some or all of the videos in “The Story of .US” campaign – you can find some of them below, or all of them on our website here.  We are extremely proud of this campaign and hope you find it inspiring too.

The next 17 years and beyond

It has been an honor for the Neustar team to launch, build, grow and shape the .US namespace, from inception to today. But we’ve never rested on our laurels and we certainly don’t plan to do so now. In the years ahead, we are committed to continue refining our marketing strategy, innovating on new and unique marketing campaigns, engaging our community of brand ambassadors and supporting ongoing growth and success of the .US TLD.

Ultimately our goal is to ensure that the millions of individuals, businesses, non-profit organizations, community groups, couples, families, startups, solopreneurs, veterans, dreamers, makers and more who are building their future on .US – as well as those who invest in the .US namespace – can rest assured knowing that .US is one of the most trusted, dynamic and in demand TLDs in the world.

If you know of any cool .US customers, or stumble upon any “in the wild” – please reach out and let us know.  We are always looking for new and interesting ways to shine the light on the great things happening in the .US namespace!  You can learn more about .US at www.about.us, and can contact us comms@registry.neustar.  Thanks for reading!

© DomainNameWire.com 2019. 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. Virtual .US Town Hall meeting takes place Wednesday
  2. From 10-cent domains to revved up marketing and policy changes, .US might finally go somewhere
  3. 1 and 2 Character .Biz Domain Names Face Delays
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.