Mimecast Data Centers and URLs - North American

Mimecast operates in multiple regions, with each having its own set of IP addresses, network ranges, and URLs for Mimecast applications, Mimecast Services, and Mimecast APIs. In order to ensure users are directed to the correct regional data centers, it is important your account uses the correct details.

Note:

Your region may not be where you are physically located. It is where your data is located. For example, a company with offices in Europe may host their data in North America.

To prevent disruption to your service, it's important to ensure that:

• You allow connections to the appropriate ports from the entire Mimecast IP Ranges for your region.
• They are mapped through to the correct destination on your network.

When a user enters their email address into the Administration Console or an API client (Mimecast for Outlook, Mimecast for Mac, Mimecast Mobile), the global resource is used to determine where the user's parent Mimecast account is hosted and provides a 302 redirect to the correct location. For redundancy, these endpoints are available in all Mimecast data centers.

Consequently, it's possible that you may observe outbound HTTPS traffic from your network to an IP address outside of your Mimecast region. To prevent disruption to your service, ensure outbound HTTPS connections are allowed to these locations. These requests are for authentication only, no email is transmitted using this method.

The sections below detail the Mimecast service network ranges. These details can be used to ensure that the organization's infrastructure accepts connections to and from the Mimecast service. If you have issues logging onto a URL, ensure you are using one of the supported browsers before contacting Mimecast Support. Read the Mimecast Browser Support Matrix page for further details.

Considerations

• You must ensure that inbound connections are allowed access to the ports for the networks listed, and that they are mapped to the correct destination on your network.
• ***The Mimecast Secure Messaging Portal URL should only be used by Mimecast customers. Non-Mimecast customers can access the portal by clicking the link in the notification message.

Global Application Resources

Global Application URL

Application	URL
Administration Console	https://login.mimecast.com/u/login?gta=administration
Mimecast Personal Portal	https://webmail.mimecast.com/m/portal/login/#/login
Mimecast API	https://api.mimecast.com/
Service Monitor	https://portal.mimecast.com/monitor/Account/Login

Protocol Connection Ports

The following list shows the most common connection types and the general ports used for each protocol. Also included are the standard connection ports for Mimecast Applications:

Protocol	Default Port	Usage
Simple Mail Transfer Protocol (SMTP)	25	Send Connectors, SMTP Journaling, user application SMTP Services.
Post Office Protocol (POP3)	110	POP Journaling, user application POP Services.
Post Office Protocol Secure (POP3S)	995
Lightweight Directory Access Protocol (LDAP)	389	Directory Synchronization
Lightweight Directory Access Protocol Secure (LDAPS)	636
Hyper Text Transfer Protocol (HTTP)	80	Downloading Strip and Link attachments, Mimecast Synchronization Engine (MSE) with Office 365 hybrid environments. Mimecast for Outlook also authenticates using this port.
Hyper Text Transfer Protocol (HTTPS)	443	Access to the Administration Console, Mimecast Personal Portal, Mimecast Mobile, Mimecast for Outlook and Mimecast Synchronization Engine.

Mimecast Website

To ensure that your users can always log in to the Mimecast website, it is recommended to permit traffic to the Mimecast website IP ranges:

Location	IP Address	CIDR	Netmask
Data Center 1	146.101.202.134	/32	255.255.255.255
	146.101.202.135	/32	255.255.255.255
Data Center 2	81.145.134.178	/32	255.255.255.255
	81.145.134.173	/32	255.255.255.255

United States of America