Loading
Slack 관련 문의처가 Salesforce Help로 통합 및 변경됩니다.더 많이 읽기
PHP 취약성 모니터링 현황에 대해더 많이 읽기

Hyperforce Network and Protocol Requirements: HTTP, TLS, and Connectivity

게시 일자: Oct 23, 2026
상세 설명

When you migrate an org to Hyperforce, some network and protocol behaviors differ from classic Salesforce datacenters. This article covers the current support status for HTTP/1.0 and HTTP/2, minimum TLS version requirements, IPv4 and IPv6 availability, VPC peering options, and the compatibility status of Salesforce Express Connect (SEC). Use this article to verify your integration and network configuration before or after a Hyperforce migration.

솔루션


Is HTTP/1.0 supported in Hyperforce?

HTTP/1.0 is supported on Hyperforce at full parity with Salesforce's first-party (1P) datacenters. There is no plan to block or restrict HTTP/1.0 traffic on Hyperforce — an earlier enforcement mechanism that was introduced in 2022 was subsequently removed and is no longer active. While HTTP/1.0 remains functional, Salesforce strongly recommends upgrading to HTTP/1.1 or HTTP/2 for improved performance and security. 
HTTP/1.1 introduced persistent connections and chunked transfer encoding. HTTP/2, which is generally available on Hyperforce, delivers multiplexing, header compression, and server push over TLS — all of which reduce latency significantly for Salesforce API and UI traffic.

Important behavior on HTTP/2: HTTP/2 transmits all headers in lowercase per RFC 9113. If your integration reads HTTP response headers in a case-sensitive manner, update it to handle lowercase header names.

TLS Requirements on Hyperforce

Minimum TLS version: TLS 1.0 and TLS 1.1 have been disabled on Hyperforce since March 2020. TLS 1.2 is the minimum supported version. TLS 1.3 is also supported. 

SNI requirement: Server Name Indication (SNI) is required for all connections to custom domain hostnames (any hostname that is not *.my.salesforce.com). Clients that do not send the SNI extension in the TLS ClientHello can receive a handshake failure.

 

Does Hyperforce support IPv6?

Hyperforce currently uses IPv4 for general commercial customer traffic. IPv6 support is being rolled out in stages: Government Cloud customers will receive IPv6 support first (2026), with commercial org support planned no earlier than 2027. Customers will receive at least 30 days' advance notice before IPv6 is enabled on their org. If you are a Government Cloud customer on the IPv6 track, ensure your firewall and allowlist configuration explicitly includes both IPv4 and IPv6 address blocks from the Hyperforce IP JSON file. For all other commercial customers, IPv4 allowlisting remains the current requirement.

No action is required from customers at this time. When IPv6 is enabled for your org, Salesforce will communicate the change through the standard Trust and instance notification channels.

If you have received notification that your org is on the IPv6 track, you must update your firewall and IP allowlist to include both IPv4 and IPv6 address blocks before the cutover date. 

Are there unique IP ranges for products on Hyperforce? If so, where can I find them

Because of the dynamic nature of cloud environments, Salesforce recommends using mTLS as described in Preferred Alternatives to IP Allowlisting on Hyperforce, rather than IP allowlists. For customers who must use IP allowlists, Hyperforce public IPs are available for download in JSON format at the URL: https://ip-ranges.salesforce.com/ip-ranges.json. This list contains the full set of IP addresses for outbound traffic originating from Hyperforce and going to third-party infrastructure, such as customers’ networks. It also includes IPs for inbound traffic to Hyperforce from external sources. See Hyperforce IPs to Allow - Sales, Service, Industries, and Tableau Clouds. These IPs are not for email, Marketing Cloud, Commerce Cloud, or Slack. If you are a Government Cloud Plus customer, see IP Addresses to Allow for Government Cloud Plus.
     

Is VPC peering available on Hyperforce?

For a private connection between virtual private clouds (VPCs) on AWS, use Salesforce Private Connect, which is built on AWS PrivateLink. This service provides private connectivity without exposing your data to the public internet. For a private connection on Hyperforce on GCP, Salesforce recommends contacting your telecom service provider to implement Google’s Verified Peering Provider (VPP). Salesforce plans to offer a product equivalent to Private Connect for Hyperforce on GCP in the future, subject to our Safe Harbor disclosures.

Salesforce Express Connect (SEC) Compatibility

Salesforce Express Connect (SEC) is not compatible with Hyperforce. SEC is a CSP-brokered private circuit service that connects to Salesforce’s classic (non-Hyperforce) datacenters. For Hyperforce customers who require a dedicated private connection, the supported alternatives are:

AWS Direct Connect — customer-managed dedicated AWS circuit to Hyperforce. See KB Set Up AWS Direct Connect (DX) for Hyperforce for setup guidance.
Salesforce Private Connect — built on AWS PrivateLink. Available for AWS-hosted Hyperforce orgs. See KB Secure Cross-Cloud Integrations with Private Connect.
 

 

Knowledge 기사 번호

000795010

 
로드 중
Salesforce Help | Article