Ask Me Help Desk

Ask Me Help Desk (https://www.askmehelpdesk.com/forum.php)
-   Networking (https://www.askmehelpdesk.com/networking/)
-   -   IP of https secure sites (https://www.askmehelpdesk.com/networking/ip-https-secure-sites-248848.html)

  • Aug 14, 2008, 09:55 AM
    snowalps
    IP of https secure sites
    What is the ip of secure http sites? i.e https sites? It must be definitely different from their non secure conterpart. For e.g meebo - online web IM for AIM, MSN, Yahoo, Google Talk messengers and https://meebo.com
    How can I find the ip for https://meebo.com??
    I tried pinging but cmd doesn't recognize the "https" part so doesn't return any ip

    Any ideas guys? :D
  • Aug 14, 2008, 10:53 AM
    WallyHelps
    The IP address could be the same. https simply means that the connection is encrypted (or secure).
    There doesn't have to be a unique IP address (although the website could do that).

    FWIW, my ping command does recognize the "https:" part. WinXP Home, SP2

    I hope this clarifies things,
    WallyH
  • Aug 14, 2008, 11:47 AM
    snowalps
    Thanks wally. But my cmd returns "ping req could not find the host" when I try to ping https://meebo.com

    Strange!
  • Aug 14, 2008, 12:05 PM
    jcdill
    Quote:

    Originally Posted by snowalps
    what is the ip of secure http sites? i.e https sites? it must be definitely different from their non secure conterpart. for e.g meebo - online web IM for AIM, MSN, Yahoo, Google Talk messengers and https://meebo.com
    how can i find the ip for https://meebo.com??
    i tried pinging but cmd doesnt recognize the "https" part so doesnt return any ip

    any ideas guys?? :D

    The IP address of a secure site does NOT need to be different from the non-secure site. A single IP address can serve regular web pages on port 80 (standard http) and encrypted web pages on port 443 (secure http aka https).

    You can telnet to a specific address and port, to determine the IP address that answers for that https server. From a command window try:

    Telnet meebo.com:443

    You will have to abort the telnet command to exit.

    Why do you need to know the IP of the https version of a given site?
  • Aug 14, 2008, 01:19 PM
    snowalps
    Thanks jcdill. I agree. I tried it on cmd but it says "could not open connection to the host on port 23" I guess telnet uses default port 23 to open hosts and its not able to open a connection in this case. I then tried telnet meebo.com 443 on cmd and it opened up a blank telnet window which means its through and connected.

    But am still not able to get the ip for it!

    I am experimenting my hosts file which is why I need this ip :-)
  • Aug 14, 2008, 01:56 PM
    jcdill
    Quote:

    Originally Posted by snowalps
    thnx jcdill. i agree. i tried it on cmd but it says "could not open connection to the host on port 23" i guess telnet uses default port 23 to open hosts and its not able to open a connection in this case. i then tried telnet meebo.com 443 on cmd and it opened up a blank telnet window which means its through and connected.

    but am still not able to get the ip for it!

    iam experimenting my hosts file whihc is why i need this ip :-)

    You have to open the command window first. Then type the telnet command. The response message will tell you what IP address it connects to, like this:

    telnet meebo.com 443
    Trying 208.81.191.126...
    Connected to meebo.com.
    Escape character is '^]'.

    (I'm on a Mac, so I put a SPACE between the domain name and the port number. You are on a Windows computer, you need to put a COLON as in meebo.com:443 rather than a space)
  • Aug 14, 2008, 02:04 PM
    snowalps
    Exactly.. I did the same thing before.. and as I said it returned an error saying:

    "connecting to meebo.com:443...could not open connection to host, on port 23: connect failed"
  • Aug 14, 2008, 03:21 PM
    jcdill
    Quote:

    Originally Posted by snowalps
    exactly.. i did the same thing before..and as i said it returned an error saying:

    "connecting to meebo.com:443...could not open connection to host, on port 23: connect failed"

    Your telnet client is not using the port number for some reason! You can't connect on the default telnet port (23) (which is normal, they shouldn't have port 23 open on the server), but it should be able to connect on the specified port (443). Try using a space instead of colon.

    You already have the command window open when you are typing the command, right? You aren't doing this in the Start -> Run dialog, right?
  • Aug 14, 2008, 03:23 PM
    jcdill
    Also see this page for more tips on using telnet including a GUI box where you can enter the port number:
    Windows Telnet

    If you are still having problems, I need to know what version of Windows you have - XP, Vista, NT, etc.
  • Aug 14, 2008, 04:32 PM
    snowalps
    Thanks jcdill.. I'll chk that and get back to you soon..
  • Aug 15, 2008, 04:50 AM
    WallyHelps
    Quote:

    Originally Posted by snowalps
    thnx wally. but my cmd returns "ping req could not find the host" when i try to ping https://meebo.com

    strange!

    FWIW, this is what I get:
    Code :

    C:\>ping http://meebo.com
     
    Pinging http://meebo.com [208.69.36.132] with 32 bytes of data:
     
    Reply from 208.69.36.132: bytes=32 time=16ms TTL=54
    Reply from 208.69.36.132: bytes=32 time=18ms TTL=54
    Reply from 208.69.36.132: bytes=32 time=17ms TTL=54
    Reply from 208.69.36.132: bytes=32 time=17ms TTL=54
     
    Ping statistics for 208.69.36.132:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 16ms, Maximum = 18ms, Average = 17ms
     
    C:\>ping https://meebo.com
     
    Pinging https://meebo.com [208.69.36.132] with 32 bytes of data:
     
    Reply from 208.69.36.132: bytes=32 time=16ms TTL=54
    Reply from 208.69.36.132: bytes=32 time=18ms TTL=54
    Reply from 208.69.36.132: bytes=32 time=18ms TTL=54
    Reply from 208.69.36.132: bytes=32 time=17ms TTL=54
     
    Ping statistics for 208.69.36.132:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 16ms, Maximum = 18ms, Average = 17ms


    I don't know why this doesn't work for you, unless you are running a different OS.

    WallyH
  • Aug 15, 2008, 07:18 AM
    jcdill
    Quote:

    Originally Posted by WallyHelps
    FWIW, this is what I get:
    Code :

    C:\>ping http://meebo.com
     
    Pinging http://meebo.com [208.69.36.132] with 32 bytes of data:
     
    Reply from 208.69.36.132: bytes=32 time=16ms TTL=54
    Reply from 208.69.36.132: bytes=32 time=18ms TTL=54
    Reply from 208.69.36.132: bytes=32 time=17ms TTL=54
    Reply from 208.69.36.132: bytes=32 time=17ms TTL=54
     
    Ping statistics for 208.69.36.132:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 16ms, Maximum = 18ms, Average = 17ms
     
    C:\>ping https://meebo.com
     
    Pinging https://meebo.com [208.69.36.132] with 32 bytes of data:
     
    Reply from 208.69.36.132: bytes=32 time=16ms TTL=54
    Reply from 208.69.36.132: bytes=32 time=18ms TTL=54
    Reply from 208.69.36.132: bytes=32 time=18ms TTL=54
    Reply from 208.69.36.132: bytes=32 time=17ms TTL=54
     
    Ping statistics for 208.69.36.132:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 16ms, Maximum = 18ms, Average = 17ms


    I don't know why this doesn't work for you, unless you are running a different OS.

    WallyH

    It doesn't work, because the second ping you show above isn't reaching the SECURE site for meebo.com. Both pings go to the same IP address, but meebo.com uses a different IP address for their https site than for their http site.

    Ping uses port 7, but http uses port 80, and https uses port 443. This is why you need to use telnet and SPECIFY the port to determine the right IP address for the secure server (on port 443) for a given domain name.
  • Aug 15, 2008, 07:20 AM
    chuckhole
    Keep in mind that your router may be filtering ICMP responses. This means that PING requests will not be completed. TCP/IP is a transport mechanism and the protocols are types of transport that serve different purposes. Some are like a delivery truck (like FTP), a mail truck (like SMTP or POP3), or a newspaper delivery (like NNTP). Each protocol has a different purpose. HTTPS is secured communications using HTTP. They all drive on the same TCP/IP highway, just for different purposes.

    If you want the IP address of a domain name such as meebo.com, go to a command prompt and type NSLOOKUP and hit enter.

    Then type the domain name and hit enter.

    The Name Server Lookup will return the IP address of the domain name or host name that you have requested.

    If you want to know what the mail server(s) name(s) for that domain are, then at the NSLOOKUP prompt, change the lookup type from A records to MX records (mail exchanger) by typing the following:

    SET TYPE=MX and enter

    Then type the domain name again and hit enter. You will then get a list of the MX records assigned to that domain. You can then return to the A record lookup by typing

    SET TYPE=A and enter

    Then type in the host names for the mail servers and it will return the IP address.

    Type EXIT and hit enter to return to the normal command prompt.
  • Aug 15, 2008, 11:59 AM
    jcdill
    Quote:

    Originally Posted by chuckhole
    If you want the IP address of a domain name such as meebo.com, go to a command prompt and type NSLOOKUP and hit enter.

    Please post an example using NSLOOKUP that finds the IP address meebo.com uses for https. I'm very interested to see how you accomplish this with NSLOOKUP.
  • Aug 15, 2008, 12:42 PM
    snowalps
    Okay. Now guys firstly sorry for being a bit late here in replying.. lemme answer jcdill's doubt first.. am not running it in "run dialog".. am doing it in the cmd window.. also if it can help, my OS is win xp sp2.

    Now as for wally, I don't know how you managed to ping for https! Its not working in mine at all.. as I mentioned earlier it throws that error.

    As for nslookup, it surely will give the ip as non authoritative reply but it would not differentiate between the http and https, as jcdill rightly pointed, here comes the difference in ports which is 80 and 443 respectively...
    So guys where are we, I guess back to square one!

    But thanks a bunch jcdill and wally for posting your suggestions... now what can we try next?
  • Aug 15, 2008, 01:15 PM
    jcdill
    Quote:

    Originally Posted by snowalps
    okay. now guys firstly sorry for being a bit late here in replying back..lemme answer jcdill's doubt first..am not running it in "run dialog"..am doin it in the cmd window..also if it can help, my OS is win xp sp2.

    now as for wally, i dont know how you managed to ping for https! its not working in mine at all..as i mentioned earlier it throws that error.

    as for nslookup, it surely will give the ip as non authoritative reply but it would not differentiate between the http and https, as jcdill rightly pointed, here comes the difference in ports which is 80 and 443 respectively...
    so guys where are we, i guess back to square one!

    but thanks a bunch jcdill and wally for posting your suggestions...now wat can we try next?? ?

    Did you try the link I posted up above, showing how to start the windows Telnet GUI? I'm not 100% sure it works in XP SP2 but I believe it does. From the command prompt just type: telnet and hit enter. This should bring up the telnet GUI and then you can select the port.
  • Aug 15, 2008, 01:25 PM
    snowalps
    Am afraid the gui is not available in xp sp2,. unless if I have to install it separately. I could try something on the command prompt version of telnet though.. i.e the window you get when you type telnet in cmd...
  • Aug 15, 2008, 01:52 PM
    jcdill
    Quote:

    Originally Posted by snowalps
    am afraid the gui is not available in xp sp2,..unless if i have to install it separately. i could try something on the command prompt version of telnet though..i.e the window you get when you type telnet in cmd...

    Try this tutorial on using command line telnet on Windows:
    Tutorials - Servers > Telnet as a Diagnostic Aid
  • Aug 15, 2008, 02:03 PM
    snowalps
    Okay.. I'll try that and get back!
  • Aug 15, 2008, 07:14 PM
    WallyHelps
    Quote:

    Originally Posted by chuckhole
    Keep in mind that your router may be filtering ICMP responses. This means that PING requests will not be completed. TCP/IP is a transport mechanism and the protocols are types of transport that serve different purposes. Some are like a delivery truck (like FTP), a mail truck (like SMTP or POP3), or a newspaper delivery (like NNTP). Each protocol has a different purpose. HTTPS is secured communications using HTTP. They all drive on the same TCP/IP highway, just for different purposes.

    If you want the IP address of a domain name such as meebo.com, go to a command prompt and type NSLOOKUP and hit enter.

    Then type the domain name and hit enter.

    The Name Server Lookup will return the IP address of the domain name or host name that you have requested.

    If you want to know what the mail server(s) name(s) for that domain are, then at the NSLOOKUP prompt, change the lookup type from A records to MX records (mail exchanger) by typing the following:

    SET TYPE=MX and enter

    Then type the domain name again and hit enter. You will then get a list of the MX records assigned to that domain. You can then return to the A record lookup by typing

    SET TYPE=A and enter

    Then type in the host names for the mail servers and it will return the IP address.

    Type EXIT and hit enter to return to the normal command prompt.

    Wow! I'm outclassed here. I'll stop answering, but this sure is interesting stuff!
    :D wh

  • All times are GMT -7. The time now is 07:23 PM.