How to Find DNS Records for Any Domain (Free Guide)

A site goes down. An email bounces back for no obvious reason. A migration seems stuck halfway. Nine times out of ten, the fix starts the same way: checking the domain's DNS records.

The good news is that finding DNS records does not require any special access or expensive software. You can do it in your browser in a few seconds, or from a command line if you want more control. By the end of this guide, you will know exactly how to look up any DNS record, read the results, and understand what each one is actually telling you.

What Are DNS Records, and Why Would You Need to Find Them?

DNS records are entries stored in a domain's zone file that tell the internet where to send traffic, where to deliver email, and how to verify that a domain belongs to a particular service or owner. Think of DNS as the internet's phonebook. Instead of memorizing a string of numbers to reach a website, you type a domain name, and DNS quietly translates that name into the correct address behind the scenes.

You typically end up needing to find DNS records for one of a handful of reasons: a website that will not load, an email that keeps bouncing, a subdomain that was just set up but is not resolving, an SSL certificate that fails to issue, or a routine security check to make sure nothing has changed without your knowledge.

The 3 Ways to Find DNS Records

There are three practical ways to look up DNS records, and which one you reach for depends on what you are trying to do.

Free online tools are the fastest option and require zero setup, which makes them a good fit for a quick, one-off check. Command Prompt is built into every Windows machine and works well once you are comfortable with a terminal. Terminal commands on Mac and Linux, particularly dig, give you the most detail and flexibility, which is why most developers and system administrators default to it.

All three methods query the same underlying data. The difference is mostly about speed, convenience, and how much detail you want back.

Method 1: Free Online DNS Lookup Tools

Web-based DNS lookup tools work by querying a domain's authoritative name server directly, the same server that holds the official, up to date version of that domain's DNS records.

Using one is simple. Enter the domain name, choose the record type you want to check (or select "all" if you want the full picture), and the tool returns the results within a second or two. Most tools also let you choose which resolver to query against, such as Google, Cloudflare, or OpenDNS. This is worth doing if you suspect propagation differences, since not every resolver around the world updates at exactly the same time.

If you want a fast, no-friction way to do this, you can run a quick DNS record lookup and see every major record type for a domain in one place.

This method is more than enough for most everyday checks: confirming a record was published correctly, verifying a migration, or just satisfying your own curiosity about how a domain is configured. Where it falls short is deeper troubleshooting, tracing exactly how a query resolves step by step, or querying an unusual record type that a basic tool does not support. That is where the command line comes in.

Method 2: Find DNS Records Using Command Prompt (Windows)

Windows comes with a built-in tool called nslookup that can query DNS records without installing anything extra.

To open it, press Start and type cmd, or press Windows key plus R and type cmd, then press enter. Once the command prompt window is open, type:

nslookup example.com

Replace example.com with the domain you want to check. By default, this returns the A record, meaning the IP address the domain currently points to.

To check a specific record type instead, switch nslookup into a more targeted mode. Type:

set type=MX

Then enter the domain name again and press enter. This will return only the MX records for that domain. You can substitute MX with A, AAAA, CNAME, NS, TXT, or SOA depending on what you need to see.

Nslookup has two modes. Interactive mode, which is what you get when you just type nslookup on its own, lets you run multiple queries in a row without retyping the whole command each time. Non-interactive mode, where you include the domain directly after the command, is faster for a single quick check.

When you read the results, you will often see a line labeled "non-authoritative answer." That is completely normal. It simply means the response came from a cached record on a recursive resolver rather than directly from the domain's own authoritative name server.

If you want to query a specific name server instead of your default one, type:

server [nameserver]

replacing [nameserver] with the server you want to use, then run your query again.

Method 3: Find DNS Records Using Terminal (Mac/Linux)

Mac and Linux users typically reach for dig, which is the most detailed and flexible command-line DNS tool available. Open Terminal and type:

dig example.com

This returns the A record along with a fair amount of technical detail about the query itself. To check a different record type, add it to the end of the command:

dig example.com MX

If you just want the answer without all the surrounding metadata, add the +short flag:

dig example.com MX +short

For a deeper look at exactly how a query resolves, step by step through the DNS hierarchy, use +trace:

dig example.com +trace

This is particularly useful when a domain is not resolving correctly and you need to figure out at which point in the chain things are breaking down.

If dig feels like more than you need, the host command offers a simpler, no-frills alternative:

host example.com

And if you are more comfortable with the nslookup syntax from the Windows section above, it works the same way on Mac and Linux too.

Understanding Every DNS Record Type

Once you can pull up a DNS record, the next step is understanding what each type actually means. Here is a plain-English breakdown of every record you are likely to encounter.

A and AAAA Records

The A record maps a domain to an IPv4 address, which is the most fundamental DNS record there is. It is how a browser knows which server to connect to when someone types in your domain name. The AAAA record does the same job but for IPv6 addresses, the newer addressing format created to handle the growing number of devices connected to the internet.

If a domain has no A or AAAA record at all, it simply will not resolve. Nothing will load, because there is no address for a browser to connect to.

CNAME Records

