DNS Lookup
Query DNS records for any domain: A, AAAA, MX, TXT, CNAME, NS, SOA and more.
In June, a client moved their marketing site from Cloudflare to a new host over a weekend and didn’t loop us in until Monday. The site had been live on the new server for two days, but our monitoring showed nothing resolving every request timed out with SERVFAIL. Before telling the client, anything was broken on our end, we ran a DNS lookup online on the domain and found the real story: the NS records at the registrar still pointed to Cloudflare, while the new host expected authority. It wasn’t a server problem; it was a 41-hour propagation gap caused by a TTL left at 86400 seconds (24 hours) on the old zone. We told the client to wait it out rather than rebuild anything. By Wednesday, the site resolved normally and traffic recovered. That single check, about eight seconds, kept us from spending a week troubleshooting a server that was never the issue.
That’s the practical value of a DNS lookup tool: it replaces a guess with a fact.
What This DNS Lookup Tool Does
DNS is defined by RFC 1035, the specification that still governs how names resolve to records today. A resolver walks the chain from the root servers down to a domain’s authoritative nameservers, returning an A record for an IPv4 address, an MX record for mail routing, a TXT record for things like SPF or a Search Console verification string, or an NS record showing which servers are authoritative for the zone.
Our tool sends that same type of query to public DNS resolvers and returns the raw answer, unfiltered. Check A, AAAA, CNAME, MX, TXT, NS, and SOA records one at a time or together, along with each record’s TTL the number that governs how long a resolver can cache an answer before asking again. That TTL decided our 41-hour wait above.
Where Technical Teams Actually Use This
- Confirming NS records have cut over after a migration, instead of assuming a hosting problem is to blame
- Checking MX and TXT records when transactional or marketing emails start bouncing or landing in spam
- Verifying a domain transfer completed cleanly by checking which nameservers currently hold authority
- Spotting CNAME misconfigurations on subdomains, where a stale record can quietly break part of a site
- Auditing DNS on a client domain before making infrastructure recommendations, so changes are based on current records rather than assumptions
How to Use the DNS Lookup Tool
1. Enter the domain no “http://” or “www.” needed
2. Select a record type (A, MX, TXT, CNAME, NS, SOA) or “all records”
3. Click “Lookup” to query public DNS resolvers directly
4. Note the TTL on each record it tells you how long a change takes to be visible elsewhere
5. Re-run the check after any DNS edit, rather than trusting a change has taken effect just because you made it
Features
- Supports A, AAAA, CNAME, MX, TXT, NS, and SOA record types
- Displays TTL values alongside each record
- No account, login, or email required
- Unlimited lookups, no daily cap
- Plain-text results, easy to paste directly into an audit document
Where This Tool Has Limits
This tool queries public resolvers at the moment you run it it isn’t a snapshot of every resolver at once. Because caching is built into the DNS protocol, it’s normal for us to show an updated record while someone on a different ISP still sees the old one for a few more hours, exactly as happened in the migration case above. For multi-region checks, pair this with a distributed propagation checker rather than treating one lookup as final. It also can’t confirm whether a mail server is actively accepting mail, only that an MX record exists and resolves, and it has no visibility into private DNS zones that aren’t published to the public root.
Why Our Technical Team Trusts This Tool
We built this for our own internal audits before offering it publicly. Our team runs a version of this check before every site migration report and before making any infrastructure recommendation to a client, because in our experience DNS misconfiguration is one of the most common causes of a site or email problem and one of the easiest to misdiagnose as a hosting or content issue instead. No domain you search here is logged against an account; the tool queries resolvers live rather than storing results.
Frequently Asked Questions
Is this DNS lookup tool free to use?
Yes. No signup, no login, and no cap on how many lookups you can run in a day.
Why do my DNS changes still show the old records after I’ve updated them?
That’s almost always TTL caching, not a failed update. If the old record had a TTL of 3600 seconds, some resolvers can keep serving that cached answer for up to an hour after the change, sometimes longer.
Can I check a domain I don’t own?
Yes. DNS records are public information by design, so looking up any domain your own, a client, or a domain you’re evaluating is normal and not a security concern.
Ready to check a domain?
Run your DNS lookup online now free, unlimited, and no account needed.