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.

Domaining Europe to return to Valencia in 2018

Domain Name Wire - Fri, 10/27/2017 - 13:26

After a stop in Berlin, European domain conference moves back to Valencia, Spain.

A popular European domain name conference has picked its venue for 2018.

Domaining Europe will return to Valencia, Spain next year for its tenth anniversary. The event will be held at the Hotel Sorolla Palace June 7 to 9, 2018.

Host Dietmar Stefitz looked for venues elsewhere in Europe but determined that Valencia offered the best combination of location and pricing. Rooms at the hotel will be only €80, making the event affordable for everyone in the domain name community.

More information and details about the hotel are online at DomainingEurope.com. Hotel reservations are now available but event registration hasn’t opened yet.


© 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 Domaining Europe to return to Valencia in 2018 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Domaining Europe to take place in Berlin in May
Categories: Domains

.Com/.Net base grew by 1.47 million in Q3

Domain Name Wire - Thu, 10/26/2017 - 20:41

Growth in base outpaces Verisign’s forecast.

Verisign (NASDAQ: VRSN), the domain name registry for .com and .net domain names, reported results for Q3 after the bell today.

The total base of registered .com and .net domain names increased 1.47 million over the quarter. Verisign had forecast growth of 0.8 million to 1.3 million registrations, so it continued its trend of coming in above its forecast. The company forecasts an increase of 0.4 million to 0.9 million in Q4 2017. If I were an analyst, I’d probably peg it at about 1.0 million.

There were 8.9 million new domain name registrations for .com and .net in the quarter, compared to 8.3 million for the same quarter in 2016 and 9.2 million last quarter.

Verisign’s Q3 revenue was $292 million, up 1.7 percent from the same quarter in 2016.


© 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 .Com/.Net base grew by 1.47 million in Q3 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. U.S. Antitrust Division investigating Verisign running .Web
  2. Domain stocks doing very well this year
  3. Verisign credits Super Bowl for strong quarter
Categories: Domains

13 recent end user domain name sales

Domain Name Wire - Thu, 10/26/2017 - 17:35

From 247ai.com to Yoss.net, here are domain names that end users bought this week.

When a new company or brand launches, one of the key but often last-minute checklist items is to obtain the relevant domain names. There are two acquisitions on this week’s list that are examples of this.

A company called 247 rebranded as 247.ai, but also acquired 247ai.com as it launched. Yoss, a new company from Adecco, uses Yoss.fr but acquired Yoss.net right before launching.

Let’s take a look at some of the end user domain name sales that took place on Sedo over the past week.

(You can view previous lists like this here.)

Nost.com £10,000 – The domain was under whois privacy and now shows native advertising company AdNow LLP as the owner. I think this is the buyer, not the seller. I don’t see anything on the company’s website that uses the term nost.

Symbiosis.cn €10,000 and Symbiosis.ro $4,000 – French pharmaceuticals company Biocodex bought two more domain names.

Crypto360.com $9,895 – A guy named Vick Strizheus is getting ready to launch a site.

Clipband.com $9,138 – How’s this for a business: Bedford industries started by making twist ties and now makes other packaging materials. I assume the clipband is a type of package fastener.

Helectron.com $5,500 – Helectron Oy Ab in Helsinki, Finland uses the country code domain Helectron.fi.

247ai.com $5,000 – A company called [24]7 rebranded to [24]7.ai, but smartly also picked up 247ai.com.

PassportOne.com $5,000 – Family Services Toronto has a service called Passport. The site says “Passport is a program that helps adults with a developmental disability to participate in their communities, and helps caregivers take a break from their caregiving responsibilities.”

Yoss.net €3,900- Staffing company Adecco partnered with Microsoft to create Yoss, which was announced today. Yoss is a freelancer site and Yoss.fr appears to be the main domain. The company does not own Yoss.com; a guy whose last name is Yoss has that one.

Quintar.com €3,900 – Quintar seems to be an Asian cryptocurrency trading app.

StudyCollege.com $3,500 – Hybrid News ltd has a number of websites including one about studying abroad.

ChicagoCollective.com $3,500 – This domain is for the men’s clothing show Chicago Collective.

Interiology.com $3,000 – Interiology Design Co. is an interior design company.

