When a website or its email breaks, the answer is usually in the DNS records. This DNS record checker performs real, live lookups — not a simulation — using DNS-over-HTTPS against Cloudflare’s public resolver, and shows you a domain’s A, AAAA, MX, TXT, CNAME and NS records with their TTLs.
Use it to confirm a migration actually propagated, to check that the MX records pointing at your mail host are the ones you expect, or to verify the TXT records that prove domain ownership to Google, Microsoft and your email provider. Type a domain, pick the record types, and read the live answer.
What each record type does
A maps a name to an IPv4 address — the record that sends browsers to your server. AAAA is the same for IPv6. CNAME aliases one name to another (www to the root domain, or a subdomain to a provider). MX names the mail servers for the domain, with a priority number in front of each: lower wins, and the others are fallbacks. TXT is free-form text that has become the internet’s proof-of-ownership drawer: SPF, DKIM and DMARC email policies live there, as do verification strings for search consoles and certificate authorities. NS lists the authoritative nameservers — the servers whose answers count as truth for the domain.
How to read the results
Each answer shows the record’s value and its TTL (time to live, in seconds) — how long resolvers may cache it. A TTL of 14400 means a change can take up to four hours to be seen everywhere, which is why the standard migration advice is to lower the TTL a day before you move, not after. If a type shows nothing, the domain simply has no record of that kind: no AAAA means no IPv6, no MX means the domain cannot receive email at all. An “NXDOMAIN” answer is stronger medicine — the domain name itself does not exist.
A worked check
The tool opens on this site’s own domain. Its MX records point at the mail host with priorities 5 and 10 — two servers, tried in that order — and the A record shows the address the site is served from. Run the same check on a domain whose email you are setting up: if the MX values do not match the exact hostnames your provider gave you, mail will bounce no matter how correct everything else is.
How the lookup works
Your browser sends an encrypted DNS-over-HTTPS query to Cloudflare’s public resolver (1.1.1.1) and this page formats the JSON answer. That has two consequences worth knowing. First, the answer reflects what a large public resolver sees right now — if you just changed a record and the old value had a long TTL, you may still see the cached old answer here, exactly as much of the internet does. Second, you are seeing public DNS only: split-horizon records that exist only inside a company network are, correctly, invisible.
Frequently asked questions
I changed a record but still see the old value. Why?
TTL caching. Resolvers keep the old answer until its TTL expires. The TTL shown in the results tells you the worst-case wait from the moment the old record was last fetched.
Can this check records for a subdomain?
Yes — type the full subdomain (like mail.example.com). Each name in DNS has its own records.
Why is there no AAAA record for my site?
Your host only publishes an IPv4 address. That is common and not an error, though adding IPv6 is increasingly expected by large networks and mobile carriers.
Are these lookups logged anywhere by this page?
The query goes from your browser directly to Cloudflare’s resolver; this page itself keeps no log of what you look up.
Related tools
Versión en español: Comprobador de Registros DNS — Consulta A, AAAA, MX, TXT, CNAME y NS Online. You may also like: IP Subnet Calculator — CIDR, Netmask, Broadcast and Host Range · User-Agent Parser — Read Any User Agent String Online.
Embed this tool on your website — free
Copy the code below to add this working tool to your own page. A small credit link stays with it — that’s all we ask.