Email stops arriving. A site loads from the wrong server after a move. Google asks you to add a TXT record to prove you own a domain. In each case the answer sits in the domain's DNS records, and you cannot fix what you cannot see. Kwebby's Find DNS Records tool reads those records for any domain or subdomain and checks nine types: A, AAAA, MX, TXT, NS, CNAME, SOA, CAA and SRV. You enter the domain, click Lookup, and read the current results.
Key Takeaways
- Kwebby's Find DNS Records tool looks up A, AAAA, MX, TXT, NS, CNAME, SOA, CAA and SRV records for any domain or subdomain and shows each record with its TTL.
- A and AAAA records point a domain to an IPv4 or IPv6 address, MX records route email, and NS records name the servers that manage the domain's DNS.
- TXT records carry domain verification codes and email authentication data such as SPF and DKIM, so they matter for both Google Search Console and email delivery.
- The tool asks Google Public DNS, a caching resolver, so a record you just changed can show its old value until its TTL runs out.
- These nine record types cover most everyday checks. For rarer types, a command line tool such as dig can query them one by one.
- The tool is free and needs no account.
What Is the Kwebby Find DNS Records Tool?
The Kwebby Find DNS Records tool is a free DNS lookup that shows the records stored for any domain. Enter a domain or subdomain and click Lookup to see its A, AAAA, MX, TXT, NS, CNAME, SOA, CAA and SRV records. The tool queries Google Public DNS over HTTPS when you click, so you see what that resolver returns at that moment. No account is needed.
DNS records are instructions stored at a domain's nameservers. They tell the internet where the domain's website, email and other services live. The tool turns those instructions into a readable list.
Key Features and How It Works
One lookup checks all nine record types, so you do not run a separate query for each. Types with no records are left out of the result. Here is what each part of the result gives you.
Nine Record Types in One Lookup
The tool retrieves A, AAAA, MX, TXT, NS, CNAME, SOA, CAA and SRV records together. CAA records name the certificate authorities allowed to issue certificates for the domain, and SRV records locate services such as SIP or XMPP; most domains have neither at the top level. These are the types you meet most often when you manage a website, an email setup or a domain move. A single lookup replaces nine separate command line queries.
Current DNS Data
The tool queries live DNS data and shows the current state of the domain's records. That makes it a good first stop after a change, because you see what DNS says now and not what a dashboard says it should be.
Hosting and Nameserver Clues
The A record shows the IP address of the server that hosts the site. The NS records show which provider runs the domain's DNS. Together they tell you who to contact and where to make changes. To identify the hosting company behind an IP, open the Domain Hosting Checker.
Mail Setup at a Glance
MX records list the mail servers for the domain, and the priority values decide which server is tried first. If the MX list is empty or points to the wrong provider, email delivery fails. The TXT records beside it often hold the SPF and DKIM data that receiving servers use to judge your mail.
Why Finding DNS Records Matters
DNS records control where your traffic and your email go, so one wrong value can take a site offline or stop messages from arriving. Cloudflare's guide to DNS records describes A records as holding a domain's IP address, MX records as directing mail to an email server, and TXT records as often used for email security.
Most DNS problems are not mysterious. A site migration leaves the A record pointing to the old host. A new email provider needs an MX change that nobody made. A verification code never got added as a TXT record. Reading the records takes a minute and often ends the guesswork.
How to Use the Find DNS Records Tool
Looking up a domain takes five steps.
- Enter the domain. Type the domain name, such as
example.com, into the input field. - Click Lookup. The tool retrieves the domain's DNS records.
- Read each record type. Check the A and AAAA values for the web server, the MX values for email, the TXT values for verification and authentication, and the NS values for the DNS provider.
- Compare with what you expect. Open your registrar or DNS host and compare the values side by side. Any mismatch is your lead.
- Check again after a change. After you edit a record, run the lookup again later to see whether the new value is live.
What Each Record Type Tells You
- A record: maps the domain to an IPv4 address. It is the main link between your domain and its hosting server.
- AAAA record: maps the domain to an IPv6 address, the equivalent of the A record for IPv6 networks.
- MX record: names the mail servers for the domain. Priority values decide which server is tried first.
- TXT record: stores text data. Common uses are domain ownership proofs, SPF records and DKIM keys.
- NS record: lists the nameservers responsible for the domain's DNS. Changing NS records hands DNS management to a new provider.
- CNAME record: points an alias to another domain name. You often see it on subdomains such as
wwwand on records that point to a CDN or hosting provider. - SOA record: holds administrative information, including the primary nameserver and a serial number that versions the DNS zone.
Best Practices for Finding and Checking DNS Records
A good DNS check starts with the symptom and ends with a recorded result. These habits keep you from chasing the wrong record.
Match the Record Type to the Symptom
Email problems point to MX and TXT records. A site that shows the wrong content points to A, AAAA or CNAME records. A domain that moved providers points to NS records. Start with the matching type and you skip most of the noise.
Save the Current Records Before You Edit
Copy the lookup results before you change anything. If a new value breaks something, you can restore the old one in minutes. The common mistake is to edit a record from memory and then discover nobody wrote down the original.
Allow Time for Caching
DNS servers cache records, so a change does not appear everywhere at once. NsLookup.io notes that servers it queries usually answer with cached record sets and that changes take a while to propagate. Check again after a few hours before you decide the edit failed.
Copy TXT Values Exactly
A verification code or SPF string must match character for character. Stray spaces or extra quotation marks added during copy and paste are a frequent reason a check fails. Paste the value as your provider gives it.
Remember What a Lookup Cannot Show
A DNS lookup shows what DNS says. It does not show whether the server behind the A record is healthy. If the records look right but the site still fails, run the Server Status Checker next.
Common Use Cases
- Troubleshoot email delivery. Confirm the MX records point to your mail provider and the TXT records hold the SPF and DKIM data it asked for.
- Verify domain ownership. Check that the TXT record from Google Search Console or another service is in place.
- Confirm a hosting move. Compare the A record and the NS records with the new host's instructions.
- Check whether changes have propagated. Run the lookup before and after an edit to watch the new value appear.
- Audit nameserver setup. Review the NS records when you take over a domain or inherit a client site.
Related Kwebby Tools
The Find DNS Records tool belongs to the networking utilities in our Developer Tools collection. These tools fill in the picture:
- WHOIS Checker shows registration data for a domain, including the registrar and expiry date.
- Domain Hosting Checker finds who hosts a domain, based on its IP address and nameservers.
- Domain Into IP converts a domain name to its IPv4 and IPv6 addresses.
- Get HTTP Headers shows what the web server returns once DNS has sent the visitor there.
- Blacklist Lookup checks whether an IP address appears on spam blacklists, which helps when mail from your server is rejected.
Frequently Asked Questions (FAQs)
How do I find all DNS records for a domain?
Enter the domain in the Find DNS Records tool to see its A, AAAA, MX, TXT, NS, CNAME, SOA, CAA and SRV records at once. For other types, use a command line tool such as dig and query each type by name, for example dig example.com MX. A single query for every type is not always answered, so per-type queries are more reliable.
Where are my DNS records stored?
Your records live in a DNS zone on the authoritative nameservers for your domain. Those servers are usually run by your registrar, your hosting provider or a DNS service. The NS records in the lookup show which servers hold the zone.
How can I find the history of a DNS record?
The Find DNS Records tool shows the current state of a domain's records, not their history. For past values, check your DNS provider's change log if it keeps one, or use a service that archives DNS data over time.
How long do DNS changes take to show up?
Changes can take from a few minutes to many hours, depending on how long DNS servers cache the old record. The wait depends on the TTL of the old record, which the tool shows next to each record. Run the lookup again after the TTL has passed to see the new value.
What is an MX record and why does it matter?
An MX record names the mail server that handles email for a domain, and its priority value decides which server is tried first. Without correct MX records, email sent to the domain cannot be delivered. Check them whenever you change email providers.
Is the Find DNS Records tool free?
Yes. The tool is free and needs no account. Enter a domain and click Lookup.
Final Thoughts
DNS problems feel hard because the records are invisible until you look. The Find DNS Records tool makes them visible in one lookup, so you can match a symptom to a record type and fix the right thing. Start by saving the current records of your most important domain, then check them again after your next hosting, email or nameserver change. If the records are correct and the site still misbehaves, run the Server Status Checker to test the server itself.