One lookup, six records that answer different questions
An A record maps a name to IPv4, while AAAA does the same for IPv6. CNAME points one hostname at another canonical hostname. MX identifies mail exchangers, TXT carries free-form data used by systems such as SPF and domain verification, and NS identifies authoritative name servers.
Toolmera requests these record types separately and keeps the returned TTL beside each answer so you can see both the value and the cache lifetime reported by the resolver.
Web addressingA, AAAA and CNAME
Email routingMX
Verification / policyTXT
Authoritative DNSNS
TTL is a cache instruction, not a propagation countdown
DNS TTL tells resolvers how long an answer may be cached. It does not guarantee that every resolver worldwide will update at the same second, because existing caches, provider behavior and delegation changes can all affect what different users see.
That is why this lookup reports the resolver result it actually received rather than displaying a fictional “propagation complete” percentage.
Use DNS records to separate web, mail and ownership problems
If a website does not resolve, start with A, AAAA and CNAME. If email delivery is the problem, inspect MX and the relevant TXT records. If a domain appears delegated to the wrong provider, compare its NS answers with the nameservers configured at the registrar.
This does not replace a full DNS diagnostic trace, but it gives a compact snapshot of the records most people need during deployments, migrations and verification setup.
A public resolver view is useful precisely because it is external
A record can look correct inside a hosting dashboard while public DNS still returns something different. Querying an external DNS-over-HTTPS resolver gives you a view outside the application or hosting control panel.
For propagation-sensitive work, compare more than one resolver and remember that cached answers can legitimately differ for a while.