skip to content

News

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

Email analytics firm 250ok scores $2.6 million Series A

Domain Name Wire - Fri, 10/13/2017 - 15:14

Company helps marketers reach their target, and domain name owners are part of the puzzle.

250ok CEO Greg Kraios

Email analytics firm 250ok has secured a $2.6 million Series A funding led by Arthur Ventures.

The Indianapolis company helps marketers make sure their messages are reaching consumers’ inboxes and improve effectiveness.

One way it does this is by ensuring the marketers have clean email lists. It buys data from third parties to see if messages are landing where they shouldn’t. The company also created MailboxPark to augment this data.

Mailbox Park allows domain name owners to direct email traffic on parked domains to the service. Mailbox park pays for all commercial emails received at these addresses.

This data is valuable because parked domain names shouldn’t receive email. Yet, as any domainer who has set up email (or used Mailbox park) knows, these domains can receive lots of email. Learn more about 250ok in this podcast.


© 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 Email analytics firm 250ok scores $2.6 million Series A appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Escrow.com acquired for $7.5 million
  2. Google Alphabet news causes CentralNic shares to jump 50%
  3. Escrow.com launches Concierge Transfer service
Categories: Domains

How to accept payments on your website

Domain Name Wire - Thu, 10/12/2017 - 15:46

No matter how great your eCommerce shop looks, you never reap any of the benefits unless you get a prospective customer to make an actual purchase. Your site visitors will never make a purchase unless they feel like they can trust you 100% with their financial information.

Choose a secure, feature-packed payment processor to finalize online transactions.Click To Tweet

There is a lot of confusion between the terms payment gateway and payment processor when it comes to online stores. Though each one plays a role in the chain of action that makes up payment processing, the lines between the two can become blurry.

Let’s do a quick rundown on payment gateways and processors and then focus on the different types of payment processors available to you.

What is a Payment Gateway?

A payment gateway is a secure online portal that works with your customers when they enter their payment information. It authorizes the payment and can be thought of as the point-of-sale terminal of your eCommerce shop.

In short, the payment gateway collects your customer’s payment information. From there, it either finalizes the transaction (as is the case with third-party payment gateways such as PayPal) or connects with your website’s payment processor to finish the transaction.

Common payment gateways for WordPress eCommerce sites include:

  • PayPal
  • net
  • Stripe
  • Braintree

Keep in mind that many WordPress eCommerce solutions, such as WooCommerce, include multiple payment gateways such as the ones mentioned above. And typically, you do not need a payment processor to finalize most WooCommerce transactions.

However, some eCommerce platforms do require a payment processor. This is especially true for retailers that that gross millions in sales a year.

What is a Payment Processor?

Payment processors, also called merchant accounts, transmit financial information between your website, the customer’s issuing bank, and the acquiring bank (which is yours).

After a customer has made a purchase on your website and has entered their payment information (such as their credit card numbers), the payment processor then executes the payment and finalizes the transaction.

In fact, payment processors are responsible for the following

  • Managing the relationships between your business and credit card companies
  • Handling your customers’ personal and financial information
  • Processing transactions by withdrawing money from your customer and crediting it to your account
  • Transferring funds to your bank account

Keep in mind that sometimes the same company will provide online shop owners both a payment processor and multiple payment gateways for finalizing online transactions. However, it is also possible for you to use two separate companies if you want to.

Let’s take a look at some of the most common WordPress payment processors so that when it comes time to open up shop you can be fully prepared.

Top WordPress Payment Processors 1. Selz

Selz gives website owners the ability to build an eCommerce store right on top of an existing website or blog. For instance, they offer pre-defined themes, a custom domain and free SLL certificate, built-in social sharing, and even the ability to sell from your Facebook page. In addition, you can utilize the built-in buy buttons, access sales metrics, give customer discounts, and even integrate a shopping cart.

Additional features include:

  • Install the free Selz WordPress plugin for basic eCommerce function
  • Easily integrate with your WordPress website in minutes
  • Use Selz Pay, PayPal, or 2Checkout as payment gateways for processing credit cards
  • Rest assured the latest SSL encryption is in place for secure transactions
  • 100+ currencies accepted
  • Customized order confirmations with upsell and cross sell capability
  • Get paid weekly using Selz Pay

PRICE: Starting at $12.99/month

2. Helcim

Helcim is an all-purpose payment processor that works in–person, via mobile device, and as an online eCommerce credit card processor. Implement recurring billing cycles, email invoice requests, and host shopping carts such as Ecwid, Shopify, and BigCommerce. Alternatively, if you prefer to download your shopping cart and integrate it into your website so with the likes of Magento, Squirrel Cart, or the ever-popular WooCommerce.

Additional features include:

  • Virtual Terminal with easy login for entering customer credit card information
  • Built-in acceptance of Visa, Mastercard, and Discover cards
  • 2-day bank settlements meaning you get paid quickly
  • Credit Card Vault for safekeeping of customers’ financial information
  • Directly integrate payment gateways into your website, shopping cart, billing system, or application
  • Integrate the third-party payment gateway Authorize.net
  • No PCI compliance fees

