🔎 DNS Lookup Tool
Check any domain's live DNS records — A, AAAA, MX, TXT, NS, and more — instantly.
What Is a DNS Lookup Tool and Why You Need It?
A DNS Lookup Tool checks how a domain name is configured on the internet's Domain Name System — the global directory that translates human-readable names like example.com into the technical addresses and settings computers actually use. Every website, email service, and app depends on DNS records being set up correctly, and a huge number of "my website is down" or "my emails aren't sending" problems trace back to a single incorrect or missing DNS record.
This tool queries live, public DNS resolvers in real time and shows you exactly what's published for a domain right now — not cached or outdated information. It's built for anyone managing a website, setting up email, migrating hosting providers, or troubleshooting a domain that isn't behaving as expected.
How to Use This Tool
- Type a domain name into the box (no need to include "http://" or "www").
- Select a record type — A, AAAA, CNAME, MX, TXT, NS, SOA, CAA — or choose "ALL Records" to check everything at once.
- Click "Lookup" to see the live results.
- Use "Check Propagation" after making DNS changes to see if Google and Cloudflare's DNS servers already agree on the new values.
Understanding DNS Record Types
A Record: Points a domain to an IPv4 address (like 93.184.216.34). This is the most common record type and the one most people mean when they say "DNS record" — it's what makes your website actually load when someone types your domain into a browser.
AAAA Record: The IPv6 equivalent of an A record. As internet infrastructure gradually moves to IPv6, more domains are adding AAAA records alongside their A records for future compatibility.
CNAME Record: Points one domain name to another domain name instead of an IP address directly. Commonly used for subdomains — for example, pointing "www.example.com" to "example.com," or pointing a subdomain to a hosting provider's platform address.
MX Record: Tells the internet which mail servers are responsible for receiving email for a domain, along with a priority number. Lower priority numbers are tried first. If your MX records are missing or wrong, email sent to your domain will bounce or never arrive.
TXT Record: A flexible, plain-text record used for many verification and security purposes — most importantly email authentication (SPF, DKIM, DMARC, explained below) and domain ownership verification for services like Google Workspace or Microsoft 365.
NS Record: Lists the authoritative nameservers responsible for a domain — the actual DNS servers that hold and answer all other DNS queries for that domain. If your NS records point to the wrong provider, none of your other DNS records will take effect no matter how correctly they're configured elsewhere.
SOA Record: "Start of Authority" — contains administrative information about the domain's DNS zone, including the primary nameserver, an administrator contact, and timing values that control how often other DNS servers should refresh their cached copy of your records.
CAA Record: Specifies which Certificate Authorities are allowed to issue SSL/TLS certificates for a domain. This is a security feature that prevents unauthorized certificate issuance — if it's misconfigured, legitimate certificate renewal can fail.
Why Results From Different DNS Providers Can Differ (Propagation Explained)
DNS is not one single database — it's a distributed system with thousands of DNS resolvers around the world, each independently caching answers for a period of time defined by the TTL (Time To Live) value of each record. When you update a DNS record, that change doesn't appear everywhere instantly. Instead, it spreads gradually as each resolver's cached copy expires and it fetches the new value. This spreading process is called "propagation," and it's the reason two different DNS providers — like Google and Cloudflare — can briefly show different results for the same domain right after a change.
This is exactly why the "Check Propagation" feature in this tool compares two independent, major DNS providers side by side. If they agree, your change has very likely spread across most of the internet already. If they disagree, some users may still be seeing your old DNS configuration.
How Long Does DNS Propagation Take?
Most DNS changes propagate within a few minutes to a few hours, but full global propagation can technically take up to 48 hours in rare cases, especially for nameserver changes rather than individual record changes. The TTL value set on a record directly controls this — a record with a TTL of 300 seconds (5 minutes) will refresh much faster across the internet than one with a TTL of 86400 seconds (24 hours). If you're planning a DNS migration, it's good practice to lower TTL values a day or two in advance so that when you make the actual change, it propagates faster.
Common DNS Problems and What They Mean
| Symptom | Likely DNS Cause |
|---|---|
| Website doesn't load at all | Missing or incorrect A/AAAA record, or NS records pointing to the wrong provider |
| Website loads on some networks but not others | DNS propagation still in progress after a recent change |
| Emails to your domain bounce | Missing, incorrect, or misprioritized MX records |
| Emails from your domain land in spam | Missing or incorrect SPF, DKIM, or DMARC TXT records |
| "www" version of site works but bare domain doesn't (or vice versa) | Missing A record for the bare domain or missing CNAME for "www" |
| SSL certificate renewal fails unexpectedly | A CAA record restricting which Certificate Authorities can issue certificates |
| Domain verification for Google/Microsoft services fails | Missing or incorrect verification TXT record |
TXT Records Explained: SPF, DKIM, and DMARC
If you manage email for a domain, three specific TXT records matter more than almost anything else, because together they determine whether your emails are trusted or sent straight to spam.
SPF (Sender Policy Framework): A TXT record that lists exactly which mail servers are allowed to send email on behalf of your domain. When a receiving mail server gets an email claiming to be from your domain, it checks your SPF record to verify the sending server is actually authorized. Without SPF, anyone could send email pretending to be from your domain.
DKIM (DomainKeys Identified Mail): Adds a cryptographic signature to outgoing emails, published as a TXT record containing a public key. Receiving servers use this to verify the email genuinely came from your domain and wasn't altered in transit.
DMARC (Domain-based Message Authentication, Reporting & Conformance): A policy record that tells receiving mail servers what to do if an email fails SPF or DKIM checks — reject it, quarantine it (send to spam), or do nothing but report it. DMARC is what actually enforces SPF and DKIM; without it, failing emails might still be delivered anyway.
Use this tool's TXT lookup to check whether these records currently exist for your domain — a missing DMARC record in particular is one of the most common, and most damaging, oversights for email deliverability.
How to Check If Your Nameservers Are Set Correctly
Your nameservers (NS records) are the foundation everything else depends on. If they're wrong, updating any other DNS record anywhere else won't have any effect, because the internet isn't even asking your intended DNS provider for answers in the first place. To verify: look up the NS record type for your domain using this tool, and confirm the listed nameservers match exactly what your hosting provider or domain registrar told you to use. If they don't match, the fix happens at your domain registrar (where you bought the domain), not in your DNS provider's dashboard.
DNS Lookup vs. WHOIS Lookup: What's the Difference?
These two tools are often confused, but they check completely different things. A WHOIS lookup tells you who registered a domain, when it was registered, when it expires, and which registrar manages it — essentially domain "ownership" information. A DNS lookup, like this tool, tells you how the domain is technically configured to actually function — where it points, how mail is routed, and what security policies are published. You'd use WHOIS to check domain ownership or expiration; you'd use DNS lookup to troubleshoot why a website or email isn't working correctly.
A Real Troubleshooting Walkthrough
Imagine you just migrated your website to a new host and updated your A record, but the site still shows the old content for some visitors. First, run an A record lookup here to confirm the new IP address is correctly published. If it is, run "Check Propagation" — if Google and Cloudflare already agree on the new IP, the DNS side is done, and the issue is likely browser or ISP-level caching on the visitor's end, not your DNS configuration. If the two providers disagree, you're still in the propagation window and simply need to wait a bit longer.
FAQs
Is this tool checking my own computer's DNS, or the internet's public DNS?
The public, authoritative DNS records for the domain — the same information every visitor's browser uses, not any local cache on your own device.
Why does my domain show no MX records?
This usually means either the domain doesn't have email configured at all, or the MX records were never set up with your email provider. Check your email provider's setup documentation for the exact records they require.
Can I look up any domain, or only ones I own?
You can look up any public domain's DNS records — this is public information available to anyone, the same way a phone directory is public.
Why do I see different results when I check the same domain a few hours apart?
DNS records can be changed by the domain owner at any time, and TTL-based caching means results can briefly vary across different resolvers during propagation, as explained above.
What does it mean if "ALL Records" shows almost nothing?
Not every domain uses every record type — for example, a domain with no email configured won't have MX records, and one without extra security policies won't have a CAA record. This is often completely normal.
Does this tool store or log the domains I search?
No. Each lookup sends a direct request to Google's or Cloudflare's public DNS service in your browser — nothing is stored on this site.
Why did my lookup fail completely?
This can happen if the domain doesn't exist, is misspelled, or if both DNS providers are temporarily unreachable from your network. Double-check the spelling and try again.
Is a longer TTL better or worse?
Neither — it's a trade-off. Longer TTLs mean fewer DNS lookups (slightly faster browsing, less load on DNS servers) but slower propagation when you make changes. Shorter TTLs propagate faster but generate more lookup traffic.
Related Tools
Network Reset Command Generator · Windows Error Code & BSOD Lookup Tool · What Is My IP Tool · WiFi Connected But No Internet — 9 Fixes