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.

Gab.com is apparently on a payment plan. That should serve as a warning.

Domain Name Wire - Wed, 10/31/2018 - 13:27

Domain name appears to be on a payment plan at Escrow.com.

The valuable domain name Gab.com is in limbo. It is used for a ‘free speech’ social network and it seems that the Pittsburgh synagogue shooter was radicalized (in part) by using the service.

GoDaddy told the company to move its domain name elsewhere. A new Whois record shows that the owners transferred Gab.com to Uniregistry in the Cayman Islands. The Hot Potato is now in Frank Schilling’s hands.

But there’s something else notable on the Whois record for Gab.com. In order to transfer it, GoDaddy’s proxy service had to be removed. Note the address and email address in the public Whois:

That’s the address for Escrow.com and the email address used when a domain name is sold in a payment plan.

In other words, it looks like the $220,000 sale on Flippa wasn’t paid up front.

The domain is damaged now that it has been used for a controversial purpose. If Gab.com stops making payments on the domain (which is possible given that their payment processors and hosts have pulled the plug), it might be harder to sell the domain again.

Whenever you lease a domain or sell it on a payment plan, you need to set terms on how it can be used. While typical clauses prevent using it for spam or adult content, you might want to look further than that.

© 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

Lawsuit filed to recover EQN.com domain name

Domain Name Wire - Tue, 10/30/2018 - 19:16

Domain was stolen in 2016, according to lawsuit.

A California company has filed a lawsuit (pdf) to recover the domain name EQN.com, which it says was stolen from its Enom account.

Blackshore Properties, Inc. of San Marino, California acquired EQN.com in a NameJet auction in 2011 for $4,950.

According to DomainTools historical Whois records, the domain name was transferred to a Chinese registrant at domain registrar 22.cn between May 5, 2016 and September 23, 2016. The lawsuit alleges that this transfer was theft.

The suit was filed in U.S. District Court in Virginia where .com registry Verisign is located. Assuming no one shows up to defend the in rem lawsuit, the just will likely enter an order of default judgment and order Verisign to transfer the domain name.

© 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. Lawsuit filed to recover stolen OnlineMBA.com domain name
  2. Lawsuit filed to recover 6213.com, an allegedly stolen domain name
  3. Former SNN.com owner goes to court to recover domain name
Categories: Domains

The economics of “forever” domain registrations

Domain Name Wire - Tue, 10/30/2018 - 18:02

Should the domain name industry introduce perpetual domain registrations?

Consumers like predictability. They dislike price increases on their cable bill, healthcare premiums and mortgage.

Companies like cash in the bank. They can do a lot with it: invest, buy back shares, etc.

So the idea of a “forever” domain registration in which one payment is made and you own the domain for life could appeal to an end user. It also appeals to the domain industry because it can use the cash and not have to worry about renewals.

Last week at the ICANN meeting in Barcelona, Epik founder Rob Monster explained to me what he’s trying to do with the concept of perpetual domain registrations. He’s offering these registrations on Epik for $420. Think of it as a proof of concept to show there’s demand for such a product.

What really needs to happen for domain registrars and registries to start offering a product like this is for the entire supply chain to be on board. The registry must offer a one-time price and ICANN must as well. Would ICANN accept a one-time $10 payment to cover all future fees it charges for domain registrations? Would Verisign accept a one-time $200 payment to renew a .com domain in perpetuity?

Epik’s Forever registrations

As it stands right now, Epik’s forever registration starts with a 10-year registration, the maximum allowed by the registries. After considering the registry fee and ICANN fees, this leaves Epik with $326 in working capital. It then renews the domain for another year each year.

Depending on what rate you consider your cost of capital, this gives Epik a lot of room. Monster figures that as long as the renewal price of a .com is $19.50 or less per year, the .com is self-financing into perpetuity without even tapping into the $326 “deposit”.

But what will the market be like in 10, 20 or 30 years? There’s a lot of uncertainty. Domains as we know them have ony been around for about 30 years.

Let’s say the NTIA agrees to let Verisign increase prices 5% a year starting next year. Assume ICANN does the same on its fees. It will still take nearly 20 years for the wholesale price of .com to top 20. 100 years from now the wholesale would be around $950 per year.

Epik’s terms of service give the company an out, albeit one that is friendly to registrants. Epik can cancel the registration at any time as long as it refunds 100% of the purchase price. It’s smart to have this exit clause given how much the market could change over time.

