DNS lookup
Queries the chosen record types for a name and returns the answers with TTL, observation time and which public resolver answered.
Updated 2026-10-07
What this tool checks
The DNS lookup queries the record types you choose for a name: A, AAAA, CNAME, MX, NS, TXT, SOA, CAA and SRV. For each type you get the records, the TTL and whether the name exists.
The result also tells you which public resolver answered and when the answer was observed.
How to read the result
The TTL is the number of seconds the answer may be cached by others. The observed_at and fresh_until fields tell you when the answer was fetched and how long it can be used; see freshness.
Limitations
- The lookup shows what a public resolver returns. It is not a query of the authoritative servers.
- It does not follow a chain to the final address, except through the answers the resolver returns for the type you asked for.
- A recent change may not be visible yet because of caching.
Use it from code
curl -i "https://api.probekit.dev/v1/dns/lookup?name=example.com"A request without payment is answered with 402 Payment Required and the exact price. See the API reference.
Limits
| Input | Domain name, Record types |
|---|---|
| Deadline | 10 seconds |
| Freshness | Up to 5 minutes, never longer than the record TTL |
| Price | $0.005 per check |
Findings this tool can report
DNS (3)
- Error
DNS_DOMAIN_NOT_FOUNDThe DNS resolver reported that the domain does not exist. - Warning
DNS_RESOLVER_FAILUREThe DNS resolver returned a server failure. - Warning
DNS_RESOLVER_TIMEOUTThe DNS resolver did not answer in time.
Check (1)
- Warning
CHECK_QUERY_BUDGET_EXCEEDEDThe check stopped after reaching its DNS query limit.
Frequently asked questions
Which resolver answers?
A public resolver. Cloudflare is the primary. Google is used if the first request fails at transport level. The result names the resolver that answered.
Is NXDOMAIN an error?
No. It is a valid answer meaning that the name does not exist. The check returns it as a result.
Why do I see a different answer from my own resolver?
Resolvers cache answers and may be at different points in a change. Our answer comes from a public resolver at the time stated in the result.
How long are answers cached?
At most 5 minutes, and never longer than the TTL of the answer.