Is this query private?

DNS lookups send the domain you enter and the requested record type to Google Public DNS over HTTPS. DNS lookup is an external network service, not local-only processing.

Why don't my changes show up yet?

DNS changes can take time to propagate across the internet, depending on the TTL settings of your specific records.

What is DNS-over-HTTPS and why does this tool use it?

DNS-over-HTTPS (DoH) sends DNS queries encrypted over HTTPS instead of plain UDP, preventing eavesdropping on which domains you look up. This tool uses public DoH endpoints from Google or Cloudflare.

Which record types can I query?

You can query A, AAAA, MX, TXT, CNAME, NS, SOA, and PTR records. Selecting ANY returns all available record types for a domain in one request.

How do I check if my SPF or DKIM record is set correctly?

Query the TXT records for your domain. SPF records start with 'v=spf1' and DKIM records are typically found under a selector subdomain like 'default._domainkey.yourdomain.com'.

Can I query DNS records from a specific resolver like Google or Cloudflare?

The DNS Lookup tool queries records using DNS-over-HTTPS (DoH). By default it uses Cloudflare's 1.1.1.1 resolver, which returns authoritative results and supports all common record types. If you need to compare results from different resolvers — useful for debugging propagation — you can manually run the same query against Google (8.8.8.8), OpenDNS, or your ISP's resolver from your system command line using dig or nslookup, then compare the outputs to identify caching or propagation discrepancies.

DNS Lookup — A, MX, TXT, CNAME Records | Free Online Tool

About DNS Lookup

Analyze domain name system records instantly. Our DNS Lookup tool provides detailed information about A, AAAA, MX, TXT, and CNAME records, essential for webmasters and network engineers troubleshooting domain configurations.

How to Use

Enter the domain name (e.g., example.com) into the search field.
Select the specific record type you want to query, or use 'ANY' for a full report.
Click 'Lookup DNS' to fetch real-time data from global DNS servers.
Review the TTL, Value, and Alias/CNAME configurations for proper routing.

Common Use Cases

Verifying DNS propagation after moving to a new hosting provider.
Troubleshooting email delivery issues by checking MX and SPF (TXT) records.
Checking domain pointing and CNAME configurations for proper routing.

Technical Details

Queries public DNS-over-HTTPS (DoH) endpoints like Google or Cloudflare to safely fetch real-time DNS information without exposing your local network details.

Frequently Asked Questions

Is this query private?: DNS lookups send the domain you enter and the requested record type to Google Public DNS over HTTPS. DNS lookup is an external network service, not local-only processing.
Why don't my changes show up yet?: DNS changes can take time to propagate across the internet, depending on the TTL settings of your specific records.
What is DNS-over-HTTPS and why does this tool use it?: DNS-over-HTTPS (DoH) sends DNS queries encrypted over HTTPS instead of plain UDP, preventing eavesdropping on which domains you look up. This tool uses public DoH endpoints from Google or Cloudflare.
Which record types can I query?: You can query A, AAAA, MX, TXT, CNAME, NS, SOA, and PTR records. Selecting ANY returns all available record types for a domain in one request.
How do I check if my SPF or DKIM record is set correctly?: Query the TXT records for your domain. SPF records start with 'v=spf1' and DKIM records are typically found under a selector subdomain like 'default._domainkey.yourdomain.com'.
Can I query DNS records from a specific resolver like Google or Cloudflare?: The DNS Lookup tool queries records using DNS-over-HTTPS (DoH). By default it uses Cloudflare's 1.1.1.1 resolver, which returns authoritative results and supports all common record types. If you need to compare results from different resolvers — useful for debugging propagation — you can manually run the same query against Google (8.8.8.8), OpenDNS, or your ISP's resolver from your system command line using dig or nslookup, then compare the outputs to identify caching or propagation discrepancies.

Local processing

Our local file, text and chart tools process content on your device using JavaScript, browser APIs and, where needed, WebAssembly. Our usage events do not include filenames, file contents, input text, chart values, raw errors, emails or license references. Network lookup tools (such as DNS, WHOIS, IP and speed tests) contact external services for their stated purpose. Loading the website, fonts, libraries and models also makes network requests. WebAssembly itself does not prevent network access.