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.

Google sues more “Google Listings” telemarketers

Domain Name Wire - Wed, 05/30/2018 - 14:53

Google files lawsuits against companies that it claims mislead businesses about their Google listings.

If your phone number is associated with a business, there’s a great chance you’ve been on the receiving end of telemarketing calls or robocalls like this. The caller usually claims to be affiliated with Google or Google itself.

Google has fought back against some of these companies in the past, and it is turning to the courts again in an effort to take stop several other companies it alleges are misleading consumers.

The search giant filed one lawsuit in California and two lawsuits in Florida.

The California suit is against Kydia, Inc., d/b/a BeyondMenu. Google alleges (pdf) that the company is misleading restaurant owners in an effort to get access to their Google listing and link to BeyondMenu’s restaurant ordering service rather than directly to the restaurant’s site.

The Florida lawsuits (pdf, pdf) name the following companies:

Supreme Marketing Group d/b/a Small Business Solution and d/b/a Claim My Biz
Pointbreak Media LLC, d/b/a Point Break Solutions and Kivanni Marketing
Modern Source Media, LLC
Modern Spotlight Group, LLC
Modern Spotlight, LLC
Perfect Image Online

Looking back at the case filed against Local Lighthouse in 2015, it appears that Local Lighthouse admitted its actions and agreed to not do it anymore…but I don’t see any financial penalty in the judgment (pdf). Unless Google brings down the hammer on companies that do this, they will continue to proliferate.

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

Related posts:
  1. YouTube Chases Down YouTube.net
  2. Google Steps Up Domain Name Arbitration Cases
  3. FairSearch files formal objections against Google’s .search, .fly and .map TLD applications
Categories: Domains

.XYZ gets another win against Verisign

Domain Name Wire - Tue, 05/29/2018 - 17:29

Appeals court decision gives XYZ another chance to be awarded legal fees.

It’s been over three years since Verisign (NYSE: VRSN) sued XYZ, the seller of .xyz domain names, for false advertising.

The District Court granted summary judgment in favor of XYZ in November 2015 but that wasn’t the end of it. XYZ asked the court to award attorney’s fees, at which point Verisign appealed the summary judgment decision to the Court of Appeals.

XYZ prevailed again in the appeal, which meant that the lower court could then consider XYZ’s request for attorney’s fees. The lower court found that the case did not qualify as exceptional and denied XYZ’s request for Verisign to pay its growing legal bills.

Then it was XYZ’s turn to appeal. It argued that the District Court applied the wrong standard–“clear and convincing evidence” instead of “a preponderance of evidence”– when considering the legal fees.

The Court of Appeal just found (pdf) in XYZ’s favor. It has remanded the case to District Court, agreeing that the lower court applied the wrong standard in its decision. It also clarified that XYZ does not need to show that Verisign acted in bad faith to prove an exceptional case worthy of legal reimbursement.

As with the original lawsuit, the stakes are higher for XYZ and Verisign. The millions in legal fees XYZ has accrued are a big deal to it and just a rounding error to Verisign.

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

Related posts:
  1. Breaking: Verisign loses appeal in .XYZ lawsuit
  2. Negari and .XYZ file Brief in Verisign Appeal
  3. Verisign signs .com contract extension, amends cooperative agreement
Categories: Domains

Drew Wash develops businesses on premium domains – DNW Podcast #186

Domain Name Wire - Tue, 05/29/2018 - 15:30

Drew Wash made a big bet that led to a business generating $1 million recurring per year.

In 2007 Drew Wash mortgaged his house to buy the domain name Towing.com. It was a big risk that has paid off. On today’s show, Wash explains how he has developed businesses on premium domain names. He is starting a documentary video series in which he will try to develop three premium domains into businesses with $25k in monthly recurring revenue…it’s going to be a blast (and educational) to follow.

Also: Tired of GDPR yet? GoDaddy’s Whois, home.loans, how to park .app domains and Wonder Woman 2.

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

Related posts:
  1. The challenges of new TLDs with Tobias Sattler – DNW Podcast #177
  2. Sandeep Ramchandani, CEO of Radix – DNW Podcast #183
  3. Jen Sale of Evergreen – DNW Podcast #185
