Method for a web site with a proxy domain name registration to receive a secure socket layer certificate

• US 7,702,902 B2
• Filed: 06/25/2004
• Issued: 04/20/2010
• Est. Priority Date: 06/25/2004
• Status: Active Grant

• Current Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Original Assignee: Go Daddy Group Incorporated (GoDaddy, Inc.)
• Inventors: Thayer, Wayne, Jilg, Justin, Reilly, Kevin
• Primary Examiner(s): LAFORGIA, CHRISTIAN A
• Application Number:
  US10/877,609
• Publication Number:
  US 20050289084A1
• Time in Patent Office: 2,125 Days
• Field of Search: 713/156
• US Class Current: 713/156
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: H04L 2209/76 Proxy, i.e. using intermediary entity to perform cryptographic operations network architectures or network communication protocols using hop-by-hop encryption H04L63/0464
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 9/321 involving a third party or a trusted authority
• CPC Class Codes: H04L 9/3268 using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]

Abstract

The present invention provides systems and methods for enabling encrypted communication capabilities for a Subscriber'"'"'s Web Site, thereby allowing Customers to access the Subscriber'"'"'s Web Site in a secure manner. The Subscriber may register a domain name associated with the Subscriber'"'"'s Web Site using a proxy domain name service, thereby hindering its Customers ability to verify the owner of the Subscriber'"'"'s Web Site. A Hosting Provider hosts the Subscriber'"'"'s Web Site and a Certificate Authority (CA) verifies the identity of the Subscriber. In combination the Hosting Provider and CA provide the Subscriber'"'"'s Web Site with Secure Sockets Layer (SSL) encrypted communications capability. The Hosting Provider and CA communicate directly with each other as needed, typically via the Internet, without using the Subscriber as an intermediary in their communications.

Claims

1. A method, comprising the steps of:

a) receiving, by a Certificate Authority, a request for a Secure Sockets Layer Certificate for a Web Site resolving from a domain name registered using proxy contact information and hosted by a Hosting Provider that provides a plurality of hardware and software necessary to place said Web Site on the Internet, said request being received from an owner of said Web Site;

b) requesting, by said Certificate Authority responsive to receiving said request for said Secure Sockets Layer Certificate from said owner of said website, a Certificate Signing Request directly from an entity that is different than said owner of said Web Site that transmitted said request for a Secure Sockets Layer Certificate to said Certificate authority in Step a), wherein said entity comprises said Hosting Provider;

c) receiving, by said Certificate Authority, a Certificate Signing Request directly from said Hosting Provider, said Certificate Signing Request comprising a public key and a distinguished name for said Web Site, said public key comprising part of a key pair generated by said Hosting Provider according to Public-Key Infrastructure protocol;

d) verifying, by said Certificate Authority, the identity of said subscriber;

e) upon successful verification of the identity of said owner of said Web Site, creating and signing, by said Certificate Authority, said Secure Sockets Layer Certificate; and

f) transmitting, by said Certificate Authority, said Secure Sockets Layer Certificate directly to said Hosting Provider for installation on said Web Site, wherein Steps b) through f) are accomplished without said owner of said Web Site being contacted by said Certificate Authority or said Hosting Provider.

2. The method of claim 1, wherein said Hosting Provider and said Certificate Authority are operated by a common Facilitator'"'"'s Web Server.

3. The method of claim 1, wherein said Hosting Provider and said Certificate Authority are operated on separate servers.

4. The method of claim 1, wherein said Certificate Authority verifies the identity of said owner of said Web Site by comparing responses from said owner with information available from information services available over the Internet.

5. The method of claim 1, wherein said Certificate Authority is a root Certificate Authority.

6. The method of claim 1, wherein said Certificate Authority is linked to a root Certificate Authority.