Abstract: An example embodiment for using a Partner Web Site within a Web Hosting Community starts with a Hosting Provider creating the Partner Web Site, a Community Web Site, and operating one or more Hosting Servers. A Partner, from the Partner Web Site, may make an application available for purchase and use to a plurality of Hosting Customers. At least one of the Hosting Customers, from the Community Web Site, may purchase and utilize the application with their Hosted Web Site.

Abstract: Systems of the present inventions allow for jointly auctioning expiring domain names. An example embodiment may comprise a server configured to: (1) determine whether a domain name's expiration date is within a predetermined timeframe (perhaps by searching a registered domain names database); and (2) contact the domain name's registrant to request an agreement to jointly sell the domain name and to share the resultant sales fee. The system also may comprise an expiring domain names database storing domain names having registrations expiring within the predetermined timeframe. A domain name sales website (that may list for sale some of the expiring domain names stored in the expiring names database) may be hosted on a server and a network may communicatively couple the server, registered domain name database, and expiring domain names database.

Abstract: Methods of the present inventions allow for jointly auctioning expiring domain names. An exemplary method may comprise determining (perhaps by a server) whether a domain name's registration may expire within a predetermined timeframe. If it is determined that the registration will expire within the timeframe, the domain name registrant may be contacted (prior to the domain name's expiration) to request an agreement to jointly sell the domain name and to share the resultant sales fee. If the parties agree, the domain name may then be sold (perhaps via a server) to a third party and the resultant fee may be shared with the registrant.

Abstract: Methods of the present inventions allow for generating a business card during domain name registration. An exemplary method may comprise the step of generating a business card containing information received during the process of registering a domain name to a registrant and, perhaps, providing the business card to the registrant. The information may comprise the registrant's name, title, address, telephone number, facsimile number, domain name, URL, email address, business name, business logo, and/or business tagline.

Abstract: Systems of the present inventions allow for generating a business card during domain name registration. An exemplary system may comprise a website (having one of more fields for receiving at least one requested domain name and a plurality of information from a prospective domain name registrant) hosted on at least one server, a domain name registration module running on at least one server and registering the domain name to the registrant (if available), a business card generation and delivery module running on at least one server and generating a business card containing some of the information received (if the domain name is registered to said registrant), and a network communicatively coupling the website, domain name registration module, and business card generation and delivery module.

Abstract: Methods and systems of the present invention allow for hosting a remote computer or server in a hosting provider's data center. An exemplary method may comprise the steps of resolving a registrant's domain name to access a remote computer or server via client software on a client. The remote computer or server may be storage area networked with additional computers and may access additional software via cloud computing.

Abstract: Systems and methods of the present invention allow for a thick client which may be provided with a domain name in a partnership between a hosting provider, an ISP and/or a thick client retailer. The client may be used to access a remote computer or server in the hosting provider's data center.

Abstract: Systems and methods of the present invention allow for a portal website further comprising an online community, storage areas, additional software, email access, etc. accessible via a direct access domain or links which manipulate a domain name to allow a registrant to access a remote computer or server in a hosting provider's data center.

Abstract: Systems and methods of the present invention allow for a thin client which may be provided with a domain name in a partnership between a hosting provider, an ISP and/or a thin client retailer. The client may be used to access a remote computer or server in the hosting provider's data center.

Abstract: Systems and processes of the present invention allow for tracking and publishing digital identity related reputation. In an example embodiment, a Digital Identity Provider maintains a database with reputation data that can be accessed by Requesters. The Digital Identity Provider may update reputation data based on a variety of events related to a digital identity. The reputation data may be tracked regarding the digital identity itself, digital identity purchaser or registrant, or an email address, domain name, URL, or website associated with the digital identity. The reputation data may include various categories, such as email practices, website content, privacy policies and practices, fraudulent activities, domain name related complaints, overall reputation, etc. The reputation data may be published in a publicly-available database, a private database, or via other methods. The Registrant may opt for a reputation service while registering a digital identity.

Abstract: Methods and systems of the present invention allow for displaying suggested concept-based results. An exemplary method may comprise the steps of receiving a combination domain name and top level domain (TLD), determining from ontological calculations suggested TLDs related to the concept of the combination and displaying the suggested combination of the domain name with suggested TLDs.

