DNS Lookup

0 of 0 ratings

About DNS Lookup

DNS Lookup queries the public Domain Name System to fetch the IP addresses and name servers that a domain currently points to. It is a quick diagnostic for sysadmins, developers and SEOs who need to verify DNS propagation after a host change.

What it shows

A, AAAA, MX, NS, TXT and CNAME records.
Authoritative DNS server that answered the query.
Round-trip time in milliseconds.

Common use cases

Confirming that a new DNS record has propagated worldwide.
Checking whether a domain points to the right mail server (MX).
Verifying SPF, DKIM and DMARC TXT records during email deliverability work.
Investigating why a website appears offline in some regions.

Limitations

DNS lookups reflect cached answers from upstream resolvers. If you recently edited a record and propagation is still in progress, repeat the query after a few minutes.

What is a DNS Lookup?

A DNS (Domain Name System) lookup queries the worldwide domain-name directory and returns the records that tell your browser, email client and other services where a domain actually lives. Every time you visit a website, your device silently performs one of these lookups long before the page loads. This tool runs the same query against the public DNS, giving you a clear, human-readable answer about any domain instead of a confusing wall of command-line output.

How to Use This DNS Lookup Tool

Enter a domain (for example google.com or bagiqo.com) and press the Lookup button. Within a second the results appear as a clean table of records: the record type (A, AAAA, MX, TXT, NS, CNAME), the host it applies to, the time-to-live (TTL) in seconds, and the resolved value such as an IP address or mail server name. A records return IPv4 addresses, AAAA records return IPv6 addresses, MX records reveal the inbound mail servers (often with a priority number), NS records list the authoritative name servers, and TXT records expose SPF and verification strings. You can run as many lookups as you like — free, no sign-up required.

Common Use Cases

This tool is built for developer diagnostics, not just curiosity. Use it to confirm that your site A record points at the right server after a hosting move or a Cloudflare switch. Check that MX records match your email provider before you migrate mail. Verify TTL values when you have just changed a record and are waiting for propagation. Look up your own domain after a fresh registration to make sure the nameservers took effect. And if a service reports a DNS problem, a quick lookup tells you instantly whether the records resolve at all.

Limitations Worth Knowing

The results reflect the publicly visible DNS, which may for a short window be stale if records were just changed, because TTLs and DNS caching delay propagation. This tool resolves the domain over the public internet; it does not inspect records that are only visible on a private or split-horizon DNS, and it does not contact a mail server directly. For authoritative checks immediately after an edit, lower the TTL first, wait for the old TTL to expire, and re-query.

Frequently asked questions

What is the difference between an A record and an AAAA record?

A records map a hostname to an IPv4 address (for example 142.250.72.14), while AAAA records map a hostname to an IPv6 address. IPv6 addresses are longer, for example 2607:f8b0:4005:808::2004. Most modern domains have both so they work on either protocol.

Why does the TTL matter?

The time-to-live is the number of seconds that a resolver is allowed to cache a record before asking for a fresh copy. A short TTL (300 seconds, for example) means changes propagate quickly after you edit a record, which is why you should lower it before a migration and restore it afterwards.

How can I check whether my email is set up correctly?

Look for the MX records. They list the mail servers that accept mail for your domain, usually with a priority number where a lower number is preferred. If your MX records match your email provider, inbound mail should be routed correctly.

What does it mean if no records are returned?

If a domain returns no A or AAAA records, it is not published on the public DNS for that record type, so standard web traffic cannot reach it. A missing MX record, by contrast, simply means no mail server is published, and mail to that domain will fail.