PRICE: $25/month

3. PayJunction

PayJunction is the perfect payment processor for mid- to large-scale businesses. For example, it offers things like smart payment processing, electronic signature capturing, and multi-user, multi-location reporting.  In addition, it allows you to send digital receipts to customers, reduce the chances of chargebacks, and turn any web browser into a virtual terminal for finalizing purchases, processing checks, and recharging accounts.

Additional features include:

  • Comprehensive reporting for accountability and business growth
  • Connect with third-party applications like Magento and Shopify, and WooCommerce
  • PCI and HIPAA compliant
  • Next day deposits
  • Easily search all transactions
  • Qualified businesses receive one free Smart Terminal for in-person purchase
  • Price match guarantee

PRICE: FREE

4. 2CheckOut

2Checkout enables merchants like you to accept secure, worldwide mobile and online payments. For example, it meets the highest PCI compliance and implements strict fraud rules so you can rest assured your data and the financial information of your customers is safe. Additionally, you can integrate this payment processor directly onto your website in minutes and start selling to customers right away.

Additional features include:

  • Responsive by design and mobile-friendly
  • 8 payment methods and 87 currencies
  • Enable recurring billing
  • Integrate with dozens of popular open-source shopping carts
  • Accept PayPal, major credit cards, and even debit card transactions
  • Receive funds via EFT, wire transfer, or Payoneer in the currency of your choice
  • 87 currency options

PRICE: FREE

Notable Mentions

There are plenty of popular payment processors available to website owners offering lots of features, competitive pricing, and ease of use.

Here are some notable mentions that may be better suited for your individual needs:

Final Thoughts

If you are looking to open an online shop, it is important you consider how you will accept payments on your website. And, while many eCommerce platforms integrate payment gateways into their software for use by website owners, the truth is, sometimes you need something with more features and more handling power.

Altogether, if you are a medium to large size online retailer or expect to grow that big, you may want to consider utilizing the power of a payment processor. And with the right one, you may not even need to invest in a separate payment gateway to accept payments.


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

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

The post How to accept payments on your website appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Which eCommerce Platform Best Suits Your Needs?
  2. How to Accept Payments and Maximize Revenue on Your Website
Categories: Domains

HarveyWeinstein.com domain name sold for $695

Domain Name Wire - Wed, 10/11/2017 - 23:11

Hugedomains had a “buy now” price on the domain name.

Someone just bought the domain name HarveyWeinstein.com

One of the top news stories over the past few days has been about film producer Harvey Weinstein. Weinstein, known for producing films such as Pulp Fiction, Good Will Hunting and Scream, has faced a number of allegations of sexual harassment and sexual assault.

During all of the uproar, someone noticed that HugeDomains.com had HarveyWeinstein.com for sale for a buy now price of $695. They scooped it up. (DomainTools has the asking price archived. Sometimes these numbers aren’t passed through correctly, but a couple archived screenshots of the site have a price near $695.)

The domain name now points to a coming soon page that says the site is undergoing maintenance and will be online shortly. It also includes the email address info@harveyweinstein.com.

Will someone develop the site to track the allegations against Weinstein? The potential of that is one more reason celebrities should lock up their .com domain name.


© 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 HarveyWeinstein.com domain name sold for $695 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Hurricane Irma drove spike in domain registrations last month

Domain Name Wire - Wed, 10/11/2017 - 17:38

Disasters drive domain name registrations.

Hurricane Irma as seen from space. Photo courtesy NASA.

The word Irma was suddenly popular in .com domain name registrations last month. When Hurricane Irma struck Florida, people dashed to their computers to register domain names related to the storm.

That made Irma the #1 trending keyword in .com registrations last month, meaning it saw the biggest percentage spike in registrations over the prior month.

Disaster also made the list. The past couple months have certainly had their fair share of natural disasters.

Here’s the complete list of the top ten trending keywords in .com domain names last month:

1. Irma
2. Pic
3. Lean
4. Jerseys
5. Prices
6. Parks
7. Disaster
8. Aspen
9. Porter
10. Drain

Any guesses what will be trending in October?


© 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 Hurricane Irma drove spike in domain registrations last month appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Some .AI domain name functions limited due to Hurricane Irma
Categories: Domains

.Co co-founder predicts healthy results for .Health domain name

Domain Name Wire - Wed, 10/11/2017 - 16:20

Jose Rasco is applying his experience with .co to .health.

Jose Rasco, who helped drive .Co’s success, is leading .Health

There was a lot of euphoria a few years ago when the rights to new top level domains were being auctioned. Companies paid millions of dollars (and in many cases tens of millions) to acquire individual strings. One thing that I noticed during the auctions was one of the companies that consistently lost the auctions.

Between Nu Dot Co, LLC and STRAAT Health, LLC, Jose Rasco and Juan Diego Calle applied for 14 top level domain names. Yet they consistently lost bidding wars for the domains. They won only two, and one of them is for a domain it plans to sign over to Verisign. That means that, out of 14 domains, they will only run one: .Health.

