Domain DNS

Pirehub DNS resolves a hostname across supported record types and returns a normalized view of answers, authority records, additional records, response flags, and status information.

Supported resolvers

Resolver	Request value	Behavior
Google Public DNS	`google`	Default when `provider` is omitted
Cloudflare DNS	`cloudflare`	Uses Cloudflare’s DNS-over-HTTPS JSON endpoint

Each lookup queries A, AAAA, CNAME, MX, NS, PTR, SRV, SOA, TXT, CAA, DS, DNSKEY, TLSA, NAPTR, HTTPS, and SVCB records in parallel.

Accepted input

Send a valid hostname such as example.com or www.example.com. Unlike WHOIS, the DNS endpoint does not accept a complete URL with a scheme or path.

Authentication

POST /api/v1/domain/dns accepts a Pirehub API key with the domain:dns scope for server-to-server integrations. Send the key in x-pirehub-api-key or as a bearer token. See Authentication for OAuth support and credential handling.

Lookup request

curl --request POST \
  --url https://www.ntanduy.com/api/v1/domain/dns \
  --header 'Content-Type: application/json' \
  --header 'x-pirehub-api-key: ph_live_your_public_id.your_secret' \
  --data '{"domain":"example.com","provider":"google"}'

The provider field is optional and defaults to google.

Lookup response

The following response is abbreviated; the API returns one entry in queries for every supported record type and groups matching records in sections.

{
  "success": true,
  "data": {
    "domain": "example.com",
    "provider": "google",
    "records": [
      {
        "section": "answer",
        "name": "example.com",
        "canonicalName": "example.com.",
        "normalizedName": "example.com",
        "typeCode": 1,
        "typeName": "A",
        "ttl": 300,
        "TTL": 300,
        "data": "93.184.216.34",
        "normalizedData": "93.184.216.34"
      }
    ],
    "sections": [
      {
        "section": "answer",
        "title": "Answer",
        "groups": [
          {
            "typeName": "A",
            "typeCode": 1,
            "records": [
              {
                "section": "answer",
                "name": "example.com",
                "canonicalName": "example.com.",
                "normalizedName": "example.com",
                "typeCode": 1,
                "typeName": "A",
                "ttl": 300,
                "TTL": 300,
                "data": "93.184.216.34",
                "normalizedData": "93.184.216.34"
              }
            ]
          }
        ]
      }
    ],
    "queries": [
      {
        "query": {
          "name": "example.com",
          "normalizedName": "example.com",
          "typeName": "A",
          "typeCode": 1
        },
        "status": {
          "code": 0,
          "name": "NOERROR",
          "message": "domain_info_page.dns.status_msg.ok"
        },
        "flags": {
          "tc": false,
          "rd": true,
          "ra": true,
          "ad": false,
          "cd": false
        },
        "records": [
          {
            "section": "answer",
            "name": "example.com",
            "canonicalName": "example.com.",
            "normalizedName": "example.com",
            "typeCode": 1,
            "typeName": "A",
            "ttl": 300,
            "TTL": 300,
            "data": "93.184.216.34",
            "normalizedData": "93.184.216.34"
          }
        ],
        "counts": {
          "answer": 1,
          "authority": 0,
          "additional": 0
        }
      }
    ],
    "statusSummary": {
      "status": "ok",
      "message": "domain_info_page.dns.status_msg.ok",
      "domainExists": true
    },
    "queried_at": "2026-08-11T12:00:00.000Z"
  }
}

records is deduplicated across all queries. sections contains the same records grouped for display, while queries preserves resolver status and flags for each requested record type. Status message values are stable localization keys; branch on status, name, or code instead of displaying or parsing the key directly.

Cache and DNS status

Successful resolver results are cached in memory for 60 seconds per hostname and provider. DNS outcomes such as NXDOMAIN, SERVFAIL, and REFUSED are represented in queries[].status and summarized by statusSummary. A completed NXDOMAIN lookup can still return HTTP 200; inspect statusSummary.domainExists instead of treating an empty record list as an API error.

Limits and failures

Administrator-issued API keys use the per-minute and monthly request limits configured for that key. Inspect X-ApiKey-RateLimit-* and X-ApiKey-Monthly-* response headers. First-party browser requests without an API key are limited to 30 requests per minute per IP and return X-RateLimit-* headers. Invalid hostnames or resolver values return VALIDATION_ERROR. If every resolver query fails, the endpoint returns SERVICE_UNAVAILABLE; a lookup exceeding its overall deadline returns UPSTREAM_TIMEOUT.

Next steps

DNS endpoint

Review the complete request and response schema.

Authentication

Learn about scopes and credential handling.

Errors and retries

Handle failures safely and predictably.

Subscription-backed API keys

Paid self-service keys use shared owner credits and the plan’s per-second and concurrent-job limits. Successful results, including cache hits, consume the configured action cost; errors release the reservation. Video jobs settle at completion. Inspect X-ApiKey-Credit-* and X-ApiKey-RateLimit-*. An optional Idempotency-Key prevents repeated synchronous execution/debits; repeated operations return 409 rather than replaying a response. Job starts use requestId instead. See API plans and idempotency for costs, billing periods, headers, error codes and retry rules.

Getting started

Network intelligence

Video tools

Payment utilities

Screenshot tools

Social embeds

Web data

Supported resolvers

Accepted input

Authentication

Lookup request

Lookup response

Cache and DNS status

Limits and failures

Next steps

DNS endpoint

Authentication

Errors and retries

Subscription-backed API keys

​Supported resolvers

​Accepted input

​Authentication

​Lookup request

​Lookup response

​Cache and DNS status

​Limits and failures

​Next steps

DNS endpoint

Authentication

Errors and retries

​Subscription-backed API keys

Supported resolvers

Accepted input

Authentication

Lookup request

Lookup response

Cache and DNS status

Limits and failures

Next steps

Subscription-backed API keys