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.

Will .Amazon ever see the light of day? There’s some movement.

Domain Name Wire - Wed, 09/19/2018 - 13:59

Amazon region countries reject $5 million gift card but ICANN pushes forward to help Amazon.com get .Amazon top level domain name.

Amazon.com’s (NASDAQ: AMZN) long battle to get rights to run the .Amazon top level domain name might still pay off, but countries that are part of the Amazon region continue to play hardball.

On Sunday, ICANN’s board resolved to have ICANN continue serve as a sort of mediator between countries such as Brazil and Peru and the United States’ second most valuable company.  It wants ICANN to come back with a proposal that will allow the region and company to essentially share the top level domain.

Amazon.com applied to run the .amazon domain name as part of the 2014 top level domain name expansion. It was one of 76 domains the company applied for. Some of the domains were generic in nature, and others were branded domains like .AWS.

Brazil and Peru filed an “early warning” through the ICANN Governmental Advisory Committee (GAC) saying that it was opposed to the application for .Amazon. It argued:

[g]ranting exclusive rights to this specific gTLD to a private company would prevent the use of this domain for the purposes of public interest related to the protection, promotion and awareness raising on issues related to the Amazon biome. It would also hinder the possibility of use of this domain to congregate web pages related to the population inhabiting that geographical region.

(No mention was made to how the region has been hurt by the ecommerce company owning Amazon.com.)

The GAC provided official advice to ICANN that it didn’t approve of the .Amazon domain application, and ICANN rejected Amazon.com’s application as a result.

Amazon.com then tried to work with the member states of the Amazon Cooperation Treaty Organization (ACTO). Its negotiations failed, and Amazon.com filed for Independent Review of the decision to reject its application. It won that review.

Since then, the company has continued to work with the ACTO to come up with a solution that makes them it comfortable. Its latest proposal includes reserving domains the ACTO would like held back, helping ACTO create a website to promote the region (and funding it), and giving a big, fat $5 million gift card to ACTO member states.

Still, no dice.

The board now wants ICANN to present it with a proposal that will let Amazon.com use the domain for its business purposes but appease ACTO members.

In a battle of hard-headed governments vs. the U.S.’s second biggest company, delay is the big winner.

 

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

Related posts:
  1. Amazon wins: .Shop and .通販 not confusingly similar after all
  2. Amazon.com gets big win in domain battle, may yet get .Amazon domain
  3. If .amazon is killed, will Amazon bail on the new TLD program?
Categories: Domains

15 more end user sales up to $25K

Domain Name Wire - Wed, 09/19/2018 - 13:27

Several web design and development companies, a personal finance service provider, a British boutique law firm and a healthcare service comparison tool bought domain names last week.

It was a solid week for end user domain sales as Sedo. Sudden.com was the top end user sale this week (that I could identify) at nearly $25K, but it remains to be seen what the web service provider who purchased this will use it for. The overall top sale of the week actually went  qnet.org at $27,250 but I wasn’t able to pinpoint the end user for this domain yet.

(You can view previous lists like this here.)

Sudden.com $24,950 – Bought by Electronic Creations Corporation which is a website creation and management service provider. This could be for a new project but for now this page has a “Coming Soon” message saying the website is currently undergoing a major re-design and expansion.

BestMind.com $15,000 – This domain is registered to Shanda Interactive Entertainment Limited, which is a Shanghai-based online publisher of books and games. In 2017 they were acquired by the Zhejiang Century Huatong Group.

Paybit.eu €10,450 – The domain isn’t resolving yet but there is a cryptocurrency payment processing service by the name of Pay Bit who uses PayBit.com. This might be part of an expansion or brand protection. Paybit.de previously sold on Sedo for $27,915.

PB.co.uk £8,400 – This two letter ccTLD already has a fully functioning site up and running for a boutique law firm based in Horsham specializing in intellectual property and business law.

Smile.direct €6,000 – Whois is redacted due to GDPR but I couldn’t help associating the name with the heavily advertised Smile Direct Club which currently uses SmileDirectClub.com. Maybe they will adopt this shorter domain name in the future. SmileDirect(.)com is also in use (NSFW).

Jass.com $5,199 – This site was bought by RAR Info Solutions LTD, an online SEO, PPC, Web Design and Development agency. There’s nothing on their site about Jass but maybe this could be a new product or service or for a client.

HappyScore.com $5,000 – This domain currently forwards to HappyMoney.com, the site of a financial company called Happy Money that used to be called Payoff. It doesn’t appear to be associated with the book of the same name. The company offers services under the name Happy Money Score.

