Name Intelligence: Difference between revisions
m added Category:Domainers using HotCat |
m removed Category:Companies using HotCat |
||
| (One intermediate revision by the same user not shown) | |||
| Line 33: | Line 33: | ||
{{reflist}} | {{reflist}} | ||
[[Category:Domainers]] | [[Category:Domainers]] | ||
[[Category:Intellectual Property Services]] | |||
Latest revision as of 19:19, 15 March 2021
 | |
| Type: | Privately held |
| Industry: | Internet |
| Founded: | 1999 |
| Founder(s): | Jay Westerdal & Ray Bero |
| Headquarters: | Bellevue, Washington |
| Country: | USA |
| Products: | DomainTools |
| Website: | Name Intelligence.com |
| Blog: | Domain Tools Blog |
| Key People | |
| Jay Westerdal, CEO & President
Ammar Kubba, CSO | |
Name Intelligence offers a variety of tools for domain management, solutions for centralized domaining, intellectual property protection, and a semantic name suggestion technology. In 2008, the company became a subsidiary of Thought Convergence, Inc., a company specializing in providing domain information, management, monetization and development tools and technologies for the domain name industry.[1]
Products & Services
The company's services include Reverse IP, an easy way to find all the .com, .net, .org, .biz, .us, and .info websites hosted on a given IP address; Whois History and Whois Search, which give access to a large database of historical Whois records; as well as Front Page Information, Indexed Data, Server Data, and Registry Data via DomainTools;[2] and Domain Insurance to protect the domainers from domain thefts.[3]
Name Intelligence also hosts the Domain Roundtable, an annual conference uniting domain industry professionals and tech savvy individuals focusing on domain assets and new technologies and products in the online marketplace.[4]
Name Intelligence and ICANN
In 2005, Jay Westerdal, CEO of Name Intelligence, wrote to ICANN president Paul Twomey and shared comments regarding the re-bidding process of the .net gTLD, Westerdall stated that "It is not an appropriate time to change the vendor servicing the .net gTLD without creating an adverse impact to what is currently a stable and predictable resource, and that it might be a more responsible, pragmatic, and appropriate course of action to reconsider the vendor at the next contact renewal option".[5]