Localites.com $2,500 – Localite Inc seems to be a new travel 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 13 recent end user domain name sales appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. What domains Hallmark, Swarovski, and Sapient bought last week
  2. A BIG end user domain name sale at Sedo
  3. Sedo’s Q2 market study plus where the top 10 sold domains are now
Categories: Domains

GoDaddy wants to patent “Determining Status of a Domain Name Registration”

Domain Name Wire - Thu, 10/26/2017 - 15:21

Patent application describes way to speed up domain lookups.

Domain name registrar GoDaddy (NYSE:GDDY) has filed a U.S. patent application (pdf) for “Determining Status of a Domain Name Registration”.

Yes, we’re talking about figuring out if a domain name is available to register. In fairness, the title of the patent makes it sound simpler than it is. It’s really about reducing the resources required and latency in the process.

First, a registrar can check the domain against a downloaded zone file from the registry. If it’s not on that list, it can then check it against the registrar’s own zone file. If that still doesn’t find a hit, it can do an EPP request to the domain registry. More checks can be done depending on the result. Of course, if it finds a hit at any stage in this process it can determine that the domain is already registered.

I believe that GoDaddy is using locally-stored data like this for initial domain lookups, especially when it provides a list of suggested names that don’t exactly match the domain name searched. When you click on search results it quickly shows a message “Verifying Availability”. Sometimes a message is returned saying it is no longer available.

Chris Ambler, Charles Beadnall and Moninder Jheeta are listed as inventors.


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

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

The post GoDaddy wants to patent “Determining Status of a Domain Name Registration” appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. GoDaddy Files Patents for “Hosting Connection”
  2. GoDaddy Files Patent App for “Jointly Auctioning Expiring Domain Names”
  3. Go Daddy Wants to Patent Way to Monetize URL Shorteners
Categories: Domains

Truth: you need your own website, not Facebook

Domain Name Wire - Thu, 10/26/2017 - 13:13

Oatmeal comic sums it up.

There are still a lot of small businesses out there that only have a Facebook presence rather than a website they own and control. As any business on Facebook will tell you, though, a Facebook page is at mercy of Facebook and its monetization goals.

Over time, Facebook has pulled pack how many of your “fans” on Facebook actually see what you post as a business. It appears to be going in the wrong direction, too. The company is testing relegating business posts to a separate feed in users’ timelines. This could crush businesses that rely on Facebook for a lot of traffic. The ironic thing is that many of these businesses paid Facebook to help grow their follower base on Facebook. Now they have to pay again to reach them.

Matthew Inman summed it up in a great comic. As if on cue, Facebook even suggested he pay $2,000 to reach more people.

Reaching people on the internet. pic.twitter.com/dneGM14Cyl

— Matthew Inman (@Oatmeal) October 25, 2017


© 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 Truth: you need your own website, not Facebook appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Top Domain Name News Stories of June 2009
  2. DNW’s new TLD roundup: the good, the bad and the funny
  3. Facebook registers domain names for WorkPlace service
Categories: Domains

Another “forgot to renew domain, service went down” story

Domain Name Wire - Wed, 10/25/2017 - 18:29

This time a Dell domain is dropped.

Earlier this week I wrote about how part of IBM’s cloud infrastructure went down when it failed to renew two domain names.

Krebs on Security has another example, this one coming from a provider to technology giant Dell.

A backup provider called Softthinks.com used the domain name DellBackupandRecoveryCloudStorage.com, but it expired and was sold through DropCatch in June. (Yes, that’s a 33 letter domain name. It’s a reminder that it’s not the quality of the name that matters when a domain expires…it’s the importance of what it connects to.)

Brian Krebs notes that the domain name, which PCs could connect to, got flagged for malware after it was parked. It’s unclear how that happened and it also doesn’t mean that malware was actually served on the domain.

This case is unique because Dell stopped using the backup service a year ago. But since computers might still make calls to it, the domain name needs to be renewed until this is no longer possible.


© 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 Another “forgot to renew domain, service went down” story appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

Kevin Ham sells domain names to GoDaddy

Domain Name Wire - Wed, 10/25/2017 - 16:27

GoDaddy continues to gobble up large domain name portfolios.

Just a week after completing a deal to acquire Donuts’ portfolio of about 200,000 domain names, GoDaddy appears to have purchased legendary domain investor Kevin Ham’s domain name portfolio, or at least part of it.