Rasco and Calle have a lot of experience running a top level domain name. They were co-founders of the .co domain name relaunch in 2010 and successfully grew the domain before selling it to Neustar for over $100 million. This experience helped guide them through the auction process.

“Having run .co, we have a good idea what top level domains are worth,” Rasco explained to Domain Name Wire. “We weren’t going to pay more than a domain was worth.”

In other words, Rasco believes many of the domains they were competing for sold for more than their value. .Health was an exception.

“I’m very confident we’ll get a return on our investment,” he said.

Rasco and Calle own the company that will operate .health and Rasco is running it as CEO.

Rasco is excited about the challenge of growing .health. He believes the experience running .co will help.

“There are some great similarities in that Health as an industry is growing in the same way that Startups were in 2010 when we started .co,” he explained. “Just like with .co, there are many startups and SMBs that are innovating in the industry who make great early adopters and great partners – and with a category like health, they are easier to identify.”

Still, there are some obvious differences between running a generic extension like .co and a specific one like .health.

“The biggest difference is that Health is also engrained in many long-standing, established brands in healthcare delivery, hospital systems, payers and big pharmaceutical companies,” he said. “These are big organizations that take a very long time to navigate and the sales cycles are just so much longer. But the positive is that if you do break through, their reach is very expansive.”

.Health also faces competition from other new top level domain names including .fit, .healthcare, and .hospital. Rasco believes that health is a broader term and more aspirational. He believes that fitness, wellness, nutrition and healthcare are subcategories of health.

The .health domain name is currently in an Industry Access period. Companies with an affiliation to health can get a token and register domain names until November 30. The domain will open for general availability on December 5. Expect to pay roughly $75 retail at that point. Anyone can register .health domains starting December 5 as long as they don’t use the domains in an abusive manner (such as running a fake pharmacy).

Early results are positive. While sunrise was lackluster, the Industry Access period is going strong. There are about 2,250 .health domain names registered so far.

Many groups are already using .health:

  • Rx.health is a company born out of Mount Sinai’s innovation center that is creating a platform for the future of digital medicine.
  • Flo.health is a women’s health consumer app for tracking ovulation. 100,000 women get pregnant each month utilizing Flo.
  • Immersive.health is a blog that teaches you about uses of VR technology in improving patient care and health interventions.
  • ACPM.health is used by the American College of Perioperative Medicine, which is a community of healthcare providers, patients, industry and insurers that aims to break the current barriers in the provision of surgical care.

Many new top level domain owners were overly optimistic about how well their domains would do. And the domain environment in 2017 is very different than when .co launched in 2010. But given his track record, I’d bet on Rasco and .health.


© 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 .Co co-founder predicts healthy results for .Health domain name appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. .VIP hits 200k registrations, $3.2 million within 5 days
  2. .Boston domain names enter general availability today
  3. More details on .Blog and Automattic
Categories: Domains

End user domain name sales up to $60,000

Domain Name Wire - Wed, 10/11/2017 - 13:58

Investor conference organizer pays $60,000 for domain name, cryptocurrency company pays $30,000.

The organizers of the Wealth365 conference paid $60,000 for Wealth365.com

Domain name marketplace Sedo had some solid sales last week, including a public sale of $30,000 and another for twice that amount.

24 Hour Fitness, a major chain of fitness centers, bought a domain name, and an office space locator paid five figures for a .co domain.

Here’s the list of end user domain name sales from the past week:

(You can view previous lists like this here.)

Wealth365.com $60,000 – The buyer is organizing the WEALTH365™ SUMMIT investor conference in January. The company bought Wealth365 in many extensions, but still determined it was worth $60,000 to get the .com.

GigaWatt.com $30,000 – Cryptocurrency mining service Giga Watt forwards this domain to its existing domain, Giga-Watt.com

24store.com $13,400 – Fitness center chain 24 Hour Fitness USA, Inc.

Truss.co $12,500 – Truss Holdings, Inc. is an office space locating service.

JapaneseBeauty.com $10,000 – JWalk, an advertising agency, likely bought this for a campaign or client.

ShareLotto.com $5,000 – A coming soon page says it’s coming in 2018.

SeeThree.com $4,025 – See Three Consulting, a motorsports racing consultancy, bought the domain and forwards it to SeeThreeConsulting.com.

Agris.de €4,000 – AGRIS GmbH in Austria.

AirSys.com $3,900 – AirSys is a two-way radio company that uses the domain AirSys.co.uk.

IBRA.com $2,000 – Zubisoft GmbH must have rebranded as IBRA. It offers eye surgery software.

GMA.me $3,000 – a CSC client bought this domain name.

UFOParasail.com $2,000 – UFO Parasail is a parasailing company in Hawaii.


© 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 End user domain name sales up to $60,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. 15 end user domain name sales
  3. The latest end user domain name sales
Categories: Domains

10 Notable NameJet Sales from September: GigaFactory.com, Everex.com and more

Domain Name Wire - Tue, 10/10/2017 - 18:32

GigaFactory.com and Everex.com among the more notable sales on NameJet last month.

How long does it take to recover from a shill bidding scandal? About one month.

