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.

Gesab, S.A. tries to reverse domain name hijack DeskWall.com

Domain Name Wire - Tue, 08/21/2018 - 19:29

Panelist says Complainant knew or (should have known) that it couldn’t prove registration and use in bad faith.

Gesab, S.A., a company in Barcelona that sells a product called DeskWall, has been found to have engaged in reverse domain name hijacking by filing a cybersquatting complaint against the domain name DeskWall.com.

The company first tried to by the domain name for $500. The owner requested $6,399.

In the World Intellectual Property Decision, the panelist notes that the “Complainant argues that the fact that Respondent registered the disputed domain name before Complainant’s trademark registration should not sway the Panel’s analysis considering Respondent’s business strategy.”

Well, that is a requirement of UDRP that can’t be ignored. It’s difficult to argue that the domain was registered in bad faith to target a company when that company didn’t have rights when the domain was registered.

The panelist noted:

…In the Panel’s opinion, Complainant knew or at least should have known that it could not prove registration and use in bad faith. As explained earlier, however, Complainant came nowhere near building a case for this essential UDRP element. Complainant should have known that its failure to even allege a senior right in the DESKWALL mark was likely to prove fatal to its prospects in this proceeding.

2. Furthermore, before launching this case, Complainant contacted Respondent and offered to buy the disputed domain name for USD 500, without offering any arguments that it possessed a legal claim relating to the disputed domain name. In the Panel’s view, this is another example of a case where a party, frustrated in its attempt to buy a domain name, resorts to the ultimate option of an artificial claim untethered to facts or the plain wording of the UDRP.

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

Related posts:
  1. Insurance company Allianz tries reverse domain name hijacking a domain name
  2. Miray Software AG nailed for reverse domain name hijacking
  3. Crypto World Journal tries to reverse domain name hijack CWJ.com
Categories: Domains

Domain investors should keep their WHOIS public

Domain Name Wire - Tue, 08/21/2018 - 15:59

There are many benefits to keeping your Whois information public.

GDPR has been in effect for a few months now and the impact on the domain name industry has been huge. The biggest impact is with Whois; many major domain name registrars are now masking all Whois data.

There are some benefits to this, including reduced spam and telemarketing calls. But domain name owners should probably do what’s necessary to keep their Whois information public. Here’s why:

1. Fewer UDRP/legal actions

A consequence of masked Whois is that companies that consider filing a UDRP or legal action no longer know who they’re filing against. WIPO has changed its process so that it informs the Complainant about who the owner is and then lets the complainant amend their complaint.

There are some problems with this. One is that if it’s obvious that you have rights or legitimate interests in the domain name (e.g. it matches your last name), the Complainant might ordinarily not file the complaint. But once they file, will they actually decide at this point to withdraw the complaint?

This is less of an issue for domain investors than smaller domain owners/businesses. But for domain investors, this still creates a problem. Owning a domain as an investment can establish a legitimate interest in a domain name.

A Complainant might think twice when seeing who owns a domain name. For example, a smart Complainant will carefully consider its options if it knows a domain is registered by Frank Schilling’s company. They know he will fight back (even beyond UDRP if necessary). I have no doubt that some companies decide not to pursue a case because he owns the domain.

Also, keep in mind that some registrars don’t even have masked email forwarding addresses in Whois. If there’s an issue that can easily be cleared up through communication prior to getting to a UDRP or lawsuit, there’s simply no way for the other party to contact you.

2. More sales contacts

Domain purchase inquiries come from various sources: parked page landers, marketplaces, and Whois. Most of the large sales and purchases I make start with an email or phone contact.

3. A clear, public ownership record

Public Whois also creates a public record of domain name ownership that can be valuable in disputes.

How you can make your Whois public

There are two ways to make your Whois public.

One is to choose a domain name registrar that still publishes Whois info for non-EU residents. The biggest example is GoDaddy.

The second is to ask your registrar to make your Whois information public. The ICANN temporary Whois specification requires registrars to make this an option “as soon as commercially reasonable”. I’m not sure how difficult this is, but I would push your domain registrar if they deny your request.

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

Related posts:
  1. Domain thoughts: Purple.com, GoDaddy, fast transfer and GDPR
  2. I just fixed Whois and GDPR
  3. June’s top DNW stories
