Skip to content

Salesforce IP ranges to allowlist, ready to copy

Pick what your firewall, proxy or mail filter needs: data centers, Hyperforce, email or domains, as CIDR, start and end, or metadata.

IP Allowlist Lookup

Copy Salesforce's IP ranges for your firewall

Letting Salesforce through a firewall or mail filter? Its lists are below. Limiting who logs in to your org? Pick Trusted IP ranges.

Try:

Runs in your browser. Nothing you type is sent or stored.

Salesforce IP ranges to allow

From each app's own pages and files, checked Nov 15, 2026.

What are you doing?

Your inbound rule, for the app calling your servers

Allow 141 ranges in 2 lists

Allow all 69 ranges, and the Hyperforce list too

Salesforce's own data center ranges by internet registry, plus a USA table its network team adds. API integrations use the same ranges as the Salesforce website.

These ranges hold 875,437 IPv4 addresses.

Why
An address only narrows who can reach you. A signature, a shared secret or mutual TLS proves the caller.
ARIN, 16 ranges
  • 3.146.43.224/28
  • 13.56.32.176/28
  • 13.58.135.64/28
  • 13.108.0.0/14
  • 34.211.108.32/28
  • 34.226.36.48/28
  • 35.182.14.32/28
  • 66.231.80.0/20
RIPE, 19 ranges
  • 13.36.84.96/28
  • 13.37.59.29/32
  • 13.50.12.176/28
  • 15.236.110.244/32
  • 15.236.160.173/32
  • 16.63.106.240/28
  • 18.102.214.64/28
  • 34.253.190.64/28
APNIC, 21 ranges
  • 13.113.196.48/28
  • 13.124.145.0/28
  • 13.126.23.64/28
  • 13.210.3.208/28
  • 13.215.171.240/28
  • 13.228.64.80/28
  • 13.250.175.171/32
  • 13.251.9.241/32
LACNIC, 4 ranges
  • 18.228.66.156/32
  • 18.228.207.180/32
  • 54.233.205.0/28
  • 177.71.229.247/32
USA, recommended by Salesforce's network team: connections from Salesforce, 9 ranges
  • 3.225.151.145/32
  • 3.225.240.254/32
  • 18.204.28.162/32
  • 18.211.105.61/32
  • 34.197.58.108/32
  • 34.204.111.166/32
  • 52.3.16.30/32
  • 52.22.251.194/32
How to apply: Salesforce data centers

Who acts: Your firewall or network team

  1. Allow every range in this list and every range in the Hyperforce list, not only the ones near you: Salesforce's best practice is to allow its entire set, and orgs not on Hyperforce need the Hyperforce list too.
  2. The USA table is the one place Salesforce gives a direction: its 'to' addresses sit on the Calls to them tab, its 'from' addresses on Calls from them.
  3. Recheck at least once a quarter, and before an instance refresh, site switch or org migration.

Better than an IP list: Salesforce prefers mutual TLS (mTLS) to IP allowlists. To let your people reach Salesforce, allow its domains on the Calls to them tab.

How changes are announced: Help article with a revision history (opens in a new tab). Notice: None stated for this list. Bookmark the article and check it at least quarterly.

Source: Salesforce help: 000384438 (opens in a new tab), Salesforce help: 000394078 (opens in a new tab). Checked Nov 15, 2026.

Allow every Hyperforce range, in and out

One list for traffic from Hyperforce to your network and from outside into Hyperforce, edge addresses included since July 21, 2026.

These ranges hold 18,944 IPv4 addresses.

Why
An address only narrows who can reach you. A signature, a shared secret or mutual TLS proves the caller.
Hyperforce on AWS, af-south-1, 2 ranges
  • 145.224.193.0/24
  • 145.224.217.0/24
Hyperforce on AWS, ap-northeast-1, 2 ranges
  • 141.163.208.0/23
  • 2a03:5d67:fe60::/45
Hyperforce on AWS, ap-northeast-2, 2 ranges
  • 141.163.200.0/23
  • 2a03:5d67:fe88::/45
Hyperforce on AWS, ap-northeast-3, 3 ranges
  • 141.163.214.0/24
  • 141.163.195.0/24
  • 2a03:5d67:fec0::/45
Hyperforce on AWS, ap-south-1, 3 ranges
  • 141.163.204.0/23
  • 141.163.207.0/24
  • 2a03:5d67:fe40::/45
Hyperforce on AWS, ap-south-2, 3 ranges
  • 141.163.216.0/24
  • 141.163.203.0/24
  • 2a03:5d67:fec8::/45
Hyperforce on AWS, ap-southeast-1, 2 ranges
  • 141.163.196.0/23
  • 2a03:5d67:fe68::/45
Hyperforce on AWS, ap-southeast-2, 3 ranges
  • 141.163.192.0/23
  • 141.163.199.0/24
  • 2a03:5d67:fe50::/45
Hyperforce on AWS, ap-southeast-3, 3 ranges
  • 141.163.212.0/24
  • 141.163.211.0/24
  • 2a03:5d67:fea0::/45
Hyperforce on AWS, ca-central-1, 3 ranges
  • 155.226.152.0/23
  • 155.226.163.0/24
  • 2a03:5d67:fe58::/45
Hyperforce on AWS, eu-central-1, 3 ranges
  • 145.224.208.0/23
  • 145.224.211.0/24
  • 2a03:5d67:fe48::/45
Hyperforce on AWS, eu-central-2, 3 ranges
  • 145.224.198.0/24
  • 145.224.215.0/24
  • 2a03:5d67:fe90::/45
Hyperforce on AWS, eu-north-1, 3 ranges
  • 145.224.204.0/23
  • 145.224.199.0/24
  • 2a03:5d67:fe98::/45
Hyperforce on AWS, eu-south-1, 3 ranges
  • 145.224.196.0/24
  • 145.224.202.0/23
  • 2a03:5d67:fea8::/45
Hyperforce on AWS, eu-west-2, 3 ranges
  • 145.224.200.0/23
  • 145.224.219.0/24
  • 2a03:5d67:fe80::/45
Hyperforce on AWS, eu-west-3, 3 ranges
  • 145.224.212.0/24
  • 145.224.206.0/23
  • 2a03:5d67:fe78::/45
Hyperforce on AWS, il-central-1, 3 ranges
  • 145.224.192.0/24
  • 145.224.221.0/24
  • 2a03:5d67:feb0::/45
Hyperforce on AWS, me-central-1, 1 range
  • 145.224.194.0/24
Hyperforce on AWS, sa-east-1, 3 ranges
  • 155.226.188.0/23
  • 155.226.164.0/24
  • 2a03:5d67:fe70::/45
Hyperforce on AWS, us-east-1, 4 ranges
  • 155.226.144.0/22
  • 155.226.137.0/24
  • 155.226.160.0/24
  • 2a03:5d67:fe20::/43
Hyperforce on AWS, us-east-2, 7 ranges
  • 155.226.156.0/23
  • 155.226.186.0/23
  • 155.226.165.0/24
  • 155.226.136.0/24
  • 155.226.161.0/24
  • 2a03:5d67:feb8::/45
  • 2a03:5d67:fed0::/45
Hyperforce on AWS, us-west-2, 6 ranges
  • 155.226.128.0/21
  • 155.226.166.0/24
  • 155.226.151.0/24
  • 155.226.141.0/24
  • 2a03:5d67:ffd0::/45
  • 2a03:5d67:fe00::/43
Hyperforce on Google Cloud, europe-west10, 2 ranges
  • 163.79.130.0/24
  • 163.79.131.0/24
Hyperforce on Google Cloud, us-central1, 1 range
  • 129.77.12.0/24
Hyperforce on Google Cloud, us-east4, 1 range
  • 129.77.13.0/24
How to apply: Hyperforce

Who acts: Your firewall or network team

  1. Allow every range in the file, IPv4 or IPv6 to match your network. Do not narrow it to your region: Salesforce asks you to allow its entire set.
  2. Fetch the JSON file on a schedule and compare its publication date (createDate) with your last copy, as Salesforce suggests, so a new range never surprises you.
  3. Since July 21, 2026, Salesforce says you can retire the short-term Edge ranges 141.163.216.224/28 and 141.163.214.224/28: both now sit inside ranges of this file.
  4. Subscribe to Trust notifications (Core Service, Maintenance) to hear about changes 30 days ahead.

Better than an IP list: Salesforce recommends mTLS or a domain allowlist over IP allowlists. For Apex callouts it still recommends an IP allowlist.

How changes are announced: JSON file (opens in a new tab). Notice: At least 30 days before the addresses are used. Trust notifications, or poll the file and compare its publication date (createDate).

Source: ip-ranges.salesforce.com: ip ranges.json (opens in a new tab), Salesforce help: 003876184 (opens in a new tab), Salesforce help: 000394078 (opens in a new tab). Checked Nov 15, 2026.

Only if you host your own model for Einstein Studio: 162 addresses

The addresses Salesforce uses to reach a large language model you host yourself and set up in Einstein Studio (BYO models and Open Connector).

These ranges hold 162 IPv4 addresses.

Why
An address only narrows who can reach you. A signature, a shared secret or mutual TLS proves the caller.
prod0, AWS us-west-2, 6 ranges
  • 100.20.8.47/32
  • 54.214.223.28/32
  • 44.227.245.234/32
  • 54.214.230.123/32
  • 35.81.97.53/32
  • 44.232.118.84/32