NameJet reported 94 sales in September of $2,000 or greater, totaling $744,000. This is a nice rebound from August when sales totaled only $333,000.

Here are ten sales that jumped out at me:

365.tv $60,000 – This ranks as the 8th highest .tv sale ever in NameBio’s database.

Everex.com $50,205 – This explains the high price.

DigitalPhotography.com $17,100 – At what point is digital photography just photography?

Dotcoms.com $8,108 – Now here’s a domain name that readers can appreciate it. What a brand for selling domains (or for Verisign).

FootballFan.com $4,800 – You know who is not a football fan these days? One famous domain investor’s twitter feed is all about hating the NFL lately.

GigaFactory.com $4,300 – Andrew Rosener’s MediaOptions bought the domain. He already has a relationship with Elon Musk with the X.com deal, so I imagine he’s pitching this for Tesla.

Travesty.com $3,957 – Even names with negative connotations can sell for big bucks sometimes.

PCIcompliance.com $3,875 – A big name for the credit card industry.

Consultations.com $3,356 – Rather generic but it could be good for a dial-an-expert service.

Demolished.com $3,125 – First thing that comes to mind is a home demolition company.


© 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 10 Notable NameJet Sales from September: GigaFactory.com, Everex.com and more appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Shills, Insiders, & Front Runners – 5 Bidding Scandals
  2. Another record-buster at NameJet
  3. Chinese buyer of TS.com also buys GH.com
Categories: Domains

GoDaddy gets patent for “Suggesting domain names based on recognized user patterns”

Domain Name Wire - Tue, 10/10/2017 - 15:32

GoDaddy adds to patent arsenal with another domain search patent.

GoDaddy gets another patent.

The U.S. Patent and Trademark Office granted patent number 9,787,634 to GoDaddy today for Suggesting domain names based on recognized user patterns.

The patent describes ways to make domain name suggestions better. According to the patent:

Many current-available solutions to finding the ideal available domain name rely on static language dictionaries including information such as part-of-speech and synonyms. Issues associated with this static approach include, for example, a limited number of synonyms, static vocabulary dictionaries which do not rank the popularity of synonyms when considering name ranking, and no consideration of domain name transformation types.

The current invention addresses these types of issues by providing domain name generation, filtering of low-quality domain names, and domain name ranking. This invention identifies interchangeable terms together with their popularity based on frequency of use as analyzed from data within domain names search logs and domain name zone files 320. Language models for name filtering and machine-learned ranking further refines the quality of domain name search suggestions while avoiding false positives or spurious suggestions.

The user’s search history can be considered to generate the best available domains:

As a non-limiting example of a user log entry 315 stored in data storage 230, a user may access a registrar web page to determine domain name availability. The user may search the domain name loanstar.com, which the domain name search software may determine is not available. The user may then search “loan-star.com,” adding a dash to the original query. If this domain name is not available, the user may attempt the domain name “theloan.com,” dropping the word star and pre pending the article “the.” If this is not available, the user may attempt additional words, numbers or stemming (dropping “the,” and appending “guru,” or “247” resulting in “loanguru.com” or “loan247.com,” or creating a stem to “loaner.com” respectively), or may replace existing words (e.g., “loanninja.com” as opposed to “loanguru.com”).

After data records for a search session 315 are created, dictionary aggregation software 330 may reconstruct each original search session 315, as well as the order of each action taken by the user within the session(s), and may create an ontology for terms used in the search, thereby generating dictionary 325 data and providing learning data for machine learning.

The patent lists Wei-cheng Lai, Yang Zhao, Moninder Jheeta, and Tapan Kamdar as inventors. You can view the full patent here (pdf).


© 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 for “Suggesting domain names based on recognized user patterns” appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. GoDaddy Looks to Social Networking for Growth
  2. GoDaddy Scores Another Whois Privacy Patent
  3. GoDaddy wants to patent way of onboarding new TLDs
Categories: Domains

.Boston domain names enter general availability today

Domain Name Wire - Tue, 10/10/2017 - 15:10

Standard registration fees are near .com prices.

.Boston domain names are available today.

The days of many notable top level domain names entering general availability are long gone, but there’s a noteworthy launch today: .Boston.

Domain names ending in .boston will be available today starting at 16:00 UTC, which is noon EDT.

Standard prices are fairly low; GoDaddy is charging $11.99 for one-year registrations. There are premium domain names but they have one-time premiums rather than annual premiums.

MMX (Minds + Machines, London AIM:MMX) acquired rights to the .boston domain name from The Boston Globe. It will be interesting to see if Boston Globe pushes the domain and what this will do for awareness.

MMX also runs .miami and .london. .Miami has 11,000 names in the zone and .london has 75,000.


© 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 .Boston domain names enter general availability today appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Boston Globe sells .Boston domain name to Minds + Machines
  2. .VIP hits 200k registrations, $3.2 million within 5 days
  3. More details on .Blog and Automattic
Categories: Domains

5 Reasons Website Speed is Crucial for Your Success

Domain Name Wire - Mon, 10/09/2017 - 19:32

