DNS Lookup
Enter a domain and a record type to see exactly what its DNS is currently returning — useful for confirming a change has propagated or debugging a misconfigured record.
Overview
DNS record types each serve a different purpose: A/AAAA records point a domain at an IPv4 or IPv6 address, CNAME aliases one name to another, MX records route mail, TXT records carry arbitrary text (often used for domain verification or SPF/DKIM), NS records name the domain's authoritative nameservers, and SOA carries the zone's administrative metadata. This tool queries the app's own DNS resolver directly and shows exactly what comes back for the record type you pick.
Results are cached briefly so rapid repeat lookups of the same domain and record type don't re-query DNS every time, but the cache window is short enough that a lookup still reflects a change made in the last few minutes in most cases.
Examples
MX records for a domain
example.com
0 example-mail.example.com
How It Works
- Enter a domain name, e.g. example.com.
- Choose a DNS record type — A, AAAA, CNAME, MX, TXT, NS, or SOA.
- Click Look Up to query DNS and see the current records.
- An empty result means the domain has no records of that type, not that the lookup failed.
Use Cases
Confirming an MX record change
Check that mail routing points to the expected provider after switching email hosts.
Debugging a domain verification TXT record
Confirm a verification string added for Google Workspace, Microsoft 365, or another service is actually visible in DNS.
Checking nameserver delegation
Look up NS records to confirm a domain is delegated to the expected DNS provider.
Tips
- DNS changes can take time to propagate globally — use the DNS Propagation Checker to see results from multiple resolvers at once.
- A CNAME record can't coexist with other record types on the same name — if a lookup for A/TXT/MX looks empty on a name that has a CNAME, that's expected DNS behavior, not a bug.
FAQ
No. The domain you enter is only used to make a standard DNS query from Adikya's server; nothing is logged beyond what's needed for rate limiting and abuse prevention.
This tool queries DNS from Adikya's server, not your own network, so it reflects what the wider internet sees rather than any local DNS cache or split-horizon DNS you might have.
Results are cached for about 30 seconds to keep the tool responsive under repeat use; a very recent DNS change may take a short moment to show up.