Loading

Salesforce Core Services - IP Addresses and Domains to Allow

Publiceringsdatum: Apr 1, 2026
Beskrivning

At Salesforce, trust is our #1 value. We understand that our customers need to be confident that they are communicating with Salesforce in a secure environment.  Whether your org is in a Salesforce-managed (first-party) data center or on Hyperforce, we recommend that customers adopt modern best practices to ensure you retain uninterrupted access to your Salesforce infrastructure. Customers can take maximum advantage of these options by adopting recommended practices such as implementing mTLS.

Allowing designated IPs is not the preferred or recommended method to prevent internet traffic intended for Salesforce from being hijacked or rerouted to a rogue website. We discourage allowlisting because when IPs are added or changed, customers can experience connection interruptions until they update their allowlist databases. This maintenance overhead can be burdensome.
 

Non Hyperforce

For customers who reside in our non-Hyperforce infrastructure and have a business or compliance need to reference IP allow lists to establish and maintain their corporate network and email settings, we provide our complete portfolio of first-party IP addresses and domains below.

We have exclusive ownership of every first-party public IP address that we use. The IP addresses that we use have been allocated directly to us by The American Registry for Internet Numbers (ARIN), The Asia Pacific Network Information Centre (APNIC), and Réseaux IP Européens (RIPE) or assigned to us by one of our partners from the same Regional Internet Registries. These organizations are coordinated by the Internet Assigned Numbers Authority (IANA) and the Internet Corporation for Assigned Names and Numbers (ICANN). Hyperforce IPs belong to the cloud provider.

If you have a business or compliance need that requires allowlisting IP addresses, we recommend bookmarking and revisiting this article regularly to stay informed about any changes to our IP ranges and addresses. It is especially important to ensure that your security team includes any new IPs in advance of any infrastructure activities such as Instance Refreshes, Site Switches, and Org Migrations. For more information about our infrastructure best practices, see Prepare for System Maintenance.

In addition to allowing the IP ranges listed in this article, customers on non-Hyperforce infrastructure must also allow the Hyperforce IP ranges listed at https://ip-ranges.salesforce.com/ip-ranges.json.
 

Hyperforce

If you are a Hyperforce customer, please note that because of the dynamic nature of cloud environments, Salesforce strongly recommends using mTLS as described in Preferred Alternatives to IP Allowlisting on Hyperforce, rather than IP allowlists. If you have a business or compliance need to maintain IP allowlists on Hyperforce, the comprehensive list of required IP addresses is available in JSON format at the URL:

https://ip-ranges.salesforce.com/ip-ranges.json

This list includes outbound IPs for connection from Hyperforce to your network, and inbound IPs, including some Edge IPs, for connections to Hyperforce from external sources. These IPs are not for email, and not for Marketing Cloud, Commerce Cloud, or Slack. Learn more in Hyperforce IPs to Allow - Sales, Service, Industries, and Tableau Clouds. A limited number of Hyperforce IPs which are not yet contained in the JSON file are listed in this article.​​​​​ If you are a Government Cloud Plus customer, see IP Addresses to Allow for Government Cloud Plus.

Allow Short-Term Edge IP ranges

The table Short-Term AWS IP Ranges for Hyperforce Edge contains Salesforce Edge IPs owned by AWS for every region, worldwide, for traffic flowing into Hyperforce.

Over time, Salesforce plans to relocate Edge IPs into the Hyperforce Public IP ranges at https://ip-ranges.salesforce.com/ip-ranges.json, which Salesforce controls.* Allowing the full set of Hyperforce Public IP ranges preserves your connectivity during the transition. Salesforce recommends revisiting this article periodically so that you’re aware when we retire the AWS ranges, and can remove them from your allowlists.

Short-Term AWS IP Ranges for Hyperforce Edge

CountryAWS RegionIP Range /28
Australiaap-southeast-213.210.3.208/28
Brazilsa-east-154.233.205.0/28
Canadaca-central-135.182.14.32/28
Franceeu-west-313.36.84.96/28
Germanyeu-central-135.158.127.48/28
Indiaap-south-113.126.23.64/28
Indiaap-south-2141.163.216.224/28
Indonesiaap-southeast-316.78.19.16/28
Israelil-central-151.17.195.96/28
Italyeu-south-118.102.214.64/28
Japanap-northeast-113.113.196.48/28
Japanap-northeast-3141.163.214.224/28
Singaporeap-southeast-113.228.64.80/28
South Koreaap-northeast-243.201.151.176/28
Swedeneu-north-113.50.12.176/28
Switzerlandeu-central-216.63.106.240/28
United Arab Emiratesme-central-151.112.11.192/28
United Kingdomeu-west-235.176.92.16/28
United Statesus-east-134.226.36.48/28
United Statesus-east-23.146.43.224/28
United Statesus-west-234.211.108.32/28

