Free Online DNS Lookup
Troubleshoot website issues, verify domain configurations, and inspect mail server settings with our fast DNS lookup tool.
DNS Lookup
Resolve common DNS record types using public DNS-over-HTTPS.
Result
Enter a domain to see DNS records.
Why Use Our DNS Tool?
Whether you are migrating a website and need to confirm DNS propagation, changing your web host, or setting up new email servers, our online nslookup alternative provides clear, accurate data.
Fast & Reliable
Rapid responses for A, AAAA, CNAME, MX, and TXT record types, queried directly from a public resolver.
DNS-over-HTTPS
Queries run over encrypted DNS-over-HTTPS (DoH), so your lookups aren't visible to anyone snooping on plain-text DNS traffic.
No Terminal Needed
Get the same diagnostic answers as dig or nslookup, without opening a terminal.
How a DNS Lookup Actually Works
Every time you visit a website, this handoff happens in the background — usually in under 50 milliseconds.
1. You request a domain
Your browser asks: "What's the IP address for example.com?"
2. Resolver checks its cache
A recursive resolver (your ISP's, or a public one like Google's) checks if it already has a cached answer.
3. Authoritative server answers
If not cached, the resolver asks the domain's authoritative name servers, which hold the actual record.
4. Answer returned & cached
The IP (or MX/TXT value) comes back to your browser and is cached for the record's TTL, so the next request is instant.
Supported Record Types
DNS (Domain Name System) is the phonebook of the internet. Our tool lets you query the most common record types to ensure your domain is routing correctly.
How to Check DNS Records
- Enter Domain: Type the target domain name (e.g., example.com).
- Select Type: Choose the specific DNS record (A, MX, TXT) you want to query.
- Run Lookup: Click the lookup button to query public DNS servers.
- Analyze: Review the raw JSON output showing TTL, target values, and resolution data.
Common DNS Lookup Problems
NXDOMAIN / no records found
The domain either doesn't exist, isn't registered, or has no record of that specific type — e.g. querying MX on a domain that only serves a website will correctly return nothing.
Old IP still showing after a change
This is almost always TTL caching, not a broken change — the old value is cached somewhere in the chain until it expires. Wait out the previous TTL before assuming the update failed.
CNAME conflicts with other records
A CNAME must be the only record on that exact name — you can't have a CNAME and an MX or TXT record on the same hostname simultaneously. This is a DNS spec rule, not a tool limitation.
SPF record not being respected
A domain can only have one SPF-type TXT record. If you have two, most mail providers will treat the record as invalid (a "permerror"), which can hurt deliverability rather than help it.
Frequently Asked Questions
What does "DNS Propagation" mean?↓
What is a TTL?↓
Why are my emails not being delivered?↓
Does this tool use my own DNS server?↓
Why doesn't this tool support NS or SOA records?↓
Explore more network tools
About This Utility
This tool is provided completely free of charge by Mavertex. Built by Kumar (an independent UI developer), our platform ensures your privacy by executing all operations strictly within your local browser DOM.
We prioritize zero-trust architecture. No files or inputs are ever uploaded to remote servers. This page serves as both an interactive web application and an educational resource explaining the mechanics of client-side operations. For further details on transparency and third-party network usage (including AdSense), please review our Privacy Policy.