networkutils.org

Home / DNS Tools / DNS Lookup

DNS Lookup

DNS Tools

A, AAAA, CNAME, TXT, NS, SOA and SRV records.

Run this tool: the interactive DNS Lookup loads here (requires JavaScript). Input: Domain — e.g. example.org.

Description

DNS Lookup queries the authoritative name servers for a domain and returns every record type we can find — A, AAAA, CNAME, MX, TXT, NS, SOA and SRV — so you see the zone exactly as it is published.

Features

✓ All major record types in a single query (A, AAAA, CNAME, MX, TXT, NS, SOA, SRV)
✓ Authoritative name-server queries by default
✓ TTL displayed for every record
✓ IPv4 and IPv6 resolution

How to Use

Enter a domain name (example.org) and run the tool. The probe queries the authoritative servers directly and returns every available record type grouped by section.

Input: Domain — e.g. example.org.

Understanding the Results

Records are grouped into ANSWER, AUTHORITY and ADDITIONAL sections. Each line shows the name, TTL (in seconds), class, type and value. The TTL tells you how long resolvers will cache the record before re-querying. MX records show priority before the mail host; TXT records show the raw string (used for SPF, DKIM, verification tokens and more).

Common Use Cases & Examples

→ Inspect the full record set of a domain before a migration.

→ Verify a new A or AAAA record has been published correctly.

→ Check MX priorities and TXT/SPF content at the authoritative source.

→ Confirm TTL values before lowering them for a cutover.

Frequently Asked Questions

What is a DNS TTL and why does it matter?

TTL (time to live) is how many seconds a resolver may cache a record before asking again. A high TTL (3600+) reduces load and speeds lookups but slows propagation of changes; a low TTL (60–300) lets changes spread fast but increases query volume. Lower the TTL before a planned cutover.

Why do I see different answers than my local resolver?

This tool queries authoritative servers directly, while your local resolver may return a cached answer still within its TTL. If they differ, propagation is in progress — wait for the old TTL to expire or flush the resolver cache.

What are TXT records used for?

TXT records hold arbitrary text and are overloaded for many purposes: SPF policies, DKIM public keys (under selector._domainkey), domain verification tokens, DMARC policies (under _dmarc), and Google/Site verification strings.

About this tool

Maintained by
networkutils.org editorial team
Last updated
September 2026
Testing methodology
DNS queries run through Node.js dns.promises and, for DNSSEC record types (DS/DNSKEY) and the AD validation flag, through Cloudflare DNS-over-HTTPS (application/dns-json). The Propagation Check queries 10 public recursive resolvers directly and compares their A-record answers. The DNS SuperTool performs its checks client-side in your browser over DNS-over-HTTPS using Cloudflare and Google.
Technical references
RFC 1034 — DNS Concepts and Facilities · RFC 1035 — DNS Implementation