Method for registering a stream of domain names received via a registrar's web site

• US 20040199493A1
• Filed: 04/04/2003
• Published: 10/07/2004
• Est. Priority Date: 04/04/2003
• Status: Abandoned Application

• Current Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Original Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Inventors: Ruiz, Tim, Krouse, Brian Richard
• Application Number:
  US10/407,778
• Publication Number:
  US 20040199493A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 50/10 Services
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• 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 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Abstract

The present invention allows a Customer to register a domain name with an accredited Registry via an accredited Registrar'"'"'s web site. Zone files from the Registries may be downloaded, optimized and stored in an internal database. As the Customer selects desired domain names, their availability may be determined by searching the internal database or, if needed, the authoritative Registry. The Customer enters the Customer'"'"'s information on a registration application displayed as a single form on a single web page. The Customer'"'"'s information may be saved in a login account for use as default Customer information at subsequent login sessions. The available domain name, Customer information and an associated status flag may be saved to an internal database. Software may be used to monitor the internal database and register all unregistered domain names in the internal database to a Registry'"'"'s SRS database.

Claims

1. A Registrar'"'"'s web site based domain name registration system, comprising:

A) means for receiving an available domain name from a Customer;

B) means for receiving registration information from the Customer;

C) means for writing the available domain name, registration information and a status flag in an internal database, wherein the status flag indicates that the domain name needs to be registered;

D) means for searching the internal database for the status flag indicating the domain name needs to be registered;

E) means for registering the domain name with a Registry when the status flag is found;

F) means for detecting a registration result associated with the registering the domain name; and

G) means for changing the status flag to indicate the registration result of the domain name.

2. The registration system of claim 1, further comprising:

H) means for validating the registration information from the Customer prior to registering the domain name.

3. The registration system of claim 1, wherein the means for registering the domain name include means for contacting the Registry via a dedicated Hub Service for the Registry.

4. The registration system of claim 1, further comprising:

H) means for sending the Customer an email notifying the Customer of the registration result.

5. The registration system of claim 1, further comprising:

H) manual means for reregistering the domain name with an unsuccessful registration result.

6. The registration system of claim 1, further comprising:

H) automated means for reregistering the domain name with an unsuccessful registration result.

7. A web site based domain name registration system, comprising:

A) a web site having a field for receiving a desired domain name;

B) an internal database;

C) a first automated process for storing the desired domain name and an associated status flag in the internal database, wherein the status flag indicates the domain name needs to be registered; and

D) a second automated process including;

a) means for searching the internal database for the status flag indicating the domain name is unregistered;

b) means for transmitting the domain name to a Registry;

c) means for receiving confirmation information from the Registry; and

d) means for updating the status flag in the internal database to reflect the confirmation information from the Registry.

8. The domain name registration system of claim 7, further comprising:

E) a plurality of Hub Services for improving communications between the second automated process and a plurality of Registries, wherein each Hub Service is dedicated to a single Registry in the plurality of Registries.

9. A web site based domain name registration process, comprising the steps of:

A) receiving an unregistered domain name from a Customer;

B) receiving a completed registration application from the Customer, wherein the completed registration application includes a contact information section for receiving contact information;

C) storing the unregistered domain name, the contact information and a status flag set to a first condition in an Internal Database during a first session;

D) searching the Internal Database for a status flag in the first condition;

E) registering the domain name associated with the status flag set in, the first condition with a Registry; and

F) setting the status flag to a second condition in the Internal Database.

10. The domain name registration process of claim 9, wherein the registration application is displayed on a single form residing on a single web page and the registration application includes a contact information section for receiving contact information.

11. The domain name registration process of claim 9, wherein the registering the domain name includes sending the domain name, a registrant contact, a technical contact and an administrative contact to the Registry.

12. The domain name registration process of claim 11, wherein the registering the domain name further includes sending the contact information to the Registry for the registrant contact, the technical contact and the administrative contact.

13. The domain name registration process of claim 10, wherein the registration application further includes a registration type section.

14. The domain name registration process of claim 9, wherein the registration application further includes a domain name service setup section.

15. The domain name registration process of claim 9, further comprising the steps of:

G) recalling the stored contact information in a second session;

H) receiving a second unregistered domain name during a second session; and

I) registering the second domain name with the Registry using the recalled contact information.

16. The domain name registration process of claim 15, further comprising the steps of:

J) receiving a payment information in the first session;

K) storing the payment information in the first session in an Internal Database; and

L) recalling the stored payment information from the Internal Database in the second session.

17. A Registrar'"'"'s web site based domain name registration process, comprising the steps of:

A) receiving an available domain name from a Customer;

B) receiving registration information from the Customer;

C) writing the available domain name, registration information and a status flag in an internal database, wherein the status flag indicates that the domain name needs to be registered;

D) searching the internal database for the status flag indicating the domain name needs to be registered;

E) registering the domain name with a Registry when the status flag is found;

F) detecting a registration result associated with the registering the domain name; and

G) changing the status flag to indicate the registration result of the domain name.

18. The registration process of claim 17, further comprising the step of:

H) validating the registration information from the Customer prior to registering the domain name.

19. The registration process of claim 17, wherein the registering the domain name includes contacting the Registry via a dedicated Hub Service for the Registry.

20. The registration process of claim 17, further comprising the step of:

H) sending the Customer an email notifying the Customer of the registration result.

21. The registration process of claim 17, further comprising the step of:

H) manually reregistering the domain names with an unsuccessful registration result.

22. The registration process of claim 17, further comprising the step of:

H) automatically reregistering the domain names with an unsuccessful registration result.