Fast DNS and Network Tools
Enter a domain or IP above — DNS lookup, speed test, leak test, SSL check, and more.
Press / to focus search. Tools have dropdown menus for related functions.
DNSApe is a fast, free network diagnostics toolkit for developers, sysadmins, and security researchers. No account required — just type a domain or IP and go.
DNS Lookup
DNS Lookup
Query DNS records for any domain to see how it's configured. DNS (Domain Name System) translates human-readable domain names into IP addresses and provides other critical routing information.
Common Uses
- Find the IP address of a website (A/AAAA records)
- Discover mail servers for a domain (MX records)
- View nameservers responsible for a domain (NS records)
- Check TXT records for SPF, domain verification, and other configurations
History
DNS was invented by Paul Mockapetris in 1983 (RFCs 882/883, later 1034/1035) to replace the unscalable HOSTS.TXT file that previously mapped all internet hostnames.
DNS Lookup
Query DNS records for any domain to see how it's configured. DNS (Domain Name System) translates human-readable domain names into IP addresses and provides other critical routing information.
Common Uses
- Find the IP address of a website (A/AAAA records)
- Discover mail servers for a domain (MX records)
- View nameservers responsible for a domain (NS records)
- Check TXT records for SPF, domain verification, and other configurations
History
DNS was invented by Paul Mockapetris in 1983 (RFCs 882/883, later 1034/1035) to replace the unscalable HOSTS.TXT file that previously mapped all internet hostnames.
Query DNS records, trace resolution paths, or check global propagation.
HTTP Headers
HTTP Headers
Fetch and analyze HTTP response headers from any URL. Headers reveal server configuration, security settings, caching policies, and redirect chains.
Common Uses
- Check security headers (HSTS, CSP, X-Frame-Options)
- Debug redirect chains and identify the final destination
- Analyze caching configuration (Cache-Control, ETag)
- Identify server software and technology stack
History
HTTP headers were defined in the original HTTP/1.0 spec (RFC 1945, 1996). Security headers like HSTS (2012) and CSP (2012) were added later to address evolving web security threats.
HTTP Headers
Fetch and analyze HTTP response headers from any URL. Headers reveal server configuration, security settings, caching policies, and redirect chains.
Common Uses
- Check security headers (HSTS, CSP, X-Frame-Options)
- Debug redirect chains and identify the final destination
- Analyze caching configuration (Cache-Control, ETag)
- Identify server software and technology stack
History
HTTP headers were defined in the original HTTP/1.0 spec (RFC 1945, 1996). Security headers like HSTS (2012) and CSP (2012) were added later to address evolving web security threats.
See request and response headers, follow redirects, debug caching.
Whois
Whois Lookup
Look up registration information for domains and IP addresses. For domains, see registrar, creation/expiration dates, and nameservers. For IPs, see network owner, ASN, and abuse contacts. Domain lookups include both domain and IP WHOIS automatically.
Common Uses
- Find when a domain was registered and when it expires
- Identify the ISP or hosting provider for an IP address
- Check domain status codes and registrar information
- Find abuse contacts for reporting malicious activity
- Research ownership for security investigations
History
Domain WHOIS originated in the 1970s as an ARPANET directory (RFC 812, 1982). IP allocation is managed by IANA and five Regional Internet Registries (RIRs). GDPR (2018) led to privacy redaction of personal registrant data.
Whois Lookup
Look up registration information for domains and IP addresses. For domains, see registrar, creation/expiration dates, and nameservers. For IPs, see network owner, ASN, and abuse contacts. Domain lookups include both domain and IP WHOIS automatically.
Common Uses
- Find when a domain was registered and when it expires
- Identify the ISP or hosting provider for an IP address
- Check domain status codes and registrar information
- Find abuse contacts for reporting malicious activity
- Research ownership for security investigations
History
Domain WHOIS originated in the 1970s as an ARPANET directory (RFC 812, 1982). IP allocation is managed by IANA and five Regional Internet Registries (RIRs). GDPR (2018) led to privacy redaction of personal registrant data.
Domain registration, IP ownership, network ranges, ASN info.
SSL Certificate
SSL/TLS Certificate
Analyze SSL/TLS certificates for any domain including validity dates, certificate chain, issuer information, and security configuration.
Common Uses
- Verify certificate validity and expiration dates
- Check the certificate chain and issuing CA
- Identify weak signature algorithms or key sizes
- Debug SSL/TLS connection issues
History
SSL was created by Netscape in 1995. TLS succeeded it in 1999. Let's Encrypt (2015) revolutionized certificate issuance with free, automated certificates. TLS 1.3 (2018) is the current standard.
SSL/TLS Certificate
Analyze SSL/TLS certificates for any domain including validity dates, certificate chain, issuer information, and security configuration.
Common Uses
- Verify certificate validity and expiration dates
- Check the certificate chain and issuing CA
- Identify weak signature algorithms or key sizes
- Debug SSL/TLS connection issues
History
SSL was created by Netscape in 1995. TLS succeeded it in 1999. Let's Encrypt (2015) revolutionized certificate issuance with free, automated certificates. TLS 1.3 (2018) is the current standard.
Certificate validity, chain, expiration, issuer details.
Email Security
Email Security
Analyze email authentication records (SPF, DKIM, DMARC) to assess a domain's protection against email spoofing and phishing attacks.
Common Uses
- Audit email security configuration before sending campaigns
- Diagnose email deliverability issues
- Verify SPF includes all legitimate sending services
- Check DMARC policy enforcement level
History
Email authentication evolved to combat spam and phishing: SPF (2003) authorizes sending servers, DKIM (2007) signs messages cryptographically, and DMARC (2012) sets enforcement policies.
Email Security
Analyze email authentication records (SPF, DKIM, DMARC) to assess a domain's protection against email spoofing and phishing attacks.
Common Uses
- Audit email security configuration before sending campaigns
- Diagnose email deliverability issues
- Verify SPF includes all legitimate sending services
- Check DMARC policy enforcement level
History
Email authentication evolved to combat spam and phishing: SPF (2003) authorizes sending servers, DKIM (2007) signs messages cryptographically, and DMARC (2012) sets enforcement policies.
Validate SPF, DKIM, and DMARC email authentication records.
Ping
Ping / Latency
Test network connectivity and measure round-trip latency to any host. TCP ping checks if a specific port is reachable and how long connections take.
Common Uses
- Test if a server is reachable from our network
- Measure latency to identify slow connections
- Check specific port accessibility (HTTP, HTTPS, custom)
- Monitor uptime and response consistency
History
Ping was created by Mike Muuss in 1983, named after submarine sonar. Traditional ICMP ping is often blocked, so TCP ping (checking port connectivity) is used as an alternative.
Ping / Latency
Test network connectivity and measure round-trip latency to any host. TCP ping checks if a specific port is reachable and how long connections take.
Common Uses
- Test if a server is reachable from our network
- Measure latency to identify slow connections
- Check specific port accessibility (HTTP, HTTPS, custom)
- Monitor uptime and response consistency
History
Ping was created by Mike Muuss in 1983, named after submarine sonar. Traditional ICMP ping is often blocked, so TCP ping (checking port connectivity) is used as an alternative.
Continuous latency monitoring with live charts. Persists while browsing other tools.
DNS Speed Test
DNS Speed Test
Benchmarks DNS resolution speed from your browser using DNS-over-HTTPS (DoH). Each provider is queried multiple times to calculate average, minimum, and maximum latency — giving you a reliable comparison of DNS resolver performance from your location.
Common Uses
- Compare DNS providers to find the fastest for your location
- Verify that your configured DNS resolver is performing well
- Diagnose slow browsing caused by DNS resolution delays
- Test whether switching DNS providers would improve performance
What You'll See
- Average latency (ms) — lower is better
- Min/Max range — shows consistency
- Bar chart — visual comparison of all providers
- History — previous test results stored locally
Diagnostic Value
- Under 30ms: Excellent — provider has an edge node near you
- 30–80ms: Good — typical for most connections
- 80–150ms: Moderate — may add noticeable delay to page loads
- Over 150ms: Slow — consider switching providers
How to Interpret
Results vary by ISP, location, network congestion, and VPN usage. Run the test a few times for reliable comparisons. The test uses 2 warm-up queries (discarded) and 5 measured queries per provider.
History
DNS-over-HTTPS was standardized in RFC 8484 (2018). Major providers like Cloudflare (1.1.1.1) and Google (8.8.8.8) were among the first to deploy public DoH resolvers, enabling browser-based DNS testing without native socket access.
DNS Speed Test
Benchmarks DNS resolution speed from your browser using DNS-over-HTTPS (DoH). Each provider is queried multiple times to calculate average, minimum, and maximum latency — giving you a reliable comparison of DNS resolver performance from your location.
Common Uses
- Compare DNS providers to find the fastest for your location
- Verify that your configured DNS resolver is performing well
- Diagnose slow browsing caused by DNS resolution delays
- Test whether switching DNS providers would improve performance
What You'll See
- Average latency (ms) — lower is better
- Min/Max range — shows consistency
- Bar chart — visual comparison of all providers
- History — previous test results stored locally
Diagnostic Value
- Under 30ms: Excellent — provider has an edge node near you
- 30–80ms: Good — typical for most connections
- 80–150ms: Moderate — may add noticeable delay to page loads
- Over 150ms: Slow — consider switching providers
How to Interpret
Results vary by ISP, location, network congestion, and VPN usage. Run the test a few times for reliable comparisons. The test uses 2 warm-up queries (discarded) and 5 measured queries per provider.
History
DNS-over-HTTPS was standardized in RFC 8484 (2018). Major providers like Cloudflare (1.1.1.1) and Google (8.8.8.8) were among the first to deploy public DoH resolvers, enabling browser-based DNS testing without native socket access.
Benchmark DNS providers from your browser. Compare Cloudflare, Google, Quad9, and more.
DNS Leak Test
DNS Leak Test
Checks which DNS resolvers your browser can reach and uses WebRTC STUN to detect your real IP addresses. This helps identify DNS leaks that could expose your browsing activity when using a VPN or proxy.
Common Uses
- Verify your VPN is routing DNS queries through the tunnel
- Detect if your ISP DNS is being used despite VPN configuration
- Check for WebRTC IP leaks that bypass VPN protection
- Audit your network privacy configuration
What You'll See
- Detected DNS resolvers — which DoH providers your browser can reach
- Expected vs Unexpected — flags resolvers that shouldn't be reachable through a properly configured VPN
- WebRTC IPs — real IP addresses detected via STUN servers
- Latency per resolver — response time to each DNS provider
Diagnostic Value
- Green (Expected): Known public DNS providers — normal if not using a VPN
- Yellow (Unexpected): Resolvers that shouldn't be reachable if VPN is working
- WebRTC IPs: Should match your VPN IP — if they show your real IP, you have a leak
- No resolvers reachable: May indicate strict DNS filtering or network issues
How to Interpret
This test checks DNS-over-HTTPS reachability from your browser. Traditional DNS (port 53) leaks require different testing. If you're not using a VPN, seeing multiple resolvers is normal and expected.
History
DNS leaks became a major privacy concern with the rise of VPN usage. The term describes situations where DNS queries bypass VPN tunnels, revealing browsing activity to ISPs. WebRTC leaks, discovered around 2015, can similarly expose real IP addresses through browser APIs.
DNS Leak Test
Checks which DNS resolvers your browser can reach and uses WebRTC STUN to detect your real IP addresses. This helps identify DNS leaks that could expose your browsing activity when using a VPN or proxy.
Common Uses
- Verify your VPN is routing DNS queries through the tunnel
- Detect if your ISP DNS is being used despite VPN configuration
- Check for WebRTC IP leaks that bypass VPN protection
- Audit your network privacy configuration
What You'll See
- Detected DNS resolvers — which DoH providers your browser can reach
- Expected vs Unexpected — flags resolvers that shouldn't be reachable through a properly configured VPN
- WebRTC IPs — real IP addresses detected via STUN servers
- Latency per resolver — response time to each DNS provider
Diagnostic Value
- Green (Expected): Known public DNS providers — normal if not using a VPN
- Yellow (Unexpected): Resolvers that shouldn't be reachable if VPN is working
- WebRTC IPs: Should match your VPN IP — if they show your real IP, you have a leak
- No resolvers reachable: May indicate strict DNS filtering or network issues
How to Interpret
This test checks DNS-over-HTTPS reachability from your browser. Traditional DNS (port 53) leaks require different testing. If you're not using a VPN, seeing multiple resolvers is normal and expected.
History
DNS leaks became a major privacy concern with the rise of VPN usage. The term describes situations where DNS queries bypass VPN tunnels, revealing browsing activity to ISPs. WebRTC leaks, discovered around 2015, can similarly expose real IP addresses through browser APIs.
Check which DNS resolvers your browser uses. Detect potential VPN or DNS leaks.
REST API
REST API
Programmatic access to all DNSApe tools via a RESTful JSON API. Rate limited to 60 requests per minute for public access.
Common Uses
- Automate DNS monitoring and alerting
- Integrate network diagnostics into CI/CD pipelines
- Build custom dashboards and reporting tools
- Batch process domain or IP lookups
What You'll See
- GET /api/v1/dns/records?host=example.com - DNS records
- GET /api/v1/dns/traversal?host=example.com&type=A - DNS traversal
- GET /api/v1/whois/domain?host=example.com - Domain WHOIS
- GET /api/v1/whois/ip?host=8.8.8.8 - IP WHOIS
- GET /api/v1/network/headers?host=example.com - HTTP headers
- GET /api/v1/network/ssl?host=example.com - SSL certificate
- GET /api/v1/network/ping?host=example.com - TCP ping
- GET /api/v1/email/security?host=example.com - Email security
History
REST APIs became the standard for web services in the 2000s, replacing XML-based SOAP. JSON format, introduced in 2001, is now the universal data interchange format for APIs.
REST API
Programmatic access to all DNSApe tools via a RESTful JSON API. Rate limited to 60 requests per minute for public access.
Common Uses
- Automate DNS monitoring and alerting
- Integrate network diagnostics into CI/CD pipelines
- Build custom dashboards and reporting tools
- Batch process domain or IP lookups
What You'll See
- GET /api/v1/dns/records?host=example.com - DNS records
- GET /api/v1/dns/traversal?host=example.com&type=A - DNS traversal
- GET /api/v1/whois/domain?host=example.com - Domain WHOIS
- GET /api/v1/whois/ip?host=8.8.8.8 - IP WHOIS
- GET /api/v1/network/headers?host=example.com - HTTP headers
- GET /api/v1/network/ssl?host=example.com - SSL certificate
- GET /api/v1/network/ping?host=example.com - TCP ping
- GET /api/v1/email/security?host=example.com - Email security
History
REST APIs became the standard for web services in the 2000s, replacing XML-based SOAP. JSON format, introduced in 2001, is now the universal data interchange format for APIs.
Programmatic access to all tools. JSON responses, 60 req/min.
MCP Server for AI Assistants
MCP Server
DNSApe MCP (Model Context Protocol) server provides DNS and network diagnostic tools for AI assistants like Claude, ChatGPT, and other LLM-based applications. Connect your AI to real-time network data.
Common Uses
- Let AI assistants diagnose DNS issues in real-time
- Enable LLMs to verify domain configurations
- Provide AI with email security analysis capabilities
- Allow automated network troubleshooting through AI
What You'll See
- dns_lookup - Query DNS records (A, AAAA, MX, TXT, NS, CNAME, SOA)
- whois_lookup - Get WHOIS information for domains and IPs
- http_headers - Fetch HTTP headers and analyze security headers
- ssl_check - Check SSL/TLS certificates and expiration
- tcp_ping - Test connectivity and measure latency
- email_security - Validate SPF, DKIM, and DMARC configuration
Diagnostic Value
- AI can explain complex DNS configurations in plain language
- Automated security audits with intelligent recommendations
- Real-time troubleshooting assistance during incidents
- Integration with AI workflows for monitoring and alerting
Setup Instructions
1. Open Claude Desktop settings (Claude > Settings on Mac, or File > Settings on Windows)
2. Click 'Developer' in the sidebar, then 'Edit Config'
3. Add DNSApe to your claude_desktop_config.json:
{
"mcpServers": {
"dnsape": {
"url": "https://dnsape.com/mcp/dnsape"
}
}
}
4. Save the file and restart Claude Desktop
5. Ask Claude to look up DNS records, check SSL certificates, etc.
1. In ChatGPT, click your profile icon and select 'Settings'
2. Navigate to 'Connected apps' or 'Plugins' section
3. Click 'Add MCP Server' or 'Connect new server'
4. Enter the server URL: https://dnsape.com/mcp/dnsape
5. Name it 'DNSApe' and save
6. Ask ChatGPT to perform DNS lookups, check email security, etc.
1. Use the MCP server URL: https://dnsape.com/mcp/dnsape
2. The server supports standard MCP protocol over HTTP
3. Available tools: dns_lookup, whois_lookup, http_headers, ssl_check, tcp_ping, email_security
4. Refer to your client's documentation for adding remote MCP servers
History
The Model Context Protocol (MCP) was introduced by Anthropic in 2024 to standardize how AI assistants interact with external tools and data sources. It enables AI to access real-world information through structured tool interfaces.
MCP Server
DNSApe MCP (Model Context Protocol) server provides DNS and network diagnostic tools for AI assistants like Claude, ChatGPT, and other LLM-based applications. Connect your AI to real-time network data.
Common Uses
- Let AI assistants diagnose DNS issues in real-time
- Enable LLMs to verify domain configurations
- Provide AI with email security analysis capabilities
- Allow automated network troubleshooting through AI
What You'll See
- dns_lookup - Query DNS records (A, AAAA, MX, TXT, NS, CNAME, SOA)
- whois_lookup - Get WHOIS information for domains and IPs
- http_headers - Fetch HTTP headers and analyze security headers
- ssl_check - Check SSL/TLS certificates and expiration
- tcp_ping - Test connectivity and measure latency
- email_security - Validate SPF, DKIM, and DMARC configuration
Diagnostic Value
- AI can explain complex DNS configurations in plain language
- Automated security audits with intelligent recommendations
- Real-time troubleshooting assistance during incidents
- Integration with AI workflows for monitoring and alerting
Setup Instructions
1. Open Claude Desktop settings (Claude > Settings on Mac, or File > Settings on Windows)
2. Click 'Developer' in the sidebar, then 'Edit Config'
3. Add DNSApe to your claude_desktop_config.json:
{
"mcpServers": {
"dnsape": {
"url": "https://dnsape.com/mcp/dnsape"
}
}
}
4. Save the file and restart Claude Desktop
5. Ask Claude to look up DNS records, check SSL certificates, etc.
1. In ChatGPT, click your profile icon and select 'Settings'
2. Navigate to 'Connected apps' or 'Plugins' section
3. Click 'Add MCP Server' or 'Connect new server'
4. Enter the server URL: https://dnsape.com/mcp/dnsape
5. Name it 'DNSApe' and save
6. Ask ChatGPT to perform DNS lookups, check email security, etc.
1. Use the MCP server URL: https://dnsape.com/mcp/dnsape
2. The server supports standard MCP protocol over HTTP
3. Available tools: dns_lookup, whois_lookup, http_headers, ssl_check, tcp_ping, email_security
4. Refer to your client's documentation for adding remote MCP servers
History
The Model Context Protocol (MCP) was introduced by Anthropic in 2024 to standardize how AI assistants interact with external tools and data sources. It enables AI to access real-world information through structured tool interfaces.
Give your AI DNS lookup, WHOIS, HTTP headers, SSL checks, ping, and email security tools
DNSApe provides a Model Context Protocol (MCP) server that gives AI assistants direct access to all DNSApe tools. Single URL, no API key, no authentication required.
What is MCP? The Model Context Protocol is an open standard that lets AI assistants (like Claude, ChatGPT, and others) use external tools directly. Instead of the AI guessing or asking you to look things up, it can query DNSApe itself.
What can the AI do? Once connected, your AI assistant can perform DNS lookups, check WHOIS records, inspect HTTP headers, verify SSL certificates, ping hosts, and audit email security — all without you leaving the conversation.
How it works: You add the DNSApe MCP URL to your AI client once. After that, the AI can call any DNSApe tool as needed. Queries go directly from the AI to DNSApe's API — no browser required.
Privacy & limits: No account or API key needed. All queries are anonymous. Rate limited to 60 requests per minute. The AI only accesses public DNS/network data — the same information anyone can look up.
Claude Desktop — Config File
Add to claude_desktop_config.json:
{
"mcpServers": {
"dnsape": {
"type": "url",
"url": "https://dnsape.com/mcp/dnsape"
}
}
}
Claude Desktop — GUI
Add via the Integrations menu:
- Open Settings → Integrations
- Click Add custom connector
- Paste the URL:
https://dnsape.com/mcp/dnsape - Name it DNSApe and save
Claude Code
Run in your terminal:
claude mcp add dnsape \ --transport sse \ https://dnsape.com/mcp/dnsape
ChatGPT
In ChatGPT settings → Connections → Add MCP:
- Open Settings → Connections
- Click Add connection, choose MCP
- Paste the URL:
https://dnsape.com/mcp/dnsape - Name it DNSApe and save