VO1.com $5,000 – VO1, Ltd in the UK.

Trasna.com €4,500 – Purchased by the Oases Health Group, a European healthcare service provider and online comparison tool to arrange for health care services across different EU countries.

Print-Point.de €4,000- Purchased by the German print company Print.point, which currently used the address nichtrumdrucksen.de. That’s a play on the words Drucken=print, and drucksen means “hum and haw”. I’d say this new domain is an improvement, even with the hyphen (which is common in Germany). This domain currently has a “Coming Soon” sign up in German.

Taihing.com $3,500 – Whois is showing the registrant as Black Media Group, which is a web design firm out of Hong Kong. Tai Hing is also the oldest existing public housing estate in the Tuen Mun neighborhood, but it’s not clear if there’s a connection between the web design firm and this domain.

JoyMade.com $3,000 – Organic foods company Hain Celestial Group has a large assortment of natural food brands under its umbrella. Maybe Joy Made is the next brand launching?

Swipe.ch $2,888 – Has a coming soon sign up but this could be the Swiss landing page for Swipe, a service that allows presentations to be made mobile friendly in an easy streamlined process. They use the domain Swipe.to.

Apotheken-Inventur.de €2,500 – The Germany company Behning bought this domain and it appears they will use it to offer inventory assessments for pharmacies to save them time and HR resources.

PCBSoftware.com $2,000 – PCB Software s.r.o. PCB is the name for electronic design automation software.

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

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

Giuseppe Graziano launches three-letter domain marketplace

Domain Name Wire - Tue, 09/18/2018 - 18:30

New domain marketplace is dedicated to just 17,576 possible domains.

Giuseppe Graziano, a domain broker who runs GGRG.com, has launched a new marketplace for buying and selling three-letter .com domain names.

GGRG.com has always specialized in short domain names, so Liquid Domain Market Exchange is right up its alley. Still, can a marketplace dedicated to a maximum pool of 17,576 possible listings work?

If you want instant liquidity, it probably will. During the beta period, a domain owner sold his domain within 15 minutes of setting his price.

Graziano says the marketplace is not for selling domains to end users, so sellers need to price their domains with domain investors in mind.

Premium account holders can set up alerts to quickly know when a domain that meets their requirements is listed. A premium account is free for the remainder of 2018 if you sign up by September 25.

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

Related posts:
  1. Why Sonic.net rebranded as Sonic, and how it got Sonic.com
  2. Trump is still trending…in .com
Categories: Domains

Domain name sinkholes and those funky domain registrations

Domain Name Wire - Tue, 09/18/2018 - 17:06

Sinkholes are why you see companies register a bunch of weird domain names.

A different kind of sinkhole.

Palo Alto Networks Inc was granted a patent today related to domain sinkholing, and it’s a continuation patent of one that was granted in 2016.

It reminded me of times I’ve seen companies (notably Microsoft) register a bunch of nonsensical domain names. Why would a company register a lot of domains with random digits and letters?

The answer is often that it’s a sinkhole.

A sinkhole redirects or blocks traffic meant for a destination. They are used by the security community to stop botnet traffic, phishing and other bad activity.

There are many ways to create a sinkhole. An ISP can simply divert traffic from the IP address nameserver you see in Whois to another. A company (or the government) can also go through the courts to get control of a domain name and then change its nameservers.

Some malware campaigns continually register new domain names as their other names get snuffed out and blocked by security companies. It’s sometimes possible to figure out what the future domain registrations will be, and that’s when you might see a company register a huge list of odd domain names. They know what domains the malware will register next, so the company registers the domains to prevent them from being registered by the bad guys.

A famous example of registering a domain to stop an attack was the domain name iuqerfsodp9ifjaposdfjhgosurijfaewrwergwea(.)com. A person researching the WannaCry ransomware noticed this domain in the malware and registered it. It turns out that registering the domain acted as a killswitch. The malware was programmed to check in on this domain and stop if the domain was registered.

While the WannaCry example isn’t a typical sinkhole, it’s interesting to think about how domain names are used to propagate malware and botnets, and how registering domains can thwart the bad guys.

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

Related posts:
  1. The Weakest Security Link is You
  2. This week’s new TLDs: 3 more from XYZ
  3. Secure your accounts better with a U2F security key
Categories: Domains

ICANN loses in German court (again)

Domain Name Wire - Tue, 09/18/2018 - 14:01

Attempts to get an injunction forcing a German registrar to collect certain Whois data are failing.

