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.

Flippa raises $11 million Series A

Domain Name Wire - 2 hours 18 min ago

An old name in the domain name business gets a big cash infusion.

Website marketplace Flippa has raised an $11 million Series A round over a decade after it was founded.

Flippa lets people buy and sell online businesses, and was doing it since before it was cool. I visited the company’s headquarters in Melbourne way back in 2012.

The service has had its ups and downs over the years. And like any business this age, you can expect some business model changes over time. Flippa added support for domain name sales a while back and even made an ultimately unsuccessful acquisition of a domain brokerage.

These days, there’s lots of competition in the website brokerage business. Much of it is in the form of brokerages and M&A groups specializing in online businesses.

Flippa has a laundry list of action items for its new cash, including expanding beyond websites and apps. In a blog post announcing the raise, CEO Blake Hutchinson states, “We will soon help you to trade ANY and EVERY digital asset type of ANY size. ” One would assume that could include another crack at the domain name aftermarket.

Post link: Flippa raises $11 million Series A

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

Domaining.com owner wins RDNH in cybersquatting dispute

Domain Name Wire - 6 hours 23 min ago

Francois Carrillo successfully defended his valuable nuro.com domain with help of attorney John Berryhill.

Francois Carrillo, owner of the popular domain news aggregator Domaining.com, has successfully defended (pdf) his domain name nuro.com in a UDRP. The Complainant was also found guilty of reverse domain name hijacking.

Canadian healthcare company NURO Corp. filed the UDRP. The company was incorporated in 2017. Carrillo acquired the domain name in 2015, so this case was dead on arrival on the issue of bad faith.

The panel found that the domain was not registered and used in bad faith. Oddly, it did not find rights or legitimate interests for Carrillo, which I think was a mistake. But the most important thing is that the panel decided the overall case correctly and also found NURO Corp. guilty of reverse domain name hijacking.

Many panels are hesitant to find a Complainant that is not represented by outside counsel to have engaged in reverse domain name hijacking. But in this case, it was clear that the Complainant had access to outside counsel when filing its case.

The panel found reverse domain name hijacking because the Complainant filed the case even though the facts demonstrated the complainant knew it could not succeed on the issue of bad faith registration and use.

John Berryhill represented Carrillo.

Post link: Domaining.com owner wins RDNH in cybersquatting dispute

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Frank Schilling Loses His First UDRP
  2. RDNH in Circus.com case
  3. Tambour Ltd filed complaint that was “bound to fail”
Categories: Domains

Takeaways from the Epik hack call

Domain Name Wire - 7 hours 29 min ago

A call that starts with a discussion about the Epik hack covers lots of ground and sometimes goes off the rails. Here are some of my takeaways.

Rob Monster in a live meeting last Thursday. Photo from video still.

On Thursday, September 16, Epik CEO Rob Monster held a live meeting on his platform PrayerMeeting.com in the wake of the hack of his company.

Nearly four hours of the meeting is recorded and available on YouTube. It has also been transcribed.

I read through the entire transcript. It went off the rails at times. Consider this exchange, per the transcript:

Catgod [holds a gallon-sized bag of marijuana up to the camera] You see that demons? You see that demons? God has given me, he’s just given me [crosstalk]

C What you smoking on, Catgod?

Catgod Got some A1 Yolo, got some Cherry Lime Rickey.

Monster, 3:15:57 That’s funny.

Catgod But all them demon n*****s, He’s just giving them reggie.

HF [holding vape] NYC Flow.

Monster, 3:16:06 Um, gosh guys.

Gosh guys, indeed.

Twice during the call, Monster broke into prayer to cast away demons. But Monster said he also thinks Epik will be better after the hack because God will repay the company:

Monster, 2:54:42 I think that Jesus basically allows evil to happen because he gives us free will. But I think that in the end he transmutes evil so when there’s injustice… and it’s repaid sevenfold. So this hack could happen, it’s going to actually repay Epik with a bounty sevenfold. That’s God’s… [noise from other participant, unintelligible] …but when Satan overplays his hand, does something really stupid, then the Lord transmutes that into good.

Here are some takeaways and other thoughts from reviewing the transcript:

Shitty code

Monster admitted that there was some “shitty Russian code” that came from acquisitions. He said the code stemmed from the acquisition of Intrust Domains in 2011.

Monster, 0:35:56 [reading chat. Full comment from “JP”: “I’m upset at the security incident at Epik, but my anger isn’t towards Rob specifically, he’s just human.”] “upset at the security incident at Epik but my anger isn’t towards Rob…” Yeah no, thank you, I appreciate that, JP. Yeah we… we did not nail that one. I think quite candidly that was some serious weak code, like hard-coding API keys… just weak sauce. And in reality, like I said earlier in the call, our top engineers mostly hadn’t seen that code because it was kind of blackboxed, behind a firewall, separate git repository, and not part of the Epik git. And that might sound surprising… [pauses to blow nose] sorry, I have a cold… considering that we’re like a registrar, but that’s basically because of the history of how that company became part of Epik. It was an acquisition, it is a captive dev team, and I’ve operated with that group to a large extent on the basis of trust. They’re good people, they’re honorable people, ethical, responsible people, but their coding methods and frameworks are not up to standard, and they’ve pretty much handed over all the keys to two top guys, Justin Tab, David Roman. And they’re they’re doing a great job diving into the code. And there were some very unpleasant discussions, very heated conversations, because some of the team hadn’t seen the code until until it was exposed. That might sound a little bit crazy but you have to keep in mind that we’ve grown really quickly around a core registrar, and if you want to know the history, I’ll tell you a story. You guys mind a digression? I’ll tell you a story…

Rob then tells the story about how he left DigitalTown and doubled down on Epik in August 2018 after he gets “absolute clarity that the Lord is going to need a registrar”.

Monster draws a line on free speech

Monster is clearly not a free speech absolutist. Epik has taken content down. Live during the call, he took down a site that had been spreading information and doxxed one of the callers. It’s also worth noting that he made a Texas anti-abortion group take down a site that asked people to submit information about people getting abortions.

This brings up an interesting point. Monster draws a line, and it’s a line somewhere in his philosophy and mind. Other people draw the line elsewhere, but Monster calls this deplatforming and unfair. So really, nearly everyone believes in free speech up until a point. And if their point is less restrictive than someone else’s, they call it censorship and deplatforming.

