Can you get a reply from a HTTPS site using the Ping command?











up vote
44
down vote

favorite
8












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?










share|improve this question




















  • 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















up vote
44
down vote

favorite
8












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?










share|improve this question




















  • 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













up vote
44
down vote

favorite
8









up vote
44
down vote

favorite
8






8





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?










share|improve this question















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?







http ping https






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 22 '11 at 13:38









slhck

158k47437461




158k47437461










asked Aug 22 '11 at 13:33









Shamim Hafiz

53141728




53141728








  • 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














  • 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








6




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






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




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






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




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










4 Answers
4






active

oldest

votes

















up vote
35
down vote



accepted










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).






share|improve this answer






























    up vote
    19
    down vote













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



    ping www.google.com





    share|improve this answer




























      up vote
      5
      down vote













      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 87.106.83.127:443/tcp - Port is open - time=19.787ms
      Probing 87.106.83.127:443/tcp - Port is open - time=20.487ms
      Probing 87.106.83.127:443/tcp - Port is open - time=24.494ms
      Control-C

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





      share|improve this answer






























        up vote
        2
        down vote













        You can issue a HEAD request with OpenSSL:



        openssl s_client -quiet -connect github.com:443 <<eof
        HEAD / HTTP/1.1
        Connection: close
        Host: github.com

        eof


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






        share|improve this answer






















          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?














          4 Answers
          4






          active

          oldest

          votes








          4 Answers
          4






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          35
          down vote



          accepted










          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).






          share|improve this answer



























            up vote
            35
            down vote



            accepted










            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).






            share|improve this answer

























              up vote
              35
              down vote



              accepted







              up vote
              35
              down vote



              accepted






              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).






              share|improve this answer














              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).







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Nov 19 '17 at 13:19









              Glorfindel

              1,30841220




              1,30841220










              answered Aug 22 '11 at 13:42









              Diogo

              21.9k55132209




              21.9k55132209
























                  up vote
                  19
                  down vote













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



                  ping www.google.com





                  share|improve this answer

























                    up vote
                    19
                    down vote













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



                    ping www.google.com





                    share|improve this answer























                      up vote
                      19
                      down vote










                      up vote
                      19
                      down vote









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



                      ping www.google.com





                      share|improve this answer












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



                      ping www.google.com






                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Aug 22 '11 at 13:35









                      grawity

                      230k35486544




                      230k35486544






















                          up vote
                          5
                          down vote













                          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 87.106.83.127:443/tcp - Port is open - time=19.787ms
                          Probing 87.106.83.127:443/tcp - Port is open - time=20.487ms
                          Probing 87.106.83.127:443/tcp - Port is open - time=24.494ms
                          Control-C

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





                          share|improve this answer



























                            up vote
                            5
                            down vote













                            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 87.106.83.127:443/tcp - Port is open - time=19.787ms
                            Probing 87.106.83.127:443/tcp - Port is open - time=20.487ms
                            Probing 87.106.83.127:443/tcp - Port is open - time=24.494ms
                            Control-C

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





                            share|improve this answer

























                              up vote
                              5
                              down vote










                              up vote
                              5
                              down vote









                              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 87.106.83.127:443/tcp - Port is open - time=19.787ms
                              Probing 87.106.83.127:443/tcp - Port is open - time=20.487ms
                              Probing 87.106.83.127:443/tcp - Port is open - time=24.494ms
                              Control-C

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





                              share|improve this answer














                              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 87.106.83.127:443/tcp - Port is open - time=19.787ms
                              Probing 87.106.83.127:443/tcp - Port is open - time=20.487ms
                              Probing 87.106.83.127:443/tcp - Port is open - time=24.494ms
                              Control-C

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






                              share|improve this answer














                              share|improve this answer



                              share|improve this answer








                              edited Mar 28 '15 at 10:45









                              karel

                              9,17793138




                              9,17793138










                              answered Mar 28 '15 at 10:14









                              mdadm

                              5111




                              5111






















                                  up vote
                                  2
                                  down vote













                                  You can issue a HEAD request with OpenSSL:



                                  openssl s_client -quiet -connect github.com:443 <<eof
                                  HEAD / HTTP/1.1
                                  Connection: close
                                  Host: github.com

                                  eof


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






                                  share|improve this answer



























                                    up vote
                                    2
                                    down vote













                                    You can issue a HEAD request with OpenSSL:



                                    openssl s_client -quiet -connect github.com:443 <<eof
                                    HEAD / HTTP/1.1
                                    Connection: close
                                    Host: github.com

                                    eof


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






                                    share|improve this answer

























                                      up vote
                                      2
                                      down vote










                                      up vote
                                      2
                                      down vote









                                      You can issue a HEAD request with OpenSSL:



                                      openssl s_client -quiet -connect github.com:443 <<eof
                                      HEAD / HTTP/1.1
                                      Connection: close
                                      Host: github.com

                                      eof


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






                                      share|improve this answer














                                      You can issue a HEAD request with OpenSSL:



                                      openssl s_client -quiet -connect github.com:443 <<eof
                                      HEAD / HTTP/1.1
                                      Connection: close
                                      Host: github.com

                                      eof


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







                                      share|improve this answer














                                      share|improve this answer



                                      share|improve this answer








                                      edited Dec 3 at 18:00

























                                      answered Jan 22 at 19:17









                                      Steven Penny

                                      4,1101683133




                                      4,1101683133

















                                          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?



                                          Popular posts from this blog

                                          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                                          Mangá

                                           ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