Even when you register and pay for your domain name, you won't necessarily be able to use the name for several hours or even a few days. The domain must propagate, meaning that the official domain name registry must be updated with your website's Domain Name System information. That's something that occurs on the backend without any need of input from you.
With over 25 million .com domains registered with Google alone, this top-level domain is by far the most popular choice worldwide. According to the domain marketplace Sedo, the average sales price for a .com domain name during the second quarter of 2015 was 4,701 dollars. The most expensive publicly traded domain names have been known to fetch eight-figures. But don’t quit your day job just yet: such sales are the exception rather than the rule.
A domain name registration is simply reserving your website's name for a specified period of time. The two parties involved with a domain registration are generally the user who is registering the domain and the domain registrar. The domain registrant is the user who actually registers the domain name and the domain registrar is the company who helps that user with their domain registration.
While numbers like the ones seen above are impressive, most domains sell for significantly less extravagant prices and are generally in the two or three-digit range. Not long ago, those who were able to secure general terms (like icecream.com or pizza.com) not protected by trademark rights often found themselves sitting on virtual gold mines. The glory days of this boom have long since passed, and those looking for a profit in today’s market need a keen sense for coming trends.
General Data Protection Regulation (GDPR) will be enforced by the European Union (EU) on May 25th, 2018. The GDPR is a strict set of rules centered around customer privacy. Internet Corporation For Assigned Names and Numbers (ICANN) has released a temporary standard to comply with GDPR while it negotiates with GDPR. As of the 25th, Oracle will remove the contact information from it’s whois server to comply with the GDPR as a temporary measure until the full ICANN standard is released.
Just days after Verisign launched the Site Finder Service, ICANN wrote a strongly worded letter ordering them to disable it. Verisign complied, but not without writing a strongly worded letter of their own, in the form of a lawsuit. Verisign argued that ICANN overstepped their bounds in trying to control their activities, and ICANN argued… that Verisign overstepped their bounds in performing those activities.