prod1, AWS us-east-1, 12 ranges
  • 34.238.21.131/32
  • 3.224.177.34/32
  • 54.237.22.177/32
  • 3.220.205.155/32
  • 52.55.32.35/32
  • 3.220.253.146/32
  • 3.229.91.235/32
  • 34.207.2.81/32
prod2, AWS ap-south-1, 12 ranges
  • 3.108.142.253/32
  • 3.110.250.47/32
  • 15.206.121.241/32
  • 43.204.14.2/32
  • 43.204.62.144/32
  • 65.0.219.99/32
  • 3.109.180.35/32
  • 3.7.182.145/32
prod3, AWS eu-central-1, 12 ranges
  • 3.121.156.71/32
  • 18.197.63.0/32
  • 18.197.54.134/32
  • 3.71.152.110/32
  • 18.184.48.162/32
  • 3.125.254.14/32
  • 3.73.249.80/32
  • 52.28.240.147/32
prod4, AWS ap-southeast-2, 6 ranges
  • 3.24.132.31/32
  • 13.236.74.124/32
  • 13.238.56.174/32
  • 13.237.1.48/32
  • 54.79.171.107/32
  • 52.62.126.31/32
prod5, AWS us-west-2, 12 ranges
  • 34.208.5.10/32
  • 52.13.250.126/32
  • 54.188.79.241/32
  • 54.200.45.180/32
  • 52.34.45.63/32
  • 54.218.193.17/32
  • 52.41.34.212/32
  • 54.212.126.141/32
prod8, AWS ca-central-1, 6 ranges
  • 15.157.153.245/32
  • 99.79.21.163/32
  • 3.96.95.234/32
  • 15.157.137.3/32
  • 3.98.115.14/32
  • 15.222.83.6/32
prod9, AWS ap-northeast-1, 6 ranges
  • 54.248.34.19/32
  • 52.195.52.255/32
  • 52.197.2.243/32
  • 13.113.104.206/32
  • 54.178.73.144/32
  • 52.193.130.46/32
prod10, AWS ap-southeast-1, 6 ranges
  • 3.1.122.171/32
  • 18.143.0.106/32
  • 18.138.0.100/32
  • 54.179.9.47/32
  • 54.179.99.250/32
  • 18.142.131.109/32
prod11, AWS sa-east-1, 6 ranges
  • 52.67.202.131/32
  • 18.229.50.218/32
  • 18.229.130.141/32
  • 52.67.49.199/32
  • 52.67.0.81/32
  • 15.229.95.180/32
prod12, AWS eu-west-3, 6 ranges
  • 13.36.150.253/32
  • 13.36.20.200/32
  • 52.47.65.168/32
  • 13.36.143.253/32
  • 35.180.224.212/32
  • 13.39.45.11/32
prod13, AWS eu-west-2, 6 ranges
  • 13.43.148.33/32
  • 18.130.162.182/32
  • 18.170.84.175/32
  • 35.177.128.93/32
  • 18.171.121.22/32
  • 3.11.125.124/32
prod14, AWS ap-northeast-2, 6 ranges
  • 52.79.165.197/32
  • 43.201.188.168/32
  • 15.165.132.221/32
  • 15.164.248.43/32
  • 13.125.137.153/32
  • 3.37.114.93/32
prod15, AWS eu-central-2, 6 ranges
  • 16.63.227.204/32
  • 16.63.248.156/32
  • 16.63.84.96/32
  • 16.63.186.2/32
  • 16.63.154.91/32
  • 16.63.193.108/32
prod16, AWS eu-north-1, 6 ranges
  • 16.171.123.179/32
  • 13.60.147.39/32
  • 13.60.112.26/32
  • 16.170.33.212/32
  • 13.60.132.148/32
  • 16.16.234.238/32
prod17, AWS ap-southeast-3, 6 ranges
  • 108.137.184.212/32
  • 16.78.36.95/32
  • 16.78.139.37/32
  • 43.218.253.9/32
  • 16.78.130.238/32
  • 43.218.64.141/32
prod18, AWS me-central-1, 6 ranges
  • 40.172.5.102/32
  • 3.28.235.200/32
  • 51.112.133.38/32
  • 40.172.72.194/32
  • 51.112.65.75/32
  • 3.28.171.227/32
prod19, AWS eu-south-1, 6 ranges
  • 18.102.37.207/32
  • 18.102.253.33/32
  • 15.161.117.12/32
  • 35.152.117.200/32
  • 15.161.31.139/32
  • 15.161.122.134/32
