skip to content

News

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

Donuts files opening brief in .Web appeal

Domain Name Wire - Tue, 09/05/2017 - 13:33

Company believes covenant not to sue is invalid.

New top level domain name company Donuts, through its company Ruby Glen, LLC, filed its opening brief (pdf) last week in an appeal over the .web domain name.

Donuts was one of the applicants for the .web domain name. Nu Dot Co won the auction for $135 million after Verisign struck a deal with it to transfer the ICANN agreement for .web to it after the auction.

The runner up in the auction was Afilias, not Donuts, but Donuts was upset that Nu Dot Co wouldn’t participate in a private auction for the domain name. Instead, Nu Dot Co pushed it to an ICANN “auction of last resort”. Had the auction been private, Donuts would have received about a $22.5 million payoff for losing.

Donuts went through ICANN’s normal appeals channels. When that failed, it sued ICANN in District court. The judge tossed out the suit because the application for new TLDs included a clause that the applicants would not sue ICANN. Donuts argues that this agreement not to sue (called an exculpatory clause) is invalid, as it writes in its opening brief:

The district court’s ruling was in error because: (1) the Exculpatory Clauses, when strictly construed, do not apply to the claims asserted in the FAC; (2) the parties’ agreement involves a matter of public interest, which renders the Exculpatory Clauses void under California common law; (3) the Exculpatory Clauses are void on their face pursuant to California Code of Civil Procedure section 1668 (“Section 1668”) because they release ICANN from intentional misconduct, gross negligence, and intentional or willful violations of the law; (4) Ruby Glen’s second (tortious breach) and fourth (unfair business practices) causes of action specifically allege intentional misconduct, rendering the Exculpatory Clauses void as applied to each claim; (5) the enforcement of the Exculpatory Clauses to the first cause of action (breach of contract) would render the parties’ agreement illusory; and (6) Ruby Glen should have been afforded at least one opportunity by the district court to amend its pleading.

Donuts’ appeal seems to be largely about trying to get a pay off for losing the auction. It didn’t challenge a previous deal similar to what Verisign did with Nu Dot Co when an Automattic-affiliated company struck a deal for .blog. That auction was private and Donuts received a share of the proceeds. Additionally, Donuts had a somewhat similar deal with Rightside (a competitor that it later acquired) to transfer domains after the auctions.

While money is a big reason for challenging the auction, it has the side benefit of delaying the rollout of .web, a competitor to Donuts’ 240 top level domain names.


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

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

The post Donuts files opening brief in .Web appeal appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. Court denies Donuts’ request to delay .web auction
  2. ICANN files motion to dismiss Donuts’ .Web lawsuit
  3. Court tosses Donuts’ .Web lawsuit because Donuts promised not to sue
Categories: Domains

Instagram registers Doxagram domain names in wake of data breach

Domain Name Wire - Sat, 09/02/2017 - 13:46

Company’s domain registrations are probably futile.

Instagram hacked, DoxAGram selling data.

This week news broke that hackers stole account information on perhaps six million Instagram users and are selling the data. A group of hackers being called DoxAGram is responsible for the breach.

In the wake of the breach and disclosure, Instagram is registering lots of domain names with DoxAGram in them. It’s unclear why Instagram is choosing the domains that it is.

For example, it has registered domains across many of Uniregistry’s top level domains, including doxagram.christmas, doxagram.hiphop and doxagram.mom. It has also registered domains from other registries, such as doxagram.guru. Yet it has left some obvious ones off the registration list, such as doxagram.store.

Perhaps it is still going through the process of registering domains, but I’m not sure that registering domains across nearly 1,000 top level domains makes sense.


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

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

The post Instagram registers Doxagram domain names in wake of data breach appeared first on Domain Name Wire | Domain Name News & Views.

No related posts.

Categories: Domains

Namecheap sues Enom and Tucows, demands transfer of 4 million domains

Domain Name Wire - Fri, 09/01/2017 - 22:09

Namecheap says Tucows is dragging its feet on transferring domains registered through Namecheap when it was an Enom reseller.

Domain name registrar Namecheap is big, but until this year it didn’t show up on charts that rank registrars by domains. That’s because Namecheap acted as an Enom reseller, so it added to Enom’s numbers rather than its own.

Starting this year, Namecheap began registering new .com domain names on its own registrar accreditations and it generally ranks as the fifth largest registrar each month when it comes to new .com registrations.

Namecheap wants to transfer four million domains that Verisign offers (e.g. .Com, .net) that were registered at Namecheap while it was an Enom reseller from Enom’s accreditations to its own accreditations. In a lawsuit filed in Seattle this week (pdf), Namecheap alleges that Tucows, which acquired Enom earlier this year, is thwarting the effort.

