CA2427266C - Registry-integrated internet domain name acquisition system - Google Patents
Registry-integrated internet domain name acquisition system Download PDFInfo
- Publication number
- CA2427266C CA2427266C CA002427266A CA2427266A CA2427266C CA 2427266 C CA2427266 C CA 2427266C CA 002427266 A CA002427266 A CA 002427266A CA 2427266 A CA2427266 A CA 2427266A CA 2427266 C CA2427266 C CA 2427266C
- Authority
- CA
- Canada
- Prior art keywords
- domain name
- acquisition
- registry
- registrar
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
Abstract
A preferred embodiment of the present invention integrates a domain name monitoring and acquisition service (116, 118) with a registry system (110, 112). The monitoring and acquisition service can receive a request from a registrar (100) to acquire a domain name. The monitoring and acquisition service also can receive a pending delete notification from the registry for a domain name having a registration that is about to be deleted. The pending delete notification can be received before the registry issues a public delete notification or purges the domain name, at which point the domain name is registrable by the first-responding registrar. If the domain name that is the subject of the pending delete notification has a corresponding acquisition request received by the monitoring and acquisition service, the monitoring and acquisition service can request acquisition of the domain name for the requesting registrar.
Description
REGISTRY-INTEGRATED INTERNET
DOMAIN NAME ACQUISITION SYSTEM
Related Applications [0001] This application is a continuation of and claims priority from U.S.
Provisional Patent Application No. 60/245,102, filed November 1, 2000, and U.S.
Provisional Patent Application No. 60/248,341, filed November 13, 2000.
Copyright Notice
DOMAIN NAME ACQUISITION SYSTEM
Related Applications [0001] This application is a continuation of and claims priority from U.S.
Provisional Patent Application No. 60/245,102, filed November 1, 2000, and U.S.
Provisional Patent Application No. 60/248,341, filed November 13, 2000.
Copyright Notice
[0002] ~ 2001 SnapNames.com, Inc. A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. 37 CFR ~ 1.71(d)-(e) (2000).
Technical Field
Technical Field
[0003] This invention pertains to distributed computer network node naming resolution processes and, more specifically, to registration of Internet domain names.
Background of the Invention
Background of the Invention
[0004] In distributed computer networks, being able to locate individual computers, servers, or various other machines on the network is critical. On the Internet, one of the most valuable identification resources is the domain name. Internet domain names provide a convenient way to reference Internet Protocol (IP) numerical addresses.
Presently, IP
addresses are 32-bit integers. They comprise four numbers separated by periods. Every "host" machine (e.g., computer, etc.) connected to the Internet must be identifiable by a specific numerical IP address. However, people prefer to reference host machines by pronounceable, easily remembered names, referred to as "domain names." The Internet implements a Domain Name System (DNS) to facilitate matching specific domain names to specific hosts.
Presently, IP
addresses are 32-bit integers. They comprise four numbers separated by periods. Every "host" machine (e.g., computer, etc.) connected to the Internet must be identifiable by a specific numerical IP address. However, people prefer to reference host machines by pronounceable, easily remembered names, referred to as "domain names." The Internet implements a Domain Name System (DNS) to facilitate matching specific domain names to specific hosts.
[0005] The DNS is a distributed database system that allows computer applications to map between domain names and IP addresses. The DNS also provides electronic mail routing information and many other services. Individual components of the DNS
distributed database can be cached locally, or stored on any of numerous distributed machines. The DNS database data correlates each domain name to a specific numeric IP
address. If a computer's local cache does not have the information to resolve a domain name into an IP address, it sends a request to other computers that may contain the resolution information. The DNS affords a domain name some measure of independence from the physical location of a host. The host can be moved to a new location on the network, but it can still be accessed using the same domain name. As long as a user can remember the domain name, the host can always be located, even if the IP
address changes over time. This illustrates the value of a domain name that is easy to remember.
distributed database can be cached locally, or stored on any of numerous distributed machines. The DNS database data correlates each domain name to a specific numeric IP
address. If a computer's local cache does not have the information to resolve a domain name into an IP address, it sends a request to other computers that may contain the resolution information. The DNS affords a domain name some measure of independence from the physical location of a host. The host can be moved to a new location on the network, but it can still be accessed using the same domain name. As long as a user can remember the domain name, the host can always be located, even if the IP
address changes over time. This illustrates the value of a domain name that is easy to remember.
[0006] Physically, the DNS comprises many servers and other computers or machines that run software and store data permitting computers to query the DNS
database. One such machine is the "root server." A root server is a server computer that maintains the software and data necessary to locate "name servers" that contain authoritative data for a specific domain, such as the ".com" top level domain. There are presently thirteen root servers throughout the world. Name servers are computers that have the software and data to resolve the domain name into an IP address. The data accessible through the name server is often referred to as a "zone file." A "zone" is a subset of the total domain name space. The domain names in that subset are stored in the zone file for that name server.
There is a zone file for each domain space (i.e., zone).
database. One such machine is the "root server." A root server is a server computer that maintains the software and data necessary to locate "name servers" that contain authoritative data for a specific domain, such as the ".com" top level domain. There are presently thirteen root servers throughout the world. Name servers are computers that have the software and data to resolve the domain name into an IP address. The data accessible through the name server is often referred to as a "zone file." A "zone" is a subset of the total domain name space. The domain names in that subset are stored in the zone file for that name server.
There is a zone file for each domain space (i.e., zone).
[0007] The DNS is organized in a hierarchical, tree structure. A domain name is the label representing a specific domain within the total possible domain space available in the DNS. The highest level in the DNS hierarchy is the "root," which is technically unnamed but often referred to as the ". " or "dot. " The level immediately below the root in the DNS
hierarchy is the top-level domain, or "TLD." It is called the "top-level domain" because it is the highest level in the hierarchy after the root. The TLD appears furthest to the right in an English-language domain name. For example, "gov" in the "uspto.gov" domain name.
There are various types of TLDs. The term "gTLD" is often interchangeably used to refer to a "global top-level domain" or a "generic top-level domain." A global TLD
is one that can be registered by an entity regardless of the entity's geographic location or political
hierarchy is the top-level domain, or "TLD." It is called the "top-level domain" because it is the highest level in the hierarchy after the root. The TLD appears furthest to the right in an English-language domain name. For example, "gov" in the "uspto.gov" domain name.
There are various types of TLDs. The term "gTLD" is often interchangeably used to refer to a "global top-level domain" or a "generic top-level domain." A global TLD
is one that can be registered by an entity regardless of the entity's geographic location or political
8 PCT/USO1/48054 boundary. For example, a person, corporation, or other entity located anywhere in the world can register a name in the ".com" domain. However, because an-entity must have a presence in the United Kingdom to register a name in the ".uk" TLD, that domain is not a global TLD. Similarly, a generic TLD represents a domain in which an entity can register a name regardless of what type of entity it is. For example, because any entity can register a name in the ".com" domain, while only military entities can register a name in the ".mil"
domain, the ".com" domain is an example of a generic TLD and the ".mil" domain is an example of a "specific TLD." The ".uk" domain is also an example of a "country code"
TLD, or "ccTLD," applicable to the United Kingdom. Other examples of ccTLDs include ".fr" for France, ".ca" for Canada, ".jp" for Japan, and ".us" for the United States of America.
[0008] By registering a domain name in a particular TLD, the TLD is sub-divided into lower levels in the DNS hierarchy. A second-level domain (SLD) is the level in the DNS
hierarchy immediately below the TLD. An example of a second-level domain would be "snapnames" in the "snapnames.com" domain name. The level in the DNS hierarchy immediately below the second-level domain is the third-level domain. An example of the third-level domain would be "portland" in the "portland.or.us" domain name.
Further subdivisions can be created in a similar manner. Domain names at each level of the hierarchy must be unique. Thus, while there can be only one "snapnames"
registered in the ".com" TLD, there can be a "snapnames.net" domain name in addition to the "snapnames.com" domain name.
domain, the ".com" domain is an example of a generic TLD and the ".mil" domain is an example of a "specific TLD." The ".uk" domain is also an example of a "country code"
TLD, or "ccTLD," applicable to the United Kingdom. Other examples of ccTLDs include ".fr" for France, ".ca" for Canada, ".jp" for Japan, and ".us" for the United States of America.
[0008] By registering a domain name in a particular TLD, the TLD is sub-divided into lower levels in the DNS hierarchy. A second-level domain (SLD) is the level in the DNS
hierarchy immediately below the TLD. An example of a second-level domain would be "snapnames" in the "snapnames.com" domain name. The level in the DNS hierarchy immediately below the second-level domain is the third-level domain. An example of the third-level domain would be "portland" in the "portland.or.us" domain name.
Further subdivisions can be created in a similar manner. Domain names at each level of the hierarchy must be unique. Thus, while there can be only one "snapnames"
registered in the ".com" TLD, there can be a "snapnames.net" domain name in addition to the "snapnames.com" domain name.
[0009] . Historically, domain name registration has been conducted through a Shared Registration System (SRS) involving registries, registrars, and registrants.
The SRS was created by Network Solutions, Inc. in 1999 to provide a registry backend through which multiple, globally diverse registrars could register domain names. The term "registry"
refers to the entity responsible for managing allocation of domain names within a particular name space, such as a TLD. One example of a registry is the VeriSign registry for the .com, .org, and .edu TLDs. The term "registrar" refers to any one of several entities with authority to issue commands or requests to add, edit, or delete registrations to or from the registry for a name space. Entities that wish to register a domain name do so through a registrar. The term "registrant" refers to the entity registering the domain name. In some name spaces, the registry and registrar functions can be performed by the same entity. The combined registry-registrar model is implemented in many ccTLDs. The overall registration system, including multiple registries, is overseen by the Internet Corporation for Assigned Names and Numbers (ICANN). ICANN is a non-profit corporation that was formed to assume responsibility for the IP address space allocation, protocol parameter assignment, domain name system management, and root server system management functions previously performed under U.S. Government contract by the Internet Assigned Numbers Authority (IANA) and other entities.
The SRS was created by Network Solutions, Inc. in 1999 to provide a registry backend through which multiple, globally diverse registrars could register domain names. The term "registry"
refers to the entity responsible for managing allocation of domain names within a particular name space, such as a TLD. One example of a registry is the VeriSign registry for the .com, .org, and .edu TLDs. The term "registrar" refers to any one of several entities with authority to issue commands or requests to add, edit, or delete registrations to or from the registry for a name space. Entities that wish to register a domain name do so through a registrar. The term "registrant" refers to the entity registering the domain name. In some name spaces, the registry and registrar functions can be performed by the same entity. The combined registry-registrar model is implemented in many ccTLDs. The overall registration system, including multiple registries, is overseen by the Internet Corporation for Assigned Names and Numbers (ICANN). ICANN is a non-profit corporation that was formed to assume responsibility for the IP address space allocation, protocol parameter assignment, domain name system management, and root server system management functions previously performed under U.S. Government contract by the Internet Assigned Numbers Authority (IANA) and other entities.
[0010] Domain names, or more specifically domain name registrations, have become significant business (and personal) assets. Registration rights are now bought, sold, traded, bartered, auctioned and stockpiled in "inventories." Some domain names have been transferred for consideration on the order of tens or even hundreds of thousands of U.S.
dollars. At the time of this writing, Verisign, Inc.~he company that maintains the .com, .net, and .org gTLD registry-reports over 32 million registrations in its database.
Industry statistics indicate, however, that only about 10 % of the domain names registered are currently in actual use, including more than just a simple holding or redirection page.
Many registrations are the work of speculators.
dollars. At the time of this writing, Verisign, Inc.~he company that maintains the .com, .net, and .org gTLD registry-reports over 32 million registrations in its database.
Industry statistics indicate, however, that only about 10 % of the domain names registered are currently in actual use, including more than just a simple holding or redirection page.
Many registrations are the work of speculators.
[0011] The actual cost to register an available domain name at present is relatively nominal, ranging from $6.50 to $35 per year. This charge is assessed by the domain name registrar to attend to entering the registration on the registry, and to maintain corresponding records. It represents a markup over the wholesale fee charged by the registry. There are numerous qualified registrars for the common gTLDs, so the market for this service is competitive. The registrar business can be viable because it can be largely automated and operated through a Web site so that direct costs are low. Volume is key, however, so much effort and money is spent on advertising and various relationships with other sites to attract "traffic." The leading registrars today each process on the order of a few million registrations or renewals per year.
[0012] New gTLDs are being added as the older ones-.com .net .org~ecome saturated. The realm of possible names under a given gTLD is not the problem, it is immense. (Names up to 67 characters long, plus the extension, apparently can be registered today.) The trouble is that popular, easy to remember or easy to recognize names are relatively limited in number. Many of the most desirable domain names, those corresponding to well-known trademarks or generically describing commercial goods or services, are long since taken in the basic gTLD spaces.
[0013] Acquisition of a desirable domain name requires current information as the registry is changing constantly. Each registry operator disseminates updates to the corresponding domain name resolution servers around the world on at least a daily basis.
One can expect this update frequency to rise toward substantially continuous.
The public can access the registry directly in a "read only" fashion; in other words, the public can view information but not change it. Presently, this ability is generally implemented by the registry maintaining a public Web site (or ftp site) where anyone can get information. The WHOIS lookup, or similar functions provided by the Registry or individual registrars, can be used to identify the registrant of a given domain name. Various sites now offer these kinds of lookups, though they merely query the actual registries and/or registrar databases to acquire the data.
One can expect this update frequency to rise toward substantially continuous.
The public can access the registry directly in a "read only" fashion; in other words, the public can view information but not change it. Presently, this ability is generally implemented by the registry maintaining a public Web site (or ftp site) where anyone can get information. The WHOIS lookup, or similar functions provided by the Registry or individual registrars, can be used to identify the registrant of a given domain name. Various sites now offer these kinds of lookups, though they merely query the actual registries and/or registrar databases to acquire the data.
[0014] The challenge arises in that many users or entities are "watching" for availability of the very same names at the very same registries. The "winner"
is the registrar (or individual scripting through the registrar's connections to the registry) who can "grab" (register) the newly released name before anyone else. It may have substantial resale value. Indeed, the registrar likely already has a buyer in the queue to whom to register the domain name. In any event, grabbing the name is a high-tech race where only first place wins. It is considered common knowledge in the industry that the winners are nearly always technologically sophisticated professional speculators, who either script through a registrar's connections without the registrar's knowledge, or strike arrangements with registrars for preferential access. It is also axiomatic that the average domain buyer has practically no chance of registering a valuable deleting name, a state of affairs the present invention would remedy.
is the registrar (or individual scripting through the registrar's connections to the registry) who can "grab" (register) the newly released name before anyone else. It may have substantial resale value. Indeed, the registrar likely already has a buyer in the queue to whom to register the domain name. In any event, grabbing the name is a high-tech race where only first place wins. It is considered common knowledge in the industry that the winners are nearly always technologically sophisticated professional speculators, who either script through a registrar's connections without the registrar's knowledge, or strike arrangements with registrars for preferential access. It is also axiomatic that the average domain buyer has practically no chance of registering a valuable deleting name, a state of affairs the present invention would remedy.
[0015] To effect a registration (renewal), domain name registrants or users must work through a qualified registrar; registrants do not have direct access to the registry (except a read-only lookup or search.) In large part, this is due to the implementation of an SRS, or Shared Registration System. There is only one registry for each gTLD, as domain names must be unique globally. Each registrar qualified to service a particular gTLD
has electronic access-typically a secure digital communication channel-for interacting with the corresponding registry, for example to enter or purge a domain name registration. A
registration is purged, for example, if the registrant does not timely pay a renewal fee (after a grace period).
has electronic access-typically a secure digital communication channel-for interacting with the corresponding registry, for example to enter or purge a domain name registration. A
registration is purged, for example, if the registrant does not timely pay a renewal fee (after a grace period).
[0016] The link between a registrar and the registry employs a Registry-Registrar Protocol (RRP), a commercial example of which is the Verisign Global Registry RRP.
This link into the registry is how registrars monitor the status of registered names. Various protocols can be used, one example being the Verisign EPP (Extensible Provisioning Protocol), which is an XML implementation for domain name related queries. As known to those of skill in the art, suitable alternative or future protocols could be employed.
This link into the registry is how registrars monitor the status of registered names. Various protocols can be used, one example being the Verisign EPP (Extensible Provisioning Protocol), which is an XML implementation for domain name related queries. As known to those of skill in the art, suitable alternative or future protocols could be employed.
[0017] The registry operator is contractually obligated to give all registrars equal access. For example, the ICANN (Unsponsored TLD) Registry Agreement provides in pertinent part: "Registry Operator shall provide all ICANN-Accredited Registrars that have Registry-Registrar Agreements in effect, and that are in compliance with the terms of such agreements, equivalent access to Registry Operator's Registry Services, including to its shared registration system." The complete contract can be found at:
http: //www. icann. org/tlds/agreements/unsponsored/registry-agmt-llmay0l .htm
http: //www. icann. org/tlds/agreements/unsponsored/registry-agmt-llmay0l .htm
[0018] Because many registrars each have a high-speed, efficient communication link to the registry, and assuming each employs an efficient communication protocol, the winner of the name-grab race is still basically left to chance. To be reliably successful at acquiring domain names, a registrar needs a way to get ahead of its competitors.
Summary of the Invention
Summary of the Invention
[0019] One basic underlying aspect of the present invention employs a domain name "monitor and acquire" method. That method involves monitoring the databases to "watch"
selected domain names, with enhanced frequency of "pinging" as the expirations draw near. This is done by pinging the WHOIS database at the registry that administers the TLD
in which the domain names are registered.
selected domain names, with enhanced frequency of "pinging" as the expirations draw near. This is done by pinging the WHOIS database at the registry that administers the TLD
in which the domain names are registered.
[0020] Second, considerable improvement is achieved over the basic monitor and acquire method by "partnering" (actually a contractual relationship) with one, or preferably, multiple registrars, and employing all or a portion of their direct registry access bandwidth. The aggregate effect of multiple connections to the registry should improve performance in terms of timeliness of information and efficacy of any acquisition efforts, toward the goal of obtaining information on deleting (and therefore available, or soon to be available) domain names ahead of competing registrars or the would-be registrants using their registry connection.
[0021] A third, and quite different, model is this: the monitor and acquire service is integrated into the registry itself, with the cooperation of the registry operator. While the singular form of "registry" is used herein for clarity of explanation, the invention is equally applicable to multiple registries.
[0022] Implementation is simplified and efficiency is improved by integrating the monitor and acquire services directly at the registry of interest. This obviates the need for multiple registrars (or other registration service providers) to constantly "ping" the authoritative database so that loading on the system is relieved. Registrars and other retail-level competitors can avoid the trouble and expense, and especially uncertainty, of the present race-to-grab a name. For example, some of these retail-level players offer a "money back guarantee" to their customers; triggered if the retailer fails to register the desired name when it becomes available (usually because a competitor registered it first).
[0023] According to the present invention, any and all domain name retailers, such as existing registrars, can participate much more simply in providing monitor and acquire domain name services. The retailer can still offer such services to its customers under the new model, generally through its Web site. Customers can sign up to have the status of a desired name monitored and the name acquired or re-acquired automatically. The retailer no longer needs to perform the monitoring and acquiring steps itself. Rather, the retailer is acting like a reseller of these services. The services are actually provided by a single (i.e., only one is permitted per registry) intermediary entity or software routine implemented at the registry. The intermediary, or the registry implementing software consistent with the present invention, maintains databases of all domain names for which any "retailer"
requests monitoring or acquisition on behalf of its customers; together with information identifying the customer.
requests monitoring or acquisition on behalf of its customers; together with information identifying the customer.
[0024] According to another aspect of the invention, the intermediary or implemented software "watches" the registry to detect availability of a desired name and register the domain name immediately upon it becoming available. The "watching" can be effected various ways, for example through "push" updates from the registry or "pull"
queries into the registry database from the intermediary.
7.
queries into the registry database from the intermediary.
7.
[0025] When a desired name becomes available, it is automatically acquired by placing a hold or immediately registering the name to the customer entity listed in the database.
The customer and or the associated retailer are then notified. Payment for the registration is prearranged so it too can occur immediately and automatically. This invention obviates the expensive race now going on to acquire recently available domain names. If an intermediary is involved, the intermediary will always effect the registration, as it has no direct competition and in any event gets notification ahead of others because of its direct communication link into the registry (which may be effected on the same machine as the registry).
The customer and or the associated retailer are then notified. Payment for the registration is prearranged so it too can occur immediately and automatically. This invention obviates the expensive race now going on to acquire recently available domain names. If an intermediary is involved, the intermediary will always effect the registration, as it has no direct competition and in any event gets notification ahead of others because of its direct communication link into the registry (which may be effected on the same machine as the registry).
[0026] One embodiment of the present invention can be directed to providing monitoring and acquisition services for receiving from a registrar a request to acquire a desired domain name, receiving from a registry a pending delete notification for the desired domain name (the pending delete notification preceding a public delete notification) and requesting acquisition of the desired domain name for the registrar. One embodiment of a system designed to provide these and similar services can include an acquisition database containing an acquisition request from a specific registrar to acquire a registered domain name as soon as practicable. An acquisition front end system can be provided to receive the acquisition request from the specific registrar and to store the acquisition request in the acquisition database. Also, an acquisition engine can be integrated with a registry system to receive from the registry system a pending delete notification for the domain name. The acquisition engine can be integrated as hardware, software, or both. The pending delete notification can precede a public delete notification issued by the registry system. The acquisition engine can then access the acquisition request from the acquisition database and request acquisition of the domain name for the specific registrar.
[0027] The domain name monitoring and acquisition services and system described herein can be offered as a viable, independent business tool. Primary customers of a business employing the present invention would be domain name registrars and resellers (such as in a thick registry system). In this capacity, the registrars essentially would be reselling the services to their customers so as to provide the customers a more reliable way to acquire a newly available domain name. Fees could be charged for placing an acquisition request. Because of the reliability of the present invention, a money-back-guarantee could also be offered at low risk to the business.
[0028] Additional aspects and advantages of this invention will be apparent from the following detailed description of preferred embodiments thereof, which proceeds with reference to the accompanying drawings.
Brief Description of the Drawings
Brief Description of the Drawings
[0029] FIG. 1 is a simplified block diagram of a domain name management and acquisition system according to the present invention.
[0030] FIG. 2 illustrates a procedure for a registrar to obtain domain name acquisition services for a customer consistent with the present invention.
[0031] FIG. 3 is a schematic of the various communications and interactions between domain name acquisition engine, a registrar, and a registry according to the present invention.
[0032] FIG. 4 is a flow diagram providing a logic overview of the process of FIG. 3.
Detailed Description of Preferred Embodiments
Detailed Description of Preferred Embodiments
[0033] When referring to the following in Figure 1, the term "systems" is meant to mean one or more, routers, layer two or three switches, computer systems, APIs, and software. .In Figure 1, a Registrar computer 100 communicates with a Registry system 102. The Registry system includes a Global Registry RRP front end 110. The front end 110 communicates with a Global Registry SRS Database Management System 112.
The SRS database itself is illustrated as 114. This database would be the unique global ("authoritative") database for the gTLD space assigned to the Registry system 102 operator (e.g., ".com").
The SRS database itself is illustrated as 114. This database would be the unique global ("authoritative") database for the gTLD space assigned to the Registry system 102 operator (e.g., ".com").
(0034] For ease of discussion, a preferred embodiment of the present invention is described in terms of a system integrated at the registry level. This system is described as receiving input from one or more registrars. As will be readily apparent to those of skill in the pertinent art, a system consistent with the present invention can be integrated with the registry as hardware, software, or both. Similarly, the present system can operate in a thick registry system (in addition to a thin registry system) by receiving input directly from potential registrants, rather than from a registrar. These alternative embodiments are equally within the scope of the present invention as set out in the attached claims.
[0035] The Registrar 100 also communicates with an Integrated Domain Acquisition Service ("IDAS") front end computer 116. This computer can implement appropriate communications protocols (many of which are known; with various levels of security), including, for example "Extensible Provisioning Protocol" (EPP). EPP is a connection-oriented, application layer client-server protocol for provisioning and management of objects stored in a shared central repository. It employs the XML schema semantics for domain name related queries to the repository.
[0036] The front end computer 116 is coupled to an Integrated Domain Acquisition Service ("IDAS") acquisition engine and database management system 118. The acquisition system, in turn, communicates with an Integrated Domain Acquisition Service ("IDAS ") database 120. The various elements of the system 102 can of course be implemented in various ways, using more or fewer computers than illustrated;
in a distributed network. One essential characteristic is that the system should be accessible by Registrar 100 at all times, and preferably accessible to many registrars. This is the primary function of the right side of the diagram, comprising the Global Registry front end 110, the Global Registry database management system 112, and the Global Registry SRS
database 114.
in a distributed network. One essential characteristic is that the system should be accessible by Registrar 100 at all times, and preferably accessible to many registrars. This is the primary function of the right side of the diagram, comprising the Global Registry front end 110, the Global Registry database management system 112, and the Global Registry SRS
database 114.
[0037] The elements on the left side of the diagram implement an Integrated Domain Acquisition Service ("IDAS"). Here "integrated" refers to integration with the global registry as further explained below. In the past, domain name acquisition services were provided by registrars or other parties using their own systems, separate and remote from the global registry. We also use the phrase "domain acquisition services" to refer to services distinct from the routine registration of an available domain name.
In particular, we use the phrase "domain acquisition services" to mean "acquiring" (by reserving, holding or substantially immediately registering) a domain name that had been registered, and recently became newly available, generally because the prior registrant did not timely extend (renew) the registration.
In particular, we use the phrase "domain acquisition services" to mean "acquiring" (by reserving, holding or substantially immediately registering) a domain name that had been registered, and recently became newly available, generally because the prior registrant did not timely extend (renew) the registration.
[0038] Figure 1 illustrates the following data paths:
"A" The current (typically SSL) RRP communications channel connecting the Registrar 100 to the Registry System 102 via the global registry RRP
front end 110.
"B" Any communications paths between the RRP front end 110 and the database processing environment 112 for the Shared Registration System.
to "C" Any communications paths between the database processing environment 112 for the Shared Registration System and the actual SRS
database 114.
"D" The (preferably SSL EPP) communications channel connecting the Registrar 100 to the IDAS front end 116.
"E" A communications channel connecting the IDAS front end 116 to the DAS acquisition engine and database management system 118.
"F" A communications channel connecting the IDAS Acquisition Engine and Database Management System 118 to the IDAS database 120.
"G" A communications channel from the Global Registry SRS database Management System 112 enabling notification of deleting domains to the IDAS Acquisition Engine and database management system 118.
"H" A communications channel between the Global Registry SRS database Management System 112 and the IDAS Acquisition Engine and database management system 118.
"A" The current (typically SSL) RRP communications channel connecting the Registrar 100 to the Registry System 102 via the global registry RRP
front end 110.
"B" Any communications paths between the RRP front end 110 and the database processing environment 112 for the Shared Registration System.
to "C" Any communications paths between the database processing environment 112 for the Shared Registration System and the actual SRS
database 114.
"D" The (preferably SSL EPP) communications channel connecting the Registrar 100 to the IDAS front end 116.
"E" A communications channel connecting the IDAS front end 116 to the DAS acquisition engine and database management system 118.
"F" A communications channel connecting the IDAS Acquisition Engine and Database Management System 118 to the IDAS database 120.
"G" A communications channel from the Global Registry SRS database Management System 112 enabling notification of deleting domains to the IDAS Acquisition Engine and database management system 118.
"H" A communications channel between the Global Registry SRS database Management System 112 and the IDAS Acquisition Engine and database management system 118.
[0039] These links implement the necessary access to the RRP/SRS (112) to issue commands needed to register desired domains on a Registrar's behalf. "Desired domains"
are the names stored in database 120 to be monitored and acquired if and when available.
Commands for this channel preferably should include RRP "check domain," RRP
"add domain," RRP "modify domain commands," and possibly other commands necessary to modify the SRS Registrar field.
are the names stored in database 120 to be monitored and acquired if and when available.
Commands for this channel preferably should include RRP "check domain," RRP
"add domain," RRP "modify domain commands," and possibly other commands necessary to modify the SRS Registrar field.
[0040] Figure 2, which illustrates a procedure for a Registrar to obtain a IDAS
subscription, is as follows. A customer 200 makes a request to a Registrar 100 for DAS
service. In a presently preferred embodiment, the Registrar establishes an EPP
or similar connection to the IDAS front end and issues a "DAS check request" 204. The "DAS check request" will query the RRP/SRS 206 for the current SRS status of the second level domain name (SLD). If the domain name is currently registered, signified by a message 210, it is eligible for a DAS subscription. The Registrar can then issue a valid "DAS add request"
212. The front end 116 causes an appropriate entry in the IDAS database (see Figure 1).
When the requested domain name becomes available, the IDAS system sends an "Acknowledge DAS Success" or similar message 214 to the Registrar that requested the service. That registrar then notifies~its customer, shown as message 220, typically via email.
subscription, is as follows. A customer 200 makes a request to a Registrar 100 for DAS
service. In a presently preferred embodiment, the Registrar establishes an EPP
or similar connection to the IDAS front end and issues a "DAS check request" 204. The "DAS check request" will query the RRP/SRS 206 for the current SRS status of the second level domain name (SLD). If the domain name is currently registered, signified by a message 210, it is eligible for a DAS subscription. The Registrar can then issue a valid "DAS add request"
212. The front end 116 causes an appropriate entry in the IDAS database (see Figure 1).
When the requested domain name becomes available, the IDAS system sends an "Acknowledge DAS Success" or similar message 214 to the Registrar that requested the service. That registrar then notifies~its customer, shown as message 220, typically via email.
[0041] The "DAS Add Request" 212 requires the Registrar to populate a data set,. for example, through the EPP interface, with information previously supplied by the requesting customer 200. This information is a data escrow containing the required registration information for the desired domain name. The data set also contains flag fields indicating who will provide the email notifications, the intermediary or the Registrar.
At any time during the DAS subscription period, the Registrar can update or modify the registration information in the DAS database. Once the desired registration occurs, the Registrar, and optionally one or more customer defined e-mail addresses, will receive notification by e-mail of the successful operation. Other methods of customer notification can be used (e.g. fax, wireless, pager, vm, voicemail, snail mail, etc.); the method is not critical.
Upon receiving the notification 214 the Registrar will update 332 the WHOIS
record 340 reflecting the new registrant information originally supplied from the DAS
database 120.
At any time during the DAS subscription period, the Registrar can update or modify the registration information in the DAS database. Once the desired registration occurs, the Registrar, and optionally one or more customer defined e-mail addresses, will receive notification by e-mail of the successful operation. Other methods of customer notification can be used (e.g. fax, wireless, pager, vm, voicemail, snail mail, etc.); the method is not critical.
Upon receiving the notification 214 the Registrar will update 332 the WHOIS
record 340 reflecting the new registrant information originally supplied from the DAS
database 120.
[0042] Once a Registrar has issued a successful "monitor and acquire service add command," information about the monitor and acquire service is stored in the IDAS
database. Fields in the monitor and acquire service database will include the SLD and TLD, the sponsoring Registrar for the future domain name registration, complete registrant and contact information, from one to thirteen name servers, date of the monitor and acquire service subscription creation, date of the monitor and acquire service subscription expiration, a status field indicating that the intermediary will perform customer notification, up to three e-mail notification addresses, and the status of the monitor and acquire service (pending or complete).
database. Fields in the monitor and acquire service database will include the SLD and TLD, the sponsoring Registrar for the future domain name registration, complete registrant and contact information, from one to thirteen name servers, date of the monitor and acquire service subscription creation, date of the monitor and acquire service subscription expiration, a status field indicating that the intermediary will perform customer notification, up to three e-mail notification addresses, and the status of the monitor and acquire service (pending or complete).
[0043] ~ Figure 3 depicts communications and interactions between the Registry and the intermediary's Acquisition Engine. In a prompt and preferably real time manner, the Registry 112 will transmit a message 310 to the IDAS Acquisition Engine 118 indicating that a domain name is ready to be released and will be in a state where it can be re-registered. This is shown as a "pending delete" notification 310. These messages are not necessarily the Registrar's RRP delete commands, but follow the Registrar's RRP
delete command when the Registry is about to initiate a final purge process making the domain name available for re-registration.
delete command when the Registry is about to initiate a final purge process making the domain name available for re-registration.
[0044] Responsive to a "pending delete notification" message to the IDAS
Acquisition Engine, the Acquisition Engine checks the domain name 312 against the monitor and acquire service subscription database 120. If an IDAS subscription is held on the domain name, the Acquisition Engine will establish an RRP connection 314 on the Registrar's behalf. This connection or message corresponds to channel "H" as illustrated in Figure 1.
Next, the Acquisition Engine acknowledges receipt 316 of the original ("pending delete") message to the Global Registry system 112 and the Registry completes a purge of the subject domain name. Now the Acquisition Engine issues an RRP "add domain"
command 318 to re-register the domain name (to the new registrant, customer 200).
Acquisition Engine, the Acquisition Engine checks the domain name 312 against the monitor and acquire service subscription database 120. If an IDAS subscription is held on the domain name, the Acquisition Engine will establish an RRP connection 314 on the Registrar's behalf. This connection or message corresponds to channel "H" as illustrated in Figure 1.
Next, the Acquisition Engine acknowledges receipt 316 of the original ("pending delete") message to the Global Registry system 112 and the Registry completes a purge of the subject domain name. Now the Acquisition Engine issues an RRP "add domain"
command 318 to re-register the domain name (to the new registrant, customer 200).
[0045] If an IDAS subscription does not exist in the IDAS database for the domain name identified in the "pending delete" notification, the Acquisition Engine simply replies with an acknowledgement 316 to the Registry, and purging of the name proceeds.
No attempt.to register the domain name is made by the Acquisition Engine. All registrars, including registrars other than 100, will learn of the deletion when they next update their records against the SRS database, and are free to register the purged name; in the conventional manner. As may be observed in view of this description, no registrar will beat registrar 100 in registering the newly released name, as registrar 100 is using the DAS
system integrated with the registry itself.
No attempt.to register the domain name is made by the Acquisition Engine. All registrars, including registrars other than 100, will learn of the deletion when they next update their records against the SRS database, and are free to register the purged name; in the conventional manner. As may be observed in view of this description, no registrar will beat registrar 100 in registering the newly released name, as registrar 100 is using the DAS
system integrated with the registry itself.
[0046] Referring again to Figure 3, once a successful RRP add domain name command has been issued, the Registrar will receive notification 330 of the desired registration. The Registrar will then update 332 its WHOIS database 340 by modifying the record corresponding to the name just re-registered. The registrar can notify 350 the customer 200 or, alternatively, the option can be implemented to have the IDAS effect the customer notification 360. If the acquisition system is employed in a thick registry domain name system, the registry provides the WHOIS update 332 to a registry WHOIS
database (not shown) as opposed to the registrar WHOIS database 340.
database (not shown) as opposed to the registrar WHOIS database 340.
[0047] Figure 4 is a flow diagram providing a logic overview of the processes described above. It illustrates the foregoing processes in an alternative format, but it need not be separately described further.
[0048] It will be obvious to those having skill in the art that many changes may be made to the details of the above-described embodiments of this invention without departing from the underlying principles thereof. The scope of the present invention should, therefore, be determined only by the following claims.
Claims (10)
1. A domain name registry system comprising:
a registry database containing a current registration record for a domain name, the current registration record having an expiration date;
a registry management system, having access to the registry database, to delete the current registration record after the expiration date, to issue a public delete notification, and to add a new registration record for a first requesting registrar;
an acquisition database containing an acquisition request from a specific registrar to acquire the domain name as soon as practicable following the expiration date and preceding the public delete notification; and an acquisition engine to receive from the registry management system a pending delete notification, the pending delete notification preceding the public delete notification, to access the acquisition request from the acquisition database, and to request the registry management system to add the new registration for the specific registrar.
a registry database containing a current registration record for a domain name, the current registration record having an expiration date;
a registry management system, having access to the registry database, to delete the current registration record after the expiration date, to issue a public delete notification, and to add a new registration record for a first requesting registrar;
an acquisition database containing an acquisition request from a specific registrar to acquire the domain name as soon as practicable following the expiration date and preceding the public delete notification; and an acquisition engine to receive from the registry management system a pending delete notification, the pending delete notification preceding the public delete notification, to access the acquisition request from the acquisition database, and to request the registry management system to add the new registration for the specific registrar.
2. The system of claim 1 further comprising an acquisition front end to receive the acquisition request from the specific registrar and to store the acquisition request in the acquisition database.
3. The system of claim 2 wherein the acquisition front end is a Web server, and further comprising a Web page hosted by the Web server to receive the acquisition request from the specific registrar.
4. An integrated domain name acquisition system comprising:
an acquisition database containing an acquisition request from a specific registrar to acquire a domain name as soon as practicable to follow a preceding registration for the domain name;
an acquisition front end system to receive the acquisition request from the specific registrar and to store the acquisition request in the acquisition database;
and an acquisition engine integrated with a registry system to receive from the registry system a pending delete notification for the domain name, the pending delete notification preceding a public delete notification, to access the acquisition request from the acquisition database, and to request acquisition of the domain name for the specific registrar.
an acquisition database containing an acquisition request from a specific registrar to acquire a domain name as soon as practicable to follow a preceding registration for the domain name;
an acquisition front end system to receive the acquisition request from the specific registrar and to store the acquisition request in the acquisition database;
and an acquisition engine integrated with a registry system to receive from the registry system a pending delete notification for the domain name, the pending delete notification preceding a public delete notification, to access the acquisition request from the acquisition database, and to request acquisition of the domain name for the specific registrar.
5. The system of claim 4 wherein the acquisition of the domain name is a registration of the domain name.
6. A method for acquiring a deleting domain name, the method comprising the steps of:
receiving from a registrar a request to acquire a desired domain name;
receiving from a registry a pending delete notification for the desired domain name, the pending delete notification preceding a public delete notification; and requesting acquisition of the desired domain name for the registrar.
receiving from a registrar a request to acquire a desired domain name;
receiving from a registry a pending delete notification for the desired domain name, the pending delete notification preceding a public delete notification; and requesting acquisition of the desired domain name for the registrar.
7. The method of claim 6, wherein the acquisition is a succeeding registration for the desired domain name.
8. The method of claim 6, wherein the acquisition includes placing the desired domain name on registration hold.
9. A method of domain name acquisition comprising:
receiving from a registrar a request to acquire a desired domain name;
storing the request in a database;
receiving from a registry system a pending delete notification for the desired domain name, the pending delete notification being received before the registry system purges the desired domain name;
correlating the pending delete notification to the request stored in the database; and requesting acquisition of the desired domain name for the registrar.
receiving from a registrar a request to acquire a desired domain name;
storing the request in a database;
receiving from a registry system a pending delete notification for the desired domain name, the pending delete notification being received before the registry system purges the desired domain name;
correlating the pending delete notification to the request stored in the database; and requesting acquisition of the desired domain name for the registrar.
10. The method of claim 9 further comprising the steps of, prior to the requesting acquisition step:
acknowledging to the registry system receipt of the pending delete notice; and receiving from the registry system notification that the desired domain name has been deleted.
acknowledging to the registry system receipt of the pending delete notice; and receiving from the registry system notification that the desired domain name has been deleted.
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US24510200P | 2000-11-01 | 2000-11-01 | |
US60/245,102 | 2000-11-01 | ||
US24834100P | 2000-11-13 | 2000-11-13 | |
US60/248,341 | 2000-11-13 | ||
PCT/US2001/048054 WO2002037338A1 (en) | 2000-11-01 | 2001-11-01 | Registry-integrated internet domain name acquisition system |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2427266A1 CA2427266A1 (en) | 2002-05-10 |
CA2427266C true CA2427266C (en) | 2005-03-29 |
Family
ID=26937001
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002427266A Expired - Lifetime CA2427266C (en) | 2000-11-01 | 2001-11-01 | Registry-integrated internet domain name acquisition system |
CA002429364A Expired - Lifetime CA2429364C (en) | 2000-11-01 | 2001-11-01 | Domain name acquisition and management system and method |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002429364A Expired - Lifetime CA2429364C (en) | 2000-11-01 | 2001-11-01 | Domain name acquisition and management system and method |
Country Status (6)
Country | Link |
---|---|
US (10) | US7418471B2 (en) |
EP (2) | EP1332445A4 (en) |
CN (2) | CN100339846C (en) |
AU (2) | AU2002243319A1 (en) |
CA (2) | CA2427266C (en) |
WO (2) | WO2002056132A2 (en) |
Families Citing this family (257)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080010365A1 (en) * | 1997-07-25 | 2008-01-10 | Eric Schneider | Methods, products, systems, and devices for processing reusable information |
US6760746B1 (en) | 1999-09-01 | 2004-07-06 | Eric Schneider | Method, product, and apparatus for processing a data request |
US6839759B2 (en) | 1998-10-30 | 2005-01-04 | Science Applications International Corp. | Method for establishing secure communication link between computers of virtual private network without user entering any cryptographic information |
US6502135B1 (en) | 1998-10-30 | 2002-12-31 | Science Applications International Corporation | Agile network protocol for secure communications with assured system availability |
US7418504B2 (en) | 1998-10-30 | 2008-08-26 | Virnetx, Inc. | Agile network protocol for secure communications using secure domain names |
ES2760905T3 (en) | 1998-10-30 | 2020-05-18 | Virnetx Inc | An agile network protocol for secure communications with assured system availability |
US10511573B2 (en) | 1998-10-30 | 2019-12-17 | Virnetx, Inc. | Agile network protocol for secure communications using secure domain names |
US7167904B1 (en) * | 1999-03-19 | 2007-01-23 | Network Solutions, Llc | Unified web-based interface-to multiple registrar systems |
USRE43690E1 (en) | 1999-03-22 | 2012-09-25 | Esdr Network Solutions Llc | Search engine request method, product, and apparatus |
US8037168B2 (en) * | 1999-07-15 | 2011-10-11 | Esdr Network Solutions Llc | Method, product, and apparatus for enhancing resolution services, registration services, and search services |
US6338082B1 (en) | 1999-03-22 | 2002-01-08 | Eric Schneider | Method, product, and apparatus for requesting a network resource |
US7188138B1 (en) | 1999-03-22 | 2007-03-06 | Eric Schneider | Method, product, and apparatus for resource identifier registration and aftermarket services |
US9141717B2 (en) | 1999-03-22 | 2015-09-22 | Esdr Network Solutions Llc | Methods, systems, products, and devices for processing DNS friendly identifiers |
USRE44207E1 (en) | 1999-09-01 | 2013-05-07 | Esdr Network Solutions Llc | Network resource access method, product, and apparatus |
KR100856149B1 (en) * | 1999-11-26 | 2008-09-03 | 네테카 인코포레이티드 | Electronic mail server |
US6922685B2 (en) * | 2000-05-22 | 2005-07-26 | Mci, Inc. | Method and system for managing partitioned data resources |
US7401131B2 (en) * | 2000-05-22 | 2008-07-15 | Verizon Business Global Llc | Method and system for implementing improved containers in a global ecosystem of interrelated services |
US20020010795A1 (en) * | 2000-06-09 | 2002-01-24 | Brown Charles P. | Method and system for protecting domain names |
US7467140B2 (en) * | 2000-06-30 | 2008-12-16 | Verisign, Inc. | System, method, and article of manufacture for maintaining and accessing a whois database |
US7711611B2 (en) * | 2000-10-27 | 2010-05-04 | Microsoft Corporation | Wish list |
CA2427266C (en) * | 2000-11-01 | 2005-03-29 | Snapnames.Com, Inc. | Registry-integrated internet domain name acquisition system |
US20020145992A1 (en) * | 2001-03-20 | 2002-10-10 | Holt Gregory S. | URL acquisition and management |
US20030182447A1 (en) * | 2001-05-31 | 2003-09-25 | Schilling Frank T. | Generic top-level domain re-routing system |
US20020198761A1 (en) * | 2001-06-11 | 2002-12-26 | First Look Networks, L.L.C. | System and method for identifying a market by projecting demand and identifying supply |
US7565402B2 (en) * | 2002-01-05 | 2009-07-21 | Eric Schneider | Sitemap access method, product, and apparatus |
US7330971B1 (en) | 2002-01-11 | 2008-02-12 | Microsoft Corporation | Delegated administration of namespace management |
US20030149690A1 (en) * | 2002-02-01 | 2003-08-07 | Kudlacik Mark E. | Method and apparatus to search domain name variations world wide |
US20030225670A1 (en) * | 2002-05-31 | 2003-12-04 | Decarlo George J. | Auction style distribution of domain names |
WO2004015547A2 (en) * | 2002-08-13 | 2004-02-19 | Snapnames.Com, Inc. | Pathway-specific, registry-integrated domain name registration system |
US8775675B2 (en) * | 2002-08-30 | 2014-07-08 | Go Daddy Operating Company, LLC | Domain name hijack protection |
US7130878B2 (en) * | 2002-08-30 | 2006-10-31 | The Go Daddy Group, Inc. | Systems and methods for domain name registration by proxy |
US7627633B2 (en) * | 2002-08-30 | 2009-12-01 | The Go Daddy Group, Inc. | Proxy email method and system |
KR20040025342A (en) * | 2002-09-19 | 2004-03-24 | (주) 닷포스 | Service offering system and method by domain registration states |
US20040059793A1 (en) * | 2002-09-20 | 2004-03-25 | Gruber Allen B. | Method and system for virtual website domain name service |
AU2003291078A1 (en) * | 2002-11-19 | 2004-06-15 | North American Internet, Llc | System and method for providing a one-time payment to secure a domain name |
US20040167982A1 (en) * | 2003-02-26 | 2004-08-26 | Cohen Michael A. | Multiple registrars |
US20040199620A1 (en) * | 2003-04-04 | 2004-10-07 | Tim Ruiz | Method for transfering a registered domain name from a first registrar to a second registrar |
US20040199608A1 (en) * | 2003-04-04 | 2004-10-07 | Rechterman Barbara J. | Method for gathering domain name registration information from a registrant via a Registrar's web site |
US20040199493A1 (en) * | 2003-04-04 | 2004-10-07 | Tim Ruiz | Method for registering a stream of domain names received via a registrar's web site |
US20040199520A1 (en) * | 2003-04-04 | 2004-10-07 | Parsons Advanced Holdings, Inc. | Method for checking the availability of a domain name |
US7320020B2 (en) * | 2003-04-17 | 2008-01-15 | The Go Daddy Group, Inc. | Mail server probability spam filter |
JP4335874B2 (en) * | 2003-06-18 | 2009-09-30 | テレフオンアクチーボラゲット エル エム エリクソン(パブル) | Online billing in mobile networks |
US7644117B2 (en) * | 2003-07-08 | 2010-01-05 | The Go Daddy Group, Inc. | Turnkey reseller program for registering domain names |
US7877432B2 (en) * | 2003-07-08 | 2011-01-25 | The Go Daddy Group, Inc. | Reseller program for registering domain names through resellers' web sites |
US20050047568A1 (en) * | 2003-08-25 | 2005-03-03 | David Nichols | Telephone number transfer |
US7566001B2 (en) | 2003-08-29 | 2009-07-28 | Semiconductor Energy Laboratory Co., Ltd. | IC card |
US8271488B2 (en) | 2003-09-16 | 2012-09-18 | Go Daddy Operating Company, LLC | Method for improving a web site's ranking with search engines |
US20050102348A1 (en) * | 2003-11-07 | 2005-05-12 | Parsons Robert R. | Integrated web based email system and document storage manager |
US20050210149A1 (en) * | 2004-03-03 | 2005-09-22 | Kimball Jordan L | Method, system, and computer useable medium to facilitate name preservation across an unrestricted set of TLDS |
US20070112950A1 (en) * | 2004-03-29 | 2007-05-17 | The Go Daddy Group, Inc. | Domain name expiration protection |
US20050216288A1 (en) * | 2004-03-29 | 2005-09-29 | Parsons Robert R | Process for registering and trademarking domain names |
US8356090B2 (en) | 2004-03-29 | 2013-01-15 | Go Daddy Operating Company, LLC | Method for a facilitator to assist an entrepreneur in creating an internet business |
US20050216287A1 (en) * | 2004-03-29 | 2005-09-29 | Crosby Michael W | Method for integrating an entrepreneur's web site and a store front web site |
CA2565077A1 (en) * | 2004-05-05 | 2005-11-17 | John Wong | System and methods for domain name acquisition and management |
US20050273344A1 (en) * | 2004-06-02 | 2005-12-08 | Lee Vincent M | Domain name maintenance |
US7702902B2 (en) | 2004-06-25 | 2010-04-20 | The Go Daddy Group, Inc. | Method for a web site with a proxy domain name registration to receive a secure socket layer certificate |
US7707404B2 (en) * | 2004-06-25 | 2010-04-27 | The Go Daddy Group, Inc. | Automated process for a web site to receive a secure socket layer certificate |
US20060168116A1 (en) * | 2004-06-25 | 2006-07-27 | The Go Daddy Group, Inc. | Methods of issuing a domain name certificate |
US8103761B2 (en) * | 2004-06-25 | 2012-01-24 | Go Daddy Holding Company, LLC | Methods of issuing a credit for a certificate for a domain name |
US8285816B2 (en) * | 2004-06-25 | 2012-10-09 | Go Daddy Operating Company, LLC | Methods of issuing a certificate for a domain name |
US8224964B1 (en) | 2004-06-30 | 2012-07-17 | Google Inc. | System and method of accessing a document efficiently through multi-tier web caching |
US7437364B1 (en) * | 2004-06-30 | 2008-10-14 | Google Inc. | System and method of accessing a document efficiently through multi-tier web caching |
US8676922B1 (en) | 2004-06-30 | 2014-03-18 | Google Inc. | Automatic proxy setting modification |
US7921162B2 (en) * | 2004-07-19 | 2011-04-05 | The Go Daddy Group, Inc. | Notification system and method for domain name registrars |
US20060282795A1 (en) * | 2004-09-13 | 2006-12-14 | Network Solutions, Llc | Domain bar |
WO2006031684A2 (en) * | 2004-09-13 | 2006-03-23 | Network Solutions, Llc | Domain bar |
US9009100B2 (en) | 2004-09-17 | 2015-04-14 | Go Daddy Operating Company, LLC | Web page customization based on a search term expertise level of a user |
US9002783B2 (en) | 2004-09-17 | 2015-04-07 | Go Daddy Operating Company, LLC | Web page customization based on expertise level of a user |
US7680901B2 (en) * | 2004-09-17 | 2010-03-16 | Go Daddy Group, Inc. | Customize a user interface of a web page using an expertise level rules engine |
US9015263B2 (en) | 2004-10-29 | 2015-04-21 | Go Daddy Operating Company, LLC | Domain name searching with reputation rating |
US20070208940A1 (en) * | 2004-10-29 | 2007-09-06 | The Go Daddy Group, Inc. | Digital identity related reputation tracking and publishing |
US20060200487A1 (en) * | 2004-10-29 | 2006-09-07 | The Go Daddy Group, Inc. | Domain name related reputation and secure certificates |
US20080028100A1 (en) * | 2004-10-29 | 2008-01-31 | The Go Daddy Group, Inc. | Tracking domain name related reputation |
US8904040B2 (en) * | 2004-10-29 | 2014-12-02 | Go Daddy Operating Company, LLC | Digital identity validation |
US20060095404A1 (en) * | 2004-10-29 | 2006-05-04 | The Go Daddy Group, Inc | Presenting search engine results based on domain name related reputation |
US20060095459A1 (en) * | 2004-10-29 | 2006-05-04 | Warren Adelman | Publishing domain name related reputation in whois records |
US7970858B2 (en) * | 2004-10-29 | 2011-06-28 | The Go Daddy Group, Inc. | Presenting search engine results based on domain name related reputation |
US20080022013A1 (en) * | 2004-10-29 | 2008-01-24 | The Go Daddy Group, Inc. | Publishing domain name related reputation in whois records |
US20080028443A1 (en) * | 2004-10-29 | 2008-01-31 | The Go Daddy Group, Inc. | Domain name related reputation and secure certificates |
US7797413B2 (en) * | 2004-10-29 | 2010-09-14 | The Go Daddy Group, Inc. | Digital identity registration |
US8117339B2 (en) * | 2004-10-29 | 2012-02-14 | Go Daddy Operating Company, LLC | Tracking domain name related reputation |
US7464136B2 (en) * | 2004-11-05 | 2008-12-09 | Microsoft Corporation | Integrated messaging domain name setup |
JP4305367B2 (en) * | 2004-11-05 | 2009-07-29 | ブラザー工業株式会社 | Communication apparatus and image forming apparatus |
US20060168020A1 (en) | 2004-12-10 | 2006-07-27 | Network Solutions, Llc | Private domain name registration |
US7580982B2 (en) * | 2004-12-14 | 2009-08-25 | The Go Daddy Group, Inc. | Email filtering system and method |
US20060167710A1 (en) * | 2005-01-25 | 2006-07-27 | King Martin T | Method and system for registering potential acquirers of assets that are not currently on the market |
US20050125451A1 (en) * | 2005-02-10 | 2005-06-09 | The Go Daddy Group, Inc. | Search engine and domain name search integration |
JP5076279B2 (en) * | 2005-03-17 | 2012-11-21 | 富士通株式会社 | IT asset management system, IT asset management method, and IT asset management program |
US20060218151A1 (en) * | 2005-03-25 | 2006-09-28 | The Go Daddy Group, Inc. | Use of a database storing domain names and business operational areas |
US20060218303A1 (en) * | 2005-03-25 | 2006-09-28 | The Go Daddy Group, Inc. | Creation of a database storing domain names and business operational areas |
US20060218289A1 (en) * | 2005-03-27 | 2006-09-28 | Elias Assad | Systems and methods of registering and utilizing domain names |
WO2006113401A2 (en) * | 2005-04-15 | 2006-10-26 | 1-800-Jackpot, Inc. | Systems and methods combining subscription services, rewards programs, and sweepstakes |
US7890369B2 (en) * | 2005-04-15 | 2011-02-15 | The Go Daddy Group, Inc. | Relevant online ads for domain name advertiser |
US7917389B2 (en) * | 2005-04-15 | 2011-03-29 | The Go Daddy Group, Inc. | Relevant email ads for domain name advertiser |
US7921035B2 (en) * | 2005-04-15 | 2011-04-05 | The Go Daddy Group, Inc. | Parked webpage domain name suggestions |
US8135778B1 (en) * | 2005-04-27 | 2012-03-13 | Symantec Corporation | Method and apparatus for certifying mass emailings |
KR100785902B1 (en) | 2006-04-11 | 2007-12-17 | 이승훈 | Domain registration system and domain registration method |
CN101479285A (en) | 2006-04-24 | 2009-07-08 | 安德鲁·阿特休勒 | System and method for selling a product multiple times during the life of the product |
US20080033866A1 (en) * | 2006-05-25 | 2008-02-07 | Lease This, Llc | System and a method for facilitating a lease on a domain name through an online competitive bidding process |
US20070299967A1 (en) * | 2006-06-23 | 2007-12-27 | Snapnames.Com, Inc. | Systems and methods to selectively acquire a domain name registration during an add grace period |
US8234379B2 (en) * | 2006-09-14 | 2012-07-31 | Afilias Limited | System and method for facilitating distribution of limited resources |
JP5335682B2 (en) * | 2006-10-24 | 2013-11-06 | アフィリアス・リミテッド | Supply chain discovery service |
US8812651B1 (en) | 2007-02-15 | 2014-08-19 | Google Inc. | Systems and methods for client cache awareness |
US20080201487A1 (en) * | 2007-02-16 | 2008-08-21 | Microsoft Corporation | Open dynamic domain name system |
US20090248623A1 (en) * | 2007-05-09 | 2009-10-01 | The Go Daddy Group, Inc. | Accessing digital identity related reputation data |
US20080300897A1 (en) * | 2007-06-01 | 2008-12-04 | Rafael Gazetov | Business method for domain name creation and marketing |
US20100036725A1 (en) * | 2007-06-07 | 2010-02-11 | Bhavin Turakhia | Method and system for providing a predetermined service to a domain registrant by a tld registry |
US8200644B2 (en) * | 2007-06-15 | 2012-06-12 | Bryte Computer Technologies, Inc. | Methods, systems, and computer program products for search result driven charitable donations |
US9015279B2 (en) * | 2007-06-15 | 2015-04-21 | Bryte Computer Technologies | Methods, systems, and computer program products for tokenized domain name resolution |
US20080318560A1 (en) * | 2007-06-25 | 2008-12-25 | Eli Reifman | Device Method and System for Handling Incoming Calls |
US8200694B1 (en) | 2007-07-23 | 2012-06-12 | Google Inc. | Identification of implicitly local queries |
US9178848B1 (en) * | 2007-07-23 | 2015-11-03 | Google Inc. | Identifying affiliated domains |
US8086622B2 (en) * | 2007-08-29 | 2011-12-27 | Enpulz, Llc | Search engine using world map with whois database search restrictions |
US8219533B2 (en) * | 2007-08-29 | 2012-07-10 | Enpulz Llc | Search engine feedback for developing reliable whois database reference for restricted search operation |
US8055671B2 (en) * | 2007-08-29 | 2011-11-08 | Enpulz, Llc | Search engine using world map with whois database search restriction |
US9008379B2 (en) * | 2007-10-26 | 2015-04-14 | Siemens Aktiengesellschaft | Pay for studies submitted (PASS) method for clinical trials |
US7805379B1 (en) | 2007-12-18 | 2010-09-28 | Amazon Technologies, Inc. | Method and system for leasing or purchasing domain names |
US9531581B1 (en) * | 2007-12-18 | 2016-12-27 | Amazon Technologies, Inc. | Method and system for identifying and automatically registering domain names |
US20090171678A1 (en) * | 2007-12-26 | 2009-07-02 | Michael Zimmerman | Protecting domain names from undesired transfer |
US20090171823A1 (en) * | 2007-12-26 | 2009-07-02 | Michael Zimmerman | Underwriting the sale of shares of equity in a domain name |
US7860755B2 (en) * | 2008-02-19 | 2010-12-28 | The Go Daddy Group, Inc. | Rating e-commerce transactions |
US7653577B2 (en) * | 2008-02-19 | 2010-01-26 | The Go Daddy Group, Inc. | Validating e-commerce transactions |
JP2011513866A (en) * | 2008-03-10 | 2011-04-28 | アフィリアス・リミテッド | Platform-independent IDN email storage conversion |
US8024456B2 (en) * | 2008-03-19 | 2011-09-20 | The Go Daddy Group, Inc. | Interactive DNS for controlling party |
US7904445B2 (en) * | 2008-03-26 | 2011-03-08 | The Go Daddy Group, Inc. | Displaying concept-based search results |
US8069187B2 (en) * | 2008-03-26 | 2011-11-29 | The Go Daddy Group, Inc. | Suggesting concept-based top-level domain names |
US7962438B2 (en) * | 2008-03-26 | 2011-06-14 | The Go Daddy Group, Inc. | Suggesting concept-based domain names |
US20090248736A1 (en) * | 2008-03-26 | 2009-10-01 | The Go Daddy Group, Inc. | Displaying concept-based targeted advertising |
US8799295B2 (en) * | 2008-04-04 | 2014-08-05 | Network Solutions Inc. | Method and system for scoring domain names |
US8788490B1 (en) | 2008-06-27 | 2014-07-22 | Google Inc. | Link based locale identification for domains and domain content |
US8234351B2 (en) * | 2008-07-24 | 2012-07-31 | Go Daddy Operating Company, LLC | Systems for generating and registering enhanced domain names |
US8301743B2 (en) | 2008-07-24 | 2012-10-30 | Go Daddy Operating Company, LLC | Enhanced domain name generation and registration |
US8422362B2 (en) * | 2008-08-05 | 2013-04-16 | At&T Intellectual Property I, Lp | Reliability as an interdomain service |
US8499032B2 (en) * | 2008-08-14 | 2013-07-30 | Yahoo! Inc. | System and method for compiling a set of domain names to recover |
US20100057484A1 (en) * | 2008-09-02 | 2010-03-04 | The Go Daddy Group, Inc. | Systems for generating business cards during domain name registration |
US20100058209A1 (en) * | 2008-09-02 | 2010-03-04 | The Go Daddy Group, Inc. | Business card generation during domain name registration |
US20100106650A1 (en) * | 2008-10-29 | 2010-04-29 | The Go Daddy Group, Inc. | Jointly auctioning expiring domain names |
US20100106616A1 (en) * | 2008-10-29 | 2010-04-29 | The Go Daddy Group, Inc. | Systems for jointly auctioning expiring domain names |
US20100146001A1 (en) * | 2008-12-04 | 2010-06-10 | The Go Daddy Group, Inc. | Systems for generating domain names relevant to current events |
US20100146119A1 (en) * | 2008-12-04 | 2010-06-10 | The Go Daddy Group, Inc. | Generating domain names relevant to current events |
US20100169492A1 (en) * | 2008-12-04 | 2010-07-01 | The Go Daddy Group, Inc. | Generating domain names relevant to social website trending topics |
US8285830B1 (en) | 2009-01-06 | 2012-10-09 | Citizenhawk, Inc. | System and method for combating cybersquatting |
US20100223143A1 (en) * | 2009-02-27 | 2010-09-02 | The Go Daddy Group, Inc. | Dynamic content relevant domain name suggestion in online advertising |
US20100223144A1 (en) * | 2009-02-27 | 2010-09-02 | The Go Daddy Group, Inc. | Systems for generating online advertisements offering dynamic content relevant domain names for registration |
US20100223132A1 (en) * | 2009-02-27 | 2010-09-02 | The Go Daddy Group, Inc. | Embedding advertisements offering available, dynamic-content-relevant domain names in online video |
US20100223278A1 (en) * | 2009-02-27 | 2010-09-02 | The Go Daddy Group, Inc. | Generating online advertisments based upon available dynamic content relevant domain names |
US20100223113A1 (en) * | 2009-02-27 | 2010-09-02 | The Go Daddy Group, Inc. | Systems for embedding advertisements offering available, dynamic-content-relevant domain names in online video |
US8806057B2 (en) | 2009-05-19 | 2014-08-12 | Neutral Space, Inc. | Internet-based value-added services system and method |
US20100325128A1 (en) * | 2009-06-18 | 2010-12-23 | The Go Daddy Group, Inc. | Generating and registering domain name-based screen names |
US20100325253A1 (en) * | 2009-06-18 | 2010-12-23 | The Go Daddy Group, Inc. | Generating and registering screen name-based domain names |
US8224923B2 (en) * | 2009-06-22 | 2012-07-17 | Verisign, Inc. | Characterizing unregistered domain names |
US8370504B2 (en) * | 2009-07-15 | 2013-02-05 | Verisign, Inc. | Method and system for predicting domain name registration renewal probability |
US20110016022A1 (en) * | 2009-07-16 | 2011-01-20 | Verisign, Inc. | Method and system for sale of domain names |
US8977705B2 (en) * | 2009-07-27 | 2015-03-10 | Verisign, Inc. | Method and system for data logging and analysis |
US8327019B2 (en) | 2009-08-18 | 2012-12-04 | Verisign, Inc. | Method and system for intelligent routing of requests over EPP |
US8856344B2 (en) | 2009-08-18 | 2014-10-07 | Verisign, Inc. | Method and system for intelligent many-to-many service routing over EPP |
US9384097B2 (en) | 2009-09-09 | 2016-07-05 | Verisign, Inc. | Method and system for recovery of a failed registry |
US8312364B2 (en) | 2009-09-17 | 2012-11-13 | Go Daddy Operating Company, LLC | Social website domain registration announcement and search engine feed |
US8276057B2 (en) | 2009-09-17 | 2012-09-25 | Go Daddy Operating Company, LLC | Announcing a domain name registration on a social website |
WO2011054071A1 (en) * | 2009-11-06 | 2011-05-12 | Edatanetworks Inc. | Method, system, and computer program for attracting localand regional businesses to an automated cause marketing environment |
US10861063B2 (en) | 2009-11-06 | 2020-12-08 | Edatanetworks Inc. | Method, system, and computer program for automated cause marketing using mobile devices |
US10902451B2 (en) | 2009-11-06 | 2021-01-26 | Edatanetworks Inc. | Systems and methods for loyalty programs |
US8209379B2 (en) * | 2009-11-25 | 2012-06-26 | Go Daddy Operating Company, LLC | Redirecting to a book website |
US8156180B2 (en) * | 2009-11-25 | 2012-04-10 | Go Daddy Operating Company, LLC | Tools for redirecting to a book website |
US8171110B1 (en) | 2009-12-11 | 2012-05-01 | Go Daddy Operating Company, LLC | Tools enabling a preferred placement service for domain registration websites |
US8280952B1 (en) | 2009-12-11 | 2012-10-02 | Go Daddy Operating Company, LLC | Methods implementing a preferred placement service for domain registration websites |
US7890602B1 (en) | 2009-12-11 | 2011-02-15 | The Go Daddy Group, Inc. | Tools enabling preferred domain positioning on a registration website |
US8370217B1 (en) | 2009-12-11 | 2013-02-05 | Go Daddy Operating Company, LLC | Methods for determining preferred domain positioning on a registration website |
US8195652B1 (en) | 2009-12-11 | 2012-06-05 | Go Daddy Operating Company, LLC | Preferred placement service for domain registration websites |
IT1397763B1 (en) * | 2009-12-22 | 2013-01-24 | Iunco | METHOD FOR MONITORING THE CANCELLATION OF INTERNET DOMAINS AND NEXT REGISTRATION. |
US8447701B2 (en) * | 2010-02-19 | 2013-05-21 | Go Daddy Operating Company, LLC | Appraising domain names using comparative data |
US8909558B1 (en) | 2010-02-19 | 2014-12-09 | Go Daddy Operating Company, LLC | Appraising a domain name using keyword monetary value data |
US8706728B2 (en) * | 2010-02-19 | 2014-04-22 | Go Daddy Operating Company, LLC | Calculating reliability scores from word splitting |
US9058393B1 (en) | 2010-02-19 | 2015-06-16 | Go Daddy Operating Company, LLC | Tools for appraising a domain name using keyword monetary value data |
US8447702B2 (en) * | 2010-02-19 | 2013-05-21 | Go Daddy Operating Company, LLC | Domain appraisal algorithm |
US20110208767A1 (en) * | 2010-02-19 | 2011-08-25 | The Go Daddy Group, Inc. | Semantic domain name spinning |
US20110208731A1 (en) * | 2010-02-19 | 2011-08-25 | The Go Daddy Group, Inc. | Automated semantic domain spinning tools |
US8515969B2 (en) * | 2010-02-19 | 2013-08-20 | Go Daddy Operating Company, LLC | Splitting a character string into keyword strings |
US8650878B2 (en) * | 2010-03-02 | 2014-02-18 | General Electric Company | Turbine system including valve for leak off line for controlling seal steam flow |
US8819148B2 (en) * | 2010-03-10 | 2014-08-26 | Afilias Limited | Alternate E-mail delivery |
US8312125B1 (en) * | 2010-03-12 | 2012-11-13 | Local Corporation | System and method for bulk web domain generation and management |
US8086684B2 (en) | 2010-04-20 | 2011-12-27 | The Go Daddy Group, Inc. | Detecting and mitigating undeliverable email |
US8601052B2 (en) | 2010-10-04 | 2013-12-03 | Qualcomm Incorporated | System and method of performing domain name server pre-fetching |
US9049229B2 (en) | 2010-10-28 | 2015-06-02 | Verisign, Inc. | Evaluation of DNS pre-registration data to predict future DNS traffic |
US8549479B2 (en) | 2010-11-09 | 2013-10-01 | Verisign, Inc. | Test automation tool for domain registration systems |
US8671221B2 (en) | 2010-11-17 | 2014-03-11 | Hola Networks Ltd. | Method and system for increasing speed of domain name system resolution within a computing device |
US20120173490A1 (en) * | 2010-12-30 | 2012-07-05 | Verisign, Inc. | Method and system for implementing business logic |
US20120185286A1 (en) * | 2011-01-17 | 2012-07-19 | Palo Alto Research Center Incorporated | Online continual automated planning framework based on timelines |
US9075886B2 (en) * | 2011-04-13 | 2015-07-07 | Verisign, Inc. | Systems and methods for detecting the stockpiling of domain names |
US8489746B2 (en) * | 2011-04-22 | 2013-07-16 | Go Daddy Operating Company, LLC | Systems for suggesting domain names from a geographic location data |
US9002926B2 (en) | 2011-04-22 | 2015-04-07 | Go Daddy Operating Company, LLC | Methods for suggesting domain names from a geographic location data |
US8818944B2 (en) | 2011-06-30 | 2014-08-26 | Microsoft Corporation | Data change tracking and event notification |
US8527309B2 (en) * | 2011-06-30 | 2013-09-03 | Verisign, Inc. | Targeted campaign management system and method |
US10565666B2 (en) * | 2011-09-26 | 2020-02-18 | Verisign, Inc. | Protect intellectual property (IP) rights across namespaces |
US9336551B1 (en) | 2011-09-29 | 2016-05-10 | Amazon Technologies, Inc. | Bidding on electronic resources |
CN102984299B (en) * | 2012-12-10 | 2015-09-16 | 中国科学院计算机网络信息中心 | Domain name registration, the method for parsing and service system is realized based on domain name group |
US10015134B2 (en) | 2011-12-29 | 2018-07-03 | Verisign, Inc. | Methods and systems for creating new domains |
US8949982B2 (en) | 2011-12-30 | 2015-02-03 | Verisign, Inc. | Method for administering a top-level domain |
TWI478561B (en) * | 2012-04-05 | 2015-03-21 | Inst Information Industry | Domain tracing method and system and computer-readable storage medium storing the method |
EP2658218A1 (en) | 2012-04-27 | 2013-10-30 | Verisign, Inc. | Bulk management of registry objects |
US9065855B2 (en) | 2012-06-29 | 2015-06-23 | Verisign, Inc. | Systems and methods for automatically providing Whois service to top level domains |
US9275040B1 (en) | 2012-09-14 | 2016-03-01 | Go Daddy Operating Company, LLC | Validating user control over contact information in a domain name registration database |
US20150095176A1 (en) * | 2012-10-01 | 2015-04-02 | Frank Taylor Schilling | Domain Name Marketplace With Mobile Sales And Brokerage Platform |
US20140095719A1 (en) * | 2012-10-03 | 2014-04-03 | Harris Andrew Decker | Creating, registering, and trading units representing internet protocol numbers |
US9065794B2 (en) | 2012-11-21 | 2015-06-23 | Verisign, Inc. | Systems and methods for providing domain name suggestions |
US20140156439A1 (en) * | 2012-12-03 | 2014-06-05 | Donald Foy | Method and Process of Conducting On Demand Electronic Auction |
CN102984298B (en) * | 2012-12-10 | 2015-07-22 | 中国科学院计算机网络信息中心 | Method and system for realizing domain name registration based on domain name group |
US20140188651A1 (en) * | 2013-01-02 | 2014-07-03 | Minds + Machines | Domain name registration and resale |
US10713356B2 (en) | 2013-03-04 | 2020-07-14 | Crowdstrike, Inc. | Deception-based responses to security attacks |
US9203856B2 (en) * | 2013-03-04 | 2015-12-01 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for detecting communication anomalies in a network based on overlap between sets of users communicating with entities in the network |
EP2779592A3 (en) * | 2013-03-15 | 2015-03-18 | Verisign, Inc. | Systems and methods for multi-tenant generic top level domain deployment |
US9904944B2 (en) | 2013-08-16 | 2018-02-27 | Go Daddy Operating Company, Llc. | System and method for domain name query metrics |
US9613374B2 (en) | 2013-10-10 | 2017-04-04 | Go Daddy Operating Company, LLC | Presentation of candidate domain name bundles in a user interface |
US9684918B2 (en) | 2013-10-10 | 2017-06-20 | Go Daddy Operating Company, LLC | System and method for candidate domain name generation |
US10140644B1 (en) | 2013-10-10 | 2018-11-27 | Go Daddy Operating Company, LLC | System and method for grouping candidate domain names for display |
US9866526B2 (en) | 2013-10-10 | 2018-01-09 | Go Daddy Operating Company, LLC | Presentation of candidate domain name stacks in a user interface |
US9715694B2 (en) | 2013-10-10 | 2017-07-25 | Go Daddy Operating Company, LLC | System and method for website personalization from survey data |
EP2871819A1 (en) | 2013-11-12 | 2015-05-13 | Verisign, Inc. | Multiple provisioning object operation |
US9929995B2 (en) * | 2014-05-21 | 2018-03-27 | Go Daddy Operating Company, LLC | Third party messaging system for monitoring and managing domain names and websites |
US10623468B1 (en) * | 2014-05-30 | 2020-04-14 | Mbr Innovations Llc | Systems and methods for simultaneous electronic file exchange |
US9756012B1 (en) * | 2014-06-16 | 2017-09-05 | Amazon Technologies, Inc. | Domain name service information propagation |
CN103996113A (en) * | 2014-06-20 | 2014-08-20 | 张康德 | Student and faculty-member management system |
US9769273B2 (en) | 2014-08-22 | 2017-09-19 | Go Daddy Operating Company, LLC | System and method for automatic configuration of domain names for third party services |
US9953105B1 (en) | 2014-10-01 | 2018-04-24 | Go Daddy Operating Company, LLC | System and method for creating subdomains or directories for a domain name |
US9954818B2 (en) * | 2014-10-23 | 2018-04-24 | Go Daddy Operating Company, LLC | Domain name hi-jack prevention |
US9785663B2 (en) | 2014-11-14 | 2017-10-10 | Go Daddy Operating Company, LLC | Verifying a correspondence address for a registrant |
US9779125B2 (en) | 2014-11-14 | 2017-10-03 | Go Daddy Operating Company, LLC | Ensuring accurate domain name contact information |
US9479533B2 (en) | 2014-12-18 | 2016-10-25 | Go Daddy Operating Company, LLC | Time based authentication codes |
US9479495B2 (en) | 2014-12-18 | 2016-10-25 | Go Daddy Operating Company, LLC | Sending authentication codes to multiple recipients |
US10164933B2 (en) | 2014-12-19 | 2018-12-25 | Go Daddy Operating Company, LLC | System and method for domain name system restore points |
US20160179822A1 (en) * | 2014-12-19 | 2016-06-23 | Go Daddy Operating Company, LLC | System and method for domain name system templates |
US10659423B2 (en) | 2014-12-19 | 2020-05-19 | Go Daddy Operating Company, LLC | System and method for modifying a domain name system template |
US10296506B2 (en) | 2015-01-07 | 2019-05-21 | Go Daddy Operating Company, LLC | Notifying users of available searched domain names |
US9865011B2 (en) | 2015-01-07 | 2018-01-09 | Go Daddy Operating Company, LLC | Notifying registrants of domain name valuations |
US9972041B2 (en) | 2015-02-18 | 2018-05-15 | Go Daddy Operating Company, LLC | Earmarking a short list of favorite domain names or searches |
TW201702955A (en) * | 2015-07-15 | 2017-01-16 | Chunghwa Telecom Co Ltd | System and method of carrying out common marketing promotion among different websites characterized by using a smart card encryption and decryption technique and a serial number of fabrication hardware apparatus to perform encryption computation on the smart card |
US9847874B2 (en) * | 2015-10-07 | 2017-12-19 | Go Daddy Operating Company, LLC | Intermediary organization account asset protection via an encoded physical mechanism |
US9929859B2 (en) | 2015-10-07 | 2018-03-27 | Go Daddy Operating Company, LLC | Account asset protection via an encoded physical mechanism |
CN106817344A (en) * | 2015-11-30 | 2017-06-09 | 北京泰尔英福网络科技有限责任公司 | A kind of method for auditing the domain name/real name for domain name registration/change operation |
CN106817343B (en) * | 2015-11-30 | 2021-05-25 | 中国信息通信研究院 | Method for auditing domain name/real name for domain name registration/change operation |
CN106817345A (en) * | 2015-11-30 | 2017-06-09 | 北京泰尔英福网络科技有限责任公司 | A kind of method for auditing the domain name/real name for domain name registration/change operation |
US10375017B2 (en) * | 2015-12-31 | 2019-08-06 | Verisign, Inc. | Detecting and mitigating registrar collusion in drop-add acquisitions of domain names |
US10320744B2 (en) | 2016-02-18 | 2019-06-11 | Verisign, Inc. | Systems, devices, and methods for dynamic allocation of domain name acquisition resources |
US10798093B2 (en) * | 2016-09-19 | 2020-10-06 | Verisign, Inc. | GTLD domain name registries RDAP architecture |
US11411913B2 (en) * | 2017-03-31 | 2022-08-09 | Verisign, Inc. | System and method for domain name registration using a cache |
US10476836B1 (en) * | 2017-04-12 | 2019-11-12 | Verisign, Inc. | Systems, devices, and methods for providing improved RDAP operations |
US10659426B2 (en) * | 2017-05-26 | 2020-05-19 | Verisign, Inc. | System and method for domain name system using a pool management service |
US10671640B2 (en) * | 2017-06-02 | 2020-06-02 | Apple Inc. | Adaptive cross-device event data synchronization |
US10701029B2 (en) | 2017-06-06 | 2020-06-30 | Hui Zhou | Processing platform and method to process domain name transactions for a remote domain name registry |
CN108306901B (en) * | 2018-05-11 | 2020-10-09 | 国家计算机网络与信息安全管理中心 | Method for acquiring domain name WHOWAS registration information |
CN108737591B (en) * | 2018-05-22 | 2021-09-14 | 华为技术有限公司 | Service configuration method and device |
KR102193058B1 (en) * | 2018-07-24 | 2020-12-18 | 이청종 | System and operating method for copyright billing and copyright profit distribution based on domain-digital asset interwork |
CN112583944B (en) * | 2019-09-27 | 2022-11-22 | 北京国双科技有限公司 | Processing method and device for updating domain name certificate |
US11552948B1 (en) | 2020-03-26 | 2023-01-10 | Amazon Technologies, Inc. | Domain management intermediary service |
CN112134902B (en) * | 2020-09-29 | 2022-04-15 | 科大国创云网科技有限公司 | RADB registration method and system based on API |
US20220321596A1 (en) * | 2021-04-06 | 2022-10-06 | Microsoft Technology Licensing, Llc | Dangling domain detection and access mitigation |
TWI815750B (en) * | 2022-12-12 | 2023-09-11 | 中華電信股份有限公司 | Automatic domain verification system, certificate issuance method and computer-readable medium |
Family Cites Families (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10795A (en) * | 1854-04-18 | Improvement in fishing rods and floats | ||
US4011545A (en) * | 1975-04-28 | 1977-03-08 | Ridan Computers, Inc. | Computer and communications systems employing new architectures |
US5671363A (en) | 1992-09-01 | 1997-09-23 | Merril Lynch, Pierce, Fenner & Smith Inc. | Private stock option account control and exercise system |
JPH0793969A (en) * | 1993-09-22 | 1995-04-07 | Olympus Optical Co Ltd | Ferroelectric capacitance element |
US5664111A (en) * | 1994-02-16 | 1997-09-02 | Honicorp, Inc. | Computerized, multimedia, network, real time, interactive marketing and transactional system |
WO1997008636A1 (en) * | 1995-08-23 | 1997-03-06 | Hitachi, Ltd. | State-adaptive type plan assistance system |
US5764906A (en) * | 1995-11-07 | 1998-06-09 | Netword Llc | Universal electronic resource denotation, request and delivery system |
US5987464A (en) * | 1996-07-26 | 1999-11-16 | Schneider; Eric | Method and system for periodically updating data records having an expiry time |
US6009459A (en) * | 1997-01-10 | 1999-12-28 | Microsoft Corporation | Intelligent automatic searching for resources in a distributed environment |
US6016515A (en) * | 1997-04-04 | 2000-01-18 | Microsoft Corporation | Method, computer program product, and data structure for validating creation of and routing messages to file object |
US7136932B1 (en) * | 1999-03-22 | 2006-11-14 | Eric Schneider | Fictitious domain name method, product, and apparatus |
US6895430B1 (en) * | 1999-10-01 | 2005-05-17 | Eric Schneider | Method and apparatus for integrating resolution services, registration services, and search services |
US6442549B1 (en) * | 1997-07-25 | 2002-08-27 | Eric Schneider | Method, product, and apparatus for processing reusable information |
US6760746B1 (en) * | 1999-09-01 | 2004-07-06 | Eric Schneider | Method, product, and apparatus for processing a data request |
US6560634B1 (en) * | 1997-08-15 | 2003-05-06 | Verisign, Inc. | Method of determining unavailability of an internet domain name |
US6016512A (en) | 1997-11-20 | 2000-01-18 | Telcordia Technologies, Inc. | Enhanced domain name service using a most frequently used domain names table and a validity code table |
JPH11225152A (en) * | 1998-02-09 | 1999-08-17 | Hitachi Ltd | Host name on tcp/p network and ip address management system |
JPH11288392A (en) * | 1998-04-02 | 1999-10-19 | Matsushita Electric Ind Co Ltd | Electronic mail system |
US6374295B2 (en) * | 1998-10-29 | 2002-04-16 | Nortel Networks Limited | Active server management |
KR100658489B1 (en) * | 1998-11-10 | 2006-12-18 | 얀센 파마슈티카 엔.브이. | HIV replication inhibiting pyrimidines |
EP1076869A1 (en) | 1999-02-05 | 2001-02-21 | Dealtime.Com, Ltd. | E-commerce notification |
US6314469B1 (en) * | 1999-02-26 | 2001-11-06 | I-Dns.Net International Pte Ltd | Multi-language domain name service |
US7167904B1 (en) * | 1999-03-19 | 2007-01-23 | Network Solutions, Llc | Unified web-based interface-to multiple registrar systems |
US6338082B1 (en) * | 1999-03-22 | 2002-01-08 | Eric Schneider | Method, product, and apparatus for requesting a network resource |
AU4800400A (en) * | 1999-04-22 | 2000-11-10 | Network Solutions, Inc. | Business rule engine |
US6880007B1 (en) * | 1999-06-07 | 2005-04-12 | Register Com, Inc. | Domain manager and method of use |
US6449657B2 (en) * | 1999-08-06 | 2002-09-10 | Namezero.Com, Inc. | Internet hosting system |
US6687746B1 (en) | 1999-08-30 | 2004-02-03 | Ideaflood, Inc. | System apparatus and method for hosting and assigning domain names on a wide area network |
US7747592B2 (en) * | 1999-09-07 | 2010-06-29 | Thomas C Douglass | Method and system for monitoring domain name registrations |
US7149893B1 (en) * | 1999-09-07 | 2006-12-12 | Poofaway.Com, Inc. | System and method for enabling the originator of an electronic mail message to preset an expiration time, date, and/or event, and to control processing or handling by a recipient |
US6298341B1 (en) | 1999-09-22 | 2001-10-02 | Raredomains.Com, Llc | System and method for generating domain names and for facilitating registration and transfer of the same |
US6980990B2 (en) | 1999-12-01 | 2005-12-27 | Barry Fellman | Internet domain name registration system |
US20010037253A1 (en) | 2000-03-06 | 2001-11-01 | Kensey Lanard M. | Secure format system for carrying out on-line purchasing of products |
WO2001082678A2 (en) | 2000-05-02 | 2001-11-08 | Sun Microsystems, Inc. | Cluster membership monitor |
US20020019800A1 (en) * | 2000-05-16 | 2002-02-14 | Ideaflood, Inc. | Method and apparatus for transacting divisible property |
US6922685B2 (en) * | 2000-05-22 | 2005-07-26 | Mci, Inc. | Method and system for managing partitioned data resources |
US7000028B1 (en) * | 2000-06-02 | 2006-02-14 | Verisign, Inc. | Automated domain name registration |
US20020010795A1 (en) * | 2000-06-09 | 2002-01-24 | Brown Charles P. | Method and system for protecting domain names |
US6745248B1 (en) * | 2000-08-02 | 2004-06-01 | Register.Com, Inc. | Method and apparatus for analyzing domain name registrations |
US7020602B1 (en) * | 2000-08-21 | 2006-03-28 | Kim Ki S | Native language domain name registration and usage |
AU2001296537A1 (en) * | 2000-10-02 | 2002-04-15 | Enic Corporation | Determining alternative textual identifiers, such as for registered domain names |
CA2427266C (en) * | 2000-11-01 | 2005-03-29 | Snapnames.Com, Inc. | Registry-integrated internet domain name acquisition system |
US20030225670A1 (en) * | 2002-05-31 | 2003-12-04 | Decarlo George J. | Auction style distribution of domain names |
WO2004015547A2 (en) * | 2002-08-13 | 2004-02-19 | Snapnames.Com, Inc. | Pathway-specific, registry-integrated domain name registration system |
US20040098375A1 (en) * | 2002-11-14 | 2004-05-20 | Dotster, Inc. | Automatic domain name status monitor |
-
2001
- 2001-11-01 CA CA002427266A patent/CA2427266C/en not_active Expired - Lifetime
- 2001-11-01 US US10/016,497 patent/US7418471B2/en not_active Expired - Lifetime
- 2001-11-01 AU AU2002243319A patent/AU2002243319A1/en not_active Abandoned
- 2001-11-01 WO PCT/US2001/047967 patent/WO2002056132A2/en not_active Application Discontinuation
- 2001-11-01 EP EP01992955A patent/EP1332445A4/en not_active Withdrawn
- 2001-11-01 CN CNB018181570A patent/CN100339846C/en not_active Expired - Lifetime
- 2001-11-01 WO PCT/US2001/048054 patent/WO2002037338A1/en not_active Application Discontinuation
- 2001-11-01 US US10/016,498 patent/US7039697B2/en not_active Expired - Lifetime
- 2001-11-01 CN CNB018181562A patent/CN1302418C/en not_active Expired - Lifetime
- 2001-11-01 EP EP01989207A patent/EP1337931A4/en not_active Withdrawn
- 2001-11-01 CA CA002429364A patent/CA2429364C/en not_active Expired - Lifetime
- 2001-11-01 AU AU2002227379A patent/AU2002227379A1/en not_active Abandoned
-
2006
- 2006-03-14 US US11/376,595 patent/US20060161681A1/en not_active Abandoned
- 2006-03-15 US US11/377,792 patent/US7752260B2/en not_active Expired - Fee Related
- 2006-03-17 US US11/378,504 patent/US7606858B2/en not_active Expired - Lifetime
- 2006-04-27 US US11/413,647 patent/US7490124B2/en not_active Expired - Lifetime
- 2006-12-15 US US11/611,769 patent/US7627628B2/en not_active Expired - Lifetime
-
2007
- 2007-05-11 US US11/747,827 patent/US7472160B2/en not_active Expired - Lifetime
-
2009
- 2009-06-02 US US12/476,495 patent/US8015244B2/en not_active Expired - Fee Related
- 2009-11-10 US US12/616,004 patent/US20100115043A1/en not_active Abandoned
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2427266C (en) | Registry-integrated internet domain name acquisition system | |
US7904898B2 (en) | Pathway-specific, registry-integrated domain name registration system | |
US6880007B1 (en) | Domain manager and method of use | |
US7694016B2 (en) | Composite DNS zones | |
US7076541B1 (en) | Method and apparatus providing distributed domain management capabilities | |
US7707289B1 (en) | Method and system for enabling persistent access to virtual servers by an LDNS server | |
US7257631B2 (en) | Domain manager and method of use | |
US7251826B1 (en) | Domain manager for plural domains and method of use | |
US20050203891A1 (en) | Automated domain name registration | |
US20020169890A1 (en) | Technique for content delivery over the internet | |
US20010034657A1 (en) | Method and apparatus for conducting domain name service | |
EP0966825A1 (en) | Method and apparatus for resolving network users to network computers | |
WO2005109228A2 (en) | System and methods for domain name acquisition and management | |
CA2527049A1 (en) | Domain name acquisition and management system and method | |
JP3405243B2 (en) | Workflow change system and workflow change method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKEX | Expiry |
Effective date: 20211101 |