A and AAAA records
A records map a hostname to an IPv4 address. AAAA records provide the IPv6 equivalent. Check these after a hosting, CDN or server-IP change.
DNS Checker
Check live DNS records for any domain. Supports A, AAAA, MX, TXT, CNAME, NS and CAA.
DNS result
Check the DNS records a public resolver can see
Enter a domain, choose a record type and run the lookup. The browser sends a DNS-over-HTTPS query to Cloudflare's public recursive resolver and displays the returned answers together with TTL values when they are available.
MX records
MX records identify the mail exchangers responsible for receiving email for a domain. Their priorities help determine which mail server is preferred.
TXT records
TXT records commonly carry SPF policies, ownership verification tokens and other service-specific text. A single domain can legitimately publish multiple TXT records.
CNAME, NS and CAA
CNAME creates an alias to another hostname, NS identifies authoritative nameservers, and CAA can restrict which certificate authorities may issue certificates for a domain.
How to interpret DNS lookup results
The Value column contains the answer returned for the selected record type. TTL is the time-to-live supplied with the answer: recursive resolvers may cache that record for up to that period before asking again. A low TTL can make planned migrations converge faster, while a previously cached record can still remain visible until its earlier TTL expires.
If no answer is returned, that does not always mean the entire domain is broken. The selected record type may simply not exist for that hostname. For example, a hostname can have an A record without having a CNAME record.
DNS troubleshooting by task
Website points to the wrong server
Check A and AAAA records and compare them with the expected hosting or CDN addresses. Also verify whether a CNAME is being used instead of a direct address record.
Email is not being delivered
Check MX records first, then review relevant TXT records such as SPF and provider verification records. Mail delivery can still fail for reasons outside DNS.
SSL validation is failing
Confirm the hostname resolves to the infrastructure where the certificate is installed. CAA records can also matter when a certificate authority is attempting issuance.
Nameserver migration looks incomplete
Review NS records and compare them with the nameservers configured at the registrar. Resolver caches can make old answers persist temporarily after a change.
DNS lookup versus DNS propagation checking
This DNS Checker answers from one public recursive resolver, which is useful for a fast, repeatable lookup. If you need to compare answers across independent resolvers after a DNS change, use the DNS Propagation Checker. Different resolvers can temporarily show different cached values while TTLs expire.
Limits of a DNS check
A correct DNS answer confirms name-resolution data, not the health of the destination service. A website can have the correct A record while the web server is offline, and correct MX records do not prove that a mail server will accept or deliver a message. Use DNS together with HTTP, SSL and service-specific diagnostics.
DNS troubleshooting guide
Related website tools
Frequently asked DNS questions
Why do I still see the old IP address after changing DNS?
A recursive resolver may have cached the old answer before the change. It can continue serving that answer until the cached TTL expires. Local operating-system, browser and ISP caches can add another layer of delay.
What is a DNS TTL?
TTL means time to live. It tells recursive resolvers how long an answer may be cached before it should be refreshed. It is not a guarantee that every user will update at exactly the same second.
Should a domain have both A and AAAA records?
Only if the service is intentionally reachable over both IPv4 and IPv6. Publishing an AAAA record for an endpoint that is not correctly serving IPv6 can create connection problems for clients that prefer IPv6.
Why can I have multiple MX or TXT records?
Multiple MX records can provide prioritized mail destinations. TXT records are general-purpose and are commonly used by several independent services, so multiple TXT answers are normal.