Categories: Domains

New TLD Economics with Colin Campbell – DNW Podcast #198

Domain Name Wire - Mon, 08/20/2018 - 15:30

Digging into .Club’s revenue and the economics of new TLDs.

New top level domain name company .Club landed on the 2018 Inc 5000. The Inc 5000 list shows that it had revenue of $7.2 million but I had lots of questions. Is this “real” revenue? Is the company profitable? This week we go straight to the source with .Club founder and CEO Colin Campbell. He explains the numbers, historical revenue and what he predicts for the future. It’s an eye-opening and unprecedented look into a private new TLD company.

Also: Other domain companies on the Inc 5000, trolling the NRA, Dreamhost, Dave Evanson’s big sale, Dynadot milestone and cruising with Hexonet.

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

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

Related posts:
  1. Ray King on Marketing Domain Names – DNW Podcast #99
  2. Chris Sheridan – DNW Podcast #115
  3. Frank Schilling explains price hike – DNW Podcast #127
Categories: Domains

66 companies in Inc 5000 use domain names for their company name

Domain Name Wire - Mon, 08/20/2018 - 13:44

These 66 fast-growing companies use a domain name for their company name.

A handful of domain name companies made this year’s Inc 5000 list.

Additionally, I noticed that some great domain names were the names of a few of the top companies, including Scientist.com at #9 and Calm.com at #19. So I decided to search the entire list of 5,000 companies to see which companies used a domain name as their company name. I found 66 if you include .Club domains.

57 of the domain names are .com domain names and 9 are non-.com, including 3 .io domains and 2 .co domains.

Here’s the full list of companies on the 2018 Inc 5000 that have a domain name company name.

RankNameCategory2017 Rev 9Scientist.comHealth$50.3m 19Calm.comConsumer Products & Services$22.3m 247Squadhelp.comBusiness Products & Services$2.5m 274Lob.comBusiness Products & Services$18.3m 286FitSmallBusiness.comBusiness Products & Services$3.0m 351HealthCare.comInsurance$26.2m 382Reverb.comRetail$23.9m 416ChromebookParts.comComputer Hardware$5.4m 458Signs.comBusiness Products & Services$14.8m 564BoldLeads.comAdvertising & Marketing$12.4m 578MzeroA.comEducation$3.2m 633RealEstateInvestor.comReal Estate$4.0m 763iHeartDogs.comRetail$17.9m 896Forever.comSoftware$5.2m 920BuybackBoss.comConsumer Products & Services$3.1m 1009KitchenSearch.comConstruction$2.9m 1138LensDirect.comHealth$5.7m 1204GlassesUSA.comRetail$45.5m 1425gosite.comSoftware$2.4m 1458WagPantry.comRetail$2.0m 1789Cabinets.comRetail$27.7m 1862DoHardMoney.comReal Estate$5.4m 2028taldepot.comRetail$26.2m 2041FreeAlliance.comGovernment Services$9.4m 2139BrandYourself.comSoftware$6.1m 2140AustinRealEstate.comReal Estate$4.1m 2196Travlu.comTravel & Hospitality$4.8m 2417TargetX.comAdvertising & Marketing$17.1m 2485Freerateupdate.comAdvertising & Marketing$17.3m 2725RedAwning.comTravel & Hospitality$11.8m 2744Jane.comRetail$147.3m 2761MarketBeat.comMedia$3.5m 2808BrandNex.comAdvertising & Marketing$4.2m 3258heartsmart.comHealth$22.6m 3327StickerGiant.comBusiness Products & Services$12.6m 3438E-file.comConsumer Products & Services$5.1m 3479TrafficSafetyStore.comRetail$16.2m 3701Environmentallights.comRetail$29.7m 3724HireAHelper.comConsumer Products & Services$6.9m 3754ULTIMOVALUE.COMConsumer Products & Services$28.1m 3870MyJobHelper.comBusiness Products & Services$10.0m 3880UpSellit.comBusiness Products & Services$6.1m 3896Confirmation.comFinancial Services$29.6m 3941DrugTestsInBulk.comHealth$11.3m 3991Tigerchef.comConsumer Products & Services$10.6m 4077SmarterChaos.comAdvertising & Marketing$4.1m 4105ShedsForLessDirect.comRetail$12.9m 41461SEO.com Digital AgencyAdvertising & Marketing$7.3m 4275powersolution.comIT Management$2.1m 4452ClassicCars.comRetail$3.6m 4455Foundation Software / Payroll4Construction.comSoftware$34.0m 4595SolidSurface.comRetail$2.7m 4706ODUrent.comReal Estate$6.5m 4802GiftBasketsOverseas.comFood & Beverage$5.6m 4914MerryStockings.comConsumer Products & Services$2.0m 4937WriterAccess.comSoftware$6.9m 4964ShoppersChoice.comRetail$96.4m 206Discuss.ioSoftware$4.4m 412Clutch.coBusiness Products & Services$5.2m 858Rankings.ioAdvertising & Marketing$2.1m 1164.CLUB DomainsBusiness Products & Services$7.2m 1704540.coGovernment Services$6.5m 3139Rev.ioTelecommunications$6.5m 3202MyComputerCareer.eduEducation$33.9m 3213FORETHOUGHT.netTelecommunications$7.0m 3696CMP.jobsHuman Resources$5.1m

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