A panacea for domain companies and registrants?

I like the concept of perpetual registrations but I believe the entire industry needs to get on board. This is Monster’s goal. Prove demand to get people talking.

Public domain companies recognize revenue over time. So selling a perpetual registration for $420 today doesn’t let them recognize $420 in revenue. They’d have to recognize it over time…a long time.

But they can still invest the upfront cash and not have to worry about domain renewals. So it would be nice.

Will many consumers bite, though?

After all, people can already register domains for a decade at a time but few people do that. Consider the most recent Verisign registration report from June.

In June, there were 2,828,662 new .com registrations. 89% were for only one year. Fewer than 10,000 were for eight years or more.

6,525,072 .coms were renewed that month. Again, fewer than 10,000 were renewed for eight or more years.

To be fair, consumers might not see the advantage of paying in advance since .com prices have been steady for many years now. Also, it’s a 10-year registration, not lifetime. But there’s still a benefit to long registrations; you’re less likely to let a domain lapse.

Despite this, consider that many Fortune 500 companies only renew their primary domain one year at a time. Fedex.com expires next month!

It’s worth a conversation

I think it’s worth having a conversation about perpetual domain registrations. In order for it to go mainstream, all players in the supply chain must be contractually involved.

At a minimum, it might be time to talk about extending the 10-year maximum for registering and renewing domains.

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

No related posts.

Categories: Domains

Group discusses Dot-Brand domains in Barcelona

Domain Name Wire - Tue, 10/30/2018 - 15:00

Angie Graves reports on the Brand Registry Group meeting in Barcelona last week.

Cole Quinn (Microsoft) comments during the Brand Registry Group meeting in Barcelona October 25. Photo courtesy Martin Sutton/Brand Registry Group.

What better way to break up the monotony of dry ICANN policy sessions than a gathering with speakers addressing real-world practices and marketplace challenges?

On October 25, the Brand Registry Group (BRG) hosted a seven-hour program for BRG members, brand registrants and consultants, presenting case studies, histories, timelines, and opportunities. Along with the BRG, and cooperation from the Domain Name Association, sponsors of the event were Neustar, Authentic Web, Lemarit, SafeBrands, Valideus, and Afilias.

The goal was to share education and increase awareness of .brands, and the value of the BRG, which was formed in 2013 by a number of companies who saw benefit in collaborating in the dot-brand TLD space.

Judging from the questions posed during the session, people are interested in understanding best practices for use of existing new gTLDs, potential timelines for the next round of new gTLD registrations, and challenges in managing corporate gTLD and domain name portfolios.

The program covered territory useful to registrants of unused brand TLDs, as well as to companies and their advisors considering applying in the next round. Those who made bold moves explained lessons learned, as well as potential landmines and ways to avoid them. The format was a mix of presentations, panels,  discussions, and question-and-answer periods.

BRG President Cole Quinn from Microsoft kicked off the event by sharing his experience as the manager of Microsoft’s domain name portfolio, and how the BRG inspired him in his role, provided access to expertise for Microsoft TLDs, and gave him the language needed to effectively communicate the value proposition of gTLDs with division leadership teams within Microsoft. Quinn explained how Microsoft runs its corporate domain portfolio and gave a sneak peek into its tool showing workflows and automation.

Participants asked what defines “success”, as well as the challenges in communicating internal successes, especially for the benefit of the ICANN community and Brands community, who are both making decisions about the future of the new gTLD program. They acknowledged that community perception is mixed on the question of the success of the first round of new gTLD registrations.

A look back at the first round of brand gTLD registrations led to a discussion of lessons learned, an analysis of the ways consultants and applicants approached the program, hurdles that were overcome, and challenges that became apparent during the process.

A snapshot of the current state of the .brand TLD space was presented, along with details of hurdles that are yet to be overcome, and examples of helpful sites dedicated to tracking progress in the space.

Other presenters shared details of their experiences as managers of their own corporate registries, including Cecilia Smith of 21st Century Fox, Kevin Audritt from HSBC, Google’s Ben McIlwain, and Kate Kahle from CERN. Sharing not only their experiences so far, but their ideas and plans for development going forward, interest from the attendees was apparent, with each presentation generating additional questions about details.

The session concluded with an in-depth look into needs identified for a success in the next round, and Jeff Neuman presented an estimated timeline and the work needed to be done within the ICANN community before the next round can be launched. Best case scenario for the next round of applications? Late 2021.

