Allowlisting and LogMeIn Resolve
We suggest you allow the GoTo URLs listed below to ensure that GoTo services are able to connect.
Important: For information about SaaS products offered by GetGo, Inc., a subsidiary of GoTo, Inc., visit this page.
Required Domains and Ports
| Domain | Port | Purpose |
|---|---|---|
| *.console.gotoresolve.com | TCP/443 |
Iot Access
Various Resolve services are hosted under this domain, in AWS
Note: Including but not limited to:
|
| *.gotoresolve.com | UDP/15000 TCP/443 |
Various Resolve services are hosted under this domain, in AWS and Azure Turn servers for media session fallback, WebRTC traffic and log collectionWebRTC server farm |
| *.services.gotoresolve.com | TCP/443 | Various Resolve services are hosted under this domain, in Azure
Note: Including but not limited to:
On client side:RMM client applications are downloaded from there |
| authentication.logmeininc.com | TCP/443 | Login page
Note: See the Optional Domains and Ports if you want to display avatars as well.
|
| devices-iot.console.gotoresolve.com | TCP/8883 | LogMeIn Resolve Android Unattended Application accessing various Resolve services
Note: Windows 7
|
helpdesk.me *.helpdesk.me |
TCP/443 | Various Resolve services are hosted under this domain |
| logmein.com | TCP/443 | LogMeIn’s main site |
| .mdm.gotoresolve.com | TCP/443 | MDM integration |
turn-media.gotoresolve.com |
UDP/3489 TCP/443 |
Turn servers for media session fallback, WebRTC traffic
Note: See Turn Server IP List
|
| turn.gotoresolve.com | UDP/3489 |
File transfer |
Optional Domains and Ports
| Domain | IP Range | Port | Purpose |
|---|---|---|---|
| *.segment.com | TCP/443 | ||
| avatars.servers.getgo.com | TCP/443 | Display avatars on the login page | |
| *.pendo.io | TCP/443 | ||
| *.sentry-cdn.com | TCP/443 | ||
| *.sentry.io | TCP/443 | ||
| *.pusherapp.com | TCP/443 | used by session cards (RC, terminal etc...) | |
| *.pusher.com | TCP/443 | used by session cards (RC, terminal etc...) | |
| dc.applicationinsights.azure.com | TCP/443 | Allows endpoint protection to receive data related to available Windows updates. Used for telemetry purposes. | |
| dc.applicationinsights.microsoft.com | TCP/443 | Allows endpoint protection to receive data related to available Windows updates. Used for telemetry purposes. | |
| dc.services.visualstudio.com | TCP/443 | Allows endpoint protection to receive data related to available Windows updates. Used for telemetry purposes. | |
| *.in.applicationinsights.azure.com | TCP/443 | Allows endpoint protection to receive data related to available Windows updates. Used for telemetry purposes. | |
| live.applicationinsights.azure.com | 20.49.111.32- 20.49.111.60 | TCP/443 |
Allows endpoint protection to receive data related to available Windows updates. Used for telemetry purposes. |
| rt.applicationinsights.microsoft.com | 13.73.253.112- 13.73.253.140 | TCP/443 |
Allows endpoint protection to receive data related to available Windows updates. Used for telemetry purposes. |
| rt.services.visualstudio.com | TCP/443 | Allows endpoint protection to receive data related to available Windows updates. Used for telemetry purposes. | |
| {region}.livediagnostics.monitor.azure.com | TCP/443 | Allows endpoint protection to receive data related to available Windows updates. Used for telemetry purposes. |
For the WebRTC component there is a fallback mechanism where it is possible to allowlist dedicated IP addresses.
Turn server IP list
| Virginia | Oregon | London | Frankfurt | Singapore | Mumbai |
|---|---|---|---|---|---|
| 3.228.209.196 | 44.229.217.227 | 3.10.62.125 | 3.72.25.221 | 175.41.141.140 | 3.108.206.123 |
| 3.230.232.226 | 44.232.77.24 | 3.11.130.196 | 3.72.174.252 | 18.140.137.139 | 13.232.7.181 |
| 18.206.68.238 | 52.13.255.230 | 13.42.92.190 | 3.73.150.182 | 54.255.48.58 | 43.205.76.185 |
| 34.232.43.4 | 52.35.84.247 | 18.134.118.217 | 3.122.32.27 | 54.255.100.96 | 65.0.112.174 |
| 35.153.21.190 | 54.185.112.207 | 18.158.121.211 | |||
| 50.17.158.207 | 54.189.249.52 | 18.158.218.2 | |||
| 52.0.88.112 | 35.156.13.147 | ||||
| 52.54.244.43 | 52.28.148.85 | ||||
| 54.146.34.187 | |||||
| 54.204.126.154 | |||||
| 54.227.77.39 | |||||
| 107.21.27.28 |
For networks explicitly filtering outbound destination ports and protocols, the following ports are used on
LogMeIn Resolve side:
- 443 TCP traffic for LogMeIn Resolve support sessions
- 3489 UDP traffic for LogMeIn Resolve file transfer sessions and as media session fallback
- 15000 UDP traffic for LogMeIn Resolve WebRTC server farm usage
Data Centers
We scale our services with third-party cloud and carrier networks for improved performance. We leverage the following regions from our cloud providers:
- AWS: Virginia
- AWS: Oregon
- AWS: Ohio (failover region only)
- AWS: Frankfurt
- AWS: Dublin (for EU Data residency only)
- AWS: London
- AWS: Singapore
- AWS: Mumbai
- Azure: Virginia
- Azure: Iowa
- Azure: Netherlands
Content Delivery Network: Edge locations are used worldwide for best performance.
Email Domains
For email invitations and correspondences from us and the LogMeIn software, we recommend allowing the following email domains through your email's spam and allowlist filters.
- @goto.com
- @m.logmein.com
- @t.logmein.com
- @purchase.goto.com
- noreply@logmein.com
Article last updated: 20 March, 2025