skip to content

News

  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.
  • : preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/kohashi/public_html/includes/unicode.inc on line 311.

NameJet and SnapNames combine for $500k+ sales in November and December

Domain Name Wire - Tue, 01/09/2024 - 14:25

Check out what sold over the past two months.

NameJet and SnapNames had a couple of slow months to finish the year, at least as far as sales of $2,000 or more are concerned.

Namefold’s two expired domain services combined for $239k of sales in November and $293k in December. 57 domains in November and 63 in December went for $2,000 or more.

Here are some domains that stand out to me:

BostonHomes.com $1,595 – Big city “homes .com” domains are super valuable. I’m less enthusiastic about long-tail real estate domains because we’ll likely see a steep drop in the number of Realtors over the next few years due to commission changes.

Mompreneur.com $6,250 – Big market for this domain geared to women entrepreneurs.

Newscaster .com $4,400 – I bought this one.

DigitalCoupons.com $4,300 – Online coupon clipping is a huge market.

RetireOnYourTerms .org $3,600 – This shows how much SEO/prior use can play a role in expired domains. I paid a lot less for the matching .com domain in July.

PittsburghRealEstate.com $3,332 – Another good city real estate domain, if not a little long.

TherapistFinder .com $2,013 – I flagged this auction while it was running. A therapist directory should absolutely not use this domain name. Stare at it long enough, and you’ll understand why. (There is some SEO value in this one, though.)

Here’s the combined list of sales over $2,000 during the past two months:

MonthDomainSales Amount 23-Novicinsights.com$13,500 23-Novsnappytv.com$8,250 23-Novtakt.com$7,800 23-Novciese.org$6,600 23-Novepicurus.com$5,555 23-Novbluesprig.com$4,710 23-Novcrosscurrent.com$4,702 23-Novmalaika.com$4,600 23-Novdigitalcoupons.com$4,300 23-Novprovidersedge.com$3,920 23-Novtechchat.com$3,700 23-Novthecakegirls.com$3,560 23-Novreefbase.org$3,500 23-Novgridforum.org$3,450 23-Novpuresoul.com$3,203 23-Novpdic.com$3,101 23-Novroboman.com$2,560 23-Novmaoi.org$2,300 23-Novbafuture.org$2,200 23-Novzray.com$2,071 23-Noveastfieldmall.com$2,051 23-Novdelitsdopinion.com$2,050 23-Novlured.com$2,050 23-Novtripmates.com$2,049 23-Novcolor-wheel-pro.com$2,019 23-Novitsok.com$12,100 23-Novbridgestreet.com$11,750 23-Novajemjournal.com$11,500 23-Novusemod.com$11,000 23-Novbankstreetbooks.com$7,550 23-Novlooksgood.com$7,077 23-Novartingeneral.org$5,750 23-Novaftron.com$4,465 23-Novservicestar.com$4,200 23-Novquicklift.com$3,649 23-Novradioworks.com$3,600 23-Novretireonyourterms.org$3,600 23-Novfcfc.com$3,038 23-Novrationalchristianity.net$3,000 23-Novsynoptics.com$2,811 23-Novmygeek.com$2,800 23-Novscreeny.com$2,625 23-Novyins.com$2,600 23-Novcafm.com$2,505 23-Novhairpro.com$2,501 23-Novhendersoninsurance.com$2,499 23-Novpoliticsoftheplate.com$2,410 23-Novhg21.com$2,400 23-Novhg67.com$2,400 23-Novadriaan.com$2,350 23-Novswales.com$2,252 23-Novpawspice.com$2,215 23-Novmakura.com$2,155 23-Novautonomously.com$2,149 23-Novtvdaily.com$2,050 23-Novinterinvest.com$2,049 23-Novthewpclub.net$2,049 23-Dectabula.com$24,000 23-Decbostonhomes.com$15,595 23-Deceeva.com$10,150 23-Decwebcraft.com$9,850 23-Dechrcr.org$6,760 23-Decpowergeneration.com$6,395 23-Decmompreneur.com$6,250 23-Dectheodore-roosevelt.com$6,055 23-Decsterlingcodifiers.com$5,761 23-Decgloballife.com$5,250 23-Decserpo.org$4,000 23-Decearlychildhoodohio.org$3,900 23-Dechexadecimal.com$3,650 23-Decietdl.org$3,100 23-Deccedd.net$3,031 23-Decasbj.com$2,504 23-Decasciiwwdc.com$2,350 23-Deccomoco.com$2,170 23-Decsupercomp.org$2,100 23-Decdailyjob.com$2,050 23-Dectherapistfinder.com$2,013 23-Decxela.com$15,700 23-Decfakeaddressgenerator.com$8,009 23-Dectoycars.com$7,025 23-Decvoosh.com$6,299 23-Decelitemedical.com$6,251 23-Decsmartbuyer.com$5,305 23-Decquadernsdigitals.net$5,000 23-Decskymania.com$5,000 23-Decneurosurgical.com$4,756 23-Declurch.com$4,650 23-Decsaly.com$4,538 23-Decnewscaster.com$4,400 23-Decplann.com$4,338 23-Decwildretreat.com$4,249 23-Declaplume.com$4,189 23-Decflightrights.com$3,950 23-Decidunn.com$3,700 23-Decseattlecentral.org$3,700 23-Decraar.com$3,433 23-Decinovamed.com$3,400 23-Decpittsburghrealestate.com$3,332 23-Decmedcode.com$3,300 23-Decmyways.com$3,300 23-Decdekon.com$3,207 23-Decmzrsrc.com$3,100 23-Decgraceway.com$3,011 23-Decnationalcad.org$3,011 23-Deckommerce.com$2,919 23-Decinterfit.com$2,800 23-Decallclaims.com$2,749 23-Deccarclick.com$2,600 23-Decnantucketproperty.com$2,600 23-Decbrightinfo.com$2,519 23-Decautodeploy.com$2,425 23-Decgchc.com$2,399 23-Decpopline.org$2,300 23-Decamcat.com$2,169 23-Decenacademic.com$2,160 23-Deccbd-oil.com$2,101 23-Decpench.com$2,005 23-Deccustomnails.com$2,002 23-Dec8b8b.com$2,000

Post link: NameJet and SnapNames combine for $500k+ sales in November and December

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

