We need not share the NAT IPs with the customer unless there is any outgoing request from Freshservice to the customer network. A few examples are listed below:
Custom Mailbox(where FS sends an outgoing request to the customer's Exchange server)
Webhooks(Webhooks from FS to other external services)
NGRok for Jira(As the request would be triggered from FS to the customer’s network)
Please find the list of NAT IPs:
Application Load Balancer(ALB) IPs
The below IP addresses must be shared in case customers have Firewall restrictions within their org. These IPs are Dynamic, however we keep switching between the list of IP addresses mentioned against each data center. We can provide these IP addresses in below cases:
If they have firewalls in their network and need FS IP addresses to whitelist so they can access without issues
To allow third party sites to communicate with FS through Webhooks
Please find the list of ALB IPs.
The IP addresses for each data center would be within one of the mentioned IP addresses above and would be dynamic in nature. Please inform the customers to whitelist all the IP addresses for their data center.
Elastic Load Balancer (ELB) IPs
We provide the ELB IPs for the same cases as mentioned for ALB IPs, the only difference here is that these IPs have to be provided if they have a vanity URL(CNAME) configured in their Freshservice account. When customers try accessing the CNAME, their request would be routed through the ELB IPs and then redirected to the corresponding ALB IPs.
These IPs are dynamic, the customer can either ping or dig their vanity URL and whitelist the IP which is displayed in the response. Alternatively, they can also write a script to ping the region/service and get the current IP address being used as explained in the link below:https://aws.amazon.com/blogs/aws/aws-ip-ranges-json
We provide the below IP addresses for customers who are using their own IMAP/SMTP mail servers within Freshservice.
Please note that the above IP addresses have to be whitelisted if their mail server has any firewalls. NAT IPs have to be provided to allow FS to authenticate the mailboxes and the above IPs for the proper functioning of these mailboxes within FS.
Please find below IP addresses that can be provided to customers who are sending mails through Sendgrid.
SPF record which is to be created by customers using Sendgrid: email.freshservice.com
Freshemail SMTP Service
Customers who are using our own mail server (freshemail) have to whitelist the below IP addresses to receive emails without issues.
Orchestrator & Web Request IPs
Below is the list of IP addresses to be whitelisted for be Freshorchestrator for specific regions:
Below is the list of domains to be whitelisted for ONPREM-OSR (Freshorchestrator) for specific regions:
If a Marketplace App doesn't work as expected in a customer's company/private network alone, the customer may have to whitelist the Marketplace IPs for their network.
For customers asking for FreshID email service IP address that needs to be whitelisted to receive password reset emails etc, please find below IP addresses that we have tested:
Other Points to Note
If we observe errors in the network log related to Freshchat, IRIS notifications, and Freshconnect we would have to check with developers for the respective IP addresses and have it shared with the customer.
New WAF IPs for India Pod (March 2023)
These IPs are in addition to the IPs addressed above:
Additional IP Addresses: