About the DNS Lookup Tool
What it does, how it protects your privacy, and how to read the results with confidence.
What the Tool Does
This tool retrieves DNS records for a domain and presents them in a clean, readable way. You can select record types, run the query, then copy values for documentation or troubleshooting. Everything renders locally in your browser and the query is sent over HTTPS to a public DNS resolver.
Why DNS Records Matter
Domain Name System records describe where services for a domain live. They direct web traffic, route email, point to aliases, and reveal the authoritative servers for a zone. When something breaks on a website or in email delivery, DNS is often the first place to check.
Types of DNS Records
- A and AAAA: Map a hostname to an IP address (IPv4 and IPv6).
- MX: Identifies mail servers for the domain.
- TXT: Carries verification tokens and SPF/DKIM values.
- CNAME: Creates an alias from one hostname to another.
- NS: Declares authoritative name servers for the domain.
- SOA: Contains zone metadata like primary nameserver and cache values.
How the Tool Works
The page builds a DNS-over-HTTPS request and sends it to a public resolver. The response contains records for the types you selected, with time to live values and data fields. The page does not send analytics and it does not include third-party trackers.
Privacy and Security Notes
- No analytics or tracking scripts on this page.
- No cookies or local storage are required for basic use.
- All rendering happens locally in your browser, which protects you from potential script injections in DNS records.
Interpreting Results
- Multiple A or AAAA records: Load balancing or anycast.
- MX priority: Lower values indicate higher priority servers.
- TXT records: Look for SPF, DKIM, and DMARC for email authentication.
- Unexpected CNAME: Ensure aliases point to intended domains.
- Authoritative mismatch: If NS records don't match your registrar, check for misconfiguration.
Troubleshooting
- Ensure the domain is typed correctly, e.g., use example.com instead of https://example.com.
- Try again after a few minutes if caching or throttling is causing outdated results.
- Check TTL values to estimate how long cached results may persist.
- Consider using an alternate resolver if regional issues arise.
Helpful References
This page is provided for informational and troubleshooting purposes. DNS answers come from the resolver you query and are presented as is. Results, interpretations, and any actions you take are your responsibility. No warranty is expressed or implied, and availability of third-party services may change at any time.