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.

Uniregistry is now Uni

Domain Name Wire - Tue, 12/04/2018 - 17:26

Domain name registrar changes to shorter name.

Frank Schilling’s Uniregistry has changed its brand name to simply Uni.

The move coincided with the launch of a new app last week that makes it easy for users to get email or create a website.

On November 28, the company filed a trademark application with the U.S. Patent and Trademark Office for Uni for several services including domain names, email and web hosting.

Intriguingly for a domain name company, it does not own Uni.com. That domain is owned by an Italian non-profit. For now, the website is still at Uniregistry.com.

While the logo on Uniregistry.com has changed to Uni, you’ll still find references to Uniregistry throughout the site and in emails the company sends.

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

Related posts:
  1. Plans for Frank Schilling’s Uniregistry go way back
  2. A first look at Frank Schilling’s new domain name registrar
  3. .Com domain name winners and losers
Categories: Domains

Tutorial: How to retrieve a list of your GoDaddy Domains

Domain Name Wire - Tue, 12/04/2018 - 16:13

Alvin Brown provides a tutorial on retrieving a list of domains from your GoDaddy account using GoDaddy’s API.

If you’re not familiar with GoDaddy’s Application Programming Interface (API), then you’re missing out on a great opportunity to streamline the management of your GoDaddy domain portfolio.

Why would anyone ever consider using GoDaddy’s API to manage my domain portfolio when GoDaddy provides a user-friendly Domain Manager experience?  That’s the question I hope to reveal and answer in today’s tutorial.

While GoDaddy’s user experience has greatly improved throughout the years (with additional areas for improvement to realize), GoDaddy’s API offers management opportunities for the following areas of interest:

This tutorial will focus on the Domains API section, specifically the GET Domains method — Retrieve a list of Domains for the specified Shopper.

Integrate the Domains method with a landing page and database using a bit of elbow grease, and you could be well on your way to creating a simple domain inquiry tracking system, or at the very least a backup for your domain portfolio.

Getting started

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

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

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

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

To get started with this tutorial, open a text editor of your choice, name and save the following php file: domains.php.

Once the domains.php file is created, define a variable named domains and set it equal to the function we’ll soon discuss: getDomains();.

$domains = getDomains();

Retrieve a list of Domains using GoDaddy API

To retrieve a list of domains using GoDaddy’s API, I’ve chosen to create a function and have given it the name getDomains. Functions are quite helpful in regards to making code more portable and easily managed.

In the case of the getDomains function, it’ll contain PHP and cURL to instantiate the GoDaddy API call to retrieve a list of domains from your GoDaddy account.

I won’t cover all the nitty-gritty details of executing a GoDaddy API call using PHP.  However, there is no need to fear.  A tutorial exists to help get you acclimated: Getting Started With GoDaddy API Using PHP.

As for the specifics of the getDomains function, take a moment to review the first method of the Domains API via GoDaddy’s API Documentation.

The Domains API method contains the following parameters that act as filters when retrieving the list of domains from your GoDaddy account:

X-Shopper-Id – This parameter is the shopper id or account id of the respective account domains are being retrieved.  Although listed as a parameter, this parameter is not set as a query parameter.  The authentication or authorization process we’ll soon discuss replaces the X-Shopper-Id.

statuses – Set this parameter to return domains of a certain status.  There are over 224 available values to select from.  For this tutorial, use ‘ACTIVE’ as the value status value.  See documentation for full list of values.

statusGroupsOnly – Set this parameter to return domains from specified groups.  There are five different values for this field: INACTIVE, PRE_REGISTRATION, REDEMPTION, RENEWABLE, VERIFICATION_ICANN, and VISIBLE.  For this tutorial, a value is not set for this parameter.

limit – Set this parameter for the maximum number of domains to be returned.  For this tutorial, use ‘5’ or another integer as the value.  To return all domains, simply do not set a value for this parameter or forgo using the parameter.

marker – Set this parameter to offset results using a domain.  If you have hundreds of domains in your account, then this parameter could come in handy if you want to return domains after a certain domain. For this tutorial, a value is not set for this parameter.

includes – Set this parameter to include optional details about domains in the response.  The available values for this parameter are as follows: authCode, contacts, nameServers.  For this tutorial, a value is not set for this parameter.

modifiedDate – Set this parameter to only include results that have been modified since a specified date.  For this tutorial, a value is not set for this parameter.

Now that parameter options have been identified, it’s time to define and set the values accordingly.  Set the statuses and limit parameters to the following values using PHP variables status and limit respectively:

$status = ‘Active’;

$limit = ‘5’;

Using GoDaddy’s API Documentation, define a url variable and its value to be the base API url to retrieve domains with status and limit variables and their respective values appended to the url as query parameters.

