DNSApe | Fast Network Tools

DNSApe

Settings

Winter snow effect

Fast Network Diagnostics

Enter a domain or IP above and choose a tool to get started.

Some tools have menus to surface related tools.

Ping tool is persistent while browsing other tools. 5-minute limit.

/ focuses the Domain or IP search box. Esc clears it and closes popups.

Click help icons for usage, more info, and history. Learn while you troubleshoot!

Add DNSApe to Slack, or the DNSApe MCP to Claude or ChatGPT with instructions in those help sections.

Sorry she's a bit of a dog, contradicting the "Fast" tagline above... I needed to get it in production environment to see pain points - v2.1 will be much faster!

old.dnsape.com is available if you want the prior experience, and will stay around as long as there is traffic.

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.

Query DNS records, trace resolution paths, or check global propagation.

google.com - See all DNS records

example.com - Check propagation after changes

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.

See request and response headers, follow redirects, debug caching.

github.com - Check security headers

t.co - Follow redirect chains

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.

Domain registration, IP ownership, network ranges, ASN info.

apple.com - Domain + IP info combined

8.8.8.8 - IP ownership lookup

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.

Certificate validity, chain, expiration, issuer details.

stripe.com - EV certificate example

expired.badssl.com - Test expired cert

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.

Validate SPF, DKIM, and DMARC email authentication records.

google.com - Well-configured example

github.com - Check email auth setup

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.

Continuous latency monitoring with live charts.

cloudflare.com - Monitor uptime

google.com - Track latency over time

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.

Programmatic access to all tools. JSON responses, 60 req/min.

GET /api/v1/dns/records?host=example.com

GET /api/v1/whois/domain?host=example.com

Slack Integration

Slack Integration

Run DNSApe lookups directly from any Slack channel using slash commands. Results use Slack Block Kit for rich formatting with status indicators and organized sections.

Common Uses

Quick DNS lookups during incident response

Share diagnostic results with your team instantly

Investigate suspicious domains or IPs in security channels

Check SSL certificates or email security without leaving Slack

What You'll See

/dns example.com - Look up DNS records

/whois example.com - Domain registration info

/ipwhois 8.8.8.8 - IP ownership info

/headers example.com - HTTP response headers

/ssl example.com - SSL certificate details

/ping example.com - TCP ping test

/email example.com - Email security check

Setup Instructions

One-click Slack app install coming soon (pending Slack approval). For now, use these manual setup steps:

1. Go to api.slack.com/apps and click 'Create New App'

2. Choose 'From scratch', name it (e.g., 'DNSApe'), and select your workspace

3. In the sidebar, click 'Slash Commands' and create commands for each tool:

- Command: /dns, Request URL: https://dnsape.com/slack/dns

- Command: /whois, Request URL: https://dnsape.com/slack/whois

- Command: /ipwhois, Request URL: https://dnsape.com/slack/ipwhois

- Command: /headers, Request URL: https://dnsape.com/slack/headers

- Command: /ssl, Request URL: https://dnsape.com/slack/ssl

- Command: /ping, Request URL: https://dnsape.com/slack/ping

- Command: /email, Request URL: https://dnsape.com/slack/email

4. Click 'Install to Workspace' and authorize the app

5. Use any command in Slack: /dns google.com

History

Slack launched in 2013 and introduced slash commands as a way to integrate external services. Slash commands provide a natural way for teams to access tools without leaving their communication platform.

Run lookups directly from Slack with slash commands.

/dns google.com - DNS records

/whois apple.com - Domain info

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.

Connect AI assistants to DNSApe tools via MCP protocol.

dns_lookup - Query DNS records

ssl_check - Certificate info

Your IP: 216.73.216.115

About DNSApe

DNSApe is a fast, no-nonsense network diagnostics toolkit built for developers, sysadmins, and security researchers.

Version History

2.0 - 2025-12-21

Complete rewrite

Rebuilt with Laravel 12, Livewire 3, and Tailwind CSS 4
Live ping monitoring with real-time Chart.js visualization
Email Security tool: SPF, DKIM, DMARC validation
REST API with JSON responses (60 req/min)
MCP server for AI assistant integration (Claude, ChatGPT, etc.)
Slack integration with /dns, /whois, /ssl slash commands
Help tooltips explaining each tool and record type
Shareable ping sessions with unique URLs
Pretty/Raw view toggle with persistent preference
Browser-based ping for client-side latency testing
Enhanced WHOIS with domain + IP info combined
Improved SSL certificate error handling

Version 2.1 with performance improvements and bug fixes coming soon.

1.1.3 - 2019-04-30

Moved to new infrastructure, resolving most DNS Traversal issues
Replaced RBL with SSL validation tool

1.1.2 - 2019-04-17

Fixed DNS Traversal issue causing many requests to fail

1.1.1 - 2019-04-16

Minor UI adjustments
Added links to lookups in DNS results
Updated dependencies
Increased session timeout to 1 week to eliminate 419 errors
Updated IP address display
Removed dnsape.com as default lookup

1.1 - 2019-02-15

Several UI adjustments
Dark mode setting is persistent between sessions via cookie
Added GDPR cookie banner for session cookies
Added tool to show client IP in lookup field (settings menu)
Keyboard shortcuts for tools, focusing, text size, copying URLs
Shareable lookup URLs - browser address changes with tool usage
Added links to Github repo and feature voting
Several error handling and bug fixes

1.0.7 - 2019-01-11

Fixed HTTP Headers issue with multiple HTTPS redirects

1.0.6 - 2019-01-09

HTTP Headers now forward to and display HTTPS headers
UI adjustments

1.0.5 - 2019-01-08

Dark Mode!

1.0.4 - 2019-01-07

TLD and subdomain validation fixes

1.0.3 - 2019-01-06

Updated DNS Cache host list
IP address validation improvements
Fixed progress bar bug with failed queries
UI adjustments

1.0.2 - 2019-01-05

IPWhois and Ping now work with IP addresses as well as hostnames
Several validation enhancements reduce errors for many lookups
Several UI adjustments

1.0.1 - 2019-01-04

Added Recent Updates panel
Fixed Whois search for many TLDs
Fixed DNS Traversal for many TLDs
Changed to fluid viewport width
Added Privacy Policy

1.0 - 2019-01-02

Initial release