Method for checking the availability of a domain name

• US 20040199520A1
• 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: YAM Special Holdings, Inc. (GoDaddy, Inc.)
• Inventors: Parsons, Robert, Ruiz, Tim
• Application Number:
  US10/407,967
• Publication Number:
  US 20040199520A1
• 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 registration system for registering a domain name via a Registrar, comprising:

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

B) a Zone File Server having a Zone File Hash of previously registered domain names;

C) a Hub Service in communication with a Registry; and

D) a Check Availability Service, wherein the Check Availability Service is in communication with the web site for receiving the desired domain name, the Check Availability Service is in communication with the Zone File Server to determine if the domain name is available, and the Check Availability Service is in communication with the Hub Service to send the domain name to the Registry for registration.

2. The registration system of claim 1, wherein the Zone File Hash is a downloaded zone file from one or more Registries that has been optimized for searching for domain names.

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

E) a plurality of Hub Services in communication with a plurality of Registries, wherein each Hub Service is dedicated to maintaining communications with a single Registry.

4. A registration system for registering a stream of unregistered domain name via a Registrar, comprising:

A) an internal database of zone file data downloaded from a plurality of Registries;

B) a web site for receiving a stream of desired domain names from a plurality of Customers;

C) a first automated process for determining the availability for each domain name in the stream of desired domain names by determining if each domain name is in the internal database and, if not, determining if each of the domain names is registered with one of the Registries; and

D) a second automated process for registering each of the domain names determined to be available in the stream of desired domain names with an appropriate Registry.

5. The registration system of claim 4, wherein the internal database of zone file data has been optimized for searchers.

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

E) a plurality of Hub Services for improving the communications between the first automated process and the plurality of Registries and between the second automated process and the plurality of Registries.

7. The registration system of claim 6 wherein each Hub Service is dedicated to maintaining communications with a single Registry.

8. A registration system for registering a stream of unregistered domain name via a Registrar, comprising:

A) means for periodically receiving a plurality of zone files from a corresponding plurality of Registries;

B) means for optimizing the plurality of zone files to create a Zone File Hash having efficient domain name search capabilities;

C) means for storing the Zone File Hash in an internal database;

D) means for receiving a stream of desired domain names from a plurality of Customers;

E) means for determining for each domain name in the stream of desired domain names if the domain name is in the zone file hash; and

F) means for determining for each domain name not in the zone file hash if the domain name is registered with the appropriate Registry via a Hub Service.

9. The registration system of claim 8, wherein there is at least one dedicated Hub Service for each of the plurality of Registries.

10. A process for checking the availability of a plurality of domain names, comprising the steps of:

A) periodically downloading a plurality of zone files from a corresponding plurality of authoritative sources;

B) creating a Zone File Hash from the plurality of zone files, wherein the Zone File Hash is a database optimized for allowing fast searches for domain names;

C) storing the Zone File Hash in an internal database;

D) receiving a stream of desired domain names from one or more Customers;

E) determining if each domain name in the stream of desired domain names is in the Zone File Hash; and

F) determining for each domain name not in the Zone File Hash if the domain name is registered with the authoritative source responsible for the domain name.

11. The registration system of claim 10, wherein the Zone File Hash is created by removing all non-domain name information in the plurality of zone files.