The Go Daddy Group, Inc.

Go Daddy Operating Company, LLC

Acronis International Gmbh

Michael Chadwick

Warren Adelman

Robert R Parsons

Eric Wagner

Adam Sink

Serguei M Beloussov

Alexander G Tormasov

Stanislav Protasov

Mark Shmulevich

Wayne Thayer

Eugene Aseev

Blake Schwendman

Blake Schwendiman

A method and system for verified data restoration in storage systems is described. The method may include calculating a hash sum relating to initial data for storing in an archive and storing the data into the archive and storing the calculated initial hash sum into a blockchain network. The method may further include retrieving the data from the archive and calculating a retrieved hash sum of the retrieved data. The method may also include comparing the initial hash sum from the blockchain network with the retrieved hash sum. The method may additionally include restoring the data from the archive if the initial hash sum is equivalent to the retrieved hash sum.

Trusted data restoration and authentication

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

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

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

Systems and processes of the present invention allow for digital identity registration. In an example embodiment, a Registrant may access a website to enter a requested digital identity and registration information. The requested digital identity may comprise a piece of client software, a digital certificate, or a URL comprising any combination of characters&#x2014;perhaps including a domain name that may be owned by the Registrant. A Digital Identity Database may then be searched to determine the availability of the requested digital identity. If the requested digital identity includes a domain name, WHOIS records may be searched to determine whether the Registrant owns and/or controls the domain name. The Registrant's registration information also may be validated. The requested digital identity may then be registered to the Registrant, possibly by adding the requested digital identity to the Digital Identity Database and/or adding the registration information to a Records database.

Digital identity registration

Disclosed methods provide for presenting search engine results based on domain name related reputation data. The search engine may sort or order search engine results based on domain name related reputation data. In some cases links connected to low reputation domain names may be excluded from search engine results. Alternatively, the search engine may show reputation ratings next to the links in the search engine results. Thus, allowing the Internet user to determine whether to visit the link or not. 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 reputation data may be digitally signed for authenticity. The reputation data may be stored in a digital certificate.

Presenting search engine results based on domain name related reputation

An example embodiment of a 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.

Community web site for creating and maintaining a web hosting community

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.

Growing community of inventors

Chandler, AZ, United States of America

Michael Chadwick