© 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. New TLDs this week: .Fashion, .Garden and .FRL
  2. How much it costs to run a domain name registry
  3. Local Popularity & Global Influence: Nations and nTLDs
Categories: Domains

Valuable three-letter .Com domains stolen

Domain Name Wire - Tue, 10/30/2018 - 12:29

NNN.com, Wok.com among domains man claims were stolen.

A Japanese man alleges that valuable domain names were stolen from his registrar account and transferred to another registrar. These aren’t run-of-the-mill three-letter domains, either. Among the domains he says are stolen include nnn.com and wok.com.

Yoshiki Okada filed (pdf) the in rem action in U.S. Federal District Court in Virginia where the .com registry Verisign is located. Okada claims that eol.com, fde.com, jol.com, nnn.com, olp.com, tang.com, wok.com, wtv.com, and zhang.com were stolen from him.

It’s unlikely that the alleged thief will show up to represent himself in Virginia. In most cases, the judge in this type of lawsuit will accept a default judgment and order Verisign to transfer the domains. The exception is when a stolen domain has been re-sold, in which case the buyer might try to defend the domain name.

 

© 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. 8 Clues a Domain Name is Stolen
  2. Company sues over stolen domains after losing UDRP
  3. Lawsuit filed to recover stolen domains: 5678.com, 26266.com and Manhua.com
Categories: Domains

U.S. Government follows up on “cooling off period” idea for ICANN employees

Domain Name Wire - Mon, 10/29/2018 - 20:28

NTIA chief wants ICANN to restrict post-ICANN employment.

Following up on remarks made during ICANN 63 in Barcelona last week, National Telecommunications and Information Administration (NTIA) head David Redl sent a letter to ICANN Friday criticizing people leaving the regulator for industry companies.

Redl first mentioned the concern publicly last week in comments during the meeting. His interest in the subject presumably stems from Donuts hiring Akram Atallah as its new CEO. Atallah led the Global Domains Division at ICANN.

Here’s the text of Redl’s letter to ICANN:

NTIA continues to be a strong supporter of the multistakeholder approach to Internet Governance, including through our participation as the U.S. representative to the Governmental Advisory Committee (GAC) at the Internet Corporation for Assigned Names and Numbers (ICANN). Paramount to the success of the multistakeholder approach is trust in the institutions that make decisions about the Internet’s future. While the community has greatly improved ICANN’s accountability through the IANA stewardship transition process, I am writing to raise a concern about an accountability deficit at ICANN.

Recent ICANN senior staff departures have highlighted that ICANN lacks postemployment restrictions. Given that ICANN, through the enforcement of its contracts with domain name registries and registrars, performs an industry self-regulatory function, it is necessary that conflicts of interest or appearance of unethical behavior be minimized. While the United States will recommend this issue be addressed in the third iteration of ICANN’s Accountability and Transparency Review Team (ATRT3), which we expect to have had its initial meeting no later than June 2019, I encourage you to look into this now. One potential fix could be “cooling off periods” for ICANN employees that accept employment with companies involved in ICANN activities and programs. This is an ethical way to ensure that conflicts of interest or appearances of unethical behavior are minimized.

One challenge I foresee is that ICANN sometimes hires people from the industry because of their specialized knowledge. It might be difficult to attract these people if they can’t return to industry companies. ICANN would need to compensate them for the restriction. I also wonder if employment laws in various states and countries would limit the ability to enforce cooling off provisions.

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

Related posts:
  1. ICANN board resuscitates .Hospital top level domain name
  2. Court denies Donuts’ request to delay .web auction
  3. Donuts demands $22.5 million for .Web domain name
Categories: Domains

Alphabet registers more Waymo domains as it makes progress on self-driving taxis

Domain Name Wire - Mon, 10/29/2018 - 16:58

Alphabet subsidiary Waymo registers domains in preparation for expanded service.

That’s me next to a Driverless car from Google (Waymo). The Waymo taxis on the road look different.

Self-driving taxis are getting closer to reality.

Alphabet (NASDAQ:GOOGL) has begun testing fares for beta users of its Waymo taxi service. In conjunction with the news about its progress, Waymo registered a handful of domain names:

waymo1.com
waymobayarea.com
waymodaily.com
waymoearlyrider.com
waymoearlyriders.com
waymofleetsupport.com
waymolidar.com
waymolidars.com
waymonext.com
waymoone.com
waymophoenix.com
waymoriders.com
waymoridersupport.com
waymosensor.com
waymosensors.com
waymosupport.com
waymotoday.com

