Connectivity Checklist
Walk through common network troubleshooting checks in a structured workflow.
How to use this toolThis checklist is local. It does not send probes, run commands or change network settings.
Suggested next check: Check the local network connection
Record whether the failure affects one application, one device or every device. A site-wide outage and a local configuration issue need different investigations.
Confirm Wi-Fi/Ethernet is connected and the device has an address and default gateway. Commands: ip addr and ip route on Linux; ipconfig on Windows.
Run nslookup your-domain.example or dig your-domain.example. Compare with an expected DNS answer. A missing record differs from a timeout or SERVFAIL.
Use traceroute your-domain.example on Linux/macOS or tracert on Windows. Routers can suppress responses; unanswered hops alone do not prove a fault.
Use curl -I https://your-domain.example. Review TLS certificate dates and HTTP status. A 404 or 500 shows the server responded; investigate the application next.
Check whether local rules or managed policies block the destination. Ask your administrator before changing managed settings.
Record exact timestamps, affected URL, network and status. For slow pages, inspect browser Network timings and compare cached and uncached requests.
Checked means you performed the check, not that it passed. Keep actual results in your incident notes. No single test establishes connectivity or security.