Overview
IP whitelisting (IP allowlisting) is a security practice that allows organizations to restrict access to their networks, systems, and resources to predefined IP addresses, blocking all others. This cybersecurity mechanism helps businesses prevent unauthorized access and protect sensitive data. Businesses can use IP whitelisting to control access to their tools, software, applications, websites, and critical resources. This document outlines the relevance of IP whitelisting and how marketers and developers can use it effectively.Key Advantages of IP Whitelisting
The following are the advantages of IP whitelisting:- Enhanced security: By permitting connections only from known, trusted IP addresses, whitelisting effectively blocks potential threats from unknown sources, significantly reducing the risk of unauthorized access and malware attacks. Overall, it adds an extra layer of security to protect sensitive data.
- Proactive defense: Unlike blacklisting, which relies on identifying and blocking known threats, whitelisting takes a proactive approach by allowing only approved access, making it more effective against emerging threats.
- Reduced false positives: Because whitelisting blocks connections only from unapproved sources, the chances of accidentally blocking legitimate users are minimized, reducing frustration and disruption.
- Improved network visibility: By actively managing the list of allowed IP addresses, organizations gain better insight into who is accessing the network and can easily identify suspicious activity.
Whitelist MoEngage IPs
MoEngage sends/receives data to/from the servers of customers or partners. With IP whitelisting, you can verify that requests are actually coming from MoEngage, adding an additional layer of security. MoEngage is a multi-tenant SaaS vendor, so our services change IPs frequently for scale and security. We may need to send data from a different server when circumstances demand it to ensure our services are operational and customers are not impacted. MoEngage may use one or all of the IPs listed in this document while sending/receiving data to/from the servers of customers or partners.Campaign Sending
MoEngage uses dynamic IPs. But if you need MoEngage to access your service via static IPs, you must whitelist MoEngage IPs on your side. To enable static IPs for a messaging channel, contact your Customer Success Manager (CSM) or the Support team to request enablement of Send via Static IPs for<Messaging Channel>. After static IPs for a messaging channel are enabled, you can whitelist the relevant MoEngage IPs based on the data center where your workspace is located. For more information on MoEngage Data Centers, refer here.
Here are the IPs that you can whitelist to ensure that only allowed IPs send messages:
| Channels or Campaigns | Data Center | MoEngage IPs That Need Whitelisting |
|---|---|---|
| Connector Campaigns | DC-01 |
|
| Connector Campaigns | DC-02 | 18.195.110.23 |
| Connector Campaigns | DC-03 | 3.6.251.95 |
| Connector Campaigns | DC-04 | 18.217.73.1 |
| Connector Campaigns | DC-05 | NA |
| Connector Campaigns | DC-06 |
|
SMS Campaigns
| DC-01 |
|
| SMS Campaigns | DC-02 | 18.195.110.23 |
| SMS Campaigns | DC-03 | 3.6.251.95 |
| SMS Campaigns | DC-04 | 18.217.73.1 |
| SMS Campaigns | DC-05 | NA |
| SMS Campaigns | DC-06 |
|
| WhatsApp Campaigns | DC-01 |
|
| WhatsApp Campaigns | DC-02 | 18.195.110.23 |
| WhatsApp Campaigns | DC-03 | 3.6.251.95 |
| WhatsApp Campaigns | DC-04 | 18.217.73.1 |
| WhatsApp Campaigns | DC-05 | NA |
| WhatsApp Campaigns | DC-06 |
|
| Email Campaigns (sent via Custom API/Custom SMTP Connector/Private ESP or using PII Fetch API/Content API) | DC-01 | 52.6.248.125 |
| Email Campaigns | DC-02 | 18.195.110.23 |
| Email Campaigns | DC-03 | 3.6.251.95 |
| Email Campaigns | DC-04 | NA |
| Email Campaigns | DC-05 | NA |
| Email Campaigns | DC-06 |
|
| Push Campaigns | DC-01 |
|
| Push Campaigns | DC-02 |
|
| Push Campaigns | DC-03 |
|
| Push Campaigns | DC-04 |
|
| Push Campaigns | DC-05 | NA |
| Push Campaigns | DC-06 |
|
| Content API or Fetch PII Token | DC-01 | PII and Content API use the same IPs as that of the channel. So, if you plan to use one or more channels in the campaign, whitelist all the campaign channel IPs mentioned above. |
| Content API or Fetch PII Token | DC-02 | |
| Content API or Fetch PII Token | DC-03 | |
| Content API or Fetch PII Token | DC-04 | |
| Content API or Fetch PII Token | DC-05 | |
| Content API or Fetch PII Token | DC-06 |
Data Transfer
Here are the IPs that you can whitelist for our Data Imports and Export services to ensure that only whitelisted IPs are reading or writing data from/to your data services:| Data Transfer | Data Center | MoEngage IPs That Need Whitelisting |
|---|---|---|
| Data Imports | DC-01 |
|
| Data Imports | DC-02 |
|
| Data Imports | DC-03 |
|
| Data Imports | DC-04 |
|
| Data Imports | DC-05 | 18.143.35.151 |
| Data Imports | DC-06 |
|
| Data Warehouse Exports For example, SFTP, Snowflake, Databricks, and so on. | DC-01 |
|
| Data Warehouse Exports | DC-02 | 18.195.110.23 |
| Data Warehouse Exports | DC-03 | 3.6.251.95 |
| Data Warehouse Exports | DC-04 |
|
| Data Warehouse Exports | DC-05 | 18.143.35.151 |
| Data Warehouse Exports | DC-06 | NA |
| Streams/Partner Exports For example, mParticle, Segment, and so on. | DC-01 | 52.6.248.125 |
| Streams/Partner Exports | DC-02 | 18.195.110.23 |
| Streams/Partner Exports | DC-03 | 3.6.251.95 |
| Streams/Partner Exports | DC-04 | 18.217.73.1 |
| Streams/Partner Exports | DC-05 | 18.143.35.151 |
| Streams/Partner Exports | DC-06 | 43.218.197.196 |
Audience Transfer
Here are the IPs that you can whitelist for Outbound Segment sync to ensure that these MoEngage IPs are allowed to call your/partner’s audience sync APIs:| Audience Transfer | Data Center | MoEngage IPs That Need Whitelisting |
|---|---|---|
| Outbound Segment Sync | DC-01 | 52.6.248.125 |
| Outbound Segment Sync | DC-02 | NA |
| Outbound Segment Sync | DC-03 | 3.6.251.95 |
| Outbound Segment Sync | DC-04 | NA |
| Outbound Segment Sync | DC-05 | NA |
| Outbound Segment Sync | DC-06 | NA |
| File Segment API | DC-01 | 184.72.243.80 |
| File Segment API | DC-02 | 18.195.110.23 |
| File Segment API | DC-03 | 3.6.251.95 |
| File Segment API | DC-04 | 3.139.47.208 |
| File Segment API | DC-05 | 18.143.35.151 |
| File Segment API | DC-06 | 43.218.197.196 |
Catalog and Feeds
You can whitelist the following MoEngage IPs to allow MoEngage to import their catalog feed via SFTP-based ingestion:| Data Center | MoEngage IPs That Need Whitelisting |
|---|---|
| DC-01 | 52.1.205.204 |
| DC-02 |
|
| DC-03 | 3.6.251.95 |
| DC-04 | 18.217.73.1 |
| DC-05 | NA |
| DC-06 | NA |
Whitelist Your IPs
IPs from your or your partner’s networks that can access MoEngage services:| Type | Description | Steps |
|---|---|---|
| Dashboard Access | Allows you to whitelist your or your partner network IPs that can access the MoEngage dashboard | You can enable the Firewall on the MoEngage dashboard. For more information, refer to Firewall. |
| Open Analytics | Allows you to whitelist your or your partner network IPs that can access the MoEngage Open Analytics. | Please contact your MoEngage Customer Success Manager (CSM) or the Support team with the subject Whitelist IPs for Open Analytics Access, and share the list of IPs to be whitelisted in the ticket. |
| MoEngage APIs | NA | NA |
Conclusion
IP whitelisting is important for maintaining data security when using MoEngage services. Contact the MoEngage Support team for additional assistance or clarification on IP whitelisting procedures.Frequently Asked Questions
Does MoEngage provide IP whitelisting for MoEngage APIs? Can a brand restrict which IPs can access MoEngage APIs on the API key level? MoEngage doesn’t currently provide this capability. To submit the request:- Log in to your MoEngage dashboard.
- In the upper-right corner, click Need help and then click Submit product idea.