Query DNS records for any domain using the Cloudflare DNS-over-HTTPS API (1.1.1.1). Look up A, AAAA, MX, NS, TXT, CNAME, and SOA records. Useful for debugging DNS issues, verifying configurations, and checking propagation. All queries go through Cloudflare's public resolver.
DNS (Domain Name System) translates human-readable domain names into IP addresses that computers use to communicate. When something goes wrong with a website — it won't load, email stops working, or SSL certificates fail — DNS is often the culprit. This lookup tool queries DNS servers to show you the actual records configured for any domain: A records (IPv4 addresses), AAAA (IPv6), MX (mail servers), NS (nameservers), TXT (verification and SPF/DKIM records), and CNAME (aliases). It's an essential troubleshooting tool for web developers, sysadmins, and anyone managing domains. Check if your DNS changes have propagated, verify email authentication records, or diagnose why a site isn't loading.
An A record maps a domain name to an IPv4 address. When you type example.com in your browser, DNS resolves it to an IP like 93.184.216.34 via the A record. Most domains have at least one A record.
MX (Mail Exchange) records specify which mail servers handle email for a domain. They include a priority number — lower means higher priority. If the primary server is down, email routes to the next priority.
When you change DNS records, the update needs to spread across DNS servers worldwide. This 'propagation' typically takes 1-48 hours depending on TTL values. During propagation, some users see old records and others see new ones.
TXT records store text data for various purposes: domain ownership verification (Google, Microsoft), email security (SPF, DKIM, DMARC), and service configuration. They're the Swiss Army knife of DNS.
Multiple A records provide load balancing and redundancy. DNS round-robin distributes traffic across servers. CDNs like Cloudflare may return different IPs based on your location (GeoDNS).