Abstract: The present inventions may be implemented by tools enabling preferred domain positioning on a registration website. An example may comprise a computer-readable media storing instructions that, when executed by a server computer, cause the server to receive a bid from a registry seeking such preferred placement for a domain (that may be administered by the registry), generate a quality score for the domain, and determine the preferred placement based upon the bid and the quality score.

Abstract: Methods of the present inventions allow for determining preferred domain positioning on a registration website. An exemplary method may comprise the steps of receiving a bid from a registry seeking such preferred placement for a domain that may be administered by the registry, generating a quality score for the domain, and determining the preferred placement based upon the bid and the quality score.

Abstract: Methods of the present inventions allow for providing a preferred domain position on a registration website. An exemplary method may comprise receiving a request from a registrar, which may comprise a bid that the registrar had previously received from a registry seeking a preferred placement on a domain registration website for a domain administered by the registry. The method may further comprise generating a quality score for the domain, determining (based upon the bid and the quality score) a preferred placement for the domain, and transmitting the preferred placement to the registrar.

Abstract: Systems of the present inventions allow for providing customer-selected solutions for multiple datacenter website hosting. An exemplary system may comprise a first datacenter comprising at least one hosting server, a second datacenter comprising at least one hosting server, and a hosting services website hosted on at least one customer interaction server. The hosting services website may be configured to offer and implement hosting of at least one customer website in the first datacenter, second datacenter, or both the first datacenter and second datacenter. The system also may comprise a network communicatively coupling the first datacenter, second datacenter, and customer interaction server.

Abstract: Methods of the present inventions allow for providing a preferred domain position on a registration website. An exemplary method may comprise the steps of receiving data from registrars regarding a domain administered by a registry, generating a quality score for the domain based upon the data, and providing the quality score to requesting entities.

Abstract: The present inventions may be implemented by tools enabling preferred domain positioning on a registration website. An example may comprise a computer-readable media storing instructions that, when executed by a server, cause the server to receive a request (comprising a bid and the domain) seeking such preferred placement, generate a quality score for the domain, determine the preferred placement based upon the bid and the quality score, and transmit a response (comprising the preferred placement) to the request.

Abstract: Systems of the present inventions allow for providing customer-selected solutions for multiple datacenter website hosting. An exemplary system may comprise a first datacenter comprising at least one hosting server, a second datacenter comprising at least one hosting server, and a hosting services website hosted on at least one customer interaction server. The hosting services website may be configured to offer and implement hosting of at least one customer website in the first datacenter, second datacenter, or both the first datacenter and second datacenter. The system also may comprise a network communicatively coupling the first datacenter, second datacenter, and customer interaction server.

Abstract: Systems of the present inventions allow for providing customer-selected solutions for multiple datacenter website hosting. An exemplary system may comprise a first datacenter comprising at least one hosting server, a second datacenter comprising at least one hosting server, and a hosting services website hosted on at least one customer interaction server. The hosting services website may be configured to offer and implement hosting of at least one customer website in the first datacenter, second datacenter, or both the first datacenter and second datacenter. The system also may comprise a network communicatively coupling the first datacenter, second datacenter, and customer interaction server.

Abstract: Methods of the present inventions allow for providing customer-selected solutions for multiple datacenter website hosting. An exemplary method may comprise the steps of registering, via at least one customer interaction server, a domain name to a registrant, offering, via the at least one customer interaction server, to host at least one customer website resolving from the domain name in a first datacenter, a second datacenter, or the first datacenter and the second datacenter, provisioning, via the at least one customer interaction server, (if the registrant selects hosting the at least one customer website in the first datacenter and the second datacenter) at least one hosting server in the first datacenter and at least one hosting server in the second datacenter to host the at least one customer website; and hosting the at least one customer website on the at least one hosting server in the first datacenter and at the least one hosting server in the second datacenter.

Abstract: The present inventions may be implemented by tools enabling preferred domain positioning on a registration website. An example may comprise a computer-readable media storing instructions that, when executed by a server computer, cause the server to receive a bid from a registry seeking such preferred placement for a domain (that may be administered by the registry), generate a quality score for the domain, and determine the preferred placement based upon the bid and the quality score.

Abstract: Systems of the present inventions allow for providing customer-selected solutions for multiple datacenter website hosting. An exemplary system may comprise a first datacenter comprising at least one hosting server, a second datacenter comprising at least one hosting server, and a hosting services website hosted on at least one customer interaction server. The hosting services website may be configured to offer and implement hosting of at least one customer website in the first datacenter, second datacenter, or both the first datacenter and second datacenter. The system also may comprise a network communicatively coupling the first datacenter, second datacenter, and customer interaction server.

Abstract: Methods of the present inventions allow for providing customer-selected solutions for multiple datacenter website hosting. An exemplary method may comprise the steps of registering, via at least one customer interaction server, a domain name to a registrant, offering, via the at least one customer interaction server, to host at least one customer website resolving from the domain name in a first datacenter, a second datacenter, or the first datacenter and the second datacenter, provisioning, via the at least one customer interaction server, (if the registrant selects hosting the at least one customer website in the first datacenter and the second datacenter) at least one hosting server in the first datacenter and at least one hosting server in the second datacenter to host the at least one customer website; and hosting the at least one customer website on the at least one hosting server in the first datacenter and at the least one hosting server in the second datacenter.