Waymo is primarily testing its service in Phoenix. Early Rider is the name of its beta program that has hundreds of users.

As the company expands its self-driving taxi service to more cities and more riders, domains like WaymoSupport.com are smart defensive 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. Google’s Waymo domain strategy and what it says about domain choices
  2. Google, ABC.xyz, and the growing awareness of new domain names
  3. 2015’s Top 5: Google now part of Alphabet, uses abc.xyz
Categories: Domains

Country Code Domains – DNW Podcast #208

Domain Name Wire - Mon, 10/29/2018 - 15:30

Two guests shed light on ccTLDs.

.Com is king in much of the world, but not in Europe. In many European countries, the country code domain name (ccTLD) is used more often than .com. On today’s show, I talk to two people who live and breathe ccTLDs. First, I talk with Peter Van Roste, who is the General Manager of CENTR, a group that helps European ccTLD managers. We then chat with Jakob Truelsen, the CEO of DK Hostmaster, which manages Denmark’s .DK domain name. Truelsen explains how the group was able to cut down on websites using .DK domains to sell counterfeit goods without wading into the murky area of reviewing content.

Also: Verisign sells security to Neustar, Google tries something new with .New, .AI expired domains, a big domain auction, Zoom.com and much more.

Subscribe via iTunes to listen to the Domain Name Wire podcast on your iPhone or iPad, view on Google Play Music, or click play above 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. Frank Schilling explains price hike – DNW Podcast #127
  2. How to Sell More Domains with Adam Strong – DNW Podcast #158
  3. Reviewing this year’s predictions – DNW Podcast #161
Categories: Domains

Google Adsense now requires site verification

Domain Name Wire - Mon, 10/29/2018 - 14:11

In a throwback, sites must be validated before showing Google Adsense ads.

Sites must be verified before Adsense shows ads like in the image above. Photo courtesy Google.

Google is now verifying websites before they can use Adsense to monetize content.

In a blog post today, the company said that the process will review sites for compliance with the Adsense Program policies.

There are a lot of policies for Adsense, but I wonder if this change is in part to make sure Adsense ads don’t show up on sites racist or hateful content, or content that incites violence. This has been a hot topic lately after the radicalization of people carrying out acts such as sending pipe bombs and mass shootings.

The verification will also verify that users can own the domain or can modify its content.

Longtime Adsense users won’t find this too burdensome. In the old days, all sites have to be reviewed before they were accepted to show Adsense ads.

© 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. Google Now Targeting Ads to Users, Not Just Content
  2. Adsense as a Platform and What it Means for Publishers
  3. Domain Parking Coming to .Tel
Categories: Domains

GoDaddy tells Gab.com to find a different domain registrar

Domain Name Wire - Mon, 10/29/2018 - 13:50

Registrar tells the controversial social network to take a hike.

A notice that Gab.com says it received from GoDaddy.

Domain name registrar GoDaddy (NYSE:GDDY) has informed Gab.com that it needs to move its domain name to a different company. This is according to a tweet from the controversial social network, which posted the email notice from GoDaddy (pictured).

Gab.com has come under fire after it surfaced that the Pittsburgh synagogue shooter was active on the site. The social network is known for letting anything be published and has become popular with racists and for hate speech.

Other companies pulling the plug on Gab.com include PayPal, Stripe and its hosting providers.

GoDaddy tries to avoid suspending service to domains due to the content on them but has made exceptions. Last year it told the operator of the white supremacist site Daily Stormer to switch registrars after the Charlottesville rally. The registrar said the site was inciting violence, which is against its terms of service.

The operators of Daily Stormer and Gab are actually fortunate that GoDaddy merely asked them to switch providers. When DailyStormer.com moved to Google, the company went a step further by suspending and locking the domain.

Gab.com was purchased for over $200,000 on Sedo. It appears that the social network then acquired the domain on Flippa for $220,000 last month. It had been using Gab.ai for its web address.

© 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

Kim Komando on Domain Names

Domain Name Wire - Sat, 10/27/2018 - 21:38

Popular tech writer/podcasts introduces her audience to domain investing.

News stories and podcasts about domain investing that are geared to a mass audience can be hit or miss.

Kim Komando, “America’s Tech Goddess”, just published a podcast that includes a segment about buying and selling domain names for profit.

