Skip to main content
Guides/Threat Intelligence

DGA Heuristic Check: Understand and Use the Results

Score domain-label patterns for possible DGA output

EdgeDNS Team·Updated ·3 min read

Domain generation algorithms: recognizing patterns without assuming maliciousness

A domain generation algorithm creates domain names according to a repeatable procedure. Some malicious software uses generated names to find command infrastructure even when individual domains are blocked. Generated names can also serve legitimate purposes, including testing, tenant identifiers, and automated infrastructure.

A name-pattern check offers a way to prioritize investigation when logs contain more names than an analyst can inspect manually. It examines the name itself rather than establishing who controls the destination or what activity occurs there. A pattern score is a heuristic signal, not a probability that a domain is malicious.

Common features include:

  • Character combinations: whether adjacent letters resemble the language used by the model.

  • Vowels and digits: their proportions within the selected label.

  • Consonant runs and length: structural properties that can distinguish some generated names.

  • Parsing scope: which label is analyzed and whether public-suffix boundaries are understood.

The useful question is which names deserve a closer look. A high score does not justify blocking a customer by itself, and a low score does not establish safety. Word-based generators can resemble ordinary names; unfamiliar languages and legitimate random labels can trigger false positives.

Combine the result with observed connections, registration information, threat-feed evidence, and the context of the device making the request. Review the analyzed label when a domain uses a suffix with multiple labels. A documented triage process makes the score useful while keeping its limitations visible.

The DGA Heuristic Check endpoint, in plain language

Score domain-label patterns for possible DGA output

Prioritize suspicious names from DNS (Domain Name System) telemetry for analyst review alongside threat feeds, endpoint activity and registration history.

What is actually happening when you call it

Analyzes English bigram frequency, vowel ratio, digit ratio, consonant runs and label length without querying external threat feeds. Scores the second-to-last dot-separated label; it does not use the Public Suffix List, so multi-label suffixes such as co.uk need special care. Returns a 0–100 score and dga_likely=true at 60 or above. Legitimate random or non-English names can produce false positives.

Why this specific tool matters

Choose a task: DNS Telemetry Triage. Rank random-looking domains before investigating associated network activity.

Run the DGA Heuristic Check request below and retain the input and observed result. Before changing configuration, compare the relevant fields with the value or policy you expected. Use the DGA Heuristic Check reference to check the field definitions and supported options.

Info:

Available on the developer plan. The technical details: `GET /v1/domain/dga-check`.

When would I actually use this?

DNS Telemetry Triage

Rank random-looking domains before investigating associated network activity.

Use the finding: Use transparent pattern-matching rules features as one investigation input.

Call this endpoint through REST

This is a REST-only GET endpoint and is not registered as a tool on the dedicated MCP server. Use its documented query parameters and the request example below. See the authentication guide for API-key setup.

Tip:

The dedicated MCP server is available on every plan. Individual tool access and request limits depend on your plan. Management categories and endpoints disabled for the tool catalog are not exposed through MCP.

The technical way: call it from code

This DGA Heuristic Check request uses the example inputs from its API contract. Replace YOUR_API_KEY with a key on the developer plan or higher; adapt the target to your task.

bash
curl --request GET 'https://api.edgedns.dev/v1/domain/dga-check?domain=example.com' \
  --header "Authorization: Bearer YOUR_API_KEY"

Prepare inputs for DGA Heuristic Check

Start with the inputs below. Keep the same hostname, path, and options when comparing DGA Heuristic Check observations. The API reference contains the complete parameter contract, optional settings, and access requirements.

FieldTypeRequired?What it meansExample

domain

string

Yes

Domain to score using the label pattern-matching rules.

example.com

Interpret DGA Heuristic Check findings

Read these fields alongside the full response from your DGA Heuristic Check check. A missing value or failed lookup is different from a passing result. Keep returned errors and confidence or cache metadata when available; do not replace missing evidence with a successful default. See the complete response reference for additional fields.

FieldTypeWhat you'll see in it

domain

string

Queried domain.

dga_score

number

pattern-matching rules pattern score from 0 to 100; not a probability.

dga_likely

boolean

Whether dga_score is at least 60.

Words you might be wondering about

DNS (Domain Name System) — The internet's address book. When you type a website name, DNS turns it into the actual numeric address computers use to find each other.

Need Programmatic Access?

Automate domain intelligence with 100+ API endpoints and a free MCP server for AI integration.

DGA Heuristic Check: Results Guide | EdgeDNS