Related posts:
  1. .Club posts $7.2 million revenue, lands on Inc 5000
Categories: Domains

Living as a Digital Nomad for a month

Domain Name Wire - Fri, 08/17/2018 - 15:52

I hit the road this summer. Here are my takeaways.

A lot of people who read DNW have immense flexibility. They can live and work from wherever they want.

Both my wife and I own our own companies and can work from wherever we want, but it’s not something we’ve taken advantage of much. Having a kid means we need continuity in education, but there’s still summer break that we can take advantage of. Despite this, I think the longest time I’ve been away from home in the past decade is just a couple of weeks.

This summer we decided to try something different. We spent an entire month in Seattle and worked while there.

The benefits are obvious. One day this was my office:

The view from our campsite in Olympic National Forest.

But there are challenges, too. Here are some of the challenges I faced.

1. Separating work time from fun time.

Since we weren’t true digital nomads on the road for good, a large portion of our time was spent doing vacation things. I generally worked for a few hours in the morning and then relaxed in the afternoon. Separating this time was tough, especially since I tend to write a lot of timely/breaking news. GoDaddy releases earnings? Gotta write about that, even if it’s in the afternoon.

Also, since Seattle is in the Pacific time zone, I felt behind every day when I woke up. Some days I would write a post and schedule it for early the next morning.

2. Working from my laptop.

All I technically need to work is my laptop and an internet connection. But I work best when I’m at my desk, docked into my dual monitors, keyboard and mouse:

It’s hard to replicate this on the road.

3. Recording podcasts on the road is difficult.

You’ll note that my workstation also has a good setup for recording podcasts. I have the mic on the left, a camera on top (when needed) and acoustic sound panels.

My wife is also a podcaster so we brought a mic with us. Still, it was hard to get good sound. While we were on Bainbridge Island we had birds in the background. While we were in Capitol Hill we had city noises to contend with.

There are a few things I would do differently next time regarding podcasts.

First, I’d try to record as many “evergreen” podcast interviews as possible in advance. I can then record the intro and news part while on the road.

Second, I’d hit up people who live/work in the area to use their equipment/space.

Third, I’d consider renting professional studio space. In fact, I came across this sign one afternoon:

A sign for a podcast studio in Seattle that rents by the hour.

4. Overcoming feelings of guilt.

If I’m only working a few hours a day, am I neglecting something important? Should I do more? For example, I posted only two of my website builder reviews and didn’t get around to completing the others yet.

This was a constant struggle for me. If I travel like this again next summer, I’ll double down in the weeks leading up to my travel by pre-writing as much evergreen content as possible.

Of course, we weren’t true digital nomads on our trip. We returned to our home. It was more like an extended working vacation. But the definition of digital nomad is expanding; you can think of it as just the flexibility to work from wherever you want.

As I mentioned at the top, there are lots of DNW readers who enjoy this flexibility. It’s one of the perks of doing what we do.

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

No related posts.

Categories: Domains

Vancouver Hexonet Cruise sets sail on August 23

