What are the network specifications for the usage of remote assistance?

Allow listing and Firewall Configuration for LogMeIn Products

If you or your company uses a firewall allowlist to restrict network access to only specific websites or software, then you can use the information below to ensure that your service can connect.

Ports

LogMeIn products are configured to work with the following ports:

PortPurpose
Outbound TCP 443Required, used by all products
Outbound TCP 80Recommended, used for in-session communication
UDP 8200Recommended, used for integrated Voice over IP (VoIP) and in-session communication
UDP 1853Recommended, used for integrated webcam video support
TCP 1720TCP 3000-4000UDP 3000-4000Used for InRoom Link video conference systemsCan be closed when not using InRoom LinkAll GoToMeeting Telepresence Gateway IPs are listed below
Inbound connectionsNot required

Domains

For most firewall or proxy systems, we recommend specifying an allowlist of DNS names for LogMeIn product services so that outbound connections can be made. The list of LogMeIn product domains currently includes (but is not limited to) the lists below.

Universally Required Allowlisting

DomainDescription/Purpose
api.filepicker.ioThird-party file-hosting serviceThis will soon change to *.filestackapi.com.
*.cdngetgo.comCDN used by multiple LogMeIn products
*.clientstream.launchdarkly.comThird-party feature testing service
*.cloudfront.netThird-party CDN
*.expertcity.comCorporate domain used by multiple LogMeIn products
*.filestackapi.comThird-party file-hosting service(NEW! FilePicker has changed their name)
*.getgo.comProduct domain used by multiple LogMeIn products
*.getgocdn.comCDN used by multiple LogMeIn products
*.getgoservices.comProduct domain used by multiple LogMeIn products
*.getgoservices.netProduct domain used by multiple LogMeIn products
*.goto-rtc.comReal-time communication service used by multiple products
*.launchdarkly.comThird-party feature testing service
*.logmein.comCorporate domain used by multiple LogMeIn products
*.logmeininc.comCorporate domain used by multiple LogMeIn products
*.logmein.euCorporate domain used by multiple LogMeIn products
*.raas.ioReal-time communication service used by multiple LogMeIn products
*accounts.logme.inCorporate domain used by multiple LogMeIn products
*.internap.netPowers updates to multiple LogMeIn products
*.internapcdn.netPowers updates to multiple LogMeIn products

Rescue

Rescue Domains
*.LogMeIn123.com
*.123rescue.com
*.support.me
*.logmeinrescue.com
*.logmeinrescue.eu
*.logmeinrescue-enterprise.com (Powers account-specific Rescue features, not required for standard accounts)
*.logmein-gateway.com

Rescue Lens

Rescue Lens Domains
*.logmeinrescue.com
*.logmeinrescue-enterprise.com (only required for Enterprise accounts)

LogMeIn Pro & Central

LogMeIn Pro/Central DomainsFeature Supported
*.logmeinusercontentFor files stored and shared using the LogMeIn Pro Files feature
*.browse.logmeinusercontent.comFor files stored and shared using the LogMeIn Pro Files feature
lmi-antivirus-live.azureedge.netFor LogMeIn Central – Antivirus
lmi-appupdates-live.azureedge.netFor LogMeIn Central – Application updates

Important considerations for allowlisting by IP Ranges

It is recommended to use wildcard rules whenever possible while allowlisting or blocking any LogMeIn services on your network as sub-domains of the domains listed above are included. Also, the client-to-host connection uses peer-to-peer connections, encrypted within a 256-bit AES tunnel.

Use of IP ranges instead of domain names for the firewall configuration is discouraged unless absolutely necessary because our IP ranges and those of our provider networks need to be periodically audited and modified, creating additional maintenance for your network. These changes are necessary to continue to provide the maximum performance for our LogMeIn products. Maintenance and failover events within our infrastructure may cause you to connect to servers within any of the ranges.

If your firewall includes a content or application data scanning filter, this may cause a block or latency, which would be indicated in the log files for the filter. To address this problem, verify that the domains or IP ranges will not be scanned or filtered by specifying exception domains or IP ranges. If your security policy requires you to specify explicit domain or IP ranges, then configure your firewall exceptions for outbound TCP ports 8200, 443, and 80 as well as UDP ports 8200 and 1853 for the LogMeIn domains or IP ranges, including those of our third-party provider networks.

LogMeIn server / Data Center IP addresses for use in firewall configurations

Equivalent specifications in 3 common formats