Related posts:
  1. Web.com has strong month for aftermarket domain sales
  2. Some Register.com and Network Solutions expired inventory is on GoDaddy Auctions
  3. Here’s what sold at NameJet and SnapNames last month
Categories: Domains

Efty to launch Efty Pay along with new branding

Domain Name Wire - Mon, 01/08/2024 - 19:01

The company says Efty Pay will make domain name transactions easier for both buyers and sellers.

Efty is launching a new payments service and rebranding early this year.

Big changes are in store for domain name sales platform Efty.

The company is launching Efty Pay, along with a complete overhaul of its marketplace and branding, early this year.

Efty promises that Efty Pay will simplify the domain sales checkout and transfer process, using automated workflows to make it easier for both buyers and sellers.

The domain sales platform partnered with a European payment processor to accept payments of all types. The payment processor will collect the payment and then disburse the seller’s funds directly to the seller (while sending the commission to Efty), ensuring that Efty never holds the buyer’s money directly. Efty declined to name the payment processor but said it will reveal it when it launches the service.

“The domain name aftermarket has been through many changes recently, such as consolidation, price alignment, and increased commission,” said Doron Vermaat, COO of Efty. “As a result, we’ve seen strong demand from the domain name investor community for an independent solution to sell domain names for a fair commission, giving them back more control and insights into their sales process and transactions.”

Unlike most domain sales platforms, Efty works on a SaaS model. Sellers pay a monthly fee based on how many domains they have on the platform and don’t pay a commission unless the domain sale originates through Efty’s separate marketplace.

Sellers have the option of using Escrow.com, Dan Payments, and now Efty Pay to consummate the transaction. This typically involves a fee for the seller.

In the case of Efty Pay, any sale that originates from the seller’s Efty landing page, custom (personal) marketplace, or lead import will have a 5% transaction fee. (There’s a 12.5% commission for domains sold through Efty’s marketplace.)

Efty will also launch a partner API so other marketplaces can use Efty Pay.

This all sounds a bit like Dan.com’s payment system, but Efty doesn’t look at it as a replacement.

“Our objective is to offer domain name investors freedom of choice,” said Vermaat. “This means Efty Pay will be available in addition to our existing integration with Dan.com and Escrow.com.”

It seems like a smart move. With Dan.com now owned by competitor GoDaddy, it’s possible that Dan payments will go away at some point.

In addition to launching Efty Pay, Efty is redesigning its marketplace and brand identity in conjunction with the new product rollout. An exact date of the launch has not been announced.

Efty shared this preview video with Domain Name Wire:

Efty Pay from Efty on Vimeo.

Post link: Efty to launch Efty Pay along with new branding

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

Related posts:
  1. Efty adds live chat to marketplace
  2. Efty teams up with Dan.com, also introducing marketplace
  3. Efty launches new domain name marketplace
Categories: Domains

The world’s sweetest domain names – DNW Podcast #468

Domain Name Wire - Mon, 01/08/2024 - 16:31

Learn how GOAT Foods is building brands on great domain names like chocolate.com.

Chocolate.com. Licorice.com. Caramels.com. These are some really sweet domain names, and they’re all owned by one company: GOAT Foods. The company is leveraging these great domain names to sell snacks and confections online.

On today’s show, GOAT Foods cofounder Jonathan Packer tells the company’s origin story and explains how the high-quality domain names have helped it launch its brands. He also discloses which great domains the company is turning into businesses next.

Also: Squarespace dip, Roberto.com, Century.com, Verizon’s cybersquatting win

Sponsor: Sav.com domain transfers

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

Post link: The world’s sweetest domain names – DNW Podcast #468

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

Related posts:
  1. Domain auction preview with Monte Cahn – DNW Podcast #220
  2. Naming Tools with Anthony Shore – DNW Podcast #227
  3. 2020 Domain Industry Predictions – DNW Podcast #266
Categories: Domains

Dynadot’s monthly .ai auction grosses over $300k with six figure sale

Domain Name Wire - Mon, 01/08/2024 - 13:32

Here’s everything that closed at $500 or more.

Dynadot’s monthly .ai expired domain name auction ended last Monday. It was New Year’s Day and I wasn’t able to keep tabs on the auction. However, I now have the final bid prices.

Assuming all of these transactions go through, the auction will gross over $300,000. That’s less than the auction that closed in December, although the inventory probably wasn’t as strong. It didn’t help that the auction ended on a major holiday, either.

Vision.ai led the pack with a six-figure closing price. Here are all of the domains that closed at $500 or more:

vision.ai 100,000
trick.ai 24,977
insure.ai 24,700
dog.ai 21,311
betty.ai 20,088
he.ai 15,800
initiate.ai 13,200
magazine.ai 10,000
sustainable.ai 7,100
hoax.ai 6,101
persons.ai 6,100
ru.ai 6,100
streak.ai 4,300
producers.ai 4,054
l1.ai 3,850
discussion.ai 3,383
actualize.ai 3,209
astound.ai 2,939
reconstruction.ai 2,827
redrock.ai 2,551
selena.ai 2,345
rainfall.ai 2,025
twice.ai 2,025
epay.ai 2,001
h3.ai 1,934
visionx.ai 1,913
hose.ai 1,631
esignature.ai 1,525
thermostat.ai 1,501
jobfind.ai 1,325
katherine.ai 1,314
stylus.ai 1,289
chateau.ai 1,136
jazzy.ai 1,006
banshee.ai 1,001
enigmatic.ai 999
countable.ai 965
omo.ai 965
calvary.ai 929
cathedral.ai 918
gfe.ai 918
3dprinted.ai 898
fireup.ai 898
ugo.ai 810
employed.ai 807
emg.ai 801
mediq.ai 785
voicestudio.ai 760
brg.ai 740
drain.ai 737
protech.ai 735
zoomer.ai 703
logistica.ai 698
smartcart.ai 695
alx.ai 676
ebanking.ai 676
medscan.ai 671
utc.ai 671
bng.ai 625
documented.ai 616
fixel.ai 616
settled.ai 616
ddr.ai 605
scoops.ai 586
myart.ai 565
reserva.ai 565
waking.ai 561
dinos.ai 551
grains.ai 545
futurelab.ai 544
bhg.ai 515
gtl.ai 515
utg.ai 515
v5.ai 510
york.ai 504
sweeps.ai 501

