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: Disclosed systems and methods provide for tracking of domain name related reputation by a domain name Registering Entity (e.g. Registry, Registrar, Reseller, etc.). The Registering Entity maintains a database with reputation data that can be accessed by the requesters. A domain name may be registered through the Registering Entity or a third party. 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, digital certificates associated with the domain name, overall reputation, etc. The reputation data may be digitally signed for authenticity. The requester may decide whether to allow email messages or to visit URLs based on the domain name related reputation.

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: Methods of the present invention provide multiple online data management solutions. An exemplary method may comprise networking a plurality of servers within a datacenter, wherein at least one server is running a software-enabled data management service comprising an email security service; a managed datacenter service; a shared exchange hosting service; a storage, recovery, and backup service; a network security service; a customer relationship management service; a human resources management service; a financial system management service; and/or a collaboration software service. Each server may be communicatively coupled to a network. A control panel also may be provided, which may be hosted on at least one of the servers. The control panel may comprise a plurality of tools for managing the software-enabled data management services.

Abstract: Systems of the present inventions provide a control panel for managing multiple online data management solutions. An exemplary system may comprise a control panel hosted on at least one server communicatively coupled to a network, wherein the control panel may be accessible to a customer via a client that is also communicatively coupled to the network. The control panel may comprise a plurality of tools for managing an email security service; a managed datacenter service; an exchange hosting service; a storage, recovery, and backup service; a network security service; a customer relationship management service; a human resources management service; a financial system management service; and/or a collaboration software service.

Abstract: Systems of the present inventions allow for hosting multiple online data management solutions in a datacenter. An exemplary system may comprise a plurality of servers located in a datacenter, wherein the servers may be communicatively coupled to a network, and at least one server may be running an email security service; a managed datacenter service; an exchange hosting service; a storage, recovery, and backup service; a network security service; a customer relationship management service; a human resources management service; a financial system management service; and/or a collaboration software service.

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: 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: 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.

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: Email senders may transmit emails over the internet to a mail server that handles emails for a plurality of users (clients). The mail server may use a spam filter to remove the spam and then transmit the filtered emails to the addressed clients. The spam filter may use a white list, black list, probability filter and keyword filter. The probability filter may use a user mail corpus and a user spam corpus for creating a user probability table that lists tokens and the probability that an email is a spam if the email contains the token. The probability filter may also use a general mail corpus and a general spam corpus for creating a general probability table that. Tokens of incoming emails may be searched for in the user probability table, and if not found, the general probability table to calculate the probability that the email is a spam.

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: An example embodiment of a Community Web Site includes a Home Page, a Web Presence Tool Page, and a Product and Community Forum which is created and maintained by a Hosting Provider. The Home Page may be made accessible to Hosting Customers and Partners and is an ideal location for placement of ads since all members of the Web Hosting Community are funneled through this Web page. The Web Presence Tool Page may display information generated by a Partner regarding the Partner's application which may be viewed by the Hosting Customers. The Product and Community Forum may allow the Hosting Customers to share information regarding all the applications with other Hosting Customers.

Abstract: An example of a certification process for an application to be made available to a plurality of Hosting Customers within a Web Hosting Community starts with a partner, from a Partner Web Site, submitting the application to a Hosting Provider. The Hosting Provider may perform a test on the application to verify the application conforms to a predetermined standard. The Hosting Provider may perform one or more manual or automated test and look for viruses, worms, Trojen horses, adware, malware, reliability/compatibility issues or other problems with the application that may adversely impact the Web Hosting Community. If the application passes the test, the Hosting Provider may make the application available to the plurality of Hosting Customers. In preferred embodiments, the Hosting Customer may purchase the application thereby triggering the Hosting Provider to automatically make the application available for use by the Hosting Customer's Hosted Web Site.

Abstract: An example embodiment of a Web Hosting Community includes at least three members, i.e. a Hosting Provider, a Hosting Customer and a Partner. The Hosting Provider may have one or more Hosting Servers, and create and maintain a Partner Web Site and a Community Web Site. The Partner Web Site and the Community Web Site may provide tools that are tailored for the needs of the Partner and the Hosting Customer, respectively, to participate in the Web Hosting Community. The Partner may provide an application, i.e. software program, to be integrated into the Web Hosting Community and the Hosting Customer may purchase and install the application onto its Hosted Web Site, which is stored on a Hosting Server.