tool / dns
DNS Lookup
A, AAAA, MX, TXT, NS and CNAME records.
try
Real resolvers
Every gap labelled.
Each result shows its source and what was not tested.
How DNS Lookup works
A DNS lookup asks a public resolver which records a domain publishes. Use it to confirm a change went live, find where mail or a website points, or debug a record that does not work.
Type a domain such as example.com in the query box.
Read the records by type. Use the tabs to filter to A, MX, TXT and so on.
Check the resolver block. If the public resolvers disagree, a change is still spreading.
Troubleshooting & Remediation
How to Read & Fix Results
How to read the result
- ProblemThe domain has no A, AAAA or CNAME record, or the lookup says the name does not exist (NXDOMAIN). Visitors cannot reach it.
- WarningResolvers return different answers. Often a change is still spreading. CDN sites also answer differently by location, which is normal.
- PassEvery resolver returns the same records and they match what you set at your DNS host.
How to fix issues
- 1Open the DNS settings at the company that hosts your DNS (the nameservers shown in WHOIS), not necessarily where you bought the domain.
- 2Add or edit the record. A website needs an A record (IPv4) or a CNAME to a hostname. Mail needs MX records.
- 3Save, then run the lookup again. If the answer is old, wait for the old TTL in seconds to pass.
- 4Before a planned move, lower the TTL a day or two ahead, make the change, check, then raise the TTL again.
Common mistakes to avoid
- •Editing records at the registrar while the nameservers point to another provider. The edit does nothing.
- •A CNAME on the bare domain (example.com). Most hosts do not allow it; use A records or the provider's flattening feature.
- •Leaving a very long TTL on a record you are about to change.
- •Typing the full domain into the Name field so it becomes name.example.com.example.com.
Example DNS Record Format
example.com. 300 IN A 203.0.113.10 example.com. 300 IN MX 10 mail.example.com. example.com. 300 IN TXT "v=spf1 -all"
This tool asks public DNS-over-HTTPS resolvers (from your browser and from our Cloudflare edge). It reports what they return at that moment. It does not see private DNS.
Next checks:Check mail recordsCheck the certificateCheck security headers
Specifications & Scope
About DNS Lookup
- 01 / What it does
- A DNS lookup asks a public resolver which records a domain publishes. Use it to confirm a change went live, find where mail or a website points, or debug a record that does not work.
- 02 / How to use
- 1. Type a domain such as example.com in the query box. 2. Read the records by type. Use the tabs to filter to A, MX, TXT and so on. 3. Check the resolver block. If the public resolvers disagree, a change is still spreading.
- 03 / Good to know
- The TTL column is how many seconds a resolver may keep the answer. After you edit a record, old answers can stay visible until the old TTL runs out.
Got Questions?
Frequently Asked Questions
Knowledge Base
Technical Guides & Reference
Explore More
More in Domain & Email
Tool Details & Usage Guide
RFC specifications, input expectations, outputs, and edge limitations.
Complete DNS Analysis Guide
When troubleshooting domain connectivity, email delivery, or DNS propagation, a thorough DNS Lookup is the essential first step. This tool queries public resolvers to return the actual DNS records currently published for your domain.
Supported Inputs
- Domain Name: e.g.,
example.com - The tool queries standard record types including A (IPv4), AAAA (IPv6), MX (Mail Exchange), TXT (Text records for SPF/verification), NS (Name Servers), and CNAME (Canonical names).
How to Interpret the Output
- Record Data: The target IP or text value.
- TTL (Time to Live): The time (in seconds) resolvers are told to cache this record. A TTL of 300 means 5 minutes.
- Record Type: Denotes what the record is used for.
Realistic Example
If you look up google.com:
- You will see multiple A records pointing to Google’s load-balanced IPs.
- You will see MX records pointing to
smtp.google.comfor handling their mail. - TXT records will show their SPF policies (e.g.,
v=spf1 include:_spf.google.com ~all).
Common Errors & Limitations
- Stale Cache: If you just updated a record at your registrar and don’t see it here, it is due to DNS caching. Wait for the old TTL to expire.
- No Results: Make sure you are querying the base domain unless the records are explicitly published on a subdomain.
Recommended Troubleshooting Deep Dives
Authoritative SRE implementation tutorials related to this tool.
How to Fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome
Step‑by‑step guide to eliminate DNS_PROBE_FINISHED_NXDOMAIN errors in Chrome. Real‑world fixes from a network security engineer.
Read guideWhy Does DNS Propagation STILL Take So Long in 2026?
Every developer has stared at a screen waiting for DNS to propagate. Here is why it happens, and how to actually force it to speed up.
Read guideDNS Migration Checklist: Move Your Domain Without Breaking Email or Your Website
A step-by-step checklist for moving DNS to a new provider: export records, lower TTL, copy MX, SPF, DKIM and DMARC, switch nameservers, then verify.
Read guideRelated tools
View all toolsDNSSEC Validator
Free DNSSEC validator. Verify the cryptographic chain of trust from ICANN root down to zone apex. Inspect DS records, DNSKEY public keys, and RRSIG validity.
DNS Time Machine
Free DNS Time Machine. Track DNS record changes with git-style visual diffs (+/-) and export standard RFC 1035 BIND zone files for 1-click disaster recovery.
DNS Propagation
Free global DNS propagation checker. Test A, AAAA, CNAME, MX, and TXT records across 12 worldwide edge locations with expected value matching and Geo-DNS detection.