network_diagnosis

To troubleshoot a website outage or API timeout, run a structured workflow of DNS resolution, ping, port checks, and HTTP probes to pinpoint the exact failure point. This layered diagnosis identifies whether the root cause is DNS failure, IP unreachability, or firewall restrictions.

The best way to check if a network port is blocked by a firewall is to perform a targeted port check after confirming host reachability. This verifies if specific service ports are open and accessible across public networks or blocked by network restrictions.

DNS resolution may fail due to misconfigured records or server issues, and you can diagnose it by running a DNS lookup as the first step in a network diagnostic workflow. This isolates whether the connectivity issue originates at the domain resolution layer.

To perform an HTTP responsiveness check for a slow-loading site, execute an HTTP probe after verifying DNS resolution and port availability. This tests the web server's application-layer response and helps isolate latency issues from underlying network reachability problems.

Yes, you can diagnose network connectivity issues across public networks without external dependencies by applying this structured workflow. It uses built-in diagnostic logic for DNS lookups, ping, port checks, and HTTP probes to identify root causes independently.

You should use a layered network diagnosis instead of a simple ping test when a host is reachable but services still fail, requiring DNS lookup, port checks, and HTTP probes to infer the root cause. A ping test only confirms IP reachability, missing firewall or application-layer failures.