What to enter as the expected answer
Type the value the way DNS returns it. Capital letters and a final dot don't matter.
| Type | Enter it like this |
|---|---|
| A or AAAA | 203.0.113.10 |
| MX | 10 mail.example.com, with the priority first |
| TXT | "v=spf1 -all", with the quotes |
| CNAME | target.example.net |
A TXT value without its quotes won't match anything.
How to read the result
Published by authoritative nameservers is the source: what the domain's own servers hand out now. Seen in public resolver caches shows the copy each resolver gives its users.
A resolver marked Matches reference returns the same records as the nameservers. Different answer means it returns something else. The comparison ignores record order. Resolver TTL is the seconds left on that resolver's copy.
example.com, A record
Example
All 12 nameserver addresses return 104.20.23.154 and 172.66.147.243. Six of 7 resolvers match. Yandex DNS returns 8.47.69.5 and 8.6.112.5 instead.
Both sets are on Cloudflare's network, AS13335. An answer like this usually comes from the provider answering by location, not from an old copy.
Checked on 9 October 2026.
How long does DNS propagation take?
Up to the old record's TTL, counted from when your nameservers start serving the change. A resolver that cached the old record keeps it until that TTL runs out, then fetches the new one.
Old TTL of 3,600 seconds
Example
You change an A record at 2:00 pm, and the nameservers serve it within a minute. A resolver that cached the old record at 1:59 pm can keep it until about 3:00 pm.
Lowering the TTL after the change doesn't speed up copies already cached. A record that didn't exist before can be cached as missing. Resolvers then wait for the zone's negative cache time, which the SOA checker shows. DNS lookup explains TTL and caching in more detail.
What if the nameservers don't agree?
Sort that out first. Resolvers can fetch from any of them, so some keep getting the old answer. The provider may still be syncing, or one server may have stopped getting updates. The result links to the SOA checker, which shows whether one server has an older version of the zone.
If no nameserver shows the new value, the change isn't live. Check that you edited the DNS provider this domain actually uses. The nameserver checker shows which nameservers that is.
Can resolvers disagree without being out of date?
Yes. Large sites and CDNs answer by location, so two resolvers can get different addresses and both be right. Some providers also rotate addresses on every reply. If a resolver still differs after its Resolver TTL has run out, the cause isn't an old copy.
Does this check propagation worldwide?
No. It asks 7 public resolvers from stack127's server, not your computer. Your internet provider's resolver, your router, and your VPN aren't included, so they can show another answer.
IPv6 nameserver addresses are skipped when the checker has no IPv6 route, and the result says so. stack127 doesn't keep the names you check.