$url = “https://api.godaddy.com/v1/domains?statuses=$status&limit=$limit”;

Next, change {API_KEY} and {API_SECRET} values to be your respective API credentials.  Generate an API key and secret to be used when instantiating and authorizing GoDaddy API calls.

Once API key and secret credentials are in place, the API call can be made to request and retrieve a list of active domains associated with your GoDaddy account.

The API call is made using PHP’s built-in cURL method.  The getDomains function returns a decoded json response object (i.e., dn variable returned at end of function) — think a list of your specified domains — containing domains.

Error checking and parsing domain response

While you likely don’t need to add error checking, it’s always in your best interest too.  To do so, I use an if else statement to check for errors by simply checking the response from the domains variable that is set equal to the getDomains function.

If the domains variable has an object key set for code, this means an error of some sort occurred when instantiating the GoDaddy API call request.

Within the if statement, simply explode and parse the response data for the message object key to obtain and display a human-readable error message. Feel free to refer to GoDaddy’s API Documentation for additional explanation and definition of each error.

Within the else statement, I can proceed to parse the response data and display the following attributes for each domain:

  • createdAt
  • domain
  • domainId
  • expirationProtected
  • expires
  • holdRegistrar
  • locked
  • nameServers
  • privacy
  • renewAuto
  • renewDeadline
  • renewable
  • status
  • transferProtected

Most of the aforementioned attributes are intuitive and somewhat self explanatory.  Feel free to refer to GoDaddy’s API Documentation for additional explanation and definition of each attribute.

For this tutorial, I display only the domain name immediately followed by a line break using and echoing the msg variable to the web browser.

Time to test your technical chops

Well, you’ve endured to the end!  Now it’s time to test your technical chops.

The code in its entirety should lie similar to the gd-domains.php file contained in the YourGoDaddyDomains.zip file.

DOWNLOAD YourGoDaddyDomains.zip

PLEASE DO NOT FORGET TO ADD YOUR RESPECTIVE GODADDY API CREDENTIALS OR THIS TUTORIAL WILL NOT WORK!