I detected a large number of domain names transferring to GoDaddy today and they all lead back to companies Kevin Ham has been associated with. The domain names were previously under Whois privacy at Uniregistry, and many of them have previously promoted that they are available for purchase through Mark.com, a broker service associated with Ham.

Kevin was profiled in a Business 2.0 story “The Man Who Owns the Internet”. I have reached out to people at Kevin’s company to confirm.

GoDaddy has acquired a handful of large portfolios in recent years. They have effectively bought out some of the largest domain name investors, including Michael Berkens. Their goal is usually to take portfolios that weren’t marketed through syndicated listings at Buy Now prices and increasing their sales velocity by setting reasonable prices in the Afternic distributed system.


© 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 Kevin Ham sells domain names to GoDaddy appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. What domain names Yahoo! and 21 other end users bought
  2. 18 end user domain name sales up to $38,000
  3. Shills, Insiders, & Front Runners – 5 Bidding Scandals
Categories: Domains

Male enhancement doctor goes limp in cybersquatting dispute

Domain Name Wire - Wed, 10/25/2017 - 15:15

Doc wants old domain name without paying the asking price.

A male enhancement doctor has been found to have engaged in reverse domain name hijacking in his attempt to get the domain name PShot.com.

Charles E. Runels, Jr. is known for his enhancement method that he markets under the names Priapus Shot and P-Shot. He started using these names this decade, but he wanted to enlarge his brand by acquiring the domain name PShot.com. PShot.com was registered in 2002. Runels tried to buy the domain name but he didn’t make a large enough offer.

So, as plan B, he filed a cybersquatting complaint under UDRP. Part of his argument was:

On information and belief, Respondent, for an extremely minimal investment, speculated that the Domain Name would become commercially valuable, and registered the Domain Name for the sole purpose of selling, renting, or otherwise transferring the Domain Name for valuable consideration in excess of the out-of-pocket costs directly related to the Domain Name. Once Complainant’s business activities using the trademarks PRIPAUS SHOT and P-SHOT caused the Domain Name to acquire value, for valuable consideration far in excess of Respondent’s out-of-pocket costs directly related to the registration and parking of the Domain Name, Respondent offered to sell the parked pshot.com domain name to Complainant initially for $150,000.00 and then for $35,000 in a subsequent counteroffer.

That argument was obviously not well received by the panel.

Runels also cited an old case as an example of a panel finding that a domain could be registered in bad faith even if it was registered before a trademark existed. But the panel in that case actually decided that bad faith registration was not proven.

Unsurprisingly, the panel found against Runels and also that he was guilty of reverse domain name hijacking.

Runels was represented by Sheryl De Luca of Nixon & Vanderhye P.C. The domain owner was represented by Zak Muscovitch of Muscovitch Law P.C.


© 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 Male enhancement doctor goes limp in cybersquatting dispute appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. An Arbitrator’s View of Reverse Domain Name Hijacking
  2. UNiDAYS guilty of reverse domain name hijacking
  3. Things aren’t looking so good for Grandma Heidi Powell
Categories: Domains

Escrow.com releases beta API for escrow integration

Domain Name Wire - Wed, 10/25/2017 - 12:33

API makes it easy for third-parties to integrate escrow services.

Escrow.com has released a new API in beta.

According to the company, the API will make it easy for websites, marketplaces, classifieds sites, shopping carts, and mobile apps to integrate Escrow.com’s services. The company says it’s as easy as integrating payment methods such as Stripe and PayPal.

Escrow.com already has integrations with many marketplaces, but I believe these were custom integrations. Now there’s a centralized API that any service can use.

Details of the beta API, including documenation, are here.

Escrow.com has long been the dominant escrow service for domain name transactions. It handled over $200 million in payments in the first half of this year. Freelancer.com acquired the company for $7.5 million in 2015.


© 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 releases beta API for escrow integration appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. DNW Interview: Brandon Abbey of Escrow.com
  2. A look at Escrow.com’s revenue growth
  3. Escrow.com wants to keep Trust while improving the service
Categories: Domains

Unique Things You Can Do With WooCommerce Extensions

Domain Name Wire - Tue, 10/24/2017 - 21:21

WooCommerce is one of the most flexible eCommerce platforms on the market today. As an excellent option for building and running a fully functioning online shop, it is no wonder so many retail shop owners are utilizing it.

