macOS Network Diagnostic Tools: What's Built In, What's Missing
A complete guide to mac network diagnostic tools: Wireless Diagnostics, Terminal commands, what Apple removed in Monterey, and free GUI alternatives.
macOS ships with real network diagnostic capability, but finding it takes some digging. The tools that do exist are scattered across System Settings, Terminal, and hidden menus. The tools that would make this easy for everyone were removed. Here’s the full picture.
| Feature | Stock macOS | With NetUtil |
|---|---|---|
| Wireless Diagnostics | ✓ | ✓ |
| ping / traceroute / dig (Terminal) | ✓ | ✓ |
| networkQuality | ✓ | ✓ |
| Ping GUI | – | ✓ |
| Traceroute GUI | – | ✓ |
| DNS Lookup / Whois GUI | – | ✓ |
| Port Scan GUI | – | ✓ |
Stock macOS covers the basics but drops you into Terminal for anything beyond connection status. NetUtil adds the GUI tools that Apple removed.
What macOS gives you out of the box
Wireless Diagnostics
Hold Option and click the Wi-Fi icon in your menu bar. You’ll see “Open Wireless Diagnostics.” Most Mac users never find this because it’s invisible unless you know the shortcut.
Once open, it’s genuinely capable. The scan tab shows every nearby access point with channel, signal strength, and noise levels. The performance monitor graphs throughput and signal quality over time. The sniffer captures raw packets for analysis in Wireshark.
For Wi-Fi problems specifically, Wireless Diagnostics is the right tool. Channel interference, signal degradation, competing access points: it surfaces all of that. The frustrating part is just finding it.
Terminal commands
Every Mac ships with a full set of network diagnostic tools in Terminal. These are standard Unix utilities that have been around for decades and aren’t going anywhere.
ping checks whether a host is reachable:
ping -c 5 google.com
traceroute maps the path between your Mac and a destination, showing each hop along the way:
traceroute google.com
nslookup and dig handle DNS lookups:
nslookup google.com
dig google.com MX
whois retrieves domain registration information:
whois google.com
netstat shows active network connections and listening ports:
netstat -an | grep LISTEN
These tools work. If you’re comfortable in Terminal, you can handle most network diagnostics with what’s already on your Mac. The limitation is that the output is plain text, reading it takes practice, and none of this is accessible to users who aren’t command line regulars.
networkQuality
Apple added a command line tool called networkQuality in macOS Monterey. It measures upload and download speed plus responsiveness under load:
networkQuality
The output includes RPM (round-trips per minute), which gives you a sense of how your connection holds up during video calls or other real-time applications. It’s a solid addition. It’s also completely hidden unless you already know to look for it.
System Settings and the Network preference pane
System Settings shows basic connection status: whether Wi-Fi or Ethernet is connected, your IP address, signal strength. For everyday “am I connected?” questions, this is enough.
It doesn’t help you troubleshoot anything beyond that.
What’s missing since macOS Monterey
Network Utility is gone
Apple removed Network Utility in macOS Monterey, ending over two decades of availability. The app bundled seven tools in a single GUI: Ping, Traceroute, Lookup (DNS), Whois, Finger, Port Scan, and Netstat. None of the underlying capabilities disappeared, but the interface did.
This mattered because Network Utility was the only built-in option for people who needed network diagnostics but didn’t want to use Terminal. Type a hostname, click a button, get results. Simple. That’s gone.
Port scanning with a GUI
Network Utility’s port scanner had no direct replacement. You can scan ports using nc (netcat) or install nmap, but nothing comes built in with a graphical interface.
# Check if port 443 is open on a host
nc -zv google.com 443
Port scanning is useful for verifying that services are running, testing firewall rules, and debugging connection failures. Without a GUI tool, it’s inaccessible to most users.
Readable results
Terminal output is functional but not readable. A traceroute scrolls past line by line. Netstat dumps hundreds of connections in plain text. There’s no column sorting, no highlighting, no way to focus on what matters.
macOS gives you data. It doesn’t help you interpret it.
What fills the gap
Third-party apps have stepped in where Apple stepped back. The quality varies significantly. Many are thin wrappers around the same command line tools with minimal thought put into the presentation. A few are genuinely well-built.
When evaluating mac network diagnostic tools, the things that matter most:
Coverage: Does it have all the core tools? Ping, Traceroute, DNS Lookup, Whois, and Port Scan are the essentials. Netstat is useful for developers and admins.
Privacy: Some tools, especially web-based ones, route your queries through their servers. That means the tool operator can see what hosts you’re scanning and what domains you’re looking up. A local app that runs queries directly from your Mac doesn’t have this problem.
Native feel: Apps built with macOS frameworks start faster, feel more responsive, and look right on Retina displays and Apple Silicon.
NetUtil
We built NetUtil to restore what Apple removed. It includes all seven classic Network Utility tools: Ping, Traceroute, DNS Lookup, Netstat, Whois, Finger, and Port Scan. Everything runs locally. No data is sent to external servers.
The app is native SwiftUI, so results display in clean tables and formatted output rather than raw terminal text. It works on both Apple Silicon and Intel Macs.
NetUtil won’t replace Wireless Diagnostics for Wi-Fi analysis, and it’s not trying to. For diagnosing a slow connection to a specific host, checking DNS records, scanning ports on a server, or tracing the network path to a destination, it’s what’s missing from a stock Mac.
It’s free.
For port-specific work, Portie goes deeper: live monitoring of every open TCP/UDP port on your Mac, grouped by application, with optional remote scanning.
Which tool for which problem
“Is this server reachable?” Run ping hostname in Terminal, or use NetUtil’s Ping tab.
“Why is this connection slow?” Run a traceroute. Terminal works, but a GUI makes it easier to spot where latency spikes. Also run networkQuality to check your actual bandwidth.
“Something is wrong with my Wi-Fi” Open Wireless Diagnostics (Option-click the Wi-Fi icon). It’s the best tool for signal and interference analysis.
“Is a specific port open on this server?” This requires a third-party tool. NetUtil’s Port Scan tab handles it, or use Portie for ongoing local monitoring.
“What DNS records does this domain have?” Either dig domain.com in Terminal (flexible but requires knowing the flags) or NetUtil’s DNS Lookup tab.
“I want all of the above without Terminal” That’s what Network Utility provided for 20 years. NetUtil picks up where it left off.