Methods of issuing a domain name certificate

• US 20060168116A1
• Filed: 01/11/2006
• Published: 07/27/2006
• Est. Priority Date: 06/25/2004
• Status: Abandoned Application

• Current Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Original Assignee: Go Daddy Group Incorporated (GoDaddy, Inc.)
• Inventors: Thayer, Wayne, Adelman, Warren
• Application Number:
  US11/330,772
• Publication Number:
  US 20060168116A1
• Time in Patent Office: Days
• US Class Current: 709/218
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/302 Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]
• CPC Class Codes: H04L 63/0407 wherein the identity of one or more communicating identities is hidden cryptographic mechanisms or cryptographic arrangements for anonymous credentials or for identity based cryptographic systems H04L9/00
• 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/166 at the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

The present invention provides methods for covering a plurality of domain names with a single certificate. This may be accomplished even if two or more of the domain names have different top level domains (TLDs). In certain embodiments, a Subscriber may be subjected to a vetting process as a prerequisite to allowing the Subscriber to create an account. Once the Subscriber has an account, the Subscriber may request a certificate, possibly covering multiple domain names, from the account without further vetting. In other embodiments, one or more domain names may be subjected to a vetting process prior to receiving a certificate. The history and prior usage of the domain name(s) may be examined to determine if a certificate should be issued for the domain names. Subjecting the domain names to a vetting process may also be done in combination with subjecting the Subscriber to a vetting process.

Claims

1. A method of issuing a secure certificate, comprising the steps of:

registering a plurality of domain names for a Subscriber;

receiving a request from the Subscriber for a certificate covering two or more domain names; and

creating, signing, and issuing the certificate covering two or more domain names, wherein at least two of the domain names have different top level domains.

2. The method of claim 1, wherein the creating, signing, and issuing the certificate is performed automatically for the Subscriber.

3. The method of claim 1, further comprising the steps of:

receiving a request from the Subscriber to install the certificate on a Subscriber'"'"'s web site; and

installing the certificate on the Subscriber'"'"'s web site.

4. The method of claim 3, wherein all steps are performed on a Facilitator'"'"'s Computer Network that includes a Domain Name Registering Function, a Hosting Provider Function and a Certificate Authority Function.

5. A method of issuing a secure certificate, comprising the steps of:

registering a plurality of domain names for a Subscriber;

receiving a request from the Subscriber for a certificate for two or more registered domain names;

subjecting the Subscriber to a vetting process; and

if the Subscriber passed the vetting process, creating, signing and issuing the certificate covering two or more domain names.

6. The method of claim 5, wherein the creating, signing and issuing the certificate is performed automatically for the Subscriber.

7. The method of claim 5, further comprising the steps of:

receiving a request from the Subscriber to install the certificate on a Subscriber'"'"'s web site; and

installing the certificate on the Subscriber'"'"'s web site.

8. The method of claim 7, wherein all steps are performed on a Facilitator'"'"'s Computer Network that includes a Domain Name Registering Function, a Hosting Provider Function and a Certificate Authority Function.

9. The method of claim 7, wherein at least two of the domain names covered by the certificate have different top level domains.

10. A method of issuing a secure certificate, comprising the steps of:

receiving a request from a Subscriber to create an account;

subjecting the Subscriber to a vetting process;

if the Subscriber passed the vetting process;

creating an account for the Subscriber;

registering a plurality of domain names selected by the Subscriber;

receiving a request from the Subscriber for a certificate for two or more domain names; and

creating, signing and issuing the certificate.

11. The method of claim 10, wherein the creating, signing and issuing the certificate is performed automatically for the Subscriber.

12. The method of claim 10, further comprising the steps of:

receiving a request from the Subscriber to install the certificate on a Subscriber'"'"'s web site; and

installing the certificate on the Subscriber'"'"'s web site.

13. The method of claim 12, wherein all steps are performed on a Facilitator'"'"'s Computer Network that includes a Domain Name Registering Function, a Hosting Provider Function and a Certificate Authority Function.

14. The method of claim 10, wherein at least two of the domain names covered by the certificate have different top level domains.

15. A method of issuing a secure certificate, comprising the steps of:

registering a plurality of domain names for a Subscriber;

receiving a request from the Subscriber for a certificate for two or more registered domain names;

subjecting the two or more registered domain names to a vetting process; and

refusing to issue the certificate for domain names that do not pass the vetting process.

16. The method of claim 15, further comprising the step of creating, signing and issuing the certificate for the domain names that passed the vetting process.

17. The method of claim 15, wherein the creating, signing and issuing the certificate is performed automatically for the Subscriber.

18. The method of claim 15, further comprising the steps of:

receiving a request from the Subscriber to install the certificate on a Subscriber'"'"'s web site; and

installing the certificate on the Subscriber'"'"'s web site.

19. The method of claim 18, wherein all steps are performed on a Facilitator'"'"'s Computer Network that includes a Domain Name Registering Function, a Hosting Provider Function and a Certificate Authority Function.

20. The method of claim 15, wherein at least two of the domain names covered by the certificate have different top level domains.

21. A method of issuing a secure certificate, comprising the steps of:

receiving a request from a Subscriber to create an account;

subjecting the Subscriber to a first vetting process;

if the Subscriber passed the first vetting process;

creating an account for the Subscriber;

registering a plurality of domain names selected by the Subscriber;

receiving a request from the Subscriber for a certificate for two or more registered domain names;

subjecting the registered domain names to a second vetting process; and

if the registered domain names passed the second vetting process, creating, signing and issuing the certificate for two or more domain names.

22. The method of claim 21, wherein the creating, signing and issuing the certificate is performed automatically for the Subscriber.

23. The method of claim 21, further comprising the steps of:

receiving a request from the Subscriber to install the certificate on a Subscriber'"'"'s web site; and

installing the certificate on the Subscriber'"'"'s web site.

24. The method of claim 23, wherein all steps are performed on a Facilitator'"'"'s Computer Network that includes a Domain Name Registering Function, a Hosting Provider Function and a Certificate Authority Function.

25. The method of claim 21, wherein at least two of the domain names covered by the certificate have different top level domains.