DNS Lookup
Look up DNS records for a domain (A, MX, TXT, and more).
DNS Lookup
Enter a domain name to lookup
Quick Lookup:
DNS Lookup Results
DNS Resolution Flow
Traceroute Results
DNS Propagation Results
Lookup History
About DNS Lookup
Common DNS Record Types:
- • A: Maps domain to IPv4 address
- • AAAA: Maps domain to IPv6 address
- • MX: Mail exchange servers
- • TXT: Text records for various purposes
- • CNAME: Canonical name alias
- • NS: Name servers for the domain
DNS Lookup Uses:
- • Website troubleshooting and debugging
- • Email delivery problem diagnosis
- • Domain configuration verification
- • Network administration tasks
- • Security analysis and monitoring
DNS Best Practices
⚡ Performance: Use multiple A/AAAA records for load balancing and redundancy.
🔒 Security: Implement DNSSEC to protect against DNS spoofing attacks.
📈 Monitoring: Regularly monitor DNS resolution times and availability.
🌐 Redundancy: Configure secondary name servers for high availability.
📝 Documentation: Keep detailed records of DNS changes and configurations.
Related tools
More from the same category
HTML Table Generator
Generate an HTML table with rows and columns.
HTTP Headers Viewer
View HTTP response headers.
Internet Speed Test
Test your internet connection speed.
IP Address Lookup
Look up geolocation and info for an IP address.
Keyboard Test
Test which keyboard keys are working.
Password Strength Test
Test password strength and security.
Learn more — open a section when you need details
The DNS Lookup tool queries public DNS resolvers using DNS-over-HTTPS (DoH) to retrieve DNS records including A records (IPv4 addresses), AAAA records (IPv6 addresses), MX records (mail server configurations), TXT records (SPF, DKIM, DMARC, verification strings), CNAME records (canonical name aliases), NS records (name server delegations), SOA records (start of authority with zone metadata), PTR records (reverse DNS lookups), and SRV records (service location records). It provides comprehensive analysis showing record values, TTL (Time To Live) durations, response times from multiple DNS providers (Google DNS, Cloudflare, Quad9), and visual flow diagrams explaining the DNS resolution process from client query through recursive resolver to authoritative name servers. The tool includes advanced features like traceroute simulation showing network path and latency to resolved IP addresses, DNS propagation checking across multiple global locations (North America, Europe, Asia, Australia, South America) to verify record distribution after changes, and historical lookup tracking with exportable JSON data for documentation, audits, or troubleshooting workflows. All DNS queries are performed securely using encrypted DoH connections ensuring privacy and bypassing local DNS cache, making it ideal for validating domain configurations, diagnosing email delivery issues, verifying CDN setups, troubleshooting DNS misconfigurations, monitoring DNS changes during migrations, and ensuring DNS security best practices are implemented correctly.
-
1
Enter a domain name (e.g., example.com) in the domain input field, ensuring you include the full domain without protocol prefixes (no http:// or https://), and prepare the domain you want to query for DNS record information.
-
2
Select your desired Record Type from the dropdown menu choosing from specific record types (A for IPv4, AAAA for IPv6, MX for mail servers, TXT for text records, CNAME for aliases, NS for name servers, SOA for authority information) or select ALL to retrieve all available record types for comprehensive domain analysis.
-
3
Click the Lookup button or press Enter to initiate the DNS query, watching the tool query multiple DNS providers sequentially for reliability, and observe real-time progress as records are retrieved and displayed in the results area.
-
4
Review the DNS Results panel showing comprehensive record details including record type labels, domain names, record values (IP addresses, mail server priorities, text strings), TTL values indicating cache duration, and response time metrics from the DNS provider used for the query.
-
5
Examine the DNS Flow Visualization diagram illustrating the complete resolution process from client query through recursive resolver, root servers, TLD servers, and authoritative name servers, helping you understand how DNS resolution works and where your query traversed.
-
6
Use the Trace Route feature by clicking the Trace Route button after a successful lookup to simulate network path analysis showing intermediate hops, IP addresses, hostnames, round-trip times (RTT), and geographic locations for each network hop to the target domain's resolved IP address.
-
7
Check DNS Propagation by clicking Check Propagation to verify record distribution across multiple global locations (using different DNS providers in various regions), viewing propagation status (propagated or not propagated), record counts per location, response times, and overall propagation percentage to confirm changes have reached all DNS caches worldwide.
-
8
Export your results using Copy Results to copy formatted text summaries to clipboard for documentation, or click Export JSON to save comprehensive lookup data including all records, timestamps, response times, and metadata in JSON format for integration into scripts, documentation, or troubleshooting tickets.
Email delivery troubleshooting and mail server configuration
Verify MX records point to correct mail servers with proper priority values, check TXT records for SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication) configurations, validate mail server IP addresses are reachable, and diagnose email delivery failures by confirming DNS records match expected mail server configurations for sending and receiving domains.
Domain go-live validation and DNS migration monitoring
Confirm A and AAAA records resolve to correct production IP addresses after DNS changes, verify CNAME records point to intended destination domains, check NS records match expected authoritative name servers, monitor DNS propagation progress across global locations after switching DNS providers or updating zone files, and validate that DNS changes have propagated successfully before announcing domain launches or completing migrations.
Security audit and DNS configuration review
Inspect TXT records for unexpected verification strings, check for unauthorized NS record changes indicating potential DNS hijacking attempts, review SOA records for proper administrative contacts and serial numbers, validate SPF records don't include unauthorized sending domains, identify missing security records (SPF, DKIM, DMARC) that should be present, and detect suspicious CNAME chains that could indicate subdomain takeovers or misconfigurations.
CDN and content delivery network setup verification
Verify CNAME records point to CDN provider endpoints correctly, confirm A and AAAA records resolve to CDN edge server IP addresses, check geographic distribution of resolved IPs matches expected CDN coverage, validate CDN configurations by comparing DNS records before and after CDN implementation, and ensure DNS TTL values are appropriate for CDN failover scenarios requiring quick DNS updates during incidents.
IPv6 deployment and dual-stack verification
Confirm both A (IPv4) and AAAA (IPv6) records exist for dual-stack deployment, verify IPv6 addresses are correctly formatted and routable, check for IPv4/IPv6 parity ensuring services are available on both protocols, validate that IPv6 records point to appropriate IPv6-enabled servers, and identify missing IPv6 records that need to be added for complete dual-stack functionality.
Subdomain delegation and organizational structure
Verify NS records for subdomains delegate to correct authoritative name servers, check CNAME records properly alias subdomains to target domains or resources, confirm subdomain DNS configurations match organizational requirements, validate that subdomain DNS records don't conflict with parent domain configurations, and ensure proper DNS hierarchy for complex domain structures with multiple levels of delegation.
Domain ownership verification and authentication
Check TXT records for domain verification tokens required by third-party services (Google Search Console, Microsoft Office 365, SSL certificate providers), verify ownership verification records match expected values, confirm authentication records are properly configured for service integrations, validate that verification records haven't expired or been removed, and troubleshoot domain verification failures by inspecting TXT record contents and formats.
DNS troubleshooting and resolution failure diagnosis
Diagnose DNS resolution failures by checking if A records exist and resolve correctly, verify NS records point to functioning name servers, identify circular CNAME references that prevent resolution, check for DNS misconfigurations like missing glue records, validate TTL values aren't causing excessive caching delays, compare results across multiple DNS providers to identify provider-specific issues, and use traceroute to diagnose network path problems affecting DNS resolution.
Lower TTL (Time To Live) values before making major DNS changes to speed up propagation, as shorter TTLs (300-600 seconds) allow DNS caches to refresh more quickly, enabling faster distribution of DNS updates across global DNS resolvers and reducing the time required for changes to become visible worldwide.
Check both A (IPv4) and AAAA (IPv6) records to ensure IPv6 parity, as modern applications should support both protocols for complete network connectivity, and missing IPv6 records can cause connection failures for IPv6-only networks or dual-stack clients preferring IPv6 connections.
Validate CNAME chains and ensure no circular references exist, as circular CNAME records (e.g., subdomain.example.com points to subdomain2.example.com which points back to subdomain.example.com) cause DNS resolution failures and prevent domains from resolving correctly, requiring careful review of CNAME target destinations.
Keep authoritative NS records consistent between domain registrar and DNS zone files, as mismatched name server records between registrar settings and actual zone file NS records can cause DNS resolution inconsistencies, confusion about which name servers are authoritative, and potential DNS resolution failures.
Archive JSON exports after DNS changes for traceability and documentation, as exported DNS lookup data provides historical records of DNS configurations before and after changes, enabling rollback if needed, compliance with change management requirements, and documentation for troubleshooting future DNS-related issues.
Use DNS propagation checks to verify changes have reached all regions before announcing domain launches, as DNS propagation can take 24-48 hours depending on TTL values and global cache distribution, requiring verification across multiple locations to ensure consistent DNS resolution worldwide before completing migrations or domain transitions.
Compare results from multiple DNS providers to identify discrepancies or caching issues, as different DNS resolvers may return different results due to caching, geographic location, or DNS provider-specific configurations, and comparing results helps identify inconsistencies that may indicate DNS propagation delays or configuration problems.
Review SOA records to understand zone metadata including primary name server, administrative contact email, serial numbers for change tracking, refresh intervals, and expiration times, as SOA records provide important information about DNS zone management, change history, and administrative contacts for DNS-related inquiries.
Confusing cached DNS results with authoritative data from name servers, when cached results from local DNS resolvers may show outdated information that doesn't reflect current authoritative DNS records, causing incorrect conclusions about DNS configuration status and requiring direct queries to authoritative name servers for accurate current data.
Expecting instant global DNS propagation after making changes, when DNS propagation typically takes hours to days depending on TTL values, global DNS cache distribution, and DNS resolver refresh intervals, causing frustration if changes aren't immediately visible worldwide and requiring patience for full propagation across all DNS caches globally.
Mixing staging or development DNS records into production zones accidentally, when incorrect DNS record types, values, or priorities are added to production DNS configurations, potentially causing service outages, email delivery failures, or routing misconfigurations that affect live production services and require immediate rollback.
Relying on a single DNS resolver or provider for correctness checks, when different DNS providers may have different caching behaviors, geographic coverage, or resolver-specific configurations, causing incomplete understanding of DNS resolution status and missing discrepancies that only appear when querying multiple DNS sources for comprehensive validation.
Ignoring TTL values when planning DNS changes or troubleshooting propagation delays, when high TTL values (several hours or days) cause DNS caches to retain old records longer, delaying propagation of DNS updates and requiring longer wait times before changes become visible, making it important to reduce TTLs before major DNS modifications.
Forgetting to verify both IPv4 and IPv6 records for dual-stack deployments, when missing AAAA records for IPv6-only networks or IPv6-preferring clients cause connection failures, incomplete network connectivity, and suboptimal performance for modern applications requiring dual-protocol support and comprehensive DNS configuration.
Creating circular CNAME references or invalid CNAME chains that prevent DNS resolution, when CNAME records point to domains that eventually reference back to the original domain or create unresolvable loops, causing DNS resolution failures, service unavailability, and requiring careful validation of CNAME target destinations to avoid circular dependencies.
Not checking DNS propagation across multiple global locations before completing migrations, when DNS changes may propagate faster in some regions than others, causing inconsistent resolution worldwide and potential service disruptions if changes are announced before full global propagation, requiring comprehensive propagation checking before considering migrations complete.
Assuming all DNS record types are supported equally across all DNS providers, when some providers or resolvers may have limitations on certain record types, query sizes, or response formats, causing inconsistent results across different DNS lookup tools or resolvers and requiring understanding of provider-specific DNS capabilities and limitations.
Overlooking security implications of DNS misconfigurations like missing SPF records or weak DNS security practices, when absent security-related TXT records (SPF, DKIM, DMARC) allow email spoofing, DNS hijacking vulnerabilities, or unauthorized domain usage, causing security risks that require proper DNS security record implementation and regular DNS security audits.
Not documenting DNS changes or maintaining historical records of DNS configurations, when lack of DNS change history makes troubleshooting difficult, compliance challenging, and rollback impossible if problems occur, requiring systematic DNS change tracking, documentation, and archival of DNS lookup exports before and after modifications.
Expecting DNS lookup tools to fix DNS configuration problems automatically, when DNS lookup tools only query and display existing DNS records without modifying configurations, requiring manual DNS zone file edits, registrar DNS settings updates, or DNS provider control panel changes to actually fix DNS misconfigurations or update record values that need correction.
The tool queries multiple public DNS providers including Google DNS (8.8.8.8), Cloudflare DNS (1.1.1.1), and Quad9 (9.9.9.9) using DNS-over-HTTPS (DoH) for secure, encrypted DNS queries. It tries multiple providers sequentially for reliability, falling back if one provider fails, ensuring robust DNS resolution even if individual DNS services experience issues.
Yes, selecting ALL from the record type dropdown iterates through common DNS record types (A, AAAA, MX, TXT, NS, SOA, CNAME) and aggregates results from all available records. This comprehensive lookup provides complete DNS configuration visibility, though not all domains will have records for every type, and some record types (PTR, SRV) may require specific query formats or separate lookups.
PTR record lookups are supported, but reverse DNS requires querying specific reverse DNS zones (in-addr.arpa for IPv4, ip6.arpa for IPv6) based on IP address ranges. PTR record support varies by network configuration and DNS provider capabilities, and some networks may not have proper reverse DNS configured, requiring IP address input and proper reverse DNS zone format for successful PTR queries.
No, all DNS queries are performed live using DNS-over-HTTPS, and no data is cached or stored server-side. Results are displayed in real-time based on current DNS records. You can export results as JSON locally for your records, but the tool itself doesn't maintain persistent server-side caching, ensuring privacy and up-to-date DNS resolution results.
DNS propagation checking queries multiple DNS providers in different geographic regions to simulate global DNS cache distribution. Results show which locations have propagated new DNS records and which haven't, though actual propagation timing depends on TTL values, DNS resolver refresh intervals, and global cache distribution. Propagation checking provides a snapshot of current propagation status but doesn't guarantee instant global visibility.
Results may vary due to DNS caching at different resolver levels, geographic location of DNS servers, TTL values affecting cache freshness, different DNS provider configurations, or timing differences between queries. Local DNS cache, ISP DNS resolvers, and public DNS providers may return different results depending on cache age and resolver-specific behaviors, requiring awareness of DNS caching when interpreting results.
Yes, verify MX records point to correct mail servers with proper priority values, check TXT records for SPF, DKIM, and DMARC configurations, validate mail server IP addresses are reachable, and confirm DNS records match expected email server configurations. DNS misconfigurations are common causes of email delivery failures, making DNS lookup essential for email troubleshooting workflows.
DNS-over-HTTPS encrypts DNS queries using HTTPS protocol instead of plain UDP/TCP DNS, providing privacy protection, bypassing local DNS cache interference, and securing DNS traffic from interception or manipulation. This tool uses DoH to ensure secure, private DNS resolution that reflects authoritative DNS records rather than potentially outdated local cache entries.
DNS propagation usually takes 24-48 hours for full global distribution, though changes can appear in some regions within minutes or hours depending on TTL values and DNS resolver refresh intervals. Shorter TTLs (300-600 seconds) enable faster propagation, while longer TTLs (hours or days) cause slower propagation. Use propagation checking to monitor progress across regions.
Yes, use the Export JSON button to save comprehensive lookup data including all records, timestamps, response times, and metadata in JSON format. Copy Results provides formatted text summaries for clipboard. The tool maintains local browser history of recent lookups, but for permanent archival, export JSON files that can be stored, shared with technical support, or integrated into documentation and troubleshooting workflows.
Verify records with domain registrar DNS settings, check DNS zone file configurations if you manage DNS directly, compare results across multiple DNS providers to identify inconsistencies, review DNS change history to identify recent modifications, check for unauthorized DNS changes indicating potential security issues, and validate records match expected configurations. Unexpected records may indicate misconfigurations, unauthorized changes, or propagation delays requiring investigation.
The tool queries public DNS resolvers using DNS-over-HTTPS, which typically uses major public DNS providers. For custom or private DNS servers, you may need to configure DNS queries differently or use DNS provider-specific APIs. The tool is optimized for standard public DNS resolution, and private DNS configurations may require specialized tools or direct DNS server access for complete visibility.