She has two guests who talk about how to value domains, where to sell them, and how to make money with domains. Kim also discusses how much she paid recently to buy two domains, including PodNet.com.

It’s an interesting high-level introduction to domain investing, and I’m curious what you think about the advice the two guests share. You can listen to the podcast 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.

No related posts.

Categories: Domains

.DE domains lead the way in $350k Sedo auction

Domain Name Wire - Fri, 10/26/2018 - 15:07

German country code domains sizzle in monthly auction.

Sedo’s October Great Domains auction ended yesterday with a higher-than-usual tally of $350,000. It was the highest-grossing Great Domains auction of 2018.

The top sale was wg.de at €102,501. WG is short for a flat/apartment share or dorm in German. There were 35 bids and the domain easily eclipsed its €65,000 reserve price.

NFC.com sold for €68,200. While higher than most three-letter domain sales to investors, NFC is short for near-field communications. NFC is used for contactless payments such as Apple Pay.

NOVO.com brought home a top bid of $52,999. Novo is a very popular name for companies. Just Google it.

Other top names include grillen.de (Barbecue) for €41990, wc.de (Water Closet) for €29000 and yal.com for $20,500

© 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. Next Navigation Sells Pathology.com and More
  2. Moms.com sells for $252,000 in Sedo Auction
  3. Two domain name auctions to watch this week
Categories: Domains

Verisign adds nearly 2 million .com/.net domains in Q3

Domain Name Wire - Fri, 10/26/2018 - 13:32

.Com continues to chug along.

Verisign (NASDAQ: VRSN) reported third-quarter 2018 results yesterday.

On the domain name side, the company processed 9.5 million new .com/.net registrations during Q3. After accounting for deletions, 1.99 million .com/.net domains were added to the domain base. At 151.7 million, it’s up 4% year-over-year.

The results exceeded Verisign’s guidance of 1.3 million to 1.8 million for the quarter.

The company expects to add 0.9 to 1.4 million .com/.net domains to the base during Q4 of this year.

After this quarter, the company will change how it provides guidance on net adds. It will switch from quarterly guidance to annual guidance.

As I’ve noted before, it’s fairly easy to pull levers to hit this guidance mark. Switching to annual guidance will allow the company more time to decide which levers to pull for better long-term performance.

With regards to the Cooperative Agreement between Verisign and the NTIA, Verisign CEO James Bidzos said the company is confident that an amended agreement can be executed before it expires at the end of next month.

© 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. .Com contract extension shorter than Verisign expected
  2. How Verisign hit its Q1 growth numbers
  3. Verisign sells security business to Neustar for up to $120 million
Categories: Domains

15 end user domain sales up to $75,000

Domain Name Wire - Thu, 10/25/2018 - 20:40

A Chinese arts school, German audio software company and psychic all bought domain names last week.

This week we have a good list of end user sales from Sedo, as well as a bonus sale that domain investor Greg Ricks sent to me.

One nice sale was the makers of the gold buying app Vaulted picking up Vaulted.com. They are forwarding it to their existing domain VaultedApp.com. Domains still matter even if you are promoting an app!

Take a look at some of the end user sales at Sedo this past week, and you can view previous weeks’ lists here.

Fingerpaint.com $75,000 – I’m going to include this one even though we don’t know the buyer yet. This is an end user price, although a very fair price for the buyer. One guess is that Fingerpaint Marketing Inc. bought it. They use FingerpaintMarketing.com and use Amazon AWS. Fingerpaint.com is pointing to AWS services but is not resolving yet.

Fraser.com $36,259 – I got word from domain investor Greg Ricks that he sold this domain. It was purchased by psychic Matt Fraser, who forwards it to MeetMattFraser.com.

Hexacom.com $19,500 – Hexacom is an oilfield technology company.

Vaulted.com $17,000 – Mcalvany ICA bought this domain name for their app Vaulted. It forwards to VaultedApp.com.

Pixelle.com €10,000 – Paper company Glatfelter has a brand called Pixelle.

The food company that sells Curry in a Hurry bought the matching .com domain name.

CurryInAHurry.com $9,000 – How’s this for a four-word domain sale? The domain was bought by Pure Indian Foods Corporation in New Jersey.

BredBand.nu €6,600- Bredband=Broadband in Swedish. This keyword domain was purchased by a company that provides quotes for broadband service. .NU is the ccTLD for Niue and is sometimes marketed as “NEW”.

