DNS is the backbone of every email system, web application, and network service on the internet. Our free DNS lookup tool lets you query any domain and inspect the full set of resource records defined in RFC 1035 and its successors. Whether you are troubleshooting mail delivery failures or auditing a domain's infrastructure, this tool returns authoritative results in seconds.
How the DNS Lookup Works
Enter a domain name and select the record type you want to query. The tool resolves the domain against multiple recursive resolvers, returning the raw response along with TTL values and any associated flags. You can query individual record types or run a comprehensive scan that pulls every common record type at once.
DNS Record Types Explained
A Records
An A record maps a hostname to an IPv4 address. This is the most fundamental DNS record type and the one your browser resolves every time you visit a website. If a domain has no A record, HTTP connections will fail outright.
AAAA Records
AAAA records serve the same purpose as A records but return an IPv6 address instead. With IPv6 adoption accelerating across major ISPs, verifying that your domain publishes AAAA records is increasingly important for global reachability.
MX Records
Mail Exchange records define which servers accept email for a domain. Each MX record carries a priority value; lower numbers indicate higher preference. When an SMTP server attempts delivery, it tries the lowest-priority MX host first and falls back to higher values if the primary is unreachable. Use our dedicated MX Lookup tool for deeper mail-server analysis.
TXT Records
TXT records hold arbitrary text strings and have become critical for email authentication. SPF policies, DKIM public keys, and DMARC policies are all published as TXT records. Run a quick SPF Check, DKIM Verify, or DMARC Analyze to validate these individually.
CNAME Records
A Canonical Name record aliases one hostname to another. CNAMEs are common for subdomains like mail.example.com pointing to a hosted provider's hostname. Per RFC 1035, a CNAME cannot coexist with other record types at the same name, which is a frequent misconfiguration that breaks DNS resolution.
NS Records
Name Server records delegate authority for a zone to specific DNS servers. Misconfigured NS records, such as pointing to non-responsive nameservers or lame delegations, can cause intermittent resolution failures across the entire domain.
SOA Records
The Start of Authority record contains metadata about the DNS zone: the primary nameserver, the responsible party's email address, the zone serial number, and timing parameters for refresh, retry, expire, and minimum TTL. The SOA serial number is especially useful when verifying that zone updates have propagated to all authoritative servers.
Why DNS Lookups Matter for Email
Every stage of email delivery depends on DNS. The sending server resolves MX records to find the recipient's mail server. The receiving server queries TXT records to validate SPF, DKIM, and DMARC. IP reputation checks often involve reverse DNS lookups. A single misconfigured record can cause messages to bounce, land in spam, or vanish entirely.
Gmail, Outlook, and Yahoo all perform strict DNS-based authentication checks. Gmail in particular requires a valid PTR record, published SPF, and DKIM alignment before granting full inbox placement. Running a Full Report through InboxTooling covers all of these checks in one pass.
Interpreting Your Results
Pay attention to TTL values. A very low TTL (under 300 seconds) suggests the domain operator expects frequent changes, while a high TTL (86400 seconds) indicates a stable configuration. If you have recently made DNS changes and the old values still appear, the TTL on the previous record has not yet expired. Check propagation status to confirm global consistency.
Look for inconsistencies between authoritative and recursive resolver responses. If they differ, caching or propagation lag is the likely cause.
Common DNS Misconfigurations
- Missing or incorrect MX records causing mail to bounce with "no mail exchanger" errors.
- CNAME at the zone apex, which violates RFC 1035 and breaks other record types.
- Lame NS delegations where the listed nameserver does not respond authoritatively.
- Conflicting TXT records that exceed the 255-byte string limit without proper concatenation.
Use InboxTooling's DNS lookup regularly to audit your domain and catch these issues before they affect production traffic.
FAQ
What is a DNS record?
A DNS record is an entry in the Domain Name System that maps a domain name to a specific piece of information, such as an IP address, mail server, or text string. DNS records are stored on authoritative name servers and are queried by resolvers whenever a device needs to connect to a service using a domain name. Without DNS records, browsers and email servers would have no way to locate the correct destination for your traffic. You can inspect any domain's records instantly using our DNS Lookup tool.
How do I look up DNS records for a domain?
Enter the domain name into the DNS Lookup tool and select the record type you want to query, or choose a comprehensive scan to retrieve all common types at once. The tool queries multiple recursive resolvers and returns the raw records along with TTL values within seconds. No account or installation is required.
What are the most common DNS record types?
The most frequently used DNS record types are A (IPv4 address), AAAA (IPv6 address), MX (mail exchange), TXT (text strings used for SPF, DKIM, and DMARC), CNAME (canonical name alias), NS (name server delegation), and SOA (start of authority). Each type serves a distinct purpose in routing traffic and authenticating services. Our DNS Lookup tool supports querying all of these record types.
How long do DNS changes take to propagate?
DNS changes can take anywhere from a few minutes to 48 hours to propagate globally, depending on the TTL value set on the previous record. Resolvers cache records for the duration of the TTL, so a record with a TTL of 3600 seconds may take up to one hour to update everywhere. Lowering the TTL before making changes can speed up propagation significantly.
What is DNS TTL?
TTL stands for Time to Live and is a value, measured in seconds, that tells DNS resolvers how long they should cache a record before requesting a fresh copy from the authoritative server. A low TTL (e.g., 300 seconds) means resolvers will refresh the record frequently, which is useful during migrations, while a high TTL (e.g., 86400 seconds) reduces query load but delays the visibility of updates. You can check the current TTL for any record using the DNS Lookup tool.
Stay on top of your email infrastructure. Sign up for the InboxTooling newsletter for deliverability tips, tool updates, and best practices.