I tried using the ping command on a https page, but the message says that ping could not find the host. Is there some issue regarding ping and https?

  • 6
    Short answer: Ping and HTTPS have nothing in common. Ping is a low level network tool whereas HTTPS is an application layer protocol (or rather, an URI scheme). – slhck Aug 22 '11 at 13:35
  • 4
    If you want to test that you ssl site is responding correctly use openssl this way: "openssl s_client -connect google.com:443" Then you can issue a GET command followed by two presses on the return key like this: "GET / HTTP/1.1" – Shadok Aug 22 '11 at 14:03
  • In case anybody ended up here looking for a ping-like tool for https, I just wrote one: github.com/voutasaurus/sup – voutasaurus May 6 '16 at 0:02

The answer to your question (Can you get a reply from a HTTPS site using the Ping command?) is Yes, you can, as long as ICMP replies are enabled on the HTTPS site provider. However, it has nothing to do with HTTP or HTTPS:

Ping will use ICMP protocol, it belongs to TCP/IP Internet Layer, which is a lower layer than HTTP or HTTPs (from Application Layer):

Ping operates by sending Internet Control Message Protocol (ICMP) echo request packets to the target host and waiting for an ICMP response. In the process it measures the time from transmission to reception (round-trip time)1 and records any packet loss. The results of the test are printed in form of a statistical summary of the response packets received, including the minimum, maximum, and the mean round-trip times, and sometimes the standard deviation of the mean.

You can test with "cmd" (Windows Start button / type cmd in the search box, open "cmd.exe"), then with ping:

ping www.hotmail.com

If you try to ping a HTTP URL, such it follows:

ping http://www.hotmail.com

You will get the same error that you would get when trying to ping a HTTPS based URL:

ping https://www.hotmail.com

(An error something like that ping cant reach the requested address will appear on both attempts).


ping works at a much lower level than HTTP or HTTPS, and only accepts hostnames, not URLs. For example:

ping www.google.com

tcping - simulate "ping" over tcp by establishing a connection to network hosts. tcping at application level will send SYN, waiting for ACK, closing with FIN ACK

C:\>tcping google.com 443

Probing - Port is open - time=19.787ms
Probing - Port is open - time=20.487ms
Probing - Port is open - time=24.494ms

Ping statistics for
     3 probes sent.
     3 successful, 0 failed.
Approximate trip times in milli-seconds:
     Minimum = 19.787ms, Maximum = 24.494ms, Average = 21.589ms

You can issue a HEAD request with OpenSSL:

openssl s_client -quiet -connect github.com:443 <<eof
Connection: close
Host: github.com


Note that you can also use "HTTP/2", but be careful because some servers (e.g. github.com) do not support it.

protected by Community Jun 30 '15 at 18:58

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.