Categories: Domains

Undeveloped adding SSL to all landing pages

Domain Name Wire - Tue, 05/29/2018 - 14:39

Marketplace is adding SSL to landing pages, starting with .app.

Domain name selling system Undeveloped.com is adding SSL certificates to all domain names parked on its service, the company has informed Domain Name Wire.

Starting now, you can park .app domain names on Undeveloped and the service will create an SSL certificate for them. The company is not stopping there; by the end of the week it hopes to have all domains on the service (including .com) using SSL certificates.

The move is important for a couple of reasons.

First, Google is requiring second level domains on some of its TLDs to have an SSL certificate in order to resolve.

Second, Google’s Chrome browser is steadily warning people away from pages that aren’t secure. This could reduce sales conversions.

Some parking services are getting around the SSL issue by forwarding domain names to secure page on the marketplace’s URL, but adding SSL to the individual domain names is ultimately a better solution.

Marketplaces can do this using the free LetsEncrypt service, but some programming work is required.

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

Related posts:
  1. Tool makes it possible to park .App domain names
  2. Domain inquiries could drop next month. Blame SSL.
Categories: Domains

Tucows responds to ICANN legal action related to GDPR

Domain Name Wire - Tue, 05/29/2018 - 13:53

World’s second largest domain name registrar lays out its position on GDPR as it relates to domain registrations.

On Friday, the day that the EU’s General Data Protection Regulation (GDPR) went into effect, ICANN filed a legal action in Europe against Tucows’ registrar EPAG. ICANN asked for a temporary injunction after EPAG notified ICANN it would no longer collect administrative and technical contact details for domains in an effort to comply with GDPR.

Tucows has issued a statement about its position, and it goes a long way to explaining the rationale behind its GDPR-related decisions.

At a high level, there are two things to mention when it comes to Tucows and GDPR.

First, Tucows has been the most forward-thinking and forward-planning registrar when it comes to Whois. At least from a public perspective, Tucows has been laying the groundwork for its plans publicly for many months. Then ICANN passed down its mandate with just days before GDPR went into effect.

Second, there is some nuance to what EPAG said that it would not collect that I didn’t pick up Friday evening in ICANN’s statement: ICANN will continue to collect registrant data for customers; its opposition is to collecting administrative and technical contact data.

Here are the items Tucows explains in its statement:

Personal data collection – Tucows takes issue with collecting admin and technical contacts in addition to registrant contacts. It points out that, while many times the contact details are the same for all contact types, this isn’t always the case. And when it’s not, Tucows is potentially collecting the personal data of people it doesn’t have a contractual relationship with.

This is a good point and one worth considering: do we really need all of these contact types for domains?

Personal data transfer to the registry – Tucows questions the need to pass personal data to registries under the thick Whois model, and points out that the thin Whois model under .com and .net has worked fine. There has been a movement to move everything to thick, in which the registries maintain the data. But plans to move .net and .com to thick have been delayed thanks to GDPR.

Personal data display– ICANN’s temporary specification for Whois requires registrars to display the organization name, state/province and country of the registrant in Whois. Tucows is opposed to publishing the organization name because it says many people don’t understand this field and enter their personal name instead of a company name.

Tucows concludes its response by saying it hopes the legal action will bring clarity. As I mentioned in the post Friday, I think Tucows was in favor of ICANN filing its legal action because it will force a response from EU courts about how they will interpret GDPR. More than anything, all parties in the domain ecosystem just want to know what they need to do to comply with the law.

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

Related posts:
  1. ICANN files legal action against Tucows registrar over GDPR
  2. Time is ticking, and domain transfers are still up in the air
  3. Namecheap leaps up .com chart as PDR falls
Categories: Domains

ICANN files legal action against Tucows registrar over GDPR

Domain Name Wire - Sat, 05/26/2018 - 01:56

Domain name overseer hopes to get clarification about data collection for domain name registrations.

