How to Check a Domain's DNS Records

To check DNS, query the exact domain and record type you care about, then compare the returned answer with the authoritative configuration. A single successful website visit is too narrow: web, email, delegation, and verification records can be correct or broken independently.

Start with the question

Write down the hostname, such as www.example.com rather than only example.com, and the service you are testing. For a website, check A and AAAA records. For inbound email, check MX and the address records of the mail host. For delegation, check NS. A TXT lookup may reveal verification or mail-policy data, but one TXT record does not explain every use of TXT.

Use /whois to inspect the records WhoisFind returns. Record the query time and exact hostname so that a later comparison means something.

Compare with the authoritative zone

If you administer the domain, open the active DNS provider's zone and compare each value and TTL. Confirm that the registrar points to the intended nameservers. A correct-looking entry in an old provider's panel is irrelevant after delegation changes. You can also query an authoritative nameserver directly with a DNS utility to separate published data from cached resolver data.

For documentation or a harmless test, use an IANA reserved example name. Do not copy an example record value into a real production zone.

Interpret missing or different answers

No A record does not mean the domain is unregistered; it may use only a different hostname or lack web hosting. NXDOMAIN says a DNS name was not found in that answer, not that the registration can be purchased. A timeout can indicate a network or server problem rather than absence. If two resolvers differ after an edit, check TTL and negative caching before making repeated changes.

When email is affected, inspect MX and the target host before altering unrelated web records. The record type guide explains each field.

Sources

• RFC 1035: DNS queries and records
• RFC 2308: negative DNS caching