CA2300421A1 - Method of determining unavailability of internet domain names - Google Patents
Method of determining unavailability of internet domain names Download PDFInfo
- Publication number
- CA2300421A1 CA2300421A1 CA002300421A CA2300421A CA2300421A1 CA 2300421 A1 CA2300421 A1 CA 2300421A1 CA 002300421 A CA002300421 A CA 002300421A CA 2300421 A CA2300421 A CA 2300421A CA 2300421 A1 CA2300421 A1 CA 2300421A1
- Authority
- CA
- Canada
- Prior art keywords
- domain
- domains
- domain name
- specified
- search
- 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
Links
Classifications
-
- 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/30—Managing network names, e.g. use of aliases or nicknames
- H04L61/3005—Mechanisms for avoiding name conflicts
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
-
- 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/30—Managing network names, e.g. use of aliases or nicknames
-
- 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
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/567—Integrating service provisioning from a plurality of service providers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Abstract
Methods, systems, and articles of manufacture consistent with the present invention provide an improved query server that overcomes the shortcomings of existing domain name searching techniques by performing a multitude of searches simultaneously, transparent to the user. Specifically, the improved query server searches for existing domain name records in various domains and then displays the results in a formatted manner, thus eliminating the need for a user to perform individual searches.
Description
Method Of Determining Unavailability Of Internet Domain Names Provisional U.S. Patent Application No. 60/055,787, entitled "Method of Deternlining Unavailability of an Internet Domain Name," filed on August 15, 1997, is relied upon and is incorporated by reference in this application.
A. Field of the Invention This invention relates generally to data processing systems and, more particularly, to a method for determining. if an Internet domain name has been registered in a specific domain.
B. Descri~~tion of the Related Art Internet domain names are related to Internet Protocol (IP) numerical addresses. Every "host" that is linked directly to the Internet (e.g., computers) must be identified by a specific IP numerical address. Data transmission over the Internet is in fact accomplished by directing the data to such numerical addresses. An IP address includes four numbers separated by periods. Currently, each number must be between 0 and 255.
Numerical addresses, however, are difficult for humans to remember.
Consequently, a domain name may be used as part of what amounts to a type of mnemonic for that IP address.
For example, the domain name infoway.com, forms part of ns.infoway.com, which is an easier-to-remember mnemonic for the host located at IP address 207.90.216.53.
In this way, the mnemonic is at least roughly analogous to the letters that are sometimes used to signify a specific telephone number, e.g., 1-800-FLOWERS is a mnemonic for 1-800-356-9377.
The availability of Internet domain names (e.g., "ibm.com," "microsoft.com,"
"netscape.com," etc.) is now a significant business issue, because a domain name is the identifier by which an individual, a company, a governmental entity, an educational institution, etc. (referred to collectively as simply "companies") can be found on the Internet.
As is well known in the art, minor variations in a name can be registered with the InterNIC as domain names. The InterNIC is a registration service for registering domain names located at Network Solutions, Inc., Herndon, VA. For example, it has been reported that the domain names 1-800-DENTIST.COM and 1800DENTISTCOM are owned by two different entities.
A. Field of the Invention This invention relates generally to data processing systems and, more particularly, to a method for determining. if an Internet domain name has been registered in a specific domain.
B. Descri~~tion of the Related Art Internet domain names are related to Internet Protocol (IP) numerical addresses. Every "host" that is linked directly to the Internet (e.g., computers) must be identified by a specific IP numerical address. Data transmission over the Internet is in fact accomplished by directing the data to such numerical addresses. An IP address includes four numbers separated by periods. Currently, each number must be between 0 and 255.
Numerical addresses, however, are difficult for humans to remember.
Consequently, a domain name may be used as part of what amounts to a type of mnemonic for that IP address.
For example, the domain name infoway.com, forms part of ns.infoway.com, which is an easier-to-remember mnemonic for the host located at IP address 207.90.216.53.
In this way, the mnemonic is at least roughly analogous to the letters that are sometimes used to signify a specific telephone number, e.g., 1-800-FLOWERS is a mnemonic for 1-800-356-9377.
The availability of Internet domain names (e.g., "ibm.com," "microsoft.com,"
"netscape.com," etc.) is now a significant business issue, because a domain name is the identifier by which an individual, a company, a governmental entity, an educational institution, etc. (referred to collectively as simply "companies") can be found on the Internet.
As is well known in the art, minor variations in a name can be registered with the InterNIC as domain names. The InterNIC is a registration service for registering domain names located at Network Solutions, Inc., Herndon, VA. For example, it has been reported that the domain names 1-800-DENTIST.COM and 1800DENTISTCOM are owned by two different entities.
In addition, companies that have, or aspire to have, an international Internet presence must keep in mind the domain name scheme in other countries. For example, it has been reported that "apple.com" and "apple.co.uk" are owned by different companies, as are "apple.net" and "apple.org."
Domain names are specific to a domain, which is a geographic area defined at a global-level or at a country-level. A global-level domain covers all countries worldwide. Examples of global-level domains include .corn, .edu, .gov, and .org. A country-level domain covers only a given country. Examples of country-Ievel domains include .us for the United States and .fr for France. Additionally, country-level domains may contain an indication of a sub-domain within the domain. When a sub-domain is specified for a domain name, the domain name is recognized only in that sub-domain and not the country-level domain that it is a part of.
The term "domain name system" (DNS) refers to a distributed database that is responsible for translating the Internet names into numerical addresses (e.g., 207.90.216.53), routing mail to its proper destination and many other services. The DNS
comprises DNS
servers or other machines that runs software permitting it to query a database (hosted either locally or on another machine) referred to as a DNS database. The DNS database contains records associating particular domain names with specific Internet Protocol (IP) numerical addresses (e.g., 207.90.216.53).
A user that wishes to check the availability of a domain name in, for example, five different countries will typically submit a separate Whois query, or its equivalent, to the domain-name registration authority in each country. Whois queries provide a way of finding registering organization names, e-mail addresses, administrative technical and billing contacts, postal addresses, and telephone numbers, of those who have registered domain names. Whois is available for use from "http://rs.internic.org," and available for download at "http://www.shareware.com." The queries might be automated to the extent that the countries in question support automated electronic queries (e.g., via a Web browser form), but in other countries the queries must be initiated by some other means, e.g., FAX, mail, email, phone call, etc. In either case, to perform a query for registered domain names in multiple countries, a user would have to submit a separate search request to each domain, thus making the searching process very time-consuming and cumbersome. It is therefore desirable to improve systems that search for domain names.
SUMMARY OF T)E ~. TNVFNTInN
Methods, systems, and articles of manufacture consistent with the present invention provide an improved query server that overcomes the shortcomings of existing domain name searching techniques by performing a multitude of searches simultaneously, transparent to the user. Specifically, the improved query server searches for an existing domain name records in various domains and then displays the results in a formatted manner, thus eliminating the need for a user to perform individual searches.
In accordance with methods consistent with the present invention, a method is provided in a data processing system with DNS servers, each responsible for maintaining registration records of domain names for an associated domain. This method receives user input containing a domain name and specified ones of the domains, transmits a request for a search of the domain names to the DNS servers associated with the specified domains, receives search results from the DNS servers associated with the specified domains, and displays the search results. The search results indicate, for each of the specified domains, whether a domain name record exists in the specified domain.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate an implementation of the invention and, together with the description, serve to explain the advantages and principles of the invention. In the drawings, Figure 1 depicts a data processing system suitable for practicing methods and systems consistent with the present invention;
Figure 2 depicts a more detailed diagram of the query server depicted in Fig.
I;
Figure 3 depicts a more detailed diagram of one of the DNS servers depicted in Fig. 1;
Figure 4 depicts a flow chart of the steps performed by the query engine of Fig. 1 when searching for registered domain names in accordance with methods and systems consistent with the present invention;
Figures Sa-Sb depict a user interface in accordance with methods and systems consistent with the present invention; and Figures 6a-6c depict example display outputs in accordance with methods and systems consistent with the present invention.
The following detailed description of the invention refers to the accompanying drawings.
Although, the description includes exemplary implementations, other implementations are possible, and changes may be made to the implementations described without departing from the spirit and scope of the invention. The following detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims. Wherever possible, the same reference numbers will be used throughout the drawings and the following description to refer to the same or like parts.
In accordance with methods and systems consistent with the present invention, a query server is provided that receives a query from a user of a client computer using a client program such as Netscape Navigator or Microsoft Internet Explorer. The query server receives the query from the client computer either directly or, alternatively, via one or more intermediary computers such as one operated by an Internet access provider, an on-line service, etc. Although the client program may generate a query at one computer, the results of the query may be returned by the query server to another computer. The format of the query can take any of a number of forms (e.g., with switches in a command line or check boxes in a graphical user interface).
The query results in the generation of a response indicating, for example, that a specified Internet host name (e.g., apple) has been registered in a specified domain (e.g., the sub-domain .co within the country-level domain .uk), resulting in a domain name (e.g., apple.co.uk).
Fig.l depicts a data processing system 100 suitable for practicing methods and systems consistent with the present invention. Data processing system 100 includes a client computer 106, a query server 104, and a number of DNS servers 108 interconnected via network 102.
Domain names are specific to a domain, which is a geographic area defined at a global-level or at a country-level. A global-level domain covers all countries worldwide. Examples of global-level domains include .corn, .edu, .gov, and .org. A country-level domain covers only a given country. Examples of country-Ievel domains include .us for the United States and .fr for France. Additionally, country-level domains may contain an indication of a sub-domain within the domain. When a sub-domain is specified for a domain name, the domain name is recognized only in that sub-domain and not the country-level domain that it is a part of.
The term "domain name system" (DNS) refers to a distributed database that is responsible for translating the Internet names into numerical addresses (e.g., 207.90.216.53), routing mail to its proper destination and many other services. The DNS
comprises DNS
servers or other machines that runs software permitting it to query a database (hosted either locally or on another machine) referred to as a DNS database. The DNS database contains records associating particular domain names with specific Internet Protocol (IP) numerical addresses (e.g., 207.90.216.53).
A user that wishes to check the availability of a domain name in, for example, five different countries will typically submit a separate Whois query, or its equivalent, to the domain-name registration authority in each country. Whois queries provide a way of finding registering organization names, e-mail addresses, administrative technical and billing contacts, postal addresses, and telephone numbers, of those who have registered domain names. Whois is available for use from "http://rs.internic.org," and available for download at "http://www.shareware.com." The queries might be automated to the extent that the countries in question support automated electronic queries (e.g., via a Web browser form), but in other countries the queries must be initiated by some other means, e.g., FAX, mail, email, phone call, etc. In either case, to perform a query for registered domain names in multiple countries, a user would have to submit a separate search request to each domain, thus making the searching process very time-consuming and cumbersome. It is therefore desirable to improve systems that search for domain names.
SUMMARY OF T)E ~. TNVFNTInN
Methods, systems, and articles of manufacture consistent with the present invention provide an improved query server that overcomes the shortcomings of existing domain name searching techniques by performing a multitude of searches simultaneously, transparent to the user. Specifically, the improved query server searches for an existing domain name records in various domains and then displays the results in a formatted manner, thus eliminating the need for a user to perform individual searches.
In accordance with methods consistent with the present invention, a method is provided in a data processing system with DNS servers, each responsible for maintaining registration records of domain names for an associated domain. This method receives user input containing a domain name and specified ones of the domains, transmits a request for a search of the domain names to the DNS servers associated with the specified domains, receives search results from the DNS servers associated with the specified domains, and displays the search results. The search results indicate, for each of the specified domains, whether a domain name record exists in the specified domain.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate an implementation of the invention and, together with the description, serve to explain the advantages and principles of the invention. In the drawings, Figure 1 depicts a data processing system suitable for practicing methods and systems consistent with the present invention;
Figure 2 depicts a more detailed diagram of the query server depicted in Fig.
I;
Figure 3 depicts a more detailed diagram of one of the DNS servers depicted in Fig. 1;
Figure 4 depicts a flow chart of the steps performed by the query engine of Fig. 1 when searching for registered domain names in accordance with methods and systems consistent with the present invention;
Figures Sa-Sb depict a user interface in accordance with methods and systems consistent with the present invention; and Figures 6a-6c depict example display outputs in accordance with methods and systems consistent with the present invention.
The following detailed description of the invention refers to the accompanying drawings.
Although, the description includes exemplary implementations, other implementations are possible, and changes may be made to the implementations described without departing from the spirit and scope of the invention. The following detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims. Wherever possible, the same reference numbers will be used throughout the drawings and the following description to refer to the same or like parts.
In accordance with methods and systems consistent with the present invention, a query server is provided that receives a query from a user of a client computer using a client program such as Netscape Navigator or Microsoft Internet Explorer. The query server receives the query from the client computer either directly or, alternatively, via one or more intermediary computers such as one operated by an Internet access provider, an on-line service, etc. Although the client program may generate a query at one computer, the results of the query may be returned by the query server to another computer. The format of the query can take any of a number of forms (e.g., with switches in a command line or check boxes in a graphical user interface).
The query results in the generation of a response indicating, for example, that a specified Internet host name (e.g., apple) has been registered in a specified domain (e.g., the sub-domain .co within the country-level domain .uk), resulting in a domain name (e.g., apple.co.uk).
Fig.l depicts a data processing system 100 suitable for practicing methods and systems consistent with the present invention. Data processing system 100 includes a client computer 106, a query server 104, and a number of DNS servers 108 interconnected via network 102.
The client computer 106 is used by the user to submit queries to query server 104. Query server 104 receives the queries from the client computer 106 and performs these queries on DNS servers 108. Query server 104 may also contain Hyper Text Markup Language (HT'ML) code for transfer to a browser on the client computer 106. DNS servers 108 contain a domain name database that associates DNS records with domain names. A DNS
record contains a domain name and the associated numerical address. DNS records may also contain textual information regarding the domain name. For example, a DNS
record may indicate a contact person for a particular domain name. DNS servers 108 receive query requests from the query server 104 and search the domain name database for a DNS record associated with the domain name. Although only one client computer 106 is depicted, one skilled in the art will appreciate that data processing system 100 may contain many more client computers.
FIG 2. depicts a more detailed diagram of query server 104. Query server 104 contains a memory 220, a secondary storage device 230, a central processing unit ("CPU") 240, an input device 250, and a video display 260. Memory 220 includes domain name query engine 222 that interacts with client computer 106 and DNS servers 108. Query engine 222 includes query software 224 that submits search requests to various DNS servers 108 located throughout the network. One example of the query software may be a UNIX
utility tool called "nslookup" available on most UNIX platforms. Alternatively, query software 226 may be a script to interact with various Domain Name Servers. Query engine 222 also includes search engine 226 that uses a forking system to perform domain name queries in parallel.
The forking system initiates multiple sub-processes to perform a subset of the queries once the query process has begun. The forking system reduces the total time to complete a search since multiple sub-processes will perform the queries in parallel. Query engine 222 further includes HT'ML parser 228 that parses H'TML form parameters passed to and from the client browser when a search is submitted to the search engine 226. Search engine 226, query software 224 and HTML parser 228 are preferably written in the PERL
environment available for download from Internet sites, such as "http://www.perl.com."
Secondary storage device 230 includes a domain file 232 that includes a listing of the available domains used by the search engine to create the queries. Also included in domain file 232 is a domain extension suffix to append to the domain name to create a full domain name to be searched. For example, the domain extension suffix ".co.uk" when combined with the domain name "apple" will create the full domain name "apple.co.uk."
Domain file 232 may also contain the numerical address of a DNS server for each domain and whether the domain supports a Whois query. Moreover, domain file 232 may also optionally include other fields for specialized searches, such as Gross Domestic Product (GDP) or whether the domain is a member of European Union or a Western country. These specialized fields allow the user to crieate a specialized domain name search in various environments.
For example, a user may select to search for a domain name located in a top SO GDP country.
One skilled in the art will appreciate that other specialized fields may exist, including Asian countries or even high Internet usage countries.
Fig. 3 depicts in greater detail an exemplary DNS server 108. DNS server 108 contains a memory 320, a secondary storage device 330, a central processing unit ("CPU") 340, an input device 350, and a video display 360. Secondary storage device 330 includes DNS
server database 332 containing resource records that describe all the registered domain names within it's zone. A "zone" contains the domain names and data that a domain contains, except for domain names and data that are delegated to a sub-domain. For example, the domain "ca" (for Canada) may have the sub-domains "ab.ca" (Alberta), "on.ca"
(Ontario), and "qb.ca" (Quebec). Authority for the "ab.ca," "on.ca," and "qb.ca" domains may be delegated to the DNS servers in each of the provinces. The domain "ca"
contains all the data in "ca" plus all the data in "ab.ca," "on.ca," and "qb.ca." However, the zone "ca" contains only the data in "ca". In other words, the domain name "apple.ca" is listed in the "ca" DNS
server database, while the domain name "apple.qb.ca" is listed in the "qb.ca°' DNS database.
Memory 320 includes program 322 that receives search requests from query server 104 for searching and retrieving information about the domain name from DNS database 332. One example of program 322 may be Berkeley Internet Name Domain (BIND) implementation of DNS available for download from the Internet Software Consortium at "http://www.isc.org."
Although aspects of the present invention are described as being stored in memory, one skilled in the art will appreciate that these aspects may be stored on or read from other computer-readable media, such as secondary storage devices, like hard disks, floppy disks and CD-ROM; a carrier wave received from a network like the Internet; or other forms of ROM or RAM. Additionally, although specific components and programs of query server 104 and DNS server 108 have been described, one skilled in the art will appreciate that a query server or a DNS server suitable for use with methods and systems consistent with the present invention may contain additional or different components.
Domain Name Searching Process Further details on operation of the search process will now be explained with reference to the flow chart of Fig. 4. The domain name search process is initiated, for example, by a request from client computer 106 to perform a search for a domain name (step 402). For example, client computer 106 may send an HTML request to query engine 104 using the well known Hypertext Transfer Protocol. Once the request is received, query engine interrogates domain file 232 (step 404) and transmits all possible domains to search and the accompanying specialized fields in an HTML format to display on client computer 106 (step 406). That is, query engine 222 transmits a possible domain to search ".uk"
with an identification that the domain is part of the European Union and also from a top 50 GDP
country.
Once displayed, a user using client computer 106 enters a domain name to search, for example "apple," and a type of search to be performed, for example "top 50 GDP
countries"
(step 408). A user may request a search for registered domain names in all domains, as shown in Fig. Sa. Alternatively, the user may request a specialized search.
That is, a search for a registered domain name in a set of domains based on the accompanying specialized fields. For example, a user may request to search in only the top 50 countries ranked by annual GDP, as depicted in Fig. Sb. One skilled in the art will appreciate that other combinations of domain selections exists, for example Western countries, Asian countries or a customized search, in that the user at client computer 106 may select a subset of domains to search from the total number of domains.
Upon the user at client computer 106 entering a domain name to search, client computer 106 sends the user input to query server 104 (step 410). Once received at query server 104, HTML parser 228 parses a listing of domains and a domain name to search submitted by the client computer 106 (step 412). Query engine 222 then invokes search engine 226 to spawn a number of search sub-processes (step 414). In this step, search engine 226 calculates the number of search sub-processes to spawn based on the number of domains to query -g submitted by client computer 106 so that each search sub-process contains at most 11 domains to search. Essentially, search engine 226 forks the queries into multiple sub-processes to perform the domain name searches in parallel for optimized performance. Each spawned search sub-process is given a subset of domains to query, thus query server 104 may perform multiple queries at once. For example, if client browser 106 selects 50 domains to query, search engine 226 may spawn 5 search sub-processes, so that each spawned search sub-process queries 10 DNS servers. Further, depending on the load of query server 104, search engine 226 may change the number of search sub-processes to spawn.
Once the search processes are spawned, a separate section of query engine 222, query software 224, transmits, to a DNS server for the domain in question (e.g., a DNS server 108 for .qb.ca or for .com), a request for a search of a domain-name database for a DNS record associated with the domain name (step 416). The transmission of the search request could be direct, but more likely will be relayed through one or more intermediary machines. For example, a search request generated by a query server in Houston could be transmitted to London, then to Moscow, and then to Zimbabwe, where the target DNS server 108 might be located.
In response to the search request, the DNS server 108 searches its domain-name database for a DNS record associated with the specified domain name (step 418). The DNS
server 108 generates a response that indicates whether a DNS record was found for that domain name.
Query server 104 ultimately receives the response from DNS server 108 (step 420) and keeps a record of all responses from the DNS servers 108 until all responses have been received. If a response indicates that the domain-name database contains a DNS
record associated with the domain name, query engine 222 flags that response signifying that the domain name has indeed been registered in the specified domain for further inquiry. This response is referred to as an "unavailability response." The unavailability response provides the user with at least some indication (although not necessarily a conclusive one) that the domain name might not be available to be adopted in the domain in question.
Once all of the DNS servers 108 have responded with information about domain-name unavailability, query engine 222 performs a subsequent query for all registered domain names that support a Whois query (step 424). Using Whois, query software 226 can also learn additional information about a domain name. Query engine 222 invokes query software 226 to perform a Whois query in the domains that returned an unavailable response for a particular domain name. Domain file 232 contains a listing of domains supporting the Whois queries, since not all domains support Whois functionality.
Finally, in step 424, the results from the initial query and/or supplemental Whois query are presented to the user in a suitable display format. In either case, query engine 222 collects, sorts and formats the results for display to client computer 106.
The results may be displayed in an HTML format.
FIG 6a and 6b depict the results displayed to the user. Fig. 6a depicts an HTML display presented to the user using client computer 106 for search results 602. In this particular search, the user requested a domain name specialized search in all Asian and Pacific countries for the domain name "Mercedes." Items 604 indicate domains for which the domain name is currently unavailable, while items 606 indicate domains for which the domain name is available. If desired, a user may request to register a domain name as indicated by item 606 by selecting item 610. That is, item 610 links a user to an FfTML order form, as shown in Fig. 6c, for the specified domain. The order form dynamically creates an order request for a particular domain name in the specified domain. The user supplies information, such as credit card and contact information, and once all the information is entered, the user may submit the order form to the appropriate registering service by email or by the well known hypertext transport protocol in order to begin the registration process.
Also, Item 608 indicates that the domain ".com.au" supports the Whois functionality and contains further details on the administration for the domain name "Mercedes."
By selecting item 608, a user will view the supplemental Whois queries for all domains supporting Whois functionality, as shown in Fig. 6b.
Also if desired, the query server can develop and maintain a centralized data store of "taken" domain names indicating which domain names have been registered and in which domains) they are registered. In response to a user's query, the query server can then search the centralized data store to make a quick, first-pass determination whether the domain name of interest has been "taken."
Methods and systems consistent with the present invention search for registered domain names in a plurality of domains by transmitting a request to search a domain-name database to selected domains. One of the advantages to searching domains in this manner is that the query server can send search requests to many top-level Domain Name Servers (e.g., .uk, .fr, .de, and so on) so that the searches can be performed quickly and, from the user's perspective, essentially simultaneously. This searching capability is available to any Web enabled client browser, UNIX or many other operating systems. For example, a domain name search may be implemented by a command line instruction. Methods consistent with the present invention also work well with multi-processor machines. On a multi-processor machine, a search may show up on more than one processor thread. Finally, systems consistent with the present invention can work well with domain name search engines written in C++, Perl, C
or even Java programming languages.
The foregoing description of an implementation of the invention has been presented for purposes of illustration and description. It is not exhaustive and does not limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practicing of the invention. For example, the described implementation includes software but the present invention may be implemented as a combination of hardware and software or in hardware alone.
record contains a domain name and the associated numerical address. DNS records may also contain textual information regarding the domain name. For example, a DNS
record may indicate a contact person for a particular domain name. DNS servers 108 receive query requests from the query server 104 and search the domain name database for a DNS record associated with the domain name. Although only one client computer 106 is depicted, one skilled in the art will appreciate that data processing system 100 may contain many more client computers.
FIG 2. depicts a more detailed diagram of query server 104. Query server 104 contains a memory 220, a secondary storage device 230, a central processing unit ("CPU") 240, an input device 250, and a video display 260. Memory 220 includes domain name query engine 222 that interacts with client computer 106 and DNS servers 108. Query engine 222 includes query software 224 that submits search requests to various DNS servers 108 located throughout the network. One example of the query software may be a UNIX
utility tool called "nslookup" available on most UNIX platforms. Alternatively, query software 226 may be a script to interact with various Domain Name Servers. Query engine 222 also includes search engine 226 that uses a forking system to perform domain name queries in parallel.
The forking system initiates multiple sub-processes to perform a subset of the queries once the query process has begun. The forking system reduces the total time to complete a search since multiple sub-processes will perform the queries in parallel. Query engine 222 further includes HT'ML parser 228 that parses H'TML form parameters passed to and from the client browser when a search is submitted to the search engine 226. Search engine 226, query software 224 and HTML parser 228 are preferably written in the PERL
environment available for download from Internet sites, such as "http://www.perl.com."
Secondary storage device 230 includes a domain file 232 that includes a listing of the available domains used by the search engine to create the queries. Also included in domain file 232 is a domain extension suffix to append to the domain name to create a full domain name to be searched. For example, the domain extension suffix ".co.uk" when combined with the domain name "apple" will create the full domain name "apple.co.uk."
Domain file 232 may also contain the numerical address of a DNS server for each domain and whether the domain supports a Whois query. Moreover, domain file 232 may also optionally include other fields for specialized searches, such as Gross Domestic Product (GDP) or whether the domain is a member of European Union or a Western country. These specialized fields allow the user to crieate a specialized domain name search in various environments.
For example, a user may select to search for a domain name located in a top SO GDP country.
One skilled in the art will appreciate that other specialized fields may exist, including Asian countries or even high Internet usage countries.
Fig. 3 depicts in greater detail an exemplary DNS server 108. DNS server 108 contains a memory 320, a secondary storage device 330, a central processing unit ("CPU") 340, an input device 350, and a video display 360. Secondary storage device 330 includes DNS
server database 332 containing resource records that describe all the registered domain names within it's zone. A "zone" contains the domain names and data that a domain contains, except for domain names and data that are delegated to a sub-domain. For example, the domain "ca" (for Canada) may have the sub-domains "ab.ca" (Alberta), "on.ca"
(Ontario), and "qb.ca" (Quebec). Authority for the "ab.ca," "on.ca," and "qb.ca" domains may be delegated to the DNS servers in each of the provinces. The domain "ca"
contains all the data in "ca" plus all the data in "ab.ca," "on.ca," and "qb.ca." However, the zone "ca" contains only the data in "ca". In other words, the domain name "apple.ca" is listed in the "ca" DNS
server database, while the domain name "apple.qb.ca" is listed in the "qb.ca°' DNS database.
Memory 320 includes program 322 that receives search requests from query server 104 for searching and retrieving information about the domain name from DNS database 332. One example of program 322 may be Berkeley Internet Name Domain (BIND) implementation of DNS available for download from the Internet Software Consortium at "http://www.isc.org."
Although aspects of the present invention are described as being stored in memory, one skilled in the art will appreciate that these aspects may be stored on or read from other computer-readable media, such as secondary storage devices, like hard disks, floppy disks and CD-ROM; a carrier wave received from a network like the Internet; or other forms of ROM or RAM. Additionally, although specific components and programs of query server 104 and DNS server 108 have been described, one skilled in the art will appreciate that a query server or a DNS server suitable for use with methods and systems consistent with the present invention may contain additional or different components.
Domain Name Searching Process Further details on operation of the search process will now be explained with reference to the flow chart of Fig. 4. The domain name search process is initiated, for example, by a request from client computer 106 to perform a search for a domain name (step 402). For example, client computer 106 may send an HTML request to query engine 104 using the well known Hypertext Transfer Protocol. Once the request is received, query engine interrogates domain file 232 (step 404) and transmits all possible domains to search and the accompanying specialized fields in an HTML format to display on client computer 106 (step 406). That is, query engine 222 transmits a possible domain to search ".uk"
with an identification that the domain is part of the European Union and also from a top 50 GDP
country.
Once displayed, a user using client computer 106 enters a domain name to search, for example "apple," and a type of search to be performed, for example "top 50 GDP
countries"
(step 408). A user may request a search for registered domain names in all domains, as shown in Fig. Sa. Alternatively, the user may request a specialized search.
That is, a search for a registered domain name in a set of domains based on the accompanying specialized fields. For example, a user may request to search in only the top 50 countries ranked by annual GDP, as depicted in Fig. Sb. One skilled in the art will appreciate that other combinations of domain selections exists, for example Western countries, Asian countries or a customized search, in that the user at client computer 106 may select a subset of domains to search from the total number of domains.
Upon the user at client computer 106 entering a domain name to search, client computer 106 sends the user input to query server 104 (step 410). Once received at query server 104, HTML parser 228 parses a listing of domains and a domain name to search submitted by the client computer 106 (step 412). Query engine 222 then invokes search engine 226 to spawn a number of search sub-processes (step 414). In this step, search engine 226 calculates the number of search sub-processes to spawn based on the number of domains to query -g submitted by client computer 106 so that each search sub-process contains at most 11 domains to search. Essentially, search engine 226 forks the queries into multiple sub-processes to perform the domain name searches in parallel for optimized performance. Each spawned search sub-process is given a subset of domains to query, thus query server 104 may perform multiple queries at once. For example, if client browser 106 selects 50 domains to query, search engine 226 may spawn 5 search sub-processes, so that each spawned search sub-process queries 10 DNS servers. Further, depending on the load of query server 104, search engine 226 may change the number of search sub-processes to spawn.
Once the search processes are spawned, a separate section of query engine 222, query software 224, transmits, to a DNS server for the domain in question (e.g., a DNS server 108 for .qb.ca or for .com), a request for a search of a domain-name database for a DNS record associated with the domain name (step 416). The transmission of the search request could be direct, but more likely will be relayed through one or more intermediary machines. For example, a search request generated by a query server in Houston could be transmitted to London, then to Moscow, and then to Zimbabwe, where the target DNS server 108 might be located.
In response to the search request, the DNS server 108 searches its domain-name database for a DNS record associated with the specified domain name (step 418). The DNS
server 108 generates a response that indicates whether a DNS record was found for that domain name.
Query server 104 ultimately receives the response from DNS server 108 (step 420) and keeps a record of all responses from the DNS servers 108 until all responses have been received. If a response indicates that the domain-name database contains a DNS
record associated with the domain name, query engine 222 flags that response signifying that the domain name has indeed been registered in the specified domain for further inquiry. This response is referred to as an "unavailability response." The unavailability response provides the user with at least some indication (although not necessarily a conclusive one) that the domain name might not be available to be adopted in the domain in question.
Once all of the DNS servers 108 have responded with information about domain-name unavailability, query engine 222 performs a subsequent query for all registered domain names that support a Whois query (step 424). Using Whois, query software 226 can also learn additional information about a domain name. Query engine 222 invokes query software 226 to perform a Whois query in the domains that returned an unavailable response for a particular domain name. Domain file 232 contains a listing of domains supporting the Whois queries, since not all domains support Whois functionality.
Finally, in step 424, the results from the initial query and/or supplemental Whois query are presented to the user in a suitable display format. In either case, query engine 222 collects, sorts and formats the results for display to client computer 106.
The results may be displayed in an HTML format.
FIG 6a and 6b depict the results displayed to the user. Fig. 6a depicts an HTML display presented to the user using client computer 106 for search results 602. In this particular search, the user requested a domain name specialized search in all Asian and Pacific countries for the domain name "Mercedes." Items 604 indicate domains for which the domain name is currently unavailable, while items 606 indicate domains for which the domain name is available. If desired, a user may request to register a domain name as indicated by item 606 by selecting item 610. That is, item 610 links a user to an FfTML order form, as shown in Fig. 6c, for the specified domain. The order form dynamically creates an order request for a particular domain name in the specified domain. The user supplies information, such as credit card and contact information, and once all the information is entered, the user may submit the order form to the appropriate registering service by email or by the well known hypertext transport protocol in order to begin the registration process.
Also, Item 608 indicates that the domain ".com.au" supports the Whois functionality and contains further details on the administration for the domain name "Mercedes."
By selecting item 608, a user will view the supplemental Whois queries for all domains supporting Whois functionality, as shown in Fig. 6b.
Also if desired, the query server can develop and maintain a centralized data store of "taken" domain names indicating which domain names have been registered and in which domains) they are registered. In response to a user's query, the query server can then search the centralized data store to make a quick, first-pass determination whether the domain name of interest has been "taken."
Methods and systems consistent with the present invention search for registered domain names in a plurality of domains by transmitting a request to search a domain-name database to selected domains. One of the advantages to searching domains in this manner is that the query server can send search requests to many top-level Domain Name Servers (e.g., .uk, .fr, .de, and so on) so that the searches can be performed quickly and, from the user's perspective, essentially simultaneously. This searching capability is available to any Web enabled client browser, UNIX or many other operating systems. For example, a domain name search may be implemented by a command line instruction. Methods consistent with the present invention also work well with multi-processor machines. On a multi-processor machine, a search may show up on more than one processor thread. Finally, systems consistent with the present invention can work well with domain name search engines written in C++, Perl, C
or even Java programming languages.
The foregoing description of an implementation of the invention has been presented for purposes of illustration and description. It is not exhaustive and does not limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practicing of the invention. For example, the described implementation includes software but the present invention may be implemented as a combination of hardware and software or in hardware alone.
Claims (15)
1. A method in a data processing system with DNS servers, each responsible for maintaining registration records of domain names for an associated domain, comprising:
receiving user input containing a domain name and specified ones of the domains;
transmitting a request for a search of the domain name to the DNS servers associated with the specified domains;
receiving search results from the DNS servers associated with the specified domains indicating, for each of the specified domains, whether a domain name record exists for the domain name in the specified domain; and displaying the search results.
receiving user input containing a domain name and specified ones of the domains;
transmitting a request for a search of the domain name to the DNS servers associated with the specified domains;
receiving search results from the DNS servers associated with the specified domains indicating, for each of the specified domains, whether a domain name record exists for the domain name in the specified domain; and displaying the search results.
2. The method of claim 1, wherein the results are sorted and formatted in a hypertext markup language.
3. The method of claim 1, wherein the transmitting step further includes:
determining a number of search processes to spawn based on a number of specified domains; and spawning the number of the search processes, wherein each search process queries at least one of the DNS servers.
determining a number of search processes to spawn based on a number of specified domains; and spawning the number of the search processes, wherein each search process queries at least one of the DNS servers.
4. The method of claim 1, wherein the receiving user input step includes:
reading a domain file to determine available domains; and displaying the available domains to a user to enable the user to indicate the specified domains.
reading a domain file to determine available domains; and displaying the available domains to a user to enable the user to indicate the specified domains.
5. The method of claim 1, wherein the domains have an associated country with a gross domestic product, and wherein the receiving user input step includes:
displaying a predetermined number of domains based on the gross domestic product of the associated countries; and indicating at least one of the predetermined number of domains as the specified domains.
displaying a predetermined number of domains based on the gross domestic product of the associated countries; and indicating at least one of the predetermined number of domains as the specified domains.
6. The method of claim 1, further comprising:
determining whether the domain name record exists for the domain name for each specified domain; and performing a query to obtain registration information for the domain name when the domain name record exists.
determining whether the domain name record exists for the domain name for each specified domain; and performing a query to obtain registration information for the domain name when the domain name record exists.
7. The method of claim 1, further comprising:
displaying an order form for registering the domain name in a specified domain.
displaying an order form for registering the domain name in a specified domain.
8. A method in a data processing system with DNS servers, each responsible for maintaining registration records of domain names for an associated domain, comprising:
receiving user input containing a domain name and specified ones of the domains;
transmitting a first request to a first of the DNS servers to determine whether a domain name record exists in the domain associated with the first DNS server;
transmitting a second request to a second of the DNS servers to determine whether a domain name record exists in the domain associated with the second DNS server while the first request is pending;
receiving search results from the first request and the second request indicating whether the domain name record exists in the domain associated with the first DNS server and indicating whether the domain name record exists in the domain associated with the second DNS server; and displaying the search results to a user.
receiving user input containing a domain name and specified ones of the domains;
transmitting a first request to a first of the DNS servers to determine whether a domain name record exists in the domain associated with the first DNS server;
transmitting a second request to a second of the DNS servers to determine whether a domain name record exists in the domain associated with the second DNS server while the first request is pending;
receiving search results from the first request and the second request indicating whether the domain name record exists in the domain associated with the first DNS server and indicating whether the domain name record exists in the domain associated with the second DNS server; and displaying the search results to a user.
9. A data processing system comprising:
a plurality of DNS servers, each DNS server configured to maintain registration information of domain names for an associated domain; and a query server containing:
a memory with a program configured to receive user input containing a domain name and specified ones of the domains, configured to transmit a request for a search of the domain name to the DNS servers associated with the specified domains, and configured to receive search results from the DNS servers associated with the specified domains indicating, for each of the specified domains, whether a domain name record exists in the specified domain;
a display configured to display the search results; and a processor configured to run the program.
a plurality of DNS servers, each DNS server configured to maintain registration information of domain names for an associated domain; and a query server containing:
a memory with a program configured to receive user input containing a domain name and specified ones of the domains, configured to transmit a request for a search of the domain name to the DNS servers associated with the specified domains, and configured to receive search results from the DNS servers associated with the specified domains indicating, for each of the specified domains, whether a domain name record exists in the specified domain;
a display configured to display the search results; and a processor configured to run the program.
10. The data processing system of claim 9, wherein the program sorts and formats the search results in a hypertext markup language.
11. The data processing system of claim 9, wherein program contains a spawn component configured to determine a number of search processes to spawn based on a number of specified domains, and configured to spawn the number of the search processes, wherein each search process queries at least one of the DNS
servers.
servers.
12. The data processing system of claim 9, wherein the domains have an associated country with a gross domestic product, and wherein the program contains a gross domestic product component configured to display a predetermined number of domains based on the gross domestic product of the associated countries, and configured to receive an indication of at least one of the predetermined number of domains as the specified domains.
13. The system of claim 9, wherein the program contains a registration component configured to:
examine the search results to determine whether a domain name record exists for each of the specified domains, and configured to perform a query on each DNS
server to obtain registration information for the domain name when the domain name record exists.
examine the search results to determine whether a domain name record exists for each of the specified domains, and configured to perform a query on each DNS
server to obtain registration information for the domain name when the domain name record exists.
14. The system of claim 9, wherein the program contains an order component configured to:
create an order form for registering the domain name in a specified domain.
create an order form for registering the domain name in a specified domain.
15. A computer-readable medium containing instructions, for controlling a data processing system to perform a method, the data processing system having DNS
servers, each responsible for maintaining registration information of domain names for an associated domain, the method comprising the steps of:
receiving user input containing a domain name and specified ones of the domains;
transmitting a request for a search of the domain name to the DNS servers associated with the specified domains;
receiving search results from the DNS servers associated with the specified domains indicating, for each of the specified domains, whether a domain name record exists in the specified domain; and displaying the search results.
servers, each responsible for maintaining registration information of domain names for an associated domain, the method comprising the steps of:
receiving user input containing a domain name and specified ones of the domains;
transmitting a request for a search of the domain name to the DNS servers associated with the specified domains;
receiving search results from the DNS servers associated with the specified domains indicating, for each of the specified domains, whether a domain name record exists in the specified domain; and displaying the search results.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US5578797P | 1997-08-15 | 1997-08-15 | |
US60/055,787 | 1997-08-15 | ||
PCT/US1998/016863 WO1999009726A1 (en) | 1997-08-15 | 1998-08-14 | Method of determining unavailability of internet domain names |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2300421A1 true CA2300421A1 (en) | 1999-02-25 |
Family
ID=22000158
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002300421A Abandoned CA2300421A1 (en) | 1997-08-15 | 1998-08-14 | Method of determining unavailability of internet domain names |
Country Status (6)
Country | Link |
---|---|
US (1) | US6560634B1 (en) |
EP (1) | EP1004192A1 (en) |
JP (1) | JP2001516094A (en) |
AU (1) | AU8829298A (en) |
CA (1) | CA2300421A1 (en) |
WO (1) | WO1999009726A1 (en) |
Families Citing this family (175)
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 |
US6901436B1 (en) * | 1999-03-22 | 2005-05-31 | Eric Schneider | Method, product, and apparatus for determining the availability of similar identifiers and registering these identifiers across multiple naming systems |
US6895430B1 (en) * | 1999-10-01 | 2005-05-17 | Eric Schneider | Method and apparatus for integrating resolution services, registration services, and search services |
US6829242B2 (en) * | 1998-06-30 | 2004-12-07 | Cisco Technology, Inc. | Method and apparatus for associating PVC identifiers with domain names of home gateways |
US10511573B2 (en) | 1998-10-30 | 2019-12-17 | Virnetx, Inc. | Agile network protocol for secure communications using secure domain names |
US7418504B2 (en) | 1998-10-30 | 2008-08-26 | Virnetx, Inc. | Agile network protocol for secure communications using secure domain names |
EP1125419B1 (en) | 1998-10-30 | 2009-08-26 | VirnetX Inc. | An agile network protocol for secure communications with assured system availability |
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 |
US6873992B1 (en) * | 1999-09-07 | 2005-03-29 | Robolaw Corporation | Method and system for automated document generation |
EP1157524B1 (en) * | 1999-03-03 | 2007-12-19 | Ultradns, Inc. | Scalable and efficient domain name resolution |
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 |
US7188138B1 (en) | 1999-03-22 | 2007-03-06 | Eric Schneider | Method, product, and apparatus for resource identifier registration and aftermarket services |
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 |
US9141717B2 (en) | 1999-03-22 | 2015-09-22 | Esdr Network Solutions Llc | Methods, systems, products, and devices for processing DNS friendly identifiers |
US8667051B2 (en) | 1999-03-22 | 2014-03-04 | Esdr Network Solutions Llc | Real-time communication processing method, product, and apparatus |
US6338082B1 (en) * | 1999-03-22 | 2002-01-08 | Eric Schneider | Method, product, and apparatus for requesting a network resource |
WO2000065507A2 (en) * | 1999-04-22 | 2000-11-02 | Network Solutions, Inc. | Business rule engine |
US6925642B1 (en) * | 1999-04-29 | 2005-08-02 | Hewlett-Packard Development Company, L.P. | Distributed computer network which spawns inter-node parallel processes based on resource availability |
US20040162916A1 (en) * | 1999-06-22 | 2004-08-19 | Ryan William Kenneth | Multiple use of identical names to identify different IP numerical addresses |
US8543732B2 (en) * | 1999-06-22 | 2013-09-24 | William Kenneth Ryan | Method and apparatus for multiplexing internet domain names |
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 |
USRE44207E1 (en) * | 1999-09-01 | 2013-05-07 | Esdr Network Solutions Llc | Network resource access method, product, and apparatus |
US6973505B1 (en) * | 1999-09-01 | 2005-12-06 | Eric Schneider | Network resource access method, product, and apparatus |
US8364688B1 (en) | 1999-09-07 | 2013-01-29 | Thomas C Douglass | System and method for providing and updating on-line forms and registrations |
US9311399B2 (en) | 1999-09-07 | 2016-04-12 | C. Douglass Thomas | System and method for providing an updating on-line forms and registrations |
US7747592B2 (en) * | 1999-09-07 | 2010-06-29 | Thomas C Douglass | Method and system for monitoring domain name registrations |
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 |
JP3725376B2 (en) * | 1999-09-29 | 2005-12-07 | 株式会社東芝 | DNS inquiry apparatus, DNS inquiry method, and recording medium |
US6792458B1 (en) * | 1999-10-04 | 2004-09-14 | Urchin Software Corporation | System and method for monitoring and analyzing internet traffic |
US7610289B2 (en) | 2000-10-04 | 2009-10-27 | Google Inc. | System and method for monitoring and analyzing internet traffic |
US6980990B2 (en) * | 1999-12-01 | 2005-12-27 | Barry Fellman | Internet domain name registration system |
US6625594B1 (en) * | 2000-01-18 | 2003-09-23 | With1Click, Inc. | System and method for searching a global communication system using a sub-root domain name agent |
US20010047396A1 (en) * | 2000-01-31 | 2001-11-29 | Jacob Nellemann | Method for identifying information in a network |
US7099956B2 (en) * | 2000-01-31 | 2006-08-29 | Ideaflood, Inc. | Method and apparatus for conducting domain name service |
US20010033301A1 (en) * | 2000-02-03 | 2001-10-25 | Tony Hong | Method and system for efficient and uniform formatting of selectable elements on a graphical user interface |
DE60116807T2 (en) * | 2000-02-29 | 2006-07-20 | Matsushita Electric Industrial Co., Ltd., Kadoma | Portable phone with URL access function |
KR100635099B1 (en) | 2000-03-06 | 2006-10-18 | 김홍년 | A system for substitution of domain name registration and a method thereof |
KR20000030601A (en) * | 2000-03-08 | 2000-06-05 | 김세기 | Method of search for domain in internet |
KR20000049762A (en) * | 2000-04-28 | 2000-08-05 | 주진용 | E-mail address allocation apparatus |
US20020019800A1 (en) * | 2000-05-16 | 2002-02-14 | Ideaflood, Inc. | Method and apparatus for transacting divisible property |
US7000028B1 (en) * | 2000-06-02 | 2006-02-14 | Verisign, Inc. | Automated domain name registration |
US7467140B2 (en) * | 2000-06-30 | 2008-12-16 | Verisign, Inc. | System, method, and article of manufacture for maintaining and accessing a whois database |
US7089325B1 (en) * | 2000-07-05 | 2006-08-08 | Register.Com, Inc. | Method and apparatus for URL forwarding |
KR100417812B1 (en) * | 2000-07-27 | 2004-02-05 | 주식회사 스피드넷 | System and method for creating/managing domain and media for storing program source thereof |
US6839738B2 (en) * | 2000-12-28 | 2005-01-04 | Pitney Bowes Inc. | System and method for cleansing addresses for electronic messages |
US7020602B1 (en) * | 2000-08-21 | 2006-03-28 | Kim Ki S | Native language domain name registration and usage |
WO2002029593A1 (en) * | 2000-10-02 | 2002-04-11 | Enic Corporation | Determining alternative textual identifiers, such as for registered domain names |
US7324965B2 (en) | 2000-10-27 | 2008-01-29 | Microsoft Corporation | Wish list |
WO2002037338A1 (en) | 2000-11-01 | 2002-05-10 | Snapnames.Com, Inc. | Registry-integrated internet domain name acquisition system |
US7320019B2 (en) * | 2000-11-30 | 2008-01-15 | At&T Delaware Intellectual Property, Inc. | Method and apparatus for automatically checking e-mail addresses in outgoing e-mail communications |
US20020145992A1 (en) * | 2001-03-20 | 2002-10-10 | Holt Gregory S. | URL acquisition and management |
US20030229632A1 (en) * | 2001-05-15 | 2003-12-11 | Mark Harris | Communications system and method |
US20020174059A1 (en) * | 2001-05-21 | 2002-11-21 | Yunbao Guo | System for e-market management and global online cross-industry business integration |
US7197550B2 (en) * | 2001-08-23 | 2007-03-27 | The Directv Group, Inc. | Automated configuration of a virtual private network |
US7769838B2 (en) * | 2001-08-23 | 2010-08-03 | The Directv Group, Inc. | Single-modem multi-user virtual private network |
US7099957B2 (en) * | 2001-08-23 | 2006-08-29 | The Directtv Group, Inc. | Domain name system resolution |
US7373644B2 (en) | 2001-10-02 | 2008-05-13 | Level 3 Communications, Llc | Automated server replication |
US20030079027A1 (en) | 2001-10-18 | 2003-04-24 | Michael Slocombe | Content request routing and load balancing for content distribution networks |
US7565402B2 (en) * | 2002-01-05 | 2009-07-21 | Eric Schneider | Sitemap access method, product, and apparatus |
US6952691B2 (en) * | 2002-02-01 | 2005-10-04 | International Business Machines Corporation | Method and system for searching a multi-lingual database |
US20030208594A1 (en) * | 2002-05-06 | 2003-11-06 | Urchin Software Corporation. | System and method for tracking unique visitors to a website |
KR100477653B1 (en) * | 2002-06-22 | 2005-03-23 | 삼성전자주식회사 | Apparatus and method for searching DNS server on outer net |
US7130923B2 (en) * | 2002-07-01 | 2006-10-31 | Avaya Technology Corp. | Method and apparatus for guessing correct URLs using tree matching |
US7676452B2 (en) * | 2002-07-23 | 2010-03-09 | International Business Machines Corporation | Method and apparatus for search optimization based on generation of context focused queries |
KR100463208B1 (en) * | 2002-08-05 | 2004-12-23 | (주)하우앤와이 | Internal Natural Domain Service System with Local Name Servers for Flexible Top-Level Domains |
CA2467644C (en) | 2002-08-13 | 2008-12-09 | 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 |
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 |
JP2004348241A (en) * | 2003-05-20 | 2004-12-09 | Hitachi Ltd | Information providing method, server, and program |
FI20030797A0 (en) * | 2003-05-27 | 2003-05-27 | Nokia Corp | Improving Database Performance on a Name Server System |
US7854009B2 (en) * | 2003-06-12 | 2010-12-14 | International Business Machines Corporation | Method of securing access to IP LANs |
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 |
US8271488B2 (en) * | 2003-09-16 | 2012-09-18 | Go Daddy Operating Company, LLC | Method for improving a web site's ranking with search engines |
US20050065774A1 (en) * | 2003-09-20 | 2005-03-24 | International Business Machines Corporation | Method of self enhancement of search results through analysis of system logs |
US8014997B2 (en) * | 2003-09-20 | 2011-09-06 | International Business Machines Corporation | Method of search content enhancement |
US7376752B1 (en) | 2003-10-28 | 2008-05-20 | David Chudnovsky | Method to resolve an incorrectly entered uniform resource locator (URL) |
US20050102348A1 (en) * | 2003-11-07 | 2005-05-12 | Parsons Robert R. | Integrated web based email system and document storage manager |
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 |
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 |
GB2429556A (en) * | 2004-05-05 | 2007-02-28 | John Wong | System and methods for domain name acquisition and management |
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 |
US8285816B2 (en) * | 2004-06-25 | 2012-10-09 | Go Daddy Operating Company, LLC | Methods of issuing 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 |
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 |
US20060039352A1 (en) * | 2004-08-19 | 2006-02-23 | International Business Machines Corporation | System and method for designating a priority access order of domain name service servers |
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 |
US9002783B2 (en) * | 2004-09-17 | 2015-04-07 | Go Daddy Operating Company, LLC | Web page customization based on expertise level of a user |
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 |
US20080028100A1 (en) * | 2004-10-29 | 2008-01-31 | The Go Daddy Group, Inc. | Tracking domain name related reputation |
US20060095404A1 (en) * | 2004-10-29 | 2006-05-04 | The Go Daddy Group, Inc | Presenting search engine results based on domain name related reputation |
US20060200487A1 (en) * | 2004-10-29 | 2006-09-07 | 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 |
US8117339B2 (en) * | 2004-10-29 | 2012-02-14 | Go Daddy Operating Company, LLC | Tracking domain name related reputation |
US7797413B2 (en) * | 2004-10-29 | 2010-09-14 | The Go Daddy Group, Inc. | Digital identity registration |
US9015263B2 (en) | 2004-10-29 | 2015-04-21 | Go Daddy Operating Company, LLC | Domain name searching with reputation rating |
US8904040B2 (en) * | 2004-10-29 | 2014-12-02 | Go Daddy Operating Company, LLC | Digital identity validation |
US20080028443A1 (en) * | 2004-10-29 | 2008-01-31 | 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 |
US20060095459A1 (en) * | 2004-10-29 | 2006-05-04 | Warren Adelman | Publishing domain name related reputation in whois records |
US7464136B2 (en) * | 2004-11-05 | 2008-12-09 | Microsoft Corporation | Integrated messaging domain name setup |
US20050125451A1 (en) * | 2005-02-10 | 2005-06-09 | The Go Daddy Group, Inc. | Search engine and domain name search integration |
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 |
US8200696B2 (en) * | 2005-05-26 | 2012-06-12 | International Business Machines Corporation | Presenting multiple possible selectable domain names from a URL entry |
EP1956818A4 (en) * | 2005-11-04 | 2011-10-12 | Sharp Kk | PoC SERVER AUTOMATIC-SEARCH METHOD, QUALITY ADJUSTING METHOD, AND COMMUNICATION SYSTEM USING THESE METHODS |
US20080126950A1 (en) * | 2006-11-28 | 2008-05-29 | Patrick Leo Glenski | Smart Reply Function on Web Pages |
US20090248623A1 (en) * | 2007-05-09 | 2009-10-01 | The Go Daddy Group, Inc. | Accessing digital identity related reputation data |
EP2006781A1 (en) * | 2007-06-21 | 2008-12-24 | Telnic Limited | Method, apparatus and system for indexing and searching DNS zone records |
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 |
US7962438B2 (en) * | 2008-03-26 | 2011-06-14 | The Go Daddy Group, Inc. | Suggesting concept-based domain names |
US8069187B2 (en) * | 2008-03-26 | 2011-11-29 | The Go Daddy Group, Inc. | Suggesting concept-based top-level domain names |
US20090248736A1 (en) * | 2008-03-26 | 2009-10-01 | The Go Daddy Group, Inc. | Displaying concept-based targeted advertising |
US7904445B2 (en) * | 2008-03-26 | 2011-03-08 | The Go Daddy Group, Inc. | Displaying concept-based search results |
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 |
US7917616B2 (en) * | 2008-08-08 | 2011-03-29 | Microsoft Corporation | Secure resource name resolution |
US8429715B2 (en) | 2008-08-08 | 2013-04-23 | Microsoft Corporation | Secure resource name resolution using a cache |
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 |
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 |
DE102009010685B3 (en) * | 2009-02-27 | 2010-09-23 | Vodafone Holding Gmbh | Checking the functionality of communication services for mobile terminals operable in mobile networks when roaming in at least two mobile networks |
FR2950717A1 (en) * | 2009-09-28 | 2011-04-01 | Indom France | Domain name geographical occupancy measuring method for Internet protocol type telecommunication network, involves modifying graphical data based on response to be measured, and transmitting graphical data to user terminal |
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 |
US20110208767A1 (en) * | 2010-02-19 | 2011-08-25 | The Go Daddy Group, Inc. | Semantic domain name spinning |
US9058393B1 (en) | 2010-02-19 | 2015-06-16 | Go Daddy Operating Company, LLC | Tools for appraising a domain name using keyword monetary value data |
US8909558B1 (en) | 2010-02-19 | 2014-12-09 | Go Daddy Operating Company, LLC | 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 |
US20110208731A1 (en) * | 2010-02-19 | 2011-08-25 | The Go Daddy Group, Inc. | Automated semantic domain spinning tools |
US8706728B2 (en) * | 2010-02-19 | 2014-04-22 | Go Daddy Operating Company, LLC | Calculating reliability scores from word splitting |
US8515969B2 (en) * | 2010-02-19 | 2013-08-20 | Go Daddy Operating Company, LLC | Splitting a character string into keyword strings |
US8447702B2 (en) * | 2010-02-19 | 2013-05-21 | Go Daddy Operating Company, LLC | Domain appraisal algorithm |
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 |
US9049229B2 (en) | 2010-10-28 | 2015-06-02 | Verisign, Inc. | Evaluation of DNS pre-registration data to predict future DNS traffic |
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 |
US8990356B2 (en) | 2011-10-03 | 2015-03-24 | Verisign, Inc. | Adaptive name resolution |
US10270755B2 (en) | 2011-10-03 | 2019-04-23 | Verisign, Inc. | Authenticated name resolution |
US9391855B2 (en) | 2012-05-09 | 2016-07-12 | Everbridge, Inc. | Systems and methods for simulating a notification system |
US9740708B2 (en) * | 2012-05-01 | 2017-08-22 | Everbridge, Inc. | Systems and methods for distance and performance based load balancing |
US9026522B2 (en) | 2012-10-09 | 2015-05-05 | Verisign, Inc. | Searchable web whois |
US9363288B2 (en) | 2012-10-25 | 2016-06-07 | Verisign, Inc. | Privacy preserving registry browsing |
US10565394B2 (en) | 2012-10-25 | 2020-02-18 | Verisign, Inc. | Privacy—preserving data querying with authenticated denial of existence |
US9202079B2 (en) | 2012-10-25 | 2015-12-01 | Verisign, Inc. | Privacy preserving data querying |
US8862566B2 (en) * | 2012-10-26 | 2014-10-14 | Equifax, Inc. | Systems and methods for intelligent parallel searching |
US9904944B2 (en) | 2013-08-16 | 2018-02-27 | Go Daddy Operating Company, Llc. | System and method for domain name query metrics |
US10140644B1 (en) | 2013-10-10 | 2018-11-27 | Go Daddy Operating Company, LLC | System and method for grouping candidate domain names for display |
US9684918B2 (en) | 2013-10-10 | 2017-06-20 | Go Daddy Operating Company, LLC | System and method for candidate domain name generation |
US9613374B2 (en) | 2013-10-10 | 2017-04-04 | Go Daddy Operating Company, LLC | Presentation of candidate domain name bundles 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 |
US9866526B2 (en) | 2013-10-10 | 2018-01-09 | Go Daddy Operating Company, LLC | Presentation of candidate domain name stacks in a user interface |
US9769117B2 (en) | 2014-02-28 | 2017-09-19 | Verisign, Inc. | Domain name variant generation |
US9900281B2 (en) | 2014-04-14 | 2018-02-20 | Verisign, Inc. | Computer-implemented method, apparatus, and computer-readable medium for processing named entity queries using a cached functionality in a domain name system |
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 |
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 |
US10979384B2 (en) * | 2016-03-25 | 2021-04-13 | Verisign, Inc. | Systems and methods for preserving privacy of a registrant in a Domain Name System (“DNS”) |
US10999240B1 (en) | 2016-08-31 | 2021-05-04 | Verisign, Inc. | Client controlled domain name service (DNS) resolution |
US11032127B2 (en) | 2017-06-26 | 2021-06-08 | Verisign, Inc. | Resilient domain name service (DNS) resolution when an authoritative name server is unavailable |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5434974A (en) * | 1992-03-30 | 1995-07-18 | International Business Machines Corporation | Name resolution for a multisystem network |
WO1996038795A1 (en) * | 1995-05-30 | 1996-12-05 | Corporation For National Research Initiatives | System for distributed task execution |
US5764906A (en) * | 1995-11-07 | 1998-06-09 | Netword Llc | Universal electronic resource denotation, request and delivery system |
US5983351A (en) * | 1996-10-16 | 1999-11-09 | Intellectual Protocols, L.L.C. | Web site copyright registration system and method |
US6023698A (en) * | 1996-12-05 | 2000-02-08 | International Business Machines Corporation | System and method for transparently registering and updating information over the internet |
US5895471A (en) * | 1997-07-11 | 1999-04-20 | Unwired Planet, Inc. | Providing a directory of frequently used hyperlinks on a remote server |
US6205482B1 (en) * | 1998-02-19 | 2001-03-20 | Ameritech Corporation | System and method for executing a request from a client application |
-
1998
- 1998-08-13 US US09/133,836 patent/US6560634B1/en not_active Expired - Lifetime
- 1998-08-14 EP EP98939945A patent/EP1004192A1/en not_active Withdrawn
- 1998-08-14 JP JP2000510265A patent/JP2001516094A/en active Pending
- 1998-08-14 WO PCT/US1998/016863 patent/WO1999009726A1/en not_active Application Discontinuation
- 1998-08-14 CA CA002300421A patent/CA2300421A1/en not_active Abandoned
- 1998-08-14 AU AU88292/98A patent/AU8829298A/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
EP1004192A1 (en) | 2000-05-31 |
US6560634B1 (en) | 2003-05-06 |
WO1999009726A1 (en) | 1999-02-25 |
AU8829298A (en) | 1999-03-08 |
JP2001516094A (en) | 2001-09-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6560634B1 (en) | Method of determining unavailability of an internet domain name | |
US7194552B1 (en) | Method, product, and apparatus for requesting a network resource | |
US8458161B2 (en) | Method, product, and apparatus for enhancing resolution services, registration services, and search services | |
US9659070B2 (en) | Methods, systems, products, and devices for processing DNS friendly identifiers | |
US7689671B2 (en) | System and method for multiple IP addresses during domain name resolution | |
US7136932B1 (en) | Fictitious domain name method, product, and apparatus | |
US7694019B2 (en) | System and method for accessing multiple addresses per domain name using networked repository | |
US7188138B1 (en) | Method, product, and apparatus for resource identifier registration and aftermarket services | |
US20060218303A1 (en) | Creation of a database storing domain names and business operational areas | |
US7565402B2 (en) | Sitemap access method, product, and apparatus | |
US7337910B2 (en) | Methods and devices for responding to request for unregistered domain name to indicate a predefined type of service | |
US6195691B1 (en) | Method and apparatus for creating and using dynamic universal resource locators | |
US8495211B2 (en) | Network service system and mechanism for searching service registries | |
US6760746B1 (en) | Method, product, and apparatus for processing a data request | |
US7117227B2 (en) | Methods and apparatus for using the internet domain name system to disseminate product information | |
US20080235383A1 (en) | Methods, Systems, Products, And Devices For Generating And Processing DNS Friendly Identifiers | |
US20050125451A1 (en) | Search engine and domain name search integration | |
US20060218151A1 (en) | Use of a database storing domain names and business operational areas | |
WO2000074335A2 (en) | Method and apparatus for redirecting users from virtual locations on the world wide web to other associated web locations | |
US20020133591A1 (en) | Method and apparatus for mapping of attributes to networked resources | |
KR20010035966A (en) | Method of Application Services using Supplementary Information for Internet Addresses | |
WO2018196962A1 (en) | Method for providing candidate domain names | |
GB2543497A (en) | Method for providing candidate domain names | |
WO2005022410A1 (en) | Search engine | |
WO2001069456A1 (en) | Method and apparatus for mapping of attributes to networked resources |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FZDE | Discontinued |