Best free DNS lookup tools
AdminKit's DNS lookup tool queries nine record types (A, AAAA, MX, TXT, NS, CAA, PTR, SOA, CNAME) through Cloudflare's resolver and explains each one in plain language; MXToolbox queries a domain's authoritative nameserver directly, Google's Dig tool offers a raw dig-style view, nslookup.io lets you pick the resolver, and intoDNS runs a configuration health check instead of a plain lookup.
AdminKit is built by Netbase JSC. AdminKit is listed below; MXToolbox, Google, nslookup.io and intoDNS are independent and not affiliated with AdminKit.
What each tool’s own page confirms
MXToolbox’s DNS Lookup, read 2026-11-04, states it “will list DNS records for a domain in priority order,” run “directly against the domain’s authoritative name server” — a near-instant read of what a zone currently publishes, rather than whatever a public resolver has cached. Its broader SuperTool page lists A, AAAA, CNAME, MX, PTR, SOA, TXT and SPF as direct lookups, with DKIM, DMARC, BIMI, MTA-STS and TLSRPT handled as separate, dedicated checks rather than folded into the plain DNS lookup. Neither page states a login requirement or a lookup cap, and both load and return results without any sign-in prompt.
Google’s Admin Toolbox Dig, read 2026-11-04, is a Google-hosted web front end to the dig command. Its own page’s record-type selector lists A, AAAA, ANY, CAA, CNAME, DNSKEY, MX, NS, PTR, SOA, SRV and TXT, and includes a “Raw View” toggle for dig-style output — the only tool in this roundup confirmed to offer that. It loads with no login prompt; its own page does not state which resolver or nameserver a plain lookup queries by default.
nslookup.io, read 2026-11-04, states on its own page that you “can select from a range of DNS servers on the result page. These include popular public DNS servers, the authoritative DNS server for the given domain, and local DNS servers all around the world” — the widest resolver choice confirmed in this roundup. It shows A, AAAA, CNAME, TXT, NS, MX and SOA by default and states it supports “all the DNS record types that are known to be in active use.” The lookup form itself needs no login; a separate “Login / Sign up” link in its own navigation covers its monitoring and REST API products, whose pricing isn’t stated on the pages read for this comparison.
intoDNS, read 2026-11-04, is a different kind of tool: its own homepage states it “checks the health and configuration and provides DNS report and mail servers report,” with “suggestions to fix and improve them.” A sample report shows pass/warn/info checks against NS delegation, glue records, SOA timing values and MX configuration, citing specific record values rather than just a pass/fail badge. It loads with no login prompt. It isn’t a pick-a-record-type lookup the way the other three tools here are — it’s a fixed configuration audit.
What AdminKit’s own tool does
AdminKit’s DNS lookup tool queries Cloudflare’s public DNS-over-HTTPS resolver through an AdminKit Pages Function for nine record types — A, AAAA, MX, TXT, NS, CAA, PTR, SOA and CNAME — with each type explained in plain language next to the result, and no raw dig-style output. It does not let you choose a different resolver or query a nameserver directly, has no public API, and runs no configuration-health audit against RFC best practice the way intoDNS does.
The honest angle
These five tools don’t all answer the same question. If you need to query a domain’s authoritative nameserver directly, or want a choice of resolver location, MXToolbox’s DNS Lookup and nslookup.io’s own pages both confirm that; AdminKit’s tool always goes through one resolver. If you want raw dig-style output across a wide set of record types including DNSSEC-adjacent ones like DNSKEY, Google’s Admin Toolbox Dig is built for that; AdminKit’s tool returns a formatted, plain-language result instead. If what you actually want to know is whether a domain’s DNS is configured correctly — not just what one record currently says — intoDNS’s health report goes further than any plain lookup tool in this roundup, AdminKit included.
What AdminKit’s tool is for is the handful of record types most people need for everyday mail and DNS troubleshooting, always through one resolver, with each one explained rather than left as raw output — see how to read a DNS lookup result for what each field actually means, and why a lookup can return different answers from different resolvers for why a tool like nslookup.io’s multi-resolver choice can show you something a single-resolver tool like AdminKit’s cannot.
For a deeper single-tool comparison against a much wider raw-dig front end, see AdminKit’s DNS lookup tool vs Dig Web Interface; for email-authentication-focused checking rather than raw record lookups, see DNSChecker vs MxToolbox; for checking which resolver your own connection uses rather than what a domain publishes, see best free DNS leak test tools.
Trademarks belong to their respective owners; AdminKit is not affiliated with MXToolbox, Inc., Google LLC, nslookup.io, or intoDNS.
| Feature | AdminKit | MXToolbox DNS Lookup | Google Admin Toolbox Dig | nslookup.io | intoDNS |
|---|---|---|---|---|---|
| Free, loads and returns a result with no login prompt | ✓ | ✓ | ✓ | ✓ | ✓ |
| Number of DNS record types a user can select | 9 (own tool page) | 8 directly (A, AAAA, CNAME, MX, PTR, SOA, TXT, SPF), plus separate DKIM/DMARC/BIMI/MTA-STS/TLSRPT checkers | 12, incl. ANY and DNSKEY, found directly in the page's own type selector | Own page: 'all DNS record types that are known to be in active use'; 7 shown by default (A, AAAA, CNAME, TXT, NS, MX, SOA) | — |
| Lets you choose which resolver or nameserver answers the query | ✗ | ✓ | — | ✓ | — |
| Raw, dig-command-style output mode | ✗ | — | ✓ | — | — |
| Flags DNS configuration problems (e.g. missing glue, SOA timing) rather than just returning records | — | — | — | — | ✓ |
| Plain-language explanation of what each record type means, shown with the result | ✓ | — | — | — | — |
| Documents a public API for scripting lookups | ✗ | — | — | ✓ | — |
AdminKit vs MXToolbox DNS Lookup
Free, loads and returns a result with no login prompt
Number of DNS record types a user can select
Lets you choose which resolver or nameserver answers the query
Raw, dig-command-style output mode
Plain-language explanation of what each record type means, shown with the result
Documents a public API for scripting lookups
AdminKit vs Google Admin Toolbox Dig
Free, loads and returns a result with no login prompt
Number of DNS record types a user can select
Lets you choose which resolver or nameserver answers the query
Raw, dig-command-style output mode
Plain-language explanation of what each record type means, shown with the result
Documents a public API for scripting lookups
AdminKit vs nslookup.io
Free, loads and returns a result with no login prompt
Number of DNS record types a user can select
Lets you choose which resolver or nameserver answers the query
Raw, dig-command-style output mode
Plain-language explanation of what each record type means, shown with the result
Documents a public API for scripting lookups
AdminKit vs intoDNS
Free, loads and returns a result with no login prompt
Number of DNS record types a user can select
Lets you choose which resolver or nameserver answers the query
Raw, dig-command-style output mode
Flags DNS configuration problems (e.g. missing glue, SOA timing) rather than just returning records
Plain-language explanation of what each record type means, shown with the result
Documents a public API for scripting lookups
Frequently asked questions
Which of these tools lets me query a specific nameserver instead of a public resolver?
MXToolbox's DNS Lookup, per its own page (read 2026-11-04), runs 'directly against the domain's authoritative name server,' and nslookup.io's own page states you 'can select from a range of DNS servers on the result page,' including 'the authoritative DNS server for the given domain' and 'local DNS servers all around the world.' AdminKit's DNS lookup tool always queries Cloudflare's public DNS-over-HTTPS resolver through an AdminKit Pages Function and has no option to pick a different resolver or nameserver — see AdminKit's DNS lookup tool vs Dig Web Interface for a deeper look at that same gap against a dedicated raw-dig tool.
Does any of these tools show raw, dig-command-style output?
Google's Admin Toolbox Dig does: its own page includes a 'Raw View' toggle, and its record-type selector (found directly in the page itself, read 2026-11-04) lists A, AAAA, ANY, CAA, CNAME, DNSKEY, MX, NS, PTR, SOA, SRV and TXT. AdminKit's DNS lookup tool, MXToolbox's DNS Lookup and nslookup.io all return a formatted, non-raw result instead; whether MXToolbox's own page supports a raw output mode is not stated either way, so that point is marked unverified for it rather than assumed.
Is intoDNS really a DNS lookup tool, or something else?
Something broader. Per its own homepage, intoDNS 'checks the health and configuration and provides DNS report and mail servers report,' with 'suggestions to fix and improve them.' Its sample report (read 2026-11-04) flags NS, SOA, MX and glue-record issues with pass/warn/info status against DNS best practice, rather than letting you pick a record type and see the raw value the way the other four tools here do. It's included because it answers a related but different question — 'is this domain's DNS configured correctly' rather than 'what does this one record say' — and is named here for that reason, not ranked against the others as a like-for-like lookup tool.
AdminKit already has pages comparing its DNS lookup to one other tool — why a third comparison?
Those two pages answer narrower questions. AdminKit's DNS lookup tool vs Dig Web Interface is a one-on-one deep dive against a single, much broader raw-dig front end; DNSChecker vs MxToolbox compares two email-authentication-and-blacklist-focused services against each other, not primarily as record-lookup tools. This page is the wider category roundup: how AdminKit's lookup stacks up against four more of the most-used free DNS lookup/report tools side by side. For DNS resolver/leak testing specifically — which resolver your own connection uses, a different question from looking up a domain's published records — see AdminKit's best free DNS leak test tools comparison instead; nothing here repeats that page's ground.
Why isn't dnschecker.org included in this roundup?
Every automated, read-only attempt to load dnschecker.org's own pages for this comparison, run 2026-11-04, returned an HTTP 403 block, the same result already on record from AdminKit's DNSChecker vs MxToolbox comparison. Rather than guess at its current DNS-lookup-specific feature set from memory, it's left out of this page's table entirely; that existing comparison page (verified 2026-10-26 from DNSChecker's own indexed pages) already covers what can be confirmed about it.
Does this page use MXToolbox's, Google's, nslookup.io's or intoDNS's logo or brand assets?
No. All four names are used only to identify and compare publicly available services (nominative use). AdminKit is not affiliated with or endorsed by MXToolbox, Inc., Google LLC, nslookup.io, or intoDNS.
Want AdminKit to watch this for you?
Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.