Domain Name Wire - Thu, 08/16/2018 - 18:08

Great networking opportunity next week in Vancouver.

If you live in the Pacific Northwest or need an excuse for a last minute trip to Vancouver, British Columbia, get ready for Hexonet’s cruise on August 23.

The domain name registrar has teamed up with a lot of sponsors for its annual evening cruise, networking and educational event. Afilias, Amazon Registry, Donuts, .ME, NamesCon, PIR, Weebly, and .Asia are sponsoring the event.

The evening cruise takes off in Coal Harbour at 5:30 next Thursday and concludes at 9 pm.

Tickets are CAN $20, and all proceeds go to British Columbia Children’s Hospital Foundation. Hexonet will match all funds raised.

The high temperature in Vancouver next Thursday is forecasted to be 73 degrees, so this should give you an incentive to make the trip. (Unfortunately, I won’t be able to make it due to a scheduling conflict.)

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

No related posts.

Categories: Domains

Betsy Riot punks NRA Lobbyist’s wife with domain name

Domain Name Wire - Thu, 08/16/2018 - 15:04

Group creates website juxtaposing NRA’s advocacy and successfully defends domain name in cybersquatting complaint.

Above: A picture from Ivy-Lane-Living.com

Betsy Riot, a group that has railed against the National Rifle Association, has won a dispute brought by Courtney Cox, who is married to the NRA’s chief lobbyist and principal political strategist, Chris Cox.

Courtney Cox runs an interior design company called Ivy Lane Living. Betsy Riot registered the domain name Ivy-Lane-Living.com and created a parody site juxtaposing her business with the National Rifle Association. You can see the parody/criticism site here.

Cox filed a cybersquatting complaint against the domain name, but Betsy Riot has prevailed in a decision handed down by World Intellectual Property Organization (WIPO).

In a nutshell, the WIPO panelist determined that this wasn’t a case of cybersquatting and qualifies as free speech and a criticism site.

The group behind the website also owns waynelapierre.com, which is the name of the National Rifle Association’s Executive Vice President.

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

Related posts:
  1. St. Louis bank sues to take over gripe domains
  2. PCO.com saved in UDRP despite no-show by domain owner
  3. Vulfpeck band member tries reverse domain name hijacking
Categories: Domains

16 end user domain sales: a big bank, custom bong maker and more

Domain Name Wire - Thu, 08/16/2018 - 13:33

A Fortune 500 bank, politician, and custom bong maker bought domain names last week.

Sedo’s top sale last week was Christian.com for $600,000 but we don’t know if it was an end user or investor yet. I did, however, uncover 16 domains that are end user sales, and there are surely more. One is a company that uses .co that bought the matching .com. Another is a new ecommerce logistics company that went with .co as it matches the company’s full name. And another is a bank that might be rebranding or starting a new brand.

Let’s take a look at some of the end user sales at Sedo over the past week:

(Want to see more lists like this?)

LineDance.com $11,500 – Line Dance is a movie, TV show and ranch.

Munite.com €9,900 – Public Financial Management, which provides financial consulting to governments and endowments, filed an intent-to-use trademark application for Munite in July. It will be for “Providing an on-line, searchable database of information about municipal bond issuers organized by obligor and specific industry sector or group.”

Commerce.co €9,000 – Commerce Co sources and ships products. If you’re interested in this stuff, you might want to review my podcast about Amazon FBA.

IconBank.com €7,000 – Is Bancorp South (NYSE:BXS), a Fortune 500 company, going to rebrand? It bought this domain name.

EZPlay.com $7,000 – I’m not sure why Integrated Solutions International LLC, a business automation company, wants a domain name that sounds like a lottery or gambling site.

Heka.in $5,500 – Livpure Smart Homes Pvt Ltd. It’s not clear what it will do with Heka.in.

RepublicCrypto.com $5,000 – The domain now forwards to Republic.co, a cryptocurrency service.

TerraEvents.com $5,000 – +39 Events is an events company in Italy.

Quant.ai $4,999 – Quant AI is a patent analytics/data company in the Seattle area.

EnGuard.com £4,900 – ENTRVST provides HIPAA-complaint email and cloud services to health groups. Its name and existing domain name fail the radio test miserably, and Entrust.com is used by another company so that probably isn’t an option.

