Online DNS Records (A, AAAA, MX, TXT, CNAME, PTR) Lookup
Query global DNS servers via encrypted DNS-over-HTTPS (DoH) to inspect A, AAAA, MX, NS, TXT, CNAME, and PTR records directly from your browser.
What is Online DNS Records Lookup via DNS-over-HTTPS (DoH)?
Traditional DNS queries are transmitted over unencrypted UDP on port 53, leaving requests susceptible to eavesdropping, ISP hijacking, and DNS spoofing attacks. DNS-over-HTTPS (DoH, RFC 8484) encapsulates DNS lookups inside standard encrypted HTTPS sessions (TLS port 443). This utility performs 100% in-browser DoH requests directly from your client machine to premier public Anycast resolvers like Cloudflare (1.1.1.1) and Google (8.8.8.8). No lookup data or domain inquiries are transmitted through our servers, guaranteeing complete privacy and zero data retention.
Comprehensive DNS Record Types Reference
Maps a human-readable domain name directly to a 32-bit IPv4 address (e.g. 142.250.191.14). Essential for routing web traffic to hosting servers or load balancers.
Directs hostnames to modern 128-bit IPv6 network addresses (e.g. 2607:f8b0:4004:c07::6a). Enables dual-stack routing for next-generation mobile and fiber networks.
Specifies mail servers responsible for accepting incoming email on behalf of your domain, paired with priority weighting (lowest number has highest precedence).
Holds arbitrary human or machine-readable text. Critical for email security mechanisms including SPF (Sender Policy Framework), DKIM, and DMARC.
Aliases one hostname to another canonical hostname (e.g. www.example.com to example.com). Note: CNAME cannot coexist with other record types at the zone apex.
Delegates a DNS zone to authoritative nameservers responsible for holding and updating the official zone file records.
Stores authoritative master information about the DNS zone: primary master server, administrator contact email, serial revision number, and secondary refresh/expire timers.
Defines exactly which Certificate Authorities (such as Let's Encrypt or DigiCert) are permitted to issue SSL/TLS certificates for the domain, preventing fraudulent issuance.
Resolves an IP address back to its associated domain name (Reverse DNS / rDNS). Essential for email deliverability and spam filtering compliance.
How DNS Propagation Works & Why TTL Matters
When you modify a DNS record at your domain registrar or hosting provider (e.g. switching your website to a new server IP or configuring Google Workspace MX records), the update does not take effect everywhere simultaneously. This delay is known as DNS propagation.
DNS propagation is governed primarily by the TTL (Time To Live) value specified in seconds on each record. Recursive DNS resolvers (such as your local ISP, Google 8.8.8.8, and Cloudflare 1.1.1.1) cache the queried record locally for the full duration of its TTL. Until that timer expires, resolvers will continue serving the stale cached record rather than requesting fresh records from your authoritative nameserver.
Prior to migrating hosting providers or mail services, lower your DNS record TTL to 300 seconds (5 minutes) at least 24 to 48 hours in advance. Once the migration has completed and propagated cleanly worldwide, restore the TTL to 3600 (1 hour) or 86400 (24 hours) to conserve DNS lookup bandwidth.
DNS Status Codes (RCODE) Reference Guide
DNS query completed successfully. Records found or zone exists.
The name server was unable to interpret the query format.
The name server failed to process the request (often DNSSEC validation failure or authoritative server timeout).
The requested domain name does not exist in the DNS registry or has no active zone.
The name server does not support the requested query kind (e.g. RFC 8482 ANY refusal).
The name server refused to perform the specified operation for policy reasons.
Frequently Asked Questions (FAQ)
Why does an 'ANY' query not return every record on some resolvers?
Under RFC 8482 ("Providing Minimal-Answer Responses to DNS Queries of Type ANY"), public DNS resolvers like Cloudflare and Google intentionally limit or synthesize responses to ANY queries to protect infrastructure against DNS reflection and amplification DDoS attacks. Our tool solves this by running parallel queries across primary types (A, AAAA, MX, TXT, CNAME, NS, SOA, CAA) directly in your browser.
How can I verify that my SPF, DKIM, and DMARC TXT records are configured properly?
Select TXT in the record filter. Look for entries starting with v=spf1 to inspect allowed sender IP addresses and include mechanisms. For DMARC, query the subdomain _dmarc.yourdomain.com to verify your alignment policy (p=none, p=quarantine, or p=reject).
Is it safe to query internal or confidential domains with this tool?
Yes, 100%. The requests are dispatched directly from your browser to public DoH endpoints (Cloudflare, Google, Quad9, AliDNS) over encrypted HTTPS connections. No input strings, domains, or query responses ever touch our web servers.