Free DNS Record Checker
Query all DNS records for any domain at once. Queries A, AAAA, CNAME, MX, TXT, NS, and SOA records in parallel via Google DNS-over-HTTPS API.
DNS records are queried via Google's public DNS-over-HTTPS API (
dns.google). Results reflect what Google's DNS resolvers see. For authoritative DNS queries, use dig or nslookup from the command line.
Key Features
All Records at Once
Queries all 7 DNS record types (A, AAAA, CNAME, MX, TXT, NS, SOA) in parallel with explanations.
Live DNS Query
Results fetched in real-time via Google DNS-over-HTTPS (DoH) API with TTL values.
Domain History
Recently looked-up domains saved in your browser for quick re-query.
Privacy First
Queries go directly to Google DNS. No data stored on our servers.
Frequently Asked Questions
About DNS Records
What is the difference between an A record and a CNAME?
An A record maps a domain directly to an IPv4 address (e.g., "example.com → 93.184.216.34"). A CNAME creates an alias pointing one domain to another (e.g., "www.example.com → example.com"), and the resolver then looks up the target's A/AAAA records. You cannot use a CNAME at the zone apex (root domain); the root must use A/AAAA records. CNAMEs are useful for CDN setups, subdomain aliasing, and avoiding duplicate record management across multiple hostnames.
How does MX record priority work?
MX records include a numeric priority (0-65535). Lower numbers have higher priority. When delivering email, SMTP servers try the MX with the lowest priority first. If that server is unreachable, they fall back to the next-lowest. Multiple MX records with the same priority are tried in a round-robin fashion for load balancing. For example, priority 10 is used before priority 20. A common setup uses a primary mail server at priority 10 and a backup at priority 20.
Advanced Usage
Does this tool query real DNS servers?
Yes — this tool queries Google's public DNS-over-HTTPS API (dns.google), which returns real DNS records from Google's resolvers. The results reflect cached data, so recently changed records may not appear immediately (TTL-dependent). For authoritative queries that bypass caching, use
dig +trace or a dedicated DNS diagnostic service. The tool does not run its own DNS resolver.What are TXT records used for?
TXT records store arbitrary text data associated with a domain. Common uses include: SPF records (
v=spf1 ...) to authorize email senders; DKIM records to verify email signatures; DMARC records (v=DMARC1; p=reject; ...) to set email authentication policy; domain ownership verification tokens for services like Google Search Console or Microsoft 365; and site verification codes for SSL certificate issuance via DNS challenge.What does TTL mean and what value should I use?
TTL (Time To Live) specifies how long (in seconds) DNS resolvers can cache a record before querying again. Low TTL values (60-300s) allow fast propagation of DNS changes — useful during migrations. High TTL values (3600-86400s) reduce DNS query load and improve performance for stable records. Common defaults: 300s for dynamic records, 3600s for static records, 86400s for NS records. Lower TTLs increase authoritative DNS server load.