Every domain runs on DNS records most people never see: A records point the name at a server, MX records route the email, TXT records prove ownership and fight spam. When a website will not load, email lands in spam, or a verification TXT record seems to vanish, the first diagnostic step is always the same: look at what DNS actually says right now. This tool queries public resolvers for the record types that matter and shows the live answers with their TTLs, so you can separate ‘the record is wrong’ from ‘the record is fine and the problem is elsewhere’.
Quick Answer: Type a domain name, choose the record type (A, AAAA, MX, NS, TXT, CNAME or SOA), and click Look Up. The live records are listed with their values and TTLs, exactly as public DNS currently answers.
How to Use the DNS Lookup Tool
- Type the domain to inspect, without http or www unless you specifically want that subdomain’s records.
- Choose the record type: A for server address, MX for email routing, TXT for verification and SPF, and so on.
- Click Look Up and read the answers returned by the public resolver.
- Check the TTL values: they tell you how long old answers stay cached around the internet after a change.
- Cross-check with a second record type if you are diagnosing: a working site needs its A record, email needs MX plus usually SPF in TXT.
Key Features
- All the record types that matter day to day: A, AAAA, MX, NS, TXT, CNAME and SOA.
- Live answers from a major public resolver, fetched when you ask, not scraped from a stale cache.
- TTL shown for every record so caching delays can be judged realistically.
- Clear status messages distinguishing ‘domain has no such record’ from ‘domain does not exist’.
- Runs from your browser using DNS-over-HTTPS: no command line, no account, no installs.
Best Practices and Tips
- After changing a record, expect the old answer to persist for its TTL; a 3600 TTL means up to an hour of mixed answers worldwide.
- For email problems, check MX first, then the TXT record for SPF, and remember DKIM lives under a selector subdomain.
- A CNAME cannot legally sit beside other records for the same name; if a lookup shows odd conflicts, start there.
- Query the exact subdomain you use: records for example.com say nothing about the records of app.example.com.
Common Mistakes to Avoid
- Typing the full URL with https:// into a DNS tool: DNS names are just the hostname part.
- Judging a change as failed five minutes after making it, when the old TTL still has the world serving cached answers.
- Confusing the registrar’s nameservers with the records themselves: NS shows who answers, not what the answers are.
- Assuming one resolver speaks for the whole internet during propagation; another resolver may legitimately answer differently for a while.
Frequently Asked Questions
What do A, MX and TXT records actually do?
An A record maps a name to an IPv4 server address (AAAA does the same for IPv6). MX records name the mail servers that accept email for the domain, with priorities. TXT records carry text used for ownership verification, SPF email policy, and assorted service settings.
What is TTL and why does it matter?
TTL (time to live) is how many seconds other servers may cache a record. Long TTLs make DNS fast and stable but slow to change; short TTLs make changes spread quickly. Lowering the TTL a day before a migration is the classic professional trick.
Why does the tool say no records when the site works?
You may have queried a type the domain does not use (many domains have no AAAA yet), or queried the bare domain when the site actually lives on www, which has its own records. Check the exact hostname and a different type.
Can this show me who owns a domain?
No: that is WHOIS data, a separate system. DNS answers how a domain is wired (servers, mail, verification), not who registered it, and many registration details are privacy-redacted nowadays anyway.
Is it safe to look up any domain?
Yes. DNS records are public by design: the system only works because anyone can ask. Your lookup goes through a public resolver over HTTPS, like any other DNS query your browser makes constantly.
Related Tools
