DNS lookup

What is the DNS lookup tool?

The DNS lookup tool queries the public domain name system for a domain you supply and returns the current set of DNS records published for it. You type a domain into the form and submit it, and the server performs a live set of record queries, assembling the answers that name servers return into readable, labeled records rather than raw protocol output. What comes back is a snapshot of how that domain is configured on the network at the moment of the request.

DNS is the infrastructure that maps a human-readable name such as example.com to the resources that actually serve a site, mail, or other service on the network. A single domain can carry many record types at once: address records that point a name at a server's IP, mail exchange records that route email, text records used for provider verification and email authentication, and more. This tool gathers the commonly published types together so you can see the whole configuration in one place instead of running several separate lookups yourself or digging through a hosting control panel.

What the DNS lookup tool returns

Submit a domain and the tool returns the DNS records currently published for it, organized by type. Address records (A and AAAA) show the IPv4 and IPv6 addresses the name resolves to, CNAME records show where an alias points, MX records list the mail servers and their priority order, TXT records expose the text entries used for SPF, DKIM, and ownership verification, NS records show the authoritative name servers, and SOA records reveal the primary source of authority together with its refresh and expiry timings. The exact set you see depends on what has been published for the domain you query.

Each returned record is shown with its type, name, and value, and where the protocol exposes it, its TTL. That means you can read off the configuration without translating numeric record data yourself. The output reflects the DNS state as it is visible across the public name server system from the server that performs the query, so the results represent the live system on the network rather than a locally held copy.

Because the lookup runs server-side and contacts the name server system directly, the answers are fetched from the network at the moment you submit. Record types that have nothing published for the domain are simply absent from the output instead of being reported as an error, which keeps the result a clean list of what actually exists.

Reading the records together is where the tool earns its keep in everyday troubleshooting. A CNAME that points a subdomain at a root domain can tell you which address record actually resolves; an MX entry with a low priority number tells you which mail server gets contacted first; and a set of NS records that does not match the registrar's list often explains why a change has not taken effect. The value of a single combined listing is that these connections become visible in one screen, without you having to issue separate queries and mentally merge the answers.

How to use the DNS lookup tool

Checking a domain's records takes a single submission; you only need to know the domain name you want to inspect.

1. Type the domain you want to check into the domain field, for example example.com, without a protocol prefix such as https:// and without a trailing slash.
2. Select the record types you want returned if the tool offers a choice, or leave the default set enabled for a full picture.
3. Submit the form and wait for the server to query the domain and assemble the records that are currently published.
4. Read the returned table, noting the type, the value, and, for mail records, the priority number that determines delivery order.
5. Copy the values you need into your own notes or configuration, or compare them against what your DNS provider shows in its control panel.

How to get better results

• Enter the domain without a www prefix and without a protocol such as http or https, since name records belong to the domain itself and a prefixed entry produces no usable answer.
• Query the bare domain and the www subdomain separately, because these frequently hold different records, and telling them apart is exactly the kind of detail DNS problems hide in.
• Check the TXT records specifically whenever email is involved, since SPF, DKIM, and DMARC entries all live there and a missing one is a common cause of rejected or misrouted mail.
• Compare the NS records the lookup returns with the name servers your registrar lists, because a mismatch between the two is a frequent reason a domain behaves unexpectedly.
• Re-run the lookup after you change anything in your DNS provider, since propagation makes old values linger, and a fresh query confirms what is actually visible right now.
• Remember that the result reflects the live public system, so if a value looks wrong, check whether a change is still propagating before assuming the lookup failed.

Why the DNS lookup tool matters

DNS problems are notoriously hard to diagnose from symptoms. A site that fails to load, email that lands at the wrong server, or a subdomain that resolves nowhere can each be caused by a record that is missing, stale, or misplaced, and none of these announce their cause in the page you see or the message you receive. Being able to pull the actual records for a domain and read them side by side turns a vague symptom into a concrete list of values you can compare against what you intended to publish.

The tool matters for routine administration as well. When you move hosting, change mail providers, or add a verification record, the moment of truth is what the public name servers serve, not what your control panel claims to be serving. A quick lookup reconciles the two. For anyone who manages domains, checks configuration after migrations, or investigates why a domain misbehaves, having the current record set one submission away removes guesswork and spares you from running several separate queries against a handful of services to assemble the same picture.

There is also a documentation angle. When you hand a site over to a client or a new team, the DNS configuration is usually the least documented part of the handover, even though it underpins mail, hosting, and verification. A lookup taken at handover time gives you a recorded snapshot of the records as they actually are, which becomes a reference point when the new team later asks why a change behaves a certain way. The same snapshot is useful internally whenever a provider change is in progress and you want a before-and-after comparison of what the domain publishes.

When to use the DNS lookup tool

• When a freshly registered or recently moved domain fails to load and you want to confirm that the expected A records are actually being served publicly.
• When you finish migrating to a new host or cloud server and need to verify that the address records now point at the new server and nowhere else.
• When email from a domain is rejected or ignored and you want to inspect the MX, SPF, and DKIM text records in one place.
• When you are about to add a TXT verification record for a service such as a search console or a mail authentication provider and want to see the current entries first.

Related SEO Tools

Complete your SEO workflow with these related free tools:

• SERP checker - Get the top search engine results for a keyword.
• Indexed pages checker - Check if a domain is indexed by search engines.
• Website status checker - Check the status and availability of a website. Verify a site is online and responding before sharing or monitoring it.
• SSL checker - Check the SSL status and information of a domain. Review certificate validity, issuer, and expiry for a site.

Related SEO Guides

Learn more about this topic with our in-depth guides:

• DNS Lookup Explained: What Your Domain Records Reveal
• WHOIS Lookup Guide: Find Domain Owner Information

Frequently asked questions

What record types does the lookup cover?

The tool returns the commonly published record types for a domain, including A, AAAA, CNAME, MX, TXT, NS, and SOA. Types for which the domain has no published answer are simply absent from the result.

Should I enter the domain with www?

Enter the domain name on its own. The www subdomain often carries its own separate records, so if you specifically need those, query the domain with the www prefix as a second entry.

Are the results live, or are they cached?

The records are fetched from the public name server system at the moment you submit the form, so the output reflects the DNS state that is visible on the network at that time rather than stored data from a previous query.

Why does the tool show nothing for a particular type?

A record type appears with no entries when the domain simply has none published of that kind. The lookup reports what exists instead of listing empty placeholders for everything that is not configured.

Can this lookup prove that a DNS change has propagated?

Yes. Run the lookup before and after a change; when the returned value matches what you published in your provider's panel, the change has reached the public system and is being served to everyone.

Why would I run a lookup if my site already works?

Working sites still deserve occasional checks. Records drift during certificate renewals, host moves, or delegated subdomains, and catching a mispointed record before it becomes an outage is cheaper than debugging an incident that is already live.