* Forward-looking statements apply.

NOTE: This information is subject to change and we recommend that you check back quarterly for the addition of new IP ranges for Salesforce-operated data centers. A chart outlining the revision history over the past 6 months can be found at the end of the article.

Lösning

 

Article Contents

 

Salesforce’s IP Ranges

Salesforce does not offer static IP addresses or small ranges of IP addresses for individual instances. All IP ranges are provided in Classless Inter-Domain Routing (CIDR) notation. For more information on CIDR please see Classless Inter Domain Routing on Wikipedia.

Required for seamless access: Our best practice is to allow our entire set of IP ranges. This is to ensure our login pools can process your end users’ and integrations’ login authentications when accessing Salesforce all over the world, and to avoid any unintended service disruptions due to movement between data center sites. Incoming traffic to your first-party org can arrive from any Salesforce Edge, which operates on both first-party and Hyperforce infrastructure. In addition to the IPs in this article, allow the complete list of Hyperforce IP ranges listed in https://ip-ranges.salesforce.com/ip-ranges.json.

Our Network Engineering team recommends that customers allow the following subnet mask IPs:
 

IPv4 NetworkIPv4 IP Range
ARIN
3.146.43.224/283.146.43.224 - 3.146.43.239
13.56.32.176/2813.56.32.176 - 13.56.32.191
13.58.135.64/2813.58.135.64 - 13.58.135.79
13.108.0.0/1413.108.0.0 - 13.111.255.255
34.211.108.32/2834.211.108.32 - 34.211.108.47
34.226.36.48/2834.226.36.48 - 34.226.36.63
35.182.14.32/2835.182.14.32 - 35.182.14.47
66.231.80.0/2066.231.80.0 - 66.231.95.255
68.232.192.0/2068.232.192.0 - 68.232.207.255
96.43.144.0/2096.43.144.0 - 96.43.159.255
128.17.0.0/16128.17.0.0 - 128.17.255.255
128.245.0.0/16128.245.0.0 - 128.245.255.255
136.146.0.0/15136.146.0.0 - 136.147.255.255
198.245.80.0/20198.245.80.0 - 198.245.95.255
199.122.120.0/21199.122.120.0 - 199.122.127.255
204.14.232.0/21204.14.232.0 - 204.14.239.255
RIPE
13.36.84.96/2813.36.84.96 - 13.36.84.111
13.37.59.29/32 
13.50.12.176/2813.50.12.176 - 13.50.12.191
15.236.110.244/32 
15.236.160.173/32 
16.63.106.240/2816.63.106.240 - 16.63.106.255
18.102.214.64/2818.102.214.64 - 18.102.214.79
34.253.190.64/2834.253.190.64 - 34.253.190.79
35.158.127.48/2835.158.127.48 - 35.158.127.63
35.176.92.16/2835.176.92.16 - 35.176.92.31
51.17.195.96/2851.17.195.96 - 51.17.195.111
51.112.11.192/2851.112.11.192 - 51.112.11.207
85.222.128.0/1985.222.128.0 - 85.222.159.255
159.92.128.0/17159.92.128.0 - 159.92.255.255
160.8.0.0/16160.8.0.0 - 160.8.255.255
161.71.0.0/17161.71.0.0 - 161.71.127.255
163.76.128.0/17163.76.128.0 - 163.76.255.255
163.79.128.0/17163.79.128.0 -163.79.255.255
185.79.140.0/22185.79.140.0 - 185.79.143.255
APNIC
13.113.196.48/2813.113.196.48 - 13.113.196.63
13.124.145.0/2813.124.145.0 - 13.124.145.15
13.126.23.64/2813.126.23.64 - 13.126.23.79
13.210.3.208/2813.210.3.208 - 13.210.3.223
13.215.171.240/2813.215.171.240 - 13.215.171.255
13.228.64.80/2813.228.64.80 - 13.228.64.95
13.250.175.171/32 
13.251.9.241/32 
16.78.19.16/2816.78.19.16 - 16.78.19.31
18.99.160.192/2818.99.160.192-18.99.160.207
18.181.43.11/32 
35.73.89.117/32 
43.201.151.176/2843.201.151.176 - 43.201.151.191
54.95.206.252/32 
54.254.118.123/32 
101.53.160.0/19101.53.160.0 - 101.53.191.255
104.161.128.0/17104.161.128.0 - 104.161.255.255
161.32.64.0/18161.32.64.0 - 161.32.127.255
161.32.128.0/17161.32.128.0 - 161.32.255.255
161.71.128.0/17161.71.128.0 - 161.71.255.255
182.50.76.0/22182.50.76.0 - 182.50.79.255
202.129.242.0/23202.129.242.0 - 202.129.243.255
LACNIC
18.228.66.156/32
18.228.207.180/32
54.233.205.0/2854.233.205.0 - 54.233.205.15
177.71.229.247/32