Monster elaborated on drawing the line:

We had two board directors, they were both Jewish they both resigned because of the Gab stuff I think was too hot. Then after the 8chan thing, it was a client for two days and we let them go. But it’s not easy running Epik, right? You have to understand. Trying to thread the needle on what’s lawful free speech is not an easy task. The decision tonight to turn off Joey’s site [the doxxing site] is not a light decision.

Epik apparently raised a lot of dough this year

Monster says the company raised $32 million from a billionaire in June of this year.

I think the Swastika guy interaction has been taken out of context

Finally, I’d be remiss if I didn’t defend Monster on one thing. I saw some chatter on Twitter about a guy with a Swastika showing up to the meeting, and Monster saying, “Much love to you.” If you read the totality of the conversation, it’s clear that Monster doesn’t approve of this person’s actions and rhetoric.

Post link: Takeaways from the Epik hack call

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Pennsylvania Attorney General subpoenas Epik over Gab.com domain name
  2. Epik CEO Rob Monster statement on 8chan
  3. Masterbucks and tax avoidance at center of Epik PayPal controversy
Categories: Domains

SC Johnson terminates remaining dot-brand top level domains

Domain Name Wire - Mon, 09/20/2021 - 16:32

SC Johnson turns .off its new top level domains.

Consumer products company SC Johnson has told ICANN it wishes to terminate the remainder of its dot-brand top level domain names.

Last year, the company terminated its agreement for the .rightathome top level domain. Now, it has informed ICANN that it wishes to terminate .glade, .scjohnson, .afamilycompany, .off, .raid and .duck.

Glade is a brand name for air freshener, Off is an insect repellent, Raid is an insect killer, and Duck is a cleaning product.

It does not appear that SC Johnson used any of the top level domain names.

Given the generic nature of some of the strings, it’s possible that another company might be interested in picking up the mantle and would likely pay SC Johnson to do so. But that might not be worth the company’s effort.

Post link: SC Johnson terminates remaining dot-brand top level domains

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. What Makes a Top Level Domain Successful?
  2. Radix to generate $12 million revenue in 2017
  3. Frank Schilling will try to liquidate his 23 top level domain names in a single day
Categories: Domains

Epik breach: credit card woes, Whois data

Domain Name Wire - Mon, 09/20/2021 - 16:15

Credit card exposure from breach could have a major impact on customers.

Credit card data, which apparently includes CVV data, was exposed in the Epik breach.

I’ve been writing a lot about the Epik security breach, and you can expect to hear a lot more in the coming weeks as more details come out.

Yesterday, I published an email from Epik stating that it might be worth taking precautionary measures with credit card data. If you’ve ever bought anything online, this isn’t the end of the world. Numbers get stolen all of the time, even from the biggest retailers. But in Epik’s case, it appears that the company was storing CVV codes as well, which is a big no-no. These are the three and four-digit codes that are usually on the back of the card that are used for verification. Merchants are supposed to only use it for authorization and not store the number.

The other big news is that a bunch of scraped Whois records of non-customers were included in the breach. I have a couple of thoughts about this.

First, you should understand the history of Epik. The company entered the domain registrar business with the acquisition of Intrust Domains in 2011. Intrust was notorious for spamming people to sell them expiring domains. And, although Epik told me at the time that it didn’t acquire the email marketing part of Intrust, Epik itself was known for trying to sell domains via unsolicited email. (In a public video chat about the hack, Epik CEO Rob Monster confirmed that the early code base it acquired from Intrust was built on “shitty Russian code”, and that some of it is still in production.)

So it’s no surprise that the company has lots of Whois data. In fact, I wonder if it has a lot more than what was breached. Last year, Epik’s VP of Communications threatened people who were saying bad things about Epik by writing, “I am one of few individuals on this planet with the capacity to email 300 million people in fifteen seconds, with a full media agency and PR firm behind me.” I have no idea where that email data he referred to comes from and where it is stored.

Is the exposed Whois data a big deal? Yes and no. On the one hand, all of this data was public and probably scraped by plenty of spammers. On the other hand, this data can easily be used to spam people now. And certainly, people are going to be upset that their data was re-exposed by a company they’ve never heard of, so it’s going to be another large headache for the domain registrar as it works through recovering from the hack.

 

Post link: Epik breach: credit card woes, Whois data

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Masterbucks and tax avoidance at center of Epik PayPal controversy
  2. Hackers claim significant Epik breach
  3. Epik hack: what we know & what you should do
Categories: Domains

Selling more geo domains – DNW Podcast #355

Domain Name Wire - Mon, 09/20/2021 - 15:30

Can SquadHelp crack the geo domain sales code?

Can SquadHelp crack the code to help you sell more geo domains? On today’s show, SquadHelp CEO Darpan Munjal discusses the company’s plans to help you sell more domains like LosAngelesSiding.com and AustinAllergists.com. We also get an update on lots of new features that should help you sell your domains.

Also: An Epik hack, “keeping” domains, record-breaking sale, and more

Sponsor: Dan.com API Partner Program

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

Post link: Selling more geo domains – DNW Podcast #355

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Sell more domains with a crowd – DNW Podcast #294
  2. Newer domain investors find success – DNW Podcast #321
  3. DNS using blockchain technology – DNW Podcast #341
Categories: Domains

Epik sends hack notice, warns on credit cards

Domain Name Wire - Sun, 09/19/2021 - 14:04

Registrar says payment card information may have been compromised.

An anonymous group said it has hacked domain name registrar Epik and downloaded significant data.

Late Saturday night, domain name registrar Epik sent an email to customers confirming the hack that was widely reported last week. This comes after one official email communication from the company, as well as a few blog and Twitter responses and a multi-hour live online meeting that included arguments with a doxxing victim and an appearance by a neo-Nazi.

The email warns customers to take precautions and suggests that customers consider contacting their credit card companies to warn them that their credit card information may have been compromised. The full email is below:

Hello,

We are contacting you to notify you of an urgent security notice. Despite the extensive security practices we use to protect our platforms and customer information, we have confirmed an unauthorized intrusion into some of our domain-related systems.

