DNS Lookup Guide
DNS Lookup answers a question that comes up constantly when something on the internet isn't working the way it should: what does this domain's DNS actually say right now? Domain Name System records control where a domain's traffic goes, which mail servers handle its email, and what other domains or services it has delegated authority to, and when something breaks — email not arriving, a website not resolving, a subdomain pointing to the wrong place — the DNS records are usually the first place to look, since the actual problem is very often a misconfigured or outdated record rather than anything more complicated.
This tool queries common DNS record types for any domain — A records (the IP address a domain points to), MX records (which mail servers handle its email), NS records (which nameservers are authoritative for it), TXT records (often used for domain verification and email authentication like SPF and DKIM), and several others — and returns the results directly in your browser. Because DNS is a public system by design, looking up a domain's records doesn't require any special access or authentication; the same information is visible to anyone who queries it, including this tool.
DNS changes don't take effect everywhere instantly, which is one of the most common sources of confusion when debugging: a record can be updated correctly at the authoritative nameserver while a particular resolver elsewhere in the world is still serving a cached, outdated answer until that cache expires, based on the record's time-to-live setting. This tool queries DNS fresh each time, which makes it useful for confirming what the authoritative answer actually is, separate from whatever a specific device or network happens to have cached at the moment.
Because DNS underpins so much of how the internet actually routes traffic, this kind of lookup is genuinely everyday tooling for anyone managing domains, troubleshooting email delivery, or verifying that a DNS change has actually propagated the way it was intended to.
How to look up DNS records for a domain
- Enter the domain name. Type in the exact full domain you want to investigate, such as example.com, without any protocol prefix like https:// in front of it. The tool accepts a plain domain name and prepares to query the standard DNS record types against it, the same way any DNS resolver on the internet would when asked about that domain. There's no need to prefix the domain with www or any subdomain unless you specifically want to query records for that particular subdomain rather than the root domain itself.
- Choose which record types to query. Select the exact, specific record type you actually need — A for the IP address, MX for mail routing, NS for authoritative nameservers, TXT for verification and authentication records, or others — or query several at once if you want a fuller picture of the domain's overall DNS configuration in a single pass rather than checking one type at a time. Querying multiple types at once is generally the more efficient approach when you're not yet sure which specific record is responsible for the problem you're actually trying to diagnose. This is especially relevant right after a domain transfer or hosting migration, when several record types may have changed simultaneously and a single query alone wouldn't reveal the complete picture.
- Run the lookup. Submit the query and the tool promptly returns the current DNS records for that exact domain and record type. Results typically include the record's value and its time-to-live, the latter telling you how long resolvers are permitted to cache that answer before they're required to check again with the authoritative source. A very low time-to-live value generally indicates the domain's administrator is actively planning changes and wants resolvers to check back frequently, while a high value suggests a stable, rarely-changed configuration.
- Interpret the results. Compare what's actually being returned against what you genuinely expect to see — the right IP address for an A record, the right mail provider entirely for MX records, and the right verification string entirely for a TXT record used specifically in email authentication. A mismatch here is frequently the entire explanation for whatever problem prompted the lookup in the first place. Cross-referencing the result against documentation from whatever service requires the record, such as an email provider's setup guide, is often the fastest way to confirm whether what's currently configured actually matches what's required.
- Re-check after making DNS changes. If you've just recently updated a record at your domain registrar or DNS provider, query again after some reasonable time has passed to confirm the change has actually taken effect at the authoritative level, keeping in mind that other locations on the internet may still show the old cached value until their local cache naturally expires. Patience is genuinely part of the process here, since DNS propagation delays are a normal and expected part of how the system works, not a sign that something has gone wrong with the change itself. It's worth bookmarking this kind of lookup for the next time something domain-related breaks unexpectedly, since DNS misconfiguration is responsible for a disproportionate share of mysterious-seeming connectivity and email problems.
Use Cases
- Debugging why email isn't being delivered: Check a domain's MX records to confirm mail is correctly routed to the right provider, and check TXT records for SPF and DKIM configuration that affects deliverability.
- Verifying a website points to the correct server: Check a domain's A record to confirm it resolves to the IP address of the hosting provider it's actually supposed to be pointing at.
- Confirming domain ownership verification: Check TXT records to confirm a domain verification string required by a third-party service (like a CDN or email platform) was added correctly.
- Investigating a DNS migration: Check NS records to confirm a domain has been correctly delegated to a new DNS provider after a migration, and that the change has propagated.
- Troubleshooting a subdomain pointing to the wrong place: Check a subdomain's records directly to determine whether it's misconfigured at the DNS level rather than at the application or server level.
- Auditing a domain's DNS configuration before a change: Look up all relevant record types for a domain before making changes, to have a clear record of the prior configuration in case something needs to be reverted.
About This Tool
What is it? A browser-based tool that queries public DNS records — A, MX, NS, TXT, and others — for any domain, without requiring special access since DNS is a publicly queryable system.
Why use it? It's the fastest way to see exactly what a domain's DNS configuration actually says right now, which is usually the first and most useful step in debugging email delivery, hosting, or routing problems.
Alternatives: Command-line tools like dig or nslookup provide the same information but require a terminal and familiarity with their syntax; many domain registrars offer basic DNS lookup in their dashboards but often only for domains you manage; this tool works for any domain directly in a browser.
Common mistakes: Assuming a DNS change has failed because it isn't visible yet, without accounting for caching and time-to-live delays, is the most common mistake — the change may be correct at the authoritative source and simply not yet visible everywhere; the second is checking the wrong record type entirely, such as checking A records when an email delivery issue actually depends on MX and TXT records.
Frequently Asked Questions
- Is querying a domain's DNS records considered sensitive or private?
- No, DNS records are public by design — anyone can query them, including this tool, since that's how the DNS system is meant to function for the internet to work.
- Why do I see different results than someone else looking up the same domain?
- This is usually caused by DNS caching — different resolvers around the world may be serving a cached answer with different remaining time-to-live, especially shortly after a record was changed.
- How long does it take for a DNS change to fully propagate?
- This depends on the time-to-live value of the previous record; once that TTL expires everywhere, resolvers are required to fetch the updated value, which can take anywhere from minutes to about 48 hours depending on the prior TTL setting.
- What does an MX record actually control?
- MX records specify which mail servers are responsible for receiving email for a domain, along with a priority value used when multiple mail servers are configured.
- What are TXT records typically used for?
- TXT records hold arbitrary text data, commonly used for domain ownership verification, and for email authentication standards like SPF, DKIM, and DMARC that help prevent email spoofing.
- Can I look up DNS records for a domain I don't own?
- Yes, since DNS records are public information, you can look up records for any domain, not just ones you manage yourself.
- Does this tool modify DNS records?
- No, this tool only queries and displays existing DNS records; actually changing records requires access to the domain's registrar or DNS provider account.
- Why does a domain show no records for a particular type?
- This simply means no record of that type has been configured for the domain — for example, a domain with no custom email setup may have no MX records at all.