# US 2012/0254398 A1 · Traffic Like NXDomains

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254398 A1
- Document ID: US20120254398A1
- Status: Published application
- Kind: A1
- Application number: 13/076,633
- Filed: 2011-03-31
- Published: 2012-10-04
- Earliest claimed: 2011-03-31
- Assignees: VeriSign, Inc.
- Inventors: Matthew Thomas
- Web page: https://patentgrep.com/patent/US20120254398A1

## CPC

- H04L 43/06: Generation of reports
- H04L 61/4511: using domain name system [DNS]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods and systems for analyzing network traffic related to domain names, including Non-Existent Domain names, comprise: storing network traffic data associated with DNS requests for NXDs; receiving an analysis request associated with a domain name; creating, based on the stored network traffic data, an NXD list comprising NXDs that received at least one DNS request during a specified time period; computing, based on the stored network traffic data, a similarity metric for each NXD listed in the NXD list; and providing an analysis report identifying potentially valuable NXDs based on the computed similarity metrics.

## Claims

### Claim 1

A computer-implemented method of analyzing network traffic related to domain names, comprising:
storing network traffic data associated with DNS requests for NXDs;
receiving an analysis request associated with at least one identified domain name;
creating, based on the stored network traffic data, an NXD list comprising NXDs that received at least one DNS request during a time period;
computing, based on the stored network traffic data, a similarity metric for each NXD listed in the NXD list; and
providing an analysis report identifying potentially valuable NXDs based on the computed similarity metrics.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
observing network traffic data associated with DNS requests;
identifying the type of domain associated with the DNS requests;
partitioning the stored network traffic data according to the identified type of domain associated with the DNS request.

### Claim 3 (depends on 1)

The method of claim 1, wherein the stored network traffic data is partitioned by at least one of the last name server making the DNS request or the time the DNS request was made.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
sorting NXDs listed in the analysis report based on the computed similarity metrics; and
removing NXDs listed in the analysis report associated with similarity metrics below a threshold value.

### Claim 5 (depends on 1)

The method of claim 1, wherein the traffic data comprises at least the IP addresses of the last name servers making the DNS requests and the times each DNS request occurred.

### Claim 6 (depends on 1)

The method of claim 1, wherein a root name server for a top-level domain stores the network traffic data.

### Claim 7 (depends on 1)

The method of claim 1, wherein the time period includes a time period that the at least one identified domain name was an NXD.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
filtering the stored network traffic data to remove network traffic data associated with machine-generated activity;

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
comparing the computed similarity metric for each NXD to a metric associated with the DNS traffic of the at least one identified domain name when the at least one identified domain name was an NXD;
selecting a subset of the NXD list based on the comparison; and
wherein the analysis report comprises the selected subset and the computed similarity metrics associated with NXDs of the selected subset.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
prioritizing the list of NXDs based on the similarity metrics.

### Claim 11 (depends on 1)

The method of claim 1, wherein the similarity metrics are computed in response to the analysis request and represent the similarity of each NXD relative to the at least one identified domain name.

### Claim 12 (depends on 1)

The method of claim 1, wherein the similarity metrics are pre-computed as hash values depicting a DNS traffic signature of each NXD.

### Claim 13

A computer system for analyzing network traffic related to domain names, comprising:
a processing system comprising one or more processors; and
a memory system comprising one or more computer-readable media, wherein the computer readable media store instructions that, when executed by the processing system, cause the system to perform the operations of:
storing network traffic data associated with DNS requests for NXDs;
receiving an analysis request associated with at least one identified domain name;
creating, based on the stored network traffic data, an NXD list comprising NXDs that received at least one DNS request during a time period;
computing, based on the stored network traffic data, a similarity metric for each NXD listed in the NXD list; and
providing an analysis report identifying potentially valuable NXDs based on the computed similarity metrics.

### Claim 14 (depends on 13)

The system of claim 13, wherein the computer-readable media further stores instructions for:
observing network traffic data associated with DNS requests;
identifying the type of domain associated with the DNS requests; and
partitioning the stored network traffic data according to the identified type of domain associated with the DNS request.

### Claim 15 (depends on 13)

The system of claim 13, wherein the stored network traffic data is partitioned by at least one of the last name servers making the DNS request or the time the DNS request was made.

### Claim 16 (depends on 13)

The system of claim 13, wherein the computer-readable media further stores instructions for:
sorting NXDs listed in the analysis report based on the computed similarity metrics; and
removing NXDs listed in the analysis report associated with similarity metrics below a threshold value.

### Claim 17 (depends on 13)

The system of claim 13, wherein the traffic data comprises at least the IP addresses of the last name servers making the DNS requests and the times each DNS request occurred.

### Claim 18 (depends on 13)

The system of claim 13, wherein a root name server for a top-level domain stores the network traffic data.

### Claim 19 (depends on 13)

The system of claim 13, wherein the time period includes a time period that the at least one identified domain name was an NXD.

### Claim 20 (depends on 13)

The system of claim 13, wherein the computer-readable media further stores instructions for:
filtering the stored traffic data to remove traffic data associated with machine-generated activity.

### Claim 21 (depends on 13)

The system of claim 13, wherein the computer-readable media further stores instructions for:
comparing the computed similarity metric for each NXD to a metric associated with the DNS traffic of the at least one identified domain name when the at least one identified domain name was an NXD;
selecting a subset of the NXD list based on the comparison; and
wherein the analysis report comprises the selected subset and the computed similarity metrics associated with NXDs of the selected subset.

### Claim 22 (depends on 13)

The system of claim 13, wherein the computer-readable media further stores instructions for:
prioritizing the list of NXDs based on the similarity metrics.

### Claim 23 (depends on 13)

The system of claim 13, wherein the similarity metrics are computed in response to the analysis request and represent the similarity of each NXD relative to the received domain name.

### Claim 24 (depends on 13)

The system of claim 13, wherein the similarity metrics are pre-computed as hash values depicting a DNS traffic signature of each NXD.
