Which resolver does this tool use?

Cloudflare's public DNS-over-HTTPS endpoint (1.1.1.1) at cloudflare-dns.com/dns-query. Cloudflare's policy is no logging of queries beyond 24h.

Why are results different from `dig` on my laptop?

Your laptop uses your ISP or local resolver, which may cache stale answers or apply split-horizon DNS. This tool always asks Cloudflare directly — useful for checking real-world propagation.

Why is my newly-changed record not showing up?

DNS caches at multiple layers (recursive resolvers, your OS, your browser). Wait for TTL to expire on each layer. Cloudflare honors authoritative TTLs but caches for that duration.

What's the difference between A and AAAA?

A records hold IPv4 addresses (e.g. 192.0.2.1). AAAA records hold IPv6 (e.g. 2001:db8::1). A domain can have both.

Certificate Authority Authorization — lists which CAs may issue TLS certificates for your domain. Required check before issuance for most modern CAs.

Does this leak my query?

Your browser sends the domain to Cloudflare's resolver over HTTPS. Cloudflare sees the query; Toolis does not. No server-side logging on our end.

DNS Checker

Look up A, AAAA, MX, TXT, NS, CNAME, SOA, and CAA records for any domain. Queries Cloudflare 1.1.1.1 over DNS-over-HTTPS, runs entirely in your browser.

Runs in browser
No signup
No tracking

Results will appear here

Enter a domain and hit “Look up” to query A, AAAA, MX, TXT, NS, CNAME, SOA, and CAA records.

AAAAACNAMEMXTXTNSSOACAA

Found this useful?Buy me a coffee

How to use DNS Checker

Enter a domain name (e.g. example.com).
Click “Look up”. All record types fetch in parallel.
Inspect each record group — host, TTL, value.
Copy individual values or full records as needed.

When to use it

Verifying DNS propagation after a registrar/nameserver change.
Debugging email: confirm MX, SPF (TXT), DKIM (TXT), DMARC (TXT) records.
Checking CAA before requesting a TLS certificate.
Auditing a domain's nameservers and SOA serial.
Confirming IPv6 (AAAA) coverage alongside IPv4 (A).

What it fixes

Local resolver cache hiding the real public state of your DNS.
Slow `dig` setup on machines without it installed.
Mystery email bounces traced back to missing SPF/DKIM TXT records.
Certificate issuance failures from forgotten CAA records.

About DNS Checker

A DNS checker reveals what the public internet actually sees for your domain — bypassing your ISP's cache and any local overrides.

This tool issues parallel DoH queries to Cloudflare's 1.1.1.1 resolver for every common record type and shows raw answers with TTLs. Useful for verifying propagation after a change, debugging email deliverability (MX, SPF, DKIM, DMARC), checking CAA before issuing certificates, or auditing nameserver setup.

No backend, no logging. Your browser talks straight to Cloudflare.

References: Cloudflare DNS-over-HTTPS docs · RFC 1035 — DNS Implementation · RFC 8484 — DNS Queries over HTTPS (DoH) · RFC 8659 — CAA Records

Frequently asked

Which resolver does this tool use?
Cloudflare's public DNS-over-HTTPS endpoint (1.1.1.1) at cloudflare-dns.com/dns-query. Cloudflare's policy is no logging of queries beyond 24h.
Why are results different from `dig` on my laptop?
Your laptop uses your ISP or local resolver, which may cache stale answers or apply split-horizon DNS. This tool always asks Cloudflare directly — useful for checking real-world propagation.
Why is my newly-changed record not showing up?
DNS caches at multiple layers (recursive resolvers, your OS, your browser). Wait for TTL to expire on each layer. Cloudflare honors authoritative TTLs but caches for that duration.
What's the difference between A and AAAA?
A records hold IPv4 addresses (e.g. 192.0.2.1). AAAA records hold IPv6 (e.g. 2001:db8::1). A domain can have both.
What's a CAA record?
Certificate Authority Authorization — lists which CAs may issue TLS certificates for your domain. Required check before issuance for most modern CAs.
Does this leak my query?
Your browser sends the domain to Cloudflare's resolver over HTTPS. Cloudflare sees the query; Toolis does not. No server-side logging on our end.

Discussion

All tools