The issue seems to revolve around if this transfer qualifies for a “Bulk Transfer After Partial Portfolio Acquisition”, or BTAPPA. This type of transfer was set up to transfer a bunch of domains between registrars in bulk.

One reason to use BTAPPA is when a registrar acquires another one, so that it can transfer the domains to a single accreditation.

Does that apply in this case?

In its suit, Namecheap says that Verisign has already approved the transfer of these domains through BTAPPA. But Tucows, according to the suit, says it doesn’t qualify:

Tucows has refused to complete the bulk transfer of the VeriSign Domains to Namecheap using the BTAPPA service based on the unmeritorious argument that doing so would violate ICANN/VeriSign rules, regulations and processes….

Namecheap also claims that Tucows is concerned that the mass transfer of domains “would wreak such havoc and confusion” because of the volume and because .com is a thin Whois in which registrant data stays with the registrar, not the registry.

Enom’s margin on Namecheap’s domain registrations is surely quite low, but the agreement allows Enom to retain 100% of expired domain revenue and all parking revenue during registrations and during the expiration cycle, according to the suit. Namecheap positions this as a reason that Enom/Tucows might want to slow the transfer.

Namecheap says it offered to make a cash payment to Tucows and execute a separate purchase agreement so that the deal would be considered a partial acquisition “and thereby obviate any further basis for disagreement about whether the VeriSign Domains transfer qualifies for the BTAPPA service.” It says Tucows rejected this option.

I have reached out to both Namecheap and Tucows for comments and will update this story if either makes a statement.


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

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

The post Namecheap sues Enom and Tucows, demands transfer of 4 million domains appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. Tucows acquires eNom from Rightside
  2. Tucows expects $20 million EBITDA/year from “opportunistic” eNom acquisition
  3. January data show why Rightside sold eNom: Namecheap
Categories: Domains

The Latest .Com Winners & Losers

Domain Name Wire - Fri, 09/01/2017 - 19:40

Latest data shows little change.

ICANN published the latest official .com transactions report from Verisign, which includes data by registrar for May 2017.

Little has changed in the top spots, with GoDaddy leading the way and Tucows, which now includes Enom, coming in second place.

Here are the top registrars in terms of new .com registrations for May:

1. GoDaddy* 930,127
2. Tucows** 190,589
3. HiChina 145,636
4. PublicDomainRegistry 124,470
5. Namecheap 122,598

Here are the top five registrars (open to the public) for net inbound transfers during the month:

1. HiChina +18669
2. GoDaddy +9,022
3. Google +7,816
4. TurnCommerce (Namebright) +6,199
5. MAFF Inc (XZ.com) +5,920

On the flip side, these five registrars saw the biggest net outflow of .com domain names due to transfers:

1. Tucows -13,170
2. PublicDomainRegistry -6,688
3. Fabulous -4,950
4. 1&1 -4,070
5. Domain.com –3979

*Includes GoDaddy and Wild West Domains **Includes Tucows and ENom.


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

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

The post The Latest .Com Winners & Losers appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. A strong month for .com; here are the winners & losers
  2. Chinese registrars lose of lot of .com, but HiChina picks up domains from others
  3. .Com Winners & Losers
Categories: Domains

Expired domain “held for ransom”?

Domain Name Wire - Fri, 09/01/2017 - 13:25

Foster agency failed to renew domain and says it is being held for ransom.

The practice of domain investing can get a bad rap sometimes, and this story is an example of why.

A UK foster agency used the domain name littleacornsfostering.com for many years but failed to renew it earlier this year. Someone bought the expired domain and is asking the company for £9,000 if it wants to buy the domain.

A couple things come to mind when reading this story.

First, I’m surprised that the agency didn’t notice the domain expired during the required DNS disruption. This is a period of at least eight days that the registrar must change the DNS to alert the owner that the domain has expired.

Second, I personally stay away from domains like littleacornsfostering.com that seem like they would only be used by one company. I buy expired domains that were previously used, but only if it seems like there would be a broad appeal for the domain name rather than selling it back to the company that previously owned it.


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

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

The post Expired domain “held for ransom”? appeared first on Domain Name Wire | Domain Name News & Views.

No related posts.

Categories: Domains

Beijing starts issuing ICPs on new top level domains

Domain Name Wire - Thu, 08/31/2017 - 15:02

Beijing residents of approved TLDs can now get a license to use them.

Getting approval for registrants to use and host content on new top level domain names in China can be a complicated process for registries. First, they need to get approval from Ministry of Industry and Information Technology (MIIT). But it doesn’t stop there. The regional communications departments also have to begin allowing registrants who live in their provinces to apply for Internet Content Provider licenses (or ICP) for their individual domains.

An ICP is a number that ties a website to an individual (usually the registrant). This number allows the Chinese government to know who is responsible for the content on a website and hold them accountable for it. Without an ICP license, it is illegal to host a website using a given domain inside of China, and the individual can get into very serious trouble with the Public Security Bureau.

Until just recently, people who live in Beijing were unable to get an ICP for sites hosted on the approved new top level domains, even if the TLD was approved by MIIT. Last week, the Beijing Communications Administration started issuing ICPs, which means that these domains (such as .VIP and .Club) can finally be put to use by residents of Beijing.

Beijing was the largest holdout of regional/city groups for issuing ICPs (most other developed provinces and municipalities were already allowing registrants to get ICPs for their websites).

It will be interesting to see if this boosts development of new TLDs registered to people in Beijing, which is home to the largest online business sector in China.

(Hat tip to Simon Cousins of Allegravita for his help understanding this latest development.)


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

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

The post Beijing starts issuing ICPs on new top level domains appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. Del Monte v. Del Monte: first new TLD objection to be upheld
  2. RrSG provides evidence to back up claims made against Minds + Machines
  3. Cheers! .Wine and .Vin domains ready to be bottled
Categories: Domains

Afilias gets patent related to community top level domains

Domain Name Wire - Thu, 08/31/2017 - 14:08

Patent describes way to verify registrant information to create trust and community.

An explanatory graphic from Afilias’ patent.

The U.S. Patent and Trademark Office granted patent 9,747,378 (pdf) to Afilias this week for “Linked web presence pages associated with a top level domain”.

I was a bit confused about what the patent covered and if the technology behind it had been implemented, so I reached out to Afilias for an explanation. Its explanation is a better description of the patent than I could come up with:

US Patent 9747378 stemmed from work by Afilias on a way to support the ability of community oriented TLDs to help the registrants gain exposure and interaction. Specifically, the patent addresses two important aspects of community building. The first is to add credibility that a particular registrant and domain name is a bonafide participant in the community.

It does this by cross checking various public sources of data against the registrant’s information and verifying the match. A proper match elevates the profile of a registrant and their domain name and gives other members of the community more confidence in dealing with them.The second is to enable the registrant to self-add functionality to their web presence by enabling things like: accepting donations, offering chat service, posting a twitter feed, allowing comments, and providing customer service.

Afilias says the concept is a result of Afilias’ support of various community-oriented TLDs, although none have specifically deployed the capability at this time.


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

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

The post Afilias gets patent related to community top level domains appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. Verisign gets patent for triggering web crawling based on registry data
  2. Afilias plans to raise $100 million, warchest will help in new top level domain auctions
  3. Verisign gets patent for predicting domain name renewal rates
Categories: Domains

.Cam will be confused for .Com

Domain Name Wire - Thu, 08/31/2017 - 13:36

The similarity at quick glance will fool a lot of people.

.Cam is short for Camera, but businesses should consider registering the domains to reduce the chances of phishing.

Verisign objected when companies applied for the .cam top level domain. It argued that the string was too similar to .com and would cause confusion. One panelist agreed with Verisign and another didn’t, leading to the ICANN board intervening. Long story short, .cam is now a top level domain with about 4,000 registrations.

So, is .cam confusing with .com? It just was for me.

I was reviewing UDRP decisions on UDRPSearch when I came across a decision for WellsFargo.cam. I didn’t notice the a instead of o in the extension. I figured it was an IDN second level domain that looked really similar to the ASCII version. When I read the decision there was no mention of that, though. It took me about a minute to realize the top level domain.

If this fooled me momentarily, imagine what will happen to the average internet user who gets visits a phishing site that uses .cam?

I think it would be wise for large brands to register their matching .cam domain name for defensive purposes.


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

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

The post .Cam will be confused for .Com appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. Kevin Ham and Mike Mann let these prize-winning domain names expire
  2. “China” is #1 trending word in .Com
  3. “Gen Z are not [visiting] dot coms.”
Categories: Domains

14 End User Domain Name Sales

Domain Name Wire - Wed, 08/30/2017 - 18:10

Here are 14 examples of end users that bought domain names on the Sedo aftermarket over the past week.

The top public sale at Sedo this past week was Quoin.com for $15,000. The buyer is a lawyer in Germany, so it might be for a client.

Other end user domain sales include a three letter .co, a .ai domain name and a company buying the .com to match its .ca domain name.

(You can view previous lists like this here.)

Quoin.com $15,000 – The buyer is a lawyer at a firm in Germany, so I’m guessing this is for a client.

KairosGroup.com $5,000 – Kairos Private Investment Limited in Cyprus.

AdSoul.com $5,000 – into-e is a German e-commerce consultancy.

Rng.co $3,999 – Raange is a consumer marketing company with a name that miserably fails the radio test.

Refounding.com $3,800 – This is a clever name. Bionic says it “installs a startup ecosystem into large enterprises”. I can see how Refounding–a play on Founding a company–could be a cool term for the company to use.

ICMJapan.com $3,488 – This company sells used Japanese cars.

Econsave.com $3,299 – The buyer is a grocer in Malaysia called Econsave. It uses the domain econsave.com.my.

OnlineFileConverter.com $3,180 – rSpark packages things like toolbars with downloadable software.

LuxuryDriver.com $3,000 – Superior Auto Extras supplies merchandise for car washes.

Plenty.ai $2,999 – Plenty, an indoor farming company, just raised $200 million. (Psst. I own IndoorFarm.com.)

Chandler.co $2,300 – Chandler Resources, a glass and packaging company that uses the domain chandler-resources.com.

GetRetired.com $2,249 – Financial Independents, Inc. is a financial advisor in Michigan.

HeathrowExpansion.co.uk £2,000 – A web design company called Studio 24 bought the domain.

Go99.com $2,000 – Freight marketplace Go99 uses the domain Go99.ca.


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

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

The post 14 End User Domain Name Sales appeared first on Domain Name Wire | Domain Name News & Views.

No related posts.

Categories: Domains

Uber (the ride hailing company) is causing a headache for Uber (the IT company)

Domain Name Wire - Wed, 08/30/2017 - 13:42

Healthcare IT company sues Uber for trademark infringement after being inundated with misdirected communication.

Need a ride or are you looking for healthcare IT?

A healthcare IT company in Florida called Uber Operations, LLC is suing ride hailing company Uber Technologies for trademark infringement after dealing with confusion between the two companies.

The lawsuit (pdf) explains a number of headaches the company has experienced from people thinking it is the ride hailing company.:

Actual customer confusion, initial interest confusion and/or reverse confusion have already occurred on numerous occasions, all to the detriment of Uber Operations. In fact, Uber Operations receives and has received multiple telephone calls and emails from the public looking for or complaining about Uber Tech and/or its goods and services. Uber Operations has received thousands of calls, emails, and faxes directed to Uber Tech. This is a constant business interruption and distraction, resulting in lost time and productivity. In addition, Uber Operations has been sent information relating to background checks, credit checks and other personal information (presumably for Uber Tech drivers or prospective drivers). Uber Operations has been sent packages with phones and other personal items in them. Uber Operations has received financing applications (with personal information) for the “Uber Xchange” leasing program (as previously noted, Uber Operations has used the mark “UberXchange” for many years).

Uber Operations says it has also received government orders meant for the California company as well as bad reviews on internet review sites.

The experience reminds me a bit of what happens when a company doesn’t use a domain name that matches their company name, or doesn’t use the .com (or logical country code).


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

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

The post Uber (the ride hailing company) is causing a headache for Uber (the IT company) appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. Obama campaign sues web site over Barack Obama merchandise
  2. Entrepreneur Media continues to sue entrepreneurs who use the word entrepreneur
  3. OrderInn.com sues Google Ventures-backed Ordr.in over name
Categories: Domains

Elisa Cooper and Matt Serlin join new corporate domain registrar

Domain Name Wire - Wed, 08/30/2017 - 13:00

Ex-MarkMonitor employees join new corporate domain manager.

Elisa Cooper and Matt Serlin have joined Brandsight.

Two former employees of corporate domain name registrar MarkMonitor have joined Brandsight, a new domain name registrar targeting the corporate market.

Elisa Cooper and Matt Serlin joined the company that was founded by Phil Lodico earlier this year. It is officially launching its website today.

Both Cooper and Serlin are well known in the domain name and ICANN communities. Cooper left MarkMonitor in 2015 and joined intellectual property company Lecorpio. Lecorpio justed merged with IP firm Anaqua, so Cooper made the move to Brandsight. Serlin’s name is well known because he was listed as the contact on about 35,000 domain names that MarkMonitor registered on behalf of clients that wished to remain anonymous. He left MarkMonitor earlier this year.


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

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

The post Elisa Cooper and Matt Serlin join new corporate domain registrar appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. MarkMonitor allegedly hacked by Syrian Electronic Army
  2. #9 in 2016: A domain company gets rebranded
  3. 35,000 domains at MarkMonitor need to be updated soon
Categories: Domains

Snappa makes creating social media graphics easy

Domain Name Wire - Tue, 08/29/2017 - 17:47

I learned about Snappa because of its domain purchase and recently became a paying customer.

Snappa helps you create social media (and other) graphics.

Back in May I interviewed Christopher Gimmer, co-founder of a graphics site called Snappa. His company paid $40,000 to upgrade its domain name from Snappa.io to Snappa.com.

I was interested because of the domain story. But a couple months ago I needed to create some video thumbnails for YouTube and didn’t have the skills to do it. I tried a few apps that popped up when I searched Google for “Create YouTube Thumbnails”. They were all rather tricky to figure out. I remembered Snappa from the interview and decided to check it out.

It turns out Snappa is the perfect solution for the graphically-challenged (like me).

Snappa offers templates and an easy editor for creating graphics. It’s super simple, with preset sizes for YouTube Thumbnails, Facebook covers, Twitter posts and more. In a minute or two, you can upgrade all of your social media graphics.

I also think the way Snappa gated its subscription option was brilliant. You can use the service for free but will start to discover limitations when you use it more than a few times.

First you can create and download graphics but not save them. Then you hit a download limit. At that point, you see the value and pay for a subscription. In my case, that’s $15 a month, which is very reasonable if I create just a few graphics per month.


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

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

The post Snappa makes creating social media graphics easy appeared first on Domain Name Wire | Domain Name News & Views.

No related posts.

Categories: Domains

Can .Web revive .Wed ?

Domain Name Wire - Tue, 08/29/2017 - 16:24

Jean Guillon argues that the similarity between .web and .wed might help the latter as companies register them defensively.

We’re talking about two Registries: one which is live and the other which should be live sometime soon.

Two Stories

The .WED and .WEB new gTLDs are two very similar TLDs with two complete very different stories:

The .WED domain is short for “wedding”. It launched years ago and only has – at the moment when this article is being written – 43 domain names created. It has a direct competitor which is the .WEDDING new gTLD with 9,219 domain names registered.

The .WEB new gTLD is thought by many to become the most successful new gTLD from the entire ICANN new program: short, meaningful (?), and a close competitor of the already popular .COM.

The .WEB new gTLD, for the story, was won in an auction for $135,000,000 (and it seriously upset losers of the auction). It is not yet delegated by ICANN so you can’t buy it yet. The ICANN database shows that it is in contracting and “on hold” because of a contention set with .WEBS but in fact, that is not the reason. The real reason is here.

The problem with .WED

In terms of sales, the .WED new gTLD is the typical project that just could not work from the start because of registration policies:

  1. The registrant’s use of the registered domain name, must be:
    1. “Generally accepted as legitimate”: it is unclear what legitimate means.
    2. “Not directly aimed at selling or offering for sale of the same domain name or for selling non .WED domains”: does it mean that a person involved in the business of domain names cannot buy one because it deals with other domain name extensions? This is unclear too.
    3. “Not directly aimed at monetisation via advertisement including but not limited to pay per click advertising”: OK, domainers not welcome as well as no crap advertising. Understood. I understand the position of the Registry here but unfortunately, a registry requires to sell domain names to pay ICANN;
    4. “.WED domains are only valid for two years”: what happens at the end of year two? It was designed so the domains would expire so another couple could use them. This is a bad business model for domain registrars.
  2. It is rather expensive: € 50+ for one year.
  3. There is a field to fill in in the registration form entitled: “EU (European Union) Information – VAT”: taxes are often added automatically at Registrars so the price for a person residing in the EU is in fact closer to € 60. Note that this added field is not really a problem in fact, it just makes it longer to fill in the form.

The future of .WED

The .WED registration figures have kept dropping, month after month, and unless the Registry accepts to change its registration policies to open its domain names to all, I don’t see how such a TLD could ever be profitable.

The positive thing about changing its registration policies is that the .WEB new gTLD will launch at some point. There is a one letter difference between the two TLDs (and inverse-looking letter) and I foresee all corporate and retail Registrars – worldwide – to inform their clients that they’d better secure their .WED too if they plan to register a .WEB domain name to prevent cyber-squatting.


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

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

The post Can .Web revive .Wed ? appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. Web.com formally announces bid for .web
  2. 10 more new TLDs hit the market this week. 1 will be a big flop.
  3. Survey: .Club and .Web domain names are favorites
Categories: Domains

Amazon registered these 28 domains for Multi-room Echo audio launch

Domain Name Wire - Tue, 08/29/2017 - 14:05

Amazon goes on defensive binge in conjunction with highly anticipated feature launch.

Amazon announced this morning that it is now supporting multi-room audio on Amazon Echo devices. Companies that make speakers (or devices with speakers) that use Alexa Voice Services (AVS) can use a new SDK to integrate the feature as well.

This is huge news for Echo users and could also be very bad news for Sonos, which is probably the king of multi-room audio playback. When we built our house five years ago we spent thousands of dollars on Sonos equipment. Today I would probably just buy a bunch of echo devices.

As Amazon always does, it registered a bunch of domains as a defensive action for this launch. If history is a guide, it will register more over the coming days. Here are 30 domains it registered late last night/early today:

alexa-multi-room-audio-sdk.com
alexa-multi-room-audio.com
alexa-multi-room-music-sdk.com
alexa-multi-room-music.com
alexa-multi-room-sdk.com
alexaaudiosdk.com
alexaconnectedspeaker.com
alexaconnectedspeakers.com
alexamulti-room.com
alexamultiroom.com
alexamultiroomaudio.com
alexamultiroomaudiosdk.com
alexamultiroommusic.com
alexamultiroommusicsdk.com
alexamultiroomsdk.com
alexamusicsdk.com
alexasynchronized.com
alexasynchronizedaudio.com
alexasynchronizedmusic.com
echo-multi-room-audio.com
echo-multi-room-music.com
echoconnectedspeaker.com
echoconnectedspeakers.com
echomultiroomaudio.com
echomultiroommusic.com
echomultiroomspeakers.com
echosynchronizedspeaker.com
echosynchronizedspeakers.com

The company also registered some domain names related to the Echo being sold at Whole Foods, which is formally acquired earlier this week.


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

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

The post Amazon registered these 28 domains for Multi-room Echo audio launch appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. Google and Amazon compete on 21 new top level domain applications
  2. Final new TLD objection tally: Donuts 55, Amazon 24, Google 22
  3. Amazon.com foreshadows AWS re:Invent news with domain name registrations
Categories: Domains

How you can help Houston and surrounding areas

Domain Name Wire - Mon, 08/28/2017 - 20:47

Rain from Hurricane Harvey has devasted a large portion of Texas.

When a natural disaster like this strikes, it can be easy to question why people live in a “dangerous” area. I can tell you that I never, ever would have imagined many of the areas under water in Houston right now to be at risk of flooding. Some areas are experiencing once-in-800-year events right now.

Even if you are far from Texas, you can have an immediate impact by donating to groups that are on the ground.

The typical go-to charity for a natural disaster like this is the American Red Cross. In addition to money, they can also connect you with a blood bank as blood needs are high right now.

There are a lot of local charities that can put your money to work quickly. Remember that this disaster has not just struck the fourth largest city in America. It stretches well beyond Houston to communities over a hundred miles away. To that end, here are some groups where your donation can have an immediate impact.

Bastrop Food Pantry – Bastrop is just east of Austin and seems to be the demarcation between places that got hit hard versus those that are OK. (I live in Austin and am completely safe. Most areas of Austin have received less than 10″ of rain. Many areas around Bastrop have been hit with 20″.) The Bastrop Food Pantry was already in need before the flood. Now the need is greater. Here’s the cool thing: the food pantry buys food for 15 cents a pound from the major food bank in Austin. So even if you’re only able to give $15, that’s like donating 100 pounds of food! You may also consider food banks in Corpus Christi, Galveston and other surrounding areas.

Texas Diaper Bank – This group is getting a lot of attention in the wake of Harvey. It looks like they’ve raised $400,000 already but can use more.

Houston Humane Society – a lot of animals are also in need right now. Also look at animal rescues around Houston and even places like Austin and San Antonio that are assisting.

Greater Houston Community Foundation – This organization has set up the Hurricane Harvey Relief Fund. The fund was established by the mayor, so I hope that it will be put to use on the ground quickly.

[Update: I hit $1,000 in matching already, but I encourage you to still consider giving.] I will match donations to Texas Diaper Bank, Houston Humane Society, Greater Houston Community Foundation or any 501c food bank in Texas up to a total of $1,000. Just post a comment with your contribution (amount and recipient), or you can email me at editor (at) domainnamewire.com with details of your contribution if you’d like to keep it private.


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

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

The post How you can help Houston and surrounding areas appeared first on Domain Name Wire | Domain Name News & Views.

No related posts.

Categories: Domains

Report suggests bright future for Chinese domain market

Domain Name Wire - Mon, 08/28/2017 - 17:28

Kassey Lee examines data from a recent CNNIC report.

If you invest in the Chinese domain market, you need to know CNNIC (China Internet Network Information Center) because it publishes a national survey report twice a year on China’s internet landscape. The latest report — the 40th — was published in July. You can download it in Chinese here.

According to the report, China has 751 million internet users. This represents only 54% of the Chinese population so there is a lot of room for growth. Compare this number with the 323 million population of the entire USA and you can appreciate the sheer size and potential of the Chinese market. This number, coupled with the continued increase in internet-related products and services, means there will be an ever expanding internet economy, which in turn will create more companies and therefore more demand for domain names.

Only 54% of China's population is online. This means 700 million more potential growth.Click To Tweet

There are now 5 million websites, growing mostly at double digits over the last 6 years. This number is dwarfed by the estimated 77 million companies in China. This large gap may be due to companies not being online or running their business from ecommerce sites such as JD.com, etc. Eventually, these companies will want to move to their own address (domain name) to gain complete control of their business. Therefore, high demand for domain names can be expected to continue.

The report shows that 96% of the internet users go online via their mobile phone. This has significance for domain investors. Whatever you do for the Chinese market, think mobile. Make sure, for example, that the landing page of your domain name for sale is mobile ready. Also, 92% of the internet users use a messaging app as their communication tool, with Wechat and QQ being mentioned as the top ones. If you want to communicate with Chinese buyers, a Chinese messaging app may be your best choice rather than email which is popular in western countries.

The report highlighted several areas with good growth: ecommerce (online shopping, online food ordering and delivery, travel booking), personal finance, online entertainment (music, video, games etc.), online education, and ridesharing. If you have domain names applicable in these areas, you may want to further explore such selling opportunities in China.

Unfortunately, data on domain names is missing in this latest report for some unknown reason, so I’ll use the one published 6 months ago. As of December 2016, the number of domain names registered in China was 42 million. Growth has been double digits over the last 5 years. Here’s the detailed breakdown: .cn (48.7%), .com (33.9%), .net (3.9%), .中国 (China, 1.1%), .org (0.8%), .biz (0.5%), and .info (0.5%). New extensions were grouped under “Others” so no insight can be obtained.

These numbers tell us that the Chinese market is growing fast, and you want to focus on .cn or .com if you want a large pool of domain buyers. If you invest in .cn domain names, however, understand that you are investing in a country extension which comes with country risks. For example, in 2009 the Chinese government announced a new rule which required registrants to submit personal information and photo identification. This rule especially hurt investors outside China as many simply let their domain names drop.

Finally, I’d like to mention two areas worth watching in China: credit and speculation. When credit becomes widely available and speculation goes mainstream, the domain market will likely explode. So, overall, I see a high-growth market for domain investors.


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

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

The post Report suggests bright future for Chinese domain market appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. How Long Until China Confiscates Google.Cn Domain Name?
  2. Kevin Ham and Mike Mann let these prize-winning domain names expire
  3. “China” is #1 trending word in .Com
Categories: Domains

Get ready to MERGE! – DNW Podcast #150

Domain Name Wire - Mon, 08/28/2017 - 15:30

A conference covering domain names, bitcoin, blockchain and more is coming. Here’s how to get free or discounted tickets.

Jothan Frakes comes on the show to discuss the upcoming MERGE! Show in Orlando. It includes The Domain Conference plus other conferences (Blockchain, bitcoin, cryptocurrencies, content management systems and more) all wrapped up in one. Be sure to listen to the end for your chance to get free or discounted tickets.

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


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

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

The post Get ready to MERGE! – DNW Podcast #150 appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. Blockchain and Common Law Trademarks – DNW Podcast #137
  2. 2017 Predictions – DNW Podcast #116
  3. Boost your domain sales chances – DNW Podcast #135
Categories: Domains

Is this a great domain or a horrible one?

Domain Name Wire - Mon, 08/28/2017 - 13:35

I can’t decide if this domain is ingenious or dumb.

Are these guys tripping or ingenious?

I was in the car listening to the radio yesterday when a commercial caught my attention.

The ad was for a site that aggregates vacation rental sites like HomeAway. I rent a vacation home about 4-5 times a year, so I was instantly interested.

Then the ad mentioned the site’s name: Tripping.com.

Did I hear that correctly? Did they name the site using a term commonly associated with drugs?

They said the word Tripping.com several times. But then they went a step further:

“That’s t-r-i-p-p-i-n-g dot com”, the announcer said.

Without that confirmation, I’m not sure if I would have believed that the site name was tripping.com. I assume people don’t hear it correctly or do no believe it’s actually tripping.com, which is why they included the spelling in the ad.

In general, any domain that has to be spelled out to understand it is a bad domain. It fails the radio test.

But the name for this site is so startling that it might just be a great domain. What do you think?


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

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

The post Is this a great domain or a horrible one? appeared first on Domain Name Wire | Domain Name News & Views.

No related posts.

Categories: Domains

5+ WordPress Backup Plugins You Need to Know About

Domain Name Wire - Fri, 08/25/2017 - 17:44

Backing up your WordPress site is essential. These tools will help you do it.

Imagine spending countless hours designing your WordPress website, creating killer content, landing pages, contacts forms, and more….only to have it all disappear because of a hacker, the push of a button, or even a bad plugin.

Frustrating to say the least, right?

Backing up your website is one of the most important things you can do to ease the worry of having to wipe your website’s slate clean and “start over”.

Backing up your WordPress website is crucial if you want avoid losing all of your hard work.Click To Tweet

Because, even if you do experience the notorious WordPress white screen of death, so long as you have been consistently backing up your website, restoring it should be a cinch.

Today we are going to look at some of the best backup (and restore) WordPress plugins on the market. Because backing your site up is only half the battle. If restoring your website is a pain in the you know what, there is very little you can do with your backed up files.

And trust me, there are so many backup plugins that make restoring your website difficult.  I learned this the hard way.

Best WordPress Backup Plugins 1. UpdraftPlus

