US20060161681A1 - Internet domain name acquisition pending deletion - Google Patents

Internet domain name acquisition pending deletion Download PDF

Info

Publication number
US20060161681A1
US20060161681A1 US11/376,595 US37659506A US2006161681A1 US 20060161681 A1 US20060161681 A1 US 20060161681A1 US 37659506 A US37659506 A US 37659506A US 2006161681 A1 US2006161681 A1 US 2006161681A1
Authority
US
United States
Prior art keywords
domain name
registry
registrar
domain
acquisition
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.)
Abandoned
Application number
US11/376,595
Inventor
Raymond King
Len Bayles
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
SnapNames com Inc
Original Assignee
SnapNames com Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority to US24510200P priority Critical
Priority to US24834100P priority
Priority to US10/016,498 priority patent/US7039697B2/en
Application filed by SnapNames com Inc filed Critical SnapNames com Inc
Priority to US11/376,595 priority patent/US20060161681A1/en
Publication of US20060161681A1 publication Critical patent/US20060161681A1/en
Assigned to SNAPNAMES.COM, INC. reassignment SNAPNAMES.COM, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BAYLES, LEN ALBERT
Assigned to BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT reassignment BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT NOTICE OF GRANT OF SECURITY INTEREST Assignors: SNAPNAMES.COM, INC.
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/15Directories; Name-to-address mapping
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12047Directories; name-to-address mapping
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99933Query processing, i.e. searching

Abstract

A preferred embodiment of the present invention integrates a domain name monitoring and acquisition service with a registry system. The monitoring and acquisition service can receive a request from a registrar 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

    RELATED APPLICATIONS
  • This application is a continuation of and claims priority from U.S. application Ser. No. 10/016,498 filed Nov. 1, 2001, which claims priority from U.S. Provisional Patent Application Ser. No. 60/245,102, filed Nov. 1, 2000, and U.S. Provisional Patent Application Ser No. 60/248,341, filed Nov. 13, 2000, all incorporated herein by this reference.
  • COPY NOTICE
  • © 2000-2006 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
  • This invention pertains to distributed computer network node naming resolution processes and, more specifically, to registration of Internet domain names.
  • BACKGROUND OF THE INVENTION
  • 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.
  • 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.
  • 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).
  • 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 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.
  • 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.
  • 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.
  • 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. the 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.
  • 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.
  • New gTLDs are being added as the older ones—.com .net .org—become 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.
  • 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 finctions 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.
  • 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.
  • 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).
  • 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.
  • 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 is a matter of public record.
  • 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
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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
  • FIG. 1 is a simplified block diagram of a domain name management and acquisition system according to the present invention.
  • FIG. 2 illustrates a procedure for a registrar to obtain domain name acquisition services for a customer consistent with the present invention.
  • 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.
  • FIG. 4 is a flow diagram providing a logic overview of the process of FIG. 3.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • When referring to the following in FIG. 1, the term “systems” is meant to mean one or more, routers, layer two or three switches, computer systems, APIs, and software. In FIG. 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”).
  • 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.
  • 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.
  • 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 finction 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.
  • 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.
  • FIG. 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.
  • “C” Any communications paths between the Global Registry Management System 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 IDAS 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 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.
  • These links implement the necessary access to the Global Registry Management System (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.
  • FIG. 2, which illustrates a procedure for a Registrar to obtain a IDAS subscription, is as follows. A customer 200 makes a request 202 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. Responsive to the “DAS check request” the IDAS Frontend 116 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 FIG. 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 200, shown as message 220, typically via email.
  • 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.
  • 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).
  • FIG. 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.
  • 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 FIG. 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).
  • 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.
  • Referring again to FIG. 3, once a successfull 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.
  • FIG. 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.
  • 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 (1)

