Ping Test (ICMP / TCP / HTTP)

This ping test lets you measure reachability and latency across three modes: ICMP (classic ping), TCP connect (socket timing) and HTTP HEAD (application reachability). It’s useful when ICMP is blocked but TCP/HTTPS is allowed, or when you need to see how quickly a web endpoint responds instead of just the network hop. Configure count, timeout and optional port/URL to mirror real-world traffic paths.

Each run records per-attempt timing plus transmission/receive counts, loss percentage and aggregate min/avg/max/stddev. ICMP reflects raw network round-trips, TCP connect measures how fast a socket handshake completes on a given port, and HTTP HEAD captures server/edge responsiveness with redirects followed automatically. Comparing the three highlights where latency is introduced—network, handshake, or application.

Use it to validate VPN/proxy exits, confirm that a CDN POP is reachable, test firewall changes, or baseline latency before rolling out an update. If packet loss appears, you can pivot to traceroute/MTR to see where it starts. TCP/HTTP modes also help when diagnosing “site down” reports that only affect specific ports or paths.

Results are copyable as JSON so you can paste them into tickets, status pages or monitoring runbooks. Client-side validation prevents port ranges and enforces sensible limits (max 10 attempts, short timeouts) so checks stay fast and safe for the target. The tool avoids internal addresses with SSRF protections and only allows http/https for the HTTP mode.

Tips: run multiple small batches instead of one huge test to catch intermittent spikes; compare HTTP HEAD with a browser waterfall if TTFB looks high; and remember that Wi-Fi, VPN encryption and middleboxes can add variable jitter even when raw ICMP looks stable.