dnstrace.devRun lookup

For agents and developers

Public infrastructure as JSON

The same evidence used by the interface is available through small, documented HTTP endpoints.

GET /api/dns?target=example.com&type=A GET /api/email-security?domain=example.com&selector=google GET /api/rdap?target=example.com&type=domain GET /api/tls?target=example.com GET /api/inspect?target=example.com&ip=93.184.216.34 GET /api/subdomains?domain=example.com POST /api/global-dns GET /api/my-ip GET /api/ip-privacy?ip=172.224.226.1 GET /api/providers

Machine-readable documentation

Use the OpenAPI document to generate a client or tool definition. Agents can start at llms.txt, and the complete human-readable reference is available as Markdown.

Usage expectations

Endpoints are unauthenticated during the public preview and no key or token is required. Requests made from a browser tab on this site complete a one-time Turnstile check first, which keeps the interactive tool usable without asking scripts, clients or agents to solve anything; direct API calls are governed by the rate limits alone. Each feature has a good-faith per-client limit, with a lower shared allowance for expensive live measurements. Successful public results carry short cache lifetimes and an X-DNSTrace-Cache response header. A 429 response includes Retry-After. Use a descriptive user agent, avoid repeated identical requests and cache stable results locally.