We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Check domain DNS records online. Instantly look up A, AAAA, CNAME, MX, and NS records with support for custom DNS servers.
The DNS (Domain Name System) lookup tool helps you quickly view various DNS records for a domain name. It supports querying multiple types such as A records (IPv4 address), AAAA records (IPv6 address), CNAME (alias), MX (mail server), and TXT (text record). You can also choose to query all record types to get complete DNS information at once.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Enter a domain name, choose a record type, and run a DNS lookup. The result is the response available through the resolver used for this query. This is useful for checking which addresses, mail hosts, aliases, or other DNS data are being returned. It is a record lookup in a browser interface, rather than a full command-line nslookup session: there is no field here to choose a DNS server for an individual query.
Available choices include A (IPv4 address), AAAA (IPv6 address), CNAME (alias target), MX (mail exchange), NS (name server), TXT (text data), SOA (zone authority data), PTR (reverse lookup), SRV (service details), CAA (certificate authority policy), and ALL. The ALL choice requests the available types together; types that return no result may simply be absent. Some records appear as structured fields rather than a single text value.
DNS resource records associate a name and type with data. TTL, where provided, is a time interval in seconds for which a record may be cached before it should be consulted again. A record result helps explain name resolution, but does not establish that a website is reachable or that its application is healthy.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Type the domain or hostname to investigate, such as example.com or mail.example.com. For a reverse lookup, use a name in the reverse-DNS form appropriate to the address rather than assuming a bare IP address is interchangeable with a hostname.
Use A or AAAA for address records, MX for mail routing, NS for delegated name servers, TXT for published text, or a more specific type such as CAA, SRV, SOA, or PTR. Choose ALL when you want a combined view of the supported types.
Submit the lookup and review each returned record group. Multiple values can be normal. Copy an individual value when you need it for a note or comparison. An empty result for one type means no value was returned in that response; it does not by itself explain why.
For example, an A lookup asks for IPv4 address data, while an MX lookup asks which mail exchange hosts are listed. Those are different DNS questions even when they use the same domain.
Use cases
See how the tool fits into real work and everyday tasks.
A site owner can inspect A and AAAA answers for a hostname and compare them with the addresses expected in the current DNS setup.
An administrator can query MX records to see the mail host names and priority data published for a domain before investigating a delivery issue further.
A developer checking a domain verification or policy string can use TXT or CAA results as a quick view of the resolver’s response, then compare with the authoritative zone configuration.
Q&A
Find concise answers to common questions and confusing cases.
No. This page exposes domain and record-type inputs, but not a per-query DNS server selector. A command-line nslookup workflow can accept an explicit server; use that workflow when you need to compare named resolvers.
The combined query omits record types that produced no value or an individual lookup error. A missing type is not proof that every DNS server would return the same response; check the specific type and resolver context.
No. It means an IPv4 address was returned through the resolver for the lookup. It does not test a network route, port, TLS certificate, web server, or application response.
Notes
Review scope, result limitations, and important precautions before use.
Related
Discover related tools, collections, and available API capabilities.