How to use the DNS lookup tool
Enter any domain name in the input field (without the https:// prefix). Select the record types you want to query using the toggle buttons—A, AAAA, MX, NS, and TXT are selected by default as they cover the most common use cases. Click "Lookup" to query Google's public DNS resolver for the selected record types.
Results appear instantly in the right panel, organized by record type with color-coded labels. Each record shows its type, value, TTL (time to live), and the queried name. You can click "Copy All" to copy the complete results to your clipboard in a tab-separated format suitable for documentation or further analysis.
Use this tool to verify DNS propagation after making changes, debug email delivery issues by checking MX records, confirm nameserver delegation with NS records, verify domain ownership with TXT records, or troubleshoot connectivity by checking A and AAAA records. The tool queries Google DNS (8.8.8.8) so results reflect what most of the internet sees.
Understanding DNS record types
A records are the foundation of DNS—they map a domain to an IPv4 address (like 93.184.216.34). AAAA records serve the same purpose for IPv6 addresses (like 2606:2800:220:1:248:1893:25c8:1946). As the internet transitions to IPv6, both record types are important for ensuring your site is reachable from all networks.
MX records direct email to the correct mail server. Each MX record has a priority number—mail is delivered to the server with the lowest priority value first. If that server is unavailable, the next priority server is tried. Organizations using services like Google Workspace or Microsoft 365 need specific MX records pointing to their provider's mail servers.
NS records identify the authoritative nameservers for a domain. These are the servers that hold the definitive DNS records. When you register a domain or change hosting providers, updating NS records is often the first step. TXT records are versatile—they hold SPF records for email authentication, DKIM keys, DMARC policies, and domain verification tokens for services like Google Search Console and SSL certificate authorities.
DNS propagation and troubleshooting
DNS changes don't take effect instantly. When you update a record, the old record may be cached by resolvers worldwide for up to the TTL duration. This means changes can take minutes to hours (rarely more than 48 hours) to propagate globally. During propagation, different users may see different results depending on which cached version their resolver holds.
To speed up propagation, lower the TTL of records you plan to change 24-48 hours before making the change. After the change, the low TTL ensures resolvers refresh quickly. Once the change has propagated, you can increase the TTL back to a higher value. This technique is standard practice for DNS migrations and server moves.
Common troubleshooting scenarios include: email not being delivered (check MX records), website showing wrong content (check A/AAAA and CNAME records), SSL certificate issues (check CAA records), and email going to spam (check TXT records for SPF, DKIM, and DMARC configuration). This tool helps diagnose all of these issues quickly.
Frequently Asked Questions
What is a DNS lookup?
A DNS lookup queries Domain Name System servers to retrieve the records associated with a domain name. These records map human-readable domain names to IP addresses, mail servers, nameservers, and other configurations. DNS is the fundamental system that makes the internet navigable—without it, you would need to remember IP addresses for every website.
What is an A record?
An A (Address) record maps a domain name to an IPv4 address. When you type a domain into your browser, the DNS resolver looks up the A record to find the server's IP address. A domain can have multiple A records for load balancing or redundancy. The AAAA record is the IPv6 equivalent, mapping to a 128-bit IPv6 address.
What is an MX record?
An MX (Mail Exchange) record specifies the mail servers responsible for receiving email for a domain. MX records include a priority value—lower numbers indicate higher priority. When sending email to user@example.com, the sending server queries MX records for example.com and delivers to the highest-priority (lowest number) available mail server.
What is TTL in DNS?
TTL (Time To Live) is the duration in seconds that a DNS record should be cached by resolvers and clients. A TTL of 3600 means the record is cached for one hour before a fresh lookup is needed. Lower TTLs mean faster propagation of changes but more DNS queries. Higher TTLs reduce DNS traffic but delay updates. Common TTLs range from 300 (5 minutes) to 86400 (24 hours).
What is a TXT record used for?
TXT records store arbitrary text data associated with a domain. They are commonly used for email authentication (SPF, DKIM, DMARC), domain ownership verification (Google Search Console, Let's Encrypt), and security policies. A domain can have multiple TXT records, each serving a different purpose. TXT records are essential for email deliverability and preventing spoofing.
How does this tool query DNS?
This tool uses the Google DNS-over-HTTPS API (dns.google) to perform DNS queries. Your browser sends HTTPS requests to Google's public DNS resolver, which returns JSON-formatted DNS responses. This method works entirely from the browser without needing local DNS tools. The queries use Google's 8.8.8.8 and 8.8.4.4 resolvers.
Privacy and methodology
This tool queries Google's public DNS-over-HTTPS API (dns.google/resolve) directly from your browser. Domain queries are sent to Google's DNS resolver and are subject to Google's privacy policy. No domain queries are stored or logged by Tool Vault. Results are displayed in your browser and not transmitted anywhere else. For sensitive domains, consider using a local DNS tool like dig or nslookup.