ICANN has yet again failed to convince German courts that an injunction is needed to force domain name registrar EPAG to continue collecting certain information for Whois.

The non-profit domain name overseer sued EPAG, part of Tucows, the day the EU’s General Data Protection Regulation (GDPR) went into effect. EPAG had informed ICANN it would no longer collect Administrative and Technical contact data for Whois because of its interpretation of GDPR.

EPAG’s arguments included that it didn’t necessarily have a contractual relationship with the Admin or Tech contacts and that it was still collecting the registrant information.

The court denied the injunction and ICANN has gone through several appeals processes, bouncing between the courts.

In light of yet another ruling from an appeals court, ICANN said that it was limited to the issue of the necessity of an injunction.

Tucows CEO Elliot Noss has said that the lawsuit isn’t really adversarial. Both ICANN and Tucows no doubt believe they are correct but would welcome some clarification from the courts on how GDPR applies to Whois.

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

Related posts:
  1. ICANN files legal action against Tucows registrar over GDPR
  2. Tucows responds to ICANN legal action related to GDPR
  3. German court denies injunction against Tucows’ registrar EPAG over GDPR
Categories: Domains

UDRP has its limits when it comes to taking down counterfeit websites

Domain Name Wire - Tue, 09/18/2018 - 12:28

Even if the domain owner is doing a bad thing, UDRP can only be used if all three prongs of the policy are met.

This website looks like that of Zimmermann, even showing a picture of one of its storefronts. It’s a fake, but UDRP isn’t the appropriate way to take it down.

The Uniform Domain Name Dispute Resolution Policy (UDRP) is a good tool to take over cybersquatted domain names. These names are often being used for nefarious purposes such as phishing or selling counterfeit goods.

One such case involving counterfeit goods that was just decided by National Arbitration Forum shows the limits of using UDRP to take down a site: you still have to prove that the domain is cybersquatting under the three prongs of UDRP.

The case was filed by Australian clothier Zimmermann Wear Pty Ltd against ZimOutlet(.)com. There’s no question that the domain owner is up to no good. The site is made to look like the clothing company and is allegedly shipping counterfeit goods when someone orders.

The problem is that Zimmermann and Zim aren’t that similar. Panelist David E. Sorkin did a good job comparing this case to others in which only part of the trademark was used in the domain:

Although Complainant has not offered any authority on this issue, the Panel has considered various decisions under the Policy involving domain names that incorporate the first few letters of a longer mark. In Fuji Photo Film U.S.A., Inc. v. Center for Ban on Drugs, D2004-0970 (WIPO Feb. 25, 2005), the Panel found fujfilm.com to be confusingly similar to FUJI, on the grounds that it combined the first three letters of the four-letter mark—”essentially the entirety of Complainant’s mark”—with a generic term for the complainant’s principal product. Similarly, in Chevron Intellectual Property LLC v. Linda Hearn, FA 1409285 (Forum Nov. 15, 2011), the Panel found chevoil.com to be confusingly similar to CHEVRON, combining the first four letters of the mark with a term descriptive of the complainant’s products and services. In Tesco Stores Ltd. v. Mat Feakins, DCO2013-0017 (WIPO Oct. 4, 2013), the Panel found tes.co to be confusingly similar to TESCO, even though the second-level component of the domain name corresponded to only the first three letters of the mark, on the grounds that the domain name taken in its entirety was identical to the complete mark but for the intervening dot.

Confusing similarity is particularly likely to be found where a mark is commonly referred to by its first syllable, and of course where the complainant also possesses trademark rights in the truncated form of the mark. See, e.g., Supercell Oy v. WhoisProxy.com Ltd / Jordan Rash, Application Automation LLC, D2015-1445 (finding clashbot.org confusingly similar to CLASH OF CLANS, based upon evidence that the mark is often abbreviated to “CLASH”); Caterpillar Inc. v. Jonathan Scandreth, FA 1348137 (Forum Nov. 8, 2010) (finding cataxles.com and other domain names confusingly similar to CAT and CATERPILLAR, based upon registered trademark rights in both forms of the mark); Anheuser-Busch Inc v. Dot Com Internet Solutions, D2001-0500 (WIPO June 13, 2001) (finding budcommercials.com and other domain names confusingly similar to BUD and BUDWEISER, based upon registered trademark rights in both forms of the mark).

