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.

Don’t blame other people for your bad domain name portfolio

Domain Name Wire - Wed, 01/10/2018 - 16:02

Learn from your domain investing mistakes and don’t blame others.

Last week I received an email from someone who was peeved at how he perceived some well-known domainers had responded to his domain portfolio.

Let’s be clear: if you send an unsolicited inquiry to a domainer with a list of your domain names, you need to be prepared for them to decline or to pass judgment on your domain names.

While I think you should take a hint from their response, I also don’t think you should get uptight if someone doesn’t like your domains. Instead, let the market judge them.

The best sign that you’re on the right track is if you frequently get unsolicited offers or sales of your domain names. If you’re doing something right, people will come to you.

That’s not to say that you shouldn’t also market your domain names to end users. But it’s a bad sign if your sales strategy is to just post a list of domains in a forum or to send a list to domain investors. It’s also a bad situation if you have to explain to another investor why your domain names are valuable.

Don’t blame those other domainers that don’t want to buy your domains.

Don’t blame Sedo or Afternic for not selling more of your domains.

Don’t blame an auctioneer or broker for refusing to represent your domains.

If your domains aren’t selling, the only person at fault is you.

If this is the case, the smart thing to do is to think about your strategy. Research and learn. Make changes.

Even the best domainers do this frequently. They re-evaluate. Many successful domain investors made a purchase (or sale) they’d like to undo.

As I sit here today, I look at many domains in my portfolio and wonder what I was thinking. But I don’t blame anyone else for my bad investing decisions. I wasn’t scammed or forced to do anything. Any mistakes I’ve made are on my shoulders, and any mistakes you’ve made are on yours.


© 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 Don’t blame other people for your bad domain name portfolio appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

GoDaddy gets patent related to facilitating expired domain and aftermarket transactions

Domain Name Wire - Tue, 01/09/2018 - 16:53

Concepts in patent could help domain owners sell more domains.

The United States Patent and Trademark Office has granted a patent to GoDaddy for “Notifying registrants of domain name valuations”.

The title of U.S. patent number 9865011 (pdf) is a bit misleading to the crux of the patent, which is much more encompassing. There are two main concepts in the patent:

1. Notifying domain searchers if a domain becomes available.

The patent states that 65% of searches today result in a user not finding the available domain they originally searched. (Note: the patent application was filed in January 2015).

So GoDaddy describes a system that monitors domain names people search for and notifies them if they later become available due to a) the domain expiring or b) the domain owner offering it for sale in the aftermarket (or indicating they are willing to sell it). The notifications may be limited so they don’t trigger if too much time has passed between the search and the availability.

2. Enabling communication between a domain searcher and domain owner to facilitate a transaction.

If the domain owner opts in, there could be a way for a domain searcher to contact the domain owner with an offer to buy the domain name. There might also be some sort of domain valuation that occurs as part of this process.

The patent states that should domain owners have success selling domains, it might incentivize them to consolidate their portfolio and listed it for sale in the domain aftermarket.

GoDaddy GM Michael Mclaughlin and VP of Product Management Tapan Kamdar are listed as the inventors.


© 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 GoDaddy gets patent related to facilitating expired domain and aftermarket transactions appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. GoDaddy Files Patent for Method of Selling Equity in Domain Names
  2. GoDaddy and AOL sued over email patents
  3. GoDaddy gets two patents for domain appraisal
Categories: Domains

CentralNic buys £2.5 million of domain names

Domain Name Wire - Tue, 01/09/2018 - 16:00

Domain company “replenished its inventory”.

Domain name company CentralNic (London AIM:CNIC) announced this morning that it has acquired £2.5 million of .com domain names. The purchases were from multiple portfolios.

In a release, CentralNic CEO Ben Crawford said, “CentralNic is delighted to have replenished its inventory of premium domains for trading, with these portfolios of mid-priced domains obtained at an attractive discount to current market rates. The market for these domains is relatively liquid, and trading in them leverages the Company’s global distribution capabilities and adds to the Company’s diversified revenue strategy.”

Premium domain sales have become a key part of CentralNic meeting its second half numbers each year. Of course, you need to find a way to replenish your stock of domains if you are to have something to sell.


© 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 buys £2.5 million of domain names appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. SedoMLS gets more domain extensions with .eu and CentralNic deals
  2. CentralNic sells $1 million domain name portfolio
  3. CentralNic closes $4.5 million domain portfolio sale
Categories: Domains

#1 in 2017: Domain name scoops

Domain Name Wire - Tue, 01/09/2018 - 14:55

This is the tenth and final post in a series covering the most-viewed stories on Domain Name Wire in 2017.

You can tell a lot about what companies are up to by observing domain names. The top three stories on DNW this year (in terms of views) were scoops I uncovered based on domain name registrations.

The most read story was about Amazon.com registering domain names related to cryptocurrencies like bitcoin. This isn’t a scoop (yet), as the company has not announced any initiatives related to these domains.

The second most-read story was my scoop that DowDuPont plans to name its agriculture spin-off Corteva. While the company has not announced it yet, it registered a slew of domain names that indicate Corteva is the current front runner.

And the third most-read story was my scoop that the Verizon Center in Washington D.C. would be renamed the Capital One Center. It became official about a week after I broke the news.

Here’s to many more name scoops in 2018!


© 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 #1 in 2017: Domain name scoops appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Cryptocurrency domains were hot in May
  2. Blockchain and Hurricane Harvey were popular in domains last month
  3. People are registering cryptocurrency domain names in droves
Categories: Domains

Intellectual Property company guilty of reverse domain name hijacking

Domain Name Wire - Mon, 01/08/2018 - 19:48

Isn’t it ironic, don’t you think?

Intellectual property management company CPA Global has been found to have engaged in reverse domain name hijacking by a World Intellectual Property Orgnaization panel.

The company filed a cybersquatting complaint against the domain name CPAGlobal-Litigation.com. The domain name is used by a law firm soliciting CPA Global customers for a class action lawsuit that alleges the IP management firm overbilled clients.

Even a rudimentary review of past UDRP cases would reveal that a panel would rule the domain name was registered and used in good faith and that the law firm had a legitimate interest in the domain. It helped that it had ‘litigation’ in the domain, which makes it clear that the site connected to the domain isn’t run by CPA Global.

In finding reverse domain name hijacking, the three-member panel wrote:

In this case, the Complainant ought to have known its Complaint was doomed to fail. The Respondent was clearly using the Disputed Domain Name in good faith to promote and provide information about a legitimate service which it offers…

…The Panel considers the Complainant launched the proceedings primarily to harass the Respondent and disrupt its lawsuit.


© 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 Intellectual Property company guilty of reverse domain name hijacking appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. $50,000 penalty for filing a frivolous UDRP!
  2. Zak Muscovitch gets reverse domain name hijacking win
  3. Canadian firm Obero tries to Reverse Domain Name Hijack domain name
Categories: Domains

Short seller targets Tucows with scathing report

Domain Name Wire - Mon, 01/08/2018 - 18:20

Company that is shorting Tucows releases report blasting company.

The same anonymous stock research group that targeted Web.com about four years ago is now going after Tucows.

Copperfield Research released a report about the domain name, mobile and broadband company titled “Cashing in on Neo-Nazis, Child Porn, & A Hidden Lawsuit as Insiders Dump”. The report’s authors have a short position in the company.

The report highlights three major grievances with Tucows (NASDAQ: TCX), a company whose stock doubled in price last year: all three of its business segments have issues, it is helping people operate unsavory websites, and it hasn’t disclosed its imminent loss of domains to Namecheap.

The hyperbole-filled report has some valid points, but I’m the type of person who sees a few misleading statements and then assumes that many of the other statements are wrong.

For example, the report blasts Tucows for its high churn rate when it took over the subscriber base of failed MVNO RingPlus. However, Tucows explicitly stated in earnings calls that it expected very low conversion from this group because RingPlus offered free service.

Also, the report devotes significant ink to a handful of bad websites that have registered their domains within the Tucows ecosystem. The report cites multiple websites with domain names that are registered at Tucows but does not draw a distinction between hosting and domain registration. It amusingly blasts the qualifications of one of Tucows’ compliance offers because she also like to DJ in her spare time.

On the NameCheap issue, it will be interesting to see how much of an impact the loss of Namecheap’s domains will have on Tucows. The revenue hit is real but the profit hit is unclear.

Shares in Tucows are down about 8% today. After opening the year around $70 they are now trading for $55.


© 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 Short seller targets Tucows with scathing report appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Tucows Posts Q1 Profit
  2. Tucows Reports Strong Earnings and More Stock Buybacks
  3. Tucows’ Revenues Steady, Brandable Domain Sales Growing
Categories: Domains

Domain business rewind – DNW Podcast #168

Domain Name Wire - Mon, 01/08/2018 - 16:30

Looking back at 2017 in the domain name business.

Happy New Year! This week I run down the top stories on DNW from last year. Top stories include GDPR, new top level domain pricing, emoji domains, dot-brands and more. Also: WordPress hosting company gets lots of dough, no more RegistrarStats and Syria.net dispute.

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 Domain business rewind – DNW Podcast #168 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. How End User Domain Buyers Think – DNW Podcast #134
  2. Paul Nicks of GoDaddy – DNW Podcast #160
  3. Building web businesses with Peter Askew – DNW Podcast #163
Categories: Domains

Afilias gets contract for Puerto Rico’s .PR domain

Domain Name Wire - Mon, 01/08/2018 - 15:24

This is how we do it down in Puerto Rico.

Domain name registry services provider Afilias has won a contract to operate the backend registry for Puerto Rico’s .PR top level domain name. The transition to Afilias was completed yesterday. Previously, technical operations were handled in-house.

.PR is unrestricted and has been pitched as a good extension for Public Relations firms. One of the more popular domains is n.pr, which is used as a shortener by National Public Radio.

Neither Afilias nor .PR manager Gauss Research Laboratories were immediately available to provide domain counts to DNW. [Update: Gauss Research disclosed that there are 7,784 .pr domains registered.] DomainTools tracks just over 5,000 domain names on .PR but this is likely misleading because many of the domains on .PR are third level registrations under second level domains like .com.pr.

Currently, registrars offer second level .PR registrations for over $1,000 per year while third level registrations are available for about $150.

While this probably isn’t a huge revenue contract for Afilias, the timing will allow the company to showcase the expanding roster of TLDs is supports during the ICANN meeting in San Juan, Puerto Rico in March.

Afilias recently won a major contract to manage 3 million domain names registered on Australia’s .AU domain.


© 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 contract for Puerto Rico’s .PR domain appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Mortgage.info for $250? There’s a Small Catch.
  2. Afilias Tells New TLD Applicants to Limit Their Expectations
  3. These domain name people are presenting at SXSW next month
Categories: Domains

#2 in 2017: GoDaddy and Uniregistry fight over new TLD prices

Domain Name Wire - Fri, 01/05/2018 - 19:36

This is the ninth in a series covering the top stories on DNW in 2017, as ranked by pageviews.

The #4 story in 2017 was about Frank Schilling’s capitulation on his forecast for new top level domains and his decision to drastically increase prices on many of his TLDs.

I’ve decided to separate the ensuing tiff between Schilling’s Uniregistry and GoDaddy into a separate item because of its importance, and because it represents an example of the often challenging interplay between registries and their registrar channel.

Following Uniregistry’s announcement of a price hike, GoDaddy temporarily pulled all of Uniregistry’s domains from its shelves. GoDaddy GM of Domains Mike McLaughlin said, “…The dramatic price hike Uniregistry announced left us no choice…”

Facing additional registrar backlash, Uniregistry backtracked a bit and decided to grandfather existing domain registrations at pre-hike prices. Uniregistry left it up to the registrars to handle the technical integration of the grandfathering.

GoDaddy later added Uniregistry domains back to its shelves but with very high markups. Then, in August, the company decided to pull the plug on Uniregistry indefinitely. In addition to halting new registrations and transfers, GoDaddy partnered with Hexonet to handle the backend for existing Uniregistry domain names.

GoDaddy was late to sign on to carry Uniregistry’s domains in the first place, so it wasn’t one of the top registrars for Uniregistry domains. Still, losing the world’s largest domain registrar is bad news for any registry operator.


© 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 #2 in 2017: GoDaddy and Uniregistry fight over new TLD prices appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Top 5 Domain Name Stories from August
  2. Silicon Alley Insider Values GoDaddy at $1.4 Billion, Oversee.net at $1 Billion
  3. GoDaddy officially launches second-line phone service
Categories: Domains

WP Engine banks $250 million from PE that bought GoDaddy

Domain Name Wire - Fri, 01/05/2018 - 14:53

WordPress hosting company takes a big investment from a company that knows the hosting space.

There was quite a bit of buzz here in Austin yesterday after WordPress hosting service WP Engine announced a $250 million investment from Silver Lake Partners.

That’s a big number by Austin standards, and might be the biggest single raise by a local tech company since HomeAway banked that much in 2008.

Local press pointed out that Silver Lake is the company that helped Austin-based Dell go private. But there’s also a connection to the hosting/domains business. Silver Lake was one of three private equity groups that bought/invested in GoDaddy in 2011.

Silver Lake definitely understands the hosting space and its business mechanics. The PE firm’s involvement means that WP Engine could be on the same course as GoDaddy when it comes to going public.

I remember when WP Engine was just a few person startup in Austin, so it’s nice to see it grow. It now employs 500 people with most of them in Austin. The company has 75,000 customers and $100 million in annual revenue.

Lisa Box, formerly with Oversee.net and Endurance International Group, is currently Vice President Strategic Alliances and Business Development at WP Engine.


© 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 WP Engine banks $250 million from PE that bought GoDaddy appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Donuts’ first new domain names are starting to drop…
  2. NamesCon acquired by WorldHostingDays
  3. CentralNic swings to loss, billings soar on .XYZ deal
Categories: Domains

#3 in 2017: GDPR and the death of Whois

Domain Name Wire - Thu, 01/04/2018 - 21:46

This is the eighth in a series covering the top stories on DNW in 2017, as ranked by pageviews.

Whois will likely undergo a major overhaul in 2018 thanks to the European Union’s General Data Protection Regulation (GDPR), which goes into full effect on May 25. A story I wrote about the topic was among the most-viewed stories on DNW in 2017.

GDPR is a law to protect the personal information and privacy of European Union residents. It will impact companies around the world that handle data of EU residents. This includes domain name registrars and registries that process domain name registrations.

GDPR was a top story on Domain Name Wire in 2017Click To Tweet

The most visible impact for domain names will be Whois because Whois is essentially a public database of personal information. Many questions remain surrounding what registrars and registries will need to do to comply with the law. ICANN, for its part, doesn’t seem to know and has said it will be lenient on contract compliance regarding Whois as it seeks to figure it out.

GDPR will continue to be a big story in 2018. Stay tuned.


© 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 #3 in 2017: GDPR and the death of Whois appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Will May 2018 be the death of Whois?
  2. Thick Whois for .com delayed 6 months
  3. Wow: this is what public Whois could look like in 2018
Categories: Domains

DealerX auto marketing company is a reverse domain name hijacker

Domain Name Wire - Thu, 01/04/2018 - 15:08

Company goes after rival’s “conquest” domain names.