We have mobilized the full force of multiple cyber security teams to assess the scope of this intrusion. We are taking aggressive action to completely secure and remediate all potentially affected systems, while complying with all applicable laws. As we work to confirm all related details, we are taking an approach toward maximum caution and urging customers to remain alert for any unusual activity they may observe regarding their information used for our services – this may include payment information including credit card numbers, registered names, usernames, emails, and passwords.

At this time, we have not confirmed that your card information has been compromised. As a precautionary measure, you may choose to contact any credit card companies that you used to transact with Epik and notify them of a potential data compromise to discuss your options with them directly. Should you observe any unauthorized activity, please document and report it immediately.

We are notifying you because we consider your privacy and security our single greatest priority. Our mission to provide legendary service to all customers remains unchanged. We appreciate your support as we work through the full resolution of this situation, and we will continue to provide you with ongoing updates as we learn more.

Thank you,

Epik Security Team

Post link: Epik sends hack notice, warns on credit cards

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Epik hack: what we know & what you should do
  2. Epik continues to bash GoDaddy. GoDaddy says this is why it dropped Epik
  3. Hackers claim significant Epik breach
Categories: Domains

.ORG Impact Awards draw record number of nominations

Domain Name Wire - Fri, 09/17/2021 - 17:14

PIR receives over 600 nominations for this year’s awards.

Public Interest Registry (PIR) received a record number of nominations for this year’s .ORG Impact Awards, the organization announced this week.

633 organizations applied for the awards, and this week the list was narrowed to 35 finalist organizations. Winners will be announced at an online event on November 9, 2021.

The 2021 awards include a winner in each of these categories:

  • Health and Healing in a Period of Pandemic
  • Overcoming Climate Change
  • Championing Diversity, Equity and Inclusion
  • Fighting Hunger and Poverty
  • Providing Quality Education for All
  • Building Better Communities
  • .ORG Rising Stars (recognizes someone under 25 years old)
  • .ORG of the Year

The .ORG of the Year will take home $35,000, while all other winners will receive $10,000.

Post link: .ORG Impact Awards draw record number of nominations

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. .Org generated $95 million revenue last year
  2. .Org wholesale price to increase to $8.25
  3. ICANN says it “does not have authority” over .org transaction
Categories: Domains

Does TenCent’s adoption of .中国 (IDN China) domains foreshadow a boom?

Domain Name Wire - Fri, 09/17/2021 - 15:50

TenCent just deployed a couple of Chinese IDN domains. Kassey Lee examines if this is a sign of things to come.

I was intrigued by the recent news of internet giant Tencent deploying two .中国 domains. Does it indicate a change in China and the start of a boom of launching Chinese websites complete with Chinese IDN domains?

Long time reader Moris alerted me to the recent news (in Chinese) that 腾讯.中国 (Tencent.china) and QQ.中国 (QQ.china) finally resolves after years of being inactive. The former forwards to Tencent.com and the latter to Tencent’s instant messaging platform QQ.com. The following domains were also mentioned but all of them (except 小度.中国) are used as domain forward only.

Domain Action Application 当当网电子书.中国 Forwards to DangDang.com General product portal 华大基因.中国 Forwards to BGI.com Genomic sequencing services 中国移动.中国 Forwards to ChinaMobile.com Telecom services 新華社.中国 Forwards to XinhuaNet.com News Beijing2022.中国 Forwards to Beijing2022.cn Beijing 2022 Winter Olympics 小度.中国 Active site Baidu’s Xiaodu brand smart accessories

I analyzed this extension back in July this year. After adding the latest 2020 data shown below, the picture still has not changed –- trending down after peaking at 1,895,745 domains in 2017.

The recent news made me wonder whether corporate China has started to favor the .中国 extension. Since internet companies are probably most sensitive to new trends, I decided to check the Top 100 Chinese Internet Companies listed in the “Research Report on the Comprehensive Strength of Chinese Internet Companies (2020)” (in Chinese) and see if the corresponding .中国 domains are actually in use. Here is the result.

Status Count Not resolve 86 Developed 2 Developed by 3rd parties 5 Forward 2 For sale 3 Expired 1 Parked 1

Only two .中国 domains are developed but the majority of them still do not resolve. For this reason, I don’t see any sign of a boom for .中国 domains coming soon.

On a side note, when checking a domain in your browser, be sure to test with and without the “www” prefix. Sometimes you may get a different result. For example, 滴滴.中国 (Didi.china) does not resolve with the “www” prefix added but displays contents without it.

Post link: Does TenCent’s adoption of .中国 (IDN China) domains foreshadow a boom?

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

Three auctions on tap for NamesCon next week

Domain Name Wire - Fri, 09/17/2021 - 13:36

NamesCon.online will have an auction for everyone next week.

Next week’s NamesCon.online event will feature three auctions, and pre-bidding is now open for the big RightOfTheDot Auction.

On Wednesday, September 22, get ready for the RapidFire live domain auction. Born on Clubhouse, this auction will feature names with no or low reserves.

The next day, Monte Cahn and RightOfTheDot will hold an auction. It will be conducted live from a studio with auctioneer Wayne Wheat and include 75-100 names. The company will follow up with an online auction for domains that didn’t meet reserves and other domains not included in the live auction. Pre-bidding is currently open for the auction.

Then on Friday, there will be an auction of Handshake domain names. This follows three days of programming in a Handshake track so people can learn more about these blockchain domains.

You can learn more about these auctions and what else to expect at the event in my interview with Soeren von Varchmin last week.

Post link: Three auctions on tap for NamesCon next week

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Domainer Personal Portfolio Auctions at Sedo
  2. Marchex’s Archeo auctioning off 71 domains in SnapNames auction
  3. .NYC and GreatDomains auctions end this week
Categories: Domains

Epik hack: what we know & what you should do

Domain Name Wire - Thu, 09/16/2021 - 20:10

What customers and other registrars should do to protect themselves until we know more.

Hackers have infiltrated Epik.

Domain name registrar Epik was hacked this week, and the hackers published reams of data online.

A group saying it’s aligned with the hacker collective Anonymous posted a release about the hack earlier this week. It says that the reason for the attack is that Epik caters to the far-right and extremist websites. After Epik seemed to waffle on whether there was a hack, the hackers made it public on Epik’s website itself.

The hackers published the data dump online, and security researchers are starting to comb through the data to see what was leaked.