1. A method of internet domain name acquisition comprising:
receiving a request for a new registration of a domain name that is currently registered;
storing the request in a database;
receiving a pending delete notification for a currently registered domain name identified in the pending delete notification, from a registry system where the identified domain name is currently registered; the pending delete notification being received before the registry system purges the identified registration;
responsive to said receiving the pending delete notification, searching the database for a new registration request that matches the domain name identified in the pending delete notification; and
if a new registration request is found in the database for a domain name that matches the domain name identified in the pending delete notification, registering the domain name before the registry system purges the domain name.
US11/376,595 2000-11-01 2006-03-14 Internet domain name acquisition pending deletion Abandoned US20060161681A1 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US24510200P true 2000-11-01 2000-11-01
US24834100P true 2000-11-13 2000-11-13
US10/016,498 US7039697B2 (en) 2000-11-01 2001-11-01 Registry-integrated internet domain name acquisition system
US11/376,595 US20060161681A1 (en) 2000-11-01 2006-03-14 Internet domain name acquisition pending deletion

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US11/376,595 US20060161681A1 (en) 2000-11-01 2006-03-14 Internet domain name acquisition pending deletion

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/016,498 Continuation US7039697B2 (en) 2000-11-01 2001-11-01 Registry-integrated internet domain name acquisition system

Publications (1)

Publication Number Publication Date
US20060161681A1 true US20060161681A1 (en) 2006-07-20

Family

ID=26937001

Family Applications (10)

Application Number Title Priority Date Filing Date
US10/016,498 Active 2023-05-04 US7039697B2 (en) 2000-11-01 2001-11-01 Registry-integrated internet domain name acquisition system
US10/016,497 Active 2024-03-04 US7418471B2 (en) 2000-11-01 2001-11-01 Domain name acquisition and management system and method
US11/376,595 Abandoned US20060161681A1 (en) 2000-11-01 2006-03-14 Internet domain name acquisition pending deletion
US11/377,792 Active US7752260B2 (en) 2000-11-01 2006-03-15 Domain name acquisition and management system and method
US11/378,504 Active 2021-11-16 US7606858B2 (en) 2000-11-01 2006-03-17 Domain name acquisition and management system and method
US11/413,647 Active 2022-06-07 US7490124B2 (en) 2000-11-01 2006-04-27 Domain name acquisition and management system and method
US11/611,769 Active US7627628B2 (en) 2000-11-01 2006-12-15 Demand based domain name auctionability
US11/747,827 Active US7472160B2 (en) 2000-11-01 2007-05-11 Domain name management system and method
US12/476,495 Active 2021-11-12 US8015244B2 (en) 2000-11-01 2009-06-02 Domain name acquisition and management system and method
US12/616,004 Abandoned US20100115043A1 (en) 2000-11-01 2009-11-10 Demand based domain name auctionability

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US10/016,498 Active 2023-05-04 US7039697B2 (en) 2000-11-01 2001-11-01 Registry-integrated internet domain name acquisition system
US10/016,497 Active 2024-03-04 US7418471B2 (en) 2000-11-01 2001-11-01 Domain name acquisition and management system and method

Family Applications After (7)

Application Number Title Priority Date Filing Date
US11/377,792 Active US7752260B2 (en) 2000-11-01 2006-03-15 Domain name acquisition and management system and method
US11/378,504 Active 2021-11-16 US7606858B2 (en) 2000-11-01 2006-03-17 Domain name acquisition and management system and method
US11/413,647 Active 2022-06-07 US7490124B2 (en) 2000-11-01 2006-04-27 Domain name acquisition and management system and method
US11/611,769 Active US7627628B2 (en) 2000-11-01 2006-12-15 Demand based domain name auctionability
US11/747,827 Active US7472160B2 (en) 2000-11-01 2007-05-11 Domain name management system and method
US12/476,495 Active 2021-11-12 US8015244B2 (en) 2000-11-01 2009-06-02 Domain name acquisition and management system and method
US12/616,004 Abandoned US20100115043A1 (en) 2000-11-01 2009-11-10 Demand based domain name auctionability

Country Status (6)

