JP2019506692A - Method, apparatus and computer program for processing data and zone file of hierarchical domain name system - Google Patents

Abstract

Data is processed in a data communication network (800) that includes a hierarchical domain name system. The authoritative name server (806) for the first domain name processes the received domain name query for the first domain name by obtaining one or more resource records associated with the first domain name . The one or more resource records include contact information associated with the entity associated with the second domain name. The authoritative name server (806) sends a response to the domain name query. The response contains one or more resource records. The first domain name includes a second domain name and at least one label following the second domain name.

Description

  The present invention relates to a method, an apparatus, and a computer program for processing data, and a zone file of hierarchical domain name system.

  There are many ways to find contact details for entities that do not yet have that contact details.

  In some known situations, http: // www. example. A person seeking contact details for a company that has a website at com.com may use a web browser to access the website and then browse the website for such contact details. For example, one looks for a phone number to dial, a zip code to visit a store, a social media profile to connect through social media, or various other ways to establish contact with a business May be

  In other known situations, a person seeking corporate contact details may attempt to use a search engine to identify the corporate contact details. For example, a user may access a search engine of a web browser to retrieve such contact details. For example, the user may enter the specific type of contact details needed, such as "example business name phone number", in addition to the name of the business.

  While these known techniques may allow a person to specify contact details, the known techniques consume a large amount of data or require significant user interaction and / or contact details. This can cause undesirable delays in removal.

According to a first aspect of the invention, there is provided a method of processing data in a data communication network comprising a hierarchical domain name system. The method is: at the authoritative name server for the first domain name
Receiving a Domain Name System Query for the first domain name via the data communication network;
Processing the Domain Name System query for the received first domain name, the processing comprising obtaining one or more resource records associated with the first domain name The one or more resource records include contact information associated with an entity associated with a different second domain name;
Transmitting a response to the Domain Name System query for the first domain name via the data communication network, wherein the response is associated with the entity associated with a different second domain name Containing the one or more resource records that contain the contact information
Including
The first domain name includes the second domain name,
The first domain name includes at least one label following the second domain name.

According to a second aspect of the present invention, there is provided a method of processing data in a data communication network comprising a hierarchical domain name system. The way is
Sending a Domain Name System Query for a first domain name via the data communication network;
Receiving a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with an entity associated with a different second domain name With contact information
Processing the response to a Domain Name System query for the first domain name, wherein the processing is associated with the entity associated with the second domain name in one or more resource records. Including identifying the contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label following the second domain name.

According to a third aspect of the present invention, there is provided an apparatus configured to perform a method of processing data in a data communication network comprising a hierarchical domain name system. The method is: at the authoritative name server for the first domain name
Receiving a Domain Name System Query for the first domain name via the data communication network;
Processing a Domain Name System query for the received first domain name, the processing including obtaining one or more resource records associated with the first domain name, The one or more resource records include contact information associated with an entity associated with a different second domain name;
Transmitting a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with said entity associated with said second domain name Including the one or more resource records including the contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label following the second domain name.

According to a fourth aspect of the invention, there is provided an apparatus configured to perform a method of processing data in a data communication network comprising a hierarchical domain network system. The way is
Sending a Domain Name System Query for a first domain name via the data communication network;
Receiving a response to a Domain Name System query for said first domain name via said data communication network, wherein said response is associated with an entity associated with a different second domain name Containing one or more resource records that contain destination information,
Processing the response to the Domain Name System query for the first domain name, wherein the processing associates with the entity associated with the second domain name in the one or more resource records Including identifying the identified contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label following the second domain name.

According to a fifth aspect of the invention, there is provided a computer program for performing a method of processing data in a data communication network comprising a hierarchical domain name system when it is executed. The method is: at the authoritative name server for the first domain name
Receiving a Domain Name System Query for the first domain name via the data communication network;
Processing the Domain Name System query for the received first domain name, the processing comprising obtaining one or more resource records associated with the first domain name The one or more resource records include contact information associated with an entity associated with a different second domain name;
Transmitting a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with said entity associated with said second domain name Including the one or more resource records including the contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label following the second domain name.

According to a sixth aspect of the invention, there is provided a computer program for performing a method of processing data in a data communication network comprising a Hierarchical Domain Name System, when it is executed. The way is
Sending a Domain Name System Query for a first domain name via the data communication network;
Receiving a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with an entity associated with a different second domain name One containing one or more resource records containing contact information,
Processing a response to the Domain Name System query for the first domain name, wherein the processing is associated with the entity associated with the second domain name in the one or more resource records. Including identifying the contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label following the second domain name.

According to a seventh aspect of the invention,
Data identifying the first domain name;
Contact information associated with an entity associated with a different second domain name,
Including
The first domain name includes the second domain name,
The first domain name includes at least one label following the second domain name,
Hierarchical domain name system zone files are provided.

According to an eighth aspect of the present invention there is provided a method of processing data in a data communication network comprising a hierarchical domain name system. The method is: at the authoritative name server for the first domain name
Receiving a Domain Name System Query for the first domain name via the data communication network;
Processing the Domain Name System query for the received first domain name, the processing comprising obtaining one or more resource records associated with the first domain name The one or more resource records include contact information associated with an entity associated with a different second domain name;
Transmitting a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with said entity associated with said second domain name Containing the contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label preceding the second domain name,
The contact information may be in plaintext form in the one or more resource records, and / or the one or more resource records may be TXT type.

According to a ninth aspect of the present invention there is provided a method of processing data in a data communication network comprising a hierarchical domain name system. The way is
Sending a Domain Name System Query for a first domain name via the data communication network;
Receiving a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with an entity associated with a different second domain name One containing one or more resource records containing contact information,
Processing the response to the Domain Name System query for the first domain name, wherein the processing associates with the entity associated with the second domain name in the one or more resource records Including identifying the identified contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label preceding the second domain name,
The contact information may be in plaintext form in the one or more resource records, and / or the one or more resource records may be TXT type.

According to a tenth aspect of the present invention, there is provided an apparatus configured to perform a method of processing data in a data communication network comprising a hierarchical domain name system. The method is: at the authoritative name server for the first domain name
Receiving a Domain Name System Query for the first domain name via the data communication network;
Processing the Domain Name System query for the received first domain name, the processing comprising obtaining one or more resource records associated with the first domain name The one or more resource records include contact information associated with an entity associated with a different second domain name;
Transmitting a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with said entity associated with said second domain name Including the one or more resource records including the contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label preceding the second domain name,
The contact information may be in plaintext form in the one or more resource records, and / or the one or more resource records may be TXT type.

According to an eleventh aspect of the present invention, there is provided an apparatus configured to perform a method of processing data in a data communication network comprising a Hierarchical Domain Name System. The way is
Sending a Domain Name System Query for a first domain name via the data communication network;
Receiving a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with an entity associated with a different second domain name One containing one or more resource records containing contact information,
Processing a response to a Domain Name System query for the first domain name, wherein the processing is associated with the entity associated with the second domain name in the one or more resource records. Including identifying the contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label preceding the second domain name,
The contact information may be in plaintext form in one or more resource records, and / or the one or more resource records may be TXT type.

According to a twelfth aspect of the present invention there is provided a computer program for performing a method of processing data in a data communication network comprising a hierarchical domain name system when it is executed. The method is: at the authoritative name server for the first domain name
Receiving a Domain Name System Query for the first domain name via the data communication network;
Processing the Domain Name System query for the received first domain name, the processing comprising obtaining one or more resource records associated with the first domain name, The one or more resource records include contact information associated with an entity associated with a different second domain name;
Transmitting a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with said entity associated with said second domain name Including the one or more resource records including the contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label preceding the second domain name,
The contact information may be in plaintext form in the one or more resource records, and / or the one or more resource records may be TXT type.

According to a thirteenth aspect of the present invention, there is provided a computer program for performing a method of processing data in a data communication network comprising a hierarchical domain name system when it is executed. The way is
Sending a Domain Name System Query for a first domain name via the data communication network;
Receiving a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with an entity associated with a different second domain name One containing one or more resource records containing contact information,
Processing a response to a Domain Name System query for the first domain name, wherein the processing is associated with the entity associated with the second domain name in the one or more resource records. Including identifying the contact information;
Including
The first domain name includes the second domain name,
The second domain name includes at least one label preceding the second domain name,
The contact information may be in plaintext form in the one or more resource records, and / or the one or more resource records may be TXT type.

According to a fourteenth aspect of the invention,
Data identifying the first domain name;
Contact information associated with an entity associated with a different second domain name,
Including
The first domain name includes the second domain name,
The first domain name includes at least one label preceding the second domain name,
The contact information is in plaintext format,
Hierarchical domain name system zone files are provided.

According to a fifteenth aspect of the present invention,
Data identifying the first domain name;
Contact information associated with an entity associated with a different second domain name,
Including
The first domain name includes the second domain name,
The first domain name includes at least one label preceding the second domain name,
The contact information is a TXT type resource record,
Hierarchical domain name system zone files are provided.

According to a sixteenth aspect of the present invention, there is provided a method of processing data in a data communication network comprising a hierarchical domain name system. The way is
Sending a request for website content from a website associated with a domain name via the data communication network;
Receiving the website content via the data communication network;
Parsing the received website content for contact information associated with the entity associated with the domain name using at least one automated contact information parsing technique When,
Recording the contact information in a zone file;
including.

According to a seventeenth aspect of the present invention, there is provided an apparatus configured to provide a method of processing data in a data communication network comprising a hierarchical domain name system. The way is
Sending a request for website content from a website associated with a domain name via the data communication network;
Receiving the website content via the data communication network;
Analyzing the received website content for contact information associated with an entity associated with the domain name using at least one automatic contact information parsing technique;
Recording the contact information in a zone file;
including.

According to an eighteenth aspect of the present invention, there is provided a computer program for performing a method of processing data in a data communication network comprising a hierarchical domain name system when it is executed. The way is
Sending a request for website content from a website associated with a domain name via the data communication network;
Receiving the website content via the data communication network;
Analyzing the received website content for contact information associated with an entity associated with the domain name using at least one automatic contact information parsing technique;
Recording the contact information in a zone file;
including.

According to a nineteenth aspect of the present invention,
A hierarchical domain name system zone file that contains contact information associated with an entity associated with a domain name,
The zone file contains data indicating that the contact information has been obtained using automatic contact information parsing techniques.
Hierarchical domain name system zone files are provided.

According to a twentieth aspect of the invention,
A hierarchical domain name system zone file that contains contact information associated with an entity associated with a domain name,
Contact information associated with the entity associated with the domain name is included in one or more resource records of TXT type,
Hierarchical domain name system zone files are provided.

  Additional features will become apparent from the following description of an example embodiment given by way of example only and made with reference to the accompanying drawings.