Various sources have confirmed that the data includes registrant details behind many of the domains registered at Epik using Whois privacy. Both The Daily Dot and The Record have spoken with people whose data was released and confirmed that they were the registrants of the corresponding domain names.

A security engineer told The Daily Dot that the data includes the auth codes required to transfer domains to another registrar. It’s unclear if this data is tied to individual domains. This same engineer told The Daily Dot that the data includes WordPress admin passwords that people could use to take over Epik customers’ websites; I’m surprised by this because I wasn’t aware that these passwords were stored in any way that could be tied to a host.

The net-net is that we don’t know the full extent of the damage yet, but it looks bad.

This gets to how both Epik customers and other domain registrars can protect themselves and domain registrants.

At this point, Epik customers should hope for the best but plan for the worst. They should work on the assumption that their passwords have been exposed. If you re-use passwords at other sites (which you shouldn’t), you should change them to something unique. For safety’s sake, Epik customers should also assume that people have what’s needed to initiate a registrar transfer. With this in mind, I recommend domain owners use a system that tracks domain changes. DomainIQ and DomainTools offer trackers for this.

I’ve heard from some people trying to delete their Epik accounts. I don’t think this will help at this point; the data is already leaked.

Registrars should keep their eyes open for unusual transfer-in requests from Epik. I imagine some Epik customers are transferring their domains right now, but registrars should monitor this to ensure they aren’t being stolen.

Post link: Epik hack: what we know & what you should do

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. A strong month for .com; here are the winners & losers
  2. Epik continues to bash GoDaddy. GoDaddy says this is why it dropped Epik
  3. Hackers claim significant Epik breach
Categories: Domains

From Matador to Public.com and a $1.2 billion valuation

Domain Name Wire - Thu, 09/16/2021 - 19:28

This company built credibility with a great domain name.

In 1952, just 4.2% of Americans were company shareholders. By 1990, that figure had risen to 21.1%, and by 2020, 55% of the population had invested money in the stock market.

As time and technology move on, stock trading becomes more accessible to more of the population. Many entrepreneurs have noticed this and have created products that capitalize on this popularity and accessibility. Companies such as Robinhood have been runaway successes with its “Investing for Everyone” tagline and an app that offers on-the-go access to stocks and funds.

A Robinhood rival that caught my eye this week is Public.com, an app that combines social networking with public stock investing. It announced an undisclosed Secondary Market investment recently.

Founded in 2018, Public.com started life as Matador, offering a social trading app, an earlier edition of the Public.com app currently available.

Matador, operating on MatadorApp.com, attracted early funding, including a $2 million Seed round and a $6.5 million Series A round. However, it seems that Matador wasn’t content with its name. In August 2019, the company performed a major rebrand that included an ultra-premium domain acquisition.

Matador became Public.com and naturally started to use the Public.com domain name instead of MatadorApp.com.

The Public.com domain was acquired from Anything.com Ltd., an investment company that owns a stunning set of premium domains, including VR.com, Design.com, and Borrow.com. Anything.com Ltd. has also sold its fair share of names, including Teams.com, Home.com, and Marketing.com.

It’s unclear whether Matador purchased Public.com outright or whether this was a lease-to-own acquisition. Representatives of Anything.com did not confirm details of the purchase at the time of publishing. However, WHOIS history suggests that this may have been acquired using a purchase plan; between August 2019 and mid-2021, the registrant of Public.com is listed as the “Attorney Trust Account” of Ari Goldberger of ESQWire.

Post rebrand, Public.com successfully unlocks access to the stock market by offering fractional share ownership for a more inclusive trading experience.

Public.com’s concept has been a hit with customers. A Medium post details Public.com’s journey to attracting more than 1 million members within 18 months. This growth hasn’t gone unnoticed in the venture capital world, with Public.com attracting $308.5 million in funding to date, including a $220 million Series D round in February 2021. This moved Public.com into unicorn territory, with the round moving the company’s valuation up to $1.2 billion.

Among Public.com’s investors are actor Will Smith and legendary skateboarder Tony Hawk.

Despite Public.com’s business revolving predominantly around its app, it invested a significant sum of money in the Public.com domain name. Why?

There are dozens of reasons why a premium domain name makes sense for a financial services company, but I think trust may be one of the biggest.

Public.com’s product is not built for an experienced financial trader or tech-savvy investors. It is being pitched to the general public as an introduction to the stock market. Trusting a company to take your money and, in exchange, allow you to easily buy company shares is something that many people will be hesitant to do. Especially a relatively new company that seemingly only exists in the form of an app.

Owning Public.com allows the company to present as a highly professional, trusted business that exudes longevity. You don’t get the same effect if you’re asking a mass market to trust MatadorApp.com with your portfolio of stocks.

Post link: From Matador to Public.com and a $1.2 billion valuation

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

No related posts.

Categories: Domains

UDRP “not designed as a remedy for poor management”

Domain Name Wire - Thu, 09/16/2021 - 15:51

You shouldn’t file a UDRP just because you’ve lost the keys to your domain name.

Moana Pacific condos lost the keys to its domain and tried to get them back through UDRP. This screenshot is of the site in 2016, courtesy of Wayback Machine. The site currently resolves to a parked page.

Companies try to shoehorn many domain name issues into UDRP, which was created to handle clear-cut cybersquatting cases. A recent example is a dispute over a Hawaiian condo website.

Association of Apartment Owners of Moana Pacific filed a UDRP to try to get control of moanapacific .org, a website that has been used by the condo association in the past. As recounted in the complaint, the association hasn’t done a good job of managing access to the domain name:

The Complainant explains that the Domain Name was registered by its “former general manager”, the Respondent Mr. Allman, and then by another “employee” and “successor manager”, Eric Lau (who was initially named as the Respondent in this proceeding). According to the Complaint, “Complainant has been locked out of the domain account and unable to access many of its important documents and emails. Complainant has attempted to work with Respondent and Eric Lau but both either forgotten [sic] the information, have been uncooperative, unresponsive, and/or claims they do not have the information to assist.” Mr. Lau said in an email that he provided the login information to “Jerrie” when he left employment with the Complainant, but the Complainant has not found that helpful.

In other words, the association hasn’t done a good job of managing the keys to its domain name. Now it’s locked out, the domain is parked, and the condo association turned to the UDRP to try to recover access to the domain.

It’s clear that the domain was never registered in bad faith, so UDRP is not an appropriate way to get the domain. Panelist W. Scott Blackmer summed this up:

The Complainant may well wish it had insisted on keeping the login credentials and updating the registration details, but the facts here do not support a conclusion of bad faith, especially going back to the time of the original registration. The Policy was not designed as a remedy for poor management.

Post link: UDRP “not designed as a remedy for poor management”

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Google loses dispute with oogle.com owner
  2. Disgraced lobbyist Jack Abramoff loses domain name fight with Democrats
  3. UDRP: Joking .com was stolen
Categories: Domains

Swetha strikes again: Quest.xyz sells for record-breaking $70k

Domain Name Wire - Thu, 09/16/2021 - 15:17

Domain investor sets a new record for a non-numeric .xyz domain sale.

Domain name investor Swetha Yenugula had another incredible week with .xyz domain name sales, including selling quest.xyz for $69,888. This is the most ever paid for a non-numeric .xyz domain name, at least that has been publicly reported and captured at NameBio.

She also sold optics.xyz for $19,888 and common.xyz for $14,888.

@xyz sales this week.https://t.co/OEC0OUPHx9 sold for $69888 @Afternichttps://t.co/YFpGBp2yjF sold for $19888 @Afternichttps://t.co/CFomB12jaz sold for $14888 @Undeveloped https://t.co/2HtsD0pG8g sold for $7888 @afternic https://t.co/KFmc3Xp60c sold for $2995 @GoDaddy

— DNGear.com (@DomainNameGear) September 16, 2021

This follows last week’s sales of Flip.xyz for $27,888 and three domains for $19,888 each: Guild.xyz, Loot.xyz and Creator.xyz.

It’s worth noting that Swetha owns a huge portfolio of .xyz domains with nearly 20,000. Still, she was profitably on her portfolio back in April of this year when her tops sales seemed to be in the four figures. So her recent uptick has made it even more profitable.

Post link: Swetha strikes again: Quest.xyz sells for record-breaking $70k

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Frank Schilling and XYZ to sell .car, cars and .auto registries
  2. XYZ wins .car/.cars/.auto auction
  3. S.club sells for $38k, leading .Club domain name auction
Categories: Domains

Three recent numeric domain sales and possible Chinese meanings

Domain Name Wire - Thu, 09/16/2021 - 13:16

Here are some possible uses for these recent NNNN domain sales.

When reading recent domain sales recently, I came across three interesting numeric domains ending with either 98 or 99, which are familiar to Chinese consumers as having the meanings of “being rich for a long time” or “for a long long time,” respectively.

The three domains are 2698 .com (sold for $18,656 on September 1 at GoDaddy), 8499 .com ($82,000 on September 6 at GoDaddy), and 9599 .com ($10,099 on July 16 at Sedo), according to Namebio.

2698 .com rhymes with An Lu Jiu Fa (安路久发 = safe road of being rich forever) and Er Lou Jiu Ba (二楼酒吧 = drinking bar at second floor), which can be used for investment and drink services respectively.

8499 .com rhymes with Ban Shi Jiu Jiu (办事舅舅 = the uncle who handles work) and Ba Shi Jiu Jiu (霸世久久 = lord over the world for a long long time), which can be used for business services and general fields, respectively.

9599 .com rhymes with Jiu Wu Jiu Jiu (酒屋99 = wine house No. 99) and Jiu Wo Jiu Jiu (酒窝舅舅 = the uncle with a dimple), which can be used for wine services and general fields respectively.

Unlike longer numeric domains that are mostly traded among investors, 4N .com domains are actually used by end users in China, such as 4399.com (games) and 2345.com (info portal). I like their solid foundation.

To get an idea of other rhymes, see my guides to numeric domain rhyming 0-4 and 5-9.

Post link: Three recent numeric domain sales and possible Chinese meanings

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Two facts to know before investing in long numeric domains
  2. Direct visits driving demand for domains in China
  3. Single letter domains in China
Categories: Domains

Newfold releases $1.1 million worth of domain sales data

Domain Name Wire - Wed, 09/15/2021 - 20:23

Data include sales from July and August.

Newfold Digital released two months’ sales data from its aftermarket platforms today. The data include domains that sold for $2,000 or more on NameJet and SnapNames during July and August.

All told, the report includes 200 domains for a total of $1.1 million.

The top sales were BestShop.com for $81,610, Turret.com for $38,000 and KJS.com for $36,668.

I’ve taken a break from buying expiring domains, but had I been buying this summer, here are ones I probably would have bid on at the final price:

Hamachi.com $9,638 – this is a common sushi name.

SonicBoom.com $9,149 – solid brandable name with a “big” connotation.

GulfofMexico.com $4,600 – it’s a big area but I think there’s a good tourism play here.

Seascapes.com 3,369 – not sure if I would have paid this much, but it works well as an exact match for selling paintings and a brandable for ocean-related products.

NetworkArchitects.com $3,123 – Great name in a high dollar field.

WinningStrategy.com $3,001 – Leadership/coaching/strategy domains like this do well on the aftermarket.

FlightInsurance.com $3,000 – I think most people buy this through their airline but what a steal of a price.

Here’s the full list of sales:

Domain NameBrandTypeSales Amount bestshop.comNamejetExpiring81610 turret.comNamejetExpiring38000 kjs.comSnapNamesDeleting36668 torus.comSnapNamesExpiring28500 naturalgourmetinstitute.comNamejetExpiring26500 medjobs.comSnapNamesExpiring20144 alga.comNamejetDeleting17500 cruiseinsurance.comSnapNamesExpiring17099 navtech.comSnapNamesDeleting15100 weiser.comSnapNamesExpiring14142 mpeg.comSnapNamesExpiring12600 intercambio.comNamejetExpiring12516 hisa.comSnapNamesExpiring11569 loveshop.comSnapNamesExpiring11120 dowa.comSnapNamesExpiring10502 richfield.comNamejetExpiring10111 renato.comNamejetExpiring10004 vetty.comNamejetExpiring10000 bowmar.comNamejetBrokerage and Escrow9999 spotlite.comSnapNamesDeleting9688 hamachi.comSnapNamesDeleting9638 supercool.comNamejetDeleting9551 pelishouse.comSnapNamesDeleting9506 pridco.comSnapNamesExpiring9504 sonicboom.comSnapNamesDeleting9149 hris.comSnapNamesExpiring8801 fictionwise.comSnapNamesDeleting8752 snapguide.comNamejetDeleting8300 trevo.comSnapNamesDeleting8086 gonet.comSnapNamesExpiring8014 connexis.comSnapNamesExpiring8005 naughty.netNamejetDirect Lister8000 efunding.comSnapNamesDeleting7850 masterlink.comSnapNamesExpiring7251 getphysical.comNamejetExpiring7250 thedance.comSnapNamesDeleting7166 axela.comSnapNamesDeleting7102 apartmentlocators.comNamejetExpiring7025 makeup.netNamejetDeleting6916 mytraining.comSnapNamesDeleting6806 greenchain.comSnapNamesDeleting6789 conformity.comSnapNamesDeleting6750 victoriapark.comNamejetExpiring6579 droneservices.comSnapNamesExpiring6543 iam.netSnapNamesExpiring6501 coocoo.comNamejetExpiring6339 cargoone.comSnapNamesExpiring6020 huga.comNamejetDirect Lister6000 hiredevelopers.comSnapNamesExpiring5860 vanson.comNamejetExpiring5813 kineto.comSnapNamesExpiring5800 playthegame.comSnapNamesExpiring5750 bitcoinanalytics.comNamejetDeleting5555 zeven.comSnapNamesExpiring5283 abpnews.comSnapNamesExpiring5250 saez.comSnapNamesDeleting5004 dinance.comNamejetBrokerage and Escrow5000 takeshots.comSnapNamesExpiring4975 noten.comNamejetDeleting4900 bodymachine.comNamejetExpiring4892 allsense.comNamejetBrokerage and Escrow4888 mikekelly.comSnapNamesExpiring4730 truetv.comSnapNamesExpiring4706 nette.comSnapNamesExpiring4621 carfleet.comSnapNamesExpiring4616 greenvillehomes.comSnapNamesDeleting4600 gulfofmexico.comNamejetExpiring4600 thisnation.comNamejetExpiring4551 rapscallion.comSnapNamesExpiring4464 vanishingpoint.comNamejetExpiring4422 cypher.ioNamejetDeleting4401 bzxhw.comSnapNamesDeleting4400 adpower.comSnapNamesExpiring4256 openborder.comSnapNamesExpiring4200 modeo.comSnapNamesExpiring4113 mocha.ioNamejetDeleting4105 sanfelipe.comNamejetDeleting4100 lift.orgNamejetExpiring4088 stiffy.comNamejetExpiry4000 paratek.comSnapNamesExpiring4000 mingweb.comSnapNamesExpiring3895 blackpaint.comSnapNamesDeleting3856 wallco.comNamejetExpiring3755 stes.comNamejetExpiring3722 flowsystems.comSnapNamesDeleting3710 purplebet.comSnapNamesExpiring3701 globaldesk.comNamejetExpiring3700 wwdev.comSnapNamesExpiring3695 banchan.comSnapNamesDeleting3679 thing.ioNamejetDeleting3666 elpresidente.comSnapNamesDeleting3660 sportspage.comSnapNamesExpiring3659 schoko.comSnapNamesDeleting3655 forkful.comNamejetDeleting3643 appkit.comSnapNamesDeleting3600 poboys.comNamejetExpiring3600 importparts.comSnapNamesExpiring3576 ajtech.comSnapNamesExpiring3538 blackglama.comNamejetExpiring3500 networkled.comSnapNamesExpiring3495 honestrentals.comSnapNamesExpiring3488 dachi.comNamejetExpiring3438 axonis.comSnapNamesExpiring3433 cheddar.ioSnapNamesDeleting3433 promore.comSnapNamesExpiring3413 thelens.comNamejetDeleting3411 seascapes.comSnapNamesExpiring3369 pahealth.comSnapNamesExpiring3315 youeye.comSnapNamesDeleting3300 discoveringmontana.comSnapNamesExpiring3280 londa.comSnapNamesExpiring3227 subscribermail.comSnapNamesExpiring3226 avica.comSnapNamesExpiring3205 antarcticconnection.comNamejetExpiring3160 networkarchitects.comSnapNamesExpiring3123 colachurch.comSnapNamesExpiring3121 hacking.ioSnapNamesDeleting3101 codup.comSnapNamesDeleting3100 mobilepixels.comSnapNamesExpiring3088 thothub.tvSnapNamesDeleting3032 winningstrategy.comNamejetExpiring3001 americandefensemanufacturing.comNamejetExpiring3000 saxons.comNamejetExpiring3000 flightinsurance.comSnapNamesExpiring3000 harborfeight.comNamejetDirect Lister2999 mightymen.comNamejetExpiring2997 bsyl.comSnapNamesDeleting2940 skysys.comNamejetDeleting2915 kidsfood.comNamejetExpiring2912 datarack.comSnapNamesDeleting2901 mafin.comSnapNamesDeleting2900 bestrentals.comNamejetExpiring2900 feedmag.comNamejetExpiring2850 financialone.comSnapNamesDeleting2815 lmao.netSnapNamesExpiring2801 cyberage.comNamejetDeleting2730 kocina.comSnapNamesExpiring2723 thehelpdesk.comNamejetExpiring2714 bookabed.comNamejetDeleting2702 ilj.orgNamejetExpiring2700 bobwhite.comSnapNamesExpiring2700 yuezhan.comSnapNamesDeleting2679 riem.comNamejetExpiring2660 bikethesites.comNamejetExpiring2606 meanies.comNamejetExpiring2601 nnff.comNamejetExpiring2600 seobot.comSnapNamesDeleting2600 me.vipNamejetExpiry2600 artsbeat.comSnapNamesBrokerage and Escrow2575 solarsales.comNamejetExpiring2562 investmentmanagers.comNamejetExpiring2562 wrays.comSnapNamesExpiring2514 deerrun.comNamejetBrokerage and Escrow2499 superbest.comNamejetDeleting2460 unisky.comSnapNamesExpiring2454 towncourier.comNamejetDeleting2437 newelement.comSnapNamesDeleting2411 beefcattle.comNamejetExpiring2405 navegador.comNamejetDeleting2402 bounceinc.comSnapNamesExpiring2400 cyan.ioSnapNamesDeleting2361 catsdogs.comNamejetExpiring2336 debtbusters.comSnapNamesExpiring2300 dj365.comSnapNamesDeleting2290 ourcellar.comSnapNamesBrokerage and Escrow2288 stoneground.comNamejetExpiring2270 mypf.comNamejetDeleting2257 hayy.comNamejetDirect Lister2250 maurus.comSnapNamesDeleting2250 fanex.comSnapNamesExpiring2218 eshop.netNamejetDeleting2200 emangetdough.comSnapNamesExpiring2195 lighthouseworld.comSnapNamesExpiring2188 davidhooper.comNamejetExpiring2161 coinbrowser.comSnapNamesDeleting2155 krtech.comSnapNamesDeleting2155 servicecare.comSnapNamesExpiring2150 nelsoninsurance.comSnapNamesExpiring2127 jantar.comNamejetExpiry2122 kidk.comSnapNamesExpiring2103 rvx.orgNamejetExpiring2101 lemonlaws.comSnapNamesExpiring2100 iyurveda.comSnapNamesExpiring2095 sensorstick.comSnapNamesBrokerage and Escrow2088 wetten24.comSnapNamesDeleting2070 polyworld.comSnapNamesExpiring2059 flawlessapp.ioSnapNamesDeleting2058 animae.comNamejetDeleting2052 emptypockets.comSnapNamesExpiring2051 lonestarsteakhouse.comNamejetExpiring2050 hausboote.comSnapNamesDeleting2050 unicarriers.comSnapNamesBrokerage and Escrow2050 visitmacysusa.comNamejetExpiring2050 vehiclehire.comSnapNamesExpiring2050 rytech.comSnapNamesDeleting2049 sustainablesecurity.orgSnapNamesExpiring2037 history.ioNamejetDeleting2021 chelseanow.comNamejetExpiring2000 choosephilippines.comNamejetExpiring2000 pingduhospital.comSnapNamesDeleting2000