Gift.pro $4,000 – Gift Pro Ltd helps companies sell gift cards. Its domain is GiftPro.co.uk.

VoluMetrix.com €3,900 – Vascular monitoring company VoluMetrix bought this domain and forwards it to its main VoluMextrix.co domain.

CustomBongs.com $2,999 – Yep, it’s a seller of custom bongs.

MainStreetHotel.com $2,800 – The Graham Companies is a developer of Miami Lakes, Florida.

Abeos.de €2,500 – Abeos is a headhunter/recruiting service that uses the domain Abeos.nl.

BonnieWatsonColeman.com $2,500 – Bonnie Watson Coleman is running for Congress in New Jersey’s 12th district. Her campaign domain is BonnieForCongress.com.

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

Related posts:
  1. What domain names Mozilla and others bought last week
  2. What domain names Goldman Sachs and others bought this week
  3. More end user domain name sales
Categories: Domains

Namecheap hits $109.1 million revenue in 2017

Domain Name Wire - Wed, 08/15/2018 - 17:32

One of the largest domain name registrars crossed the 9 figure mark in 2017.

Domain name registrar Namecheap has been a big domain name registrar for a long time but didn’t always show up on top registrar lists because it was an Enom reseller.

Now that it has pulled most of its domains onto its own registrar accreditation, the company’s size has become apparent. It’s among the top five largest domain name registrars for .com domain names.

In 2015, Namecheap had revenue of $76 million and three-year growth of 117%. It fell off the Inc 5000 in 2017, but is back for the 2018 list. Its 2017 revenue was $109.1 million. That’s up 78% over three years, and up 44% from 2015.

According to the company’s Inc 5000 listing, it employees 950 people.

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

Related posts:
  1. Namecheap lands on Inc. 5000 with $76 million in revenue
  2. Rightside and NameCheap ink longer term deal
  3. Namecheap leaps up .com chart as PDR falls
Categories: Domains

.Club posts $7.2 million revenue, lands on Inc 5000

Domain Name Wire - Wed, 08/15/2018 - 17:25

Revenue more than quadrupled from 2014 to 2017.

New top level domain name registry .CLUB Domains has landed at #1164 on the newly released Inc 5000 for 2018. The list is ranked based on three-year revenue growth.

The company had $7.2 million revenue in 2017, up 419% over 3-years. It launched its domain name in early 2014.

This is the first look we’ve had at .Club’s financials in a while. .Club CEO Colin Campbell previously discussed the group’s 2015 financials with DomainName Wire. In that year it had about $7.0 million in bookings, but that excludes any sort of revenue recognition so it’s not necessarily comparable.

Whois API remained on the list for a second year, coming in at #651 with $2.7 million in revenue and 775% three-year growth. It will be interesting to see what happens with this company in the age of GDPR.

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

Related posts:
  1. .Club applicant seeks to raise up to $7 million
  2. In Da Club, 50 Cent, and New TLD marketing
  3. .Club has sold 2,000 premium domain name so far today
Categories: Domains

Gumwand Inc. files lawsuit to get Gumwand.com domain name

Domain Name Wire - Wed, 08/15/2018 - 15:25

Gum removal company continues to chase elusive domain name.

The company that makes the Gumwand is suing to get Gumwand.com. Photo from Gumwand.net

Gumwand Inc, a company that sells tools to remove gum from flooring and public spaces, has filed a lawsuit (pdf) in Federal District Court in Virginia to get the domain name Gumwand.com.

The company uses Gumwand.net and has been trying to get Gumwand.com for years. It originally sued the owner of Gumwand.com in 2015 in New York. The court issued a default judgment in 2017, demanding that the domain name be transferred to Gumwand Inc.

But Gumwand Inc. has had trouble getting the domain transferred. The original defendant has changed its name several times, according to the company.

It filed a case with National Arbitration Forum this summer. The Forum denied the complaint but the decision hasn’t been published yet.

So now Gumwand is doing what it probably should have done in the beginning: file a case in the Eastern District of Virginia, where .com registry Verisign is located. It filed an in rem case there on August 9. If the court enters a default judgment, it can order Verisign to transfer the domain name.