Abstract: A Web site, through the use of a Rules Engine, determines an expertise level of a User for one or more topics on a Web page. The Rules Engine may analyze User related data, such as the search term used by the User to find the Web site, the past products purchased by the User, the path through the Web site taken by the User, the usage history by the User on the Web site, the demographics of the User and/or the self declared expertise level of the User, to determine an expertise level of the User for the topics on the Web page. A Display Engine may customize a Web page based on the expertise levels of a User so that topics on the Web page are presented in a manner most appropriate for the User. An Email Engine may be used to customize emails to the User so that topics in the email are presented in manner most appropriate for the User. A Support Entity Engine may also be used to route an incoming support inquiries from a User to an appropriate technical support person for the User.

Abstract: A Web site, through the use of a Rules Engine, determines an expertise level of a User for one or more topics on a Web page. The Rules Engine may analyze User related data, such as the search term used by the User to find the Web site, the past products purchased by the User, the path through the Web site taken by the User, the usage history by the User on the Web site, the demographics of the User and/or the self declared expertise level of the User, to determine an expertise level of the User for the topics on the Web page. A Display Engine may customize a Web page based on the expertise levels of a User so that topics on the Web page are presented in a manner most appropriate for the User. An Email Engine may be used to customize emails to the User so that topics in the email are presented in manner most appropriate for the User. A Support Entity Engine may also be used to route an incoming support inquiries from a User to an appropriate technical support person for the User.

Abstract: A system and method of proxy domain name registration permits a would-be domain name registrant anonymity. A registrar affords customers the opportunity to use the proxy registration. If the customer seeking registration of a domain name requests, the registrar obtains contact information needed for registration from a proxy entity established for this purpose. The registrar completes the registration of the domain name with the appropriate registry (i.e. “.com, .net” etc.). The contact information published in WHOIS is that of proxy entity. Contractually the customer is afforded control over the domain name. Emails intended for the customer are received by the proxy entity who may filter them if the customer requests. Emails sent by the customer are sent to the proxy entity who in turn sends them to the indicated addressee.

Abstract: A Web site, through the use of a Rules Engine, determines an expertise level of a User for one or more topics on a Web page. The Rules Engine may analyze User related data, such as the search term used by the User to find the Web site, the past products purchased by the User, the path through the Web site taken by the User, the usage history by the User on the Web site, the demographics of the User and/or the self declared expertise level of the User, to determine an expertise level of the User for the topics on the Web page. A Display Engine may customize a Web page based on the expertise levels of a User so that topics on the Web page are presented in a manner most appropriate for the User. An Email Engine may be used to customize emails to the User so that topics in the email are presented in manner most appropriate for the User. A Support Entity Engine may also be used to route an incoming support inquiries from a User to an appropriate technical support person for the User.

Abstract: A Web site, through the use of a Rules Engine, determines an expertise level of a User for one or more topics on a Web page. The Rules Engine may analyze User related data, such as the search term used by the User to find the Web site, the past products purchased by the User, the path through the Web site taken by the User, the usage history by the User on the Web site, the demographics of the User and/or the self declared expertise level of the User, to determine an expertise level of the User for the topics on the Web page. A Display Engine may customize a Web page based on the expertise levels of a User so that topics on the Web page are presented in a manner most appropriate for the User. An Email Engine may be used to customize emails to the User so that topics in the email are presented in manner most appropriate for the User. A Support Entity Engine may also be used to route an incoming support inquiries from a User to an appropriate technical support person for the User.

Abstract: A Web site, through the use of a Rules Engine, determines an expertise level of a User for one or more topics on a Web page. The Rules Engine may analyze User related data, such as the search term used by the User to find the Web site, the past products purchased by the User, the path through the Web site taken by the User, the usage history by the User on the Web site, the demographics of the User and/or the self declared expertise level of the User, to determine an expertise level of the User for the topics on the Web page. A Display Engine may customize a Web page based on the expertise levels of a User so that topics on the Web page are presented in a manner most appropriate for the User. An Email Engine may be used to customize emails to the User so that topics in the email are presented in manner most appropriate for the User. A Support Entity Engine may also be used to route an incoming support inquiries from a User to an appropriate technical support person for the User.

Abstract: A system and method of proxy (60) domain name registration permits a would-be domain name registrant anonymity. A registrar (24) affords customers (20) the opportunity to use the proxy registration. If the customer seeking registration of a domain name requests, the registrar obtains contact information needed for registration from a proxy entity established for this purpose. The registrar completes the registration of the domain name with the appropriate registry (22) (i.e. “.com, .net” etc.). The contact information published in WHOIS (27) is that of proxy entity. Contractually the customer is afforded control over the domain name. Emails intended for the customer are received by the proxy entity who may filter them if the customer requests. Emails sent by the customer are sent to the proxy entity who in turn send them to the indicated addressee.