The decisions cited above are all distinguishable from the present matter. The disputed domain name incorporates only three letters of a ten-letter trademark. While those letters correspond to the first syllable of the mark, it is not clear that they serve as the distinctive or dominant aspect of the mark. Complainant has not claimed that it has rights in ZIM or that its ZIMMERMANN mark is commonly referred to in this truncated manner. (Indeed, a cursory Google search for “zim” would likely lead one to conclude that these letters standing alone almost never refer to Complainant.) Nor does the generic term “outlet” that the domain name appends to these three letters bear any obvious connection to Complainant or its products; an “outlet” could be a discounter or retailer of virtually any sort of products.

It’s quite clear that the domain owner is doing a bad thing. Sometimes panelists make the wrong decision for the right reason, effectively trying to remedy a wrong using UDRP. But it’s important for panelists to apply the same standards across all cases. Kudos to Sorkin for his decision in this case.

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

Related posts:
  1. Twitter finally gets Twiter.com domain it won in dispute
  2. Reverse domain name hijacking in Hakoba Saree case
  3. PCO.com saved in UDRP despite no-show by domain owner
Categories: Domains

Rob Monster exits DigitalTown, George Nagy takes over CEO role

Domain Name Wire - Mon, 09/17/2018 - 18:46

Rob Monster has left DigitalTown.

Monster pares CEO roles down to one.

Rob Monster has resigned as CEO of DigitalTown, a company that provides community building platforms. The company owns a large portfolio of domain names, including 11,000 .city domain names.

Monster told Domain name Wire that the move has been planned for a while. In an email, he said that new CEO George Nagy, who was the COO, “brings significant experience with running and selling public companies and with working with institutional investors, both which will be highly relevant for the next phase.”

He was CEO of both DigitalTown and domain name company Epik. He will now have more time to focus on Epik and other endeavors.

He noted:

As a general statement, my competency leans more toward vision, strategy and corporate development. Over the last 2.5 years, we completed 7 acquisitions with which we assembled the technology and team that has allowed us to start rollout of DigitalTown around the world as well as secure deals with both private developers and government clients.

Blockchain, Crypto and Decentralized Apps are a logical response to the pattern of winner-take-all and the policies that allow it. Timing-wise, I believe the world is on the cusp of a major catalyzing event that will make DigitalTown a lot more relevant. The economic situations that are unfolding in Puerto Rico, Turkey, Venezuela and Argentina are not isolated events.

Looking ahead, I continue to be a significant DigitalTown shareholder with 18 million shares and to be an informal advisor. I have high hopes for George and the team we built. Epik continues to manage DigitalTown’s domain portfolio and will help accelerate progress on selling domains into the hands of end-users, an area that was lower priority while I was running both companies.

On the personal side, after 3 years of working 100 hour weeks while running 2 companies, I am looking forward to devoting more time to equipping Epik for the next phase. I also plan to devote more time to Christian ministry and philanthropy. My family doubts that I will slow down. Regardless I am taking a measured and Spirit-led approach to what comes next.

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

Related posts:
  1. Monster Venture Partners Closing Doors
Categories: Domains

ICANN #63 in Barcelona is next month

Domain Name Wire - Mon, 09/17/2018 - 17:54

Meeting will attract policymakers, registries, registrars and domain investors.

ICANN #63 takes place in Barcelona, Spain next month from October 20-25. I was on the fence about going but booked my travel over the weekend.

I find ICANN meetings to be a good place to catch up with registries, registrars, service providers and domainers in one place. I’ve heard lots of chatter from domain investors about going to this event, so it should be a good one to attend.

There will also be lots of continuing discussion about GDPR as it relates to domain names. Policy stuff might not be fun, but it has a huge impact on everyone in the business.

Details are here if you’re interested in attending. Nearby hotels are available starting at €185 per night and there is no cost to attend.

If you are going and want to meet up, please drop me a line.

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

No related posts.

Categories: Domains

XYZ files renewed motion for fees against Verisign

Domain Name Wire - Mon, 09/17/2018 - 17:06

District Court will reconsider request for Verisign to pay legal fees stemming from lawsuit.

After winning its second Appeals Court case against Verisign, top level domain name registry .XYZ is renewing its request (pdf) for Verisign to pay attorney fees.

Here’s the background:

Verisign (NASDAQ:VRSN) sued XYZ for false advertising. A federal district court granted summary judgment in XYZ’s favor, and XYZ asked the court to award it legal fees of over $1 million. Verisign then appealed the original case and lost the appeal. The federal district court then ruled against awarding legal fees (beyond about $57,000 related to discovery.)

XYZ appealed the attorney fees decision. In May, the Appeals Court agreed with XYZ that the lower court did not consider the motion for fees correctly. It wrote:

…we hold that a prevailing party need only prove an exceptional case by a preponderance of the evidence, rather than by clear and convincing evidence, as the district court below required. We further clarify that a prevailing party need not establish that the losing party acted in bad faith in order to prove an exceptional case.

That sent the case back to the lower court to apply the correct standard to XYZ’s motion for fees. On Saturday, XYZ filed its post-remand submission in support of its motion for fees.

XYZ gives a long list of reasons the case should be considered exceptional, including Verisign’s broad discovery requests, 25 depositions and 17 third-party subpoenas. XYZ wrote:

Why would a sophisticated company with competent legal counsel file such a flimsy case? XYZ said nothing about .com that hadn’t been said before, and Verisign’s own numbers showed .com registrations continued to grow even after XYZ’s statements. Why draw further attention to those statements by filing a lawsuit over them? Why drag that suit on as the odds of victory grew ever longer, all the while refusing to ever meaningfully discuss settlement? The reasonable inference is that Verisign’s primary motive wasn’t winning the lawsuit so much as sending a message, not only to XYZ but to all of the other new top-level domains that entered the market and presented Verisign with meaningful competition for the first time in decades.

The circumstantial evidence supports an inference that Verisign’s true motive in pursuing a claim this weak, this aggressively, was to drain XYZ’s resources, intimidate its principal, and send a message to its other new competitors. [redacted] Under these circumstances, fee-shifting is warranted to both deter such conduct going forward and to compensate XYZ for enduring, defending and defeating Verisign’s tenuous claims and faulty lawsuit.

XYZ spent over $1 million defending itself in the lawsuit.

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

Related posts:
  1. Judge: .XYZ statements were puffery and opinion
  2. .XYZ asks Verisign to pay $1.6 million in fees from lawsuit
  3. XYZ files opening brief in request for Verisign to pay $1.6 million
Categories: Domains

The Registry/Registrar Sales Channel with Jay Daley – DNW Podcast #202

Domain Name Wire - Mon, 09/17/2018 - 15:30

.Org operator is changing how it works with registrars.

Public Interest Registry (PIR), the group that operates the .org top level domain name, recently announced changes to how it’s approaching marketing through the domain name registrar channel. On today’s show, PIR interim President and CEO Jay Daley discusses why the organization is making these changes. Jay discusses the current state of registry marketing and sales through registrars, how we got here, and what might change in the future. It’s a great interview.

Also: AWS.com, DomainTools injunction, Sedo gets into expired domains, and Verisign’s (NASDAQ:VRSN) .com contract.

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

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

Related posts:
  1. The challenges of new TLDs with Tobias Sattler – DNW Podcast #177
  2. Sandeep Ramchandani, CEO of Radix – DNW Podcast #183
  3. All About .Me – DNW Podcast #191
Categories: Domains

New: “Like” comments on Domain Name Wire

Domain Name Wire - Thu, 09/13/2018 - 21:24

Now you can Like comments you read on Domain Name Wire.

Ever read a comment on Domain Name Wire that you agree with or find interesting? Now, in addition to adding your own reply or comment, you can Like the person’s comment.

Just look for the Like link underneath the comment:

In the future, I might feature comments that get more likes.

The Like feature is an experiment. Let me know if you think it’s useful or not.

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

No related posts.

Categories: Domains

Verisign files patent application for IDN domain searches

Domain Name Wire - Thu, 09/13/2018 - 15:20

Patent covers providing IDN translations and transliterations of ASCII searches.

.Com registry Verisign (NASDAQ: VRSN) has filed a U.S. patent application (pdf) for searching for internationalized domain names (IDN).

An IDN is a domain name that includes at least one non-ASCII character. Many top level domain names allow people to register domain names in languages with non-ASCII character sets, such as Arabic, Japanese and Russian. These domains can be registered in .com, and Verisign now offers some transliterations of .com to the right of the dot. (A transliteration of .com is essentially something that makes the same sound as ‘com’ in the language.)

The patent application describes a way to search for a word and see various translations and transliterations. For example, I might enter a search for ‘house’ in ASCII and the search would return translations and transliterations in other languages. I can see if the domains are available or registered.

It’s essentially a namespinner with a translation element. The graphic to the right is from the patent application.

Sumit Daryani and Craig Davies are listed as the inventors. The patent application was filed in March 2017 and published by the U.S. Patent and Trademark Office today.

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