That said, there is so much more to this eCommerce plugin than just creating an online store that sells products and services to customers. In fact, WooCommerce offers website owners a vast amount of functionality that aims to help you build something truly one-of-a-kind.

See how WooCommerce elevates your eCommerce store and helps you create a standout website.Click To Tweet

Today we are going to look at some of the unique things you can do with WooCommerce extensions through a variety of free and premium extensions.

1. Facebook for WooCommerce

If you have a large customer base on Facebook, this is the WooCommerce plugin for you. Build a bigger audience, sell to your existing followers by displaying relevant ads, and even track your sales and revenue. In addition, set up shop directly on Facebook and start selling to customers right away.

Features include:

  • Conversion tracking
  • Ad optimization
  • Facebook ad delivery to site visitors
  • Mobile-friendly shopping
  • Product and service organization

Price: FREE

2. WooCommerce Simple Auctions

This WooCommerce extension adds an interesting twist to how you sell your best products. Mimicking the likes of eBay, WooCommerce Simple Auctions lets you run multiple auctions for your products. More so, you can include a bid history, a countdown timer, and even enable the “My Auctions” section for customers so they can easily track their bids.

Features include:

  • Normal, reverse, and silent auction functionality
  • Email notifications for things like auction won, payment reminder, and auction relist
  • AJAX live updating for current bids and auction history
  • Bids for virtual or downloadable products available
  • Frontend auction sorting

Price: $21

3. Newsletter Subscription

One of the neat things about WooCommerce is that it aids you in your marketing efforts. One such way that WooCommerce does this is with the Newsletter Subscription extension. Allowing you to easily integrate your MailChimp or CampaignMonitor email service providers into your online shop, you can start building a bigger email list as customers peruse your shop and while they are making purchases on the checkout page,

Features include:

  • Widget ready for sidebar box
  • Dashboard widget for tracking subscriber activity
  • Boost your ability to stay in touch with loyal customers
  • Connect with eCommerce360 to track links and sales
  • MailPoet newsletter management plugin support

Price: $49

4. WooCommerce Subscriptions

Implementing subscriptions onto your eCommerce shop is one of the best ways to garner consistent revenue each month. And, using WooCommerce Subscriptions is a great way to do just that. Create and manage physical or virtual products and services with recurring payments by setting up a subscription model.

Features include:

  • Over 25 available payment gateways
  • Automatic or manual rebilling of payments
  • Built-in renewal notifications and automatic emails
  • Detailed reports tracking revenue, active subscribers, and more
  • Free trials and sign up fees

Price: $199

5. Name your Price

Maybe you want to be a little flexible when it comes to the prices your customers pay for your products and services. That’s where Name Your Price comes into play. Accept customer-determined donations, suggest a price, and even require a minimum acceptable price. In the end, the customer does the talking when it comes to prices and you collect what they are willing to pay.

Features include:

  • Simple and variable product type support
  • Make product bundles available
  • Support subscription based models
  • Let subscribers choose when they will pay
  • Create printable gift certificates with separate Woo extension

Price: $49

6. WooCommerce Product FAQs

Building a knowledge base or FAQ section for your website is extremely helpful for customers during the purchasing process. And, many times customers do not want to email a shop owner and await a response because let’s face it people can be impatient. With the WooCommerce Product FAQs plugin, you not only help answer people’s pressing concerns, but you use their questions to build a FAQs section for your website to help others with similar concerns, as well as save a lot of time and effort.

Features include:

  • Customers can ask questions, get answers, and see other threads
  • Notifications sent to admin when questions asked, and customers when answered
  • Plenty of filters available for added functionality
  • Manually add questions to specific product FAQ sections
  • Similar to eBay’s “Ask Buyer” system

Price: FREE

7. WooCommerce Currency Switcher

Building a global brand is important if you want to be hugely successful. And, besides translating your website’s content for your international customers, another key thing you should be doing is implementing a currency switcher so customers can always know exactly how much your products or services will cost.

Features include:

  • Exchange rates are always up to date
  • Easy currency switcher drop down menu makes viewing other currencies easy
  • Display currencies on product, cart, shipping/tax, coupon, and check out pages
  • Manually define currencies or use the Yahoo Exchange rates
  • Add as many included currencies as needed

Price: FREE

8. Notable Mentions

