Network troubleshooting commands

Get the ping, port, traceroute, DNS, curl, TLS, routing, MTU and packet capture commands for Linux, macOS or Windows, with each flag explained.

Runs locally. Nothing you paste leaves this tab.

    Work up the layers

    Most “the network is down” problems are one of these. Check them in order and stop at the first one that fails.

    1. DNS: does the name resolve, and to the address you expect? Compare the system resolver with a public one.
    2. Route: does traffic for that address leave through the interface you expect (VPN, not Wi-Fi)?
    3. TCP: is the port open? Refused means nothing listens there; timed out means a firewall drops it.
    4. TLS: is the certificate valid for the name, not expired, and sent with its intermediate?
    5. HTTP: what status and headers come back, and which step is slow?

    A failed ping proves little: many networks block ICMP. Test the port the application uses instead.

    View this tool’s source · Report a problem

    Support on Ko-fi