NetDebug ToolkitPing, DNS, Whois, Traceroute, Port Scan, TLS Inspector, Wake-on-LAN, and more — chain any of them into one-tap workflows with the new My Automation builder.
Chain any combination of tools into a one-tap workflow. See every result on one screen, export the whole run as PDF, PNG, or text, and trigger it from a deeplink.
Save frequently tested hosts and run any tool against them instantly with one tap. Export the result as PDF, PNG, or text, and trigger it from a deeplink.
Every run is saved on-device and charted over time — latency, speed, reachability, and more. Free, with longer retention as a bundle perk.
Every tool returns clean, structured results designed for quick troubleshooting — not walls of text.
Everything you need for network diagnostics, organized by workflow.
Check host reachability and measure response time.
Inspect status codes, redirect chains, and TLS summaries.
Measure latency, jitter, download, and upload speed.
TCP throughput tests against an external iperf3 server.
Trace the network path and latency to any destination.
Find the largest packet a path carries and detect MTU black holes.
Test if a specific TCP or UDP host:port is reachable.
Query an NTP time server and compare it with the device clock.
View your public IP, ISP, ASN, and approximate location.
Look up domain or IP registration details via RDAP and WHOIS.
Resolve DNS records with optional custom resolver support.
Explore A, AAAA, CNAME, MX, TXT, NS, SRV records with TTL.
Inspect certificate expiry, SAN entries, issuer chain, and weak signals.
Scan selected TCP ports and review open/closed/filtered outcomes.
Ask a server on the internet to connect back to a port on your public IP.
Discover active devices on your local subnet.
Calculate subnet details, boundaries, and host counts from CIDR.
Discover .local Bonjour services like AirPlay, HomeKit, and printers.
Detect gateway UPnP IGD and NAT-PMP with external-IP hints.
Send a magic packet to wake compatible devices on your network.
Guides to the network problems people actually run into, from Wi-Fi that connects to nothing through to self-hosting behind CGNAT.
Four tests, in order, that tell you whether it is your device, your router, DNS or your ISP.
NXDOMAIN, SERVFAIL and timeouts are different problems. One comparison tells them apart.
Why speed tests miss it, how long to run the test, and the traceroute trap that fools everyone.
Lag is latency, not bandwidth. Where the delay is added and which part you can actually fix.
Seven things have to be true. Start with the ten second check that rules out CGNAT.
Each certificate error points somewhere different. Start by checking your clock.
All server side, all different. Which one means crashed, which means slow, which means deliberate.
A call needs a few megabits. It is jitter that breaks it, and a speed test cannot see jitter.
Scan your subnet, name every device, and judge an unfamiliar one properly.
If your router's WAN address is not your public IP, no forwarding rule will ever work. Five options that do.
Real certificates on services nobody outside can reach, with no open ports and no browser warnings.
Container up, logs clean, nothing connects. Six causes, and the test that rules out the other five.