Related posts:
  1. VeriSign Gets Patent Related to Internationalized Domain Names
  2. Verisign gets patent for Recovery of a Failed Registry
  3. Why getting patents is smart for domain name companies
Categories: Domains

Amazon buys AWS.com domain name

Domain Name Wire - Thu, 09/13/2018 - 13:36

Company gets coveted domain name for its cloud business.

Amazon.com (NASDAQ: AMZN) has acquired the domain name AWS.com, Whois records indicate.

Historical Whois records at DomainTools show that the domain was transferred to Amazon.com this week, between September 11 and September 12.

The domain name was owned by AWS Convergence Technologies, Inc. Although the corporate relationships are a bit convoluted, the seller appears to be part of a company called Earth Networks that runs the site WeatherBug.com. (That’s further convoluted by a company name of GroundTruth on the WeatherBug website).

The oldest Whois record at DomainTools dates to 2001, showing Automated Weather Source as the registrant. But data in the Whois records since then all show a common owner. The domain was registered in 1995.

Amazon’s cloud business is Amazon Web Services, or AWS for short. The company recently started using the dot-brand domain name .AWS in marketing. Although I’m sure it has coveted the AWS.com domain name for many years, I wonder if traffic to the domain has increased since it began marketing domain names like BuildOn.AWS.

AWS.com does not resolve as of this morning.

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

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

New Zealand’s .Nz namespace gets preliminary injuction against DomainTools

Domain Name Wire - Thu, 09/13/2018 - 00:41

Judge orders DomainTools to cease collecting and publishing .nz Whois records.

Domain Name Commission (DNC), the organization that manages New Zealand’s .nz domain name, has won a big victory against DomainTools.

U.S. District Judge Robert S. Lasnik has granted DNC’s motion for preliminary injunction against DomainTools. DNC alleged that DomainTools collected and published .nz Whois records in violation of DNC’s terms of use. DomainTools’ business model relies (in part) on aggregating domain name ownership data from Whois databases.

Lasnik ordered DomainTools to stop accessing .nz Whois records and to remove any publication of the records while the lawsuit proceeds. He did not seem sympathetic to any of DomainTools’ arguments. In one particularly damning paragraph, Lasnik wrote:

Finally, defendant argues that a preliminary injunction in this case could start an avalanche of litigation as other registers attempt to protect the privacy of their registrants. If defendant built a business by downloading, storing, and using data from other registers in violation of the terms that governed its access to that data, defendant may be correct – other
registers may be encouraged to pursue a breach of contract claim if plaintiff is successful here. It would be ironic, however, if a plaintiff who has shown a likelihood of success and irreparable injury were deprived of preliminary relief simply because defendant may have acted wrongfully toward others as well.

DomainTools is already facing headwinds thanks to the European Union’s GDPR, which has resulted in domain registrars ceasing to publish Whois records.

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

Related posts:
  1. U.S. Gov: Whois info must remain available
  2. Whois GDPR carnage continues: Afilias to ditch almost all data in Whois on millions of domains
  3. GDPR will make domain name transfers more difficult
Categories: Domains

Google News is not the publisher’s foe

Domain Name Wire - Wed, 09/12/2018 - 16:46

Google News is the bogeyman of many publishers, but it shouldn’t be.

The European Union is at it again, trying to muck up the web with new regulations.

This time it’s new copyright rules.

As an online publisher, I’m certainly frustrated by copyright infringement. But the EU’s rules are designed more to attack innovative internet companies.

One particularly controversial rule is dubbed the “link tax”. It seems squarely aimed at Google News and would charge Google for including a snippet from news stories in Google News.

For small publishers like me, Google News is a savior. It helps surface my stories to a large audience including many other journalists who sometimes pick up my stories and link to them. The idea of charging Google to send me traffic is asinine.

Big publications might be frustrated that people treat Google News as their news destination rather than going directly to the news site’s homepage. But there are huge societal benefits to this. I get much more diverse viewpoints on Google News than I do on a news site, whether that’s MSNBC or Fox News.

What happens when a “link tax” gets applied in a country? Google News shuts down, hurting many publishers.

The EU’s rules will probably hurt all publishers, but they will particularly impact small publishers. It’s the upstarts that should be protected, not the dinosaurs.

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

No related posts.

Categories: Domains

14 end user domain names sales up to $30,500

Domain Name Wire - Wed, 09/12/2018 - 13:27

An IT Company, a fruit distributor, and an eyewear manufacturer bought domain names last week.