FIG. 1 is a schematic block diagram of an example of a hierarchical domain name system. FIG. 1 is a schematic block diagram of an example data processing network. FIG. 1 is a schematic block diagram of an example of a data processing network according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. FIG. 1 is a schematic block diagram of an example of a data processing network according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. FIG. 1 is a schematic block diagram of an example of a data processing network according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. 5 is a flow chart schematically illustrating an example of a method according to an embodiment of the present invention. FIG. 1 is a schematic block diagram of an example of a hierarchical domain name system according to an embodiment of the present invention. FIG. 1 is a schematic block diagram of an example of a hierarchical domain name system according to an embodiment of the present invention. FIG. 1 is a schematic block diagram of an example of a hierarchical domain name system according to an embodiment of the present invention. FIG. 1 is a schematic block diagram of an example of a hierarchical domain name system according to an embodiment of the present invention. FIG. 1 is a schematic block diagram of an example of an apparatus according to an embodiment of the present invention.

  Referring to FIG. 1, an example of a hierarchical domain name system 100 is schematically illustrated. In this example, the Hierarchical Domain Name System is Domain Name System (DNS).

  DNS is a global distributed hierarchical naming system for resources connected to computer networks. DNS is described in detail, for example, in RFCs 1034 and 1035. One function of DNS is to translate human-friendly domain names into machine-friendly Internet Protocol (IP) addresses. For example, DNS may translate the human-friendly domain name "example.com" into a machine-friendly IP address 123.45.67.89. DNS functions as a directory service of the Internet.

  Every domain name on the Internet is part of DNS. DNS is the backbone of the Internet and was created to make the Internet easier to use. DNS converts easy-to-remember domain names into IP addresses of IP devices such as servers. DNS is used daily by billions of people. DNS is used whenever someone enters a domain name in his web browser. The DNS tells the web browser, for example, a computer or a smartphone, to which web server to go to when a website, for example "example.com" is requested.

  Every domain name is hosted on a DNS server. There are thousands of DNS servers running around the world. Information about domain names is recorded in zone files on the DNS server. Zone files contain DNS resource records. The DNS is configured of a name server that holds information on domain names in the DNS zone. Information about each domain name is kept in a zone file. Included in the zone file is a DNS resource record.

  At the top level of the DNS hierarchy is the root name server. The root name server lists the authoritative name servers for the top level domain (TLD). Examples of TLDs include, but are not limited to "com" and "uk".

  For the domain name "this.example.com", the following are all domain names: "this.example.com", "example.com", and "com". "Com" is a TLD. In addition to being a domain name, “example.com” is a subdomain of TLD “com”, and “this.example.com” is a subdomain of domain name “example.com”. Each part of the domain name separated by a dot (.) Is called a label. In the domain name "this.example.com", "this", "example", and "com" are labels.

  For the domain name "this.example.co.uk", the following: "this.example.co.uk", "example.co.uk", "co.uk" and "uk" are all domain names It is. "Uk" is the country code TLD (ccTLD). "Co. Uk" is a sub-domain of ccTLD "uk" in addition to being a domain name, "example. Co. Uk" is a sub-domain of domain name "co. Uk", "this. Example" .Co.uk is a subdomain of the domain name "example.co.uk". In the domain name "this.example.co.uk", "this", "example", "co", and "uk" are labels.

  The TLD (or "name space") is managed by the domain registry (hereinafter "registry"). For example, VeriSign is a registry that manages the "com" namespace. Nominet is a registry that manages the "uk" namespace. Some registries split their domain names into subdomains. For example, Nominet splits its TLD "uk" into "co. Uk", "org. Uk", "me. Uk" and others. Nominet has recently allowed the creation of domain names at the second level under "uk" in the format of "example.uk". Creating a new domain in the namespace is known as domain name registration.

  Although domain names may be registered directly through the registry, this is not recommended, and registration of domain names in the registry namespace is usually done through the domain registrar (hereinafter "registrar") . The registrar charges a fee for registration in its namespace. This fee varies by registrar, but may be charged on a yearly basis, for example. A person registering a domain name (eg, "example.com") through a registration authority is known as a registrant. The registrant is allowed to set up additional domain names (sub-domains) within that domain (eg "this.example.com"). Subscribers may be able to set up subdomains at no additional charge.

  Every domain name has an authoritative name server. The authoritative name server is a name server that holds current DNS resource records for domain names. There are various types of DNS resource records. One type of resource record is a name server (NS) record. The NS resource record is used to delegate DNS zone authority to another name server. The most common DNS resource record is the "A" record. A records are used to direct web site requests to IP addresses. The DNS resource record types include, but are not limited to, mail exchange records (MX) for e-mail and records for free text (TXT), and there are other record types.

  Referring to FIG. 2, a diagram of an example of a data communication network 200 is schematically illustrated.

  Data communication network 200 includes user device 201. A user device is associated with a user. Examples of user devices 201 include, but are not limited to, smartphones, tablet computing devices, laptop computers, desktop computers, satellite navigation devices, and smart televisions. Data communication network 200 also includes a local network 202. Local network 202 includes one or more components. An example of a component of the local network 202 is a router. The communication network 200 also includes a DNS resolver 203 at the user's Internet Service Provider (ISP). Communication network 200 also includes route server 204. Communication network 200 also includes registry name server 205. In this example, the registry name server 205 is the authoritative name server of the top level domain name "com". Communication network 200 also includes registrant name server 206. In this example, the registrant name server 206 is the authoritative name server of the domain name "example.com".

  The process of finding DNS resource records for domain names is known as DNS resolution or domain name resolution. DNS resolvers are used for this purpose. The DNS resolver works with the rightmost label, working towards the leftmost of the domain name, and determines the authoritative name server for a given domain name by resolving the full domain name.

  In this example, the user enters the domain name “example.com” in the web browser on his user device 201.

  If a domain name is recently resolved, the DNS resource record previously retrieved for that domain name is recorded in the DNS cache of the user device 201 or in the DNS of the local network 202, which is the user device 201 Will be returned to

  For example, if the IP address for the domain name "example.com" is not cached on the local network 202, then the DNS query is passed to the DNS resolver 203 if the domain name "example.com" has not been recently resolved. Be

  In this example, the DNS resolver 203 performs a recursive DNS lookup beginning with the label "com". The DNS resolver 203 first resolves the domain name of the label starting with the rightmost, and requests from the root server 204 the IP address of the authoritative name server 205 for the “com” TLD. The IP address of the authoritative name server 205 for the "com" domain name is returned from the root server 204.

  The DNS resolver 203 queries the authoritative name server 205 for the domain name “com” for the IP address of the authoritative name server 206 of the domain name “example.com”.

  The authoritative name server 205 for the domain name "com" returns the IP address of the authoritative name server 206 for the domain name "example.com" to the DNS resolver 203. In this example, the authoritative name server 206 for the domain name “example.com” is a registrant of the domain name “example.com” when the registrant of the domain name “example.com registers its domain name“ example.com ”. Is the name server chosen by.

  When the DNS resolver 203 reaches the leftmost label of the domain name "example.com", the DNS resolver 203 sends a DNS resource for the domain name "example.com" from the authoritative server 206 for the domain name "example.com". Request a record The DNS resolver 203 returns an error if the resource record is not found.

  If a resource record for the domain name "example.com" is found, the IP address of the web server associated with the domain name "example.com" is sent to the DNS resolver 203 as a resource record for the domain name "example.com". returned. The DNS resolver 203 stores resource records in a cache.

  The DNS resolver 203 returns resource records to the local network 202. The local network 202 stores resource records in a cache.

  The local network 202 returns the resource record to the user device 201. The user device 201 stores resource records in a cache. A web browser running on user device 201 requests the IP address of the web server associated with domain name "example.com" on port 80 to obtain website HTML content for domain name "example.com" Send The IP address of the web server associated with the domain name "example.com" was included in the resource record returned by the DNS resolver 203.

  As indicated above, the resource records retrieved for the domain name "example.com" are cached at the user device 201, at the local network 202, and at the DNS resolver 203 for a specified period of time Ru. The specified time is determined by the lifetime ("TTL") setting of the returned resource record.

  The DNS query is sent to the name server by using User Datagram Protocol (UDP) on port 53. The response to the DNS query from the name server includes the response to the query. The answer is provided by the DNS zone file, which lists resource records of domain names. As with even TLDs, every domain name has an associated zone file.

The format of the DNS zone file is defined in RFC1035 (section 5) and RFC1034 (section 3.6.1). This format was originally used by the Berkeley Internet Name Domain (BIND) software package, but has become widely adopted by other DNS servers. A zone file is a sequence of entries of resource records. Each line of the zone file is a text description that defines a single resource record. The text description contains several fields separated by whitespace as follows:

An example entry of the zone file of the example domain name "example.com" is as follows.

  The TTL value is 270 seconds in this example and indicates how long the record should be stored in the cache.

An example DNS query of any DNS resource record type for an exemplary domain name "example.com" generated using the "dig" command line tool is as follows:

An example of the response received from the name server for the domain name "example.com" is as follows.

  In this example, the DNS query for the domain name "example.com" is returning 5 resource records. Each resource record is shown on its own line. The first resource record displayed in the first line is an A record indicating the IP address of the server that processes the HTTP request at port "80". The second resource record displayed in the second line is an MX resource record with a priority of "10" indicating that the e-mail is to be processed by "mailserver.com". The third resource record and the fourth resource record shown in the third and fourth lines indicate that the authoritative name server for the domain name is "ns1.nameserver.com" and "ns2.nameserver.com" It is an NS record indicating that. The last resource record in the fifth line is a TXT record in sender policy framework ("SPF") format.

  SPF is an established way to tackle spam. SPF allows domain name owners to list servers that can be used to send e-mail instead of domain names. The SPF record in the above example means that the only IP address allowed to send an e-mail instead of the domain name "example.com" is the IP address 123.45.67.89 . The final part "-all" means that e-mails from all other IP addresses should be treated as spam. The recipient's e-mail server checks the SPF record when receiving e-mail from the domain name and follows the SPF guidance to filter and block spam e-mail.

  Referring to FIG. 3, a block diagram of an example of a data communication network 300 is schematically illustrated. Data communication network 300 may be used to process data as described in detail herein.

  In this example, data communication network 300 is used in application to a framework hereinafter referred to as the "Name Over Method (NOM) Framework".

  The NOM framework allows entities such as, for example, companies and / or individuals to list to others how they can connect with them. An entity may be a registrant of one or more domain names. For example, the entity has not been invented yet, as well as contact information for contacting by phone, Whatsapp (TM), Instagram (TM), Pinterest (TM), Facebook (TM), Twitter (TM) and others New social media platforms can also be listed. Examples of contact identifiers include, but are not limited to, phone numbers, GPS coordinates, FacebookTM pages, and the like. This contact information is recorded in association with the entity's domain name. The NOM framework also defines how contact information can be retrieved for a given domain name. The NOM framework is extensible and can accommodate future communication methods.

  The NOM framework allows domain name owners to record contact information in DNS in association with domain names. Subsequently, the user can use DNS to convert domain names into contact information, using a specially formatted DNS record, hereafter called "NOM record". The NOM record contains one or more resource records.

  If you have access to your DNS settings, domain name owners can use the NOM framework to create their own NOM records. This type of NOM record is hereinafter referred to as “ndependent NOM Record”. Many domain name owners lack the technical expertise to create their own independent NOM records.

  Within the NOM framework where NOM records are hosted, host services are available on behalf of domain name owners. This type of NOM record is hereinafter referred to as "Hosted NOM Record". The host NOM record may be managed and / or the contact information recorded in the host NOM record may be updated, for example using a web interface.

  In this example, data communication network 300 includes a first device 301, a second device 302, a third device 303, and a fourth device 304. In this example, the four devices 301, 302, 303, 304 are interconnected via a computer network 305. In this example, computer network 305 is the Internet.

  In this example, the first device 301 is a user device that includes DNS query functionality, hereinafter referred to as a "NOM Interrogator". In this example, the NOM Interrogator is part of the software. The NOM interrogator is, for example, a smartphone application, a web application, a satellite navigation system application, a smart TV application, or another program running on any other device. The NOM interrogator makes a request to the DNS system, retrieves the NOM record, and performs processing such as displaying the result. Queries to the NOM framework may be handled in the same way as standard DNS queries, ie on port 53 via UDP.

  The NOM Interrogator is responsible for formatting and displaying the NOM records, eg display to the user. The way in which NOM records are displayed may vary depending on one of many factors. An example of such a factor is the NOM interrogator and / or user device type. For example, the satellite navigation system may ignore all data except GPS coordinates and display this data as a location on the map. This type of NOM interrogator may allow the GPS system to navigate to the locations listed by domain name. The telephone autodialing device may ignore all data except the telephone number. The telephone autodialing device may dial that number as soon as the number is returned. The telephone autodialing device may display options for the number to be dialed when multiple numbers are returned, and may display a label for each telephone number.

  Using the NOM Interrogator to retrieve contact information about a domain name is hereinafter referred to as "NOM Lookup". NOM lookups can be performed for any domain name. NOM lookup corresponds to DNS query.

  In this example A, the second device 302 is a name server, hereinafter referred to as the "independent server". The independent server 302 records independent NOM records. Independent NOM records are written directly to the authoritative DNS resource record of the domain name.

  In this example, the third device 303 is a name server, hereinafter referred to as the "NOM server". The NOM server 303 hosts host NOM records. The host NOM record is recorded in the DNS resource record of the NOM server 303 instead of the entity associated with the domain name. An example of such an entity is a registrant of a domain name. Another example of such an entity is a company that wishes to associate contact details with domain names, whether or not they are registrants, as described in more detail below.

  In this example, the fourth device 304 is a server, hereinafter referred to as the "NOM Bot". In some examples, the NOM bot 304 automatically creates NOM records for domains that have neither independent NOM records nor host NOM records. If a NOM lookup is performed on a domain name that does not yet have a NOM record, in some instances, the NOM bot 304 creates a new NOM record based on the content of the web site indicated in the domain name . The NOM Bot 304 collects the contact information shown on the website and creates a NOM record based on the contact information on the website.

  Although the NOM bot 304 is shown as separate from the other devices 301, 302, 303 in the data communication network 300 in this example, some or all of its functionality will be described in more detail below. Can be incorporated into one or more of the other devices 301, 302, 303. For example, the functionality of the NOM bot 304 may be provided by the hardware and / or software of the user device 301.

  A NOM record is a record that includes one or more specially formatted DNS resource records that include contact information associated with an entity associated with a domain name. One or more resource records may consist only of TXT type resource records. TXT resource records make it possible to record arbitrary text. TXT resource records are already used for SPF, as can be seen in the zone file example given above as well as other restricted uses.

  In this example, the contact information of the NOM record is recorded in plaintext format. In other words, contact information is recorded in an unencrypted form. Recording contact information in plaintext format facilitates access to the contact information.

NOM lookups use DNS queries to request NOM records. The format of an example DNS query where << domain_to_lookup >> is used as a placeholder for an example purpose is as follows:

An example format of the DNS response to the NOM lookup is as follows, where << domain_to_lookup >> is again used as a placeholder for an illustrative purpose, and << nom_record_content >> indicates the content of the NOM record: It is street.

  Unlike SPF, in some instances, NOM records are not recorded at the root of the domain name. Instead, for independent NOM records, independent NOM records are recorded in their own subdomain. An example of such a subdomain is "nomrecordlookup". This helps to keep the DNS efficient and orderly.

In some examples, the NOM lookup for the domain name "example.com" will involve a DNS query for the subdomain "nomrecordlookup.example.com". In other words, at least one label is prepended to the domain name for which contact information is sought. The label is "nomrecordlookup" in this example. Such DNS queries will be made to the authoritative name server for the "nomrecordlookup" subdomain of the domain name to which the NOM lookup relates. This type of NOM lookup is hereinafter referred to as "independent NOM domain name lookup". An example of the form of a DNS query for independent NOM domain name lookup for domain name "example.com" is as follows.

  In this example, only TXT resource records are required, as opposed to any type of resource record. Any type of resource record may be requested by including the type identifier "ANY" in the request. By simply requesting only TXT resource records, queries and responses can be processed quickly. In this example, only TXT resource records will be returned. If no answer is received, the query is a failure. If a response is received but the response does not contain a NOM record, the query is a failure.

In some examples, if the first query fails, a second NOM lookup is performed to the NOM server 303. This type of NOM lookup is hereinafter referred to as "Host NOM Domain Name Lookup". In this example, the domain name being queried ("example.com") is prepended to at least one label. In some instances, at least one label forms part of a resolvable domain name. In this example, the resolvable domain name added after the domain name for which contact information is sought is "lookup.nomserver.com". The resolvable domain names include three labels: "lookup", "nomserver", and "com". The domain name "lookup.nomserver.com" is resolvable if the DNS query for the domain name "lookup.nomserver.com" results in a DNS response. An example of the form of a DNS query for host NOM domain lookup for domain name "example.com" is as follows.

  If the second NOM lookup also fails, a third phase may follow, in which NOM records are automatically created by NOM bot 304 based on the website content published on the domain name. This third step can be accomplished in a variety of different ways, as described in more detail below.

Independent NOM records are returned from independent server 302 in the following format:

In the above example, the independent NOM record has a line break for the formatting of this document, but the NOM record itself does not contain a line break. The independent NOM record has a first part that conforms to the standard DNS response format.

  The item "nomrecordlookup.example.com" is the zone being queried. The item “3600” is a TTL indicated in seconds. The TTL indicates how long records can be stored in the cache. The item "IN" indicates the class of response. The item "TXT" indicates the type of DNS resource record returned.