One thing perplexing about this case is that Gumwand.com was registered before Gumwand.net. It may be that the creator of the device announced the product without registering the domain name. It will be interesting to read the UDRP decision to see if it explains the order of events.

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

No related posts.

Categories: Domains

Christian.com domain name sells for $600,000 (again)

Domain Name Wire - Tue, 08/14/2018 - 17:14

Domain name sells for the exact same price that it sold for in 2009.

Sedo domain name broker Dave Evanson announced today that he brokered the sale of the Christian.com domain name for $600,000:

Just sold Christian(.)com for $600,000 @sedo!! Congrats to buyer and seller!!

— dave evanson (@SedoDaveEvanson) August 14, 2018

The domain name is in escrow at Sedo and the buyer’s identity hasn’t been revealed yet.

Christian.com sold for the exact same amount in 2009 when Boris Kreiman bought the domain name shortly after buying Call.com for $1.1 million. Kreiman told Domain Name Wire that he was going to create a Christian social network using the domain name.

The domain was about to be sold at the Rick Latona TRAFFIC auction in 2009, but the transaction went through Sedo. So this is the second time Sedo has had a hand in selling Christian.com.

After the 2009 deal, the domain was under Whois privacy until late 2015. At that time the domain Whois record changed to Avatar Invest Inc. in Russia.

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

Related posts:
  1. Why Envelopes.com acquired two more category-defining domain names
  2. Fashion.nyc domain name sells for $37,000, Shop.nyc sells for $33,500
  3. Great premium domain data from Radix
Categories: Domains

DreamHost enables export-to-WordPress for its Remixer website builder

Domain Name Wire - Tue, 08/14/2018 - 16:00

No lock-in with DreamHost’s site builder.

I’ve been reviewing non-WordPress website builders over the past month and have more reviews to come.

These site builders make it easier for non-techies to build websites than using WordPress. But there’s a big drawback: lock-in.

Each builder is proprietary and they are designed to limit the ability to export to a different platform and/or webhost. In return for an easy-to-use site builder, you agree to be locked in indefinitely with the service.

But hosting company DreamHost announced today that it is opening up its Remixer site builder. Customers that use Remixer to build a site can export it to WordPress on a Dreamhost shared hosting account. Even though the initial export is to a Dreamhost account, customers could then use the WordPress export feature if they wish to change hosting companies.

Being able to start designing a site in a simple site creator and then harness the customizability that WordPress offers seems like a big win.

DreamHost says that it is the first company to allow exporting from a standalone website builder to WordPress.

Although I haven’t tested Remixer yet, I will do so in the future.

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

No related posts.

Categories: Domains

Dynadot eclipses 1 million domain name milestone

Domain Name Wire - Mon, 08/13/2018 - 21:20

Domain name registrar hits key growth milestone.

Domain name registrar Dynadot has hit the one million domains under management milestone.

The company was founded in 2002 and became ICANN-accredited the following year. It didn’t hire its first employee until 2006. Since then, it has grown to four offices (San Mateo, CA, Beijing, Zhengzhou, Toronto).

Dynadot is also a 50% female company in an industry that is male-dominated.

Todd Han founded and bootstrapped the company. It hasn’t taken any outside investment or debt, and Han doesn’t plan to sell the company.

Listen to Han talk about the Dynadot story and what it’s like being a small-to-mid-sized registrar in DNW Podcast #141.

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

Related posts:
  1. Dynadot Recovers from Two Day Outtage
  2. Domain Security: Dynadot Offers Two-Factor Authentication
  3. Dynadot to host domain name meetup in San Francisco in July
Categories: Domains

Reverse domain name hijacking (even with no response)

Domain Name Wire - Mon, 08/13/2018 - 15:57

Panelist finds Mister Auto SAS filed complaint in abuse of policy despite domain name owner not responding.

A World Intellectual Property Organization panelist has found Mister Auto SAS in France guilty of reverse domain name hijacking for the domain name MisterAuto.com.

The decision by panelist John Swinson comes despite the domain name owner not responding in the case. Yet it was a fairly easy decision; the domain was registered well before the Complainant existed and the Complainant made no argument to address this.