Post link: Dynadot’s monthly .ai auction grosses over $300k with six figure sale

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

Related posts:
  1. Dynadot auctioning expired .AI domain names
  2. Over $160k of expired .ai domains sold today
  3. .AI expired domain auction grosses over $425k, led by engage.ai
Categories: Domains

Verizon wins $450k cybersquatting judgment

Domain Name Wire - Fri, 01/05/2024 - 16:49

Company gets $50,000 in statutory damages per domain.

Telecommunications company Verizon, through its Verizon Trademark Services LLC affiliate, has been awarded $450,000 in statutory damages against a cybersquatter.

The company filed the case in U.S. District Court in Washington D.C. against Verizon Trademark Services LLC and Matt McMan.

If the corporate name of the defendant sounds confusing, it’s because the defendant took a rather interesting approach to cybersquatting. According to the court’s opinion, issued yesterday:

Per the Complaint, VTS LLC—under the exclusive control of its “sole organizer and contact,” Co-Defendant Matt McMan—registered multiple infringing domain names and trade names as part of a scheme to mislead consumers, damage the VERIZON mark, and extort Verizon. Id. ¶¶ 10, 67–68, 96–100. As early as April 2023, the various named Defendants (including VTS LLC), through McMan, began registering domains that derived from or incorporated trademarks owned by Verizon, which prompted Verizon to send cease-and-desist letters objecting to the unauthorized use of its trademarks. Id. ¶¶ 41, 44, 72. In response, Defendants doubled down, registering additional domain names (as well as trade names) incorporating the entirety of the VERIZON mark or other marks owned by Plaintiff. Id. ¶¶ 45, 73–74, 77, 83–84. When registering the domains at issue, Defendants often did so anonymously, using “a popular domain privacy service” known as “Domains By Proxy.” Id. ¶¶ 42, 103.

At the height of this misconduct, VTS LLC drafted a “Complaint” alleging that Plaintiff was misleading consumers. Id. ¶ 94. This same document also boasted that Plaintiff “Can’t Even Get a DBA in Washington, DC for ‘Verizon Trademark Services’ LLC because . . . Verizon Trademark Services LLC Owned By Matt McMan Will NOT Grant ‘Verizon’ written Consent.” ECF 1-10 at 4. On multiple occasions, Defendant sent versions of this “Complaint” to Plaintiff and government officials in a coercive attempt to sell or license these marks to Verizon. See ECF 1 ¶¶ 88, 94, 100; ECF 1-11; ECF 1-12; ECF 1-13. When Verizon resisted those efforts, Defendants promptly registered even more domains incorporating the VERIZON mark.

The defendant didn’t show up in court and Verizon won a default judgment.

Verizon asked for $50,000 statutory damages for nine domain registrations, including VerizonTrademark .com and Verizon .com.co. The court awarded (pdf) this amount and ordered the domains transferred to Verizon.

This appears to be the defendant’s website.

Post link: Verizon wins $450k cybersquatting judgment

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

Related posts:
  1. UDRP has its limits when it comes to taking down counterfeit websites
  2. Meta Platforms drops lawsuit against Namecheap after settlement
  3. What’s your duty to search for trademarks before registering a domain?
Categories: Domains

New registrations plummet after Squarespace takes over Google Domains

Domain Name Wire - Fri, 01/05/2024 - 13:45

Unsurprisingly, the strong brand name mattered.

Squarespace acquired Google Domains on September 8, 2023, and we now have an idea of how important the Google brand name was to ginning up registrations there.

ICANN has published data from .com registry Verisign showing new registrations at each registrar for September.

In August, Google Domains and Squarespace registered a combined 250,324 domains. In September, they registered just 189,713 new .com domains.