The independent NOM record includes a second portion that includes contact information associated with the domain name "example.com". In this example, the part containing the contact information with a line break added for clarity is as follows.

  When the independent server 302 returns a TXT resource record, it encloses the data in quotes. In some instances, the syntax of the NOM record dictates that each data portion should be separated by a pipe ("|") character.

  The item “v = NOM1” indicates that the TXT resource record is a NOM record using version 1 of the NOM syntax. This item is similar to the format used in SPF records and other uses of TXT records. Version numbers allow different interpretations to be specified in different syntaxes as the NOM framework evolves.

  The item "t = r" indicates the "type" of the NOM record. In this example, "r" means "root". This allows for further extensions of the NOM framework in the future.

  The item “n = Example Company Ltd” is the name of the company for which the NOM record is targeted.

  The item "tel = General: 0123456789" contains a contact identifier. "Tel" indicates that the contact identifier is a telephone number. "General" indicates that the telephone number is for general inquiry. The number "0123456789" is the telephone number itself. The item "tel = Support: 0123498765" is similar except that the phone number "0123498765" is for "support".

  The item “fb = nomfb” includes a contact identifier. "Fb" indicates that the contact identifier is related to the Facebook (trademark) profile. In this case, the contact method associated with the contact identifier is Facebook (trademark). If the contact identifier is displayed to the user to provide a link to the Facebook (TM) page, the contact method URL, in this case "http: //www.facebook .Com "will be prepended to it.

  The item "tw = nomtw" contains a contact identifier. "Tw" indicates that the contact identifier relates to the Twitter (trademark) profile. In this case, the contact method associated with the contact identifier is Twitter (trademark). If the contact identifier is displayed to the user to provide a link to the Twitter (TM) page, the contact method URL, in this case "http://www.twitter.com" Will be prepended.

  The last period (.) Indicates the end of the NOM record.

  The NOM record given as an example is for illustrative purposes only. The NOM record may include other contact identifiers relating to different contact methods, such as the geographical contact identifier "gps".

DNS TXT resource records are limited to 255 characters. If NOM records exceed this limit, TXT resource records may be chained together as follows.

  In the above example, the variable "p" is present. This variable indicates the number of parts making up the NOM record. "P = 1/2" means the first of two parts.

  The multiple NOM records are, for example, nomrecordlookup. example. com as an independent NOM record, or for example com. lookup. nomserver. Can be recorded as a host NOM record at com. Such NOM records are concatenated in the correct order and then processed.

  Referring to FIG. 4, a flowchart illustrating an example of a method of processing data is shown. The method according to this example is associated with the NOM lookup.

  At 400, a domain name is identified. For example, the user can enter a domain name. In this example, the domain name is "example.com".

  At 401, an independent NOM domain name lookup is performed. Independent NOM domain name lookup involves adding one or more labels, such as "nomrecordlookup", and a dot (.) Before the domain name "example.com". In this example, the word "nomrecordlookup." Is prepended to "example.com" to form a lookup domain name of "nomrecordlookup.example.com".

  At 402, it is determined as a result of the independent NOM domain name lookup performed at 401 whether a NOM record has been returned.

  As a result of the determination in 402, if the NOM record is returned, the NOM record is subsequently displayed in 403.

  If the NOM record is not returned as a result of the determination at 402, a host NOM domain name lookup is subsequently performed at 404. The host NOM domain name lookup involves adding the domain name "example.com" followed by one or more labels, eg, "lookup.nomserver.com". In this example, “example.com”, “lookup.nomserver.com”, and “example.com.lookup.nomserver.com” are all resolvable domain names.

  At 405, it is determined as a result of the host NOM domain name lookup performed at 404 that a NOM record has been returned.

  If the result of the determination at 405 is that a NOM record is returned, then at 403, the NOM record is displayed.

  If the result of the determination at 405 is that a NOM record is not returned, then at 406 a NOM bot lookup is performed.

  At 407, it is determined whether the NOM bot lookup performed at 406 results in a NOM record being returned.

  If NOM record is returned as a result of determination at 407, NOM record is displayed at 403 subsequently.

  If, as a result of the determination at 407, the NOM record is not returned, predetermined actions are subsequently taken. In this example, the predetermined action involves an error message being returned and displayed. For example, the message "NOM record not found for this domain name" may be displayed.

  In this example, items 400, 402, 403, 405, 407, and 408 are performed by the NOM interrogator. In this example, items 401, 404, and 406 involve at least one other device other than the user device being a NOM Interrogator.

  Referring to FIG. 5, a flowchart illustrating an example of a method of processing data is shown. The method according to this example is associated with an independent NOM domain name lookup. In this example, independent NOM records for a given domain are recorded in the domain zone file on the authoritative server for the given domain under the subdomain "nomrecordlookup".

  At 500, a domain name is identified. For example, the domain name is provided by the user. In this example, the domain name is "example.com".

  At 501, the identified domain name is prepended with one or more labels. In this example, the identified domain is prefixed with the label "nomrecordlookup" and a dot. In this example, the term "nomrecordlookup." Is prepended to "example.com" so that the lookup domain name "nomrecordlookup.example.com" is available.

  In this example, the domain name "nomrecordlookup.example.com" is a first domain name and the domain name "example.com" is a second domain name. The first domain name "nomrecordlookup.example.com" includes the second domain name "example.com". The first domain name "nomrecordlookup.example.com" further includes at least one label preceding "example.com". In this example, the label is "nomrecordlookup".

  At 502, domain name resolution is performed using the obtained domain name "nomrecordlookup.example.com". This may be done by performing a DNS query using the domain name "nomrecordlookup.example.com".

  At 503, it is determined whether the domain name has been resolved as a result of the domain name resolution performed at 502.

  If the result of determination in 503 is that the domain name has not been resolved, predetermined action is subsequently taken in 504. In this example, the predetermined action involves an error being returned.

  If the result of the determination in 503 is that the domain name has been resolved, it is subsequently determined in 505 whether there is a TXT resource record.

  If the result of the determination at 505 is that there is no TXT resource record, then at 504, predetermined actions are taken.

  If the result of the determination at 505 is that there is a TXT record, then at 506 it is determined whether the TXT resource record is a valid NOM record.

  If the result of the determination at 506 is that the TXT resource record is not a valid NOM record, then, at 504, predetermined actions are taken.

  If the result of the determination at 506 is that the TXT resource record is a valid NOM record, a NOM record is subsequently returned at 507.

  Referring to FIG. 6, a diagram of an example of a data communication network 600 is shown. In this example, data communication network 600 is used to perform an independent NOM domain name lookup. In this example, the user is attempting to enter the domain name "example.com" and obtain contact information associated with the entity associated with the domain name.

  In this example, data communication network 600 includes a user device 601 including a NOM interrogator, a local network 602, a DNS resolver 603, and three name servers 604, 605, 606.

  In this example, the NOM interrogator on user device 601 performs an independent NOM domain name lookup for the domain name "example.com". In this example, the NOM interrogator requests a TXT resource record using only the lookup domain name "nomrecordlookup.example.com".

  If the resource record for the domain name “nomrecordlookup.example.com” is not stored in the cache on the local network 602, the query is forwarded to the DNS resolver 603.

  The DNS resolver 603 resolves the lookup domain “nomrecordlookup.example.com” starting from the rightmost label. In this example, the rightmost label is the "com" TLD.

  In this example, the name server 604 is a route server that returns the IP address of the authoritative name server 605 for the "com" TLD.

  The DNS resolver 603 requests the authoritative name server for the domain name "example.com" from the authoritative name server 605 for the domain name "com".

  The authoritative name server 605 for the domain name "com" returns the name server address for the authoritative name server for the domain name "example.com". The DNS resolver 603 resolves the name server address for the authoritative name server for the domain name "example.com" as the IP address of the authoritative name server 606 for the domain name "example.com".

  The DNS resolver 603 requests the authoritative name server for the domain name "nomrecordlookup.example.com" from the authoritative name server 606 for the domain name "example.com".

  The authoritative name server 606 for the domain name "example.com" returns the name server address of the authoritative name server 606 for the domain name "nomrecordlookup.example.com". If found, the DNS resolver 603 resolves this name server address as the IP address of the authoritative name server 606 for the domain name "nomrecordlookup.example.com".

  The DNS resolver 603 requests a NOM record for the domain name "nomrecordlookup.example.com" from the authoritative name server 606 for the domain name "nomrecordlookup.example.com" or the domain name "nomrecordlookup.example.com" An error is returned if no authoritative name server is found for. In this example, the NOM record contains one or more specially formatted DNS TXT resource records.

  Assuming that the authoritative name server for the domain name "nomrecordlookup.example.com" is found, then the authoritative name server 606 for the domain name "nomrecordlookup.example.com" matches the NOM record for "nomrecordlookup.example.com". Returns an error if it returns or if there is no NOM record.

  The DNS resolver 603 passes the result to the local network 602. If the authoritative name server for the domain name "nomrecordlookup.example.com" is not found, the DNS resolver 603 returns an error instead of a NOM record.

  The NOM Interrogator receives and processes the response. If the response is a valid NOM format, in some instances, the process is complete. If the response was an error or an invalid format, the NOM interrogator may perform one or more additional actions. In some examples, one or more additional actions may include performing a host NOM domain name lookup, as described with reference to FIGS. 7 and 8.

  Referring to FIG. 7, a flowchart illustrating an example of a method of processing data is shown. The method according to this example is associated with a host NOM domain name lookup. In this example, the NOM record is recorded in the domain zone file of the NOM server, with a subdomain called domain name "lookup.nomserver.com". By hosting NOM records, you can use the distributed nature of DNS and the caching capabilities. The domain name "lookup.nomserver.com" is a resolvable domain name that includes the three labels "lookup", "nomserver", and "com".

  At 700, a domain name is identified. In this example, the domain name is "example.com".

  At 701, three labels, "lookup", "nomserver", and "com" are identified in "lookup.nomserver.com" so that the domain name "example.com.lookup.nomserver.com" can be obtained Is added after "example.com" which is the specified domain name.

  In this example, the domain name "example.com.lookup.nomserver.com" is the first domain name and the domain name "example.com" is the second domain name. The first domain name "example.com.lookup.nomserver.com" includes the second domain name "example.com". The first domain name includes at least one label following the second domain name. In this example, the first domain name includes three labels following the second domain name: "lookup", "nomserver", and "com". The label "com" corresponds to a TLD. The label "nomserver" corresponds to the second level domain name. The label "lookup" corresponds to the third level domain name. At least one label following the second domain name contained in the first domain name forms part of the resolvable domain name. In this example, each of the three labels "lookup", "nomserver" and "com" following the second domain name "example.com" form part of the resolvable third domain name. In this example, the resolvable third domain name is "lookup.nomserver.com". The second domain name "example.com" is also a resolvable domain name in that the domain name "example.com" resolves with a given IP address itself.

  In this example, there is no label in the first domain name "example.com.lookup.nomserver.com" before the second domain name "example.com". In other words, the label in the first domain name does not precede the second domain name. That is, the second domain name "example.com" is at the leftmost end of the first domain name "example.com.lookup.nomserver.com".

  In this example, there is an authoritative name server for the domain name "example.com.lookup.nomserver.com" and an additional authoritative name server for the domain name "example.com". In this example, the two authoritative name servers are different from one another.

  At 702, domain name resolution is performed using the obtained domain name "example.com.lookup.nomserver.com".

  At 703, it is determined whether the domain name has been resolved as a result of the domain name resolution performed at 702.

  If the result of determination in 703 indicates that the domain name has not been resolved, predetermined action is subsequently taken in 704. In this example, the predetermined action involves an error message being returned.

  If the result of determination in 703 is that the domain name has been resolved, it is subsequently determined in 705 whether there is a TXT resource record.

  As a result of the determination at 705, if there is a TXT resource record, a predetermined action is subsequently taken at 704.

  As a result of the determination at 705, if there is a TXT resource record, it is subsequently determined at 706 whether the TXT resource record is a valid NOM record.

  As a result of the determination at 706, if the TXT resource record is not a valid NOM record, then at 704, predetermined actions are taken.

  If the result of the determination at 706 indicates that the TXT record is a valid NOM record, then at 707 the NOM record is returned.

  Referring to FIG. 8, a schematic block diagram illustrating an example of a data communication network 800 is shown. In this example, data communication network 800 is used to perform host NOM domain name lookup. In this example, the host NOM domain name lookup uses the lookup domain name "example.com.lookup.nomserver.com" and requests only TXT resource records.

  In this example, data communication network 800 includes a user device 801 including a NOM interrogator, a local network 802, a DNS resolver 803, and three name servers 804, 805, 806.

  If the resource record for the domain name "example.com.lookup.nomserver.com" is not stored in the cache on the local network 802, the query for the domain name "example.com.lookup.nomserver.com" is DNS resolver 803. Transferred to

  The DNS resolver 803 resolves the lookup domain “example.com.lookup.nomserver.com” starting from the rightmost label. In this example, the rightmost label is the "com" TLD.

  In this example, the name server 804 is a route server that returns the IP address of the authoritative name server 805 for the "com" TLD.

  The DNS resolver 803 requests the authoritative name server for the domain name "nomserver.com" from the authoritative name server 805 for the domain name "com".

  The authoritative name server 805 for the domain name "com" returns the authoritative name server address for the domain name "nomserver.com". The DNS resolver 803 resolves the authoritative name server address for the domain name "nomserver.com" as the IP address of the authoritative name server 806 for the domain name "nomserver.com".

  The DNS resolver 803 requests the authoritative name server for the domain name "lookup.nomserver.com" from the authoritative name server 806 for the domain name "nomserver.com".

  The authoritative name server 806 for the domain name "nomserver.com", which in this example is the NOM server, returns the authoritative name server for the domain name "lookup.nomserver.com". The DNS resolver 803 resolves the authoritative name server address for the domain name "lookup.nomserver.com" as the IP address of the authoritative name server 806 for the domain name "lookup.nomserver.com".

  The DNS resolver 803 requests the authoritative name server for the domain name "com.lookup.nomserver.com" from the authoritative name server 806 for the domain name "lookup.nomserver.com".

  The authoritative name server 806 for the domain name "lookup.nomserver.com", which in this example is the NOM server, returns the authoritative name server for the domain name "com.lookup.nomserver.com". The DNS resolver 803 resolves the authoritative name server address for the domain name "com.lookup.nomserver.com" as the IP address of the authoritative name server 806 for the domain name "com.lookup.nomserver.com".

  The DNS resolver 803 requests the authoritative name server for the domain name "example.com.lookup.nomserver.com" from the authoritative name server 806 for the domain name "com.lookup.nomserver.com".

  The authoritative name server 806 for the domain name "com.lookup.nomserver.com", which in this example is a NOM server, returns the authoritative name server address for the domain name "example.com.lookup.nomserver.com". DNS resolver 803 resolves the authoritative name server address for the domain name "example.com.lookup.nomserver.com" as the IP address of the authoritative name server 806 for the domain name "example.com.lookup.nomserver.com" Do.

  The DNS resolver 803 requests a NOM record for the domain name "example.com.lookup.nomserver.com" from the authoritative name server 806 for the domain name "example.com.lookup.nomserver.com" or If the authoritative name server for the name "example.com.lookup.nomserver.com" can not be found, an error is returned. In this example, the NOM record is a specially formatted DNS TXT resource record. In this example, the NOM record contains one or more resource records of TXT type.

  Thus, in this example, the authoritative name server for the domain name "example.com.lookup.nomserver.com" receives a domain name system query for the domain name "example.com.lookup.nomserver.com" . In this example, the authoritative name server for the domain name "example.com.lookup.nomserver.com" is the name server 806. The name server 806 processes domain name system queries received for domain names ("example.com.lookup.nomserver.com"). When processing a received Domain Name System query, one or more resource records associated with the domain name "example.com.lookup.nomserver.com" are obtained. The one or more resource records include content information associated with the entity associated with the domain name "example.com".

  Assuming that the authoritative name server for the domain name "example.com.lookup.nomserver.com" is found, the authoritative name server 806 for the domain name "example.com.lookup.nomserver.com" Returns a NOM record for ".lookup.nomserver.com" or returns an error if the NOM record does not exist. In this example, the one or more resource records included in the NOM record are in the zone file describing the first domain name "example.com.lookup.nomserver.com". In some examples, the authoritative name server for the domain name "example.com.lookup.nomserver.com" is in the zone file describing the first domain name "example.com.lookup.nomserver.com" You have prerecorded one or more resource records. In some examples, the authoritative name server for the domain name "example.com.lookup.nomserver.com" is one or more from the zone file that describes the first domain name "example.com.lookup.nomserver.com" Retrieve resource records of

  In some examples, one or more resource records include multiple resource records. For example, there may be multiple resource records chained together.

  Thus, the authoritative name server for the domain name "example.com.lookup.nomserver.com" sends a response to the domain name system query for the domain name "example.com.lookup.nomserver.com". The response includes one or more resource records that include contact information associated with the entity associated with the domain name "example.com". In this example, the response to the Domain Name System Query contains only one or more resource records contained in the NOM record.

  The DNS resolver 803 passes the result to the local network 802. If the authoritative name server for the domain name "example.com.domain.nomserver.com" is not found, the DNS resolver 803 returns an error instead of a NOM record.

  The NOM interrogator on user device 801 receives the response. If the response is in a valid NOM format, the process may be complete. If the response is in error or in an invalid format, the NOM interrogator performs one or more additional actions. In some examples, one or more additional actions include performing a NOM bot lookup, as described below with reference to FIGS. 9-11.

  In this example, user device 801 sends a domain name system query for the first domain name "example.com.lookup.nomserver.com". User device 801 receives a response to a Domain Name System query for a first domain name "example.com.lookup.nomserver.com". The response includes one or more resource records that include contact information associated with an entity associated with a different second domain name "example.com". User device 801 processes responses to domain name system queries for the first domain name "example.com.lookup.nomserver.com". The process includes identifying contact information associated with the entity associated with the second domain name "example.com" of one or more resource records.

  If the user requests a NOM record for a domain name that has neither an independent NOM record nor a host NOM record, the NOM bot attempts to automatically create a NOM record based on the website content indicated in the domain name. The NOM bot parses the HTML content on the website and collects contact information from this content. There are various different ways in which the NOM bot process can be initiated. Three example techniques are shown here with reference to FIGS. 9, 10 and 11. Two of these example techniques described by FIGS. 9 and 10 are “server side” techniques. In these two server-side technology examples, the NOM bot runs on the server infrastructure. One of these example techniques described by FIG. 11 is the “client side” technique. In the client-side example technology, the process is performed on a user device.

  The illustration of each implementation described below launches a NOM bot to collect and analyze HTML content. To do this, each method requests a website with domain name "example.com" by HTTP on port 80. The web server responsible for the domain name "example.com" returns the HTML for the home page. The HTML is parsed for links, and a list of links will be created that will include contact information for the business. These pages are hereinafter referred to as "potential contact pages".

