Salesforce IP ranges to whitelist come in two lists: its own data center ranges, and the Hyperforce file for its public cloud. Orgs outside Hyperforce must allow both. Hyperforce orgs need the Hyperforce file, though Salesforce prefers mutual TLS there. Its best practice is to allow the entire set, not just the ranges near your org.
Everything above comes from Salesforce's own pages: its IP Addresses and Domains to Allow article, its Hyperforce file and its email article, each linked under its list. We re-read them every week.
Which list you need
If Salesforce calls your systems (outbound messages, Apex callouts, a flow that posts to your server), allow both lists on your inbound rule. If your people or servers call Salesforce, allow its required domains in your proxy. Lists for a model you host for Einstein Studio and for myTrailhead sit under the main lists, for the teams that use them.
Email is separate. Salesforce publishes address blocks for its core mail servers, but not for mail from Hyperforce instances, whose addresses change. It recommends TLS, SPF, DKIM and DMARC over an IP list. Its Email Relay addresses are only for orgs that relay Salesforce mail through their own server. Our SPF lookup shows what your own domain authorizes.
Keep the list current
Salesforce adds Hyperforce addresses to its file before it starts using them, and asks you to recheck its lists regularly and before an instance refresh or org migration. To spot a change before your integration does, have a script save the JSON file and compare its publication date with your last copy, as Salesforce suggests. The tool also shows each change Salesforce dates in its articles.
Limiting logins to your own addresses
Trusted IP ranges and login IP ranges hold your addresses, not Salesforce's. Trusted ranges let users skip the extra identity check; login ranges on a profile block logins from anywhere else. Our login IP ranges tool turns an app's ranges, such as Zapier's, into metadata you deploy once, instead of one form per range.