DealerX Partners, LLC, a company that helps automobile dealers market to consumers, has been found to have engaged in reverse domain name hijacking over the domain names ConquestAutomotive.com, Conquest.email and Conquest.marketing.

In the car industry “conquest” is a term used to refer to winning over a customer that drives a competitor’s car. You will often see promotions on car websites that include “conquest cash” or something similar in which the manufacturer offers discounts when a buyer owns or leases a competitive vehicle.

The domain owner uses the .com domain to market its auto advertising services.

DealerX apparently offers services under the Conquest name. But it failed to mention to the panel that the term is common in the industry. It also didn’t mention ongoing legal proceedings with another party to cancel DealerX’s Conquest Service mark. In finding reverse domain name hijacking, the panel noted “we have a prime example of material evidence omitted from the Complaint”. The panel also noted:

The Complaint also alleges, without evidence, that its mark has acquired renown. Complainant’s essential argument is that Respondent cannot possibly have a legitimate interest in the Domain Names because: Complainant holds a registered mark, and any use of “conquest” in the automotive software field is trademark infringement and per se illegitimate. This position has been roundly rejected by the Panel in this case, based in part on the fact (also undisclosed in the Complaint) that the word “conquest” has a special meaning within the argot of automotive marketing.

DealerX was represented by Phillips Ryther & Winchester. The domain owner was internally represented.


© 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 DealerX auto marketing company is a reverse domain name hijacker appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Egton loses Patient.com UDRP, but it should have been reverse domain name hijacking
  2. Frank Schilling gets RDNH win on 3 letter domain name
  3. Zak Muscovitch gets reverse domain name hijacking win
Categories: Domains

#4 in 2017: A new TLD death spiral?

Domain Name Wire - Thu, 01/04/2018 - 14:48

This is the seventh in a series covering the top stories on DNW in 2017, as ranked by views.

It’s been apparent for years that new top level domains aren’t meeting the expectations applicants had for the domains. A big new TLD cheerleader succumbed to this reality earlier this year.

Frank Schilling announced a major price hike for most of Uniregistry’s top level domain names early in 2017. (This set a lot of balls in motion that are the subject of the #2 story of the year.)

Schilling admitted that his expectations for sales were not being met. He came on the DNW Podcast to talk about the price hike and why it was necessary. Schilling said that he was in the red on many of these domains and wanted to get them to profitability. Also, if he could do it all over again, he would have applied for a different set of domains.

One of the reasons I believe Rightside sold itself this year was because it was becoming evident that it wasn’t going to meet the expectations it set in the market for new TLD revenue. Its revenue from new domains actually started falling quarter-over-quarter when it promised lofty growth within the next few years.

Are new top level domain names dead? Hardly. Some of the biggest players are doing quite well and spinning off lots of cash. But it became clear (or clearer) in 2017 that some models aren’t going to work.


© 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 #4 in 2017: A new TLD death spiral? appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. 3 .com typos that may be applied for as new TLDs
  2. Final new TLD objection tally: Donuts 55, Amazon 24, Google 22
  3. The .ART Premium Name Model: Four Months In
Categories: Domains

RegistrarStats.com to shut down next month

Domain Name Wire - Wed, 01/03/2018 - 18:53

Old school domain data site is shutting down next month.

Donuts has announced that it is shutting down RegistrarStats.com on February 19, 2018. The company acquired the site as part of its acquisition of Rightside last year.

The company says it is shutting down the service “due to dwindling interest and usage in the website service over the past several years.” Paying customers will receive a pro-rata refund of any subscription payments that extended beyond February 19.

RegistrarStats was once a popular site for gathering data on domain names such as registrar market share stats. However, the site has languished in recent years under a paid model. The copyright notice hasn’t been updated since 2013.


© 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 RegistrarStats.com to shut down next month appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

#5 in 2017: The Chinese trademark scam

Domain Name Wire - Wed, 01/03/2018 - 18:34

This is the sixth in a series covering the top stories on DNW in 2017, as ranked by pageviews.

One of the great things about writing DNW is that I get to help people. One way I help people is by writing about scams.

The Chinese trademark scam has been going on for years, but a post I wrote this year detailing the scam in its entirety has attracted a steady stream of visitors. I trust that this means people are doing research before falling for the scam, which means I’m helping people avoid falling for it.

This particular scam starts with an email from a Chinese company warning you that someone is trying to register domain names that include your brand. The company wants to make sure you’re OK with someone else registering the domains.

Of course, no one is trying to register these domains. The company is trying to scare you into registering the domain names and paying it a nice premium to do so.

Another scam still making the rounds is the domain appraisal scam. I heard from a couple people this year who lost thousands on this scam.

Don't fall for the Chinese Trademark Scam!Click To Tweet

 


© 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 in 2017: The Chinese trademark scam appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Top Domain Name News Stories – March 2008
Categories: Domains

Syria.net provides rare look into transfer dispute

Domain Name Wire - Wed, 01/03/2018 - 16:38

Was this domain stolen? If so, the original owner is having a lot of trouble getting it back.

Domain name transfer disputes due to alleged domain theft are usually handled behind the scenes and occasionally in court. That’s why a National Arbitration Forum decision on Syria.net under the Transfer Dispute Resolution Policy (TDRP) is so interesting.

TierraNet, Inc. was the registrar for Syria.net. It received a request to change the email address tied to the domain name. The “owner” submitted a copy of a photo ID with a name matching the domain owner Ahmad A. Hashem, so TierraNet changed the email address.

Recent ICANN rules required that TierraNet place a 60-day lock on the domain due to the email change unless the registrant opts out. This rule is in place to prevent domain theft. But TierraNet failed to place this lock on the domain even though the registrant did not opt out.

The person who requested the email change subsequently transferred the domain name to LexSynergy.

At that point another person purporting to be Ahmad A. Hashem contacted TierraNet and claimed his account was hacked. TierraNet reviewed the original photo ID and determined that the address and zip code on it did not match, suggesting that it might have been fraudulent.

TierraNet filed a TDRP against LexSynergy to try to get the domain back. The panelist determined:

No evidence has been presented that the Gaining Registrar, Lexsynergy Ltd., engaged in any fraudulent conduct in procuring the transfer. Thus, Complainant’s assertion of fraud by Ahmad A. Hashem is not a reason to have refused the transfer. Moreover, there is nothing in the TDRP that permits a registrar to “claw back” the transfer of a domain name if the domain name is transferred in violation of the 60-day lock period.

Because Complainant’s argument regarding “evidence of fraud” is not correct under the TDRP, and because Complainant transferred the domain without complying with 60-day lock, Complainant’s appeal is denied.


© 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 Syria.net provides rare look into transfer dispute appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

15 end user domain name sales including a .net for $70,000

Domain Name Wire - Wed, 01/03/2018 - 14:26

These end users bought domain names over the holidays.

Sedo has published sales data from the two week holiday period, including a great sale of a great .net domain: App.net. It appears that the seller had previously developed a business called app.net.

Other buyers include a sliding door company, a chocolatier and an online shopping rewards site. Regarding the latter, take a look at ShareFlare.com. It’s proof that you can still get a catchy, brandable domain for a reasonable price.

If you like this list, check out previous end user lists here.

App.net $70,000 – Mobiblocks, an app developer in the Seattle area.

LoveCoin.com $25,000 – There’s a coin for everything. The buyer has Whois privacy but forwards the domain to “LOVEcoin official telegram group” on Telegram.

UTime.com $10,000 – Software company IVTime.com. The domain resolves to a login page with the page title “LifePlanner”.

HollywoodPalladium.com $6,107 – Live Nation Entertainment, Inc. bought the domain name matching the popular Hollywood venue.

Doal.com €5,000 – Italian sliding door company Doal Srl.

CryptoTrustee.com $4,999 – Time Value Property Exchange specializes in 1031 real estate exchanges.

SalaryCloud.com $4,900 – Salary.com. The company does not own Salary.cloud.

RPSystems.com $4,000 – Revere Plastics Systems, LLC uses the domain name RevereIndustries.com

Aasuman.com $4,000 – Asuman Cikolata Dukkani is a chocolatier in Turkey.

Kidlo.com €3,750 – Kidlo makes apps for kids.

OnlineNotaryPublic.com $2,419 – American Association of Notaries. I have to say, and online notary public service would be awesome.

Agil.ch €2,241 – agil gmbh in Switzerland

IBR.in $2,000 – IBR Messtechnik GmbH & Co. KG owns the matching .com domain.

Garaji.com $2,000 – Garaji says it is “Revolutionising Auto Care”

ShareFlare.com $2,000 – ShareFlare offers shopping discounts in exchange for your shopping reviews.


© 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 15 end user domain name sales including a .net for $70,000 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. End user domain name purchases including State Street and Live Person
  2. 36 End User Domain Name Purchases
  3. What domain names Time Inc. and others bought at the end of the year
Categories: Domains

#6 in 2017: Police raid a top level domain company

Domain Name Wire - Tue, 01/02/2018 - 18:42

This is the fifth in a series covering the top stories on DNW in 2017, as ranked by pageviews.

A police raid the domain name business? That’s unusual, and the story about it ranks among the top ten most viewed on DNW in 2017.

A big story in the mainstream press this year was Catalonia’s independence referendum and the ensuing protests that occurred. The controversy involved domain names even before the referendum vote occurred.

Spanish authorities asked Fundació puntCAT, the group that operates the .cat domain name for the Catalonian people, to block certain domain names related to the referendum. The group refused.

Then, things got real when Spanish police raided Fundació puntCAT’s offices and arrested its head of IT, Pep Masoliver. The arrest might have been related to concerns other than merely deleting certain .cat domain names.

.Cat is a sponsored top level domain name, not a country code. There are about 100,000 .cat domains registered.


© 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 #6 in 2017: Police raid a top level domain company appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Spanish police raid .Cat domain name registry offices
  2. September’s Top 5 Domain Name Stories
Categories: Domains

The Internet of Things – DNW Podcast #167

Domain Name Wire - Tue, 01/02/2018 - 16:30

What is the future of the Internet of Things and how will it impact our business?

In our first episode of 2018, Stacey Higginbotham of StaceyOnIoT.com joins me on the show to talk about the Internet of Things. Understand what it is, what industries it impacts, the easiest way to get started with the smart home, and how the internet of things might impact web usage and domain names.

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 The Internet of Things – DNW Podcast #167 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. The Internet of Things – DNW Podcast #129
Categories: Domains

Phoenix Chinese Cultural Center developer guilty of reverse domain name hijacking

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

Group tried to take down gripe site.

A developer that recently acquired the Chinese Cultural Center in Phoenix with plans to redevelop it has been found to have engaged in reverse domain name hijacking.

668 North, LLC, which is owned by private equity group True North, acquired the mostly empty mixed-user center last year with plans to redevelop it. Some of those plans irked the local Chinese community, which is concerned about changes the developer plans to make.

Many in the community raised a fuss about the changes and one group registered PhoenixChineseCulturalCenter.com as a way to raise awareness. 668 North filed a cybersquatting complaint against the domain name with National Arbitration Forum.

A National Arbitration Forum panelist ruled that 668 North failed to prove any of the three elements necessary to win its case. The panelist went further, noting that the developer “knew or should have known that it was unable to prove that Respondent lacks rights or legitimate interests in the disputed domain name and that Respondent registered and is using the domain name in bad faith.” For this reason, the panelist found that 668 North, LLC engaged in reverse domain name hijacking by filing the case.


© 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 Phoenix Chinese Cultural Center developer guilty of reverse domain name hijacking appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.