ICANN has filed injunction (PDF) proceedings against EPAG, a domain name registrar owned by Tucows (NASDAQ:TCX), in a challenge meant to get clarity on the European Union’s General Data Protection Regulation (GDPR). EPAG is a German registrar that Tucows acquired in 2011.

While many registrars have stopped publishing personal information in Whois, EPAG has told ICANN that it will no longer collect administrative and technical contact details because it believes doing so will violate GDPR.

ICANN’s recent temporary specification for Whois states that accredited registrars must continue to collect the information even though they aren’t required to display it publicly in Whois.

In a release, ICANN stated:

“We are filing an action in Germany to protect the collection of WHOIS data and to seek further clarification that ICANN may continue to require its collection. It is ICANN’s public interest role to coordinate a decentralized global WHOIS for the generic top-level domain system. ICANN contractually requires the collection of data by over 2,500 registrars and registries who help ICANN maintain that global information resource,” said John Jeffrey, ICANN’s General Counsel and Secretary. “We appreciate that EPAG shared their plans with us when they did, so that we could move quickly to ask the German court for clarity on this important issue. We also appreciate that EPAG has agreed that it will not permanently delete WHOIS data collected, except as consistent with ICANN policy.”

If EPAG’s actions stand, those with legitimate purposes, including security-related purposes, law enforcement, intellectual property rights holders, and other legitimate users of that information may no longer be able to access full WHOIS records.

It seems that ICANN is using this as a test case, perhaps with a wink and a nod from EPAG as all parties seek to get a better understanding of how GDPR should be interpreted.

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

Related posts:
  1. Tucows responds to ICANN legal action related to GDPR
  2. GDPR will make domain name transfers more difficult
  3. Canada Leading the Way with Whois Changes
Categories: Domains

Walker Edison is a reverse domain name hijacker

Domain Name Wire - Thu, 05/24/2018 - 15:48

Company files dead-on-arrival cybersquatting dispute.

Furniture company Walker Edison has been found guilty of reverse domain name hijacking by a National Arbitration Forum panelist.

The decision comes after Walker Edison Furniture Company filed a cybersquatting complaint under UDRP against the domain name ForestGate.com. Walker Edison has a furniture brand called Forest Gate.

But the owner of the domain name ForestGate.com registered it in 1999, well before Walker Edison started using the brand. It filed a trademark application just weeks before filing the UDRP. It claimed common law rights, but even those potential rights postdated the domain registration.

In other words, the complaint was doomed to fail.

The fact that the UDRP was filed so soon after the trademark application makes me question the complainant representative’s (J. Dustin Howell of Workman Nydegger) understanding of UDRP.

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

Related posts:
  1. Non-Profit Urban Logic Guilty of Reverse Domain Name Hijacking
  2. Dubai Law Firm Nailed for Reverse Domain Name Hijacking
  3. Telepathy scores $40,000 from reverse domain name hijacking case
Categories: Domains

Home.loans is ranking high on Google

Domain Name Wire - Wed, 05/23/2018 - 18:05

New website is already ranking well for a very competitive term.

When Blake Janover bought the domain name home.loans for $500,000, people scoffed at how he believed the domain name would help him in search results. Sure, his multifamily.loans domain ranked quickly, but there’s little competition for that term.

Fast forward several months and home.loans is indeed ranking well. It shows up on the first page for me when I search for “home loans” in quotes, and #11 when I search without quotes.

That’s pretty darn good for such a competitive term.

Of course, search rankings fluctuate. Just recently vacation.rentals was on the first page of Google but it appears to have slipped to the second page.

[Update: as of Friday, the domain has slipped significantly in the rankings]

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

Related posts:
  1. Top 5 Domain Name stories from January
Categories: Domains

Tool makes it possible to park .App domain names

Domain Name Wire - Wed, 05/23/2018 - 15:53

Free system generates an SSL on your domain name and forwards it to popular domain sales services.

If someone wants to buy your .app domain name they won’t be able to use Whois to contact you. Google Registry does not show .app domain owner information in Whois.

That means you have to park the domain name so people can fill out a contact form to inquire about buying the domain. That’s not easy, either; the domain name you have must have an SSL certificate installed in order to forward to another page.

