DNS Resolver List API — /api/v1/domain/dns/servers
Returns the resolver catalogue used across all DNS endpoints. Useful when building a resolver picker UI.
01 · OVERVIEW
What DNS Resolver List does
Returns the resolver catalogue used across all DNS endpoints. Useful when building a resolver picker UI.
- Method GET
- Path /api/v1/domain/dns/servers
- Stability STABLE
- Version v2026-05-15
- Summary List the public DNS resolvers accepted by the `server` parameter.
03 · RESPONSE
Response schema
All successful responses follow the standard `{ success: true, data: {...} }` envelope. Notable fields on the data object for this endpoint:
- data.<resolverName>.IP — array<string> IPv4 / IPv6 endpoints for the resolver.
- data.<resolverName>.DESC — string Short positioning copy.
- data.<resolverName>.URL — string Vendor homepage.
04 · EXAMPLE
Example response
Truncated but representative example for a real lookup:
{
"success": true,
"data": {
"Google": {
"IP": [
"8.8.8.8",
"8.8.4.4"
],
"DESC": "High performance, reliability, basic protection.",
"URL": "https://dns.google/"
},
"Cloudflare": {
"IP": [
"1.1.1.1",
"1.0.0.1"
],
"DESC": "Privacy-first, no query logs, DDoS protection.",
"URL": "https://one.one.one.one/"
},
"OpenDNS": {
"IP": [
"208.67.222.222",
"208.67.220.220"
],
"DESC": "Content filtering, parental controls.",
"URL": "https://www.opendns.com/"
},
"Quad9": {
"IP": [
"9.9.9.9",
"149.112.112.112"
],
"DESC": "Blocks known malicious domains.",
"URL": "https://www.quad9.net/"
}
}
}06 · BEST PRACTICES
Implementation tips
Patterns we recommend when integrating this endpoint:
- Hit once at app start and cache forever — list is stable across deploys.