Salesforce login IP ranges sit on a profile and block that profile's users from logging in from any other address. Trusted IP ranges, under Network Access, only let users inside them skip the extra identity check; everyone else can still log in after it. Both hold your addresses, never Salesforce's.
Pick an app in the tool above, such as Zapier or Account Engagement, and its published ranges come out as login IP ranges for a profile, or as trusted ranges for your org's security settings, ready to deploy.
Where the setting lives
In Enterprise, Unlimited, Performance and Developer Editions, login IP ranges are on each profile. In Group and Personal Editions, and in Professional Edition without the Edit Profiles & Page Layouts preference, they are on the Session Settings page. Each range takes a start and an end address, IPv4 or IPv6 but never both in one range.
Many ranges, one deploy
The form saves one range at a time, so an app with many ranges means one form per range. The metadata format writes them as loginIpRanges entries for a profile, or as ipRanges entries under networkAccess for trusted ranges. Salesforce warns that deploying trusted ranges replaces every range you have, so retrieve your current ones and add to them.
Enforce on every request
Session Settings can enforce login IP ranges on every request, not only at login. It applies to every profile that has login IP ranges, so add each integration user's app ranges to its profile before you turn it on. Apps that publish no fixed address, such as most Zapier traffic, need a static option first. Salesforce publishes the sync addresses of its own Account Engagement for exactly this case.