A domain investor created a simple and free tool to make forwarding domains to landing pages possible: DomainSales.app.

The system is very basic but does just what you need it to. When you submit a domain and point your nameservers to it, it gets a free LetsEncyrpt SSL certificate for your domain. You can then choose to forward the domain to landing pages for many different services: Afternic, Epik, Efty, Sedo, Undeveloped, and Uniregistry as of today.

To see it in action, visit Voicemail.app.

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

Related posts:
  1. Domain inquiries could drop next month. Blame SSL.
  2. .App domains are off to a strong start with brands
  3. Over 100,000 .App domains already registered
Categories: Domains

Domain registrations might tip Wonder Woman 2 details

Domain Name Wire - Wed, 05/23/2018 - 13:52

Domain names suggest titles or themes for Wonder Woman sequel.

It’s no secret that a sequel to the Wonder Woman movie is in the works. New domain name registrations might tip off possible names for Wonder Woman 2.

Warner Bros. registered several dozen domain names yesterday that might give hints. Here are the .com domains it registered:

wonderwoman1980.com
wonderwoman1981.com
wonderwoman1982.com
wonderwoman1983.com
wonderwoman1984.com
wonderwoman1985.com
wonderwoman1986.com
wonderwoman1987.com
wonderwoman1988.com
wonderwoman1989.com
wonderwomanarrives.com
wonderwomancheetah.com
wonderwomanlives.com
wonderwomanminerva.com
wonderwomanpart2.com
wonderwomanpartii.com
wonderwomanreturns.com
wonderwomanrises.com

Based on these registrations, it appears that working titles for the film include Wonder Woman Arrives, Wonder Woman Cheetah, Wonder Woman Lives, Wonder Woman Minerva, Wonder Woman Returns or Wonder Woman Rises. Are any fans of the movie and comic books able to shed light on these, or on the date domains?

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

No related posts.

Categories: Domains

Benefits to keeping Whois open

Domain Name Wire - Wed, 05/23/2018 - 13:38

Domain name owners benefit when their Whois records are publicly available.

The world’s largest domain name registrar is going to keep publishing Whois data for the bulk of its customers despite GDPR. This is good news for many people who rely on the data. I understand that security researchers will be upset that the data won’t be available in bulk. But even the individual lookups will help people–including the domain name owners themselves.

Here are some ways that Whois helps domain name owners:

1. Fewer UDRPs and lawsuits

I expect there to be an increase in UDRP filings thanks to redacted Whois information. Currently, UDRP complainants are able to research the owner of a domain name based on the Whois. This allows them to think twice about filing a UDRP if a) the owner is someone who commonly defeats UDRPs, such as Frank Schilling or b) it’s clear from the Whois record that the owner has a legitimate interest, such as if their name or company name matches the domain.

True, some complainants file cases even in these circumstances. But going forward they will have to file blind “John Doe” cases. They won’t always know who owns the domain until the response is filed.

Some complainants will back out at this point, but many will go forward.

It would be nice if the UDRP providers add an interim step to the filing process. The complainant could say it’s making a filing and pay the fee. At this point, they will find out the identity of the domain owner from the registrar. If they withdraw the case at this point they get most of their money back.

Also, escalation to UDRP and the courts will happen faster. Right now, intellectual property owners typically start by sending a cease & desist letter when they believe a domain is infringing on their trademark. They escalate this to a UDRP and/or a lawsuit if they can’t resolve the matter.

Whois records that don’t contain a forwarding email address have no good way for lawyers to contact domain owners. So they’ll either decide it’s not worth pursuing or will move straight to the UDRP/lawsuit stage. That’s bad for everyone when a simple email could resolve the issue.

In fact, UDRP panelists sometimes site a lack of pre-dispute communication from a complainant as a sign of bad faith.

2. More domain sales

People tend to buy existing domain names in three ways: through a marketplace listing (sometimes syndicated), through a link or contact form on a parked page, or by looking up the owner in Whois. Most of my bigger deals have come through the latter.

It’s probable that redacted Whois records will drive more sales to marketplace listings and parked pages, but taking any option off the table adds friction to the process.