prod20, AWS il-central-1, 6 ranges
  • 51.17.149.232/32
  • 51.17.188.148/32
  • 51.17.143.61/32
  • 51.16.246.241/32
  • 51.16.194.202/32
  • 51.17.119.175/32
prod21, AWS us-east-2, 12 ranges
  • 18.220.72.169/32
  • 3.16.227.154/32
  • 3.128.44.52/32
  • 3.23.58.253/32
  • 3.134.18.129/32
  • 18.224.234.3/32
  • 13.58.230.133/32
  • 13.58.166.139/32
prod22, AWS ap-northeast-3, 6 ranges
  • 15.168.196.99/32
  • 15.168.106.33/32
  • 13.208.57.88/32
  • 15.168.120.98/32
  • 15.168.146.194/32
  • 15.168.203.85/32
prod24, AWS ap-south-2, 6 ranges
  • 18.60.209.20/32
  • 98.130.40.211/32
  • 18.61.180.230/32
  • 98.130.27.97/32
  • 18.61.213.67/32
  • 18.60.197.131/32
How to apply: Calls to a model you host (BYO models)

Who acts: The team that runs your model endpoint

  1. Allow these on the endpoint that serves your model. Salesforce lists them by its own region names; if you are not sure of yours, allow all of them.
  2. Recheck often: Salesforce says these addresses are likely to change and will move into the Hyperforce file later.

Better than an IP list: Require a key or token on your model endpoint as well; the addresses alone do not prove the caller.

How changes are announced: Help article with a revision history (opens in a new tab). Notice: None stated; Salesforce says the addresses are likely to change. Check the article.

Source: Salesforce help: 000384438 (opens in a new tab). Checked Nov 15, 2026.

Only if you use myTrailhead with login IP limits: 10 addresses

The addresses myTrailhead calls out from. Salesforce asks orgs that use Salesforce Identity for myTrailhead and limit logins by IP to allow them.

These ranges hold 10 IPv4 addresses.

Why
An address only narrows who can reach you. A signature, a shared secret or mutual TLS proves the caller.
myTrailhead outbound, 10 ranges
  • 52.205.40.33/32
  • 52.205.41.207/32
  • 52.205.38.38/32
  • 52.6.127.225/32
  • 34.217.238.68/32
  • 52.13.162.184/32
  • 52.36.203.77/32
  • 52.43.127.242/32
How to apply: myTrailhead outbound

Who acts: Your Salesforce admin

  1. Add these to your org's login or trusted IP ranges (copy them as Salesforce metadata), or users may not be able to log in to myTrailhead.

How changes are announced: Help article with a revision history (opens in a new tab). Notice: None stated. Check the article.

Source: Salesforce help: 000384438 (opens in a new tab). Checked Nov 15, 2026.

Photo of Utku Zihnioglu

By

ยท CEO & co-founder

Published Nov 16, 2026

New page: Salesforce's IP lists by direction, ready to copy.

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.

Salesforce IP ranges: questions

Does Salesforce publish its IP ranges as a JSON file?

Yes, for Hyperforce: ip-ranges.salesforce.com/ip-ranges.json covers traffic into and out of Hyperforce. The older data center ranges are only in Salesforce's help article, and orgs outside Hyperforce must allow both.

Which IP addresses does Salesforce send email from?

Its core mail servers use the blocks in Salesforce's email article. Mail from Hyperforce instances has no fixed blocks, so Salesforce recommends TLS, SPF, DKIM and DMARC over an IP allowlist.

Can I allow only the Salesforce IP ranges for my region?

Salesforce advises against it. Its best practice is to allow its entire set of ranges, and the Hyperforce file as well, even for orgs not on Hyperforce.

How often do Salesforce IP ranges change?

Several times a year. Salesforce adds Hyperforce addresses to its JSON file at least 30 days before it uses them, and asks you to recheck its lists at least once a quarter and before an instance refresh or org migration.

Which Salesforce domains should a proxy allow?

The domains on Salesforce's Allow the Required Domains page, such as *.force.com, *.salesforce.com and *.forceusercontent.com. Salesforce says users need these standard domains to reach it.

About this article

Photo of Utku Zihnioglu

Utku Zihnioglu

CEO & co-founder

Serial entrepreneur who built infrastructure companies handling billions of requests. Now leads engineering at Oneprofile, which finds the people worth talking to, researches each one, and follows up until they reply.

Drafted with AI from our product docs and code. Utku Zihnioglu answers for what it says.

Enrich Salesforce through its own API

Connect Salesforce to Oneprofile and fill in missing fields, at a per-minute rate you set.

Free plan: 200 credits a month, 3 integrations, no card

Enrich Salesforce through its own API

Connect Salesforce to Oneprofile and fill in missing fields, at a per-minute rate you set.

Free plan: 200 credits a month, 3 integrations, no card