Abstract: Methods and systems of the present invention allow for displaying suggested concept-based results. An exemplary method may comprise the steps of receiving a domain name, determining from ontological calculations suggested domain names related to the concept of the domain name and displaying the suggested domain names.

Abstract: Methods and systems of the present invention allow for displaying suggested concept-based results. An exemplary method may comprise the steps of receiving search terms, determining from ontological calculations suggested search results related to the concept of the search terms and displaying the suggested search results.

Abstract: Methods and systems of the present invention allow for displaying suggested concept-based results. An exemplary method may comprise the steps of receiving targeted advertising information, determining from ontological calculations suggested keywords related to the concept of the targeted advertising information and displaying the suggested keywords.

Abstract: Systems and processes of the present invention allow for tracking and publishing digital identity related reputation. In an example embodiment, a Digital Identity Provider maintains a database with reputation data that can be accessed by Requesters. The Digital Identity Provider may update reputation data based on a variety of events related to a digital identity. The reputation data may be tracked regarding the digital identity itself, digital identity purchaser or registrant, or an email address, domain name, URL, or website associated with the digital identity. The reputation data may include various categories, such as email practices, website content, privacy policies and practices, fraudulent activities, domain name related complaints, overall reputation, etc. The reputation data may be published in a publicly-available database, a private database, or via other methods. The Registrant may opt for a reputation service while registering a digital identity.

Abstract: A Hosting Entity or another entity may provide a framework for collecting DNS Business Information from a Non-Controlling Party of a domain name and entering it into DNS. The framework may include a website, webpage, web service, web resource, software, API, or another technological solution suitable for collecting DNS Business Information from Non-Controlling Party. The website, webpage, web service, or the web resource may be located at URL associated with a Controlling Party's domain name, e.g. an active or a parked page for the domain name. DNS Business Information will be typically available for viewing to everyone along with the traditional DNS information.

Abstract: A Registering Entity or another entity may provide a framework for collecting WHOIS Business Information from a Non-Controlling Party of a domain name and entering it into WHOIS. The framework may include a website, webpage, web service, web resource, software, API, or another technological solution suitable for collecting WHOIS Business Information from Non-Controlling Party. The website, webpage, web service, or the web resource may be located at URL associated with a Controlling Party's domain name, e.g. an active or a parked page for the domain name. WHOIS Business Information will be typically available for viewing to everyone along with the traditional WHOIS information.

Abstract: A Hosting Entity or another entity may provide a framework for collecting DNS Business Information from a Controlling Party of a domain name and entering it into DNS. The framework may include a website, webpage, web service, web resource, software, API, or another technological solution suitable for collecting DNS Business Information from Controlling Party. The website, webpage, web service, or the web resource may be located at URL associated with a Controlling Party's domain name, e.g. an active or a parked page for the domain name. DNS Business Information will be typically available for viewing to everyone along with the traditional DNS information.

Abstract: Systems and methods of the present invention allow for tracking of domain name related reputation by a domain name Registering Entity (e.g. Registry, Registrar, etc.). In a preferred embodiment, the Registering Entity maintains a database with reputation data that can be accessed by the requesters. The Registering Entity may update reputation data based on a variety of events related to the domain name. The reputation data may be tracked on the domain name itself, URLs, domain name purchaser or registrant, or email addresses associated with the domain name. The reputation data may include various categories, such as email practices, website content, privacy policies and practices, fraudulent activities, domain name related complaints, overall reputation, etc. The registrant may opt for a reputation service while registering domain name. The requester may decide whether to allow email messages or to visit URLs based on the domain name related reputation.

Abstract: Systems and methods of the present invention allow for tracking of domain name related reputation by a domain name Registering Entity (e.g. Registry, Registrar, etc.). In a preferred embodiment, the Registering Entity maintains a database with reputation data that can be accessed by the requesters. The Registering Entity may update reputation data based on a variety of events related to the domain name. The reputation data may be tracked on the domain name itself, URLs, domain name purchaser or registrant, or email addresses associated with the domain name. The reputation data may include various categories, such as email practices, website content, privacy policies and practices, fraudulent activities, domain name related complaints, overall reputation, etc. The registrant may opt for a reputation service while registering domain name. The requester may decide whether to allow email messages or to visit URLs based on the domain name related reputation.