DNS Lookup

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.

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.

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.

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.

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.

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.

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.

A domain lookup can mean a few things, so here it pulls live DNS records across nine types in one pass. A domain name lookup for ownership or registrar dates belongs on the WHOIS Lookup tool instead, which reads the registry rather than the zone.

Enter the hostname, press Lookup, and nine queries fire in parallel. It is the direct way to check dns records and to check domain records for a name, with each type grouped and counted so an empty section reads as real information, not an error.

Yes. The A and AAAA groups give you a dns ip lookup in the same view as everything else, so you can find dns entries for mail and text records at the same time. When you only care about addresses, the Domain to IP tool is the leaner choice.

It does. Each dns query goes out server side the moment you press Lookup, so a dns lookup online here reflects what the authoritative nameservers publish right now rather than a saved snapshot. It can still differ briefly from your ISP resolver while its cache expires.

No. It queries forward records for a hostname across the nine common types, so mapping an address back to a name through a PTR record is not part of this tool. Enter a domain, not an IP, for it to return anything.

The results line up, because both read the same records. A dns lookup command gives you scripting and flags on your own machine, while this page runs the query server side and formats all nine types at once, which helps when your local resolver is caching an old answer.

Close, but not identical. A google dns lookup queries Google's 8.8.8.8 resolver, while this tool uses the server's own resolver. For the same domain the answers usually match, since both ultimately read your authoritative nameservers.

Plenty. A dns check online here surfaces the MX, TXT, and SPF-style records that mail depends on, so a domain dns check before you cut over confirms the receiving servers and verification strings are already in place. Missing MX records are the classic reason mail bounces after a move.

Run the lookup on the affected hostname and read each group top to bottom. When you check website dns this way you can check domain dns records against what the new provider promised, and the NS group tells you whether the delegation itself moved yet.

It parses each type into its own labelled group with a count, so a domain details lookup reads cleanly rather than as a wall of text. For a domain information lookup you get the dns details for A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, and CAA on a single screen.

No, and that is worth flagging. This shows live records only, so a dns history lookup of what a domain published last month needs a passive DNS service that archives changes over time. Use this page for the current state and re-run it after each change to watch propagation.

A search here returns the records that exist for the exact name you enter. Since a domain name dns lookup depends on the label, checking dns search domains such as www or _dmarc means entering those full hostnames rather than the apex alone.