The NOM bot finds a potential contact page by evaluating the link text and page URL used. An example HTML that can be obtained by NOM bots is:

Another example of HTML content that NOM bots can obtain is:

  Because the hyperlink text in the first example is "contact us" and the hyperlink URL in the second example is "contact.html", the NOM bot will contact both of these links with potential It will be considered as a link to the previous page. The NOM bot looks for keywords in the link text and URLs to evaluate whether the link may move to a page containing contact information. An example of such a keyword is "contact".

  In this example, the NOM bot then creates a string of data based on the HTML on the home page and the HTML found on the potential contact page and records this in memory. The NOM bot uses pattern matching and / or regular expressions and parses this HTML to pick out contact information for each method the NOM bot is programmed to look for.

ＮＯＭボットが電話番号であると見なさない場合がある番号の例は、以下の例のＨＴＭＬコンテンツで示される。

For example, when searching for phone numbers, NOM bots look for sequences of numbers. NOM bots start with 01, 02, 03, 07, or 08 when searching for UK user numbers, with or without spaces, a sequence of 10 or 11 digit numbers, and a leading "+" sign Look for a sequence of 11 or 12 digit numbers starting with 44, with or without a space appended to. In some instances, the NOM bot intentionally ignores the 09 number as it is a premium number in the UK and potentially useless. NOM bots can use different matching rules when finding other country numbers. The NOM bots may ignore sequences of numbers preceded by a currency symbol or end of a weight measurement. An example telephone number that the NOM bot will identify in this example is shown in the HTML content of the example below.

An example of a number that the NOM bot may not consider to be a telephone number is shown in the HTML content of the example below.

In some instances, for example, when searching for social media contact identifiers, such as identifiers associated with TwitterTM, FacebookTM, or LinkedInTM profiles, NOM bots encounter a termination character with NOM bots Look for “twitter.com/”, “facebook.com/” or “linkedin.com/” in the HTML content until you right click on the text on the right Think of it as the contact identifier associated with your LinkedInTM profile. In some instances, the end character is a single or double quotation mark, but the end character may be another character such as a space. In some cases, the search is not case sensitive. An example of HTML content from which NOM bots can identify social media content identifiers is as follows.

  Each contact method may have different pattern matching rules, and new contact methods and rules may be added to the NOM bot.

  For example, if the contact information is not recorded in clear text, such as if the contact information is displayed in the image or otherwise hidden by the client-side JavaScript, this information is NOM It may not be removable by the bot.

  Referring to FIG. 9, a flowchart illustrating an example of a method of processing data is shown. In this example, the method is associated with the first example of NOM bot lookup. In this example, the NOM bot lookup is in the form of a NOM bot DNS query.

  At 900, a domain name is identified. In this example, the domain name is "example.com".

  At 901, so that the lookup domain name "example.com.bot.nomserver.com" is obtained, the dot "." And the labels "bot", "nomserver", and "com" are ".bot.nomserver At .com, it is added after the identified domain name "example.com". In this example, the domain names "example.com", "bot.nomserver.com", and "example.com.bot.nomserver.com" are all resolvable domain names.

  At 902, domain name resolution is performed using the obtained domain name "example.com.bot.nomserver.com".

Queries as part of the domain resolution process may be made against a custom DNS server, hereinafter referred to as the "NOM bot server". In this example, the domain being queried is prepended to the domain name "bot.nomserver.com". The form of the query is as follows.

  At 903, the domain name "example.com.bot.nomserver.com" is resolved. In this example, the custom name server running under domain name "bot.nomserver.com" is an optional sub of domain name "bot.nomserver.com", for example "example.com.bot.nomserver.com". The domain name "example.com.bot.nomserver.com" should be resolved in order to respond to TXT resource record queries for the domain.

  At 904, it is determined whether the NOM bot has a cached record for the domain name "example.com.bot.nomserver.com". All records stored in the cache are recorded in the domain name "cache.bot.nomserver.com" as the NOM bot makes a DNS request for the domain name "example.com.bot.nomserver.com".

  If the NOM bot has the record stored in the cache for the domain name "example.com.bot.nomserver.com" as a result of the determination in 904, the record stored in the cache is subsequently returned.

  If, as a result of the determination at 904, the NOM bot does not have a cached record for the domain name "example.com.bot.nomserver.com", then at 905, the NOM bot notifies the NOM bot lookup And make an HTTP request to the domain name "example.com" on port 80. The NOM bot downloads all of the HTML content on the home page and stores the downloaded HTML content in the variable "html_content". The NOM bot constructs an array from the internal links found on the home page.

  At 906, it is determined whether any of the links in the array appear to lead to potential contact pages.

  If, as a result of the determination at 906, it appears that some of the links in the array may lead to a potential contact page, then NOM bots at 907 against the potential contact page Make an HTTP request, download HTML content from those pages, and add the downloaded content to the variable "html_content".

  If any of the links in the array do not appear to lead to a potential contact page as a result of the determination at 906, or if such a page is identified, download from the potential contact page In addition to the added content, the NOM bot at 908 processes the content of the variable "html_content" to find contact information, using pattern matching and / or regular expressions.

  At 909, it is determined whether any contact information is found in the variable "html_content".

  If no contact information is found as a result of the determination in 909, predetermined actions are taken in 910. In this example, the predetermined action is to return an error.

  If the contact information is found as a result of the determination in 909, the contact information is then recorded as a NOM record in 911 and recorded in the NOM bot cache. The NOM record is returned in the following 912.

In this example, the response is of the form:

  In this example, the response includes the domain name "example.com.bot.nomserver.com". The label "bot" of this domain name indicates that the response contains data generated using the NOM record. Thus, the label "bot" is data indicating that the NOM record was generated using automated contact information parsing techniques.

  In this example, items 901, 902, and 904 are performed by the NOM interrogator on the user device. In this example, item 903 is performed by DNS. In this example, items 905-912 are executed by the NOM bot server.

  The NOM Bot DNS Query technology allows queries to be cached at two levels. Queries can be initially cached as part of a broader DNS system. The queries can be stored secondarily in the NOM bot cache. These are DNS zones recorded in the domain name "cache.bot.nomserver.com". In addition to the independent NOM domain name lookup and the host NOM domain name lookup, performing this NOM bot lookup will require one additional DNS query.

  Referring to FIG. 10, a flow chart illustrating an example of a method of processing data is shown. The method according to this example relates to NOM bot lookup in the form of an application programming interface (API) call.

  At 1000, a domain name is identified. In this example, the domain name is "example.com".

At 1001, an API call is made using JavaScript Object Notation (JSON). The API provides a way for an application, in this example a NOM interrogator, to communicate with other applications, in this example a NOM bot server, using a defined set of commands. In this example, the API contains a set of HTTP request messages, as well as a definition of the structure of the response message. In this example, the information is sent and received in JSON format. An example of an API call that can be made is as follows.

  At 1002, the NOM bot makes an HTTP request on port 80 to the domain name "example.com". The NOM bot downloads all of the HTML content on the home page and stores the HTML content in the variable "html_content". The NOM bot builds an array out of the internal links found on the home page.

  At 1003, it is determined if any of the links in the array appear to be likely to lead to potential contact pages.

  If, as a result of the determination at 1003, it appears that some of the links in the array may lead to potential contact pages, then NOM bots at 1004 for potential contact pages Make an HTTP request, download HTML content from those pages, and add the downloaded content to the variable "html_content".

  If any of the links in the array do not look like a potential contact page as a result of the determination at 1003, or if such a page is identified, the addition of content downloaded from the potential contact page Continuing, at 1005, the NOM bot processes the content of the variable "html_content" using pattern matching and / or regular expressions to find contact information.

  At 1006, it is determined whether any contact information is found in the variable "html_content".

  If the contact information is not found as a result of the determination at 1006, predetermined action is taken at 1007. In this example, the predetermined action is to return an error.

  If the contact information is not found as a result of the determination in 1006, the contact information is subsequently recorded as a NOM record in 1008 and is recorded in the NOM bot cache. The NOM record is then returned at 1009.

