DNS lookup
See the records a domain really publishes, read from its own nameservers and from the registry. Free, no signup.
Know when a record changes
A lookup shows the records as they are right now. DNS Guard in WWT remembers the records you choose, including the delegation at the registry, re-checks them on a schedule and alerts you when one changes or a CNAME starts pointing at nothing.
How to read the result
The records come from the zone's own nameservers, asked directly and without recursion. That is the source every resolver in the world eventually copies, so what you see here is what the domain publishes right now, not what a cache somewhere still remembers. If your browser or your provider's resolver shows something else, the difference is a cache that has not expired yet.
The second block is a different view: the nameservers and DNSSEC keys that the registry of the top-level domain lists for the registered domain. Those are set in the registrar account, not in the zone. When they differ from what the zone says about itself, either a migration is in progress or somebody changed the delegation, which is exactly how a domain gets hijacked without a single record in the zone being touched.
About DNS records
Which record types does the lookup read?
A and AAAA (the addresses a name points at), CNAME (an alias to another name), MX (where mail is delivered), NS (the zone's nameservers), TXT (SPF, domain verification and similar text entries) and CAA (which certificate authorities may issue for the domain).
Why do I see different values than with another lookup tool?
Most tools ask a public resolver, which answers from its cache until the record's TTL runs out. This one asks the zone's own nameservers, so a change shows up here first. Services that answer differently per region or rotate their addresses will also legitimately return different values from one question to the next.
What is a dangling CNAME and why is it dangerous?
It is an alias whose target no longer exists, typically a cloud resource or a hosted service that was shut down while the DNS record stayed. If the target name can be registered again, a stranger can claim it and serve their own content under your subdomain. This is known as a subdomain takeover.
What does the DNSSEC line tell me?
Whether the registry holds a DS record for the domain. With a DS record, validating resolvers can verify that answers were signed by the zone owner. Without one the domain works normally but its answers cannot be verified. A DS record that disappears or changes unexpectedly is a serious signal, because it is set in the registrar account.
How is this different from DNS monitoring?
This reads the records once, because you asked. Monitoring remembers the expected values and compares them on a schedule, so you hear about a changed MX, a replaced nameserver or a removed DS record within hours instead of when mail stops arriving or visitors land somewhere else.