Cybersecurity & Information Security

Malicious DNS Analysis: Tunneling, DGA, and Domain Anomalies

6 min readPublished: August 5, 2026

Professional visual illustration on malicious DNS analysis in Network Security Monitoring

Quick answer

Malicious DNS analysis is performed by mapping flow, timing, protocols, DNS/TLS/HTTP, and the context to the asset. A single packet or connection is partial evidence, so a sequence is built and validated against additional sources.

Network traffic provides a perspective that is not solely dependent on the endpoint. It allows identifying who communicated with whom, using what protocol, in what order, and with what volume, but requires understanding the limitations of visibility and encryption. This article focuses on malicious DNS analysis and is intended for SOC analysts and Network Analysts. The goal is to provide a working methodology that can be applied in practice, in professional interviews, and in a work environment, without settling for a dictionary definition.

The main challenge is that data is almost always incomplete. Query name, response code, and TTL can point in a direction, but their meaning depends on the time, asset, user, and expected activity. Therefore, we will structure the investigation around an investigative question, required evidence, and a clear completion criterion.

The practical scenario in the article is: analysis of a simulated dataset of queries. All examples are laboratory data or process descriptions. When dealing with Penetration Testing, Web, or Cloud, work only with explicit authorization, a defined scope, and the ability to stop the test.

DNS as an Investigation Surface

An investigation into malicious DNS analysis begins with formulating a Hypothesis: what behavior explains the finding, and what evidence will confirm or refute it. Then, expand the time window, validate the entities, and look for a sequence before and after the event.

Good correlation combines at least two types of information from query name, response code, TTL, subdomain entropy, NXDOMAIN ratio, resolver context. For each finding, state what it proves, what it does not prove, and what the next step is. If the data is insufficient, mark it as Unknown and do not turn absence of evidence into evidence of absence.

Signs of Tunneling

The topic 'Signs of Tunneling' is a central part of working on malicious DNS analysis. It is recommended to break it down into three questions: what is the input, what decision needs to be made, and what evidence is sufficient to justify it. These questions prevent automatic tool use without understanding the goal.

In practice, record the query name, response code, TTL, subdomain entropy, NXDOMAIN ratio, compare with expected behavior, and define at least one Pivot. The result should be verifiable by another analyst, including limitations and next steps.

Signs of DGA

The topic 'Signs of DGA' is a central part of working on malicious DNS analysis. It is recommended to break it down into three questions: what is the input, what decision needs to be made, and what evidence is sufficient to justify it. These questions prevent automatic tool use without understanding the goal.

Baseline and Anomalies

The topic 'Baseline and Anomalies' is a central part of working on malicious DNS analysis. It is recommended to break it down into three questions: what is the input, what decision needs to be made, and what evidence is sufficient to justify it. These questions prevent automatic tool use without understanding the goal.

Validation against Endpoint and Threat Intel

To understand the difference in the context of malicious DNS analysis, it is important to compare objectives, not just tools. One option provides breadth or speed, while another provides deep validation or context. The correct choice depends on the question: Is discovery, investigation, impact proof, containment, or reporting required?

A professional comparison table should include at least: input type, certainty level, operational cost, potential impact, limitations, and required follow-up. In case of doubt, use the least intrusive approach and add a complementary source instead of drawing too broad a conclusion.

Unique Focus Areas for Examination

For this topic, it is recommended to build a focused evidence map in advance. The central examination points are: query name, response code, TTL, subdomain entropy, NXDOMAIN ratio, resolver context. The list is not an automatic Checklist; each item is chosen because it can link an entity, action, and time or explain legitimate behavior.

query name: Define the expected value, what would be considered anomalous, and what additional source would validate the finding.
response code: Define the expected value, what would be considered anomalous, and what additional source would validate the finding.
TTL: Define the expected value, what would be considered anomalous, and what additional source would validate the finding.
subdomain entropy: Define the expected value, what would be considered anomalous, and what additional source would validate the finding.
NXDOMAIN ratio: Define the expected value, what would be considered anomalous, and what additional source would validate the finding.
resolver context: Define the expected value, what would be considered anomalous, and what additional source would validate the finding.

When one of the focus areas is unavailable, the gap must be documented and an alternative chosen. For example, if the Process identifier is not stable, one can use time, Host, User, and Parent; if the Payload is encrypted, metadata, volume, frequency, and TLS/DNS context are used.

Recommended Workflow

Define the Scope and one working question regarding malicious DNS analysis.
List the data sources and required evidence: query name, response code, TTL, subdomain entropy.
Create a short Baseline of normal behavior or expected outcome.
Perform the minimal test in a laboratory environment and save time, input, and output.
Build a Timeline or comparison table and separate facts from interpretation.
Pivot to an additional source to confirm or refute the initial explanation.
Summarize the decision, limitations, recommended action, and Retest criterion.

Practical Scenario

The chosen scenario is the analysis of a simulated Dataset of Queries. The purpose of the exercise is not to demonstrate attack capability, but to practice safe collection, comparison, and documentation. Before starting, define simulated data, time window, and expected outcome.

At the end of the exercise, a product should be submitted that another analyst or tester can review: a screenshot or export of the evidence, a short Timeline, initial hypothesis, validating evidence, limitation, and recommendation. When there is insufficient evidence, the correct conclusion is that the scenario has not been proven.

Step	What to Perform	Output
Preparation	Define Scope, time, and goal. List which fields or evidence from query name, response code, TTL are expected to appear.	Short test plan
Data Generation	Perform a safe, simulated action related to malicious DNS analysis, without real information or impact on a production system.	Controlled event/Request/Flow
Collection	Collect the raw evidence and context from an additional source. Verify Time zone, identifiers, and integrity.	Two linked pieces of evidence
Analysis	Write what each piece of evidence proves, what it does not prove, and what the possible legitimate explanation is.	Interim conclusion
Completion	Choose closure, escalation, Finding, or Tuning; add recommendation and Retest.	Documented output

Practical Checklist

Check and document: the five components of Flow.
Check and document: start time, duration, and volume.
Check and document: DNS name and TLS metadata.
Check and document: HTTP method, host, and URI when visible.
Check and document: TCP flags and stream.
Check and document: connection to Host and Process.
Specify Time zone, tool version, and collection time.
Save the raw data before filtering or modification.
Write what the finding proves and what is still unknown.
Define owner and follow-up action with a deadline.

Common Mistakes

Confusing Capture Filter with Display Filter.
Inferring content when traffic is encrypted.
Analyzing IP without DNS/TLS context.
Ignoring NAT or Proxy.
Focusing on a single Packet.
Not saving original Capture.

Summary and CTA

Malicious DNS Analysis: Tunneling, DGA, and Domain Anomalies is a topic that connects technical knowledge with work discipline. Start with a question, collect only relevant evidence, maintain context and time, and choose an action that can be justified and re-tested.

In HPI's Cybersecurity & AI track, these principles are practiced using systems, logs, and labs. A natural next step is to move on to the linked articles, perform the lab exercise, and save the output as part of a professional portfolio.

FAQ

Does malicious DNS analysis alone prove an attack or vulnerability?

No. It provides a signal or finding that requires context, validation, and an additional source. A professional conclusion relies on a sequence of evidence and consistency with expected behavior.

What to do when some data is missing?

Document the missing data, check an alternative source, and reduce the level of certainty. Do not fill in fields speculatively or present Unknown as legitimate.

How long should evidence be kept?

The retention period depends on policy, regulation, cost, and the type of event. It is important to define Retention, Legal hold, and the ability to export evidence in a verifiable format in advance.

How to practice without risking a real system?

Use virtual machines, simulated data, CTF, or a dedicated lab. In authorized tests, define Scope, Stop conditions, and backup before starting work.