Nameserver Details API — /api/v1/domain/ns

Returns the NS records, with optional `detailed=true` to also resolve each nameserver's A/AAAA records.

• Method GET
• Path /api/v1/domain/ns
• Stability STABLE
• Version v2026-05-15
• Summary Resolve authoritative nameservers for a domain.

Pass these as query-string parameters (or, where indicated, in the request headers). Required params marked required.

• domain (required) — string FQDN.
• detailed — boolean, default false Include IP addresses for each nameserver.

All successful responses follow the standard `{ success: true, data: {...} }` envelope. Notable fields on the data object for this endpoint:

• data.ns.result — array<string> Nameserver hostnames.
• data.ns.time — number Resolver RTT in ms.
• data.detailed — object Present only when `detailed=true` — keyed by NS hostname.

Truncated but representative example for a real lookup:

{
  "success": true,
  "data": {
    "ns": {
      "type": "NS",
      "result": [
        "ns1.google.com",
        "ns4.google.com",
        "ns2.google.com",
        "ns3.google.com"
      ],
      "time": 12,
      "host": "google.com"
    }
  }
}

Errors return HTTP status codes paired with stable machine-readable codes. Match on the code field rather than the human-readable message.

• 404 NO_NS_RECORD Domain has no NS records (likely unregistered).

Patterns we recommend when integrating this endpoint:

• Use `detailed=true` only when you need to verify NS reachability — adds 4 extra DNS queries.