My Tool Studio
WebmasterURL-first

DNS Lookup

Run a dns lookup against any domain and get all nine common record types back at once: A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, and CAA. The queries fire in parallel through Node's dns module rather than a third-party API, so the result is a live dns record lookup, not a cached snapshot. It's built for the moments that matter: confirming MX records before an email cutover, verifying a TXT value for domain ownership, or watching an A record change land during a migration. Each record row has its own copy button, so you can check dns records online and paste evidence straight into a ticket.

Always freeNo sign upRuns in your browser

How to use

01

Enter a domain or subdomain

Put the bare hostname in the Domain field, example.com or something deeper like mail.example.com. Subdomains matter here because their records often differ from the root domain's.

02

Hit Lookup

Press the Lookup button and nine queries run in parallel. Results come back grouped by record type, with each group's header showing how many records were found.

03

Copy the records you need

Every row has a copy button, so you can grab an MX line or a long TXT value exactly as the resolver returned it, without retyping anything.

Why DNS Lookup

Common questions

Which record types does this DNS lookup query?
All nine common ones in a single pass: A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, and CAA. Each type gets its own section in the results, including an explicit note when a type returns nothing.
How soon after a change will the DNS lookup show new records?
That depends on the TTL the old record carried. If it was 3600 seconds, resolvers can keep serving the stale answer for up to an hour after your change. Once caches expire, this tool reflects whatever your authoritative nameservers currently publish.
Why does a dns query tool report no records found for some types?
Because most domains genuinely don't have every type. SRV and CAA records are relatively rare, and a root domain usually won't have a CNAME at all. An empty section is information, not an error.
What do the numbers next to mail servers in DNS MX results mean?
That's the priority value, and lower wins. A record like priority 10 for mx1.example.com and priority 20 for mx2.example.com tells sending servers to try mx1 first and fall back to mx2 if it's unreachable.
Can I query DNS records for a subdomain?
Yes, and you often should. CNAME records typically live on subdomains like www or shop, and verification TXT records frequently sit on prefixed names such as _dmarc.example.com. Query the exact hostname you care about.
Are the DNS results here live or cached?
The query runs server-side through Node's resolver at the moment you press Lookup, so it's live from that resolver's point of view. It can still differ briefly from what your ISP's resolver serves, since each resolver expires its cache on its own schedule.
Why do long TXT records in DNS results appear split into chunks?
The DNS protocol stores TXT data in strings of at most 255 characters, so a long DKIM key comes back as multiple pieces. Receiving software joins them back together, and you should too when comparing values.

More Webmaster tools

View all