Post link: Newfold releases $1.1 million worth of domain sales data

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Here’s what sold on NameJet and SnapNames last month
  2. Shills, Insiders, & Front Runners – 5 Bidding Scandals
  3. Web.com aftermarkets generated $500k in big sales last month
Categories: Domains

Keeping a domain in bad faith? How about RDNH?

Domain Name Wire - Wed, 09/15/2021 - 16:53

A new Turkish car company tries a novel argument.

Turkey’s car brand Togg tried reverse domain name hijacking. Photo from Togg.com.tr.

A World Intellectual Property Organization panelist has found Türkiye’nin Otomobili Girişim Grubu Sanayi Ve Ticaret Anonim Şirketi guilty of reverse domain name hijacking in a dispute over togg.com.

The Complainant plans to sell Turkey’s first domestically-produced automobile. It was formed in 2018 and registered the country code domain togg.com.tr for its business.

It wants togg.com, but of course, that was registered a long time ago. Perhaps realizing the dates were not in its favor, the Complainant made a rather novel argument that the domain owner “keeps” the domain in bad faith.

Attorney John Berryhill, representing the domain owner (who uses the domain, by the way), was incredulous. In his response, he wrote:

…Not a single place in the entire Complaint, does the Complainant come right out and say that the domain name was registered after the mark was announced. The Complaint does not say that, because the Complainant knew, when it filed the Complaint, it would be a false statement. The only other place where the Complainant attempts to make a bad faith reigstration allegation is at page 14 where the Complainant alleges:

“It is likely that the Respondent keeps the disputed domain name in bad faith in an aim to obtain unfair benefits from the high reputation of the TOGG Trademark which created a tremendous impression due to the great launch.”

Keeps? The Respondent “keeps” the disputed domain name in bad faith? What is that nonsense supposed to mean under the Policy? Again, the Policy requires the Complainant to show that the domain name was registered in bad faith and was used in bad faith. But the allegation here, along with the empty chest-thumping about a “great launch” of no products whatsoever so far, is purely intended to mislead the reader. It is not a violation of the Policy to “keep” a domain name which has been used for the same business for 18 years. The Complainant knew it had to use the word “keeps” instead of “registered”, because the Complainant knows this case was filed as a bad faith attempt to steal a legitimately registered and used senior name.

The Complainant later tried to withdraw the complaint, but the Respondent said it would only agree if the Complainant agreed not to file another UDRP against the domain or pursue it via judicial means. Apparently, the car company did not agree, so panelist Matthew Kennedy decided the case in the Respondent’s favor and found reverse domain name hijacking.

Gün + Partners represented the Complainant.

Post link: Keeping a domain in bad faith? How about RDNH?

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. City of Paris ordered to pay $100k for reverse domain name hijacking
  2. Turkish restaurant chain guilty of Reverse Domain Name Hijacking
  3. Wirecard nailed for Reverse Domain Name Hijacking
Categories: Domains

24 end user domain name sales including a big .xyz

Domain Name Wire - Wed, 09/15/2021 - 13:22

An ecommerce company, a blockchain company and a law firm bought domain names.

Sedo had a strong week for end user domain sales, led by a company that just raised $6.7 million using some of the money to upgrade its domain name.

Here’s a list of end user domain name sales that just completed at Sedo. You can view previous lists like this here.

Homesome.com $59,999 – Homesome, Inc. helps grocery stores with their ecommerce businesses. It just raised a $6.7 million series A and upgraded its domain from GetHomesome.com.

Flip.xyz $27,888 – This is one of Swetha Yenugula’s recent sales. The buyer is a DeFi/blockchain company.

iRaffle.com $25,000 and Prize.co $5,000 – Both of these domains forward to Raffle.com.au, a site that operates charitable raffles in Australia. Prize.co seems like a bargain.

Nfund.com €15,000 – N Fund is a venture capital fund.

Datawords.cn €8,000 – Datawords is an international digital marketing firm. It forwards the .cn domain to its website at Datawords.com.

Donda.org $7,995 – Shadowserve is an IT company in the UK, so this is probably for a client.

NotGuilty.law $5,800 – This domain forwards to a website for Rose Law.

CryptoIsland.com $5,500 – If I understand this correctly, this will be some sort of cryptocurrency deal in a metaverse…but with a physical location. The business uses the domain CryptoIsland.group.

ClanWars.com $5,000 – Clan Wars is a Multiplayer Online Battle Arena (MOBA) game.

