Check any DNS record, and whether it has spread.
Enter a domain and pick a record type to see what Google, Cloudflare, AdGuard and NextDNS answer, next to what the domain's own nameservers say. No account needed.
- Eight record types
- Four public resolvers
- Compared with the nameservers
- TTL for every answer
- Subdomains and TXT names
What you get
One record, five answers, side by side.
The checker asks four big public resolvers for the record, then asks the domain's own nameservers directly. Each resolver is marked as matching, different, missing or not answering, with how long its copy may stay cached.
| Resolver | A record | TTL | Status |
|---|---|---|---|
| Google Public DNS | 93.184.215.14 | 5 min | Matches |
| Cloudflare 1.1.1.1 | 93.184.215.14 | 4 min | Matches |
| AdGuard DNS | 192.0.2.10 | 38 min | Different |
| NextDNS | 93.184.215.14 | 5 min | Matches |
| Nameservers | 93.184.215.14 | 5 min | Authoritative |
Example for example.com: one resolver still holds the old address until its cached copy expires.
Why it matters
DNS decides where everything goes.
Your domain's records send visitors to your server, mail to your inbox and verification checks to the right place. A wrong or stale record breaks one of them quietly, often for only some people.
Launches
Know when a change is live
After moving a site or switching hosts, see whether the big resolvers already give the new address or still serve the old one.
Email
Keep mail flowing
Check MX records and the TXT records behind SPF, DKIM and DMARC, which decide whether your mail arrives or lands in spam.
Verification
Pass ownership checks
Search Console, ad platforms and certificate authorities read TXT and CAA records. Confirm the record is there before you press verify.
Who it's for
Built for the people who change DNS.
01
SEO specialists
Confirm a migration has reached the resolvers before checking rankings, and that the TXT record for Search Console is in place.
02
Developers
Check a record straight from the authoritative nameservers, and see which resolvers still cache the old answer and for how long.
03
Agencies
When a client changes DNS provider, check every record type in a few minutes before and after the switch.
04
Site owners
Changed a record at your registrar and the site still looks the same? See whether the change is out there yet.
How it works
From domain to answer in seconds.
01
Enter a domain or host
Type a domain such as example.com, a subdomain such as www.example.com, or a TXT name such as _dmarc.example.com, and pick the record type.
02
Ask the resolvers
Google, Cloudflare, AdGuard and NextDNS are asked over DNS over HTTPS at the same time. Each gives its answer and the TTL left on its cached copy.
03
Compare with the source
Up to four of the domain's own nameservers are asked directly. Their answer is the current truth, and every resolver is compared with it.
FAQ
Questions, answered.
It looks up a domain's DNS records, the entries that say which server hosts its website, which servers take its mail and more. This one asks several public resolvers and the domain's own nameservers, so you can see whether they all give the same answer.
When you change a record, the domain's nameservers have the new value right away. Resolvers such as Google's and Cloudflare's keep a cached copy of the old answer until its TTL runs out, then ask again. Propagation is that waiting period, and it is over once every resolver has fetched the new answer.
At most the TTL of the old record, which is often 5 minutes to 1 hour, and sometimes a day. Lowering the TTL a day before a planned change makes the switch faster. A change of nameservers at the registrar can take longer, because the top-level domain's own records have TTLs of up to two days.
Four large public resolvers: Google Public DNS, Cloudflare 1.1.1.1, AdGuard DNS and NextDNS, plus up to four of the domain's own nameservers. Each public resolver runs many sites worldwide and answers from the one nearest our server, so this is not a map of servers by country. Your internet provider's resolver keeps its own cache and may differ.
It is the answer from the nameservers that hold the domain's records, read directly rather than from a cache. When a public resolver matches it, that resolver has the current record. When it differs, the resolver is still serving an older copy.
A and AAAA for a host's IPv4 and IPv6 addresses, CNAME for aliases, MX for mail servers, NS for nameservers, TXT for SPF, DKIM, DMARC and verification codes, SOA for the zone's serial number and timers, and CAA for which certificate authorities may issue certificates.
Time to live: how many seconds a resolver may keep an answer before asking again. The nameservers show the full TTL. A resolver shows the time left on its cached copy, which is why the numbers differ and count down.
Usually a cached old record that has not expired yet. Some large sites and CDNs also hand out different addresses on purpose to spread traffic, so a mismatch on a busy site is not always a problem. When the host is an alias, the checker compares the alias target, since the domain's nameservers do not hold the target's addresses.
Yes. Enter the full name, such as blog.example.com, _dmarc.example.com or selector._domainkey.example.com, and pick the record type. The domain's nameservers are found from the zone the name belongs to.
Yes. You can run 10 checks a day without an account. It uses only free public resolvers and the domain's own nameservers.
Free SEO tools