What DNS Lookup checks
DNS problems often come from inspecting only an A record while email, ownership verification, delegation, or IPv6 depends on another record type. This lookup groups common answers without requiring dig or nslookup.
Common uses
- Confirm website A and AAAA destinations
- Inspect MX, TXT, and NS records during domain setup
- Find CNAME targets while debugging CDN or application routing
Privacy, safety, and limitations
The public domain is resolved by the ParseNest server's configured resolver and is not stored. Local, internal, reserved, and single-label names are rejected. Resolver answers may differ by network and geographic location.
Results reflect the check time and the server's network. DNS, CDN routing, and remote configuration can change afterward.
Frequently asked questions
Does this show global DNS propagation?
No. It shows the answer visible to the ParseNest server resolver. Propagation requires comparison across multiple independent resolvers and locations.
Why is TTL not displayed?
The Go system resolver returns record values without authoritative TTL metadata. Use an authoritative DNS client when TTL is required.
Why can a CNAME be absent?
Some providers flatten CNAME-like records at the zone apex and return A or AAAA answers instead.