Country Link
US (10) US7039697B2 (en)
EP (2) EP1332445A4 (en)
CN (2) CN1302418C (en)
AU (2) AU2002243319A1 (en)
CA (2) CA2427266C (en)
WO (2) WO2002037338A1 (en)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050010482A1 (en) * 2003-07-08 2005-01-13 The Go Daddy Group, Inc. Reseller program for registering domain names through resellers' web sites
US20050021588A1 (en) * 2003-07-08 2005-01-27 Michael Zimmerman Turnkey reseller program for registering domain names
US20120265748A1 (en) * 2011-04-13 2012-10-18 Verisign, Inc. Systems and methods for detecting the stockpiling of domain names
US8806057B2 (en) 2009-05-19 2014-08-12 Neutral Space, Inc. Internet-based value-added services system and method
US9015263B2 (en) 2004-10-29 2015-04-21 Go Daddy Operating Company, LLC Domain name searching with reputation rating
US9451050B2 (en) 2011-04-22 2016-09-20 Go Daddy Operating Company, LLC Domain name spinning from geographic location data
US9684918B2 (en) 2013-10-10 2017-06-20 Go Daddy Operating Company, LLC System and method for candidate domain name generation
US9715694B2 (en) 2013-10-10 2017-07-25 Go Daddy Operating Company, LLC System and method for website personalization from survey data
US9779125B2 (en) 2014-11-14 2017-10-03 Go Daddy Operating Company, LLC Ensuring accurate domain name contact information
US9785663B2 (en) 2014-11-14 2017-10-10 Go Daddy Operating Company, LLC Verifying a correspondence address for a registrant
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

Families Citing this family (224)

