What are the IP addresses of Splashtop servers?

Follow

In some network environments, firewalls may be blocking the communication with Splashtop servers and thereby preventing Splashtop from working properly.

Testing Network Accessibility

You can determine whether this is the case by running the Splashtop network check tool from within those network environments. Just browse to www.splashtop.com/check using a device that's on the network you want to test.

Allowing Communication with Splashtop Servers

If communication is blocked, please enable your firewalls to allow communication with these domains:

  • *.api.splashtop.com (* represents wildcard)
  • *.relay.splashtop.com (* represents wildcard)

There are numerous Splashtop servers across several regions, but they are all covered under the above wildcard domains. This is the easiest way to allow access through firewalls.

IP Addresses of Splashtop Servers

Splashtop servers reside in datacenters hosted by Amazon. The servers' IP addresses are dynamically allocated and change over time. Therefore, it is not really practical to configure your firewall exceptions using IP addresses. The list of IP addresses is long, and they may change from time-to-time. The best way is to configure your firewall exceptions using the wildcard domains above.

If you do need the IP addresses of the Splashtop API servers, you can use the following commands to look up the current IP addresses:

  • nslookup ca-st2.api.splashtop.com
  • nslookup oregon-st2.api.splashtop.com
  • nslookup ca-st2-relay.api.splashtop.com
  • nslookup oregon-st2-relay.api.splashtop.com
  • nslookup cn-st2-relay.api.splashtop.com

If you need the IP addresses of the Splashtop relay servers, please contact our support team.

Have more questions? Submit a request

Comments

  • Avatar
    Bwe

    I am blocking traffic to computers by using Acrylic DNS Proxy. I am trying various IPs and wildcard combinations of api.splashtop.com to allow communication with Splashtop servers.... thusfar - no success.

    Any Ideas?

  • Avatar
    Support

    @Bwe,

    Can you send us a screenshot of what you see when you run the test tool www.splashtop.com/check?

    Be sure to access that URL from a computer behind your DNS proxy where you're seeing problems.

    Thanks,
    Phil

  • Avatar
    Robdalton

    Same here... even allowing all http and https to *.splashtop.com does not allow the On Demand sessions to connect. Are there any other domains required?

    Any thoughts?

  • Avatar
    Support

    @Robdalton,

    Is it the SOS agent didn't show the 9 digit access code, or there was a 9-digit access code but you can't connect to the remote computer using SOS?

    Can you also send us screenshots of the test result on both local and remote computer after visiting our check page www.splashtop.com/check?

    Thanks,
    Vans

  • Avatar
    Bwe

    Hello again!
    After checking, via the link you indicated, all connections failed. I pinged the 2 API server urls, got the IPs and added them to the allowed IPs in the AcrylicHosts file. After this I could connect with the API servers.

    It still fails with the Relay Server, and the 2 Chrome connection Servers.

    The Acrylic uses a very similar syntax as a standard hosts file.

    So far my exceptions to the total block out are:

    54.52.243.147 *.splashtop.com
    52.52.243.147 api.splashtop.com
    34.209.224.216 st2.api.spalshtop.com
    52.26.17.8 st2-relay.api.splashtop.com

  • Avatar
    Support

    @Bwe,

    If you add *.api.splashtop.com and *.relay.splashtop.com to the exceptions, will it work? If not, what is the result of the checking page?

    Thanks,
    Vans

  • Avatar
    Azam Khalid

    I'm not sure this is entirely helpful. We all know that IP addresses are subject to change. Especially so when servers are hosted in cloud environments. Furthermore, Windows firewall doesn't even allow for URL filtering. Apps like SplashtopSOS seem to do a DNS query and look for a URL to connect to. This means we would have to specify a whole list of IP addressed on firewalls and then probably repeat the process in a few months when those IPs change.

    I wanted to control outbound connections from my machine by doing a default Block approach and Allow by exception. The only way I was able to get firewalled Splashtop outbound connections to work was to allow ANY application to send port 443 & 80 traffic. I went and tried the route of adding SplashtopSOS to the exception list but it just didn't work. I added nearly every Splashtop related .exe file I could see getting launched in the task amanger but still to no avail. I turned off my firewall and used netstat to note down the PID and file path of every single Splashtop process that got launched and added them to the exception list. This still did not work. I then found that SplashtopSOS actually unpacks files to a temp directory and that the location within the temp directory structure will also change. There also seems to be multiple instances of the SRManagerSOS.exe getting launched which Windows firewall isn't able to handle. Given this, and that Windows firewall does not do URL filtering, it seems nearly impossible to get Splashtop to play well in a restricted firewall environment. It would be nice to see if Splashtop staff themselves have tested SOS or any of their other apps in a restricted firewall environment and got it to work. If so, I would greatly appreciate if they can publish their findings to provide guidance.