It’s not surprising that Mister Auto wanted MisterAuto.com. It uses the hyphenated domain name Mister-Auto.com to sell auto parts. It sent a cease & desist letter to the domain name owner and never heard back.

Swinson summed up Mister Auto SAS’ action in filing the UDRP:

The Panel considers the Complainant launched the proceedings out of desperation as its prior attempt to contact the Respondent went unanswered (and the webpage did not resolve – revealing no clues as to the Respondent’s possible motives) but without a reasonable chance of success and as such in the circumstances constitutes an abuse of the Administrative Proceeding.

Mister Auto was represented by Cairn Legal in Belgium.

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

Related posts:
  1. Insurance company Allianz tries reverse domain name hijacking a domain name
  2. Miray Software AG nailed for reverse domain name hijacking
  3. Crypto World Journal tries to reverse domain name hijack CWJ.com
Categories: Domains

Top Domain Sales of the Year – DNW Podcast #197

Domain Name Wire - Mon, 08/13/2018 - 15:30

Reviewing the top domain names sales so far this year.

For this week’s special edition of the Domain Name Wire Podcast, I review the top 10 public domain name sales of the year as reported by DN Journal. It includes everything from Ice.com at the top to a discussion of cryptocurrency buyers and new top level domain name sales. We’ll be back next week with the regular podcast format — and if you have suggestions for guests, please let me know!

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

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

Related posts:
  1. 2017 Predictions – DNW Podcast #116
  2. Domain name due diligence – DNW Podcast #148
  3. Domain aftermarket update – DNW Podcast #151
Categories: Domains

How to be a guest on podcasts

Domain Name Wire - Mon, 08/13/2018 - 14:14

This step-by-step guide shows the process for marketing yourself through podcasts.

There are lots of interesting companies in the domain name space. There are also lots of Domain Name Wire readers who dabble in domain names yet have more intriguing businesses than just buying and selling domain names.

These companies and people should take advantage of podcasts to get the word out. Being a guest on a podcast is a lot like being a guest on a radio show but with several benefits

– The audiences are micro-targeted
– There’s a relevant podcast for every topic
– They aren’t live and can be edited before airing
– Because there are so many podcasts, it’s much easier to get booked as a guest on one

My PodcastGuests.com service now has over 5,000 users, many of whom have used the service to get booked on multiple podcasts.

If you need a little push to get over the hump and start being a guest on podcasts, I put together a handy guide that walks you through the process step-by-step. You can download it here.

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

Related posts:
  1. Participate in an upcoming DNW Podcast about China
  2. The latest on PodcastGuests.com
  3. Top Podcasts of 2016
Categories: Domains

Domain names around Seattle

Domain Name Wire - Fri, 08/10/2018 - 14:52

Here are some notable domain names I saw around Seattle over the past month.

I spent the past month in Seattle on my annual “escape the Texas heat” vacation. And while people up here have complained about the 80+ degree days, it’s much nicer than what Austin is experiencing right now.

During my visit, I came across a handful of domain names that caught my attention. Here are some of them:

Southport.life

My understanding is that Renton has typically been the working class and manufacturing part of Seattle. Renton has become more attractive for living and office space as the rest of the city has become insanely expensive.

That seems to be part of the idea behind Southport, a big development on the southern edge of Lake Washington. I walked through the beautiful new Hyatt Regency and came across a sign promoting Southport:

An ad for Southport in Seattle.

Southport.com is owned by Digimedia. Southport is trying to pitch a lifestyle, so I understand why it went with Southport.life for its marketing.

RFI.com

While walking to lunch one day I spotted RFI.com on the side of a van. I always like seeing companies put three letter domains to use.

RFI Communications & Security Systems is a West Coast commercial security system design company.

RFI is a commercial security company that uses RFI.com.

HillTopper.bike

Biking is a popular way to get around in Seattle but the hills can be an impediment.

This poster caught my attention for its use of a .bike domain name to promote a kit that adds motorized power to your bicycle:

An ad for HillTopper.bike

HillTopper.bike forwards to electric-bike-kit.com. I understand why they are promoting the .bike domain instead!

Jucy

I’ll finish with a perplexing non-domain. Take a look:

This van doesn’t have a domain name on it.