Assigned Range by BlockNumeric IP Address RangeNetmask NotationCIDR Notation
Block 1216.115.208.0 – 216.115.223.255216.115.208.0 255.255.240.0216.115.208.0/20
Block 2216.219.112.0 – 216.219.127.255216.219.112.0 255.255.240.0216.219.112.0/20
Block 367.217.64.0 – 67.217.95.25567.217.64.0 255.255.224.067.217.64.0/19
Block 4173.199.0.0 – 173.199.63.255173.199.0.0 255.255.192.0173.199.0.0/18
Block 5206.183.100.0 – 206.183.103.255206.183.100.0 255.255.252.0206.183.100.0/22
Block 668.64.0.0 – 68.64.31.25568.64.0.0 255.255.224.068.64.0.0/19
Block 723.239.224.0 – 12.239.255.25523.239.224.0 255.255.224.023.239.224.0/19
Block 8202.173.24.0 – 202.173.31.255202.173.24.0 255.255.248.0202.173.24.0/21
Block 978.108.112.0 – 78.108.127.25578.108.112.0 255.255.240.078.108.112.0/20
Block 10185.36.20.0 – 185.36.23.255185.36.20.0 255.255.252.0185.36.20.0/22
Block 11188.66.40.0 – 188.66.47.255188.66.40.0 255.255.248.0188.66.40.0/21
Block 1245.12.196.0 – 45.12.199.25545.12.196.0 255.255.252.045.12.196.0/22
Block 13162.250.60.0 – 162.250.63.255162.250.60.0 255.255.252.0162.250.60.0/22
Block 14199.36.248.0 – 199.36.251.255199.36.248.0 255.255.252.0199.36.248.0/22
Block 15199.87.120.0 – 199.87.123.255199.87.120.0 255.255.252.0199.87.120.0/22
Block 1666.151.158.0 – 66.151.158.25566.151.158.0 255.255.255.066.151.158.0/24
Block 1766.151.150.160 – 66.151.150.19166.151.150.160 255.255.255.22466.151.150.160/27
Block 1864.74.80.0 – 64.74.80.25564.74.80.0 255.255.255.064.74.80.0/24
Block 19103.15.16.0 – 103.15.19.255103.15.16.0 255.255.252.0103.15.16.0/22
Block 2064.74.17.0 – 64.74.17.25564.74.17.0 255.255.255.064.74.17.0/24
Block 2164.74.18.0 – 64.74.19.25564.74.18.0 255.255.254.064.74.18.0/23
Block 2264.74.103.0 – 64.74.103.25564.74.103.0 255.255.255.064.74.103.0/24
Block 2364.94.18.0 – 64.94.18.25564.94.18.0 255.255.255.064.94.18.0/24
Block 2464.94.46.0 – 64.94.47.25564.94.46.0 255.255.254.064.94.46.0/23
Block 2564.95.128.0 – 64.95.129.25564.95.128.0 255.255.254.064.95.128.0/23
Block 2666.150.108.0 – 66.150.108.25566.150.108.0 255.255.255.066.150.108.0/24
Block 2769.25.20.0 – 69.25.21.25569.25.20.0 255.255.254.069.25.20.0/23
Block 2869.25.247.0 – 69.25.247.25569.25.247.0 255.255.255.069.25.247.0/24
Block 2995.172.70.0 – 95.172.70.25595.172.70.0 255.255.255.095.172.70.0/24
Block 30111.221.57.0 – 111.221.57.255111.221.57.0 255.255.255.0111.221.57.0/24

IPv6 addresses space

Assigned by BlockClassless Inter-Domain Routing (CIDR) format
Block 12620:0:c70::/48
Block 22a04:6660::/30

Data Centers

We scale our services into third-party cloud and carrier networks for improved performance. To ensure continuous up-time, we also maintain data centers in the following regions:

  • U.S.: Nevada, Georgia, Virginia
  • Global: Netherlands, Germany, India, China
  • Global Public Cloud (including, but not limited to): California, Oregon, Virginia, Singapore, Australia, Japan
  • Content Delivery Public Cloud (including, but not limited to): California, Washington, Texas, Indiana, Missouri, New Jersey, Brazil, United Kingdom, Amsterdam, Germany, France, Italy, Hong Kong, Japan, Singapore

Third-party provider IP ranges

IP ranges for the content delivery network (CDN)

IP ranges for other services (audio, video and screen sharing)

IP ranges for Microsoft Azure

IP ranges for Cloudflare (specific to GoToMyPC)

Was this article helpful?

Yes No

Related Articles