Perform a DNS lookup for a domain and review A, AAAA, CNAME, MX, NS, TXT, SOA and other returned records with TTL and value details.
A DNS lookup shows the records that a domain name returns when it is queried through the server that performs the check. Enter a domain and the tool requests the available DNS data, then presents each response in a readable table with its record type, TTL, and value or target. This makes it useful for checking website addresses, mail routing, nameserver delegation, aliases, verification text, and basic zone information.
The lookup is a forward DNS check: it starts with a domain name and asks what records are published for that name. It is different from Reverse DNS Lookup, which starts with an IP address and asks whether a hostname is associated with it. A DNS result is a technical observation at a particular time and resolver; it is not proof that a website is online, that email is delivering, or that every network in the world sees the same answer.
Enter a hostname or domain in the lookup field, such as a root domain or a subdomain. You can paste a full web address, but the tool removes the web protocol, a leading www, and any path before it queries DNS. It also normalizes the name to lowercase. This is helpful when a copied address contains a page path that is meaningful to a browser but is not part of a DNS name.
The input still needs to look like a domain with a dot and a valid DNS response. A spelling mistake, an incomplete hostname, a newly created record, or a domain with no records can produce an error or an empty result. The tool does not edit a zone, register a domain, or choose a DNS provider. It reads the answer available to the application server, so record changes should be checked again after the relevant cache period and compared with the configuration held at the authoritative DNS provider.
Choose the hostname that matches the problem you are investigating. The apex domain, www hostname, mail hostname, and verification hostname can all have different records. If a hosting provider gives you a target for a subdomain, checking only the root domain may produce a perfectly valid result that says nothing about the service you are trying to fix. Repeating the lookup with the exact hostname avoids that common diagnostic shortcut.
An A record maps a name to an IPv4 address, while an AAAA record maps it to an IPv6 address. A domain may have multiple address records for load balancing, failover, or separate network paths. A CNAME record identifies an alias and points it to another hostname, so the final address may be returned by a later lookup. These records help explain where a web hostname is directed, but an address alone does not confirm that an HTTP service is responding.
An MX record identifies mail-exchange hostnames for a domain, and an NS record lists nameservers responsible for answering for a DNS zone. The table shows the record type, TTL, and a readable value or target returned by the resolver. It is useful for confirming whether a mail hostname or nameserver appears, but it does not send a test email, verify mailbox delivery, or prove that a nameserver is correctly delegated at every parent zone.
TXT records carry text published for many purposes, including domain verification and email policies such as SPF, DKIM, or DMARC-related values. The tool displays returned text so you can compare it with the value supplied by a service or DNS administrator. It does not interpret an SPF policy, cryptographically validate DKIM, evaluate DMARC alignment, or decide whether a verification token is safe to publish. Treat long TXT output as configuration data and check it carefully for missing quotes, spaces, or outdated entries.
The SOA record provides zone-level authority information and helps administrators understand which primary nameserver and timing data a zone publishes. The table presents the returned record data in a compact value or target column rather than turning every SOA field into a separate diagnostic. Each displayed record also has a TTL, measured in seconds. TTL tells caching resolvers how long an answer may be reused, so an old value can remain visible for a while after a change.
DNS propagation is therefore not a single switch that changes everywhere at once. Different recursive resolvers may have different cached answers, and a lookup from one server is only one observation. If you are checking a migration, nameserver change, email record, or verification token, save the time of the lookup, review the TTL, and repeat the check after the expected cache window. A different result is a reason to compare resolver paths, not immediate proof that the DNS provider ignored the change.
For a website problem, begin with the A and AAAA responses and check whether a CNAME is directing the hostname somewhere unexpected. For email, review MX targets and the TXT values used by the sending service. For delegation problems, inspect NS and SOA information and compare it with the nameservers configured for the domain. This separates a name-resolution problem from an application outage, certificate issue, or mail-server rejection that happens after DNS has already returned an answer.
Common mistakes include checking the root domain when the failing service uses a subdomain, forgetting that www and the apex can have different records, reading a CNAME as if it were an IP address, or assuming that a missing record is caused by propagation when the record was never created. An A record can be correct while an AAAA record sends some IPv6 users to a different service. Multiple MX records can also be intentional, so inspect the returned targets instead of deleting a record simply because more than one exists.
This DNS checker does not change records, test HTTP status, open mail connections, run DNSSEC validation, compare many geographic resolvers, or perform a complete security audit. It also does not replace the authoritative control panel or a detailed command-line diagnosis. Use the displayed record type, TTL, and value as evidence, then confirm important changes against the provider configuration, server logs, mail service settings, and a check from an authorised environment.