Wildcard DNS
free/v1/dns/wildcardDetects wildcard DNS configuration by testing for *.domain resolution. Per RFC 4592, wildcard records match only one label level — *.example.com matches foo.example.com but NOT bar.foo.example.com. This endpoint tests this distinction and analyzes security implications.
What It Does
Tests by querying two independent cryptographically random subdomains and comparing responses. Wildcard DNS is confirmed only when both probes return matching records, preventing false positives from DNS load balancers. Determines the wildcard record type (A, AAAA, CNAME) and identifies the wildcard target.
Why It's Useful
Wildcard DNS makes NXDOMAIN-based subdomain enumeration impossible and can mask dangling CNAME vulnerabilities. Understanding wildcard configuration is a prerequisite for accurate subdomain discovery, takeover detection, and proper certificate scoping.
Use Cases
Security Assessment
During reconnaissance, detect if wildcard DNS is in use which affects subdomain enumeration techniques.
Adjust subdomain discovery methodology based on wildcard detection.
Subdomain Takeover Risk Assessment
Detect wildcard CNAME configurations pointing to third-party services. If the service is deprovisioned, ALL subdomains become vulnerable to takeover.
Identify one of the most dangerous DNS misconfigurations before attackers exploit it.
DNS Hygiene Audit
Audit domains for unintended wildcard configurations that could expose internal services.
Identify and remediate accidental wildcard DNS that increases attack surface.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | Required | The domain to check for wildcard DNSExample: example.com |
Response Fields
| Field | Type | Description |
|---|---|---|
domain | string | The queried domain |
has_wildcard | boolean | Whether wildcard DNS is detected |
wildcard_type | string | The wildcard record type: A, AAAA, CNAME, or null |
wildcard_ips | array | IPv4 addresses returned by wildcard resolution |
wildcard_ipv6s | array | IPv6 addresses returned by wildcard resolution |
wildcard_cname_target | string | CNAME target if wildcard is a CNAME record |
tested_subdomain | string | Random subdomain used for wildcard detection |
Code Examples
curl "https://api.edgedns.dev/v1/dns/wildcard" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d "domain=example.com"const response = await fetch(
'https://api.edgedns.dev/v1/dns/wildcard?domain=example.com',
{
headers: {
'Authorization': 'Bearer YOUR_API_KEY'
}
}
);
const data = await response.json();
console.log(data);import requests
response = requests.get(
'https://api.edgedns.dev/v1/dns/wildcard',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
params={
'domain': 'example.com'
}
)
data = response.json()
print(data)Read the full Wildcard DNS guide
Why it matters, real-world use cases, parameters, response fields, and how to call it from Claude, ChatGPT, or Gemini via MCP.
Read the guide →Related Endpoints
External References
Learn more about the standards and protocols behind this endpoint.
Try This Endpoint
Test the Wildcard DNS endpoint live in the playground.