Query domain name DNS records, resolve to IP addresses, test connectivity with ping, and display geolocation information
Features
- DNS Resolution: Resolve domain names to IP addresses using DNS over HTTPS (DoH), supporting multiple DNS providers with automatic failover for high availability
- Ping Testing: Test domain connectivity using HTTP HEAD requests, measure response time, and check HTTP/HTTPS status codes to verify server availability
- Geolocation Display: Automatically query geolocation information for resolved IP addresses, displaying country, region, city, coordinates, and network information on an interactive map
- Multiple IP Support: Display all IP addresses resolved from domain name A records, supporting domains with multiple IP addresses for load balancing or CDN configurations
Usage Guide
- Enter Domain Name: Enter the domain name you want to query in the input box (e.g., example.com). The tool will automatically remove protocol prefixes (http://, https://) and www prefixes.
- Execute DNS Lookup: Click the 'Lookup' button or press Enter to query DNS records. The system will resolve the domain name to IP addresses using DNS over HTTPS (DoH) and display the results.
- Test Connectivity: Click the 'Ping' button to test domain connectivity using HTTP HEAD requests. Select HTTP or HTTPS protocol, and view response time and status code.
- View Results: View DNS resolution results (IP addresses), geolocation information (country, region, city, coordinates), network information (ISP, ASN), and map visualization.
Technical Details
DNS over HTTPS (DoH)
DNS over HTTPS is a protocol that encrypts DNS queries using HTTPS, improving privacy and security. This tool uses Google DNS and Cloudflare DNS DoH services to resolve domain names. DoH queries are sent over HTTPS connections, preventing DNS query interception and tampering. The tool implements automatic failover: if Google DNS fails, it automatically switches to Cloudflare DNS to ensure query success rate.
HTTP Ping Implementation
Since Cloudflare Workers does not support ICMP ping, this tool uses HTTP HEAD requests to simulate ping functionality. HEAD requests only retrieve response headers without downloading content, making them faster than GET requests. The tool measures the time from sending the request to receiving the response header, calculating response time. It supports both HTTP and HTTPS protocols, allowing users to test different service endpoints.
Domain Name Format Validation
Domain name validation follows RFC 1123 standards: domain names consist of labels separated by dots, each label can contain letters, numbers, and hyphens, must start and end with alphanumeric characters, maximum length 63 characters per label, total domain name length maximum 253 characters. The tool automatically removes protocol prefixes (http://, https://) and www prefixes before validation, ensuring accurate domain name parsing.
Frequently Asked Questions
- Why does ping use HTTP HEAD instead of ICMP?
- Cloudflare Workers (where this tool runs) does not support ICMP ping protocol. HTTP HEAD requests are used as an alternative: they test server connectivity, measure response time, and check HTTP status codes. While not identical to ICMP ping, HTTP ping provides similar functionality for web-based tools and works better in browser environments.
- What's the difference between DNS lookup and ping?
- DNS lookup resolves domain names to IP addresses by querying DNS servers. Ping tests server connectivity by sending HTTP requests and measuring response time. DNS lookup tells you where the domain points to (IP addresses), while ping tells you if the server is reachable and how fast it responds. Both are useful for network troubleshooting.
- Why might a domain have multiple IP addresses?
- Domains can have multiple IP addresses for several reasons: 1) Load balancing - distributing traffic across multiple servers; 2) Redundancy - backup servers for high availability; 3) CDN - content delivery networks use multiple IPs in different locations; 4) Round-robin DNS - rotating between multiple servers. The tool displays all resolved IP addresses.
- How accurate is the geolocation information?
- Geolocation accuracy depends on IP address allocation and routing. Typically accurate to city or regional level, not precise physical addresses. For CDN and cloud services, geolocation may show data center locations rather than actual server locations. Mobile networks and VPNs may show ISP locations rather than user locations. The location is approximate and based on IP address ranges.
Related Documentation
- RFC 1035 - Domain Names - Official DNS protocol specification, defining domain name structure, DNS query format, and record types
- RFC 8484 - DNS over HTTPS - DNS over HTTPS (DoH) protocol specification, defining how to send DNS queries over HTTPS
- Google DNS Documentation - Google Public DNS service documentation, including DNS over HTTPS API usage
- Cloudflare DNS Documentation - Cloudflare DNS over HTTPS service documentation and API reference
- MDN - DNS - Mozilla Developer Network DNS documentation, explaining DNS concepts and working principles