A DNS lookup is a query that retrieves the DNS records of a domain — the records that tell the internet where a website is hosted, where its email is delivered, and how it is verified. To run one, enter a domain and the tool returns its A, MX, TXT, CNAME, and other records. The FindUtils DNS Lookup does this in seconds — free, with no signup.

This guide explains what DNS records are, how to run a lookup step by step, what each record type does, and how to use DNS lookups to debug websites and email.

What Is DNS and Why Look Up Records?

DNS (Domain Name System) is the internet's address book — it translates human-readable domain names into the IP addresses and configuration that computers use. A DNS lookup reveals exactly how a domain is currently configured.

When a website will not load, email bounces, or a domain change "has not taken effect," the answer is almost always in the DNS records. A lookup shows you the live, authoritative configuration instead of guessing.

Run a DNS lookup when:

  • A website will not resolve — the A record may be missing or pointing to the wrong server.
  • Email is failing — MX, SPF, or DKIM records control whether mail is delivered.
  • You changed DNS settings — a lookup confirms whether the new records are live.
  • You verify a domain — many services require a TXT record to prove ownership.
  • You investigate a domain — checking where an unknown domain points.

How to Run a DNS Lookup Online

Running a DNS lookup takes one step to query and a few minutes to interpret. The FindUtils DNS Lookup queries public DNS and returns every record type for the domain.

Step 1: Enter the Domain Name

Open the FindUtils DNS Lookup and enter the domain you want to inspect — for example, example.com. Enter the bare domain without https:// or a path.

Step 2: Choose the Record Type

Select the record type you need, or view all of them. A records show the hosting IP; MX records show the mail servers; TXT records hold verification and email-policy data.

Step 3: Review the Results

Read the returned records. Each record has a value and a TTL (Time To Live) — the number of seconds the record can be cached before being refreshed.

Step 4: Compare Against What You Expect

Match the live records against your intended configuration. A missing record, a wrong IP, or an outdated value is usually the root cause of the problem you are debugging.

DNS Record Types Explained

Each record type serves a distinct purpose. Knowing what each one does turns a lookup into a diagnosis.

RecordPurposeExample value
AMaps a domain to an IPv4 address93.184.216.34
AAAAMaps a domain to an IPv6 address2606:2800:220:1::
MXNames the mail servers for the domain10 mail.example.com
TXTHolds text data — verification, SPF, DKIMv=spf1 include:_spf.google.com ~all
CNAMEPoints one name to another namewww → example.com
NSNames the domain's authoritative nameserversns1.host.com

The most-checked records in practice are A (is the site pointing at the right server?), MX (can the domain receive email?), and TXT (are SPF and verification records correct?).

DNS Lookup: Online Tool vs Command Line vs Paid Monitoring

An online lookup reports one resolver path at one time. A command-line query can select another resolver or record type. Repeated monitoring is a separate task. Different caches can temporarily return different answers.

Common DNS Issues and How to Fix Them

Mistake 1: Expecting DNS Changes to Apply Instantly

DNS records are cached for the duration of their TTL, so changes can take time to appear everywhere. Fix it by checking the TTL and waiting that long, or lowering the TTL before a planned change.

Mistake 2: Missing or Wrong A Record

If a domain has no A record or points to an old server, the site will not load. Fix it by setting the A record to the correct current server IP.

Mistake 3: Email Fails Because of MX or SPF Records

Mail bounces when MX records are missing or SPF (a TXT record) is misconfigured. Fix it by confirming MX records point to your mail provider and the SPF record lists every sending source.

Mistake 4: A CNAME Where a CNAME Cannot Go

A domain's root (apex) usually cannot use a CNAME record. Fix it by using an A record at the apex and reserving CNAME for subdomains like www.

Mistake 5: Checking Only One Record Type

A site can have a correct A record but a broken MX record. Fix it by reviewing all record types together so you do not miss the actual fault.

Tools Used in This Guide

FAQ

Q1: Is the DNS lookup tool free to use? A: Yes. The FindUtils DNS Lookup is available without signup and no usage limits. Enter any domain and get instant results for every DNS record type.

Q2: How long do DNS changes take to take effect? A: DNS changes propagate based on each record's TTL (Time To Live), which can range from minutes to 48 hours. Lowering the TTL before a planned change makes it apply faster.

Q3: Is it safe to look up DNS records online? A: Yes. DNS records are public information by design — they are how the internet routes traffic to a domain. A lookup only reads data that any computer can already query.

Q4: How do I check why my email is not being delivered? A: Run a DNS lookup and check the MX records (which name your mail servers) and the TXT records (which hold SPF and verification data). Missing or wrong values in either are the usual cause of email failures.

Q5: What is the difference between an A record and a CNAME? A: An A record maps a domain directly to an IP address. A CNAME maps one domain name to another name. Use A records at the domain root and CNAME for subdomains that should follow another name.

Q6: What does TTL mean in DNS? A: TTL (Time To Live) is how many seconds a DNS record may be cached before it must be looked up again. A lower TTL means changes propagate faster but slightly increases query volume.

Next Steps