DNS Lookup Scanner
Initialize a targeted deep-scan across dns lookup endpoints in real-time.
Everything about DNS Lookup
Detailed insights and instructions for using the diagnostic utility effectively.
What is the DNS Lookup tool?
The NetScanner DNS Lookup tool is a free, browser-based diagnostic utility designed for developers and IT professionals. It allows you to securely inspect configurations, verify deployments, and troubleshoot issues in real-time. Unlike older tools, this check runs instantly and fetches live data.
How to use it
Simply enter your target domain name, IP address, or input string into the scanner above and hit Run Analysis. The tool will automatically parse your input, execute the necessary network requests from our secure proxy, and return the formatted results.
Understanding the Results
Our DNS Lookup tool not only provides raw data but also highlights expert recommendations. Look for yellow warning banners—these indicate potential security vulnerabilities or misconfigurations that you should address.
Limitations
Results are cached for a few seconds to prevent abuse. If you recently updated your DNS records or server configuration, please allow time for global DNS propagation before running the check again.
Related Diagnostic Tools
Tool Details & Usage
Information on inputs, outputs, and limitations.
Complete DNS Analysis Guide
When troubleshooting domain connectivity, email delivery, or DNS propagation, a thorough DNS Lookup is the essential first step. This tool queries public resolvers to return the actual DNS records currently published for your domain.
Supported Inputs
- Domain Name: e.g.,
example.com - The tool queries standard record types including A (IPv4), AAAA (IPv6), MX (Mail Exchange), TXT (Text records for SPF/verification), NS (Name Servers), and CNAME (Canonical names).
How to Interpret the Output
- Record Data: The target IP or text value.
- TTL (Time to Live): The time (in seconds) resolvers are told to cache this record. A TTL of 300 means 5 minutes.
- Record Type: Denotes what the record is used for.
Realistic Example
If you look up google.com:
- You will see multiple A records pointing to Google’s load-balanced IPs.
- You will see MX records pointing to
smtp.google.comfor handling their mail. - TXT records will show their SPF policies (e.g.,
v=spf1 include:_spf.google.com ~all).
Common Errors & Limitations
- Stale Cache: If you just updated a record at your registrar and don’t see it here, it is due to DNS caching. Wait for the old TTL to expire.
- No Results: Make sure you are querying the base domain unless the records are explicitly published on a subdomain.
You might also need
Keep troubleshooting with these related free tools.