The truth is, there are so many awesome WooCommerce extensions, both free and premium, that can help you create a standout eCommerce shop.

Here are some additional extensions or plugins that may interest you:

So, there you have it. Some of the coolest things you can do with WooCommerce extensions.

Whether you have a limited budget, or are looking to invest more into your online shop, there are many ways you can create unique online shops full of exceptional design and impressive functionality. All you have to do is know where to look.

 

 

 

 

 


© 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 Unique Things You Can Do With WooCommerce Extensions 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
  3. How to accept payments on your website
Categories: Domains

Namecheap drops lawsuit against Tucows

Domain Name Wire - Tue, 10/24/2017 - 16:56

Companies appear to be resolving their disagreement outside of court.

Domain name registrar Namecheap has dropped its lawsuit against Tucows.

Namecheap has historically been a domain name reseller using Tucows’ Enom platform. Namecheap is now registering domain names under its own registrar accreditation and asked Tucows to transfer the four million domains it has sold as a reseller to Namecheap.

Tucows did not agree with the transfer method in which Namecheap wanted to handle the transition. Worrying that Tucows was dragging its feet, Namecheap sued Tucows.

In response, Tucows said that it proposed multiple ways of transitioning the domain names that it believed were more appropriate and did not run afoul of ICANN rules.

Namecheap voluntarily dismissed the case without prejudice, meaning that it can refile the claims at a later time. This suggests that the parties are working out their differences outside of the courtroom.


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

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

The post Namecheap drops lawsuit against Tucows appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. January data show why Rightside sold eNom: Namecheap
  2. Namecheap sues Enom and Tucows, demands transfer of 4 million domains
  3. Tucows responds to Namecheap’s lawsuit over domain transfers
Categories: Domains

.London domain name to get a big marketing boost

Domain Name Wire - Tue, 10/24/2017 - 14:05

.London will start popping up in The Underground, on billboards and TV.

The .London top level domain name is about to get a lot more exposure in London.

The registry is beginning a major online and offline marketing campaign based on fictional companies from various London neighborhoods.

Ads will appear in the London Underground, prominent roadside billboards and TV. There will also be a digital and social media advertising component as well as business community outreach. Out-of-home ads will start in October and November and TV ads will air in January and February.

Here are examples of a couple of the ads:

I find the choice of domain names perplexing because the ads include apostrophes, which aren’t valid characters in domain names. Consumers will have to not only remember the lengthy domains, but also realize they should drop the apostrophe when typing the domain.

Still, this is exactly the type of campaign necessary to boost awareness of geo domain names.

There are currently 75,000 .london domain names in the zone file.


© 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 .London domain name to get a big marketing boost appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Dot London and Dot NYC taking two different approaches
  2. .London ads spotted in London last week
  3. .London’s unique “SunPriorityRush” period ends tomorrow
Categories: Domains

Screen-It Graphics attempted to Reverse Domain Name Hijack Grandstand.com

Domain Name Wire - Tue, 10/24/2017 - 13:47

Printing company filed cybersquatting case in abuse of policy.

As predicted, Screen-It Graphics of Lawrence, Inc. dba Grandstand has been found to have engaged in reverse domain name hijacking over the domain name Grandstand.com.

Screen-It has used the domain name egrandstand.com since 2006 and started using the name Grandstand for its business in 1991, according to the complaint. Grandstand.com, a valuable dictionary word, was registered in 1995.

The owner of Grandstand.com subsequently used the domain name on two occasions: once for a business and once for email.

In finding that the case was filed in abuse of the policy, panelist Richard G. Lyon noted:

A few of the more egregious examples are failure to allege or prove targeting, failure to provide proof of either registration or use of the disputed domain name in bad faith, and citing a number of Policy provisions and precedent misleadingly out of context. The circumstances of this case, consisting most significantly of the facts that the GRANDSTAND mark is also a word with dictionary meaning, the Respondent having registered the disputed domain name over 20 years ago, and the lack of targeting demonstrated on the record, at a minimum calls out for an explanation from the Complainant…

…The Complainant has advanced arguments, on both facts and Policy precedent, that are at best misleading and at worst intended to mislead the Panel.

Lyon summarizes his finding:

On any objective analysis the fact remains that the Respondent has been put to time and trouble to defend a proceeding the Panel considers groundless. Even the Complainant’s research, selective and cursory as it is, demonstrates an awareness of the Respondent’s prior commercial structure and its activity in an unrelated and noncompeting field. This, together with the fundamental flaws in the Complainant’s case and lack of proof on key Policy elements, convinces this Panel that this Complaint should not have been brought, and the Complainant and its professional representative should have known it.

Screen-It Graphics of Lawrence was represented by Hovey Williams LLP, an intellectual property law firm in Kansas. Ironically, its slogan is Where Integrity Thrives®.


© 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 Screen-It Graphics attempted to Reverse Domain Name Hijack Grandstand.com appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Nat Cohen’s Telepathy sues for reverse domain name hijacking
  2. comScore gets Reverse Domain Name Hijacking win
  3. Telepathy gets another Reverse Domain Name Hijacking win
Categories: Domains

Here’s an example of why Emojis are bad for domain names

Domain Name Wire - Mon, 10/23/2017 - 17:17

Domain names need to render the same way everywhere to work.

I send out a weekly newsletter matching podcasters with guests for their shows. (If you don’t subscribe, you should.)

The newsletter is powered by MailChimp, and the service has an easy system for inserting emojis in the subject line of your email. I imagine having an emoji or two draws attention to the subject line. For this week’s email, I included a megaphone emoji.

When the email showed up in my Gmail inbox today, the subject line looked like this:

That’s what it looked like in MailChimp, too. Then I opened the email and the subject line looked like this:

Hmm.

If I look at the email on the Gmail app on my iPhone it looks different again:

It’s a megaphone in all three examples but they all look different. This sort of inconsistency is OK for email marketing, but not for domain names.

This is just one of the reasons I believe emoji domain names will remain just a niche marketing gimmick.


© 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 Here’s an example of why Emojis are bad for domain names appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. What do I think of Emoji domains? Not much.
  2. I still think emoji domains are a bad investment
Categories: Domains

Domain Industry Roundup – DNW Podcast #157

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

Five interviews from Merge bring you up-to-speed on the domain business.

This week we catch up with five people in the domain name industry with interviews from last week’s Merge conference. You’ll hear from Dr. Hani Armstrong with Protected Parking about typo domains, Jonathan Tenenbaum about Tucows’ domain inventory and new lower prices, Ryan Colby about blockchain, Brandon Abbey with the latest updates from Payoneer, and Jothan Frakes, the new interim executive director of Domain Name Association. Also: Donuts-GoDaddy deal, domain theft and expired domain names.

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


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

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

The post Domain Industry Roundup – DNW Podcast #157 appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. What you need to know from ICA – DNW Podcast #128
  2. How End User Domain Buyers Think – DNW Podcast #134
  3. Dynadot CEO Todd Han – DNW Podcast #141
Categories: Domains

Comparing the GoDaddy Auctions model vs. NameJet model

Domain Name Wire - Mon, 10/23/2017 - 14:11

The two dominant expiring domain services have different models, each with their own pros and cons.

There are two big players in the market for back ordering expiring domain names that haven’t entered the deletion phase yet. These are names at registrars that have agreements with auction services to sell the names before they enter pending delete status.

GoDaddy and NameJet own this market. GoDaddy has its own inventory plus that of Endurance International Group. Next year it will add Name.com to this list. NameJet’s prized inventory is from Network Solutions, Register.com, Enom and Tucows. (The parent companies of these registrars own NameJet.)

The services take two different approaches to how domainers can buy expiring domains and what happens to names they acquire.

GoDaddy

No backorder is necessary, but investors can add names to their private watchlist. Domains have a set ending time and anyone can bid. If a name gets zero bids, it enters a reverse auction. The timing is such that registrants can still renew their domains after an auction is won. All won names are deposited into winner’s GoDaddy account.

Pros: Adding a domain to your watch list does not tip off other investors. No need to deal with backorders and subsequent auctions. All domains entered into one registrar account.

Cons: Other investors (and bots) can watch your late bids and enter auctions at any time. It’s typical to have auctions have no bids with five minutes left, then attract multiple bidders. Domains can still be renewed by the previous owner, so your time spent bidding on a domain can be wasted if they renew it.

NameJet

Investors place a backorder by a set deadline. Only people who place a backorder can participate in a three-day auction for the name. If only one person backorders the domain, they get the domain without an auction. Domains stay with the registrar that previously had the domain.