A fast-loading website is critical to your success.

How fast your website pages load when a site visitor clicks on your site is crucial to your success.

In fact, Kissmetrics offers some startling statistics all website owners should heed:

  • 47% of online consumers expect websites to load in 2 seconds or less
  • A 1 second page load delay can reduce conversions by 7%
  • 40% of people abandon a website that takes more than 3 seconds to load

So what does all of this mean?

If you have a slow WordPress website, you risk losing money, conversions, and site visitors. Click To Tweet

However, it’s not that simple. There are more in-depth reasons why website speed is crucial to your overall success. Let’s look at some of the consequences you will face should you not pay close attention to your website’s overall speed and performance.

1. You Will Lose Site Visitors

There is nothing more frustrating than visiting a website that takes too long to load. And, chances are, if a site visitor comes to your website, and realizes it’s too slow for their liking, they will never return. This means your regular visitors may become distant memories, despite how much they enjoy what you have to offer.

2. Your Bounce Rate Will Skyrocket

If a site visitor clicks on your website and is dissatisfied with how fast the page is loading, they will leave, or bounce, immediately. The percentage of people that “bounce” back to the referring website or search results is what is called your website’s bounce rate.

Most websites have a bounce rate that falls between 25% and 70%. The lower the rate, the more successful your website is. That’s because a low bounce rate means people are entering your website, liking what they see, and engaging with your content.

3. Reduced Conversions

One of the reasons online stores and popular blogging sites do so well is because they encourage site visitors to subscribe. And, it works.

If your website is slow to load, people will not be apt to subscribe. This means no weekly newsletter, no firsthand look at your newest e-book, and no special coupons for your site visitors. For online businesses that thrive off email subscribers, this is bad news.

4. Poor Search Rankings

Every time someone conducts a search using a major search engine such as Google, the internet serves up web pages related to the search inquiry. And, although it seems obvious, you should know that being as close to page one as possible is the key to getting people onto your website.

Since Google ranks websites in part based on overall speed, it makes sense that the slower your website is, the worse the search ranking will be for your website’s pages. This will largely affect how much organic traffic enters your website based solely on search results.

5. A Loss in Revenue

Many website owners supplement the income they make off their website using strategically placed advertisements. And, what a shame to go to all that trouble to find the sweet spot on your website, where site visitors are most likely to click on a banner ad, if your website loads too slow for them to even notice ads are there.

In addition, if you own an eCommerce shop, and again, your site loads too slowly for site visitors to want to stick around, you miss sales opportunities. This results in major revenue loss.

In the end, the speed of your WordPress website is an overwhelming factor in how successful you will be. And, by understanding the consequences you face by not addressing a slow website, you are better preparing yourself to move forward with a website that site visitors enjoy coming to on a consistent basis.


© 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 Reasons Website Speed is Crucial for Your Success appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Gannett backs Thanksgiving.com publisher

Domain Name Wire - Mon, 10/09/2017 - 19:31

USA Today owner invests in company that is developing Thanksgiving.com domain name.

Publisher Gannett Co., Inc, which owns USA Today, has invested in Grateful Ventures. The investment will be used in part to accelerate development of Thanksgiving.com, which it hopes to make a destination for holiday cooking.

Grateful Ventures describes itself as “an online media and publishing coalition, focusing on building content and monetization strategies for high value domains”. It uses the domain Grateful.ventures.

Thanksgiving.com was owned by Digimedia. In 2014 the Whois record switched to privacy.

Digimedia president Jay Chapman tweeted about the investment earlier today:

Gannett & GV plan to make https://t.co/YjzwF6sh76 "top destination for all holiday-related food & cooking content" https://t.co/pFgzlmlHsv

— Jay Chapman (@Jay_Chapman) October 9, 2017

I have reached out to Jay to see if Digimedia is still involved with the domain name.


© 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 Gannett backs Thanksgiving.com publisher appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Review: “The Domain Game” Book Released
Categories: Domains

ICANN hopes Puerto Rico will recover in time for March meeting

Domain Name Wire - Mon, 10/09/2017 - 16:44

First Zika, then Hurricane Maria.

Hurricane Maria might necessitate moving an ICANN meeting away from Puerto Rico for the second time, but ICANN hopes that won’t be the case.

The non-profit released a statement this weekend saying that it still hopes to hold ICANN61 in San Juan, Puerto Rico March 10-15, 2018:

“Our sincere hope is that by that time, recovery on the island will have advanced to the point where our meeting can proceed as scheduled. It is one way that we can all show meaningful economic support for this storm-battered U.S. territory.”

If it does have to move the meeting, it will be the second time the meeting has shifted. The meeting was supposed to be held in Puerto Rico in the fall of 2016 but was moved due to concerns about the Zika virus.


© 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 ICANN hopes Puerto Rico will recover in time for March meeting appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Zuccarini Files Another Lawsuit, This Time Adding ICANN to the List
  2. “Internet Villain” Stephen Conroy wants role on ICANN ATRT
  3. Who goes to ICANN meetings? Here’s an answer
Categories: Domains

