DNS Lookup Tool — Check DNS Records Online Free
Instantly query A, AAAA, MX, TXT, NS, CNAME, and SOA records for any domain. No signup required — runs entirely on our server, results delivered in seconds.
⏱ 8 min read · Complete guide below
How the DNS Lookup Tool Works
- 1Enter a domain name (e.g.
example.com) in the input field. You can paste full URLs — the protocol and path are stripped automatically. - 2Click Lookup. Our server queries all seven DNS record types in parallel — A, AAAA, MX, TXT, NS, CNAME, and SOA — and returns the results simultaneously.
- 3Use the record type tabs to switch between result sets. Tabs with no records are dimmed so you can immediately see which types are configured.
- 4MX records are sorted by priority. TXT records display each string value clearly. SOA records show all zone parameters in a labelled table.
Common DNS Record Types Explained
Every domain is controlled by its DNS records — small data entries that map names to values. A records and AAAA records are the most fundamental: they translate a domain like example.com into a routable IP address. Without them, browsers cannot connect to a website.
MX records govern email routing. When you send email to user@example.com, the sending server looks up the MX records for example.com to find the destination mail server. SPF and DKIM policies live in TXT records, alongside third-party ownership verification tokens from Google, Facebook, and others.NS records identify which nameservers are authoritative for the domain — changing these is what "pointing your domain" to a new host actually means.
DNS Troubleshooting Tips
Check MX records before blaming email
When email is not arriving, the first thing to check is whether MX records exist and point to the correct mail server. A missing or mistyped MX record silently drops all inbound email.
Verify SPF with TXT lookup
Look up TXT records on your root domain and confirm a record beginning with "v=spf1" exists. An SPF record that is missing or incorrectly formatted causes major providers to reject or spam-folder your emails.
Use the SOA serial to track propagation
After making DNS changes, check the SOA serial number across multiple resolvers. If different resolvers return different serials, propagation is still in progress and some users may see old records.
CNAME and root domains do not mix
A CNAME record cannot be placed on a bare apex domain (example.com) — only on subdomains (www.example.com). If you need to alias a root domain, use ALIAS or ANAME records if your DNS provider supports them.
Low TTL before a migration
Before moving a site to a new server, lower your A record TTL to 300 seconds a day in advance. When you switch the IP, old values expire within 5 minutes rather than 24 hours, minimising downtime.
Multiple MX records for redundancy
Configure at least two MX records with different priorities. If the primary server is unreachable, sending servers retry the next-highest-priority server automatically. A single MX record is a single point of failure for email.
How DNS Resolution Actually Works
The Domain Name System is often called the phone book of the internet, and the analogy is apt: it translates human-friendly names like example.com into the numeric IP addresses computers actually use to connect. But the process behind a single lookup is a small, elegant relay race that happens in milliseconds every time you visit a website, and understanding it demystifies most DNS problems.
When your browser needs an address, it asks a recursive resolver (usually run by your ISP or a service like Cloudflare or Google). If the resolver does not already have the answer cached, it begins a journey up the DNS hierarchy. First it asks a root server, which points it to the TLD server for the extension (the “.com” servers). The TLD server points to the domain's authoritative nameserver — the one that actually holds the records — which finally returns the answer. The resolver caches that result for a set time and hands it back to you. This hierarchical, cached design is what lets a system serving trillions of daily queries stay fast and resilient.
DNS and Email Security: SPF, DKIM, and DMARC
One of the most important modern uses of DNS is authenticating email, because the humble TXT record is what stops much of the world's spam and spoofing. Three related standards, all published as DNS records, work together. SPF (Sender Policy Framework) is a TXT record listing which mail servers are allowed to send email for your domain, so a receiving server can reject mail from unauthorised sources. DKIM (DomainKeys Identified Mail) publishes a public key in DNS that lets receivers verify a cryptographic signature on your emails, proving they were not tampered with and genuinely came from your domain.
DMARC ties the two together: a DMARC TXT record tells receiving servers what to do with email that fails SPF or DKIM checks (allow, quarantine to spam, or reject outright) and where to send reports. Getting these three right is essential for deliverability — misconfigured or missing records are a leading reason legitimate email lands in spam folders or bounces entirely. Being able to inspect a domain's TXT records is exactly how you diagnose these issues, which is why an email administrator spends a lot of time in DNS.
DNS Propagation and TTL
A concept that confuses many people is why DNS changes are not instant. When you update a record, the new value does not reach the whole internet immediately — a delay commonly called propagation. The reason is caching: every record has a TTL (time to live), a number of seconds that resolvers are allowed to remember the old answer. Until a cached record's TTL expires, resolvers keep serving the previous value, which is why a change can appear to work for you but not for someone else whose resolver still holds the old record.
This gives rise to a valuable practical technique for planned migrations: lower the TTL in advance. A day before switching servers, reduce the relevant record's TTL from, say, 24 hours to 5 minutes. Then when you make the actual change, old cached values expire within minutes rather than a full day, dramatically shrinking the window in which some visitors reach the old server. Checking the SOA serial number across multiple resolvers is another way to gauge whether a change has propagated. Between resolution, caching, and TTL, most “weird” DNS behaviour has a straightforward explanation once you know how the pieces fit — and a lookup tool that queries the authoritative records directly is how you check what the truth actually is at any moment.
Frequently Asked Questions
What is a DNS lookup?
A DNS lookup queries the Domain Name System to retrieve records associated with a domain. When you visit a website, your browser performs an A record lookup to find the IP address behind the domain name. This tool lets you inspect all record types — not just A records — which is useful for troubleshooting email delivery, verifying domain ownership, or auditing DNS configuration.
What do the different record types mean?
A records map a domain to an IPv4 address. AAAA records map to IPv6. MX records specify which mail servers handle email for the domain. TXT records store free-form text — commonly used for SPF policies, DKIM keys, and domain ownership verification. NS records list the authoritative nameservers. CNAME records point a name to another name (an alias). SOA records contain zone metadata like the primary nameserver and serial number.
Why does a record type show "No records found"?
Not every domain has every record type. For example, a domain that does not send email will have no MX records. A domain that is not aliased will have no CNAME records. "No records found" means the DNS resolver received a response confirming no records of that type exist — it is not an error.
How do I verify an SPF or DKIM record?
SPF records are stored as TXT records on the root domain (e.g. example.com). Look in the TXT tab and find a record starting with "v=spf1". DKIM records are also TXT records but stored on a subdomain like selector._domainkey.example.com — enter that subdomain directly in the tool and look at the TXT results.
Why might results differ from other DNS tools?
Different tools use different resolvers. This tool uses the server-side DNS resolver, which may return different results than your local ISP resolver if DNS propagation is still in progress, if your ISP has cached stale records, or if the domain has a low TTL. For the most authoritative answer, compare results against multiple resolvers.
Does this tool store the domains I look up?
No. The domain name is sent to our server to perform the lookup, but results are returned immediately and the domain is not logged or stored. No account or signup is required.
What is the SOA record and when should I check it?
The Start of Authority record contains administrative information about the DNS zone: which nameserver is primary, the contact email (hostmaster), the serial number (used to trigger zone transfers), and timing parameters like refresh, retry, and expire intervals. Check the SOA when troubleshooting DNS propagation, zone transfers, or secondary nameserver synchronisation.
Why does the MX lookup matter for email deliverability?
MX records tell other mail servers where to deliver email for your domain. Missing or misconfigured MX records mean email sent to your domain will bounce. The priority number determines delivery order — lower numbers are tried first. Multiple MX records provide redundancy if the primary mail server is unreachable.