Check A, AAAA, CNAME, MX, TXT, NS, and SOA records with a fast DNS-over-HTTPS lookup tool. Clean output, quick copy actions, responsive results, and practical guidance for troubleshooting websites, email, and domain setup.
| Type | Answer | TTL |
|---|
This tool sends a DNS-over-HTTPS request from your browser to the selected resolver and returns the matching answers for the record type you choose. It supports common DNS checks like A, AAAA, CNAME, MX, TXT, NS, and SOA records, plus an ANY-style combined view.
Results are shown in a clean table for fast scanning and can also be copied as raw JSON when you need to save the response in notes, tickets, or documentation.
DNS checks are useful when troubleshooting websites, email routing, domain verification, CDN changes, or migration issues. A fast browser-based lookup helps you confirm what records are currently visible from a public resolver.
This DNS lookup tool is commonly used by developers, IT teams, marketers, and website owners to diagnose and verify domain configurations. DNS problems can affect much more than a homepage. They can break email delivery, block domain verification, delay migrations, and create difficult-to-trace issues across different services.
Each DNS record type serves a different purpose. Understanding what each one does makes troubleshooting much easier. A domain may work fine for website traffic while still failing for email, or a verification request may fail even though the main site loads correctly. That is why it helps to check the specific record type related to the problem.
DNS failures are often small configuration mistakes with big visible effects. A wrong record value, old cache, or incomplete migration can cause a site to appear broken even when the underlying service is healthy. Running a direct lookup is one of the fastest ways to narrow down the issue.
This tool helps you see whether the public resolver is returning the records you expect right now, which is often the fastest way to confirm whether a change has actually taken effect.
Not every resolver answers in exactly the same way at exactly the same time. Public resolvers may cache results differently, refresh data on different schedules, apply filtering or geo-aware logic, or simply return data from different points in the update cycle. That is why Cloudflare and Google can sometimes show slightly different results even when both are working correctly.
When diagnosing a problem, it is often useful to compare more than one resolver. If both return the same answer, confidence is higher. If they differ, the issue may be related to caching, propagation, or resolver behavior rather than the domain itself.
InstantQR tools are designed to be simple, privacy-first, and immediately useful. This DNS lookup runs from the browser, supports trusted DNS-over-HTTPS providers, and gives results in both human-readable and raw formats. That combination makes it useful for quick checks, deeper troubleshooting, and documentation workflows.
A DNS lookup checks the DNS records for a domain or hostname, such as A, AAAA, CNAME, MX, TXT, NS, and SOA records.
This tool supports A, AAAA, CNAME, MX, TXT, NS, SOA, and an ANY-style multi-record lookup.
Yes. This tool queries the selected resolver from your browser using DNS-over-HTTPS.
A lookup may return no answers if the domain has no records for that type, the hostname is incorrect, or the resolver does not return results for that query.
Resolvers can differ because of caching, propagation timing, filtering, geo-routing, or resolver-specific behavior.