You see this type of promotion (to just Google the company name) a lot in Japan. But not in the States. It doesn’t make much sense to me why you’d send someone to Google rather than directly to your website.

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

No related posts.

Categories: Domains

Quantifying GoDaddy’s aftermarket

Domain Name Wire - Thu, 08/09/2018 - 15:33

GoDaddy’s aftermarket business continues to grow, and analysts need to understand how it works.

An analyst asked GoDaddy about its domain name aftermarket business on this week’s GoDaddy earnings conference call. GoDaddy credits increased aftermarket revenue for growing its topline domain name revenue and it’s important for analysts and shareholders to get an understanding of how the business works.

Aftermarket revenue is not like domain name registration revenue. Domain registration revenue is recognized over time and is recurring. If a registrar sells a domain for $12 this month, it will recognize $1 of revenue per month for the next year. More often than not, that domain will be renewed so the one registration continues to contribute to revenue for a long time.

But when GoDaddy sells a domain for $10,000, the best it can expect the next year is to get a standard renewal fee. It also recognizes the full amount upfront.

While aftermarket revenue is good revenue, analysts that are modeling GoDaddy’s business need to separate out what is recurring and what is not.

After the call, I contacted GoDaddy’s investor relations group to get clarity on GoDaddy’s answer provided during the conference call. Here’s the takeaway: the aftermarket business contributes mid-single digits to GoDaddy’s total revenue. Last quarter the company had revenue of $652 million, so if you assume about 4%-6%, that gives a number of about $25 million to $40 million in aftermarket revenue for the quarter.

GoDaddy’s domain revenue was $305 million, so roughly 10%-15% of domains revenue comes from the aftermarket.

The GoDaddy aftermarket has three main revenue sources:

1. Domains that GoDaddy has purchased for resale. Think Mike Berkens’ portfolio, Donuts’ portfolio, etc. that it has purchased and are now part of NameFind.

2. Expired domain names. This includes both domains expiring on GoDaddy’s platform as well as partners that send their inventory to GoDaddy.

3. Afternic and AfternicDLs sales.

The company counts revenue differently for each bucket depending on if it takes on the risk. Investor relations noted:

“[Domain aftermarket sales can be] recognized as either gross or net, depending on the set of circumstances with that partner. Each partner’s arrangement governs whether or not we take the risk of loss in the sale or we’re merely facilitating the sale. If we are placing any warranty/guarantee on the sale (assuming risk of loss) we’ll recognize the sale on a gross basis, scenarios where we’re facilitating the sale…we’ll record net.”

GoDaddy books the full amount of revenue if it sells a domain from its own portfolio. If it sells a domain investor’s domain through Afternic for $10,000, it only recognizes the $2,000 commission it earns.

Give GoDaddy credit for its smart approach to growing the aftermarket. As I mentioned earlier, Aftermarket revenue is good revenue, it’s just very different from what the company makes from domain registrations.

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

Related posts:
  1. GoDaddy is buying NamesCon
  2. GoDaddy (GDDY) reports earnings, domain revenue of $263.3 million
  3. GoDaddy adding more expired domain registrars, increasing European aftermarket presence
Categories: Domains

Tucows’ revenue drops on Namecheap transfers

Domain Name Wire - Thu, 08/09/2018 - 13:55

Bulk transfer during Q1 hits revenue at Tucows.

Domain name company Tucows (NASDAQ: TCX) reported second quarter 2018 earnings after the market closed yesterday.

Revenue fell 4% year-over-year to $81.1 million. This was not a surprise and it mostly relates to the bulk transfer of 2.65 million domain name to Namecheap. The Namecheap contract was low margin; the gross margin for the wholesale domain business fell by only $350,000.

Net income fell 31% year-over-year to $3.6 million, but Tucows’ adjusted EBITDA number posted an 8% gain to $11.2 million.

While Namecheap hurt the overall revenue from the domains business, its retail domain operation and portfolio business showed gains. Ting Mobile also showed growth.

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

Related posts:
  1. Tucows expects $20 million EBITDA/year from “opportunistic” eNom acquisition
  2. Tucows revenue jumps on Enom acquisition
  3. Court orders Tucows to transfer 3.2 million domains to Namecheap
Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.