3. Fewer stale marketplace listings

Domain name marketplaces scan Whois to look for changes in ownership and are sometimes proactive about removing domain names no longer owned by the lister. A lack of public Whois will lead to more stale listings on marketplaces that are not listed by the actual owner.

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

Related posts:
  1. GoDaddy Gets Split Decision in Domain Dispute
  2. Trans-Pacific Partnership Treaty addresses cybersquatting, Whois
  3. I just fixed Whois and GDPR
Categories: Domains

Domain name transfer process changes this week

Domain Name Wire - Tue, 05/22/2018 - 16:58

New registrar won’t have to get positive authorization from Form of Authorization.

A temporary change to the inter-registrar domain name process kicks in later this week due to Whois changes associated with the EU’s General Data Protection Regulation (GDPR).

In many cases, domain name registrars will not be able to get the registrant email address from Whois that is necessary to send a Form of Authorization when someone transfers a domain name to them. As a result, gaining registrars will be allowed to skip the Form of Authorization requirement. This means the new process will work like this:

1. Domain registrant gets an authorization code from the old registrar.
2. Registrant orders transfer at the new registrar and provides the authorization code to the new registrar.
3. New registrar sends the transfer request to the old registrar.
4. Old registrar sends notice to the registrant. If the registrant doesn’t cancel the transfer within five days, the transfer is completed.

The registrant will have to provide Whois data to the new registrar since it can’t be pulled from the existing Whois record.

Eventually, ICANN will have a system in which registrars can get access to Whois data. At that point, the transfer policy will possibly revert to the old policy (or a new transfer mechanism will be put in place).

The policy applies to domain name that are regulated by ICANN, so ccTLDs will not be affected.

The new policy might increase domain thefts. Some registrars are stepping up monitoring and taking other precautions to prevent this.

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

Related posts:
  1. GoDaddy’s 60 Day Transfer Lock Closer to Termination
  2. .Com winners and losers
  3. Consensus be damned: here’s how transfers will work at Tucows after GDPR
Categories: Domains

GoDaddy will continue publishing most domain owner data

Domain Name Wire - Tue, 05/22/2018 - 13:24

Registrar is more selective about which Whois records will be redacted in wake of GDPR.

With the GDPR deadline quickly approaching, the world’s largest domain name registrar has been mostly silent on its plans. Over the past week, I connected with GoDaddy (NYSE:GDDY) to understand what it plans to do to comply with the EU’s privacy law, especially as it relates to Whois.

Unlike many of its competitors, GoDaddy does not plan to redact Whois information for domain names registered by people outside of the EU. It will continue to publish contact information like it always has for web-based Whois searches. Because it has to redact information for EU residents, GoDaddy will no longer sell DomainsByProxy to people in the European Union but will continue to offer it to people in other regions. (Some countries are routed through others for purchasing due to common currencies and/or languages. For example, customers in Morocco are routed to GoDaddy’s France website. They will be treated like EU residents for purposes of Whois.)

GoDaddy’s decision doesn’t surprise me too much. GoDaddy was an early pioneer of Whois proxy services and has aggressively pushed the paid and high-margin product to its customers. I’m not sure how much money GoDaddy makes from DomainsByProxy but I imagine it’s significant.

Of course, GoDaddy won’t come out and say that Whois privacy revenue is the reason for its decision. SVP & GM – Domains, Kevin Doerr told Domain Name Wire:

There were many reasons we looked at keeping Whois the way it is globally. GoDaddy welcomes the privacy changes that come with GDPR, but we wanted to be thoughtful about impacting our global customers. So GoDaddy will closely monitor the impact of GDPR, as well as regulatory requirements from governments around the world, before making decisions on how to evolve our privacy and Whois practices for every customer.

Whatever the reasons, as a proponent of more public data, I’m in favor of GoDaddy’s decision.

GoDaddy will continue to restrict data on Port 43 lookups, however. Port 43 lookups will contain technical data, state and country only. This will apply to people who currently have whitelisted port 43 access, too.

