Whether you're troubleshooting a site that won't load, fixing email that isn't arriving, or just curious where a website is hosted, the answer is often hidden in a domain's DNS records. These records are public — anyone can look them up in seconds — and reading them tells you exactly how a domain is configured. Here's how to look up DNS records for any domain, using either a free online tool or the command line, and what each record type actually means.

Why look up a domain's DNS records?

DNS records are the settings that control where a domain points and how its services behave. Checking them is useful when you want to:

  • Confirm a domain resolves — see whether it has a valid address at all, or diagnose why it won't load.
  • Debug email delivery — verify the mail (MX) and authentication (TXT) records that decide whether email reaches the inbox or the spam folder.
  • Check DNS propagation — after changing a record, confirm the new value is live.
  • Identify the host or IP — see which server or provider a domain points to.
  • Verify nameservers — confirm which servers are actually authoritative for the domain.

The easiest way to look up DNS records

You don't need any technical skills or software. The simplest method is a free online DNS lookup tool: you enter a domain, and it queries the authoritative servers and shows you every record type instantly.

Our free DNS Records tool does exactly this — enter any domain and it returns its A, AAAA, MX, NS, TXT, CNAME and SOA records in one clean view. It's the fastest way to see a domain's full configuration without touching a command line, and it works from any device.

If you're curious how that lookup actually happens behind the scenes — the journey from your device to the root, TLD and authoritative servers — our plain-English guide on what a DNS lookup is and how it works breaks it down.

What each DNS record type tells you

When you run a lookup, you'll see several record types. Here's what each one means and why you'd check it:

  • A record — maps the domain to an IPv4 address (like 93.184.216.34). This is the core "where does this site live" record. No A record usually means the site can't be found.
  • AAAA record — the same idea for IPv6 addresses, the newer addressing system.
  • CNAME record — an alias that points one name to another (for example, www.example.com pointing to example.com). Useful for spotting how subdomains are routed.
  • MX record — the mail exchange record, which tells the world where to deliver email for the domain. If email isn't arriving, this is the first thing to check.
  • TXT record — free-form text used for verification and email security, including SPF, DKIM and DMARC records that prove your email is legitimate. Missing or wrong TXT records are a top cause of email landing in spam.
  • NS record — the nameservers that are authoritative for the domain. If these are wrong, nothing else resolves correctly.
  • SOA record — the "start of authority," containing administrative details about the domain's DNS zone.

Looking up DNS records from the command line

If you're comfortable with a terminal, you can query records directly. On Windows, use nslookup:

nslookup example.com
nslookup -type=MX example.com
nslookup -type=TXT example.com

On macOS and Linux, dig gives cleaner output:

dig example.com
dig example.com MX
dig example.com TXT +short

Swap example.com for the domain you're checking and the record type for whichever you need. For most people, though, the online tool is faster and easier to read — the command line is mainly handy for scripting or advanced diagnostics.

Common reasons to check DNS records

Here's how these lookups solve real problems:

  • A site won't load. Look up the A record. If it's missing or points somewhere unexpected, the domain's DNS is broken or expired — which is exactly what causes errors like DNSPROBEFINISHEDNXDOMAIN. Our guide on diagnosing why one website won't load uses this check as a key step.
  • Email isn't being delivered. Check the MX record (where mail goes) and the TXT records (SPF/DKIM/DMARC that authenticate it). A missing SPF record is a classic reason messages get flagged as spam.
  • You just changed a record. Look it up to confirm the new value is live. Note that changes take time to spread, and your own device may show an old cached answer until you flush your DNS cache.
  • You want to confirm a site is really down. If the records look fine but the site still won't load, run it through our live website down checker to see whether the problem is the domain or just your connection.

The bottom line

Looking up a domain's DNS records is one of the most useful diagnostic skills you can pick up, and it takes seconds. Enter a domain into a free DNS Records tool to see its full configuration, or use nslookup/dig from the command line for specific records. Once you know what A, MX, TXT and NS records mean, you can diagnose loading problems, fix email delivery, and verify changes with confidence — no guesswork required.