It was a busy week for sales at Sedo with lots of diverse end users in the mix including international companies, many based in Sedo’s headquarter country of Germany. The top sale of the week was bad.de at €119,000, but it’s not yet clear who bought the domain name.

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

EBF.Com $30,500 – German IT Consultant EBF specializes in management and safeguarding of mobile end devices for companies in the DACH region (Germany, Austria, Switzerland).
The domain forwards to the .DE of this domain.

Fyat.com €12,075 – The title of the “coming soon” page says it’s “Everyone’s Exchange”. This could potentially be a cryptocurrency related site.

Namensaufkleber.de €8,400 – Currently forwards to namensetiketten.de, a German site for customized label making.

Webschmoeker.de €7,500 – A Germany-based web designer.

ERCE.com €5,900 – ERCE Energy is an oil & gas company. The domain forwards to its website at ERCE.energy.

Hakkipilke.com €5,322 – HakkiPilke makes firewood processing equipment in Finland. The domain forwards to the company’s matching .FI domain.

XNDO.com €5,000 – Xndo is a health food and supplements company. The domain forwards to the company’s existing .net domain.

Win.gg $5,000 – Forwards to winesports.com, but they may be shifting to this shorter domain in the future or it could be used as a URL shortener. The site boasts that they are “the next big thing in esports media” with coverage of the biggest games in esports, including League of Legends, Counter-Strike: Global Offensive, Dota 2, and Overwatch.

Bussgeld-Katalog.de €3,500 – Forwards to geblitzt.de, which provides legal services for traffic offenders in Germany.

Trendworthy.com $3,000 – The domain now resolves to a page with trending news stories.

FixNetwork.com $3,200 – A Canadian company called MondoFix inc. bought the domain. The company owns hundreds of auto repair shops.

Regalin.com $3,001- An upgrade from a hyphenated version: Regal-In.com for this French fruit distributor specializing in peaches, nectarines, apricots, cherries and apples.

Forecastable.com $2,500 – A coming soon page on the site says “Enterprise Account-Based Selling Will Never be the Same”.

DeerOptics.com $2,353 – Appears to be a rebranding of an eyewear company previously called MN Optics, the exact same site is also on MNOptics.com.

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

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

How much would .Com domains cost if .com went out to bid?

Domain Name Wire - Tue, 09/11/2018 - 16:05

Consumers pay over a half billion dollars more than necessary each year to register .com domains.

Verisign (NASDAQ: VRSN) is currently in negotiations with the U.S. Department of Commerce with regards to the Cooperative Agreement to run the .com domain name. The agreement expires November 30 of this year. The Department of Commerce has the sole discretion to extend the term of the agreement.

It’s the Department of Commerce, through the Cooperative Agreement, that effectively sets price controls on registrations and renewals .com. Verisign has a contract with ICANN for running the domain but the Cooperative Agreement can mandate price controls in the ICANN agreement. In the past, ICANN granted Verisign the ability to raise prices in .com. The DOC stepped in and froze the amount Verisign charges registrars at $7.85 per domain per year.

Verisign also has a presumptive right of renewal with ICANN for the .com contract. It got this right after negotiations with ICANN following a lawsuit. Unless Verisign really messes up, or if there’s an antitrust ruling, Verisign gets to run .com in perpetuity.

So in some ways, considering what the cost of .com would be if the contract was put out to bid is a pointless exercise. However, it’s relevant to the Department of Commerce and National Telecommunications and Information Administration (NTIA) as they consider what to do with the Cooperative Agreement.

Verisign’s business

Verisign’s business is effectively an exclusive contract to run .com. (While it also runs .net and a handful of other top level domains, its business is built on .com.) It has extremely high margins and these margins are akin to a tax on consumers around the world.

Let’s take a look at the margins.

In 2017, Verisign had a gross margin of 83.4% and an operating margin of 60.7%.

These numbers are staggering. According to CSIMarket, the S&P 500 combined gross margin is typically in the mid-40% range and operating margins are in the mid-teens. CSIMarket shows that gross margins for communications services companies are near 80%. But the operating margin of these companies is still typically in the teens.

Verisign is printing money. Every additional domain that is registered drops directly to the bottom line after paying ICANN 25 cents.

That’s why investors love the company. Even as the S&P 500 and tech sector valuations have skyrocketed, Verisign has outpaced them.

A chart of Verisign’s stock returns from the company’s 2017 annual report.

A fair price

How much would a competitor bid to run .com? It would certainly be lower than $7.85.

