DNS Lookup & Multi-Nameserver Propagation Checker (A, MX, TXT, CNAME, NS)
Resolve and audit DNS records including A, AAAA, MX, TXT, CNAME, and NS records with authoritative TTL values.
Authoritative DNS Resolver
Enter a domain hostname above and click Lookup DNS to query authoritative records, routing targets, and TTL values.
About DNS Lookup & Multi-Nameserver Propagation Checker (A, MX, TXT, CNAME, NS)
Domain Name System (DNS) records translate human-friendly domain names like example.com into machine-routable IP addresses, mail server destinations, and cryptographic security verification tokens. When setting up a new website, deploying email servers, or configuring SSL certificates, verifying that DNS records have propagated globally is essential.
Using terminal commands like dig or nslookup requires command-line familiarity and local DNS configuration that can be tainted by stale local ISP caches. Webmasters need an independent, direct DNS resolver to inspect authoritative records.
This public DNS record resolver queries secure DNS-over-HTTPS (DoH) services to inspect authoritative records for any domain. You can query A (IPv4), AAAA (IPv6), MX (Mail Exchange), TXT (SPF and verification), CNAME (Aliases), and NS (Nameserver) records in real time.
To diagnose domain routing, inspect server response headers with the HTTP headers inspector and look up host coordinates using the IP address lookup.
Step-by-step practical guide
- Enter the domain name you wish to inspect (such as github.com or cloudflare.com) into the hostname input.
- Select your desired record type from the dropdown: A, AAAA, MX, TXT, CNAME, NS, or ALL.
- Click Resolve DNS Records to dispatch the query to the secure DNS-over-HTTPS resolver.
- Inspect the returned record cards showing record type, Time-to-Live (TTL), and resolved data values.
- Review any SPF, DKIM, or domain verification records displayed in the TXT results panel.
- Click Copy DNS Report to copy the formatted resolution results to your clipboard.
Engineering specifications and execution details
Utilizes Google Public DNS and Cloudflare DNS-over-HTTPS (RFC 8484) JSON APIs.
Parses standard DNS record types: Type 1 (A), Type 28 (AAAA), Type 15 (MX), Type 16 (TXT), Type 5 (CNAME), and Type 2 (NS).
Decodes priority integers for MX mail exchange routing records.
Displays exact Time-to-Live (TTL) countdown intervals in seconds.
Includes local cached fallbacks for major internet domains in case of network connectivity interruptions.
Data privacy and memory isolation
Queries are transmitted over encrypted HTTPS sockets directly to public DNS resolvers.
Zero queried domain names or IP addresses are recorded or tracked in our system.
Common production use cases
- Web administrators verifying DNS propagation after changing website hosting providers.
- Email administrators validating SPF, DKIM, and DMARC TXT records to prevent email delivery failures.
- Security researchers auditing nameserver configurations and checking for dangling CNAME takeover risks.
- Developers troubleshooting API endpoint connectivity and hostname resolution issues.
- Network engineering students studying DNS record structures, TTL values, and resolution steps.
Edge cases and operational boundaries
- Non-existent domains: Domains that are unregistered return NXDOMAIN (Non-Existent Domain) status codes with clear guidance.
- Long TXT records: Verification strings exceeding 255 characters are parsed and concatenated according to DNS standards.
- Subdomain resolution: Deeply nested subdomains (like api.v2.staging.example.com) are resolved identically to root domains.
- Root CNAME restrictions: CNAME records at the zone apex are illegal under DNS RFCs; the tool notes ALIAS or A record conventions.
Frequently Asked Questions
What is DNS propagation and how long does it take?
DNS propagation is the time it takes for DNS changes to update across internet resolvers worldwide. It typically takes between a few minutes and 48 hours based on TTL settings.
What is the difference between an A record and an AAAA record?
An A record maps a domain name to a 32-bit IPv4 address (e.g. 192.0.2.1). An AAAA record maps a domain name to a 128-bit IPv6 address (e.g. 2001:db8::1).
What is the purpose of an MX record?
An MX (Mail Exchange) record directs incoming email messages to the specific mail servers responsible for accepting email on behalf of that domain.
What are TXT records used for in modern web domains?
TXT records hold human-readable and machine-readable text used for email sender validation (SPF, DKIM, DMARC) and third-party domain ownership verification.
What does TTL mean in DNS records?
TTL stands for Time-to-Live, measured in seconds. It tells intermediate DNS caching servers how long to store the record before querying authoritative nameservers again.
Does this tool bypass my local ISP DNS cache?
Yes. The resolver queries public cloud DNS-over-HTTPS endpoints directly from your browser, bypassing local router and ISP caching delays.