How to use this tool
Checks the selected record type across the DNS intelligence provider's resolvers. Inspect each resolver's answer and status. Geographic or load-balanced differences are not automatically faults.
Enter the target, complete any relevant options and choose Check. Review the requested records, query outcomes and diagnostic findings. Copy Report saves the visible report.
Reading the results
No matching records and an unavailable query are different outcomes. TTLs are displayed in seconds; zero is a valid TTL. A completed request does not mean a domain passed its health checks. Only the submitted DNS owner and explicitly listed checks are inspected.
Frequently Asked Questions
Does this page query multiple worldwide DNS servers?
No. The current code uses its server DNS lookup and a Google Public DNS browser fallback. It does not display a location-by-location resolver comparison.
Can one result confirm global DNS propagation?
No. This output represents one resolver path. Other recursive resolvers can still hold different cached answers.
Why does the previous DNS value remain in the table?
The resolver serving the request may have cached that value before the change. It can continue returning it until the old record's TTL expires.
Why is a changed record missing even though other records appear?
The requested name may differ from the record owner, or the selected resolver may not have refreshed it. Check the exact hostname and its authoritative zone.
Does a low TTL force every resolver to update immediately?
No. A low TTL limits normal cache duration after it is observed. Resolver behavior, earlier cached TTLs, and delegation changes can still affect timing.
How can I compare this result later?
Copy the current output, then run the same hostname again after the relevant TTL window. Compare Type, Host / Name, Target / Value, and TTL for changes.