DNS Records
Google · Network · 1 endpoint
What Google's public resolver sees for one name — the answer status and every record of the asked type, A through CAA. An empty answer is data, not an error.
Base URL
Endpoint
Snippet
Request — cURL
v1
curl https://api.diraz.ae/v1/domains/dns/%7Bdomain%7D \
-H "Authorization: Bearer drz_live_…"Query parameters
- domainpath segment · required
- The name to resolve, e.g. `iix.web.id`.
- typestring · optional
- Record type: `A`, `AAAA`, `CAA`, `CNAME`, `MX`, `NS`, `SOA`, `SRV`, or `TXT`.Default: A
- max_ageinteger (seconds) · optional
- Ask for data no older than this. Clamped to the product's own floor, so it can narrow the window but never force a refresh on every call.Default: 300
Example response
200 OK
v1
{
"data": {
"domain": "iix.web.id",
"type": "A",
"status": "NOERROR",
"records": [
{ "name": "iix.web.id.", "type": "A", "ttl": 300, "data": "104.21.47.52" },
{ "name": "iix.web.id.", "type": "A", "ttl": 300, "data": "172.67.144.141" }
]
},
"meta": {
"request_id": "req_7Q2fK4mZ",
"as_of": "2026-08-20T04:05:00.000Z",
"age_seconds": 42,
"next_update_at": "2026-08-20T04:10:00.000Z"
}
}- domain / type
- The question, echoed back.
- status
- `NOERROR`, or `NXDOMAIN` when the name does not exist.
- records[].name / type / ttl
- One row per answer record: owner, type, and seconds it may be cached.
- records[].data
- The record's value — an address, a priority-prefixed exchange, or quoted TXT text.
Errors
401 Unauthorized
v1
{
"error": {
"code": "UNAUTHORIZED",
"message": "The API key is invalid, expired, or revoked."
},
"meta": {
"request_id": "req_7Q2fK4mZ"
}
}Every failure carries a stable machine-readable code before the human message, and the same meta.request_id the successful responses carry. Quote it and we can find your exact request.
Errors are free
Nothing on this page is billed. You are charged for a 2xx and nothing else — a rejected key, a bad parameter, a rate limit, or an outage on our side all cost you zero. Retry without watching the meter.
- UNAUTHORIZEDHTTP 401
- Missing, malformed, expired, or revoked API key.
- FORBIDDENHTTP 403
- The key is valid but lacks the scope this product needs.
- VALIDATION_ERRORHTTP 422
- A query parameter is the wrong type or out of range.
- RATE_LIMITEDHTTP 429
- Rate limit exhausted. `Retry-After` says how long to wait.
- SERVICE_UNAVAILABLEHTTP 503
- No data recent enough to serve. Carries `Retry-After`, and is never billed.
- Status
- Operational
- Category
- Network
- Scope
- market:read
- Rate limit
- 120 requests / 60s per key
- Pricing
- 1 credit / request
- DNS Records
1/1 passing
Every response is timestamped. as_of is when the data was published, age_seconds how old that is now, and next_update_at when newer data is expected.
Three shapes to handle:
- Up to date200
The data is inside its published window. The overwhelming majority of requests.
- Delayeddelayed: true
Newer data is late. You still get the most recent there is, flagged so you can decide whether to use it.
- Unavailable503
Nothing recent enough to serve. Carries Retry-After, and is never billed.