Consider a recent bid to manage the registry for India’s .in domain name. According to MoneyControl, Neustar bid just 70 cents per domain. Its rival Afilias offered to run it for $1.65 per domain.

These are competent registry operators. Neustar runs .us, .biz and .co. Afilias runs .info and .au. These companies also manage the registries for hundreds of other top level domains.

While .com comes with challenges of scale, it also benefits from economies of scale.

Now, consider what the above-market contract with Verisign means for consumers. Let’s be generous and say that the best competent bid to run .com would be $3.50 per name. With 137 million .com domains currently registered, that means consumers across the globe are paying about $600 million in extra fees per year than necessary. That amount only grows if Verisign gets the right to increase prices.

That’s a big tax on the world’s consumers that exists primarily because the .com contract can’t be put out to bid. It’s not a market-price situation.

That’s where the Department of Commerce needs to step in. With the Cooperative Agreement, it is the only entity that can control the price of .com domain names. It should exercise this power.

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

Related posts:
  1. IANA transition will not remove government relationship with .com contract
  2. Verisign patents “Methods and systems for creating new domains”
  3. VeriSign Loses Money (Sort Of) as .Com and .Net Top 105 Million
Categories: Domains

1&1 sends expired domain names to Sedo

Domain Name Wire - Tue, 09/11/2018 - 15:23

New arrangement sends domains to Sedo before SnapNames.

Domain name registrar 1&1 has begun sending expired domain names to Sedo as a preliminary stop through the expiration cycle.

The domain names are listed for sale on Sedo in a special category with starting bids at $79.00.

1&1 is continuing to partner with SnapNames for expired domains, but Sedo is the first stop. Domains that don’t sell at Sedo are then sent through SnapNames.

Sending the domain names to Sedo first could expose expiring domain names to more end users.

1&1 and Sedo are part of the same family of companies. However, the companies just recently started working more closely together. 1&1 didn’t join Sedo’s aftermarket syndication network until just last year.

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

Related posts:
  1. Sedo and Pool Explain Employee Policies for Bidding
  2. Recap: Domain Name Auction Firestorm
  3. Site Finds “Orphaned” Domains on Sedo and Afternic
Categories: Domains

PIR (.org) makes changes to its sales practices

Domain Name Wire - Mon, 09/10/2018 - 18:19

No more volume discounts, focus on quality over quantity.

Public Interest Registry (PIR), the non-profit registry that runs the .org top level domain name, is making changes to how it markets its domains.

Jay Daley, Interim President and CEO of PIR, said in a blog post that the organization is nixing volume discounts. These discounts are only attainable by the largest registrars; new incentives and rebates will be designed so that all registrars can participate.

It will also start judging results by more than just registration numbers. It will look at how domains are used in an effort to favor positive use and avoid spam and other nefarious uses.

Reading between the lines, it also appears that the company will stop participating in pay-for-placement deals with registrars in which it takes on all of the risk.

Daley admits that its headline domain stats might dip in the short term as a result of these changes.

He says the changes mean the organization is moving from a sales-led organization to a marketing-led organization. The company has made several marketing hires as a result.

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

Related posts:
  1. .Org sticks with Afilias for backend
  2. .Org non-profit is looking for new members of Board of Directors
  3. Donuts appoints outside director, new CFO
Categories: Domains

The limits of using UDRP for personal names

Domain Name Wire - Mon, 09/10/2018 - 16:44

Does your personal name function as a trademark?

Celebrities and well-known people can use the Uniform Domain Name Dispute Resolution Policy to go after cybersquatters who use their names in domain names. But this has limits; the name must function as a common law or unregistered trademark (or be a registered trademark).

This can be difficult to prove, especially if the person filing the dispute is not a major media celebrity.

Consider the case of MaryPfaffko(.)com, in which the Complainant has a long career in wildlife biology and policy. The registrant of the domain name appears to have a personal vendetta against the Complainant.

World Intellectual Property Organization panelist Georges Nahitchevansky found that there wasn’t enough evidence to show that the Complainant has common law trademark rights in the name. He noted that UDRP is limited in scope and that the complaint would be better served in the courts:

The Panel wants to make clear that it takes no pleasure in reaching this decision. Hijacking the name of another for purposes of furthering what appears to be a personal vendetta is likely an abusive practice. However, the scope of the Policy is a narrow one and is meant to provide appropriate relief to a party that has rights in a trademark and not to address matters such as defamation or other torts that are outside the scope of the Policy. Such abusive practices would be better addressed in a court action and not through the UDRP.

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

No related posts.

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