Evonomy.com $5,000 – Evonomy offers technical & commercial services for vehicle, system, component, and semiconductor solutions.

AirConditioningOnline.com $4,000 – Airconditioning-Online, an Australian air conditioner seller, uses the domain airconditioning-online.com.au

HTV.ca $3,500 – According to the skeleton site on the domain now, this stands for “Heat Transfer Vinyl”

Lamellendach.com $3,499 – VIL Bausysteme GmbH sells outdoor patios and sun rooms. This domain translates as louvered roof in German.

BinaryCortex.com $3,110 – I can’t find any information about BinaryCortex LLC, which bought the domain.

FVbank.com $2,999 – FV Bank in Puerto Rico uses the domain FVbank.us.

Streamline.ch $2,990 – Voice communications and IT company Streamline AG uses the domain StreamlineAG.ch.

Wordell.com $2,611  – Wordell is a marketing agency.

Yuicery.ch €2,600 – Yuicery is a restaurant chain with most of its locations in Germany. It uses the domain Yuicery.de but also owns the matching .com.

25×25.com €2,500 – 25×25, an initiative to increase the number of women CEOs in UK businesses, uses the domain 25×25.uk.

VaultChip.com €2,500 – Based on trademark applications, it appears that Sparx Novate LLC is involved with electronic health records, vaccine passports, and similar medical data information transfer.

SofabedStore.com $2,500 – SETS Group LLC is a furniture importer in New Jersey.

Solver.ch €2,250 – Tax consulting firm Solver Advisory uses the domain name solver-advisory.ch.

Kamur.com $2,200 – Ka-Mur Beverages Limited in Egypt bought this domain.

Post link: 24 end user domain name sales including a big .xyz

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. 15 end user domain name sales
  2. 21 more end user domain name sales
  3. What domain names Cox Media, Steinway and other end users bought last week
Categories: Domains

Dan.com says new follow up system results in 9% better conversions

Domain Name Wire - Tue, 09/14/2021 - 19:07

Domain sales platform continues to iterate on payments, checkout and more.

Dan.com published details about many improvements to its domain selling system today. While some of the updates may seem like small details, they show the company’s emphasis on faster payments and closing more deals.

For example, the company says it has introduced more and better payment reminders and updated the follow-up process with buyers, resulting in 9% better conversions.

On the payments front, Dan.com says bank wires are now handled 1.5 hours faster than before. It’s also integrating with Payoneer to send payments locally, meaning there will be no intermediary bank fee and a 2-hour payout delivery. The company says that for 90% of payouts, 2 hours after Dan has verified the payout, the money will be in your account.

The company has also improved SEO for for-sale pages and implemented a system to customize individual domain listings.

More details are available at Dan.com.

Post link: Dan.com says new follow up system results in 9% better conversions

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Undeveloped rebrands to DAN.com, uses blockchain for transfers
  2. DAN.com enhances domain financing options
  3. Efty teams up with Dan.com, also introducing marketplace
Categories: Domains

Hackers claim significant Epik breach

Domain Name Wire - Tue, 09/14/2021 - 17:36

A group claims that it has hacked Epik and downloaded significant data.

An anonymous group said it has hacked domain name registrar Epik and downloaded significant data.

A group says it has hacked domain name registrar Epik and released a trove of data online.

A posting (see PDF version) claims that the hackers gained access to data about all domain purchases, transfers, all Whois history (unredacted), all email forwards, account credentials for customers, internal systems, and a lot more.

I have not independently verified the veracity of the claims, nor reviewed the large file the hackers released. I reached out to Epik CEO Rob Monster this morning to ask for a comment but did not immediately hear back. At the time of publishing, Epik has not posted anything to its blog, news page, or official twitter account regarding the apparent incident.

However, Monster responded to one of the people who tweeted about the hack yesterday, linking to a domain registered at Epik that says negative things about the person who posted the link. The tweet states, “Chad – I know that you are keen to get a client of Epik to take down a damning URL that does not reveal your highest self. I try hard to give everyone the benefit of the doubt but your latest tactic needs to stop right now.”

It’s unclear if Monster is suggesting that the person had anything to do with the hack, and the tweet doesn’t deny that Epik was hacked.

The apparent hack appears to be in response to Epik being a favored registrar for far-right sites. The hack notice states:

NOTORIOUS “HACKERS ON ESTRADIOL” PRESENT GRAND REVEAL OF ROB “HITLER SHOULD’VE WON” MONSTER’S EPIK FAILURE

You know, when you name a company “Epik”,
that implies something really big’s going to happen.
Deserving of the name.
Well, after years of bolstering the worst trash the Internet has to offer,
this is, truly, the Epik moment we’ve all been waiting for.

It also mentions recent efforts to take down an anti-abortion website.

Epik came under fire this month when a Texas anti-abortion group moved its “whistleblower” domain name to Epik after GoDaddy asked it to leave. Epik quickly shut the site down too. Epik said the site, which asked people to submit information about people in Texas getting abortions, violated its terms and asked the group to remove the content.

On Tuesday evening, Rob Monster responded: “We are assessing and don’t have any evidence of any domains compromised. Our team has been diligently assessing the claims and proactively securing systems.”

On Wednesday, September 15, Epik C”EO Rob Monster sent this message to customers:

At Epik, we take security and the privacy of your information very seriously. Therefore as a precautionary measure, I am writing to inform you of an alleged security incident involving Epik.

Our internal team, working with external experts, have been working diligently to address the situation. We are taking proactive steps to resolve the issue. We will update you on our progress. In the meantime please let us know if you detect any unusual account activity. I am proud of our team’s efforts as we do our part to empower a thriving internet for the benefit of our customers around the world.

You are in our prayers today. We are grateful for your support and prayer. When situations arise where individuals might not have honorable intentions, I pray for them. I believe that what the enemy intends for evil, God invariably transforms into good.

Blessings to you all.

 

Post link: Hackers claim significant Epik breach

© DomainNameWire.com 2021. 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 editor (at) domainnamewire.com. Latest domain news at DNW.com: Domain Name Wire.

Related posts:
  1. Epik CEO Rob Monster statement on 8chan
  2. PayPal drops Epik, sparking registrar to cry it is being “deplatformed”
  3. Masterbucks and tax avoidance at center of Epik PayPal controversy
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.