Our Network Engineering team additionally recommends that customers allow the following IP addresses:
 

Region Connections to SalesforceConnections from Salesforce
USA

3.228.190.251
34.206.116.149
35.174.143.92
52.203.77.201
54.156.107.163
54.158.77.4
54.163.166.54
54.83.60.38
107.21.202.122

3.225.151.145
3.225.240.254/32
18.204.28.162/32
18.211.105.61
34.197.58.108
34.204.111.166/32
52.3.16.30
52.22.251.194
52.70.135.185



NOTE: Salesforce Support occasionally requests a subset range of IPs to allow. Be advised that our best practice and recommendation is to allow the entire list of Salesforce IP ranges for seamless access. Narrowing the range of IPs would put you at greater risk of interrupted access for you and your users.

Back to Top
 

API Integrations

API integrations use the same set of IP ranges as the Salesforce website. Please use the IP ranges listed in Salesforce’s IP Ranges above.

Back to Top

 

Firewalls

Allowing designated IPs can occur at several different points on a customer’s network, but the most common place is the firewall. When adding or updating IPs allowed, please ensure that any IP restrictions on your firewall match the described information in this article.
 

Back to Top

 

Required Domains

If your company has policies to allow only Salesforce domains, please include the domains in the Salesforce Help Required Domains, to ensure you receive all content from Salesforce:

If you are using Force.com sites, and you want to set up domain name-based filtering, you will need to add in your My Domain (subdomain) followed by secure.force.com to access your site (e.g. https://[MyDomainName]. secure.force.com).

CloudFront content delivery network (CDN) for static Lightning components is now enabled in all new and existing Experience Cloud. Additionally, the CDN for Lightning Component framework is also now available. A CDN speeds up page load time by storing cached versions in multiple geographic locations. This setting turns on Lightning CDN delivery for the static JavaScript in the Lightning Component framework. For more information, review Enable CDN to Load Lightning Experience Faster. If you experience issues, ensure that static.lightning.force.com, a.static.lightning.force.com, b.static.lightning.force.com, *.static.lightning.force.com is added to any allowed list or firewall that your company operates, and ask your IT department if your company’s firewall blocks CDN content.

Back to Top
 

Salesforce URLs not in our infrastructure

If you need to allow specific URLs for internal routing (also known as URL filtering), please include the following URLs in your network settings:
 

 

Feature-Specific IP Addresses

  • Salesforce Inbox - For seamless usage, visit the Salesforce Email Integration Security Guide for a specific list of IP addresses to allow.
  • Salesforce Identity for myTrailhead - To use Salesforce Identity for myTrailhead in a Salesforce org that has IP restrictions configured, allow the IP addresses listed in the myTrailhead Outbound IP Addresses section.


Back to Top

 

Email Settings

NOTE: If you are a Gov Cloud customer, please refer to the IP Addresses to Allow for Government Cloud article for Email Settings details specific to your organization.
 

Email Security Filters

Salesforce sends email from a variety of IP addresses. If your organization blocks these IP addresses, users may not receive all email sent from Salesforce. Because Salesforce sends email from an ever-growing list of IP addresses, we recommend relying on standard email security protocols - TLS, SPF, DKIM, and DMARC - instead of IP allowlists to ensure that your organization’s users receive all Salesforce emails. Please refer to the Ensure you can receive email from the Salesforce application article for more information.
 
NOTE: If you are a Hyperforce customer, you should use the standard email security protocols to maintain email security and ensure your organization’s users receive all Salesforce emails. Please refer to the Retain uninterrupted access to Salesforce services on Hyperforce article for more information.


Back to Top

 

myTrailhead Outbound IP Addresses

myTrailhead customers who choose Salesforce Identity for myTrailhead as their authentication provider may need to enable the following myTrailhead outbound IP addresses in their Salesforce org. If your org blocks any of these IP addresses and you use Salesforce Identity for myTrailhead, you users may not be able to log in to myTrailhead.
 

myTrailhead Outbound IP Addresses
52.205.40.33
52.205.41.207
52.205.38.38
52.6.127.225
34.217.238.68
52.13.162.184
52.36.203.77
52.43.127.242
54.245.10.179
100.20.235.153


Back to Top

BYO Models and Open Connector IP Addresses

Salesforce uses these IP addresses to communicate with an LLM that you host yourself and configure in Einstein Studio or a service that implements the LLM Open Connector API specification. 

With Bring Your Own LLM (BYOLLM), you can use Einstein Studio to add a foundation model from a supported provider, configure your own instance of the model, and connect to the model using your own credentials. The LLM Open Connector enables you to connect any language model to the Einstein AI Platform. If your security policy requires a strict network Access Control List (ACL), make sure to add these IP addresses to your allowlists.

 

SF Region Name

AWS Region

BYO Models and Open Connector IP Addresses

prod0

uswest2

100.20.8.47/32

prod0

uswest2

54.214.223.28/32

prod0

uswest2

44.227.245.234/32

prod0

uswest2

54.214.230.123/32

prod0

uswest2

35.81.97.53/32

prod0

uswest2

44.232.118.84/32

prod1

useast1

34.238.21.131/32

prod1

useast1

3.224.177.34/32

prod1

useast1

54.237.22.177/32

prod1

useast1

3.220.205.155/32

prod1

useast1

52.55.32.35/32

prod1

useast1

3.220.253.146/32

prod1

useast1

3.229.91.235/32

prod1

useast1

34.207.2.81/32

prod1

useast1

100.28.155.43/32

prod1

useast1

18.205.65.180/32

prod1

useast1

54.145.109.78/32

prod1

useast1

54.83.235.217/32

prod2

apsouth1

3.108.142.253/32

prod2

apsouth1

3.110.250.47/32

prod2

apsouth1

15.206.121.241/32

prod2

apsouth1

43.204.14.2/32

prod2

apsouth1

43.204.62.144/32

prod2

apsouth1

65.0.219.99/32

prod2

apsouth1

3.109.180.35/32

prod2

apsouth1

3.7.182.145/32

prod2

apsouth1

3.108.205.172/32

prod2

apsouth1

13.234.139.246/32

prod2

apsouth1

3.109.245.36/32

prod2

apsouth1

43.204.189.211/32

prod3

eucentral1

3.121.156.71/32

prod3

eucentral1

18.197.63.0/32

prod3

eucentral1

18.197.54.134/32

prod3

eucentral1

3.71.152.110/32

prod3

eucentral1

18.184.48.162/32

prod3

eucentral1

3.125.254.14/32

prod3

eucentral1

3.73.249.80/32

prod3

eucentral1

52.28.240.147/32

prod3

eucentral1

52.59.29.183/32

prod3

eucentral1

3.77.174.1/32

prod3

eucentral1

52.29.12.45/32

prod3

eucentral1

18.194.60.96/32

prod4

apsoutheast2

3.24.132.31/32

prod4

apsoutheast2

13.236.74.124/32

prod4

apsoutheast2

13.238.56.174/32

prod4

apsoutheast2

13.237.1.48/32

prod4

apsoutheast2

54.79.171.107/32

prod4

apsoutheast2

52.62.126.31/32

prod4

apsoutheast2

54.79.171.107/32

prod4

apsoutheast2

13.237.1.48/32

prod4

apsoutheast2

13.238.56.174/32

prod4

apsoutheast2

52.62.126.31/32

prod4

apsoutheast2

13.236.74.124/32

prod4

apsoutheast2

3.24.132.31/32

prod5

uswest2

34.208.5.10/32

prod5

uswest2

52.13.250.126/32

prod5

uswest2

54.188.79.241/32

prod5

uswest2

54.200.45.180/32

prod5

uswest2

52.34.45.63/32

prod5

uswest2

54.218.193.17/32

prod5

uswest2

52.41.34.212/32

prod5

uswest2

54.212.126.141/32

prod5

uswest2

52.39.154.254/32

prod5

uswest2

44.234.229.153/32

prod5

uswest2

54.188.164.118/32

prod5

uswest2

52.41.102.181/32

prod8

cacentral1

15.157.153.245/32

prod8

cacentral1

99.79.21.163/32

prod8

cacentral1

3.96.95.234/32

prod8

cacentral1

15.157.137.3/32

prod8

cacentral1

3.98.115.14/32

prod8

cacentral1

15.222.83.6/32

prod9

apnortheast1

54.248.34.19/32

prod9

apnortheast1

52.195.52.255/32

prod9

apnortheast1

52.197.2.243/32

prod9

apnortheast1

13.113.104.206/32

prod9

apnortheast1

54.178.73.144/32

prod9

apnortheast1

52.193.130.46/32

prod10

apsoutheast1

3.1.122.171/32

prod10

apsoutheast1

18.143.0.106/32

prod10

apsoutheast1

18.138.0.100/32

prod10

apsoutheast1

54.179.9.47/32

prod10

apsoutheast1

54.179.99.250/32

prod10

apsoutheast1

18.142.131.109/32

prod11

saeast1

52.67.202.131/32

prod11

saeast1

18.229.50.218/32

prod11

saeast1

18.229.130.141/32

prod11

saeast1

52.67.49.199/32

prod11

saeast1

52.67.0.81/32

prod11

saeast1

15.229.95.180/32

prod12

euwest3

13.36.150.253/32

prod12

euwest3

13.36.20.200/32

prod12

euwest3

52.47.65.168/32

prod12

euwest3

13.36.143.253/32

prod12

euwest3

35.180.224.212/32

prod12

euwest3

13.39.45.11/32

prod13

euwest2

13.43.148.33/32

prod13

euwest2

18.130.162.182/32

prod13

euwest2

18.170.84.175/32

prod13

euwest2

35.177.128.93/32

prod13

euwest2

18.171.121.22/32

prod13

euwest2

3.11.125.124/32

prod14

apnortheast2

52.79.165.197/32

prod14

apnortheast2

43.201.188.168/32

prod14

apnortheast2

15.165.132.221/32

prod14

apnortheast2

15.164.248.43/32

prod14

apnortheast2

13.125.137.153/32

prod14

apnortheast2

3.37.114.93/32

prod15

eucentral2

16.63.227.204/32

prod15

eucentral2

16.63.248.156/32

prod15

eucentral2

16.63.84.96/32

prod15

eucentral2

16.63.186.2/32

prod15

eucentral2

16.63.154.91/32

prod15

eucentral2

16.63.193.108/32

prod16

eunorth1

16.171.123.179/32

prod16

eunorth1

13.60.147.39/32

prod16

eunorth1

13.60.112.26/32

prod16

eunorth1

16.170.33.212/32

prod16

eunorth1

13.60.132.148/32

prod16

eunorth1

16.16.234.238/32

prod17

apsoutheast3

108.137.184.212/32

prod17

apsoutheast3

16.78.36.95/32

prod17

apsoutheast3

16.78.139.37/32

prod17

apsoutheast3

43.218.253.9/32

prod17

apsoutheast3

16.78.130.238/32

prod17

apsoutheast3

43.218.64.141/32

prod18

mecentral1

40.172.5.102/32

prod18

mecentral1

3.28.235.200/32

prod18

mecentral1

51.112.133.38/32

prod18

mecentral1

40.172.72.194/32

prod18

mecentral1

51.112.65.75/32

prod18

mecentral1

3.28.171.227/32

prod19

eusouth1

18.102.37.207/32

prod19

eusouth1

18.102.253.33/32

prod19

eusouth1

15.161.117.12/32

prod19

eusouth1

35.152.117.200/32

prod19

eusouth1

15.161.31.139/32

prod19

eusouth1

15.161.122.134/32

prod20

ilcentral1

51.17.149.232/32

prod20

ilcentral1

51.17.188.148/32

prod20

ilcentral1

51.17.143.61/32

prod20

ilcentral1

51.16.246.241/32

prod20

ilcentral1

51.16.194.202/32

prod20

ilcentral1

51.17.119.175/32

prod21

useast2

18.220.72.169/32

prod21

useast2

3.16.227.154/32

prod21

useast2

3.128.44.52/32

prod21

useast2

3.23.58.253/32

prod21

useast2

3.134.18.129/32

prod21

useast2

18.224.234.3/32

prod21

useast2

13.58.230.133/32

prod21

useast2

13.58.166.139/32

prod21

useast2

18.223.61.186/32

prod21

useast2

3.15.123.216/32

prod21

useast2

3.132.64.235/32

prod21

useast2

18.189.74.117/32

prod22

apnortheast3

15.168.196.99/32

prod22

apnortheast3

15.168.106.33/32

prod22

apnortheast3

13.208.57.88/32

prod22

apnortheast3

15.168.120.98/32

prod22

apnortheast3

15.168.146.194/32

prod22

apnortheast3

15.168.203.85/32

prod24

apsouth2

18.60.209.20/32

prod24

apsouth2

98.130.40.211/32

prod24

apsouth2

18.61.180.230/32

prod24

apsouth2

98.130.27.97/32

prod24

apsouth2

18.61.213.67/32

prod24

apsouth2

18.60.197.131/32



Note: These IP addresses are likely to change over time. We recommend that you periodically check this list to ensure that your allowlist is up to date.

Back to Top

 

Revision History

Revisions made approximately within the past 6 months:
 

Date Revised

Revisions

April 1, 2026

Added revision history entry for March 27, 2026.

March 27, 2026

Fixed a typo in the URL embedded in the text https://ip-ranges.salesforce.com/ip-ranges.json under Allow Short-Term Edge IP ranges under Hyperforce.

March 12, 2026

Fixed a small typo in this line: prod3 eucentral1 52.28.240.147/3 to be 52.28.240.147.32.

 

October 30, 2025

Added instructions for customers with orgs in first-party infrastructure to allow the complete set of Hyperforce IP ranges. Removed instructions for allowing a regional subset of IPs. Allowing only one region could block legitimate traffic.

October 22, 2025

Modified the Hyperforce section of the introduction. The Hyperforce JSON file now includes inbound IP ranges.

 Oct 6, 2025

Added an additional clarification to the Required Domains section: *.static.lightning.force.com

Aug 21, 2025

Added prod0, prod1, prod3, prod4, prod5, prod10, prod11, prod12, prod14, prod15, prod16, prod17, prod18, prod19, prod20, prod21, prod22, and prod24 entries to BYO Models and Open Connector IP Addresses

June 19, 2025

Added prod21 entries to BYO Models and Open Connector IP Addresses

January 27, 2025

Added the 18.99.160.192/28 address block for Edge in HYD (with a range of 18.99.160.192-18.99.160.207) to the APNIC section. 

December 5, 2024

Updated location to find Hyperforce egress IPs.

December 3, 2024

Added SF Region Name and AWS Region columns to BYO Models and LLM Open Connector.

November 26, 2024

Added IP addresses for BYO Models and LLM Open Connector.

May 9, 2024

Added the following IP Ranges:

  • (RIPE) - 16.63.106.240/28 (16.63.106.240 - 16.63.106.255)

  • (RIPE) - 18.102.214.64/28 (18.102.214.64 - 18.102.214.79)

  • (RIPE) - 51.17.195.96/28 (51.17.195.96 - 51.17.195.111)

  • (APNIC) - 16.78.19.16/28 (16.78.19.16 - 16.78.19.31)

 

Removed IP ranges and guidance for legacy AWS environments in Canada and Australia. Those environments have been decommissioned.

Removed section Canada (Public Cloud) from table and removed these IP ranges.

  • 52.60.248.0/22 (52.60.248.0 - 52.60.251.255)

  • 52.60.252.0/22 (52.60.252.0 - 52.60.255.255)

Removed section Australia (Public Cloud) from table and removed these IP ranges.

  • 13.210.4.0/22 (13.210.4.0 - 13.210.7.255)

  • 13.210.8.0/22 (13.210.8.0 - 13.210.11.255)

March 21, 2024

Added 51.112.11.207 to the IP range for RIPE 51.112.11.192/28 network. 

February 6, 2024

Fixed ranges for the following:

ARIN: 3.146.43.224/28

RIPE: 51.112.11.192/28

January 15, 2024

Added to ARIN and RIPE:

ARIN: 3.146.43.224/28
RIPE: 51.112.11.192/28

 

Ytterligare resurser
Vote on the Salesforce ideaexchange to Provide Downloadable List of Allowed IP Addresses
Knowledge-artikelnummer

000384438

 
Laddar
Salesforce Help | Article