About The DNS Lookup Tool

The DNS Lookup Tool queries DNS records for a domain or hostname and returns readable results for A, AAAA, CNAME, MX, TXT, and NS records. It is useful for checking domain resolution, mail routing, DNS migrations, verification records, and infrastructure changes.

The lookup is performed through a server-side endpoint so it can query DNS records consistently. Results may still differ from another resolver because of cache state, propagation timing, DNS provider behavior, and record TTLs.

How to Run a DNS Lookup Online

1. Enter a domain or hostname, such as example.com.
2. Click Lookup DNS.
3. Review the returned record groups and record counts.
4. Open Show more options when you need specific record types or JSON output.
5. Copy the output for migration notes, incident reports, or configuration checks.

Choosing Options Correctly

Basic mode:
Runs a quick A and AAAA lookup for the hostname, which is usually enough for simple web reachability checks.

Record types:
Use advanced mode to include CNAME, MX, TXT, or NS records when checking aliases, mail routing, verification tokens, or nameserver delegation.

Output mode:
Use readable text for quick inspection. Use JSON when you need structured data for notes or scripts.

Common Use Cases

• Checking A and AAAA records during site or API troubleshooting.
• Verifying MX records before or after mail configuration changes.
• Reviewing TXT records for SPF, DKIM, ownership verification, or service setup.
• Confirming NS records and CNAME aliases during DNS migrations.

Quick FAQ

Why do DNS results differ from another tool?
Resolvers, cache state, DNSSEC handling, split-horizon DNS, TTLs, and propagation timing can all differ.

Can I query private internal hostnames?
No. Public web tools generally cannot resolve private DNS zones reliably and should not receive sensitive internal names.

Does this replace authoritative DNS tooling?
No. Use dig, nslookup, registrar tools, or authoritative nameserver queries for production DNS troubleshooting.

When should I use JSON output?
Use JSON when you want to copy results into scripts, tickets, monitoring notes, or structured comparisons.