In this example, an example response from the NOM bot server may have the following format and content.

  In this example, items 1000 and 1001 are performed by the interrogator on the user device. In this example, items 1002-1009 are executed by the NOM bot server.

  Referring to FIG. 11, a flowchart illustrating an example of a method of processing data is shown. The method according to this example relates to NOM bot lookup in the form of client side NOM bot lookup.

  At 1100, a domain name is identified. In this example, the domain name is "example.com".

  At 1101, the NOM interrogator initiates client-side HTML download and parsing.

  At 1102, the NOM Interrogator makes an HTTP request at port 80 to the domain name "example.com". The NOM Questioner downloads all of the HTML content on the home page, and stores the HTML content in the variable "html_content". The NOM Interrogator builds an array out of the internal links found on the home page.

  At 1103, it is determined whether any of the links in the array appear to be likely to lead to potential contact pages.

  If, as a result of the determination at 1103, it appears that some of the links in the array may lead to potential contact pages, then NOM interrogator at 1104 continues to the potential contact pages. Make an HTTP request, download HTML content from those pages, and add the downloaded content to the variable "html_content".

  If any of the links in the array do not look like a potential contact page as a result of the determination at 1103, or if such a page is identified, the potential contact page Following the addition of the downloaded content, at 1105 the NOM Interrogator processes the content of the variable “html_content” using pattern matching and / or regular expressions to find contact information.

  At 1106, it is determined whether any contact information is found in the variable "html_content".

  If no contact information is found as a result of the determination at 1106, predetermined actions are subsequently taken at 1107. In this example, the predetermined action is to return an error.

  If the determination at 1106 results in contact information being found, then at 1008, the contact information is formatted as a NOM record. The NOM record is then returned 1109.

  At 1110, the NOM record is recorded in the NOM bot cache.

  In some instances, NOM record data from a user device will be trusted only when the same data has been collected by a predetermined number of independent users, eg, twenty.

  Referring to FIG. 12, a flow chart of an example of a method of processing data is shown. The method according to this example is associated with adding and editing NOM records at the NOM server.

  In this example, a web interface is provided for the domain administrator to add a new host NOM record or to modify its existing host NOM record. When editing a host NOM record, a domain administrator can not only edit or delete existing contact methods but also add new contact methods. In some instances, the host NOM record is automatically published when it is compiled and contains new contact information.

  In some instances, the server is configured to perform at least a portion of an automatic authentication process to allow some or all of the contact information of one or more resource records associated with the domain to be modified. Ru. When performing at least part of the automatic authentication process, this may also include receiving login details via the administrator web application and collating the received login details with the details recorded in the record. Good.

  The pre-registered domain administrator is asked to authenticate by providing a username and password to log into the NOM server's web interface and make changes. In some instances, a domain administrator who has not yet registered accepts an automatic call to the telephone number shown on the homepage or contact page of a website hosted on the domain that the domain administrator is attempting to register You are asked to prove your authority by The domain administrator is asked to enter the security code provided to the call recipient on the provided web page. In some instances, domain administrators can also prove authority by adding HTML comments containing random strings to their home page.

  At 1200, the requesting domain administrator requests a change to the NOM record for the domain name.

  At 1201, it is determined whether the requesting domain administrator has already been authenticated for the domain.

  If it is determined in 1201 that the requesting domain administrator has already been authenticated for the domain, then in 1202 a username and password are required.

  At 1203, it is determined whether the username and password are correct.

  If it is determined in 1203 that the username and password are not correct, predetermined actions are taken in 1204. In this example, the predetermined action is an error message. An example of an error message is "login failure".

  If it is determined at 1203 that the username and password are correct, then at 1205, changes to the NOM record are allowed.

  If the result of the determination at 1201 is that the requesting domain administrator has not yet been authenticated for the domain, it is subsequently determined at 1206 whether any domain administrator has already been authenticated for the domain.

  If it is determined at 1206 that the domain administrator has already been authenticated for the domain, then at 1207, the domain administrator already authenticated for the domain is notified.

  At 1208, it is determined whether a domain administrator who has already been authenticated for the domain has approved or rejected the request within a given time period. In this example, the given period is 72 hours.

  If at 1208 it is determined that a domain administrator who has already been authenticated for the domain has approved the request, then at 1205 changes to the NOM record are allowed.

  If at 1208 it is determined that a domain administrator who has already been authenticated for the domain has rejected the request, then at 1209 predetermined actions are taken. In this example, the predetermined action comprises displaying an error message. For example, the error message may be "authentication rejection".

  If it is determined at 1208 that the domain administrator who has already been authenticated for the domain has not taken action within the 72 hour period, then, at 1210, the domain administrator making the request has its authority over the domain. Are required to establish the

  Similarly, if it is determined at 1206 that the domain administrator has not yet authenticated to the domain, then, at 1210, the requesting domain administrator is required to establish authority to the domain.

  At 1211, it is determined whether the requesting domain administrator has established authority over the domain.

  If it is determined at 1211 that the new domain administrator has established authority over the domain, then at 1205 changes to the NOM record are allowed.

  If it is determined at 1211 that the requesting domain administrator has not established authority over the domain, then predetermined actions are taken. In the example, the predetermined action is to display an error message. For example, the message is "authentication failure".

  In the example described below, the NOM framework can also be used to search for brands and / or keywords by converting the brands and / or keywords into domain names as an initial procedure. In the example described below, the company name "Smith & Sons" is used as an example. In this example, Smith & Sons operates the website "smithandsons.co.uk", providing double glazing throughout the United Kingdom.

  Brand search can be performed in two different ways. The NOM interrogator can perform searches within the NOM framework, or the NOM interrogator can convert the brand into the domain itself.

  Referring to FIG. 13, a flow chart of an example of a method of processing data is shown. The method according to this example is associated with brand searching within the NOM framework. In this example, the user can search using the term "Smith & Sons" instead of "smith and sons. Co. Uk".

  At 1300, at least one data string is identified. In this example, the data string "Smith & Sons" is identified. In this example, the data string is associated with the brand. A lookup domain name is created. In this example, one or more lookup domain name rules are used to create a lookup domain name. In this example, spaces in the data string are replaced with hyphens. In this example, the ampersand character "&" is replaced with the word "and".

  In this example, the variable "record_number" is initially set to the value "1" if it is currently blank. In this example, the lookup domain name is prefixed with "<< record_number >>" which is the current value of the variable "record_number". In this example, the current value of the variable "record_number" is "1".

  In this example, the domain name "brand. << user_country >>. Nomquery.com" is added after the lookup domain name. The domain name "brand. << user_country >>. Nomquery.com" includes four labels: "brand", "<< user_country >>", "nomquery", and "com". The variable “user_country” indicates, for example, the country associated with the user, such as the country where the user is currently located. << user_country >> indicates the current value of the variable “user_country”. In this example, the user is currently in the United Kingdom, so the current value of the variable "user_country" is "uk".

  In this example, the created domain name is "l. Smith-and-sons. Uk. Brand. Nomquery. Com".

  At 1301, an independent NOM domain name lookup is performed. The lookup domain name used for independent NOM domain name lookup is "nomrecordlookup.l.smith-and-sons.uk.brand.nomquery.com".

  At 1302, it is determined whether the result of the independent NOM domain name lookup performed at 1301 is that a NOM record is returned.

  If NOM record is returned as a result of the determination in 1302, then NOM record is displayed in 1303.

  If the NOM record is not returned as a result of the determination at 1302, a host NOM domain name lookup is subsequently performed at 1304. The lookup domain name used for host NOM domain name lookup will be "l. Smith-and-sons. Uk. Brand. Nomquery. Com. Lookup. Nomserver. Com".

  In this example, the domain name “l.smith-and-sons.uk.brand.nomquery.com.lookup.nomserver.com”, which is the domain name used for host NOM domain name lookup, is the created domain name “l. Smith-and-sons. Uk. Brand. Nomquery. Com. In this example, the authoritative name server for the domain name "l. Smith-and-sons. Uk. Brand. Nomquery. Com. Lookup. Nomserver. Com" has the domain name "l. Smith-and-sons. Uk. It may be an authoritative name server for nomquery.com.

  At 1305, it is determined whether the result of the host NOM domain name lookup performed at 1304 is that a NOM record is returned.

  If the determination at 1305 results in a NOM record being returned, then at 1303 the NOM record is displayed.

  If the NOM record is not returned as a result of the determination at 1305, then at 1306, a NOM bot lookup is performed.

  At 1307, it is determined whether the NOM bot lookup performed at 1306 results in a NOM record being returned.

  If the determination at 1307 results in a NOM record being returned, then at 1303 the NOM record is displayed.

  If, as a result of the determination at 1307, a NOM record is not returned, then predetermined actions are taken. In this example, the predetermined action involves an error message being returned and displayed. For example, the message "NOM record not found for this brand" may be displayed.

  In this example, items 1300, 1302, 1303, 1305, 1307, and 1308 are performed by the NOM interrogator. In this example, items 1301, 1304, and 1306 involve at least one other device other than the user device in which the NOM interrogator is located.

  In the example described above with respect to FIG. 13, the following domains “nomrecordlookup.l.smith-and-sons.brand.uk.nomquery.com” (independent) and “l.smith-and-sons.brand.uk.nomquery” .Com.lookup.nomserver.com "(hosted as a backup) is queried. These domain names may be created in the NOM framework and may include NOM records for domains that match the brand. The NOM records may be copied from the relevant domain name listed as a match for the search, in this example "smithandsons.co.uk". The example described above by FIG. 13 relies on the NOM infrastructure. Other techniques implemented more independently of the NOM framework may be used, and the brand is converted to a resolvable domain name in the NOM interrogator itself, as described with respect to FIGS. 14A and 14B. May be

  Referring to FIGS. 14A and 14B, a flowchart of an example of a method of processing data is shown. The method according to this example relates to the brand to domain conversion procedure. The NOM Interrogator may perform a brand to domain conversion procedure to convert a brand to a domain name.

  At 1400, at least one data string is identified. In this example, the data string "Smith & Sons" is identified. In this example, the data string is associated with the brand.

  At 1401, all spaces are removed from the data string, and all ampersand characters "&" are replaced with the word "and". In this example, the data string "Smith & Sons" is processed in this manner to produce data string "smith and sons". In this example, the data string "smith and sons" is stored in the variable "brand_domain".

  At 1402, the value of the variable "record_number" is determined.

  If it is determined at 1402 that the value of the variable "record_number" is "1", then at 1403, the primary country domain is obtained based on the current value of the variable << user_country >>. For example, if the current value of the variable << user_country >> is "UK", the primary country domain may be "co. Uk". The primary country domain is stored as variable "brand_domain_extension".

  If it is determined in 1402 that the value of the variable “record_number” is “2”, then in step 1404, the variable “brand_domain_extension” is set as “.com”.

  At 1405, the values of variable "brand_domain" and variable "brand_domain_extension" are combined. As a result, for example, domain names "smith and sons. Co. Uk" and "smith and sons. Com" are obtained. In this example, "smith and sons. Co. Uk" and "smith and sons. Com" are domains resulting from the NOM brand through the domain conversion procedure.

  At 1406, an independent NOM domain name lookup is performed. In this example, the lookup domain names used for independent NOM domain name lookup are "nomrecordlookup.smithandsons.co.uk" and "nomrecordlookup.smithandsons.com". In this example, an independent NOM domain name lookup is performed on one of these domain names at a time, based on the current value of the variable "record_number". For example, when the value of 'record_number' is' 1 ', the domain name' nomrecordlookup.smithandsons.co.uk 'is used, and when the value of' record_number 'is' 2', the domain name 'nomrecordlookup.smithandsons. "com" is used. In another example, independent NOM domain name lookups for both "nomrecordlookup.smithandsons.co.uk" and "nomrecordlookup.smithandsons.com" are performed in parallel.

  At 1407, it is determined whether the result of the independent NOM domain name lookup performed at 1406 is that a NOM record is returned.

  If the result of the determination at 1407 is that a NOM record is returned, then at 1408, the NOM record is displayed.

  If a NOM record is not returned as a result of the determination at 1407, then a host NOM domain name lookup is performed at 1409. In this example, the lookup domain names used for the host NOM domain name lookup are "smithandsons.co.uk.lookup.nomserver.com" and "smithandsons.com.lookup.nomserver.com".

  In this example, the domain names used for host NOM domain name lookups, namely "smithandsons.co.uk.lookup.nomserver.com" and "smithandsons.com.lookup.nomserver.com" are each domain name "smithandsons." Includes .co.uk and smithandsons.com. In this example, the authoritative name server for the domain name "smithandsons.co.uk.lookup.nomserver.com" is different from the authoritative name server for the domain name "smithandsons.co.uk", but the domain name "smithandsons.com.lookup" The authoritative name server for ".nomserver.com" is different from the authoritative name server for the domain name "smithandsons.com".

  At 1410, it is determined whether the host NOM domain name lookup performed at 1409 results in a NOM record being returned.

  If the determination at 1410 results in a NOM record being returned, then at 1408 the NOM record is displayed.

  If, as a result of the determination at 1410, a NOM record is not returned, then at 1411 a NOM bot lookup is performed.

  At 1412, it is determined whether the NOM bot lookup performed at 1410 results in a NOM record being returned.

  If NOM record is returned as a result of the determination in 1412, then NOM record is displayed in 1408. The user can use the record navigator at the user device to navigate the returned ROM records. As the user navigates between the first NOM record and the second NOM record, the variable "record_number" is incremented by 14 at 1413 and the desired NOM record is displayed.

  If the NOM record is not returned as a result of the determination at 1412, then a predetermined action is taken. In this example, the predetermined action involves an error message being returned and displayed. For example, the message "NOM record not found for this domain name" may be displayed.

  Referring to FIG. 15, a flowchart of a method of processing data is shown. The method according to this example is associated with a keyword search. In this example, the user can use the string "Double Glazing" to perform a keyword search. In this example, there is only one way to perform a keyword search within the NOM framework, as there is no reliable way for the NOM Interrogator to translate keywords into domain names. Companies may be allowed to list their domain names under keywords.

  At 1500, at least one data string is identified. In this example, the data string "Double Glazing" is identified. In this example, a data string is associated with one or more keywords. A lookup domain name is created. In this example, one or more lookup domain name rules are used to create a lookup domain name. In this example, every space in the data string is replaced with a hyphen. In this example, every ampersand character "&" in the data string is replaced with the word "and".

  In this example, the variable "record_number" is initially set to the value of "1" if it is currently blank. In this example, the lookup domain name is preceded by "<< record_number >>" which is the current value of the variable "record_number". In this example, the current value of the variable "record_number" is "1".

  In this example, the domain name "keyword. << user_country >>. Nomquery.com" is added after the created domain name. The domain name "keyword. << user_country >>. Nomquery.com" includes four labels: "keyword", "<< user_country >>", "nomquery", and "com". The variable “user_country” indicates a country associated with the user, for example, the country where the user is currently located. << user_country >> indicates the current value of the variable “user_country”. In this example, the user is currently in the United Kingdom, so the current value of the variable "user_country" is "uk".

  In this example, the created domain name is "l.double-glazing.uk.keyword.nomquery.com".

  At 1501, an independent NOM domain name lookup is performed. In this example, the lookup domain name for independent NOM domain name lookup is "nonrecordlookup.l.double-glazing.uk.keyword.nomquery.com".

  At 1502, it is determined whether the result of the independent NOM domain name lookup performed at 1501 is that a NOM record is returned.

  If NOM record is returned as a result of determination at 1502, NOM record is displayed at 1503.

  If NOM record is not returned as a result of determination at 1502, host NOM domain name lookup is subsequently performed at 1504. In this example, the lookup domain name for host NOM domain name lookup is "l.double-glazing.uk.keyword.nomquery.com.lookup.nomserver.com".

  In this example, the domain name "l.double-glazing.uk.keyword.nomquery.com.lookup.nomserver.com" used for host NOM domain name lookup is the created domain name "l.double-glazing" Contains ".uk.keyword.nomquery.com". In this example, the authoritative name server for the domain name "l.double-glazing.uk.keyword.nomquery.com.lookup.nomserver.com" is the domain name "l.double-glazing.uk.keyword.nomquery.com" It may be an authoritative name server for

  At 1505, it is determined whether the host NOM domain name lookup performed at 1504 results in a NOM record being returned.

  If NOM record is returned as a result of determination at 1505, NOM record is displayed at 1503.

  If, as a result of the determination at 1505, a NOM record is not returned, then, at 1506, a NOM bot lookup is performed.

  At 1507, it is determined whether the NOM bot lookup performed at 1506 results in a NOM record being returned.

  As a result of the determination in 1507, if the NOM record is returned, the NOM record is continuously displayed in 1503.

  If, as a result of the determination at 1507, the NOM record is not returned, predetermined actions are subsequently taken. In this example, the predetermined action involves an error message being returned and displayed. For example, the message "NOM record not found for this keyword" may be displayed.

  In this example, items 1500, 1502, 1503, 1505, 1507, and 1508 are performed by the NOM interrogator. In this example, items 1501, 1504, and 1506 involve at least one other device other than the user device in which the NOM interrogator is located.

  In the above example, the following domains "nomrecordlookup.l.double-glazing.uk.keyword.nomquery.com" (independent) and "l.double-glazing.keyword.uk.nomquery.com.lookup.nomserver.com" It is queried (hosted as a backup). These domains contain NOM records for domains that match this keyword. These ROM records may be copied from the relevant domain, which in this example is "smithandsons.co.uk", listed as a match for the search.

  If it is unclear to the NOM interrogator whether the search query entered by the user is a keyword or a brand, the NOM interrogator can perform a "string" search. This is a combined search of brand and keywords, which uses the domain name "<< record_number >>. << search_text >>. String. << country >>. Nomquery.com" to query Except that it works the same as the brand search and keyword search described above. The domain name includes six labels: "<< record_number >>", "<< search_text >>", "string", "<< country >>", "nomquery", and "com". In this example, << search_text >> is a placeholder for the text entered by the user on the user device.

  Referring to FIG. 16, a flowchart of a method of processing data is shown. The method according to this example is associated with a method and keyword search. Using the method and the keyword search, for example, “Facebook is used to indicate that the user is a company offering double glass and only wants a NOM record for a company that can be contacted via Facebook. You can search for contact methods and keywords such as (trademark) and "Double Glazing".

  At 1600, at least one data string is identified. In this example, the first data string "fb" is identified. In this example, "fb" represents Facebook (trademark). In this example, the string "fb" is associated with the variable "method" for one or more methods that the user wishes to contact with another entity. Thus, in this example, the user indicates that the user wants to use Facebook (TM) and contact another entity.

  In this example, a second data string "Double Glazing" is identified. In this example, the string "Double Glazing" is associated with the variable "keyword".

  At 1601, a lookup domain name is created. In this example, one or more lookup domain name rules are used to create a lookup domain name. In this example, every space in the keyword data string is replaced with a hyphen. In this example, every ampersand character "&" in the keyword data string is replaced with the word "and". In this example, the string << keyword >>. << method >> is obtained.

  In this example, the variable "record_number" is initially set to the value "1" if it is currently blank. In this example, the lookup domain name is preceded by "<< record_number >>" which is the current value of the variable "record_number". In this example, the current value of the variable "record_number" is "1".

  In this example, the domain name "method-kw. << user_country >>. Nomquery.com" is added after the created domain name. The domain name "method-kw. << user_country >>. Nomquery.com" includes four labels: "method-kw", "<< user_country >>", "nomquery", and "com". The variable “user_country” indicates, for example, the country associated with the user, such as the country where the user is currently located. << user_country >> indicates the current value of the variable “user_country”. In this example, the user is currently in the United Kingdom, so the current value of the variable "user_country" is "uk".

  In this example, the created domain name is "l.double-glazing.fb.uk.method-kw.nomquery.com".

  At 1601, an independent NOM domain name lookup is performed. In this example, the lookup domain name for the independent NOM domain name lookup is “nomrecordlookup.l.double-glazing.fb.uk.method-kw.nomquery.com”.

  At 1602, it is determined whether the result of the independent NOM domain name lookup performed at 1601 is that a NOM record is returned.

  If NOM record is returned as a result of the determination in 1602, NOM record is continuously displayed in 1603.

  If the determination at 1602 results in a NOM record not being returned, then at 1604 a host NOM domain name lookup is performed. In this example, the lookup domain name used for host NOM domain name lookup is "l.double-glazing.fb.uk.method-kw.nomquery.com.lookup.nomserver.com".

  At 1605, it is determined whether the host NOM domain name lookup performed at 1604 results in a NOM record being returned.

  If the result of the determination at 1605 is that a NOM record is returned, then at 1603 the NOM record is displayed.

  If, as a result of the determination at 1605, a NOM record is not returned, then, at 1606, a NOM bot lookup is performed.

  At 1607, it is determined whether the NOM bot lookup performed at 1606 results in a NOM record being returned.

  If the determination at 1607 results in a NOM record being returned, then at 1603 the NOM record is displayed.

  If, as a result of the determination at 1607, a NOM record is not returned, predetermined actions are subsequently taken. In this example, the predetermined action involves an error message being returned and displayed. For example, the message "This method + NOM record not found for keyword" may be displayed.

  In this example, items 1600, 1602, 1603, 1605, 1607, and 1608 are performed by the NOM interrogator. In this example, items 1601, 1604, and 1606 involve at least one other device other than the user device on which the NOM interrogator is located.

  Referring to FIGS. 17A and 17B, a flowchart of a method of processing data is shown. The method according to this example is associated with a search performed by the NOM interrogator based on domain or other input data. The search function works in parallel with the process of searching users for contact information by entering a domain name. In the following example, "BrandSearch" is shown.

  At 1700, user input is received. The user input may include, for example, a domain name and / or one or more data strings.

  At 1701, it is determined whether the data entered by the user includes predetermined characters. In this example, the predetermined character is a dot (or "period") "."

  If it is determined at 1701 that the data input contains dots, then it is determined that the user input is a domain name. At 1702, an independent NOM domain name lookup is performed on the domain name entered by the user.

  At 1703, it is determined whether the result of the independent NOM domain name lookup performed at 1703 is that a NOM record is returned.

  If NOM record is returned as a result of the determination in 1703, then NOM record is displayed in 1704.

  If the result of the determination at 1703 is that a NOM record is not returned, a host NOM domain name lookup is subsequently performed at 1705.

  At 1706, it is determined whether the host NOM domain name lookup performed at 1705 results in a NOM record being returned.

  If the result of the determination at 1706 is that a NOM record is returned, then at 1704 the NOM record is displayed.

  If, as a result of the determination at 1706, a NOM record is not returned, then at 1707, a NOM bot lookup is performed.

  At 1708, it is determined whether the NOM bot lookup performed at 1707 results in a NOM record being returned.

  If the result of the determination at 1708 is that a NOM record is returned, then at 1704 the NOM record is displayed.

  If, as a result of the determination at 1708, the NOM record is not returned, predetermined actions are subsequently taken at 1709. In this example, the predetermined action involves an error message being returned and displayed. For example, the message "NOM record not found for this domain name" may be displayed.

  If it is determined at 1701 that the data input does not contain dots, then it is determined that the user input is not a domain name.

  The value of the variable "record_number" is set to "1". At 1710, a NOM brand search procedure in the framework is performed based on the current value of the variable "record_number".

  At 1711, it is determined whether the NOM brand search procedure in the framework performed at 1710 results in a NOM record being returned.

  If it is determined at 1711 that the NOM brand search procedure in the framework performed at 1710 returns a NOM record, then at 1704 the NOM record is displayed.

  If at 1711 it is determined that the NOM brand search procedure in the framework performed at 1710 does not return a NOM record, then at 1712 predetermined actions are taken. In this example, the predetermined action comprises returning an error message.

  If the user wishes to navigate through multiple NOM records via the interrogator's record navigator function, for example by selecting "next" and "previous", then the value of the variable "record_number" is It is incremented by one or decremented by one.

  Referring to FIGS. 18A and 18B, an example of a hierarchical domain name system 1800 is shown. 18A-18D show how well the NOM fits in the DNS. The NOM framework is designed to conform to the DNS system and benefit from the caching and distributed nature of DNS. FIGS. 18A-18D show how well the independent NOM records, host NOM records, NOM bots, and NOM searches conform to DNS.

  Referring to FIG. 19, a block diagram of an apparatus 1900 is shown. The device is configured to process data. The apparatus 1900 may include one or more of the apparatuses 301, 302, 303, 304 described above, for example, in connection with FIG.

  Apparatus 1900 may take a variety of different forms. Examples of the format of the device 1900 include, but are not limited to, cell phone communication devices, satellite navigation systems, smart television receivers, desktop computers, laptop computers, laptop computers, servers, name servers, tablet computing devices, routers, etc. It is not a thing.

  In this example, apparatus 1900 includes one or more processors 1901 configured to process information and / or instructions. One or more processors 1901 may include a central processing unit (CPU). One or more processors 1901 are connected to the bus 1902. The operations performed by one or more processors 1901 may be performed by hardware and / or software.

  In this example, apparatus 1900 includes volatile memory 1903 usable by a computer configured to record information and / or instructions for one or more processors 1901. Volatile memory 1903 usable by the computer is connected to the bus 1902. Volatile memory 1903 usable by the computer may include random access memory (RAM).

  In this example, the apparatus 1900 includes non-volatile memory 1904 usable by a computer configured to record information and / or instructions used by one or more processors 1901. A non-volatile memory 1904 that can be used by a computer is connected to the bus 1902. Non-volatile memory 1904 that can be used by a computer may include read only memory (ROM).

  In this example, apparatus 1900 includes one or more data storage units 1905 configured to record information and / or instructions. One or more data storage units 1905 are connected to the bus 1902. One or more data storage units 1905 may include, for example, magnetic disks or optical disks and disk drives.

  In this example, device 1900 includes one or more input / output (I / O) devices 1906 configured to communicate information to one or more processors 1901. One or more I / O devices 1906 are connected to the bus 1902. One or more I / O devices 1906 may include at least one network interface. At least one network interface may allow the device 1900 to communicate via one or more data communication networks. Examples of data communication networks include, but are not limited to, the Internet, local area networks (LANs), and wide area networks (WANs). One or more I / O devices 1906 allow a user to provide input to device 1900 via one or more input devices (not shown). Examples of input devices include, but are not limited to, a keyboard and a mouse. One or more I / O devices 1906 may be enabled to provide information to the user via one or more output devices (not shown). Examples of output devices include, but are not limited to, computer monitors and display screens.

  Various other entities are illustrated for apparatus 1900. For example, operating system 1907, data processing system 1908, one or more modules 109, and data 1910, when present, may be computer usable volatile memory 1903, computer usable non-volatile memory 1904, and one or more It is shown as residing in one or a combination of data storage portions 1905. The data processing system 1908 is stored in a non-volatile memory 1904 usable by a computer, a computer readable recording medium in one or more data storage units 1905, and / or a memory in another tangible computer readable recording medium It may be implemented via computer program code.

  Although at least some aspects of the examples described herein in connection with the drawings include computer processes executed on a processing system or processor, the examples described herein may be, for example, those examples The present invention extends to computer programs, such as computer programs, present on or in a carrier that are applied to put into practice. The carrier may be any entity or device capable of implementing the program.

  It is understood that the apparatus 1900 may include more, less and / or different components than those shown in FIG.

  Various features of the NOM framework described above are described herein.

  The NOM framework may reduce the load on the network and / or enable the reduction of bandwidth costs. The first known technique for obtaining corporate contact information involves entering the corporate domain name in the address bar of a web browser on a device that can connect to the Internet, but this is per web page It is estimated that an average of approximately 2.2 Mb of data needs to be downloaded. The second known technique involves entering the company name into the search engine and clicking on the relevant list to be moved to the company domain name, which will download about 2.2 Mb of data It is estimated that it is necessary to A third known technique involves entering a company name into a search engine and finding relevant information on the results page, which is estimated to require about 50 kb of data to be downloaded Ru.

  The amount of data needed to download a regular web page based on currently available data is estimated to be over 2.2 Mb. The data size per web page is estimated to increase at a rate of about 15% each year. The data size of the search engine results page varies depending on the device and application used and the search query. Search engine applications for smartphone users and file caching reduce the amount of data needed in some cases, but the data requirements are still large compared to the amount of data needed under the NOM framework It is. Even if using the 50 kb conservative estimate needed when performing a search using the third known technique described above, by using the NOM framework to perform some searches In this example, only 512 bytes (0.512 kb) of data may be used. This is required for less than 0.025% of the data estimated to be required for the second and third known techniques described above, as well as for the third known technique described above. Less than 1% of the estimated data. With the first known technology, the second known technology, and the third known technology, often the required contact information may not be found on the first page, and the search The user may need two or more clicks to find out what information is.

  The NOM framework is designed to return contact information, rather than returning more detailed information via search engines. When the user is looking for a contact phone number, the user only needs 11 numbers, but the known technology configures the user with HTML, JavaScript and CSS included in the website Force download of thousands of bytes of data.

  The NOM framework can significantly reduce the number of people using search engines and corporate websites to obtain contact information. If all of these people find contact information using the NOM framework, this will result in a noticeable reduction of traffic on the Internet. This is particularly important when using the mobile internet.

  The cost savings of using the NOM framework will also be significant, especially for mobile Internet users. In developing countries where only the mobile Internet is the only way to connect with others, data charges can be very restrictive.

  Despite using DNS to implement the NOM framework, the NOM framework can significantly reduce the load on DNS. This is due to the way the website works and the growing trend to outsource hosting website assets. When a web page is requested, the web page uses many asset files and may be rendered. These assets may be images or style sheets for JavaScript to display presentation or syndicated advertisements or advanced features. Many of these assets are provided by external services known as content delivery networks (CDNs). For example, an example website domain1. When accessing com, the request requires a first DNS query domain1. The image is made for the com.com images that require a second DNS query. domain1. When loaded from com, CSS requires a third query css. domain1. If loaded from j.com, jQuery requires a fourth DNS query for the CDN code. jquery. If it is loaded from com, but also the ads need a fifth DNS query adsense. google. May be loaded from com. Although one website is required, the browser is doing five separate DNS queries. In contrast, less than 5 DNS queries may be required to return contact information under the NOM framework.

  Voice over IP (VoIP) has been established, and despite the fact that many companies have VoIP connectivity, companies seldom advertise VoIP numbers. The telephone infrastructure is slowly transitioning to VoIP, but typically a conventional telephone switch is used that is involved to initiate a call. Companies generally do not want to disrupt potential customers by advertising two different contact numbers. The NOM framework will allow users to call businesses using the company's domain name. The NOM framework could forward calls over VoIP when available, reducing the cost of the caller.

  The NOM framework allows people to connect to related companies in many different ways, using domain names (eg, "example.com"). For example, the user may dial the domain name "example.com" from the smartphone. The user may enter the domain name "example.com" into the GPS system (e.g. satellite navigation system or smartphone) for the exact location of the customer parking lot or the customer entrance instead of the store zip code which is often inaccurate . Users may connect through social media through the domain name "example.com". The user can view the list of connection methods simply by entering the domain name "example.com" in the NOM Interrogator application.

  As described in the several examples above, the NOM server provides domain hosting. In some instances, the NOM server records and provides host NOM records. The NOM server may be used by users who may not have the expertise or time to set up their own independent NOM records at their DNS server. In some instances, DNS records contact information in DNS TXT records for domain names (eg, example.com) in DNS zones of another domain name (eg, lookup.nomserver.com) And create a new zone containing domain contact information (eg, example.com.lookup.nomserver.com).

  The NOM server can search for brands or keywords. These are known as "search terms". Domain names can be listed under search terms in the NOM server's DNS system. This allows the NOM server to query for brands or keywords instead of just domain names. For example, the user says, Instead of searching "com", "example" or "double. You will be able to search for 'glazing'. Spaces in the search query are automatically replaced with hyphens. NOM lookups for UK users will be in the format "example.brand.uk.nomquery.com" and "double-glazing.keyword.nomquery.com".

  The domain names returned for the search are "country specific domain" (e.g., for example, example.co.uk and doubleglazing.co.uk for UK users) and "international domain" (e.g. example.com and doubleglazing. com). Also, domain names may be listed for companies holding trademarks for the correct term in the user's country. In some instances, trademarked lighting needs to be submitted by the domain owner. Companies may be allowed to pay to be listed under keywords. The results of these searches are retrieved from the DNS in the following format: "<< record_number >>. << brand >>. Brand. << user_country >>. Nomquery.com". For example, the first record number would be "1.example.brand.uk.nomquery.com" and the second record would be "2.example.brand.uk.nomquery.com".

  The NOM server can use the DNS system to search for keywords and methods. This allows the NOM server to query for companies that can be contacted about a particular subject (eg "builder") via a particular method (eg Facebook). The results of these searches are: Retrieved from DNS in the format, << record_number >>. << keyword >>. << method >>. Method-kw. << user_country >>. Nomquery.com An example of the first record is “1.builder The example of the second record would be "2.builder.fb.method-kw.uk.nomquery.com".

  As explained in some of the above examples, NOM bots automatically generate NOM records for domain names that have neither an independent NOM record on their DNS server nor a host NOM record on the NOM server It is software to make it. In some instances, contact information in the HTML content of a website hosted on a given domain name is automatically collected, and DNS. Recorded in TXT record.

  Various means (eg, methods, apparatus, and computer programs) are provided for processing data in a data communication network including a hierarchical domain name system. The authoritative name server for the first domain name receives a Domain Name System Query for the first domain name via the data communication network. The authoritative name server for the first domain name processes domain name system queries received for the first domain name. The process includes obtaining one or more resource records associated with the first domain name. The one or more resource records include contact information associated with an entity associated with a different second domain name. The authoritative name server for the first domain name sends a response to the Domain Name System Query for the first domain name over the data communication network. The response includes one or more resource records that include contact information associated with the entity associated with the second domain name. The first domain name includes a second domain name. The first domain name includes at least one label following the second domain name.

  The second domain name may be a resolvable domain name. At least one label following the second domain name may form part of a resolvable third domain name. The first domain name may include at least two labels following the second domain name. The at least two labels may include a label corresponding to the top level domain name. The at least two labels may include a second level domain name. The second domain name may include at least two labels. The second domain name may include at least three labels. The second domain name may include at least four labels. The second domain name may include at least five labels. One or more resource records may be in a zone file that describes the first domain name. One or more resource records may be recorded in a zone file that describes the first domain name. Obtaining one or more resource records associated with the first domain name may be obtained by retrieving one or more resource records associated with the first domain name from the zone file describing the first domain name It may be One or more resource records may include multiple resource records. Domain Name System queries may only include requests for TXT types of resource records. One or more resource records may be TXT type. The response to the domain name system query may include only one or more resource records. The entity may be a registrant of a second domain name. The Hierarchical Domain Name System may be Domain Name System (DNS). The contact information may include a plurality of contact identifiers associated with the entity associated with the second domain name. The additional name server may be an authoritative name server for the second domain name, and the additional name server may be different than the authoritative name server for the first domain name. Also, the authoritative name server for the first domain name may double as the authoritative name server for the second domain name. At least a portion of the auto-authentication process may be performed at the server to allow some or all of the contact information contained in the one or more resource records to be modified. The first domain name may not include a label before the second domain name.

  Various means (e.g., methods, apparatus, and computer programs) of processing data in a data communication network including a hierarchical domain name system are provided. A Domain Name System Query for the first domain name is sent over the data communication network. A response to a Domain Name System Query for the first domain name is received via the data communication network. The response includes one or more resource records that include contact information associated with an entity associated with a different second domain name. The response to the Domain Name System Query for the first domain name is processed. The process includes identifying contact information associated with the entity associated with the second domain name in one or more resource records. The first domain name includes a second domain name. The first domain name includes at least one label following the second domain name.

  The second domain name may be a resolvable domain name. At least one label following the second domain name may be part of a resolvable domain name. The first domain name may include at least two labels following the second domain name. The at least two labels may include a label corresponding to the top level domain name. The at least two labels may include a second level domain name. The second domain name may include at least two labels. The second domain name may include at least three labels. The second domain name may include at least four labels. The second domain name may include at least five labels. One or more resource records may include multiple resource records. Domain Name System queries may only include requests for TXT types of resource records. One or more resource records may be TXT type. The response to the domain name system query may include only one or more resource records. The entity may be a registrant of a second domain name. The Hierarchical Domain Name System may be Domain Name System (DNS). The contact information may include a plurality of contact identifiers associated with the entity associated with the second domain name. The additional name server may be an authoritative name server for the second domain name, and the additional name server may be different than the authoritative name server for the first domain name. Also, the authoritative name server for the first domain name may double as the authoritative name server for the second domain name. The first domain name may not include a label before the second domain name. A Domain Name System Query for the third domain name may be sent via the data communication network. A response to a Domain Name System Query for a third domain name indicating that contact information associated with the entity associated with the second domain name is not available may be received via the data communication network. The third domain name may include the second domain name. The third domain name may include at least one label preceding the second domain name. Said domain name system for a third domain name, wherein the sending of a domain name system query for the first domain name indicates that the contact information associated with the entity associated with the second domain name is not available It may be a response to receipt of a response to the query. The method may be performed by a user device.

  Hierarchical domain name system zone files are provided. The zone file of the hierarchical domain name system includes data identifying a first domain name, and contact information associated with an entity associated with a different second domain name. The first domain name may include a second domain name. The first domain name may include at least one label following the second domain name.

  The second domain name may be a resolvable domain name. At least one label following the second domain name may be part of a resolvable domain name. The first domain name may include at least two labels following the second domain name. The at least two labels may include a label corresponding to the top level domain name. The at least two labels may include a second level domain name. The second domain name may include at least two labels. The second domain name may include at least three labels. The second domain name may include at least four labels. The second domain name may include at least five labels. One or more resource records may include multiple resource records. One or more resource records may be TXT type. The entity may be a registrant of a second domain name. The Hierarchical Domain Name System may be Domain Name System (DNS). The contact information may include a plurality of contact identifiers associated with the entity associated with the second domain name. The additional name server may be an authoritative name server for the second domain name, and the additional name server may be different than the authoritative name server for the first domain name. Also, the authoritative name server for the first domain name may double as the authoritative name server for the second domain name. The first domain name may not include a label before the second domain name.

  Various means (e.g., methods, apparatus, and computer programs) are provided for processing data in a data communication network including a hierarchical domain name system. The authoritative name server for the first domain name receives a Domain Name System Query for the first domain name via the data communication network. The authoritative name server for the first domain name processes received Domain Name System queries for the first domain name. The process includes obtaining one or more resource records associated with the first domain name. The one or more resource records include contact information associated with an entity associated with a different second domain name. The authoritative name server for the first domain name sends a response to the Domain Name System Query for the first domain name over the data communication network. The response includes one or more resource records that include contact information associated with the entity associated with the second domain name. The first domain name includes a second domain name. The first domain name includes at least one label preceding the second domain name. The contact information is in plaintext format with one or more resource records, and / or one or more resource records are TXT type.

  One or more resource records may be in a zone file that describes the first domain name. One or more resource records may be recorded in a zone file that describes the first domain name. Obtaining one or more resource records associated with the first domain name may be obtained by retrieving one or more resource records associated with the first domain name from the zone file describing the first domain name It may be One or more resource records may include multiple resource records. Domain Name System queries may only include requests for TXT types of resource records. The response to the domain name system query may include only one or more resource records. The entity may be a registrant of a second domain name. The Hierarchical Domain Name System may be Domain Name System (DNS). The contact information may include a plurality of contact identifiers associated with the entity associated with the second domain name. The additional name server may be an authoritative name server for the second domain name. The additional name server may be different than the authoritative server for the first domain name. Also, the authoritative name server for the first domain name may double as the authoritative name server for the second domain name.

  Various means (e.g., methods, apparatus, and computer programs) are provided for processing data in a data communication network including a hierarchical domain name system. A Domain Name System Query for the first domain name is sent over the data communication network. A response to a Domain Name System Query for the first domain name is received via the data communication network. The response includes one or more resource records that include contact information associated with an entity associated with a different second domain name. The response to the Domain Name System Query for the first domain name is processed. The process includes identifying contact information associated with the entity associated with the second domain name in one or more resource records. The first domain name includes a second domain name. The first domain name includes at least one label preceding the second domain name. The contact information is in plaintext format with one or more resource records, and / or one or more resource records are TXT type.

  One or more resource records may be in a zone file that describes the first domain name. One or more resource records may include multiple resource records. Domain Name System queries may only include requests for TXT types of resource records. The response to the domain name system query may include only one or more resource records. The entity may be a registrant of a second domain name. The Hierarchical Domain Name System may be Domain Name System (DNS). The contact information may include a plurality of contact identifiers associated with the entity associated with the second domain name. The additional name server may be an authoritative name server for the second domain name, and the additional name server may be different than the authoritative name server for the first domain name. Also, the authoritative name server for the first domain name may double as the authoritative name server for the second domain name. The method may be performed by a user device.

  A zone file of hierarchical domain name system is provided that includes data identifying a first domain name and contact information associated with an entity associated with a different second domain name. The first domain name includes a second domain name. The first domain name includes at least one label preceding the second domain name. The contact information is in plaintext format.

  A zone file of hierarchical domain name system is provided that includes data identifying a first domain name and contact information associated with an entity associated with a different second domain name. The first domain name includes a second domain name. The first domain name includes at least one label preceding the second domain name. The contact information is in a resource record of TXT type.

  Various means (e.g., methods, apparatus, and computer programs) are provided for processing data in a data communication network including a hierarchical domain name system. A request for website content from a website associated with a domain name is sent via a data communication network. Website content is received via a data communication network. The received website content is analyzed for contact information associated with the entity associated with the domain name, using at least one automated contact information parsing technique. Contact information is recorded in the zone file.

  The Hierarchical Domain Name System may be Domain Name System (DNS). The "recording" described above may include recording the contact information in one or more resource records of TXT type in the zone file. Zone files may define additional domain names, and additional domains may be different from domain names. Parsing may include inspecting website content for links to additional website content that potentially includes the content information. A request for additional website content is sent via the data communication network in response to identifying one or more links to additional website content potentially including contact information It is also good. An inspection for contact information for additional website content may be included. The request for website content may include the domain name. The request for website content may include an HTTP GET request. Website content may include HTML content. The at least one automated contact information parsing technique may include at least one pattern matching technique. The at least one automatic contact information parsing technique may include at least one regular expression matching technique. The method may be performed at a user device. The method may be performed at a server device. The sending of the request for website content may be performed in response to receiving a request from the user device, and the request may include a domain name. The request from the user device may include an HTTP GET request. The request from the user device may include a domain name system request.

  A hierarchical domain name system zone file is provided that includes contact information associated with an entity associated with a domain name. The zone file contains data indicating that the contact information was obtained using automatic contact information parsing techniques. The data indicating that the contact information has been obtained using automated contact information parsing techniques may include a label in the domain name.

  Hierarchical domain name system zone files are provided. The zone file contains contact information associated with the entity associated with the domain name. Contact information associated with an entity associated with a domain name is included in one or more resource records of type TXT.

  The above embodiments are to be understood as illustrative examples. Additional embodiments of the invention are envisaged.

  Optional features described with respect to any one embodiment may be used alone or in combination with other features described, and any other embodiment one or more features or implementations of the embodiments. It should be understood that it may be used in any combination of any other embodiments of the forms. Furthermore, equivalents and modifications not described above may also be employed without departing from the scope of the invention, which is defined in the accompanying claims.