Google is using Squarespace when people buy some of its products that need a domain and is also sending people to Squarespace when they land on the Google Domains site. (Google Domains still shows up #2 for me in Google when I search for domain names.) Still, it’s clear that the brand name drove a lot of registrations. And these numbers reflect only .com domains, so it’s surely a bigger delta when including all domains.

The winners? Other registrars that picked up the registrations that would have gone to Google had it still been a domain registrar.

Below is a chart showing how the largest registrars did in terms of new registrations in September. Note that the rankings include multiple registrar accreditations within families of registrars. You can see the list at the end of this post. (I started including Mesh Digital and the five “Go” registrars (e.g., Go China Domains) in GoDaddy’s numbers this month. This added about 2k new registrations and 530k total registrations.)

1. GoDaddy.com (NYSE: GDDY) 715,431 (775,175 in August 2023)
2. Namecheap Inc. 283,620  (291,747)
4. Newfold Digital 216,538 (169,663)
3. Squarespace (NYSE: SQSP) 189,713 (250,324)
5. Tucows (NASDAQ: TCX) 163,648 (163,629)
6. Gname.com 133,917 (115,409)
7. IONOS 79,420 (99,454)
8. Alibaba 71,895
9. Dynadot 71,212
10. Wix 70,798 (71,825)

Here’s the leaderboard of the top registrars in terms of total .com registrations under management as of the end of August.

1. GoDaddy 56,142,674 (55,638,534 in August 2023)
2. Newfold Digital 12,380,044  (12,370,532)
3. Tucows 11,113,636 (11,131,272)
4. Namecheap 9,387,689 (9,376,275)
5. Squarespace 8,184,335 (8,166,306)
6. TurnCommerce 5,940,486 (5,958,992)
7. IONOS# 5,669,464 (5,659,585)
8. Alibaba 4,187,402 (4,213,654)
9. Gname 4,237,209 (4,155,354)
10. CentralNic 3,826,492 (3,910,648)

Many domain companies have multiple accreditations, and I’ve tried to capture the largest ones. See the notes below.

  • GoDaddy includes GoDaddy, Wild West Domains, Uniregistry, GoDaddy Corporate Domains, MeshDigital, the 5 “Go Country” registrars, and 123 Reg
  • Namecheap includes Namecheap and Spaceship
  • Tucows includes Tucows, Enom, Ascio and EPAG
  • Newfold Digital Includes PDR, Domain.com, FastDomain, Bigrock, Network Solutions, Register.com, MarkMonitor, SnapNames registrars, and Crazy Domains/Dreamscape. There are other Newfold registrars, but these are the biggest.
  • Squarespace includes Squarespace and Google
  • TurnCommerce Includes NameBright and DropCatch registrars
  • IONOS includes Includes 1&1, PSI, Cronon, United-Domains, Arsys, and world4you
  • CentralNic includes Key-Systems, 1API, Internet.bs, TLD Registrar Solutions, RegistryGate, Moniker, Instra

Post link: New registrations plummet after Squarespace takes over Google Domains

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

Related posts:
  1. The biggest 20 domain name registrars across all ICANN-TLDs
  2. .Com Winners & Losers
  3. A strong month for .com; here are the winners & losers
Categories: Domains

December’s top domain name stories

Domain Name Wire - Thu, 01/04/2024 - 21:36

A look back at the holiday month in the domain name business.

These were the top five stories on Domain Name Wire last month:

1. 14 things you can’t do with .AI domain names – .ai is a country code domain, and you should understand the rules Anguilla has placed on it…which are constantly changing.

2. ICANN debates action after community member’s antisemitic comments – He is behind a domain registrar, a UDRP provider, and an L-Root operator. ICANN is trying to figure out how best to respond to his comments.

3. Two things to do today for your Afternic domain names – One isn’t quite as urgent as I thought, but owners of .io and .xyz domains should take notice of the other.

4. Using Domain Academy’s Research Snapshot to evaluate domains – Some nifty data tools help when evaluating domain names.

5. 3 end user domain buyers tell their stories – A lease-to-own deal, a ccTLD-to-gTLD upgrade, and an expired domain purchase.

Here are podcasts you might have missed:

Selling brandable domains with Keith DeBoer – DNW Podcast #466

2023’s top stories – DNW Podcast #465

NIS2 is here – DNW Podcast #464

Post link: December’s top domain name stories

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

Related posts:
  1. The accidentally successful top level domain names
  2. Domain reads: .Com for uptime, .Bank transitions
  3. Two things to do today for your Afternic domain names
Categories: Domains

ICANN might not renew TAG-Domains accreditation after antisemitic remarks

Domain Name Wire - Thu, 01/04/2024 - 15:46

ICANN gives registrar mini-extension while it awaits Ombud’s determination.

ICANN has delayed fully renewing the accreditation agreement for TAG-Domains after one of the registrar’s leaders made antisemitic remarks.

Talal Abu-Ghazaleh, a leader in the intellectual property community in the Middle East, said in a TV interview:

The Jews do not have any ideology. All they care about is money and interests. I had a friend who was a German cabinet member. I once asked him: ‘When Hitler, may God forgive him, carried out the Holocaust, why didn’t he finish the job and kill all the Jews?’ He said to me: ‘It’s the other way around, but don’t tell anyone I said this. He left a group of them on purpose, so that people would know why we carried out the Holocaust. When you would be tormented by them, you would know the reason.

Abu-Ghazaleh is also affiliated with a UDRP provider and a group that hosts an instance of ICANN’s L Root in Jordan.

ICANN has referred the matter to its Ombuds, stating that this violates ICANN’s Expected Standards of Behavior.

In a letter to TAG-Domains, ICANN noted that the group’s accreditation is set to renew on January 16. Rather than renewing it for a full term, ICANN is renewing it for three months to allow for the conclusion of the Ombuds investigation.

While many people find Abu-Ghazaleh’s comments abhorrent, some in the ICANN community are privately questioning the extension of ICANN’s Expected Standards of Behavior to speech made outside of any connection to ICANN and the domain name community.

This particular case puts ICANN in a precarious position. Abu-Ghazaleh commented in the heat of a war between Israel, which has generally been backed by the United States, where ICANN is based, and someone in a region that has often opposed the establishment of Isreal.

ICANN seems to understand this to a degree and has alluded to free speech considerations.

It’s possible that an apology from Abu-Ghazaleh would resolve the matter, but I’m not sure that one is forthcoming.

One thing’s certain: ICANN’s interim Ombuds has her hands full.

Post link: ICANN might not renew TAG-Domains accreditation after antisemitic remarks

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

Related posts:
  1. .Asia Plans to Release 1 and 2 Character Domain Names
  2. 56 new TLD contracts signed, Donuts has more than half
  3. Signed new TLD registry contracts have a wide range of priority numbers
Categories: Domains

WIPO panel lets bakery off the hook

Domain Name Wire - Wed, 01/03/2024 - 20:46

Panel says Complainant, represented by a 100+-year-old IP law firm, has “simply not understood the Policy.” 

Some UDRP filings have no chance of succeeding.

Consider the case (pdf) that Roberto Industria Alimentare S.r.l. filed against the domain name roberto.com. The Italian baked goods company filed the dispute against Reflex Publishing, which acquired the domain name over two decades ago.

You don’t have to be Italian to know that Roberto is a very common name. In fact, it’s one of the top 20 most common names in Italy.

Yet Roberto Industria Alimentare S.r.l. argued in its case that “ROBERTO” is not a common or descriptive term but is obviously a trade mark in which the Complainant has rights.”

Um, OK.

The World Intellectual Property Organization rightly found in Reflex Publishing’s favor. It noted that Reflex is a company in Florida and probably wasn’t aware of the Complainant. And even if it was aware of the Complainant, “Having regard to the fact of its varied potential uses and the Respondent’s intended use non-infringing of the disputed domain name, registration of it by the Respondent, would not have been abusive.”

The three-person panel then listed several reasons why this appears to be a case of reverse domain name hijacking:

  1. the Complainant has been professionally represented and many panels will find that such a party should be held to a higher standard.
  2. this was a misconceived Complaint in that the Complainant had no credible basis for alleging that its mark had a reputation in the United States and consequently that the Respondent was, or should have been, aware of it. Moreover, it adduced scarcely any evidence to support its assertions and it produced no evidence at all in relation to the alleged repute of its ROBERTO mark in the United States as at the date of registration of the disputed domain name.
  3. the record suggests that the Complainant bought these proceedings because its offer of USD 1,000 for the disputed domain name had been rejected by the Respondent. The Panel notes that the Complainant’s offer did not contain any allegation of wrongdoing on the part of the Respondent in its registration and use of the disputed domain name and was made some 23 years after the Respondent’s registration of it. Having recourse to proceedings under the Policy following an unsuccessful attempt to purchase a domain name is sometimes referred to as a “Plan B.”

Got it, so reverse domain name hijacking.

Except the panel let the Complainant off the hook, saying it probably just didn’t know what it was doing by filing the complaint:

In these proceedings, some of more egregious features associated with a finding of RDNH, such as manifestly untrue allegations against a respondent and attempts to mislead the panel, are absent. The overall impression is that the Complainant has simply not understood the Policy and the burden it has to meet. For this reason, by a very narrow balance, the Panel declines to make a finding of RDNH.

Wouldn’t you say that not mentioning that Roberto is a common first name was an attempt to mislead the panel?

And get this. The Complainant’s representative was Società Italiana Brevetti S.p.A. Go to its website, and you’ll see that it prominently displays “Intellectual Property since 1882” in Italian at the very top.

So it just didn’t know what it was doing? Hmm.

John Berryhill represented Reflex Publishing.

Post link: WIPO panel lets bakery off the hook

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

Related posts:
  1. Company fails to upgrade from .com.mx to .com in UDRP
  2. A (mostly) thorough cybersquatting decision
  3. HDT.com: why no reverse domain name hijacking?
Categories: Domains

Swiss watchmaker alleges century.com is stolen, but loses cybersquatting claim

Domain Name Wire - Wed, 01/03/2024 - 17:00

The current owner likely has clean hands.

Watchmaker Century says the domain name century .com was stolen from it, but a WIPO panel found in favor of the current owner—image from century.ch website.

Swiss watchmaker Century Time Gems Ltd has lost a cybersquatting dispute it filed against the domain name century.com.

In a World Intellectual Property Organization (WIPO) filing, the company said it acquired the domain name in 2006 for a six-figure sum. It subsequently used the domain name and said it attracted over 2.5 million visits since then.

But something happened in late 2022. According to DomainTools historical Whois records, the domain name moved from Tucows reseller Funio on December 18 to registrar Name SRS AB by December 21.

The current owner, Century Aluminum, says it acquired the domain name in July of this year. This is reflected in Whois records that show the domain name moved to GoDaddy at that time.

Century Aluminum says it bought the domain name from another party and provided a copy of an invoice. Other details of the acquisition are scant in the WIPO decision.

This may well be a situation in which a legitimate company acquired a domain name that had been stolen from another party.

Either way, the analysis that would need to be conducted — and the repercussions should the current owner indeed have purchased a “hot” domain — is outside the scope of the Uniform Domain Name Dispute Resolution Policy. Therefore, panelist Steven Maier denied the claim.

Hopefully, this will serve as a lesson to corporations that own valuable domain names. If you spend six figures for a domain name, you need to add security to it to prevent its unauthorized transfer. Verisign’s Registry Lock would have likely prevented this alleged theft.

FMP Fuhrer Marbach & Partners represented the Complainant, and Frost Brown Todd LLC represented the Respondent.

Post link: Swiss watchmaker alleges century.com is stolen, but loses cybersquatting claim

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

Related posts:
  1. Allegedly stolen domain PV.com returned via UDRP
  2. UDRP filed against two letter domain Yu.com
  3. Standard & Poor’s loses domain name dispute
Categories: Domains

The biggest 20 domain name registrars across all ICANN-TLDs

Domain Name Wire - Wed, 01/03/2024 - 14:43

Ranking the biggest registrars by domains under management.

Each month, I publish a report of the top 10 domain name registrars in .com domain names. This report is based on data that registries submit to ICANN every month.

ICANN publishes data for every top level domain, but the data is in separate files. It would be a lot of work to compile this data across 1,000+ TLDs by hand, so I’ve never done a report showing domains across all top level domains.

But earlier this year, ICANN had to run these numbers for a unique purpose: a vote to change the registrar accreditation agreement. Voting was partly weighted based on domains under management, so ICANN ran the numbers for July 2023. It was even more helpful by combining the top five registrars into “families” since many companies own multiple registrars.

So, drum roll, please…here are the top 20 registrars, ranked by total domains under management as of July.

Some caveats before you dig in:

  • ICANN doesn’t get reports on ccTLDs, so country domains aren’t included in these numbers.
  • ICANN calculated the top five registrar families. After that, in cases where a registrar owns multiple registrars, I did my best to include all the registrars in one family. I surely missed some.
  • Some registrars sell domains registered through resellers, often due to consolidation. This inflates the number of DUMs the reseller gets credit for and deflates the registrar that sold them.

1. GoDaddy 71,161,941
2. Newfold Digital 19,466,275
3. Namecheap 15,865,856
4. Tucows 14,913,192
5. Squarespace 10,663,563
6. IONOS 8,266,995
7. TurnCommerce 6,143,131
8. Alibaba 5,874,012
9. Team Internet 5,575,514
10. GMO 4,789,564
11. Gname 4,728,979
12. NameSilo 4,602,373
13. Dynadot 3,492,034
14. Wix 2,725,873
15. OVH sas 2,285,366
16. Name.com 2,225,529
17. Sav 2,011,237
18. Xin Net 1,444,962
19. CSC 1,427,617
20. PorkBun 1,350,021

Post link: The biggest 20 domain name registrars across all ICANN-TLDs

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

Related posts:
  1. .Com finished last year with a bang – updated rankings
  2. The Latest .Com Winners & Losers
  3. Namecheap jumps up .Com leaderboard
Categories: Domains

A few tickets remain for this month’s ICA meeting in Las Vegas

Domain Name Wire - Tue, 01/02/2024 - 18:34

If you want to go to the ICA Meeting in Vegas (and you should!), a handful of tickets remain.

Internet Commerce Association (ICA) will hold its annual meeting in Las Vegas from January 17-20.

I checked in this morning with Kamila Sekiewicz, Executive Director of ICA, for an update. There’s a hard cap on attendance due to space, but there is room for another 10 or so people. So, if you haven’t purchased a ticket yet and want to attend, do it as quickly as possible.

Tickets are $599. If you’re not a member, you can get a steep discount if you join. For example, you get half off by joining at the $600/year level. Bronze and higher levels get at least one free ticket.

With high demand this year, the room block at Resorts World has sold out. However, there are still affordable rooms available when booked directly or through hotel comparison sites.

And the fun day activities on Thursday, January 18, are filling up quickly. Kamila tells me the most popular activities are the Red Rocks hike and the pickleball tournament.

I look forward to seeing everyone there.

Post link: A few tickets remain for this month’s ICA meeting in Las Vegas

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

Related posts:
  1. ICA Member Meeting returns to Las Vegas in January
  2. Domain Name Companies Spend $2M Lobbying Washington
  3. Nominations now open for ICA’s 2021 Lonnie Borck Memorial Award
Categories: Domains

4 New Year’s Resolutions for domain name investors

Domain Name Wire - Tue, 01/02/2024 - 17:15

Here are four things every domain investor should strive to do in 2024.

1. Check your nameservers

I’ve been trading domain names for about 25 years, but even I sometimes drop the ball on this. I have a system for onboarding new domain names I acquire, but some fall through the cracks. Every time I audit nameservers, I find some domains that point to stale nameservers.

There are a couple of simple ways to audit your nameservers. If you keep your domains at just a couple of registrars, it’s easy to download lists or view nameservers from within your account. If you keep domains at many registrars, a simple tool like Watch Your Domains Pro can help.

2. Audit your pricing

When was the last time you checked your aftermarket pricing? I often “set it and forget it” and miss out on opportunities as a result. There are a few things I try to check with pricing:

  1. Check to make sure values shouldn’t be adjusted due to trends. Have some AI-related domains with the same listing price they had a few years ago?
  2. Make sure prices aren’t just above the $5k or $10k threshold. Here’s why.
  3. Lower pricing on domains you are considering dropping. If I price them below $1,000 and they don’t sell this year, I’ll drop them the next.
3. Renew domains in advance

Wholesale domain prices generally increase every year, and domain registrars pass this increase on to registrants.

Some of these increases are well known, such as when Verisign increases prices. It raised the .com wholesale price to $9.59 last year and has the option to increase it to $10.26 this year. You can bet this will happen around September 1. Other increases aren’t as newsworthy, and you might not know about them until after they are implemented.

But one thing is for sure…prices almost never go down. So, renewing your domains early helps you save money. It also prevents you from accidentally letting domains expire.

If you have the cash flow, I can think of no good reason not to renew domains early. On the off chance that the domain sells after you renew the domain early, the renewal cost is likely minuscule compared to what you sold it for.

4. Experiment

I’m guilty of getting stuck in my ways. But the best domain investors continually test and find new ways to make money.

What are your New Year’s Resolutions I’ve missed?

Post link: 4 New Year’s Resolutions for domain name investors

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

No related posts.

Categories: Domains

What does the NIS2 Directive mean for domain experts?

Domain Name Wire - Tue, 01/02/2024 - 16:10

In DNW Podcast episode #464, Polina Malaja of CENTR talked about the implications of NIS2 for the domain name industry. I asked Simone Catania of InterNetX if he would share some thoughts on NIS2.

In the constantly evolving world of digitization, staying updated on the latest legislation affecting the cyber landscape is of paramount importance. One such critical piece of legislation recently drawn attention is the Directive on Security of Network and Information Systems (NIS2 Directive). The NIS2 Directive represents an ambitious aspect of the European Union’s plans to ensure a high common level of cybersecurity across all member states.

A deep dive into the NIS2 Directive: its background, purpose and goals

The NIS2 Directive finds its roots in the first-ever EU-wide legislation on cybersecurity, the original NIS Directive adopted in 2016. As the digital landscape continued to grow, so did the realization that with expansion came newer and more complex threats.

Everything around us is bursting into the digital realm—from our personal lives to the industries we work in, making cybersecurity more critical than ever. The threats, including DNS abuse, are diverse and increasing in number. They hold the potential to cause severe disruption to essential services like healthcare, energy and transport systems. This necessitates collective vigilance and adaptation to these potential menaces.

This led the European Commission to propose a revision, aptly named the NIS2 Directive (EU) 2022/2555, in December 2020. The NIS2 Directive is, in essence, a significant upgrade to the original Directive. It establishes a comprehensive framework designed to address growing cyber threats while ensuring the resilience of critical infrastructure across all member states. It provides guidelines and requirements for increasing security measures and reporting incidents for various essential sectors and digital service providers.

The objectives of the NIS2 Directive can be broadly categorized into three primary goals:

  1. Developing a culture of shared responsibility in addressing cybersecurity risks.
  2. Ensuring that essential service providers and digital service providers adhere to strict security standards.
  3. Facilitating swift and efficient information sharing and collaboration for responding to cyber threats among member states.

In sum, the NIS2 Directive displays the European Union’s proactive approach to addressing the urgent issue of cybersecurity. By intent and design, it seeks to shore up the EU’s defenses and make its digital environment safer and more resilient.

NIS2 reshapes the roles of digital operators and domain experts

The NIS2 Directive will have significant implications, not just on a macro level but also on the operational aspects of digital operators and domain experts. Articles 27 and 28 mandate the establishment of registries and the upkeep of domain name registration data. To fulfill these objectives, domain companies must adapt to new standards, reinforce cybersecurity protocols, implement risk management strategies and develop systems for reporting incidents.

Under Article 27, the European Union Agency for Cybersecurity (ENISA) is tasked with assembling and maintaining a registry of multiple entities. These include DNS service providers, TLD name registries, domain name registration services, data center service providers, content delivery network providers and more. The registry consolidates information about such entities, ensuring close monitoring and cooperation between the competent authorities in EU member states. As per the Directive, entities specified in Article 27(1) must provide the necessary information to their competent authorities by 17 January 2025.

Article 28, on the other hand, bears significant implications for the domain industry. It emphasizes the necessity for TLD registries and domain name registration service providers to gather and maintain accurate, comprehensive data on domain name registrations. To ensure this, TLD registries and domain name registration service providers must craft policies and procedures to validate the accuracy of the information in their databases. Additionally, non-personal domain name registration data should be made publicly available promptly after domain name registration.

Domain industry faces new challenges with the NIS2 Directive

The NIS2 Directive presents several challenges for the industry, particularly regarding the verification process and the allocation of responsibilities between registries and registrars. As the Directive pushes for strengthened cybersecurity, it demands stringent verification processes for domain registrations. However, the lack of clear procedures and standards often leaves domain professionals in the dark.

Furthermore, the NIS2 Directive has potential implications outside of the EU as well. It may also apply to companies outside the EU if they offer services to customers within the European Union. One crucial concern is maintaining a balance between legitimate access and data privacy. Operators must provide access to information when they receive legitimate, lawful requests and are required to respond within 72 hours.

So, while the primary goal of the NIS2 Directive is to fortify cybersecurity and enhance infrastructure resilience across the EU, it brings considerable changes and challenges for digital operators and domain professionals. The industry remains highly attentive, closely monitoring the developments and working collaboratively to shape the debate. This will ensure the smooth implementation of the Directive and help companies to navigate the ever-evolving complexities of the cybersecurity landscape successfully.

How to be prepared for these legislative changes

Embracing the changes brought forth by the NIS2 Directive is essential not just for compliance but for the sustainability and resilience of organizations in the face of evolving cyber threats.

For digital operators, the first step towards aligning with the Directive should involve carrying out a thorough risk assessment to accurately understand their existing security postures and identify any gaps that need to be addressed. Subsequent actions should focus on strengthening their systems with advanced cybersecurity measures, frequent auditing and rigorous testing. A proactive approach to incident reporting by establishing clear communication channels can ensure transparency and the ability to implement timely remediation.

Non-compliance with NIS2 can result in reputational damage, loss of essential services, increased scrutiny from customers and investors, decreasing revenue and market share, not to mention substantial fines of up to €10 million or 2% of global annual revenue for essential companies and up to €7 million or 1.4% for important companies.

Compliance with the NIS2 Directive isn’t simply a regulatory necessity but can prove to be a testament to an organization’s commitment to protecting its services, clients and itself against cyber threats. When seen through this lens, the NIS2 Directive is less of a challenge and more of an opportunity for digital operators and domain experts to build trust and assure their customers of their unwavering commitment to security and resiliency.

The value in understanding the NIS2 Directive

The NIS2 Directive represents a significant step towards strengthening the cybersecurity of critical infrastructure within the European Union. This comprehensive framework has implications for both digital operators and domain experts, compelling them to adhere to stricter security standards and fulfill enhanced incident reporting obligations.

That said, decoding the NIS2 Directive in full, with all its complexities and subtleties, can be challenging. To learn more, read the whitepaper “NIS2: Unraveling the Directive“. Tailored for digital operators and domain experts, this resource provides a comprehensive understanding of the NIS2 Directive and helps navigate its implementation.

Post link: What does the NIS2 Directive mean for domain experts?

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

No related posts.

Categories: Domains

2024 Predictions Episode – DNW Podcast #467

Domain Name Wire - Mon, 01/01/2024 - 16:30

25 people kick off the year in our annual predictions episode.

It’s the annual predictions episode! On today’s show, you’ll hear from 25 people about what the biggest surprises of 2023 were and what they expect to happen in 2024. Happy new year and let’s make 2024 a great one!

Sponsor: Sav.com domain transfers

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

Post link: 2024 Predictions Episode – DNW Podcast #467

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

Related posts:
  1. 2016 Domain Name Biz Predictions – DNW Podcast #64
  2. 2018 DNW Predictions Episode – DNW Podcast #166
  3. The 2022 Predictions Episode – DNW Podcast #369
Categories: Domains

2023 top stories: Artificial intelligence

Domain Name Wire - Fri, 12/29/2023 - 14:39

Artificial intelligence had a significant impact on the domain name industry — in more than one way.

Late last year, OpenAI launched ChatGPT. Suddenly, a concept that has been talked about for over a decade had a case study.

It’s hard not to be wowed by the progress of generative artificial intelligence. ChatGPT kicked off a boom in use cases, from creating images to generating content. And with its API, many companies sprung up to take advantage of the power of AI.

You need not look further than the domain registration business to see this play out. Many AI-powered domain name generators sprung to life this year, and they’re pretty darned good. In fact, I sold a domain I found through one of these tools on the aftermarket.

Just about every industry has a use case for AI, and it’s transforming how people work.

It’s also been a boon to the tiny island of Anguilla. It had the good fortune of being assigned the ISO country code AI. It has profited for years from companies registering .ai domains for their businesses, and this went into overdrive in 2013.

In addition to a rapid increase in registrations, the country is profiting by selling expired domains. It started auctioning these names in 2018. It auctions the domains monthly through a partnership with Dynadot (which bought park.io); this month, it grossed over $400k.

It’s not just .ai domains that have seen a lift from the AI boom. This year, chat.com sold for over $10 million — twice! Personally, I sold four AI-related domains on the aftermarket: brainstormAI.com, productivityAI.com, facilityAI.com, and questionAI.com.

As AI has captured the world’s attention, another popular technology has taken a dive. Web3 and blockchain suffered a horrible year, including a near cessation of the market for NFTs and many of web3 leaders doing the perp walk. This has reduced attention on blockchain-based domains, as well as domains adopted by the web3 community. .Xyz saw a fall in aftermarket activity compared to a year ago, although sales are still happening.

Unlike web3, AI has actual use cases that have already been implemented. It’s here to stay.

Post link: 2023 top stories: Artificial intelligence

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

Related posts:
  1. All about these popular .AI domain names
  2. Can AI write good domain name descriptions?
  3. Will AI change domain name search?
Categories: Domains

2023 top stories: An Epik failure

Domain Name Wire - Thu, 12/28/2023 - 20:38

Epik was a big story for the second year in a row.

One of last year’s top stories was still a story this year.

Last year, domain name registrar Epik ran into trouble.

In September 2022, Epik announced that Rob Monster was departing as CEO. This came as a shock; Monster was the founder and face of the company and frequently interacted with domain investors on domain forums and via email.

It turns out there was a reason for the change. Epik owed a lot of customers a lot of money. Rather than keeping escrow and store credit funds separate, Epik used them to fund business operations.

When Monster left, people started to worry and asked for their money. It started a run on the bank, and there wasn’t enough money to pay the customers.

Turning to this year, the company went into triage. It laid off a bunch of employees. Then, customers started complaining about technical issues, including their domains not renewing. It turns out this wasn’t a technical issue; Epik hadn’t been paying the registries. This resulted in ICANN sending a breach notice to the company for failing to renew domains. (Epik later cured the breach.)

One person who was owed money decided to sue.

Despite his absence, Monster continued to have an impact on the company. He and Epik were forced to pay the state of Washington a $10,000 fine for running an unauthorized insurance business called DNProtect.

Then, Epik publicly complained about Monster and asked him to step down from the board. It threatened to sue him.

Epik struck a deal to sell the business in early June. It was held up for a few days until the person who sued over unpaid money agreed to a settlement.

As 2023 comes to a close, Epik has a new (but anonymous) owner. ICANN still hasn’t formally approved the change of control, but it’s business (mostly) as usual at the registrar. It seems most people have been paid back.

Hopefully, Epik won’t make news for the wrong reasons again in 2024.

Post link: 2023 top stories: An Epik failure

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

Related posts:
  1. Epik sued over misuse of funds
  2. Epik responds to customer lawsuit over $327,000 debt
  3. Epik is sold
Categories: Domains

Monthly expired .AI auction ends on New Year’s Day

Domain Name Wire - Thu, 12/28/2023 - 18:38

Celebrate the holiday in front of your laptop.

Domain investors have something to do on New Year’s Day besides nurse a hangover and watch football: bid on .ai domain names.

This month’s expired .ai auction started on December 22, and since auctions last 10 days, that means you’re going to have to pay attention on the holiday.

There are some doozies in this month’s auction. Vision.ai leads the pack with 84 bids up to $38,000 as of the morning of December 28. Insure.ai, sustaintable.ai, and dog.ai are in the four-figure range and will surely go up from there.

I suspect diehards won’t miss the bidding, but there might be an opportunity to pick up domains for a bit less because people have tuned out over the holidays. As for me, I won’t be glued to my computer all day tracking auctions. I’m heading to the Winter Classic hockey game in Seattle and then tuning in to watch Texas beat Washington in the Sugar Bowl.

Post link: Monthly expired .AI auction ends on New Year’s Day

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

Related posts:
  1. Dynadot auctioning expired .AI domain names
  2. My new favorite AI domain generator
  3. Over $160k of expired .ai domains sold today
Categories: Domains

2023 top stories: GoDaddy’s “commission alignment”

Domain Name Wire - Thu, 12/28/2023 - 14:44

GoDaddy’s Dan.com acquisition continues to reverberate in the domain aftermarket.

You might think it’s odd to say that one company changing its sales commissions is a top story of the year. But GoDaddy is the dominant player in the domain aftermarket, and its rate change greatly impacted the domain resale business.

Let’s turn back the clock a bit.

GoDaddy acquired domain sales platform Dan.com last year for about $70 million. One of the first questions people asked was what this would mean for commissions.

Dan charged just 9% to handle payment and escrow for domains. GoDaddy’s Afternic charged much higher but had a declining scale for bigger transactions: 20% on sales below $5,000, 15% of the amount between that and $25,000, and 10% of the amount above that on these sales.

GoDaddy said it was undertaking a “commission alignment” for its aftermarket brands, which also included Uniregistry before it was shut down.

Most people assumed the rate would increase from 9% to somewhere at or below Afternic’s 20% rate.

Instead, GoDaddy dropped a bomb on the industry in January. It said it was raising rates to 25% with no reduction for bigger sales.

But there was a bit of a carrot-and-stick approach to this: park your domains on a GoDaddy-affiliated service and pay just 15%.

So, people who are willing to use GoDaddy’s various landing page services actually pay less for Afternic sales, at least for lower-priced domains.

But it’s bad news for competition. It’s a blow to the many smaller domain sales businesses like Squadhelp and Efty. Domainers are penalized if they use these companies for landers but sell a domain on the Afternic network.

Afternic is also slowly winding down the ability to self-broker domains. Uni is already dead; you can expect this capability to go away on Dan.com, too.

It’s not all bad news, though. GoDaddy has introduced checkout links for Afternic listings that carry just a 5% commission when you find a buyer, similar to Dan’s program. Afternic also now offers lease-to-own transactions.

And if you sell a lot of domains on Afternic that are pointed to GoDaddy landers, you can save a lot of money. This year, I’ve saved thousands of dollars compared to the old 20% rate.

Post link: 2023 top stories: GoDaddy’s “commission alignment”

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

Related posts:
  1. GoDaddy to change aftermarket commissions on Feb 1
  2. Aftermarket alternatives to GoDaddy
  3. Lease to Own is finally coming to Afternic – here’s everything you need to know
Categories: Domains

ICANN debates action after community member’s antisemitic comments

Domain Name Wire - Wed, 12/27/2023 - 16:55

Organization says community member violated Expected Standards of Behavior.

ICANN is debating what to do after someone deeply entrenched in the domain name ecosystem made highly controversial remarks about Jews.

The issue came to light after ICANN community member Jeffrey Neuman sent a letter (pdf) (and follow up) highlighting comments made by Talal Abu-Ghazaleh. In a TV interview, Abu-Ghazaleh stated:

The Jews do not have any ideology. All they care about is money and interests. I had a friend who was a German cabinet member. I once asked him: ‘When Hitler, may God forgive him, carried out the Holocaust, why didn’t he finish the job and kill all the Jews?’ He said to me: ‘It’s the other way around, but don’t tell anyone I said this. He left a group of them on purpose, so that people would know why we carried out the Holocaust. When you would be tormented by them, you would know the reason.

Abu-Ghazaleh is a well-known intellectual property practitioner and founder of the Talal Abu-Ghazaleh Organization (TAG-Org). He has several interests connected to ICANN:

  • TAG-Org hosts an instance of ICANN’s L Root in Jordan
  • Two non-profits Abu Ghazaleh chairs formed the UDRP provider Arab Center for Dispute Resolution in Intellectual Property
  • He is affiliated with the ICANN-accredited registrar TAG-Domains
  • His law firm represents Complainants in UDRPs (and has a rather poor record)

In a response (pdf) to Neuman on December 26, ICANN interim CEO Sally Costerton called Abu-Ghazaleh’s comments “beyond offensive or objectionable” and that “We want to make it absolutely clear that hate speech has no place in ICANN’s multistakeholder process, and that Talal Abu Ghazaleh’s statements violate ICANN’s Expected Standards of Behavior.”

Costerton said that ICANN is trying to figure out how it can respond using ICANN’s policies and processes. ICANN has contacted Talal Abu-Ghazaleh and TAG-Org to inform them that the comments violate ICANN’s Expected Standards of Behavior and has referred the matter to ICANN’s Office of the Ombuds.

Post link: ICANN debates action after community member’s antisemitic comments

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

No related posts.

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