Download, extract, and save the gd-domains.php file to an accessible web directory. Open gd-domains.php via a web browser (just like how you would visit a web page – http://yourdomain/gd-domains.php).

Once gd-domains.php is opened and executed via a web browser, your web browser should display a list of domains identical to domains listed in your GoDaddy account.

Closing Thoughts

I hope this and previous tutorials spark your interest as well as ideas for how GoDaddy’s API can be used to become more efficient and effective in managing your domain portfolio external of GoDaddy’s native user interface and experience.

As I stated in the opening, integrating a landing page and database with this tutorial provides an opportunity to create a simple domain inquiry tracking system, or a backup of your domain portfolio at least.

In closing, please do not hesitate to leave me questions, comments, or propose ideas for future tutorials using GoDaddy’s API.

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

No related posts.

Categories: Domains

.Com Winners: Some shakeup in the top 10

Domain Name Wire - Tue, 12/04/2018 - 14:44

Top 10 registrars juggle places in latest monthly report.

ICANN has published the latest official data from Verisign (NASDAQ: VRSN) about the .com registry. This registrar-by-registrar report covers August 2018.

Note that HiChina is now listed as Alibaba in the official reports, so I’ve changed the name on this report.

Here’s how registrars did in terms of new .com registrations. There was a bit of shifting as Endurance had a good month and NameSilo dropped a bit.

1. GoDaddy.com* (NYSE: GDDY) 920,365 (916,032 in July)
2. Alibaba (HiChina) 224,383 (237,296)
3. Tucows** (NASDAQ:TCX) 200,563 (212,279)
4. Endurance+ (NASDAQ: EIGI) 153,130 (127,916)
5. Xin Net Technology Corporation 144,999 (129,492)
6. NameCheap Inc. 139,914 (124,011)
7. Web.com++ 103,022 (93,535)
8. Google Inc. (NASDAQ: GOOGL) 95,841 (94,033)
9. NameSilo 86,955 (127,451)
10. 1&1 47,333 (not in top 10)

Here’s the leaderboard of the top registrars in terms of total .com registrations as of the end of August 2018. There were no changes, but I suspect that once we see the October or November report, Google will have surpassed GMO.

1. GoDaddy* 48,907,328 (48,659,723 in July)
2. Tucows** 12,816,784 (12,834,441)
3. Endurance+ 7,357,344 (7,411,874)
4. Web.com++ 6,722,545 (6,721,550)
5. Alibaba 5,813,977 (5,683,428)
6. Namecheap 4,354,411 (4,312,430)
7. 1&1 3,701,944 (3,716,477)
8. Xin Net Technology Corporation 2,376,346 (2,260,541)
9. GMO 1,993,491 (2,011,266)
10. Google 1,903,695 (1,840,869)

Many domain companies have multiple accreditations and I’ve tried to capture the largest ones. See the notes below.

* Includes GoDaddy and Wild West Domains
** Includes Tucows and Enom
+ Includes PDR, Domain.com, FastDomain and Bigrock. There are other Endurance registrars, but these are the biggest.
++ Includes Network Solutions and Register.com

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

Related posts:
  1. How domain name stocks did on GoDaddy’s IPO day
  2. Tucows sells some domain names to GoDaddy
  3. GoDaddy reports earnings, Domain revenue tops $300 million
Categories: Domains

NameJet sales helped by short domains

Domain Name Wire - Mon, 12/03/2018 - 20:29

Three digit and NL domain sell for $100k+.

NameJet (which is now wholly owned by Web.com) had a bump in its monthly sales numbers thanks to selling two short domains last month. Overall, NameJet sold 63 domains for $2,000 or more in November, totaling $554,000.

Two domains sold for six figures including 864.com for $147,000 and 1M.com for $112,000. Two three-letter .com’s also traded hands: NZD.com for $25,000 and TIW.com for $20,000.

Here are some other notable sales followed by the full list:

Soundbites.com – $15,108 – a spectacular name for a spoken-word audio site, perhaps podcasting? Could also be used for new, politics and more.

MedicalExam.com – $7,877 – a nice exact match, although the plural might be better depending on your planned use.

Burbank.net – $4,000 – Domain financing company Lendvo appears to be the seller.

ChilliPepper.com $3,336 – Not necessarily a typo; the British spelling has two Ls.

DomainPrice 864.com147000 1m.com112000 nzd.com25000 tiw.com20000 soundbites.com15108 alertpay.com10600 qy.org10000 globalcare.com9300 charteryacht.com9171 jeny.com8500 medicalexam.com7877 jaden.com7144 cinematographer.com7100 saho.com7088 nebi.com6700 bccb.com6645 curative.com6500 greeninsurance.com5100 staunton.com5099 withyou.com5022 shortcode.com4905 dowork.com4489 gapo.com4000 burbank.net4000 millimeter.com3855 facecam.com3700 mindforce.com3600 handhelds.org3366 chillipepper.com3336 86858.com3109 usis.com3100 jepa.com3000 pacificpartners.com3000 attbi.com2956 pa1.com2900 sextoyshop.com2850 familymediation.com2810 fremontstreet.com2802 blackletter.com2801 presidentsclimatecommitment.org2801 ancore.com2755 claimswork.com2700 detoxing.com2655 plovdiv.net2603 braind.com2588 hotelsuk.com2507 foodnet.com2500 rearranged.com2500 casinotop.com2500 newoffice.com2488 nuworld.com2478 35z.com2443 yhdj.com2417 pitlane.com2365 ifirst.com2333 z9z.com2300 worldhelp.com2300 sufresh.com2210 gaige.com2210 timber.org2200 cbil.com2103 glrppr.org2100 pinless.com2020

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

No related posts.

Categories: Domains

Web.com acquires Tucows’ half of NameJet

Domain Name Wire - Mon, 12/03/2018 - 18:19

Deal is a sign of the times in the expired domain business.

Web.com is now the sole owner of domain name auction site NameJet after acquiring Tucows’ (NASDAQ: TCX) interest in the business.

NameJet was created as a partnership between Enom and Network Solutions (now part of Web.com) in 2007 at a time when SnapNames was dominating the direct-transfer expired domain business. The deal meant that Network Solutions’ expired domain inventory would move to the new NameJet platform, delivering a blow to SnapNames. Oversee.net had just acquired SnapNames but knew about Network Solutions leaving the platform before completing the acquisition.

In 2014, Web.com acquired Snapnames from KeyDrive for $7.4 million. That meant that Web.com owned all of Snapnames and half of its competitor NameJet.

SnapNames and NameJet later combined forces on grabbing pending delete domains, which are domains that make it through the deletion cycle and are deleted by the registry.

Tucows acquired Enom last year and Enom’s half ownership in NameJet was a sort of “gift with purchase”. After the acquisition closed, Tucows shifted its expired domain name inventory from GoDaddy to NameJet, only to switch back to GoDaddy later in the year.

This was a big indication that GoDaddy was far better at monetizing Tucows’ expiring domain names than NameJet.

Today’s news makes sense. In fact, it probably makes sense to merge the SnapNames and NameJet platforms.

The big question is if Enom domains will remain on NameJet and for how long. This was obviously part of the negotiation and ultimate purchase price. If Enom leaves the platform for GoDaddy at some point in the future, it will further degrade NameJet’s role in the marketplace.

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

Related posts:
  1. Web.com paid $1.3 million for about 100 eNom registrars
  2. Tucows shifts expired domain name inventory to NameJet
  3. How NameJet can right the ship
Categories: Domains

Understanding .Brand domains – DNW Podcast #213

Domain Name Wire - Mon, 12/03/2018 - 16:30

Inside the world of .brand top level domain names.

Companies applied for many types of new top level domains in the current round of expansion. Hundreds of them were for so-called “.brand” domain names that match those of companies and their trademarks. On today’s show we talk with Tony Kirsch, who runs the .brand program for domain registry Neustar, to learn more about .brand domains and how they are playing out so far.

Also: A new TLD record, XFL Teams, DataRecovery.com, T-Mobile Money and more.

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

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

Related posts:
  1. How to avoid UDRP – John Berryhill – DNW Podcast #170
  2. Panama, Sherpas and the Domain Market with Andrew Rosener – DNW Podcast #180
  3. John Pollard: How to grow the usage of domain names – DNW Podcast #188
Categories: Domains

USMCA.com case study

Domain Name Wire - Mon, 12/03/2018 - 15:17

Building a site on USMCA.com has led to significantly more traffic.

In October I wrote about creating a website for USMCA.com using GoDaddy WordPress hosting and the included Beaver Builder plugin. I thought I’d provide a bit of an update about how the site is performing.

As background, USMCA is short for United States-Mexico-Canada Agreement, a new trade agreement that is designed to replace NAFTA. It still needs U.S. congressional approval.

I bought USMCA.com the day the deal was announced in a buy now transaction. I parked it for a few days and received lots of purchase inquiries, but none that met my requirements. So I decided to see what happened if I developed the domain into a website. Could I attract significantly more eyeballs to the site than just the type-in traffic it received as a parked domain?

Fast forward to last Friday when U.S. President Donald Trump, Canadian Prime Minister Justin Trudeau and Mexican President Enrique Peña Nieto signed the agreement during the G-20 summit. I checked in on the stats to see how the site was doing. Here’s a chart showing page views:

The top of the chart is 2,000. In a typical day the site gets roughly 100 pageviews but it spiked after USMCA was in the news again. I expect more spikes like this as it is debated in Congress.

The traffic comes mostly from type-ins and search and mostly the latter. The search traffic is primarily from Bing and DuckDuckGo (which sometimes pulls from Bing). Most of the searches are for USMCA but there are also long tail searches and many for USMCA.com.

My goal is still to sell the domain name to a group that can benefit from it, but developing the site has been an interesting exercise.

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

No related posts.

Categories: Domains

Domains suggest which cities might get XFL football teams

Domain Name Wire - Fri, 11/30/2018 - 14:34

21 cities are likely in the running for football teams.

In which cities will the new, faster version of American football land? Some domain name registrations are a good hint at possible cities.

XFL is a new (again) football league that wants to reimagine the sport. WWE chairman Vince McMahon tried to launch the XFL in 2001 and it failed. Now it’s time for another go with a season starting in 2020.

“We are given a game that lacks rhythm and has been overtaken by commercials, timeouts, complex rules and analysis,” its website at XFL.com states about the NFL.

The league will hold a press conference on December 5 to unveil first-year cities. Yesterday the league registered a bunch of domain names for possible cities. The domains take the format of CityXFL.com, XFLCity.com and XFLCityAbbreviation.com.

For example, it registered AtlantaXFL.com, XFLAtlanta.com, and XFLAtl.com. Here are the cities that associated names were registered for:

Atlanta
Austin
Chicago
Cleveland
Dallas/Arlington
Detroit
Houston
KansasCity
Los Angeles
Minnesota
Nashville
NewYork
Orlando
Philadelphia
Phoenix
Pittsburgh
San Francisco
Seattle
St. Louis
Washington DC
Tampa Bay

While the league is unlikely to launch that many cities at first (the plan is eight cities), it is likely that the planned cities are on the list.

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

Related posts:
  1. NBA, MLB, and NFL apply for top level domains
Categories: Domains

DataRecovery.com, a $1.7M domain 10 years later

Domain Name Wire - Thu, 11/29/2018 - 20:59

DataRecovery.com president Benjamin Carmitchel says his big domain purchase was worth it.

In 2008, ESS Data Recovery bought the domain name DataRecovery.com from Associated Computers, Inc. of Minnesota for $1.659 million. I recently caught up with company president Benjamin Carmitchel to find out how the deal played out now that he has ten years of experience with the domain.

The company formally changed its name from ESS Data Recovery to DataRecovery.com, Inc. after acquiring the domain name, making it easier for customers to remember its name.

Switching to DataRecovery.com also helped the company win new business without advertising.

“Before we bought the domain name we were spending a quarter of a million to half of a million a year in advertising on things like Google Adwords and print ads,” Carmitchel said. Now the company has eliminated almost all of its advertising because it’s so busy.

Carmitchel attributes a lot of the success to the domain name.

“It’s the domain name along with building a reputation around that,” he said. “It helped distinguish our company. At the time there were only four other data recovery companies in the United States. As time went on, now there’s probably thousands so it really distinguishes us.”

The seller financed the purchase of the domain name so DataRecovery.com, Inc. has been paying for it over the past ten years. The monthly payment was like an advertising cost to the company. The domain is finally paid off and Carmitchel has a great domain name that will continue to pay dividends for years to come.

 

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

Related posts:
  1. Flippa acquires Domain Holdings
  2. Shills, Insiders, & Front Runners – 5 Bidding Scandals
  3. GoDaddy “for sale” tweak leads to 41% more aftermarket sales revenue
Categories: Domains

Practical Implications of GDPR so far

Domain Name Wire - Thu, 11/29/2018 - 17:33

It’s been tough adjusting to less Whois data.

It’s been about 6 months since the European Unions General Data Protection Regulation (GDPR) went into effect and many registrars obscured Whois records as a result. Here are some of the practical implications this has had for me personally as someone covering the domain business for DNW and as a domain investor.

Verifying domain ownership is more difficult

I’ve had several instances this year when I needed to verify who owned a domain name for a transaction and had difficulty doing so. In one case, a friend was buying a domain and wanted to verify that the person who previously owned it still did before doing the transaction. The registrar had masked Whois. I was able to find a recent public record showing the owner.

In another case, someone wanted to buy a domain and was at an impasse because the Whois record was masked and the domain didn’t resolve. There were no public Whois records so the potential transaction died.

Finally, I helped a friend who was trying to track down a domain owner. There was an active site but the owner didn’t identify himself on the site. There were some old Whois records but the most recent ones had info for a disconnected phone number and an email that bounced. Finally, by going further back in historical Whois records I was able to find a name and track the person down using other databases.

While historical Whois records from services like DomainTools help in some cases, the value of these records is degrading every day as new masked records are added.

It’s harder for people to reach out to me via whois

There are good reasons people reach out to me using Whois (want to buy a domain) and bad reasons (spam).

Fortunately, GoDaddy still displays contact info via web-based Whois. This has helped facilitate transactions this year. Most of my domains are at GoDaddy but it’s possible I’ve missed inquiries on domains at other registrars.

Finding domains for end-user sales reports is challenging

It’s a lot harder to find end user sales to report in my weekly end user reports. I can only find a handful each week based on Whois records so I have to dig deeper and hope that sites are already being developed. This means fewer names on the list.

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

Related posts:
  1. Domain thoughts: Purple.com, GoDaddy, fast transfer and GDPR
  2. Domain investors should keep their WHOIS public
  3. Top 5 Domain Name stories from January
Categories: Domains

A smart marketing idea for local service businesses

Domain Name Wire - Thu, 11/29/2018 - 14:47

Service businesses should use hyper-targeted referral marketing.

Whenever I interact with a local service company such as a carpet cleaner or pest control, I take a look at how they are marketing. I think most are missing a big opportunity for referral marketing.

So I was happy to see a window washing company do something smart, although the execution could be better.

The company cleaned a neighbor’s windows and sent this postcard to us:

The flip side has information about the cleaning company and a special offer.

Good idea, but this is what I think companies should do.

  1. Call or email the customer to make sure they were happy with the service. Perhaps through an automated email survey.
  2. Ask the customer if you can send a letter to their neighbors telling them that they provided the service for you–using your name. The letter includes a discount offer for customers if they mention the letter.
  3. Offer the customer a $10 (or whatever is reasonable) credit toward future service for every neighbor that books the service from the letter.

It’s a bit more hands on but could be automated easily.

The problem with the postcard example is that I have no idea how good of a job they did and who they did it for. Sure, a neighbor decided to hire them, but many times I hear neighbors gripe about their contractors.

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

Related posts:
  1. .Marketing and .Holiday each pick up 2,000+ domains on first day
Categories: Domains

29 end user domain sales up to $500,000

Domain Name Wire - Wed, 11/28/2018 - 19:15

An organic products company, ethanol distributor and insurance company recently bought domain names.

This week is a double issue of end user sales from Sedo since we skipped last week for Thanksgiving. There are a lot of the domains on the list this week, led by Kush.com at $500,000. The buyer is unknown at you could stretch to say it might be an investor, but it appears the buyer is building out the site.

Kush.com was one of 29 end user sales I uncovered.

Check out the list below, and you can view previous lists like this here.

Kush.com $500,000 – The buyer isn’t known yet, but the site is under development. Apparently, the domain wasn’t worth $3 million.

Databased.com $12,000 – Databased is a sales team analytics company.

Nedstar.com $11,500 – Nedstar sells ethanol and various chemicals.

SkyOrganics.com $11,500 – This forwards to Skyorganics.us; the .com is now owned by a health and beauty organic products company.

Wugen.com $9,999 – Wugen is a biotech company that is creating gene editing technology.

Potex.com €8,000 – An acronym that stands for Perpetual Options Token Exchange. According to the site, it will house a new global asset derivatives token exchange.

ICATOnline.com $6,000 – ICAT Managers, LLC is an insurance claims service that owns the domain name ICAT.com.

TeamGenius.com $5,300 – Team Genius Systems, Inc. provides software to evaluate sports player performance, helping them manage tryouts, camps, etc. It has been using the domain MyTeamGenius.com.

Blague.com €4,888 – Blague is French for joke and this website offers exactly that.

PMSol.com $4,700 – This is short for Program Management Solutions, a company that uses the loooong domain programmanagementsolutions.net.

Colouration.com $4,000 – Colouration will be a cosmetics company launching next year.

Bauerfeind.in €3,500 – Bauerfeind AG is a German health care equipment company. This purchase was likely defensive.

PlaceTag.com $3,495 – This looks to be a new company from Magical, a science and technology startup company that invents, funds, and incubates new technologies into businesses.

Frutop.com $3,300 – Frutop sells netting systems to protect crops, parking lots and more. It uses the domain Frutop.it, and the .com now forwards to the Italian ccTLD.

Xreference.com $3,200 – Xreference is a business administration system.

Pocas.com $3,200 – Pocas International sells healthy foods and drinks.

Triploop.com $3,200 – Triploop offers technology for group trip providers…think itineraries, updating about travel changes, etc.

SI24.com $3,000 – Signal Iduna is an insurance company that uses the domain name SI24.de.

SysConf.com $3,000 – SysConf Limited is a Unix consulting company in Hong Kong.

Advertas.com $3,000 – Purchased by Advertas, which claims to be “The Technology Company’s Marketing Firm”. This is a full-service marketing agency out of Houston, TX.

Cipatex.com $3,000 – A manufacturer of fabric coverings operating out of São Paulo, Brazil. They now own the .com of their company name but are still using Cipatex.com.br for their website.

DentsuaegisNetwork.at €2,999 – Currently forwards to Dentsu.at. Dentsu Aegis Network, or “DAN”, is an Austrian Digital Communications Agency and Network.

SchutzShoes.com $2,988 – Women’s shoes company Schutz Shoes. It forwards this domain to Schutz-Shoes.com.

MandMInsurance.com $2,700 – Musselwhite & Michel Insurance LLC in Mississippi.

AmbienteDirect.nl €2,500 – Forwards to Ambientedirect.com, the site for Ambiente Direct, an furniture and design eCommerce siteWith this purchase they now own the ccTLD for the Netherlands.

Viewsport.com $2,400 – ViewSPORT is an athletic clothing company that uses the domain name Viewsport.us.

TidePowderMBG.com $2,392 – Procter & Gamble for obvious reasons.

Comprara.com £2,390 – Comprara is a procurement services company.

Spreadshirt.co $2,000 – Print-on-demand company Spreadshirt bought yet another domain on Sedo.

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

Related posts:
  1. Forward U.S. bought domain for $1,500
  2. These end users just bought domain names
  3. End user domain name sales up to $90,000
Categories: Domains

Kaiser Premanente goes on the defensive in #KaiserDontDeny mental health battle

Domain Name Wire - Wed, 11/28/2018 - 15:38

Domain name registrations include key employees/board members and “dontdeny”.

A graphic from NUHW’s #KaiserDontDeny campaign.

Health care provider Kaiser Permanente has apparently gone on a defensive domain name registration binge in light of a campaign against its mental health practices.

National Union of Healthcare Workers (NUHW) launched a social media campaign last month bringing attention to patients having to wait a long time for follow-up mental health care appointments. It features Kaiser Permanente mental health clinicians and their messages about how they believe the company is violating state and federal law. The campaign uses the hashtag #KaiserDontDeny.

Yesterday, a company registered domain names featuring Kaiser Permanent personnel and “dontdeny”. While the domains are registered with Whois privacy protection, Kaiser uses the brand protection registrar Mark Monitor where the names are registered. NUHW uses other domain name registrars.

Here are some of the domains:

bernardjtysondontdeny.com, bernardtysondontdeny.com – Bernard Tyson is Kaiser Permanente’s CEO

arthursouthamdontdeny.com, arthursouthammddontdeny.com – Arthur Southam is Kaiser’s EVP of Health Plan Operations

becharachoucairmddontdeny.com – Bechara Choucair is SVP and Chief Community Health Officer of the Kaiser Foundation Health Plan

cynthiatellesontdeny.com – Cynthia Telles is on the Board of Directors

Other names include:

davidhoffmeisterdontdeny.com, davidjbargerdontdeny.com, donmordecaidontdeny.com, donmordecaimd.com, edellisondontdeny.com, edellisonmddontdeny.com, edwardellisondontdeny.com, edwardellisonmddontdeny.com, edwardpeidontdeny.com, eugenewashingtonmddontdeny.com, gregaadamsdontdeny.com, gregadamsdontdeny.com, gregoryadamsdontdeny.com, janetliangdontdeny.com, jeffepsteindontdeny.com, judithjohansendontdeny.com, kathrynbeiserdontdeny.com, kathybeiserdontdeny.com, kimkaiserdontdeny.com, leslieheiszdontdeny.com, megporfidodontdeny.com, patcourneyamddontdeny.com, patrickcourneyamddontdeny.com, ramonfbaezdontdeny.com, reginabenjamindontdeny.com, reginabenjaminmddontdeny.com, richardshannonmddontdeny.com, richardsisaacsdontdeny.com, richisaacsdontdeny.com, richisaacsmddontdeny.com

While it’s common to defensively register domain names, it seems like there are too many possible variations to register them all.

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

No related posts.

Categories: Domains

T-Mobile rebirths T-Mobile Money name, registers a bunch of typos

Domain Name Wire - Wed, 11/28/2018 - 14:44

Company registers 75+ domain names to protect its T-Mobile Money name.

Back in 2016 T-Mobile (NASDAQ:TMUS) killed its Mobile Money banking program for the unbanked. It now appears the company is trialing a new program with a similar name.

T-mobilemoney.com, a domain name T-Mobile used for the old program, now features a new program offering digital banking and a mobile wallet.

Yesterday, the company registered at least 75 typos and variations of t-mobilemoney.com and tmobilemoney.com, suggesting T-Mobile is going big on this new service. Here’s a list of some of the domains the company registered yesterday

t-m0bilemoney.com
t-mbilemoney.com
t-mboilemoney.com
t-mibilemoney.com
t-mobielmoney.com
t-mobilemoney.click
t-mobilemoney.sucks
tm-obilemoney.com
tm0bilemoney.com
tmboilemoney.com
tmibilemoney.com
tmobielmoney.com
tmobikemoney.com
tmobildmoney.com
tmobilem0ney.com

That’s an extensive typosquatting prevention plan. I’m also intrigued by its choice to register .click while skipping many other new top level domains.

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

No related posts.

Categories: Domains

Online.Casino domain sells for record-breaking $510,000

Domain Name Wire - Wed, 11/28/2018 - 14:11

Donuts beats its previous records for a new top level domain sale.

New top level domain company Donuts has sold the domain name Online.Casino for $510,000, a record for a publicly-disclosed sale of a second level domain under a new TLD.

The sale tops Donuts’ previous record-setting sales of home.loans for $500,000 and vacation.rentals for $500,300.

Donuts completed the all-cash transaction in June.

“It’s another large sale to an end user and we’re excited to follow their site launch next year,” Matt Overman, SVP of Sales for Donuts, told Domain Name Wire. “We expect big things from online.casino similar to home.loans and vacation.rentals.”

Overman was not yet able to disclose the buyer.

Some other casino domains have sold for high prices recently. Casino.online sold for $201,250 in March 2017. Last month Sedo sold Casino.ro for €220,000.

The online.casino sale does not appear to be connected to these other sales, at least as far as I can tell from Whois.

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

Related posts:
  1. Vacation.rentals domain name sells for record $500,300
  2. 4 more Donuts domain names entered GA yesterday. Here are the numbers.
  3. Entrepreneur pays $500,000 to acquire Home.loans domain name
Categories: Domains

15% of new TLD auction proceeds for marketing? That’s all anyone cares about.

Domain Name Wire - Tue, 11/27/2018 - 20:24

New TLD companies pile on for awareness campaign.

How should ICANN spend the $240 million it has raised by auctioning rights to new top level domain names?

Last month, ICANN asked the community for feedback on initial ideas for how to allocate the money. It was primarily interested in some of the mechanisms and procedures for allocating the money.

So far, however, all of the comments are from new top level domain name operators backing an idea that .Club put forward to allocate 15% of the money to an awareness campaign for new TLDs.

Hey, it’s worth asking. After all, ICANN has already decided to skim $36 million off the top to plug budget shortfalls.

Perhaps the lack of diversity of comments is why ICANN decided to extend the comment period by two weeks.

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

Related posts:
  1. Minds + Machines nets $8.4 million from auctions, .Cloud and .Book settled
  2. GMO loses community bid for .Shop domain name
  3. This week’s new TLDs (retroactive edition)
Categories: Domains

.Be will take down bad domains in 24 hours

Domain Name Wire - Tue, 11/27/2018 - 15:29

New policy speeds up old process for blocking domains used for fake web stores and phishing.

A new policy will help take down .be domains within 24 hours when used for fraudulent purposes, such as phishing.

DNS Belgium, the group that manages Belgium’s .be country code domain, announced that it will start taking down domains used for fraudulent purposes within as little as 24 hours. The new policy goes into effect on December 1.

The group can delete domain names at the request of FPS Economy, which is sort of like the trade and economic competitiveness arm of the government.

Names used for sites selling fraudulent goods or phishing websites can be blocked within 24 hours. The registrant has two weeks to respond to such action and the domains will be deleted after 6 months.

Previously, FPS Economy couldn’t ask DNS Belgium to block websites based on content, only fraudulent or inaccurate identification data. An application had to be filed with the crown prosecution service in order to block a domain, a process which takes at least two weeks.

DNS Belgium says there are “several hundreds” of fraudulent websites each year.

This approach differs from some other country codes in Europe. For example, Denmark has found that cracking down on false ownership information has eliminated almost all sites used for fake stores. You can learn more about Denmark’s approach on DNW Podcast #208.

 

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

Related posts:
  1. ICANN files motion to dismiss Donuts’ .Web lawsuit
  2. Court tosses Donuts’ .Web lawsuit because Donuts promised not to sue
  3. Telepathy sues after getting RDNH win
Categories: Domains

The secure padlock doesn’t mean a website is safe

Domain Name Wire - Tue, 11/27/2018 - 14:26

Nearly half of phishing sites now use SSL.

Google has led a big push in recent years to get all websites to use Secure Sockets Layer (SSL). You know a site uses it when it starts with https:// instead of http:// and the browser shows a padlock next to the URL.

People have been trained to look for sites that are secure but this has created a false sense of security. According to new research from PhishLabs, half of all phishing sites detected last quarter used SSL.

SSL merely means that the data sent between you and the website operator is encrypted. So if you send data to a phisher using SSL, congratulations…you just securely sent your data to a criminal.

Perhaps this false sense of security is why Google is starting to downgrade the positive designations it uses in Chrome to identify sites using SSL. It no longer shows a green padlock with “Secure” next to the URL. It’s just a gray padlock. Eventually, sites with SSL will show no designation in Chrome; sites without it will show “Not Secure”:

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

Related posts:
  1. Another domain-registration-date-for-security patent is filed
  2. Phishing Scam Targets USAA
  3. Domain name sinkholes and those funky domain registrations
Categories: Domains

A NamesCon suggestion, plus auction submissions now open

Domain Name Wire - Mon, 11/26/2018 - 19:36

You’ll want to be there on Sunday this year.

NamesCon Global in Las Vegas is just two months away, so it’s time to get your ticket and book travel. A Cyber Monday sale for 25% off ends today; use code FridayMonday.

The event has shifted up in the week compared to a couple of years ago. While activities used to kick off Sunday afternoon and go through Wednesday night, Sunday has become a more important part of the conference. For that reason, I decided this year to arrive on Saturday night and stay through Wednesday morning.

Also, Right of the Dot has opened submissions for its NamesCon auction. The auction will include a live event on January 30, 2018 during NamesCon and a follow-up auction online. The online portion has previously been on NameJet, but this year might take place on GoDaddy.

 

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

Related posts:
  1. Could NamesCon hit 1,000 attendees next year?
  2. A Review of last week’s NamesCon conference
  3. The DNW NamesCon recap
Categories: Domains

Insurance company Cover paid $825,000 to get Cover.com

Domain Name Wire - Mon, 11/26/2018 - 17:31

Domain name added trust to brand, founder says.

Insurance brokerage and comparison service Cover paid $825,000 to buy the domain name Cover.com last year, the company disclosed.

Co-founder and CEO Karn Saroya released details of the purchase in a blog post last week.

The company worked with brokers to buy the domain name from DigiMedia. $75,000 of the total payment was for the domain brokers, so the net was $750,000.

Saroya explained why it was a good investment:

We sell an intangible product and at the end of the day, we’re in the trust business. Owning Cover.com has lent an extra level of legitimacy to the brand and this, in turn, has translated into sales.

We have seen firsthand how it helps get people over the hump when it comes to investing their money with us. Immediately after moving to Cover.com we saw our conversions rise, largely because customers would cross-reference our app on the internet before they made the purchase decision.

Saroya noted that it doesn’t make sense for all businesses to spend this much on a domain, especially very early stage companies.

Hat tip: George Kirikos. Also see Elliot’s post.

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

No related posts.

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