Skip to main content
iply.dev

DNS Lookup

Retrieve common DNS records with the standard server-side lookup, or opt in to compare A, AAAA, MX, TXT, and NS records across Cloudflare and Google.

Try:

Resolver comparison requires Redis-backed rate limiting on this deployment.

Opt-in localStorage only; stores query text, not results.

What This Tool Does

Our DNS lookup tool resolves common DNS records for any domain. The standard lookup checks A records (IPv4), AAAA records (IPv6), MX records (mail servers), TXT records (SPF and verification), DMARC policy records, NS records (nameservers), SOA records (zone authority), SRV records (service discovery), and CAA records (certificate authority authorization). An optional comparison checks A, AAAA, MX, TXT, and NS answers from Cloudflare and Google. It compares only those selected public resolvers and is not an authoritative trace.

Common Use Cases

  • Spot-check how your DNS records currently resolve after making changes
  • Compare selected public resolver answers after DNS changes
  • Debug email delivery issues by checking MX and SPF records
  • Investigate domain configuration problems
  • Check SPF and DMARC records for email authentication
  • Find all nameservers responsible for a domain

Frequently Asked Questions

What are the different DNS record types?
A records point to IPv4 addresses, AAAA to IPv6. MX records specify mail servers. TXT records hold text data like SPF policies. NS records list nameservers, SOA records describe zone authority, SRV records advertise services, and CAA records authorize certificate authorities.
How long does DNS propagation take?
DNS changes become visible as resolver caches expire according to record TTLs and each resolver's cache state. The optional comparison shows current answers from Cloudflare and Google only; agreement does not prove that every resolver has updated.
Why might DNS lookup show different results?
DNS results can vary due to geographic load balancing, CDN configurations, or propagation delays. Different resolvers may cache records at different times, showing temporarily inconsistent results.

Related Tools

IP LookupWHOIS