Dns Lookup

Introduction

DNS Lookup lets you query DNS records for any domain to see how the internet resolves names to hosts and services. It's a practical tool for site owners, developers, and engineers who need to inspect A/AAAA, CNAME, MX, TXT, NS, SOA, and other DNS records to debug mail delivery, CDN configuration, redirects, and DNS propagation issues.

What is this tool?

The Domain Name System (DNS) maps human-friendly names to machine-friendly records. This tool performs live DNS queries against public resolvers and returns the records it finds — including record type, value, and TTL when available. Use these results to confirm authoritative settings, spot stale entries, and validate DNS-based services like email, verification TXT records, and service discovery.

Supported record types

• A / AAAA: IPv4 and IPv6 address records.
• CNAME: Aliases pointing one hostname to another.
• MX: Mail exchange servers and their priorities.
• TXT: Arbitrary text — used for SPF, DKIM, domain verification.
• NS: Authoritative nameservers for the zone.
• SOA: Start of Authority record with zone serial and TTL metadata.
• SRV, PTR, and others: Service records and reverse DNS where applicable.

Why use this tool?

• Verify DNS changes: Confirm new records after updates or migrations.
• Email troubleshooting: Check MX, SPF (TXT), and DKIM records that affect deliverability.
• CDN & proxy checks: Inspect CNAMEs and A/AAAA records to ensure traffic is routed correctly.
• Security & verification: Validate TXT records for ownership and security configurations.
• Propagation troubleshooting: Diagnose caching or TTL issues across resolvers.

How to use it

1. Enter the domain or hostname (e.g., example.com or www.example.com).
2. Select the record type to query (or choose “All” to fetch common types).
3. Click “Lookup” and review returned records, values, and TTLs.
4. If results differ from expectations, check authoritative nameservers, flush caches, or re-run from a different network.
5. For in-depth verification, query the domain’s NS records then query those nameservers directly.

Example

Input: example.com (Type: MX)
Output:

• ASPMX.L.GOOGLE.COM (priority 1) — TTL 3600
• ALT1.ASPMX.L.GOOGLE.COM (priority 5) — TTL 3600

Interpretation: Mail for example.com is routed to Google Workspace. Verify SPF/DKIM TXT records separately for full deliverability health.

FAQ

Do you store my queries?
No — lookups are executed live and are not retained. If your implementation logs queries, disclose this in your Privacy Policy.

Why do results differ between tools?
Different resolvers and caches may return different records depending on propagation, TTLs, and geographic DNS policies. Querying authoritative nameservers reduces variance.

How long for DNS changes to propagate?
Propagation depends on TTL settings and resolver caches; changes can appear in seconds for low TTLs or take several hours to fully propagate for higher TTLs.

Can this detect DNSSEC issues?
This tool reports DNS records. If you need DNSSEC validation, use a DNSSEC-aware resolver or tool that performs signature verification.