The Go Daddy Group, Inc.

Go Daddy Operating Company, LLC

Go Daddy Holding Company, LLC

Warren Adelman

Michael Chadwick

Justin Jilg

Robert R Parsons

Wayne Thayer

Shawn Michael Fitzpatrick

Nathan Curran

Eric Wagner

Matthew Jallo

Yong Lee

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.

Web hosting community

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.

Branded and comarketed domain-based thick client system

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.

Direct domain software and file access computer system

Systems and processes of the present invention allow for digital identity validation. In an example embodiment, a digital identity is registered to a Registrant. During the registration process, one or more registration records are collected from the Registrant and stored in a Records Database. The registration records may include information regarding a digital identity, its Registrant, or another person or entity associated with the digital identity. They may also include name, address, phone number, email address, website, URL, or other information. The information is then verified, possibly by contacting a Registrant, administrative contact, technical contact, or another contact to confirm at least some information in the records. If the information is verified, the Digital Identity Provider may provide the Registrant with a Validation Marker indicating that the digital identity has been validated.

Digital identity validation

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.

Interactive DNS for non-controlling party

Methods of the present inventions allow for verifying the authenticity of social website accounts. An example embodiment of a domain name control based social website account authentication method may comprise the steps of receiving a request (that may include a business name and a business email address) to verify the authenticity of a social website account, determining whether the domain name used by the business email address is registered to and under control of the business, and&#x2014;if so&#x2014;certifying the authenticity of the social website account.

Domain name control based social website account authentication

An example embodiment for providing one or more applications to one or more customers of an online application store via a partner website starts with hosting the partner web site and an online application store. A partner, from the partner web site, may make an application available for purchase and use to one or more customers. The one or more customers, may purchase and download the application from the online application store.

Offering applications via an online application store

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.

Systems and methods for software and file access via a domain name

The invention provides methods for efficiently registering a domain name and issuing a certificate without a Subscriber submitting a separate request for the certificate. In some embodiments, a notice may be provided to the Subscriber, after requesting to register a domain name, that a certificate may be issued for the domain name. The certificate may be saved in a Subscriber's account to enable the Subscriber to use the certificate at a later time. In yet other embodiments, a single vetting process may be used to facilitate one or more of: creating a Subscriber's account; registering a domain name; and issuing a certificate.

Methods of issuing a certificate for a domain name

Systems and methods of the present invention provide for redirecting a user to a book's website after submitting a request for information about the book. The book's website or a link to the website may be displayed to the user on a client browser.

Redirecting to a book website

Tools for redirecting to a book website

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.

Tracking domain name related reputation

The invention provides methods for efficiently registering a domain name and issuing a certificate without a Subscriber submitting a separate request for the certificate. A notice may be provided to the Subscriber after requesting to register the domain name that a credit for a certificate may be issued for the domain name. In other embodiments a credit may be given to the Subscriber for the certificate without receiving a separate request for the credit or certificate. The credit may be saved in a Subscriber's account to enable the Subscriber to use a certificate at a later time. In yet other embodiments, a single vetting process may be used to facilitate one or more of: creating a Subscriber's account; registering a domain name; and issuing a certificate.

Methods of issuing a credit for a certificate for a domain name

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.

Suggesting concept-based top-level domain names

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.

Growing community of inventors

Scottsdale, AZ, United States of America

Warren Adelman