Pros: Auctions are limited to people who place backorders, so there’s less last minute sniping. Existing registrants can’t renew after you win the auction, so the winner definitely gets the domain.

Cons: Placing a backorder tips off other investors, so the “sniping” happens at the backorder deadline instead of the auction deadline. Domain names you win end up at various registrars rather than just one.

Which model do you prefer?


© 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 Comparing the GoDaddy Auctions model vs. NameJet model appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Expired Domain Report: 4 letter domain sells for $31.5k
  2. HuaGao.com at $20k and other expired domain name sales
  3. 15 domain names to backorder this week
Categories: Domains

Oh, zero click, when will you be cleaned up?

Domain Name Wire - Fri, 10/20/2017 - 15:24

Misleading landers and scams run rampant in zero-click programs.

The concept of zero-click domain name parking makes a lot of sense. Rather than sending a domain visitor to a pay-per-click page where they must make two clicks to generate revenue, zero-click forwards unused domain names to other destinations and collects a fee from the advertiser.

For example, instead of a sports domain name leading to a lander with sports keywords, it might forward directly to The Sports Authority’s website.

In practice, many parking companies use zero-click to augment standard pay-per-click when they believe it will monetize better. The problem is that, despite all of their claims, zero-click companies appear to suck at weeding out scam and spam destinations in their networks.

Part of the problem is that zero-click tends to bounce between several domain names before landing on the final destination. So a bad actor might get their URL approved as an advertiser, but then redirect the destination page to another page that wouldn’t be approved.

I came across another example today. The domain name Esty.com was hit with a UDRP. I don’t know for sure, but my guess is the homemade goods marketplace Etsy filed the complaint.

When I visited the domain name the first time, I was bounced between a few URLs and ended up at arp.bettersearchtools.com. The page looked like this:

This page looks a lot like the pages CloudFlare shows to prevent DDoS attacks. But look closely and you’ll see that it’s quite misleading. There’s a small disclaimer to “continue and accept offer”. The small print below the button says “By clicking the button above and installing the extension…”

In other words, it’s tricking users into clicking “I’m human” to continue to the site they were seeking, but they’ll end up installing a Chrome extension.

Zero-click companies need to figure out how to stop this or the whole business model should be shuttered. A day of reckoning is coming.


© 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 Oh, zero click, when will you be cleaned up? appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. ZeroPark revs up zero-click monetization for domainers
  2. Direct nav company files patent application for bidding on domain parking traffic
  3. Warning: do you know where your parked domain traffic is going?
Categories: Domains

Expired domains brought down IBM services

Domain Name Wire - Fri, 10/20/2017 - 14:12

Forgetting to pay about thirty bucks leads to critical services going down.

For about 24 hours in September, two IBM services associated with IBM Bluemix went down. The cause? Expired domain names.

According to an incident report spotted by The Register, global-datacenter.com and global-datacenter.net expired, bringing down Reverse DNS and Global Load Balancing with them. Ouch.

The company says the domain names are now set to auto renew to prevent this from happening again. I think the company would be wise to renew the domains for ten years at a time. It only renewed them for two years.

Perhaps executives at FedEx should take note: the Fedex.com expires next month.


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

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

The post Expired domains brought down IBM services appeared first on Domain Name Wire | Domain Name News & Website Stuff.

No related posts.

Categories: Domains

The .ART Premium Name Model: Four Months In

Domain Name Wire - Fri, 10/20/2017 - 13:12

[Editor’s note: I have been critical of both the number of .art domain names with premium prices and the number of tiers. In this article, Kurt Pritz, Member of the Strategic Planning Board and Operations team member for .art, provides an update on how the strategy is working. There are currently about 15,000 .art domain names registered.]

First, let me reiterate the purpose of the .ART premium names strategy. .ART set its standard domain price fairly low, $9. That was done to provide affordable names to the art community. Not surprisingly, over 30% of the .ART registrations to date are of the first-name—last-name type or some version of that. One would expect that where artists are self-identifying with their work. These name combinations are rarely premiums and so serves the art community well. We have also found that families have adopted the first-name—last-name idea, securing names for their kids as well. This .ART cachet with families is something being pursued as a product. The result is that .ART is selling many names to the expanded art community at low prices.