Side-Effects.com $6,000 – This hyphenated name was appropriately purchased by Medikura, a German pharmaceutical company.

PlugInCenter.com $5,000 – Initial Audio, a German audio software company, bought this domain. It doesn’t resolve yet.

IMBeauty.com $2,888 – This is forwarding to IMFitStore.com, an online nutritional supplement store that could be venturing into beauty products.

Sisa.cn €2,700- This Chinese ccTLD was purchased by the Stella International School of Arts in Guangdong, China.

Money-art.com $2,577 – No stranger to the hyphen, this was purchased by the German audio equipment company Speakers-4-you.

Calculators.io $2,250 – The buyer is setting up a site with different types of calculators including financial, health, math and more.

YLPro.com €2,125 – Young Living Essential Oils bought this domain. It uses the domain YoungLiving.com.

HelloTax.com $2,003 – A great deal for a strong and catchy name. Bought by a software provider based in Spain who specializes in VAT services to help businesses be tax compliant within Europe.

© 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

Verisign sells security business to Neustar for up to $120 million

Domain Name Wire - Thu, 10/25/2018 - 20:16

The .com registry sends security business to Neustar.

Verisign (NASDAQ:VRSN) has sold its Security Services business to rival registry provider Neustar for up to $120 million.

The deal is for $50 million up front and a contingent amount of up to $70 million due on the first anniversary. The contingent payment is based mostly on successfully transitioning customers to Neustar over the 12-month period after closing.

Verisign’s Security Services business includes DDoS protection, managed DNS, DNS Firewall and recursive DNS services.

With this exit, Verisign will now focus solely on internet naming and related services

© 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. U.S. Antitrust Division investigating Verisign running .Web
  2. Verisign earnings: 149.7 million total .com/.net base, $302 million revenue
  3. How much would .Com domains cost if .com went out to bid?
Categories: Domains

Google uses .New TLD to create shortcuts for Google Docs

Domain Name Wire - Thu, 10/25/2018 - 17:53

Type “Doc.New” to easily create a new Google Doc.

Google is using its .New top level domain name in a unique (and perhaps unprecedented) way.

People can now type certain .new domains in their browsers to instantly create Google Docs, Sheets, Slides, Sites and Forms.

If you are logged into your Google account, try going to one of these domains:

doc.new
form.new
sheet.new
slide.new
site.new

This is an interesting idea. It goes beyond the typical URL forward by taking you to an action-based URL.

Here’s a tweet from Google that lists more domains you can use.

Introducing a .new time-saving trick for users. Type any of these .new domains to instantly create Docs, Sheets, Slides, Sites or Forms ↓ pic.twitter.com/erMTHOsdyH

— Google Docs (@googledocs) October 25, 2018

© 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. Google open sources domain registry, Donuts collaborates as pressure on registry providers mounts
  2. MMX releases 2015 report, discusses go-forward strategy
  3. Donuts chooses Rightside over Google Nomulus
Categories: Domains

.Amazon top level domain taken off “Will not Proceed” status

Domain Name Wire - Thu, 10/25/2018 - 17:44

So you’re saying there’s a chance…

There’s another ray of light for those hoping that ICANN will eventually delegate the .Amazon top level domain name to Amazon.com.

Earlier today, ICANN’s Board of Directors instructed the non-profit domain overseer to remove the “Will Not Proceed” status on the .amazon application. (The actual change in the public database hasn’t occurred yet.)

Last month, the Board passed a resolution asking ICANN to act as a mediator between countries in the Amazon Cooperation Treaty Organization (ACTO) and Amazon.com. These countries are concerned that Amazon.com’s ownership of .Amazon will somehow hurt the region.

Amazon has been negotiating with the countries for many years. It has offered to reserve domains, provide funding for a .amazon website to promote the region, and give $5 million in Amazon goods and services. The ACTO members are unmoved.

The decision to remove the “Will Not Proceed” status is mostly symbolic as ICANN still needs to work with the parties to come up with a compromise.

It will be a big win for new top level domain companies if .Amazon is delegated to the company. Amazon’s usage of the domain will help spread the word that there are new options to the right of the dot.

© 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. Amazon.com gets big win in domain battle, may yet get .Amazon domain
  2. Will .Amazon ever see the light of day? There’s some movement.
  3. Court denies Donuts’ request to delay .web auction
Categories: Domains

.AI begins auctioning expired domain names

Domain Name Wire - Thu, 10/25/2018 - 16:37