* Cited by examiner, † Cited by third party
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
AT441275T (en) 1998-10-30 2009-09-15 Virnetx Inc Network protocol for secure communications with assured system availability
US7188180B2 (en) 1998-10-30 2007-03-06 Vimetx, Inc. Method for establishing secure communication link between computers of virtual private network
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
US7167904B1 (en) * 1999-03-19 2007-01-23 Network Solutions, Llc Unified web-based interface-to multiple registrar systems
US7565402B2 (en) * 2002-01-05 2009-07-21 Eric Schneider Sitemap access method, product, and apparatus
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
US7188138B1 (en) 1999-03-22 2007-03-06 Eric Schneider Method, product, and apparatus for resource identifier registration and aftermarket services
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
US6760746B1 (en) 1999-09-01 2004-07-06 Eric Schneider Method, product, and apparatus for processing a data request
US6338082B1 (en) 1999-03-22 2002-01-08 Eric Schneider Method, product, and apparatus for requesting a network resource
KR100751622B1 (en) * 1999-11-26 2007-08-22 네테카 인코포레이티드 Network address 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
AU7532701A (en) * 2000-06-09 2001-12-24 Charles P Brown 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
US7315834B2 (en) * 2000-10-27 2008-01-01 Microsoft Corporation Wish list
WO2002037338A1 (en) * 2000-11-01 2002-05-10 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
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
US7904898B2 (en) * 2002-08-13 2011-03-08 Snapnames. Com, Inc. Pathway-specific, registry-integrated domain name registration system
US7627633B2 (en) * 2002-08-30 2009-12-01 The Go Daddy Group, Inc. Proxy email method and system
US7130878B2 (en) * 2002-08-30 2006-10-31 The Go Daddy Group, Inc. Systems and methods for domain name registration by proxy
US8775675B2 (en) * 2002-08-30 2014-07-08 Go Daddy Operating Company, LLC Domain name hijack protection
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
US20040199520A1 (en) * 2003-04-04 2004-10-07 Parsons Advanced Holdings, Inc. Method for checking the availability of a domain name
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
US7320020B2 (en) * 2003-04-17 2008-01-15 The Go Daddy Group, Inc. Mail server probability spam filter
WO2005004456A1 (en) * 2003-06-18 2005-01-13 Telefonaktiebolaget Lm Ericsson (Publ) Online charging in mobile networks
WO2005022324A2 (en) * 2003-08-25 2005-03-10 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
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
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
US20070112950A1 (en) * 2004-03-29 2007-05-17 The Go Daddy Group, Inc. Domain name expiration protection
WO2005109228A2 (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
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
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
US8285816B2 (en) * 2004-06-25 2012-10-09 Go Daddy Operating Company, LLC Methods of issuing a certificate for a domain name
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
US20060168116A1 (en) * 2004-06-25 2006-07-27 The Go Daddy Group, Inc. Methods of issuing a domain name certificate
US7437364B1 (en) * 2004-06-30 2008-10-14 Google Inc. System and method of accessing a document efficiently through multi-tier web caching
US8224964B1 (en) 2004-06-30 2012-07-17 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
US20060059136A1 (en) * 2004-09-13 2006-03-16 Network Solutions, Llc Domain bar
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
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
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
US20080028100A1 (en) * 2004-10-29 2008-01-31 The Go Daddy Group, Inc. Tracking domain name related reputation
US20070208940A1 (en) * 2004-10-29 2007-09-06 The Go Daddy Group, Inc. Digital identity related reputation tracking and publishing
US20080028443A1 (en) * 2004-10-29 2008-01-31 The Go Daddy Group, Inc. Domain name related reputation and secure certificates
US20080022013A1 (en) * 2004-10-29 2008-01-24 The Go Daddy Group, Inc. Publishing domain name related reputation in whois records
US7797413B2 (en) * 2004-10-29 2010-09-14 The Go Daddy Group, Inc. Digital identity registration
US20060200487A1 (en) * 2004-10-29 2006-09-07 The Go Daddy Group, Inc. Domain name related reputation and secure certificates
US7970858B2 (en) * 2004-10-29 2011-06-28 The Go Daddy Group, Inc. Presenting search engine results based on domain name related reputation
US20090248623A1 (en) * 2007-05-09 2009-10-01 The Go Daddy Group, Inc. Accessing digital identity related reputation data
US20060095459A1 (en) * 2004-10-29 2006-05-04 Warren Adelman Publishing domain name related reputation in whois records
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 an 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
US20060218303A1 (en) * 2005-03-25 2006-09-28 The Go Daddy Group, Inc. Creation of a database storing domain names and business operational areas
US20060218151A1 (en) * 2005-03-25 2006-09-28 The Go Daddy Group, Inc. Use 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
US7890369B2 (en) * 2005-04-15 2011-02-15 The Go Daddy Group, Inc. Relevant online ads for domain name advertiser
US7921035B2 (en) * 2005-04-15 2011-04-05 The Go Daddy Group, Inc. Parked webpage domain name suggestions
WO2006113401A2 (en) * 2005-04-15 2006-10-26 1-800-Jackpot, Inc. Systems and methods combining subscription services, rewards programs, and sweepstakes
US7917389B2 (en) * 2005-04-15 2011-03-29 The Go Daddy Group, Inc. Relevant email ads for domain name advertiser
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
US7962374B2 (en) 2006-04-24 2011-06-14 Andrew Altschuler 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
CA2667577C (en) * 2006-10-24 2017-11-07 Afilias Limited Supply chain discovery services
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
US20080300897A1 (en) * 2007-06-01 2008-12-04 Rafael Gazetov Business method for domain name creation and marketing
WO2009047784A2 (en) * 2007-06-07 2009-04-16 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
US8055671B2 (en) * 2007-08-29 2011-11-08 Enpulz, Llc Search engine using world map with whois database search restriction
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
US9008379B2 (en) * 2007-10-26 2015-04-14 Siemens Aktiengesellschaft Pay for studies submitted (PASS) method for clinical trials
US9531581B1 (en) * 2007-12-18 2016-12-27 Amazon Technologies, Inc. Method and system for identifying and automatically registering domain names
US7805379B1 (en) 2007-12-18 2010-09-28 Amazon Technologies, Inc. Method and system for leasing or purchasing domain names
US20090171823A1 (en) * 2007-12-26 2009-07-02 Michael Zimmerman Underwriting the sale of shares of equity in a domain name
US20090171678A1 (en) * 2007-12-26 2009-07-02 Michael Zimmerman Protecting domain names from undesired transfer
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
KR20160078511A (en) * 2008-03-10 2016-07-04 아필리어스 리미티드 Platform independent idn e-mail storage translation
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
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
US8069187B2 (en) * 2008-03-26 2011-11-29 The Go Daddy Group, Inc. Suggesting concept-based top-level domain names
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
US8301743B2 (en) * 2008-07-24 2012-10-30 Go Daddy Operating Company, LLC Enhanced domain name generation and registration
US8234351B2 (en) * 2008-07-24 2012-07-31 Go Daddy Operating Company, LLC Systems for generating and registering enhanced domain names
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
US20100058209A1 (en) * 2008-09-02 2010-03-04 The Go Daddy Group, Inc. Business card generation during domain name registration
US20100057484A1 (en) * 2008-09-02 2010-03-04 The Go Daddy Group, Inc. Systems for generating business cards during domain name registration
US20100106616A1 (en) * 2008-10-29 2010-04-29 The Go Daddy Group, Inc. Systems for jointly auctioning expiring domain names
US20100106650A1 (en) * 2008-10-29 2010-04-29 The Go Daddy Group, Inc. 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
US20100169492A1 (en) * 2008-12-04 2010-07-01 The Go Daddy Group, Inc. Generating domain names relevant to social website trending topics
US20100146119A1 (en) * 2008-12-04 2010-06-10 The Go Daddy Group, Inc. Generating domain names relevant to current events
US8285830B1 (en) 2009-01-06 2012-10-09 Citizenhawk, Inc. System and method for combating cybersquatting
US20100223278A1 (en) * 2009-02-27 2010-09-02 The Go Daddy Group, Inc. Generating online advertisments based upon available dynamic content relevant domain names
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
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
US20100223143A1 (en) * 2009-02-27 2010-09-02 The Go Daddy Group, Inc. Dynamic content relevant domain name suggestion in online advertising
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
US20100325253A1 (en) * 2009-06-18 2010-12-23 The Go Daddy Group, Inc. Generating and registering screen name-based domain names
US20100325128A1 (en) * 2009-06-18 2010-12-23 The Go Daddy Group, Inc. Generating and registering domain name-based screen 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
US8856344B2 (en) 2009-08-18 2014-10-07 Verisign, Inc. Method and system for intelligent many-to-many service routing over EPP
US8327019B2 (en) 2009-08-18 2012-12-04 Verisign, Inc. Method and system for intelligent routing of requests 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
US8156180B2 (en) * 2009-11-25 2012-04-10 Go Daddy Operating Company, LLC Tools for redirecting to a book website
US8209379B2 (en) * 2009-11-25 2012-06-26 Go Daddy Operating Company, LLC Redirecting to a book website
US8280952B1 (en) 2009-12-11 2012-10-02 Go Daddy Operating Company, LLC Methods implementing a preferred placement service for domain registration websites
US8370217B1 (en) 2009-12-11 2013-02-05 Go Daddy Operating Company, LLC Methods for determining preferred domain positioning on a registration website
US8171110B1 (en) 2009-12-11 2012-05-01 Go Daddy Operating Company, LLC Tools enabling 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
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 of the cancellation of the Internet and next recording domains.
US8515969B2 (en) * 2010-02-19 2013-08-20 Go Daddy Operating Company, LLC Splitting a character string into keyword strings
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
US9058393B1 (en) 2010-02-19 2015-06-16 Go Daddy Operating Company, LLC Tools for appraising a domain name using keyword monetary value data
US8447701B2 (en) * 2010-02-19 2013-05-21 Go Daddy Operating Company, LLC Appraising domain names using comparative data
US8447702B2 (en) * 2010-02-19 2013-05-21 Go Daddy Operating Company, LLC Domain appraisal algorithm
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
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
US8489746B2 (en) * 2011-04-22 2013-07-16 Go Daddy Operating Company, LLC Systems for suggesting domain names from a geographic location data
US8527309B2 (en) * 2011-06-30 2013-09-03 Verisign, Inc. Targeted campaign management system and method
US8818944B2 (en) 2011-06-30 2014-08-26 Microsoft Corporation Data change tracking and event notification
US9336551B1 (en) * 2011-09-29 2016-05-10 Amazon Technologies, Inc. Bidding on electronic resources
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
WO2014055072A1 (en) * 2012-10-03 2014-04-10 Decker Harris Andrew 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
CN102984299B (en) * 2012-12-10 2015-09-16 中国科学院计算机网络信息中心 Domain name registration based group achieved a domain name, analytical methods and service system
US20140188651A1 (en) * 2013-01-02 2014-07-03 Minds + Machines Domain name registration and resale
US20140250524A1 (en) * 2013-03-04 2014-09-04 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
US9866526B2 (en) 2013-10-10 2018-01-09 Go Daddy Operating Company, LLC Presentation of candidate domain name stacks in a user interface
US10140644B1 (en) 2013-10-10 2018-11-27 Go Daddy Operating Company, LLC System and method for grouping candidate domain names for display
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
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
US9954818B2 (en) * 2014-10-23 2018-04-24 Go Daddy Operating Company, LLC Domain name hi-jack prevention
US9479495B2 (en) 2014-12-18 2016-10-25 Go Daddy Operating Company, LLC Sending authentication codes to multiple recipients
US9479533B2 (en) 2014-12-18 2016-10-25 Go Daddy Operating Company, LLC Time based authentication codes
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
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
TWI560630B (en) * 2015-07-15 2016-12-01 Chunghwa Telecom Co Ltd
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
CN106817345A (en) * 2015-11-30 2017-06-09 北京泰尔英福网络科技有限责任公司 Domain name/real name checking method for domain name registration/change operation
CN106817343A (en) * 2015-11-30 2017-06-09 北京泰尔英福网络科技有限责任公司 Domain name/real name checking method for domain name registration/change operation
CN106817344A (en) * 2015-11-30 2017-06-09 北京泰尔英福网络科技有限责任公司 Domain name/real name checking method for domain name registration/change operation
US20170195285A1 (en) * 2015-12-31 2017-07-06 Verisign, Inc. Detecting and mitigating registrar collusion in drop-add acquisitions of domain names
US20170244668A1 (en) * 2016-02-18 2017-08-24 Verisign, Inc. Systems, devices, and methods for dynamic allocation of domain name acquisition resources
US20180287991A1 (en) * 2017-03-31 2018-10-04 Verisign, Inc. System and method for domain name registration using a cache
US20180351910A1 (en) * 2017-06-06 2018-12-06 Hui Zhou Processing platform and method to process domain name transactions for a remote domain name registry

Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
US5999915A (en) * 1994-02-16 1999-12-07 Honicorp, Inc. Computerized, multimedia, network, real time, interactive marketing and transactional system
US6009459A (en) * 1997-01-10 1999-12-28 Microsoft Corporation Intelligent automatic searching for resources in a distributed environment
US6249767B1 (en) * 1995-08-23 2001-06-19 Hitachi, Ltd. Portable information terminal surrounding formulation of an optimum plan
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
US6314469B1 (en) * 1999-02-26 2001-11-06 I-Dns.Net International Pte Ltd Multi-language domain name service
US6338082B1 (en) * 1999-03-22 2002-01-08 Eric Schneider Method, product, and apparatus for requesting a network resource
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
US6868441B2 (en) * 2000-05-22 2005-03-15 Mci, Inc. Method and system for implementing a global ecosystem of interrelated services
US6895430B1 (en) * 1999-10-01 2005-05-17 Eric Schneider Method and apparatus for integrating resolution services, registration services, and search services
US7000028B1 (en) * 2000-06-02 2006-02-14 Verisign, Inc. Automated domain name registration
US7020602B1 (en) * 2000-08-21 2006-03-28 Kim Ki S Native language domain name registration and usage
US7136932B1 (en) * 1999-03-22 2006-11-14 Eric Schneider Fictitious domain name method, product, and apparatus
US7167904B1 (en) * 1999-03-19 2007-01-23 Network Solutions, Llc Unified web-based interface-to multiple registrar systems

Family Cites Families (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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 substance capacitance element
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
US6374295B2 (en) * 1998-10-29 2002-04-16 Nortel Networks Limited Active server management
SK287270B6 (en) * 1998-11-10 2010-05-07 Janssen Pharmaceutica N. V. Pyrimidine derivative
AU2868000A (en) 1999-02-05 2000-08-25 Dealtime.Com, Ltd. E-commerce notification
AU4659100A (en) 1999-04-22 2000-11-10 Network Solutions, Inc. A shared registrations system for registering domain names
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
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
US7747592B2 (en) * 1999-09-07 2010-06-29 Thomas C Douglass Method and system for monitoring domain name registrations
US6980990B2 (en) * 1999-12-01 2005-12-27 Barry Fellman Internet domain name registration system
US20020019800A1 (en) 2000-05-16 2002-02-14 Ideaflood, Inc. Method and apparatus for transacting divisible property
US20010037253A1 (en) 2000-03-06 2001-11-01 Kensey Lanard M. Secure format system for carrying out on-line purchasing of products
AU5940201A (en) * 2000-05-02 2001-11-12 Sun Microsystems Inc Cluster membership monitor
AU7532701A (en) * 2000-06-09 2001-12-24 Charles P Brown 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
WO2002029593A1 (en) * 2000-10-02 2002-04-11 Enic Corporation Determining alternative textual identifiers, such as for registered domain names
WO2002037338A1 (en) 2000-11-01 2002-05-10 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
US7904898B2 (en) * 2002-08-13 2011-03-08 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

Patent Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5999915A (en) * 1994-02-16 1999-12-07 Honicorp, Inc. Computerized, multimedia, network, real time, interactive marketing and transactional system
US6249767B1 (en) * 1995-08-23 2001-06-19 Hitachi, Ltd. Portable information terminal surrounding formulation of an optimum plan
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
US6442549B1 (en) * 1997-07-25 2002-08-27 Eric Schneider Method, product, and apparatus for processing reusable information
US6314469B1 (en) * 1999-02-26 2001-11-06 I-Dns.Net International Pte Ltd Multi-language domain name service
US6446133B1 (en) * 1999-02-26 2002-09-03 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
US7136932B1 (en) * 1999-03-22 2006-11-14 Eric Schneider Fictitious domain name method, product, and apparatus
US6760746B1 (en) * 1999-09-01 2004-07-06 Eric Schneider Method, product, and apparatus for processing a data request
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
US6519589B2 (en) * 1999-09-22 2003-02-11 Raredomains.Com System and method for generating domain names and for facilitating registration and transfer of the same
US6895430B1 (en) * 1999-10-01 2005-05-17 Eric Schneider Method and apparatus for integrating resolution services, registration services, and search services
US6868441B2 (en) * 2000-05-22 2005-03-15 Mci, Inc. Method and system for implementing a global ecosystem of interrelated services
US7000028B1 (en) * 2000-06-02 2006-02-14 Verisign, Inc. Automated domain name registration
US7020602B1 (en) * 2000-08-21 2006-03-28 Kim Ki S Native language domain name registration and usage

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050021588A1 (en) * 2003-07-08 2005-01-27 Michael Zimmerman Turnkey reseller program for registering domain names
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
US20050010482A1 (en) * 2003-07-08 2005-01-13 The Go Daddy Group, Inc. Reseller program for registering domain names through resellers' web sites
US9015263B2 (en) 2004-10-29 2015-04-21 Go Daddy Operating Company, LLC Domain name searching with reputation rating
US8806057B2 (en) 2009-05-19 2014-08-12 Neutral Space, Inc. Internet-based value-added services system and method
US20120265748A1 (en) * 2011-04-13 2012-10-18 Verisign, Inc. Systems and methods for detecting the stockpiling of domain names
AU2012242839B2 (en) * 2011-04-13 2016-08-11 Verisign, Inc. Systems and methods for detecting the stockpiling of domain names
US9075886B2 (en) * 2011-04-13 2015-07-07 Verisign, Inc. Systems and methods for detecting the stockpiling of domain names
US9451050B2 (en) 2011-04-22 2016-09-20 Go Daddy Operating Company, LLC Domain name spinning from geographic location data
US9684918B2 (en) 2013-10-10 2017-06-20 Go Daddy Operating Company, LLC System and method for candidate domain name generation
US9715694B2 (en) 2013-10-10 2017-07-25 Go Daddy Operating Company, LLC System and method for website personalization from survey data
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
US9779125B2 (en) 2014-11-14 2017-10-03 Go Daddy Operating Company, LLC Ensuring accurate domain name contact information
US9785663B2 (en) 2014-11-14 2017-10-10 Go Daddy Operating Company, LLC Verifying a correspondence address for a registrant

Also Published As

Publication number Publication date
US7490124B2 (en) 2009-02-10
WO2002056132A3 (en) 2003-03-06
US20020091827A1 (en) 2002-07-11
CA2429364A1 (en) 2002-07-18
AU2002243319A1 (en) 2002-07-24
EP1332445A4 (en) 2005-05-25
US20070214284A1 (en) 2007-09-13
US7039697B2 (en) 2006-05-02
CN1575465A (en) 2005-02-02
CA2427266C (en) 2005-03-29
US20020091703A1 (en) 2002-07-11
CA2427266A1 (en) 2002-05-10
US20060195582A1 (en) 2006-08-31
US7472160B2 (en) 2008-12-30
EP1332445A1 (en) 2003-08-06
EP1337931A2 (en) 2003-08-27
WO2002037338A1 (en) 2002-05-10
US20060161683A1 (en) 2006-07-20
US8015244B2 (en) 2011-09-06
WO2002056132A2 (en) 2002-07-18
CN100339846C (en) 2007-09-26
US20090240812A1 (en) 2009-09-24
CN1302418C (en) 2007-02-28
US7752260B2 (en) 2010-07-06
EP1337931A4 (en) 2005-05-11
CN1471673A (en) 2004-01-28
US7627628B2 (en) 2009-12-01
US7606858B2 (en) 2009-10-20
US20060161682A1 (en) 2006-07-20
AU2737902A (en) 2002-05-15
CA2429364C (en) 2007-01-02
US20100115043A1 (en) 2010-05-06
US7418471B2 (en) 2008-08-26
US20070083652A1 (en) 2007-04-12

Similar Documents

Publication Publication Date Title
Mockapetris Domain names-concepts and facilities
US6694375B1 (en) Communications network and method having accessible directory of user profile data
US6366950B1 (en) System and method for verifying users' identity in a network using e-mail communication
CN1149474C (en) Reserved reguest method deifineded by routing events supervisor
JP4570252B2 (en) Determining a region to place a remote computer in the wide area network for delivering digitized products conditionally
CA2452998C (en) Method and system for providing static addresses for internet connected devices even if the underlying address is dynamic
CN100484125C (en) Answering method to address inquire and appts. thereof
US6374253B1 (en) System and method for generating hierarchical forward knowledge
US6173407B1 (en) Method of authenticating and charging a client using a web infoshop service system
Mockapetris RFC-1034 Domain Names-Concepts and Facilities
US9515981B2 (en) Method and system for increasing speed of domain name system resolution within a computing device
US8037168B2 (en) Method, product, and apparatus for enhancing resolution services, registration services, and search services
US7320026B2 (en) Intersystem messaging using ENUM standard
CA2310277C (en) Enhanced domain name service
US7653747B2 (en) Resolving virtual network names
EP0455402B1 (en) Automatic discovery of network elements
US20040167966A1 (en) Method and system for directing communications in a communications network
US6101537A (en) Universal electronic resource denotation, request and delivery system
US8285870B2 (en) Systems and methods for statistical resolution of domain name service (DNS) requests
EP2088744A1 (en) System and method for performing client-centric load balancing of multiple globally-dispersed servers
US6256747B1 (en) Method of managing distributed servers and distributed information processing system using the method
US7277911B2 (en) Method and system for controlled distribution of contact profiles over a network
CN100536444C (en) Data packet commmunication device
JP4684534B2 (en) Homology resources between cached resources in a peer-to-peer environment
US6678717B1 (en) Method, product, and apparatus for requesting a network resource

Legal Events

Date Code Title Description
AS Assignment

Owner name: SNAPNAMES.COM, INC., OREGON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BAYLES, LEN ALBERT;REEL/FRAME:019646/0501

Effective date: 20020304

AS Assignment

Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, WA

Free format text: NOTICE OF GRANT OF SECURITY INTEREST;ASSIGNOR:SNAPNAMES.COM, INC.;REEL/FRAME:019704/0870

Effective date: 20061122