function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion

SF IP Range for Outbound Messaging via a Sandbox

According to the SF API manual (version 19), the IP ranges SF uses for outbound messaging are as follows:


"Lock down the client application’s listener to accept requests only from the IP range. While this guarantees the message came from, it does not guarantee that another customer is not pointing to your endpoint and sending messages. The IP ranges are:

  • to
  • to"

We tried this range but messages just bounced off our firewall.  When we temporarily expanded the range, we found an incoming message on - outside the range specified above.  We are working with a sandbox, not production.  It would appear that the IP ranges in the manual are either incorrect or do they do not also apply to a sandbox.  If so, can you provide the correct IP range so we can button up our firewall appropriately?




- Cris


Hey Cris, you seem to have an out of date range.


From the help doco: East Coast Data Center (set one) East Coast Data Center (set two) West Coast Data Center (set one) West Coast Data Center (set two) Singapore Data Center


NB the /25 means from .0 to .127 in each range.





Thanks Stephen.  I think we'll try that.



But my info was from their integration API doc for summer 2010 (security considerations for outbound msging):


I guess that's not reliable?



- Cris



Yeah, looks like the developer doco guys need to update the info on their side :smileywink: