codynet

DNS

DNS Lookup Tool

Free online DNS lookup tool. Check A, AAAA, MX, NS, TXT, CNAME, SRV, and CAA records for any domain in seconds.

Query DNS

Choose a record type and resolve it through Node DNS.

Results come from deterministic DNS APIs or HTTPS RDAP endpoints.

Results

Run a lookup to see structured results here.

Practical guide

How to use the DNS lookup tool

Use this online DNS lookup tool when you need a direct answer for one record type and a readable result you can share, compare, or verify from the command line.

What this tool checks

The DNS lookup tool asks a public resolver for a specific record type — A, AAAA, CNAME, MX, NS, TXT, SRV, or CAA — on a hostname. It is the fastest way to confirm what a resolver currently returns for a domain, including records used for websites, mail routing, vendor verification, and service discovery.

When to use it

Run a DNS lookup after changing DNS at a registrar or DNS host, before launching a site, when email delivery fails, when a vendor asks you to prove a verification record is visible, or when you simply need to know which IP a hostname currently resolves to. If a record exists in your DNS control panel but this lookup does not show it, double-check the record type, hostname, and which domain you are querying.

How to read the result

A successful DNS lookup returns one or more records for the exact name and type requested. An empty answer means the record type is missing on that name (the name itself may still exist for other types). NXDOMAIN means the name does not exist at all. SERVFAIL means the resolver could not complete the query — usually unreachable authoritative servers or a DNSSEC validation failure. For packet-level detail, switch to the DIG tool.

Common errors and what they mean

Empty answer with NOERROR status means the name exists but the record type is not published — for example, querying MX on a name that has only A records. NXDOMAIN means the resolver was authoritatively told the name does not exist. SERVFAIL usually means a DNSSEC chain is broken or the authoritative servers are unreachable. If you see different answers from different resolvers, the change is propagating but caches have not all expired yet.

DNS lookup vs dig vs nslookup

This tool is the right starting point for everyday questions. The DIG tool shows you the full DNS response including flags, response codes, and TTLs — useful for troubleshooting. The NSLookup tool is the simpler interactive style familiar to Windows users. All three talk to the same public resolvers under the hood; the difference is what they show you.

Example DNS lookup

Example input
example.com A
Example result
A 93.184.216.34

An A record maps a hostname to an IPv4 address. AAAA is the equivalent record type for IPv6.

Related tools

DIG Lookup

Inspect raw DNS response details, flags, rcodes, sections, and TTLs.

Open tool

MX Lookup

Run a free MX record lookup — check MX records, priorities, and mail exchanger hostnames for any domain.

Open tool

TXT Lookup

Free TXT record lookup — check SPF, DKIM, DMARC, and verification TXT records.

Open tool

Related guides

DNS Records Explained

A practical reference for A, AAAA, CNAME, MX, TXT, NS, CAA, and the rest.

Read guide

DNS TTL Explained

How long resolvers cache an answer, and how to pick a value that ages well.

Read guide

NXDOMAIN vs SERVFAIL

Two different DNS error codes that need two different fixes.

Read guide

FAQ

What is a DNS lookup?
A DNS lookup is a query to a DNS resolver asking for a specific record type on a hostname. The resolver returns the record value (an IP, a hostname, a text string, etc.) plus its TTL. This online DNS lookup tool runs that query for you against a public resolver and shows the answer in a clean structured format.
How do I check DNS records for a domain?
Enter the domain (for example example.com), choose the record type (A, AAAA, MX, NS, TXT, CNAME, SRV, or CAA), and submit. The tool sends a live DNS query to the selected public resolver and shows you exactly what came back. No login, no rate limits, no logs of your queries.
Why does my DNS provider show a record but the lookup does not?
The most common causes are querying the wrong hostname (for example the apex when the record is on a subdomain), choosing the wrong record type, or waiting on resolver cache expiry. If the record was just changed, try the same query against another resolver with the Multi-Resolver Compare tool — if Cloudflare shows the new value but Google does not, the change is propagating but has not finished.
Which public DNS resolver should I use?
For a normal user view, leave the default resolver. Use Cloudflare (1.1.1.1) for fast neutral answers, Google (8.8.8.8) for the most-deployed view, Quad9 (9.9.9.9) for malware-filtered results, and OpenDNS for content-filtered views. The actual DNS data is the same; the difference is whose cache and policy you are seeing.
What is the difference between DNS Lookup and DIG Lookup?
DNS Lookup gives you a clean, parsed answer for one record type — fastest path to 'what does this domain resolve to?' DIG Lookup gives you the full DNS response with header flags, response codes, sections, and TTLs — what you want when something is broken and you need protocol-level detail. Same underlying data, different presentation.
Does this tool support all DNS record types?
It supports the common ones: A, AAAA, MX, NS, TXT, CNAME, SRV, and CAA. For uncommon types (DNSKEY, DS, RRSIG, NSEC, TYPE65, HTTPS), use the DIG Lookup tool, which speaks any record type the resolver supports.
Is this an online DNS lookup tool — do I need to install anything?
No installation, no signup, no command-line tools required. The lookup runs entirely in your browser through this site, and Codynet does not retain or log your queries. If you would rather run it locally, the equivalent commands are dig example.com A or nslookup example.com.

Last reviewed: 2026-05-20.