Anguilla’s registry cuts out the middleman and begins auctioning expired domain names.

Anguilla’s ccTLD registry is auctioning expired domains.

The registry for country code domain name .AI (Anguilla) has started auctioning off domain names that previous registrants let expire. The auctions run differently than on most expired domain auction sites.

Auctions run only once a month for ten days. They start on the third Friday of each month and run for ten days. Also, any bids placed in the final hour extend the auction by an hour, which is much longer than most platforms extend bidding for late bids.

Starting bids are $100 with $10 increments.

In order to bid, users need to create an account and deposit at least $100. Users can pay with a credit card, wire transfer or bitcoin. There’s a 60 day delay to transfer a domain if you pay with a credit card.

Also, note that .AI has a $100 transfer fee that doesn’t extend the registration. So if you want to transfer the domain to another registrar, you need to factor in another $100 to the price.

The .AI registry has licenced the software used by Park.io to run its platform.

For the auction that ends on Monday, Customer.ai is currently the top domain with 14 bids and a $3,343 price. Other available names include BTC.ai, Strategy.AI, Target.ai and Ledger.ai.

© 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. NameJet and SnapNames combine forces on pending delete domain names
  2. 1&1 sends expired domain names to Sedo
  3. How NameJet can right the ship
Categories: Domains

HugeDomains uses a novel approach in UDRP response

Domain Name Wire - Thu, 10/25/2018 - 16:22

Company used Amazon Turk to survey people about the meaning of a term.

Tenaris with an ‘n’, not an ‘m’.

Domain name seller HugeDomains used a unique approach in a recent UDRP response.

Oil and gas company Tenaris Connections BV filed the dispute against the domain Temaris.com, which is one letter off from the company’s Tenaris.com domain.

HugeDomains had a lot going for it in this case. It didn’t point the domain to competing ads and apparently capitalized the domain on the landing page as TeMaris.com.

“Te” is a common pronoun in many languages.

To bolster its argument that it had no idea who the complainant was when it registered the domain, HugeDomains used Amazon mTurk to survey people about what “temaris” meant to them. No respondents mentioned the oil and gas company. Amazon’s Mechanical Turk is a fast and cheap way to get feedback from a large crowd.

This is a clever idea.

The panel didn’t put too much weight on the survey results but did consider it:

In reaching this conclusion the Panel has not attributed significant weight to the Amazon survey the Respondent relies upon (above) as it does not know enough about exactly how it was conducted. The Panel is however struck by the fact that it would seem that not a single person responding to the survey identified the Complainant or the TENARIS trademark in his or her answer, which seems consistent with the Panel’s view (above) as to the specialized sector the Complainant operates in.

One of the three World Intellectual Property Organization panelists found this to be a case of reverse domain name hijacking. The other two gave Tenaris a pass:

…However in circumstances where the Complainant is seeking to be vigilant to prevent “typosquatting” in relation to its name, and where it has succeeded in previous UDRP cases (albeit with materially different facts) the majority are not persuaded the Complainant’s conduct falls within the above guidelines nor that it deserves the censure of a finding of RDNH.

The most baffling part of this case to me is that Tenaris pursued legal action when the domain was listed for sale for only $3,195. It had a flimsly case to begin with and likely spent well more than the asking price between filing and legal fees.

© 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. Porsche.me: Money Down the Drain
  2. Certipost Pays to Settle Domain Dispute
  3. EA loses domain dispute for SSX.com for upcoming SSX launch
Categories: Domains

“We Buy TLDs”

Domain Name Wire - Wed, 10/24/2018 - 15:37

Companies really want to buy TLDs, but at a fair price.

I was amused to see a sign at Afilias’ booth at ICANN 63 in Barcelona today that read “We Buy TLDs” (pictured).

It reminds me of that old t-shirt that read “I Buy .Coms”. I think Skenzo created the shirts.

Now people are buying entire namespaces.

Afilias is not alone in wanting to acquire top level domains. Donuts has acquired some and Radix is actively looking. CentralNic, Neustar, etc. are all on the lookout to expand their portfolios.

There still seems to be a disconnect between the price new top level domain owners want for their domains compared to how much buyers are willing to pay. Some sellers are perhaps stuck on 2014 prices while buyers are valuing them based on 2018 reality. That’s why many of the transactions you see are for defunct domains.

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

No related posts.

Categories: Domains
Syndicate content
Powered by Drupal. CristalX theme created by Nubio | Webdesign.