DNS Lookup

DNS (Domain Name System) translates human-readable domain names into IP addresses and stores other routing information. This tool queries multiple DNS record types for any domain using Google's public DNS-over-HTTPS API at dns.google. Supported record types include A (IPv4), AAAA (IPv6), MX (mail servers), CNAME (aliases), TXT (SPF, DKIM, verification), NS (nameservers), and SOA (zone authority).

Tip: Press Ctrl+Enter to lookup

What this tool does

This tool queries DNS records for any domain using Google's public DNS-over-HTTPS API. Select which record types to look up — A, AAAA, MX, CNAME, TXT, NS, SOA, PTR, SRV — and see values including TTL in seconds, right in your browser. Useful for verifying DNS changes, debugging email configuration, and inspecting domain settings without opening a terminal.

How to use it

  • Enter a domain name (e.g. example.com) and select the record types you want.
  • Click Lookup or press Ctrl+Enter.
  • Results show the record value, TTL, and priority (for MX records).
  • Click Copy All Results to copy the full output as text.

When to use each record type

  • A / AAAA — Verify that a domain resolves to the expected IP after a migration or deployment.
  • MX — Debug email delivery issues. Check priority order and confirm MX hostnames are correct.
  • TXT — Inspect SPF, DKIM, and DMARC records, or domain ownership verification strings for external services.
  • CNAME — Trace alias chains to confirm a subdomain points to the right target (CDN, SaaS provider, load balancer).
  • NS — Verify authoritative nameservers after migrating DNS to a new provider.

Frequently Asked Questions

What is TTL and why does it matter for DNS changes?

TTL (Time To Live) is how long, in seconds, resolvers may cache a record before re-querying. Before making a critical DNS change, lower the TTL to 60–300 seconds and wait for that TTL to expire. Then make the change — cached copies will expire quickly and the new value will propagate fast. Raise the TTL again after confirming everything works.

How long does DNS propagation take?

DNS propagation depends on the TTL of the record being changed and the caching behavior of resolvers worldwide. For records with a 1-hour TTL, most resolvers will have the new value within 1–4 hours. Records with a 24-hour TTL may take up to 48 hours. There's no global "push" of DNS changes — resolvers simply stop using cached values when they expire.

Why do I see different results from different DNS servers?

Different resolvers may have different cached values at different points during propagation. The ToolsKit DNS lookup uses Google's public resolver (8.8.8.8), which is widely accessible and updated frequently. To see what a specific resolver returns, you'd need a tool like dig @resolver domain from the command line.

Want the full explanation? Read the guide: DNS Records Explained: A, CNAME, MX, TXT, NS — What They All Mean →