UpdraftPlus is one of the most reliable and popular WordPress backup plugins. Not only does it schedule automatic backups of your WordPress website, you have several storage options for saving your backups. For instance, back your site’s data into the cloud directly to Dropbox, Google Drive, Amazon S3, FTP, and more.

In addition, thanks to its ability to function using less server resources than most other backup plugins, UpdraftPlus ensures optimal site speed and performance. And, don’t forget the best feature – one-click restoration of any site backup.

If you are interested in additional features such as WordPress Multisite functionality, duplication and migration services, and free dedicated support, consider using UpdraftPlus Premium.

2. BackWPup

BackWPup is another trustworthy backup plugin that allows for scheduled backups so you never forget. In addition, it will let you save your backups to external services such as Dropbox, or if you prefer, download a single .zip file straight to your computer.

The only drawback to this plugin is that the only way to restore your website right now is to import a saved .zip file. Unfortunately, a one-click restore is not available, though the plugin developers have mentioned that this functionality is underway.

However, this WordPress backup plugin does give you the ability to optimize, check, and repair your database, which is a feature not many plugins have.

3. VaultPress

VaultPress is a premium backup service brought to you by Automattic, the same people behind WordPress itself. And to start, enjoy automated backups into an offsite digital vault, all in real-time.

In addition, transfer or duplicate your site, fix vulnerabilities that threaten your site’s security, enable spam defense, and even take advantage of automatic file scanning for things like viruses and malware.

This dependable backup solution also comes with easy restore options. In fact, you never have to contact your host when you want to return your website to an earlier version. And, since VaultPress has a 30-day backup archive, you can make sure to restore your site to the exact point in time you need.

Domain Name Wire uses VaultPress to back up its website.

4. BackUpWordPress

BackUpWordPress helps you backup your entire website, including all your files and database. It is very simple to set up and start using, works well in shared hosting environments because it doesn’t require a lot of resources, and can even handle multiple backup schedules.

The great thing about this WordPress backup plugin is that you have the option to have your backup emailed to you, which is very convenient. In addition, you can exclude specific files and folders from your scheduled backups, use this plugin on Linux or Windows servers, and even get good support when needed.

5. My WP Backup

My WP Backup offers many features besides a simple backup of your WordPress website. To start, enjoy the convenient Plugin Walkthrough so you can become familiar with all that this backup plugin has to offer. In addition, set as many automatic backups as you want and have them emailed to you, choose to back up only your WordPress database, and even migrate your website to another host.

Restore backups using any number of My WP Backup restore options, back up all of your site’s customizations and content so you don’t lose all of your hard work, and choose from backup storage options such as Dropbox, FTP, Google Drive, and even a .zip file. Lastly, this plugin comes translation ready, provides access to backup logs, and even has 24/7/365 around the clock support.

Notable Mentions

The truth is, there are a ton of exceptional WordPress backup plugins for you to choose from. Here are some additional ones to consider:

In the end, using a WordPress backup plugin for your website is critical. This is even true if your hosting provider performs backups for you. After all, with so many high-quality and affordable solutions, there is no reason not to take the added precautions. Plus, sometimes utilizing a backup plugin is easier when it comes to the restoring process.

Automate your website backups, stay on top of threatening security issues, and even rest easy at night knowing that no matter what, your hard work is just a click away should your website disappear unexpectedly.

 


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

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

The post 5+ WordPress Backup Plugins You Need to Know About appeared first on Domain Name Wire | Domain Name News & Views.

No related posts.

Categories: Domains

CentralNic acquires .SK operator for €26 million

Domain Name Wire - Fri, 08/25/2017 - 14:59

Controversial deal will boost CNIC annual revenue by about €4 million.

Domain name company CentralNic (London AIM: CNIC) has acquired SK-NIC, A.S., manager of Slovakia’s .sk country code domain name, for about €26 million. The deal is for €21.27 million up front and deferred cash consideration of up to €4.85 million depending on how the namespace performs over the next three years.

The deal has been in the works for a while and faced opposition from some in Slovakia who argued that management of the name was stolen back in 1999.

Opposition to the deal might explain why CentralNic agreed with the Slovak government to donate 5% of revenue from the domain to a fund dedicated to projects that contribute to the Slovakian digital economy.

With 360,000 registered .sk domain names, the purchase price represents a whopping €72.55 per domain if all targets are met. That’s a stiff price, but based on CentralNic’s accounting rules it says the business would have added a profit before tax of €3.58 million last year, so the multiple is about seven.


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

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

The post CentralNic acquires .SK operator for €26 million appeared first on Domain Name Wire | Domain Name News & Views.

Related posts:
  1. CentralNic reports earnings, numbers decline from last half
  2. CentralNic to relaunch Christmas Island .CX Domain
  3. CentralNic swings to loss, billings soar on .XYZ deal
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.