A CNAME record is an alias that points one domain or subdomain to another hostname, never directly to an IP address. The most common use case is pointing www.yourdomain.com to yourdomain.com, so both versions of the address lead to the same place.

One important rule: a CNAME record cannot coexist with other record types at the same name, and this restriction is especially strict at the root or apex of a domain. If you see a CNAME sitting alongside an MX or TXT record at the same location, that is a configuration error worth fixing.

MX Records

MX records tell the internet which mail servers are responsible for handling a domain's incoming email, and in what order of priority. Each MX record comes with a priority value, where a lower number means a higher priority, so mail is attempted through that server first.

If email keeps bouncing, checking the MX records is almost always the first troubleshooting step. No MX records, or MX records pointing to the wrong provider, will guarantee delivery failures.

TXT Records

TXT records are a general-purpose field for storing text-based information about a domain, and they show up constantly in email authentication and domain verification. The three most common uses are SPF, DKIM, and DMARC, which together help mail servers confirm that an email claiming to be from your domain is actually legitimate. TXT records are also how services like Google Search Console or payment processors confirm that you actually own a domain, typically by asking you to add a specific text string and then checking for it.

NS Records

NS records identify the authoritative name servers responsible for managing and publishing a domain's DNS records. Looking at a domain's NS records is a quick way to figure out which DNS provider or host it is using, since many providers assign distinctly branded name servers.

SOA Records

The Start of Authority record holds metadata about the domain's zone file itself: which server is the primary source of truth, an administrative contact, a serial number that increments with each change, and timing values that control how often secondary servers should refresh their copy of the data.

PTR, SRV, CAA, DS, and DNSKEY Records

A handful of record types show up less often but matter for specific situations. PTR records handle reverse DNS, mapping an IP address back to a hostname, which is commonly checked when reviewing server logs or validating an email server's configuration. SRV records specify the location and configuration details for a particular service, such as VoIP or instant messaging.

CAA records control which certificate authorities are allowed to issue SSL certificates for a domain, and they can block certificate issuance entirely if misconfigured. DS and DNSKEY records work together to support DNSSEC, maintaining a chain of cryptographic trust between a domain and its parent zone. You are less likely to check these day to day, but they matter a great deal during security audits.

For a deeper technical breakdown of any of these, Cloudflare's overview of common DNS record types is a solid reference, and IANA's official registry of DNS record types lists every record type that has ever been formally defined.

How to Read Your Results (What "Correct" Looks Like)

Once you have your results in front of you, a few quick checks will tell you whether things are actually configured correctly.

A healthy domain should have at least one A or AAAA record pointing to a valid, reachable IP address. It should have more than one name server listed, since relying on a single nameserver means the entire domain goes offline if that one server has an outage. There should be no CNAME record sitting at the same name as an MX or TXT record. And if the domain sends email of any kind, there should be an SPF record present in the TXT records, since a missing SPF record makes it far easier for someone else to send spoofed email that appears to come from your domain.

Run through that short list after any lookup, and you will catch most common misconfigurations before they turn into a real problem.

Understanding TTL and DNS Propagation

Every DNS record includes a TTL, or Time to Live, value. This number tells resolvers around the world how long they are allowed to cache that record before checking back in for an updated version.

This is why DNS changes do not take effect everywhere instantly. Depending on the TTL, a change can take anywhere from a few minutes to as long as 48 hours to fully propagate across every resolver globally. If you know a change is coming, lowering the TTL to something short, like 300 seconds, a day or two beforehand will help the new value spread much faster once you make the switch. Just remember to raise it back to a more normal value afterward, since a permanently low TTL increases the load on your DNS provider.

To confirm a change has actually propagated, run a quick DNS record lookup again after making the update, ideally checking it against more than one resolver. And if you are also trying to confirm who currently controls a domain during a migration or ownership dispute, it can help to check its WHOIS record too, since DNS and ownership data are often reviewed side by side.

Troubleshooting Common DNS Record Issues

Most DNS problems fall into a handful of recognizable categories, and knowing which record to check first will save you a lot of time.

If a website will not load at all, start with the A or AAAA record. If email is not arriving, check the MX record first, then move on to SPF, DKIM, and DMARC in the TXT records. If a newly created subdomain is not resolving, check whether its specific CNAME or A record actually exists, since subdomains need their own entry and do not automatically inherit the root domain's records. If an SSL certificate is failing to issue, check the CAA record, since it may be restricting which certificate authorities are allowed to issue for that domain.

If you suspect something has changed without your knowledge, perhaps due to a compromised account or an unauthorized edit, compare your current records against your last known-good configuration. And if the DNS records themselves look correct but the site still is not loading properly, it is worth taking the extra step to see where the domain is actually hosted, since the issue may sit with the hosting provider rather than DNS itself.

Quick Reference: DNS Record Types Cheat Sheet

Final Thoughts

Finding DNS records really comes down to two things: picking the method that fits what you are trying to do, and knowing what each record type is actually telling you once you have it. A quick web tool covers most everyday needs, while nslookup and dig give you the depth to troubleshoot almost anything.

The best way to make this stick is to try it yourself. Pick a domain, run a quick DNS record lookup, and work through the record types in this guide until reading a DNS record feels as natural as reading any other list.