• Overview
  • Get Started
product logo
Back button image Back
Back button image
product logo

Firewall openings needed to manage devices with LogMeIn Resolve MDM

This article lists network requirements for managing devices remotely with LogMeIn Resolve MDM.

LogMeIn Resolve MDM services

LogMeIn Resolve MDM services are accessible at the following addresses via HTTPS (port 443):
mdm.gotoresolve.com (online-production-d5cbbrbxc0dqbkcn.z01.azurefd.net)
This is our user interface. It is also used when entering credentials during the enrollment of iOS and macOS devices.
gateway.miradore.com (online-production-d5cbbrbxc0dqbkcn.z01.azurefd.net)
Mobile devices use this address to contact our servers.
ejbca.miradore.com (online-production-d5cbbrbxc0dqbkcn.z01.azurefd.net)
iOS and macOS devices use this address to request certificates during enrollment and certificate renewal.
mdmcontent.miradore.com (online-production-d5cbbrbxc0dqbkcn.z01.azurefd.net)
This is the address of our content delivery network, which optimizes network traffic distribution for better performance.
onlineproduploads.blob.core.windows.net
This is the storage location in Azure where uploaded files are stored for deployment.
mdnotificationservice.azurewebsites.net (Windows and macOS clients)
This is the address from where LogMeIn Resolve MDM sends wake-up requests to managed Windows and macOS devices, for example, when the device is manually synced with LogMeIn Resolve MDM.
gerwconline.blob.core.windows.net (Windows and macOS clients)
This is the address from where the Miradore client is downloaded to Windows and macOS devices during enrollment.
authentication.logmeininc.com
This endpoint must be accessible to be able to sign in to LogMeIn Resolve MDM.
admin.goto.com
You can manage licenses and users in GoTo Admin.
profile.goto.com
This is the GoTo account profile page.

Connections between push notification services and managed devices

All supported device platforms have their own push notification service hosted by Google, Apple, and Microsoft. Push notifications are needed for real-time connection to devices. For example, when you deploy a configuration profile or send a wipe command, the device is prompted by a push notification.
Android
The ports required for Google Firebase Cloud Messaging (FCM) are 5228, 5229, and 5230. For more information about IP addresses and FCM, check Google's ASN of 15169 and  their article about FCM messages.

See Google's documentation about Android Enterprise network requirements.

iOS and macOS
The Apple Push Notification service (APNs) requires that devices be able to connect to TCP ports 5223 and 443 on all IP addresses within the 17.0.0.0/8 block. For more information, see Apple's article. To use Apple products on enterprise networks, see this article from Apple.
Windows
For Windows, configure your firewall to permit network traffic on port 443 (HTTPS) to the internet.

Ports and addresses are subject to change.

Article last updated: 22 May, 2025

Need help?

Contact icon Contact support
Manage Cases icon Manage cases
Video icon Watch videos
  • Language selector icon Language selector icon
    • English
    • Français
    • Italiano
    • Deutsch
    • Español
    • Português
    • Nederlands
  • About Us
  • Terms of Service
  • Privacy Policy
  • Trademark
  • Do Not Sell or Share My Personal Info
  • Browse Products
  • Copyright © 2025 GoTo Group, Inc. All rights reserved

Collaboration Products

GoTo Connect

GoTo Meeting

GoTo Webinar

GoTo Training

join.me

Grasshopper

OpenVoice

Remote Solutions Products

GoTo Resolve

Rescue

GoToAssist

Access Products

Pro

Central

GoToMyPC