Two checks answer different questions
Ping measures ICMP replies. Opening a website involves DNS, a network connection, TLS for HTTPS, and an HTTP response. A firewall can ignore Echo requests while allowing web traffic. Missing replies alone cannot identify which of those services is working.
Interpret the combination
In the example, no ICMP reply arrived but the HTTP request succeeded. This is consistent with ICMP filtering; it does not prove filtering is the cause. Compare the tested IP addresses and IP versions before combining results. A domain may lead to different servers.
Keep the measurement in context
An online Ping runs from the service running the check. Its latency is not your device’s latency. Four replies form a short sample, not an uptime history. Use repeated observations to investigate intermittent behavior, and retain the target and timestamps when sharing evidence.
Example
Illustrative results — not a live test Ping: 4 sent, 0 received, 100% packet loss HTTP: 200 OK Interpretation: HTTPS responded; ICMP reachability is unconfirmed.
What to check next
- Look up the domain’s A and AAAA records.
- Run Ping and HTTP Status using the same IP version.
- If HTTP also fails, inspect DNS and TLS findings. Use Traceroute for route clues; missing intermediate replies are not conclusive failures.