Second, .ART set out to determine a predictive value for each domain. It has always surprised me that domains are typically priced as if they were sold at the Dollar Store rather than the grocery store. It can be intuitively concluded that domains all have different values. The question is whether the differences are sufficient to warrant varying the pricing.

Without making a pre-determination, .ART set out to answer that question through an exhaustive “big-data” collection and analysis approach that gathered hundreds of millions of words and word-combinations from online sources (e.g., Google AdWords and Wikipedia) and static sources (e.g., art reference materials). This occurred over months of online data collection and included billions of queries.

We scored each word combination against 14 separate criteria such as word length (the shorter the better), and frequency of Google search (the more the better) in order to create relative values. We then compared these values against every prior premium domain sale in the past, and, after appropriate normalization, calculated a prospective market value for each of the possible domains. (A paper can be written on the previous two paragraphs.)

Considerable work was done after the fact to ensure the valuations were stable and immune to small environmental fluctuations.

The result, as you have written, was 3.5 MM premium names.  This caused .ART to identify these assets as “inventory names.” Does .ART expect to sell them all? No. (Even if they were sold as standard, .ART wouldn’t expect to sell them all.) But there are two positive outcomes, and I see no negatives ones.

One positive outcome is that .ART could build a business plan that could:

  1. serve the art community by selling domains cheaply to those in the art world (and those outside it) that wanted the sort of first-name—last-name domain that has become popular and is an obvious choice for those displaying their work online; and
  2. derive needed revenue from more-highly valued names that were sold to those who valued those names.

The second positive outcome was in the proportion of revenue generated. Shortly after GA opening, only 7% of the names registered were .ART inventory names but that represented 80% of the revenue. As time went on, the percentage of inventory names registered decreased to 5% but the revenue generated stayed above 70% of the total. These results are without the benefit of any premium name auctions, promotions or other concentrated efforts.

The vast, vast majority of these inventory names is priced above, but not too much above, standard prices. Over 96% of the identified names come from the bottom 3% of the pricing tiers. If .ART had followed traditional premium names models, these lower-valued inventory names would have been priced as standard names and much of that revenue would have been foregone. (That revenue is not a windfall; as other registry operators will tell you, it is vital to ongoing operations.)

I have found that, compared to other registries, .ART prices premiums either modestly or in-line with others.

The .ART inventory name model also provides an excellent opportunity for registrars. Registrars realize higher margins on inventory names and some have seen revenue ratios approaching that of .ART. When using .ART rebates and tools that point registrants towards inventory names, the impact on revenue can be significant.

The algorithmic prediction that there is a “long tail” of modestly valued premiums falls into line with marketplace thinking that is over ten years old. When I managed engineers (if such a thing is possible), our mantra was to trust the numbers. The .ART algorithm was carefully designed. Even though this algorithm is, in some ways, the first of its kind, the results should not be disregarded in favor of instinct or past practice.


© 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 .ART Premium Name Model: Four Months In appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. Delayed.art: .Art domain name launch shuts down over technical difficulties
  2. A look at .Art after one week
  3. Five Warning Signs a Top Level Domain is Doomed
Categories: Domains

CentralNic adds 14 TLDs but .SK deal delayed

Domain Name Wire - Thu, 10/19/2017 - 18:33

KSRegistry deal brings total TLDs managed to 65.

Domain name company CentralNic (London AIM:CNIC) made two announcements today involving top level domain names.

First, it has signed a deal with KSRegistry to handle registry services for the 14 TLDs KSRegistry inherited when it acquired Open Registry from Group NCC this year. (I reached out to KSRegistry to understand how it is servicing other TLDs not mentioned in the deal but have not heard back.) This will increase CentralNic’s stable of TLDs it manages to 65.

Second, CentralNic says its deal to acquire SK-NIC’s assets for running Slovakia’s .sk domain name has been delayed “due to complexities in legal processes”. CentralNic announced the €26 million acquisition in August. Many people in Slovakia are opposed to the deal. I reached out to CentralNic CEO Ben Crawford for comment and he said it’s just some slow legal processes.


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

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

The post CentralNic adds 14 TLDs but .SK deal delayed appeared first on Domain Name Wire | Domain Name News & Website Stuff.

Related posts:
  1. CentralNic to relaunch Christmas Island .CX Domain
  2. CentralNic acquires .SK operator for €26 million
  3. CentralNic hits 4 million new top level domain names
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.