All tools

DNS Lookup

Network

Look up DNS records (A, AAAA, MX, TXT, NS, CNAME and more) via DNS-over-HTTPS

Enter a domain and a record type (A, AAAA, CNAME, MX, TXT, NS, SOA, PTR, SRV, or CAA) and see the actual DNS records back, without opening a terminal to run `dig` or `nslookup`. It queries a public DNS-over-HTTPS resolver directly from your browser rather than your local or ISP resolver, so it's genuinely live data, though that also means results can differ from what your own machine has cached, especially right after a DNS change propagates unevenly. TTL values are converted into a human-readable duration, and status codes like NXDOMAIN or SERVFAIL are labeled plainly rather than left as a raw numeric code. It's a common first stop for debugging email routing (checking MX records) or verifying SPF/DKIM setup (checking TXT records) before assuming the problem is somewhere else.

dnslookuprecordsamxtxtcname

How to use DNS Lookup

  • 1.Enter a domain and select record type (A, AAAA, MX, TXT, NS, CNAME) to see current DNS records without needing `dig` or `nslookup` installed.
  • 2.Check TXT records to verify SPF, DKIM, or domain verification strings are correctly published after a DNS change.
  • 3.Look up MX records when debugging why email isn't routing correctly to a domain's mail server.

Frequently asked questions

How does this look up DNS records without a terminal?
It queries a DNS-over-HTTPS resolver from your browser, which returns the same record data you'd get from `dig`, just over HTTPS instead of raw UDP/TCP DNS.
Will this show me my own local DNS resolver's cached results?
No, since it queries a public DoH resolver directly, results may differ slightly from what your ISP's or local DNS cache would return, especially right after a change before propagation completes.
Why do I still see old records after updating DNS?
DNS propagation depends on TTL values and caching at multiple layers — this tool shows what the resolver currently has cached, which may lag behind your authoritative nameserver's records until the TTL expires.
Is my query logged or sent anywhere besides the DNS resolver?
The domain you look up is sent to the DoH resolver to perform the query, which is necessary for any DNS lookup tool, but nothing else about your input is stored by this tool.

Use via API, SDK, or MCP

cURLcurl "https://api.utilix.tech/v1/tools/dns-lookup?domain=utilix.tech&type=A" \
  -H "Authorization: Bearer utx_live_..."
# Free: 1,000 req/day · Pro: 10,000 req/day

Get an API key from your dashboard · Full API docs →