Understand Blockchain with Ken Hansen – DNW Podcast #156

Domain Name Wire - Mon, 10/09/2017 - 15:30

Ken Hansen explains what blockchain is and how it can be used.

You might know Ken Hansen from the domain name industry, but he’s also very involved with spreading the gospel of blockchain. On today’s show, Ken explains blockchain in language that you can understand. He also discusses how blockchain technology might be applied to domain names. Also: lots of donuts, Escrow.com price drop, GoDaddy fixes the glitch and MicroStrategy faces another domain challenge.

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.)

Here are the blockchain resources Ken mentioned in the podcast:


© 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 Understand Blockchain with Ken Hansen – DNW Podcast #156 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Get ready to MERGE! – DNW Podcast #150
  2. Blockchain and Hurricane Harvey were popular in domains last month
  3. Cryptocurrency domains were hot in May
Categories: Domains

How to Accept Payments and Maximize Revenue on Your Website

Domain Name Wire - Fri, 10/06/2017 - 17:08

These days, it seems everyone has an online shop that sells products and services.

And rightfully so.

With 71% of people believing they can get a better deal online, it’s no wonder businesses of all sizes and kinds are throwing up eCommerce stores to supplement their income.

To add to that, it is estimated that by 2019, there will be nearly 224 million digital shoppers in the United States alone.

Online shopping is a multi-billion dollar enterprise that spans the globe.  People all over choose to buy online because it is simple, easy to price compare, and is relatively low pressure. Plus, they can do it from the comfort of their own home if they choose to.

And in response, as I mentioned above, website owners worldwide are jumping in and building their very own eCommerce shop so they too can reap the benefits online shopping brings to business owners.

But what if you are just starting out in the eCommerce biz? How are you supposed to know what you need on your website in order to securely collect payments from your customers?

Find out what essentials you need on your eCommerce website in order to accept payments.Click To Tweet

If this is something you are struggling with, keep reading. Today I have a list of what it takes for you to accept payments on your website so that you too can generate revenue from the slew of online shoppers that prefer to buy online.

Must-Have Features so You Can Accept Payments on Your Website 1. eCommerce Platform

This piece of software is an essential building block to being able to accept payments on your website. For instance, an eCommerce platform allows you to manage your online shop, sales, and associated operations. In addition, it often comes with all the necessary tools to begin accepting payments directly from customers on your website.

Popular eCommerce platforms include:

Depending on the size of your shop, and other factors such as support, cost, mobile-friendliness, security, and scalability, you will want to make sure you do your due diligence in researching which eCommerce platform best suits your needs.

*Keep in mind that many of the essential “must-haves” I am about to share with you come included with some of the top eCommerce platforms on the market today.

2. PCI Compliance

The PCI Security Standards Council is responsible for the ongoing development, enhancement, storage, dissemination, and implementation of security standards as it applies to your customers’ data. In short, they make sure you are protecting your customer’s credit card data during checkout.

No matter how big or small your eCommerce shop is, it’s your responsibility to make sure you are PCI compliant. The level of compliance you need is determined by how many credit card transactions are processed through your shop annually. The more transactions you process, the higher your PCI compliance must be.

3. Payment Processor

For smaller eCommerce shops, integrating a simple payment gateway onto your website such as PayPal, Stripe, Google Wallet, or Authorize.net may suffice for finalizing transactions.

However, for larger retail sites that process thousands in revenue daily, it is better to install a payment processor onto your website. This will ensure top notch security, prevent chargebacks and revenue loss, and make sure your website can handle the traffic that flows through your online shop on a consistent basis.

Though we have discussed popular payment processors in the past, here is a look at some of the best options you have to choose from:

4. SSL Certificate

The purpose of an SSL certificate is to protect your customers’ personal and financial information. In short, SSL certificates guarantee that data passed between a web server and a browser remain secure and private.

If you do not have an SSL certificate on your eCommerce website, all data that is processed through your website, including sensitive information such as credit card numbers, are vulnerable to hackers looking to steal and use that information.

You can tell when a website is SSL certified by looking at their URL. If you see an “https://”, the site is secure. On the other hand, if you see “http://” it is not secure.

Getting a free SLL certificate is not difficult to do, especially if your eCommerce platform or website hosting provider provides one. If not, however, you can always use the popular Let’s Encrypt SLL certificates.

5. Secure Login Options

Have you ever tried to purchase something online and realized that the only way to finalize your purchase was to register an account with said shop?

Pretty annoying right?

Cater to customers that hate the thought of registering for accounts in order to make purchase by having multiple login options available. This means having an account section for those that are interested or already have an account with you. Additionally, have a “Checkout as Guest” option.

In addition, you will want to make sure that any login requirements you have are secure. This includes answering security questions in the case of a forgotten password or locked accounts after a specific number of failed login attempts.

6. Smooth Checkout Process

In order for you to collect payments from your customers, you must provide easy ways for them to finalize their purchases. This is done in a number of ways:

Checkout Buttons

Make it very clear to customers where the checkout process begins by using an extremely visible checkout button such as the one found on Target.com.

