DGA Heuristic Check API
developer/v1/domain/dga-checkScores domain-label patterns associated with domain-generation algorithms using a local heuristic. A high score is a triage signal and does not establish that a domain is malicious or controlled by a botnet.
What It Does
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 It's Useful
Prioritize suspicious names from DNS telemetry for analyst review alongside threat feeds, endpoint activity and registration history.
Use Cases
DNS Telemetry Triage
Rank random-looking domains before investigating associated network activity.
Use transparent heuristic features as one investigation input.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
domain | query | string | Required | Domain to score using the label heuristic.Example: example.com |
Response Fields
Result fields below are inside the JSON data object. Any row named meta describes the sibling response metadata object. See response and error handling for status codes and error responses. Optional observations may be absent or null; inspect warnings and partial-failure fields before treating a missing result as a negative finding.
| Field | Type | Description |
|---|---|---|
domain | string | Queried domain. |
dga_score | number | Heuristic pattern score from 0 to 100; not a probability. |
dga_likely | boolean | Whether dga_score is at least 60. |
features | object | bigram_avg_score, vowel_ratio, digit_ratio, consonant_run_max and length for the analyzed label. |
recommendations | string[] | Investigation suggestions; corroborate any maliciousness claim. |
Code Examples
Replace YOUR_API_KEY with your API key. This endpoint requires the developer plan or higher; see plans and usage limits.
curl --request GET 'https://api.edgedns.dev/v1/domain/dga-check?domain=example.com' \
--header "Authorization: Bearer YOUR_API_KEY"const response = await fetch(
"https://api.edgedns.dev/v1/domain/dga-check?domain=example.com",
{
"method": "GET",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
);
if (!response.ok) {
throw new Error(`EdgeDNS returned HTTP ${response.status}`);
}
const data = await response.json();
console.log(data);import requests
response = requests.request(
'GET',
"https://api.edgedns.dev/v1/domain/dga-check?domain=example.com",
headers={'Authorization': 'Bearer YOUR_API_KEY'},
timeout=60,
)
response.raise_for_status()
data = response.json()
print(data)Read the full DGA Heuristic Check guide
Learn the concepts, choose a practical workflow, and interpret the observations from DGA Heuristic Check before acting on them. Use the documented REST request for this operation.
Read the guide →Related Endpoints
External References
Learn more about the standards and protocols behind this endpoint.