DNS Lookup

Inputs that matter

Enter the exact hostname you want to test, not just the organization name. www.example.com, mail.example.com, and example.com can have different records. Choose the record type that matches the problem: A/AAAA for web addressing, MX for mail routing, TXT for SPF/verification, and NS for authoritative nameservers.

How to read the output?

An answer proves that the queried resolver returned that record at the time of the test. TTL indicates how long resolvers may cache the result; it does not guarantee a synchronized global refresh. If a CNAME is returned, follow the target because the service can ultimately depend on another hostname.

Example diagnosis

If a website stopped loading after an A-record change, compare the expected authoritative value with the result here. If the old address remains only on some resolvers, caching is likely. If the authoritative zone itself still returns the old value, fix the DNS provider configuration rather than waiting for “propagation.”

Common errors

• NXDOMAIN: the queried name does not exist in DNS.
• No record of that type: the name can exist while the requested type is absent.
• Unexpected nameserver: delegation may still point to an old DNS provider.
• Different answers: split DNS, geo/load balancing, filtering, or stale caches can produce legitimate differences.

Limitations

DNS success does not prove the website, mail server, or application is healthy. After name resolution is correct, continue with the protocol that is failing: HTTP/TLS, SMTP, firewall, routing, or server application.