After all, the less time a customer has to spend figuring out how to get to their cart and make their payment, the less likely they are to abandon their cart. And, with abandonment rates reaching nearly 70%, it’s important to prevent this as much as possible.

Visible Checkout Process

Customers get anxious the longer the checkout process is. Especially if it spans across multiple pages. This can lead to cart abandonment, which does no good for your bottom line or customer satisfaction.

Amazon does a good job of directing customers through the checkout process step-by-step. You always know which part of the process you are at, can easily navigate back if necessary, and in the end you can always make changes to your purchase.

Refund and Return Policy

Though not exactly required to accept payments on your website, a clearly defined refund and return policy will help satisfy your customers’ need to know what steps to take in the case something goes wrong with their purchase.

Customers place a lot of trust in your company when they buy something online from you because they cannot physically check out the product they are purchasing. In addition, they want to know that if for whatever reason they are not satisfied, they can return or exchange the item.

If you make your refund and return policy visibly on your website, you solidify that trust and put customers at ease to continue finalizing their transaction. This of course generates you more revenue and provides your shop an opportunity to grow.

Final Thoughts

In the end, there is a lot that goes into accepting payments from your customers online. From payment processors to site security, checkout processes to refund policies, it is important you touch on all of the essentials.

In doing so, you will instill customers with a sense of confidence in your brand. Plus, you will breed loyalty amongst customers and give your online shop the ability to grow and succeed.

 


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

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

The post How to Accept Payments and Maximize Revenue on Your Website appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Which eCommerce Platform Best Suits Your Needs?
  2. How to Turn Your Existing Domain Into an eCommerce Shop Using WooCommerce
Categories: Domains

The Gleissner Files reveals stunning level of activity

Domain Name Wire - Fri, 10/06/2017 - 03:00

Behold: an in-depth look at Michael Gleissner’s trademark applications, companies and domain names.

I’ve written many times about Michael Gleissner’s odd activities around trademarks, domain names and cybersquatting claims.

Now, World Trademark Review has compiled an extensive list of all of his activities.

The publication calls it The Gleissner Files. It contains more than 1,100 registered company names, over 2,500 trademark applications and 5,300 domain names (and how they are being used).

It’s a 69-page .pdf document, so searching it won’t be that easy. But it shows the breadth of Gleissner’s bizarre activities. Among the .com trademarks his companies have applied for: Top.com, Host.com, Bob.com, Fiji.com, Salt.com, Connect.com, Black.com and many more.

What is Gleissner’s end game? We know he has filed UDRPs to try to get generic domains and has threatened trademark applicants about getting their marks canceled. But I’m still scratching my head about the overall strategy.


© 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 Gleissner Files reveals stunning level of activity appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Chinese resellers cut off from .Au domain names

Domain Name Wire - Thu, 10/05/2017 - 14:08

Registry sites fraud in a decision to halt .au registrations from Chinese resellers.

No more .au for Chinese resellers.

.au Domain Administration Ltd (auDA), the registry for Australia’s .au domain names, has instructed Tucows to cut off Chinese resellers from .au domain names.

Tucows operates both the OpenSRS and Enom reseller platforms, making it by far the dominant domain reseller company.

According to the company:

auDA cited an increased number of complaints they have received in recent months regarding domains that were fraudulently registered using unauthorized Australian business information. Those registrations, as auDA determined, appear to have originated from resellers based in China.

You must be a company or organization registered in Australia in order to register a .au domain name. Registrants are required to have an Australian Business Number.

The move came in August but was included in a newsletter Enom sent to all resellers today.


© 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 Chinese resellers cut off from .Au domain names appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Tucows expects $20 million EBITDA/year from “opportunistic” eNom acquisition
  2. January data show why Rightside sold eNom: Namecheap
  3. Who won and lost in .Com?
Categories: Domains

Donuts’ numbers show promise for new TLD business model

Domain Name Wire - Thu, 10/05/2017 - 13:47

Company reports solid growth and metrics. Keep an eye on it as discounted domains come up for renewal.

These donuts keep stacking up.

Donuts has summarized data about its progress in 2017 and there are some interesting tidbits:

  • Year-over-year growth in new registration volume (excluding new TLD launches) has increased by 34%
  • One million new registrations so far in 2017, bringing total domains under management to 3 million
  • Average renewal rate for a Donuts TLD is 71% (weighted by volume)

These numbers are indeed encouraging for Donuts’ business model and perhaps some of the other new TLD registries.

Donuts has done some fairly large promotions this year with discount pricing for initial registrations. It had every TLD in its stable on sale for a while and most domains were under $10 for the first year. 60 were about $5 or less retail. The low prices have certainly juiced initial registrations.

Domains that cost a lot more to renew than the initial registration fee usually have lower renewal rates. However, Donuts’ discounting wasn’t the same as some registries that did extreme discounting with a goal of attracting domain investors in China.

The 71% renewal rate is in line with what the company told me it was getting a little over a year ago.

Rightside (now owned by Donuts) reported 59% overall renewal rates earlier this year with 50% on first-year renewals. Rightside has traditionally offered more first-year discounts, so I expect Donuts’ renewal rates to slip as discounted domains come up for renewal.

