DNS Lookup

Look up DNS records for any domain. Find A, AAAA, MX, TXT, CNAME records.

Domain
Record Types
DNS Records
Enter a domain name to lookup

Frequently Asked Questions

What DNS record types can I look up?+
This tool supports A records (IPv4 addresses), AAAA records (IPv6 addresses), MX records (mail servers), TXT records (verification strings, SPF, DKIM), and CNAME records (domain aliases). Select multiple record types at once to get a complete picture of a domain's DNS configuration.
Why might my DNS lookup show no records?+
Several reasons: the domain may not exist or be newly registered (still propagating), the specific record type may not be configured, or the record's TTL (time-to-live) may have expired from cache. Some domains intentionally omit certain record types. If you recently made DNS changes, wait 24-48 hours for global propagation.
Is my data sent to a server?+
Queries are sent to Cloudflare's DNS-over-HTTPS API (cloudflare-dns.com) to perform the actual DNS lookups. No other data is sent, and no logs are created of your lookups. This provides privacy by using HTTPS instead of traditional UDP DNS queries.
How can DNS lookup help diagnose email issues?+
Checking MX records helps verify that your domain points to the correct mail servers for email delivery. If email is bouncing, ensure MX records exist and point to valid mail servers. TXT records contain SPF configurations that determine which servers can send email "from" your domain—missing or incorrect SPF can cause delivery problems.
What does it mean when a domain has multiple A records?+
Multiple A records typically indicate load balancing or failover configurations. When multiple IP addresses exist, browsers and servers typically try them in order, which distributes traffic across servers. If one server fails, clients will eventually try the next address in the list.
What is DNS propagation?+
DNS propagation is the time it takes for DNS changes to update globally across all servers. Each DNS record has a TTL (time-to-live) setting that determines how long servers cache it before refetching. Changes typically take effect within minutes to hours, but some configurations cache records for days. Most propagation completes within 24-48 hours.
Copied!