GoDaddy has restricted Port 43 data since January to cut down on spam. The company has been criticized for Port 43 blocking, but the final GDPR Whois spec from ICANN is essentially in line with what GoDaddy has already done.

The net effect should be little to no spam for domain name registrants but people with a good reason to contact them will still be able to by performing individual Whois lookups on GoDaddy’s website.

Tucows, the world’s second-largest domain registration company, has announced that it will treat all Whois records the same regardless of where the registrant is located. They will all be redacted.

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

Related posts:
  1. How GoDaddy “uses this one simple trick” to get 56,000 more registration years per month
  2. GoDaddy to start masking some Whois data through Port 43
  3. GoDaddy (GDDY) reports earnings, domain revenue of $263.3 million
Categories: Domains

Google Chrome will downgrade positive SSL designations

Domain Name Wire - Mon, 05/21/2018 - 17:17

Rather than focus on positive indicators, Chrome will focus on negative indicators for sites without SSL.

Google has been on a mission to get website owners to add an SSL certificate to their website. It has used its market power with the Chrome browser to positively identify sites with SSL and to negatively identify those without SSL.

Over time, as more and more sites have SSL, the company plans to remove the positive identifiers for sites with SSL and instead just focus on negative identifiers for sites without https. Here are the changes it’s making:

Google is upping the ante on sites without SSL while it ratchets down the notices for secure sites. All sites without an SSL certificate will show Not Secure in the address bar, and this will become red when people enter information into a form.

The move makes sense and actually solves a problem with Chrome’s treatment of SSL. By denoting sites with SSL in a positive way, Google might be sending the false impression that the site is safe. But it’s easy for a phisher or other scammer to get a domain-validated SSL certificate.

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

Related posts:
  1. Could Google Chrome Actually Be Good for Domainers?
  2. Top 5 Domain Name News Stories September 2008
  3. Gap.com and HomeDepot.com lack full SSL
Categories: Domains

Building an Ecommerce business on your domain name – DNW Podcast #186

Domain Name Wire - Mon, 05/21/2018 - 15:30

How to easily create an online store.

How can you turn your domain name into an ecommerce store and sell it? Our guest today, Caroline Balinska, explains how to find products to sell, how to set up your online store on Shopify, and drive consumers to it. Then, learn how you can sell your ecommerce site on an exchange similar to Flippa. Download Caroline’s guide here.

Also: Domain investor arrested, GDPR, Donuts invests in a former DNW Podcast guest, easier .Travel, and more.

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

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

Related posts:
  1. Help! My Domain name was stolen! with Pablo Palatnik – DNW Podcast #29
  2. Michael Blend – DNW Podcast #62
  3. Risks ahead for domain name owners? – DNW Podcast #104
Categories: Domains

EnCirca offers trademark holders a shortcut to Amazon’s .Bot

Domain Name Wire - Mon, 05/21/2018 - 13:34

Service creates a bot for companies, making them eligible to register .bot domain names.

Amazon’s .bot top level domain name has been open for registrations since December, but registering them hasn’t been easy. Amazon has restricted registrations to companies and people that have an existing bot built on one of a handful of bot platforms.

Encirca, a registrar that specializes in difficult-to-register domain names, has partnered with one of those bot platforms to help companies register .bot domains. The offering is aimed squarely at trademark holders and was announced in conjunction with the International Trademark Association (INTA) meeting in Seattle this week.

Encirca is working with Pandorabots to essentially create and register a bot for the companies, making them eligible to register a .bot domain name. The total fee is $200, including the $75 registration fee EnCirca charges for .bot domain names.

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

Related posts:
  1. Registrar suspends all domain names transferred from terminated registrar
  2. Amazon opens .Bot up to more bots
Categories: Domains

Latest U.S. Government statement on GDPR and Whois

Domain Name Wire - Fri, 05/18/2018 - 15:58

Government is looking into Article 49 exceptions of GDPR.

David Redl, who runs the U.S. government’s National Telecommunications and Information Administration (NTIA), has repeatedly spoken against GDPR’s potential effects on Whois. Yesterday, at a meeting of National Security Telecommunications Advisory Committee (NSTAC), he gave further remarks about the issue and what the U.S. government is currently doing about it:

And so far, the EU’s guidance issued for implementing the GDPR is vague and insufficient. American companies and the U.S. government do not have an adequate basis on which to comply with the law.

We are seeking a broader interpretation of Article 49 of the GDPR, which provides exemptions for data transfers that are necessary for “important reasons of public interest.” This would not only address our concerns with regard to WHOIS, but would also address the potential interruption of U.S.-EU cooperation in many other public interest areas.

Absent a broader interpretation of Article 49, a short-term moratorium on GDPR enforcement with regard to WHOIS may be necessary. If not, then come May 25, we anticipate registries and registrars will stop providing access to WHOIS directories and services. The loss of access to WHOIS information will negatively affect law enforcement of cybercrimes, cybersecurity, and intellectual property rights protection activities globally. To all of you who know the importance of these issues, I ask that you make your voices heard.

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

Related posts:
  1. Redl groups “Right to be Forgotten” with other censorship, calls it “regrettable”
  2. Will May 2018 be the death of Whois?
  3. I just fixed Whois and GDPR
Categories: Domains

Sahar Sarid arrested on charges related to Mugshots.com

Domain Name Wire - Thu, 05/17/2018 - 20:31

California AG files criminal charges against Sarid and three other people it says were behind extortion scheme.

The alleged owners of Mugshots.com might find their own mugshots on the site soon.

This includes domain name investor Sahar Sarid.

California Attorney General Xavier Becerra announced charges of extortion, money laundering, and identity theft against the four alleged owners yesterday. Sarid was arrested in Florida and his mugshot is available here.

According to the Attorney General, Mugshots.com posts mugshots of people who are arrested. If they want the mugshot removed they have to pay a fee, even if they were never charged or were arrested in error.

Sarid is based in Florida and the state of California wants to extradite him to California to face the charges.

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

Related posts:
  1. Commercial Connect fails miserably in Community Priority bid
  2. Breaking: Judge dismisses Verisign’s lawsuit against .XYZ
  3. Man sentenced for hijacking company’s domain name and demanding $10,000
Categories: Domains

Now is the time to join ICA

Domain Name Wire - Thu, 05/17/2018 - 19:04

There’s a lot worth fighting for in 2018.

This year is going to be an important one for the domain name industry and domain investors.

Domain investors face serious headwinds from the EU’s General Data Protection Regulation. Changes to Whois will drastically change how we securely transfer domain names, find domains to buy, and communicate with domain buyers.

And later this year we’ll find out if the U.S. NTIA renews its cooperative agreement with Verisign, which could have a big impact on .com domain name prices.

This is a lot to keep up on, and I doubt many domain investors reading this have taken any action with regards to these, such as participating in a working group on the Whois user accreditation model.

One group that is participating in these groups and advocating for your needs is the Internet Commerce Association (ICA).

I’ve personally never been more confident in ICA’s leadership, and it would be wise to consider joining as a member. You can join online, and individuals can join for just $50 a month. That’s less than the cost of many domainer service subscriptions, and it will have a great impact on the future sustainability of your business.

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

No related posts.

Categories: Domains

Donuts invests in Cognate, a blockchain-trademark company

Domain Name Wire - Thu, 05/17/2018 - 13:00

Cognate uses blockchain tech to record proof-of-use of trademarks.

Donuts.Ventures, the investing arm of new top level domain name registry Donuts, has invested in Cognate. Cognate uses blockchain technology to record proof-of-use of trademarks.

I interviewed Cognate founder Bennett Collen on DNW Podcast #137. At the time, the business was based on saving records to show common law trademark rights. Since then, the company has added the ability to add proof-of-use for registered trademarks.

There are a number of potential ways that Donuts can help Cognate grow, including assisting the company with getting into the registrar channel to sell the product to business owners.

Donuts.Ventures’ other two public investments include Netki and GeoNetwork.

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

Related posts:
  1. Trademark Clearinghouse extends alert service beyond 90 days
  2. New TLD company Architelos sued after threatening IP Law Firm
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.