It will be interesting to watch over the next few quarters.


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

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

The post Donuts’ numbers show promise for new TLD business model appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Digging in on Donuts’ Sunrise: Amazon tops the list, gaming, and top registrars
  2. This week in new TLDs: $150k/domain? Plus .black, .hiv, and .creditcard
  3. This week’s new TLDs: A big week for Donuts, Radix
Categories: Domains

Escrow.com drops minimum fee to $10

Domain Name Wire - Thu, 10/05/2017 - 00:00

Small transactions are now cheaper at Escrow.com.

Escrow.com is dropping its minimum fee on transactions to $10.

This will lower the price customers pay for the standard service for any transaction under $775. It will lower the price for transactions using a credit card under $400.

Escrow.com GM told Domain Name Wire that this move was made to compete with PayPal. “This will give people escrow protection without the need to pay $25 on a $300 domain,” he said. “$10 makes it a no-brainer.”

Payoneer, a competing escrow service, also has a $10 minimum.


© 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 Escrow.com drops minimum fee to $10 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Want to use Escrow.com? Prepare to be verified.
  2. Escrow.com tops $1.5 billion in transactions
  3. Domain name escrow price and services guide
Categories: Domains

Who won and lost in .Com?

Domain Name Wire - Wed, 10/04/2017 - 17:15

A look at how registrars fared in the most recent public report.

ICANN published the latest official .com transactions report from Verisign, which includes data by registrar for June 2017. There was no change to the order of the top registrars for new registrations but there were some changes in domain transfers, including a registrar from Czech Republic making an appearance.

Here are the top registrars in terms of new .com registrations for June. There were no changes in the top five order from the prior month.

1. GoDaddy* 879,470
2. Tucows** 186,570
3. HiChina 169,012
4. PublicDomainRegistry 135,027
5. Namecheap 111,907

When it comes to net inbound transfers for registrars open to the public (transfer gains minus transfer losses), Subreg.cz popped up on the list. This is probably a one-time blip.

1. HiChina +19,421
2. MAFF Inc (XZ.com) +8,674
3. subreg.cz +8,247
4. GoDaddy +6,540
5. NameSilo +6,521

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

1. Web.com*** -7,381
2. HebeiDomains.com -7,286
3. Domain.com -6,836
4. Fabulous -4,834
5. Tucows -4,480

HebeiDomains appears to be a reseller platform.

*Includes GoDaddy and Wild West Domains **Includes Tucows and ENom *** Includes Network Solutions and Register.com


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

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

The post Who won and lost in .Com? appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Domain search progressing, but still not ready for new top level domain names
  2. Chinese registrars lose of lot of .com, but HiChina picks up domains from others
  3. The Latest .Com Winners & Losers
Categories: Domains

13 More End User Domain Sales

Domain Name Wire - Wed, 10/04/2017 - 15:55

Publisher of Billboard Magazine is among end user domain buyers.

Sedo had a handful of nice sales last week, including Buda.com for €25,000 and Ploy.com for $18,000. I hope Buda.com was purchased for the Austin suburb called Buda because that would be a great comp for my Lakeway.com domain (a wealthy city outside Austin). It’s still in escrow. Ploy.com is under Whois privacy and does not resolve, so I don’t know who the buyer is.

The top end-user sale I can identify for sure is ProKnow.com.

Also, who bought BonnieAndClyde.com for $2,077? It’s still in escrow and could be a domain investor or end user.

As for domains we know are end-user purchases, here’s the list:

(You can view previous lists like this here.)

ProKnow.com $14,000 – The registrant is the finance director for .Decimal. I’m not sure if she registered it for .Decimal or something else.

MisterTrip.com €12,500 – Tervado GmbH is a data protection company that uses the domain name mistertrip.de.

Progate.com £12,000 – Wow. The Japanese company Progate has been using the domain prog-8.com. Yikes.

Bridge.tv €9,999 – The Bridge Church in Tennessee.

GetAQuote.co.uk £4,500 – Loanable, a new online lending platform in the UK.

BillboardVietnam.com $4,500 – Prometheus Global Media publishes the music publication Billboard.

KPF.org $4,488 – Kohn Pedersen Fox Associates PC bought the .org to match its domain KPF.com.

TJTaylor.com €3,200 – TJ Taylor teaches languages and uses the domain name TJTyalor.net.

AuctionTech.com $3,000 – This German company just got funding.

LivingEarth.co.uk $2,500 – UK Healthy food company Living Earth.

Complete.co.uk $2,500 – Complete Office Solutions in the UK.

BRTX.com $2,200 – BioRestorative Therapies in New York. The company uses BRT for short, but I’m not sure where the X comes in.

CXOsummit.com $2,000 – CXOsync LLC holds a number of events for CIOs.


© 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 13 More End User Domain Sales appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Bitcoin company among end user buyers at Sedo last week
  2. .Club domain tops last week’s end user domain name sales
  3. Big names buy domains: Under Armour, Mary Kay, SAP and more
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.