Claims (119)

A method of processing data in a data communication network comprising a hierarchical domain name system, in an authoritative name server for a first domain name,
Receiving a Domain Name System Query for the first domain name via the data communication network;
Processing the Domain Name System query for the received first domain name, the processing comprising obtaining one or more resource records associated with the first domain name The one or more resource records include contact information associated with an entity associated with a different second domain name;
Transmitting a response to the Domain Name System query for the first domain name via the data communication network, wherein the response is associated with the entity associated with a different second domain name Containing the one or more resource records that contain the contact information
Including
The first domain name includes the second domain name,
The first domain name includes at least one label following the second domain name,
Method. The second domain name is a resolvable domain name.
The method of claim 1. At least one label following the second domain name is part of a resolvable third domain name
A method according to claim 1 or 2. The first domain name includes at least two labels following the second domain name.
The method according to any one of claims 1 to 3. The at least two labels include a label corresponding to a top level domain name.
The method of claim 4. The at least two labels include a second level domain name.
A method according to claim 4 or 5. The second domain name includes at least two labels,
The method according to any one of claims 1 to 6. The second domain name comprises at least three labels,
The method according to any one of claims 1 to 7. The second domain name comprises at least four labels,
The method according to any one of claims 1 to 8. The second domain name comprises at least five labels,
A method according to any of the preceding claims. The one or more resource records are in a zone file that describes the first domain name,
A method according to any of the preceding claims. The one or more resource records are recorded in a zone file that describes the first domain name,
The method of claim 11. The one or more resource records associated with the first domain name comprises the one or more resource records associated with the first domain name from the zone file describing the first domain name. Done by taking out,
A method according to claim 11 or 12. The one or more resource records include a plurality of resource records,
A method according to any of the preceding claims. The Domain Name System Query contains only the request for TXT type of resource record,
A method according to any of the preceding claims. The one or more resource records are of TXT type,
The method according to any one of claims 1-15. The response to the Domain Name System Query includes only the one or more resource records,
17. A method according to any one of the preceding claims. The entity is a registrant of the second domain name,
18. A method according to any of the preceding claims. The hierarchical domain name system is a domain name system (DNS),
A method according to any of the preceding claims. The contact information includes a plurality of contact identifiers associated with the entity associated with the second domain name.
20. A method according to any of the preceding claims. The additional name server is an authoritative name server for the second domain name, and the additional name server is different from the authoritative name server for the first domain name,
21. A method according to any of the preceding claims. The authoritative name server for the first domain name doubles as the authoritative name server for the second domain name,
22. A method according to any of the preceding claims. At least a portion of an automatic authentication process is performed at the server to allow some or all of the contact information contained in the one or more resource records to be modified.
A method according to any of the preceding claims. The first domain name does not include a label before the second domain name.
24. A method according to any of the preceding claims. A method of processing data in a data communication network including a hierarchical domain name system, the method comprising:
Sending a Domain Name System Query for a first domain name via the data communication network;
Receiving a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with an entity associated with a different second domain name With contact information
Processing the response to a Domain Name System query for the first domain name, wherein the processing is associated with the entity associated with the second domain name in one or more resource records. Including identifying the contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label following the second domain name,
Method. The second domain name is a resolvable domain name.
26. The method of claim 25. At least one label following the second domain name is part of a resolvable domain name,
27. A method according to any of claims 25 or 26. The first domain name includes at least two labels following the second domain name.
28. The method of any of claims 25-27. The at least two labels include a label corresponding to a top level domain name.
29. The method of claim 28. The at least two labels include a second level domain name.
The method according to any of claims 28 or 29. The second domain name includes at least two labels,
31. A method according to any of claims 25-30. The second domain name comprises at least three labels,
32. The method of any of claims 25-31. The second domain name comprises at least four labels,
33. The method of any of claims 25-32. The second domain name comprises at least five labels,
34. The method of any of claims 25-33. The one or more resource records include a plurality of resource records,
35. The method of any of claims 25-34. The Domain Name System Query contains only the request for TXT type of resource record,
36. The method of any of claims 25-35. The one or more resource records are of TXT type,
A method according to any of claims 25-36. The response to the Domain Name System Query contains only one or more resource records,
A method according to any of claims 25-37. The entity is a registrant of the second domain name,
39. The method of any of claims 25-38. The hierarchical domain name system is a domain name system (DNS),
40. The method of any of claims 25-39. The contact information includes a plurality of contact identifiers associated with the entity associated with the second domain name.
41. The method of any of claims 25-40. The additional name server is an authoritative name server for the second domain name, and the additional name server is different from the authoritative name server for the first domain name,
42. The method of any of claims 25-41. The authoritative name server for the first domain name doubles as the authoritative name server for the second domain name,
43. The method of any of claims 25-42. The first domain name does not include a label before the second domain name.
44. The method of any of claims 25-43. Said Domain Name System query for a third domain name is sent via a data communication network;
A response to the Domain Name System Query for the third domain name indicating that the contact information associated with the entity associated with the second domain name is not available is received via the data communication network To be
Including
The third domain name includes the second domain name,
The third domain name includes at least one label preceding the second domain name.
45. The method of any of claims 25-44. The transmission of the Domain Name System Query for the first domain name indicates that the contact information associated with the entity associated with the second domain name is not available Response to the receipt of the response to the Domain Name System query for
46. The method of claim 45. Executed by the user device,
47. The method of any of claims 25-46. A method according to any of claims 1 to 46 is to be carried out,
apparatus. 47. for performing the method according to any of claims 1 to 46 when it is performed,
Computer program. The computer program according to claim 49 is recorded,
Computer readable medium. Data identifying the first domain name;
Contact information associated with an entity associated with a different second domain name,
Including
The first domain name includes the second domain name,
The first domain name includes at least one label following the second domain name,
Hierarchical domain name system zone file. The second domain name is a resolvable domain name.
52. The zone file of claim 51. At least one label following the second domain name is part of a resolvable domain name,
53. A zone file according to any of claims 51 or 52. The first domain name includes at least two labels following the second domain name.
54. A zone file according to any of the claims 51-53. The at least two labels include a label corresponding to a top level domain name.
55. The zone file of claim 54. The at least two labels include a second level domain name.
56. A zone file according to any of claims 54 or 55. The second domain name includes at least two labels,
56. A zone file according to any of claims 51-56. The second domain name comprises at least three labels,
58. A zone file according to any of claims 51-57. The second domain name comprises at least four labels,
59. A zone file according to any of claims 51-58. The second domain name comprises at least five labels,
60. A zone file according to any of claims 51-59. The one or more resource records include a plurality of resource records,
61. A zone file as claimed in any of claims 51 to 60. The one or more resource records are of TXT type,
62. A zone file as claimed in any of claims 51 to 61. The entity is a registrant of the second domain name,
73. A zone file as claimed in any of claims 51 to 62. The hierarchical domain name system is a domain name system (DNS),
A zone file according to any of the claims 51-63. The contact information includes a plurality of contact identifiers associated with the entity associated with the second domain name.
A zone file according to any of claims 51-64. The additional name server is an authoritative name server for the second domain name, and the additional name server is different from the authoritative name server for the first domain name,
66. A zone file as claimed in any of claims 51-65. The authoritative name server for the first domain name doubles as the authoritative name server for the second domain name,
70. A zone file according to any of claims 51-66. The first domain name does not include a label before the second domain name.
The zone file according to any of claims 51-67. A method of processing data in a data communication network comprising a hierarchical domain name system, in an authoritative name server for a first domain name,
Receiving a Domain Name System Query for the first domain name via the data communication network;
Processing the Domain Name System query for the received first domain name, the processing comprising obtaining one or more resource records associated with the first domain name The one or more resource records include contact information associated with an entity associated with a different second domain name;
Transmitting a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with said entity associated with said second domain name Containing the contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label preceding the second domain name,
The contact information is in plain text form in the one or more resource records, and / or the one or more resource records are in TXT type.
Method. The one or more resource records are in a zone file that describes the first domain name,
70. The method of claim 69. The one or more resource records are recorded in a zone file that describes the first domain name,
71. The method of claim 70. The obtaining of the one or more resource records associated with the first domain name is from the zone file describing the first domain name from the zone file the one or more resources associated with the first domain name Done by retrieving the record,
72. A method according to any of claims 70 or 71. The one or more resource records include a plurality of resource records,
73. The method of any of claims 69-72. The Domain Name System Query contains only the request for TXT type of resource record,
74. The method of any of claims 69-73. The response to the Domain Name System Query contains only one or more resource records,
75. The method of any of claims 69-74. The entity is a registrant of the second domain name,
76. The method of any of claims 69-75. The hierarchical domain name system is a domain name system (DNS),
77. The method of any of claims 69-76. The contact information includes a plurality of contact identifiers associated with the entity associated with the second domain name.
78. The method of any of claims 69-77. The additional name server is an authoritative name server for the second domain name, and the additional name server is different from the authoritative name server for the first domain name,
79. The method of any of claims 69-78. The authoritative name server for the first domain name doubles as the authoritative name server for the second domain name,
80. The method of any of claims 69-79. A method of processing data in a data communication network including a hierarchical domain name system, the method comprising:
Sending a Domain Name System Query for a first domain name via the data communication network;
Receiving a response to said Domain Name System query for said first domain name via said data communication network, said response being associated with an entity associated with a different second domain name One containing one or more resource records containing contact information,
Processing the response to the Domain Name System query for the first domain name, wherein the processing associates with the entity associated with the second domain name in the one or more resource records Including identifying the identified contact information;
Including
The first domain name includes the second domain name,
The first domain name includes at least one label preceding the second domain name,
The contact information is in plain text form in the one or more resource records, and / or the one or more resource records are in TXT type.
Method. The one or more resource records are in a zone file that describes the first domain name,
82. The method of claim 81. The one or more resource records include a plurality of resource records,
83. The method of any of claims 81 or 82. The Domain Name System Query contains only the request for TXT type of resource record,
84. A method according to any of claims 81-83. The response to the Domain Name System Query includes only the one or more resource records,
85. The method of any of claims 81-84. The entity is a registrant of the second domain name,
86. The method of any of claims 81-85. The hierarchical domain name system is a domain name system (DNS),
87. The method of any of claims 81-86. The contact information includes a plurality of contact identifiers associated with the entity associated with the second domain name.
89. The method of any of claims 81-87. The additional name server is an authoritative name server for the second domain name, and the additional name server is different from the authoritative name server for the first domain name,
89. The method of any of claims 81-87. The authoritative name server for the first domain name doubles as the authoritative name server for the second domain name,
90. The method of any of claims 81-89. Executed by the user device,
91. The method of any of claims 81-90. 94. A method according to any of claims 81 to 91 is to be performed,
apparatus. 92. for performing the method according to any of claims 81 to 91 when it is performed,
Computer program. 94. A computer program according to claim 93 is recorded,
Computer readable medium. Data identifying the first domain name;
Contact information associated with an entity associated with a different second domain name,
Including
The first domain name includes the second domain name,
The first domain name includes at least one label preceding the second domain name,
The contact information is in plaintext format,
Hierarchical domain name system zone file. Data identifying the first domain name;
Contact information associated with an entity associated with a different second domain name,
Including
The first domain name includes the second domain name,
The first domain name includes at least one label preceding the second domain name,
The contact information is a TXT type resource record,
Hierarchical domain name system zone file. A method of processing data in a data communication network including a hierarchical domain name system, the method comprising:
Sending a request for website content from a website associated with a domain name via the data communication network;
Receiving the website content via the data communication network;
Analyzing the received website content for contact information associated with an entity associated with the domain name using at least one automated contact information parsing technique;
Recording the contact information in a zone file;
including,
Method. The hierarchical domain name system is a domain name system (DNS),
100. The method of claim 97. The recording may include recording the contact information in one or more resource records of TXT type in the zone file.
A method according to any of claims 97 or 98. The zone file defines additional domain names, said additional domain being different from said domain name,
100. A method according to any of claims 97-99. The parsing includes examining the website content for links to additional website content that potentially includes content information.
A method according to any of claims 97-100. In response to identifying one or more links to additional website content that potentially includes contact information, a request for additional website content is sent via the data communication network,
102. A method according to any of claims 97-101. Including inspection of the contact information for additional website content,
103. The method of claim 102. The request for the website content comprises the domain name,
A method according to any of claims 97-103. The request for the website content comprises an HTTP GET request,
A method according to any of claims 97-104. The website content includes HTML,
A method according to any of claims 97-105. The at least one automatic contact information parsing technique comprises at least one pattern matching technique,
A method according to any of claims 97-106. The at least one automatic contact information parsing technique comprises at least one at least one regular expression matching technique
A method according to any of claims 97-107. Run on the user device,
A method according to any of claims 97-108. Executed on the server device
A method according to any of claims 97-108. The sending of the request for the website content is in response to receiving a request from a user device, the request comprising the domain name,
111. The method of claim 110. The request from the user device comprises an HTTP GET request,
112. The method of claim 111. The request from the user device comprises a Domain Name System request,
112. The method of claim 111. A method according to any of claims 97 to 111 is adapted to be performed,
apparatus. 112. for causing the method according to any of claims 97 to 111 to be carried out when it is carried out
Computer program. The computer program according to claim 115 is recorded,
Computer readable medium. A hierarchical domain name system zone file that contains contact information associated with an entity associated with a domain name,
The zone file contains data indicating that the contact information has been obtained using automatic contact information parsing techniques.
Hierarchical domain name system zone file. The data indicating that the contact information was obtained using the automatic contact information parsing technique includes a label in the domain name
A zone file according to claim 117. A hierarchical domain name system zone file that contains contact information associated with an entity associated with a domain name,
Contact information associated with the entity associated with the domain name is included in one or more resource records of TXT type,
Hierarchical domain name system zone file.

Images