This article describes the usage and verification methods for various IP addresses in B2C Commerce environments. It covers outbound IPs for external communications, Business Manager, email sending sources, and storefront (CDN) IPs.
When communicating from the B2C Commerce environment to external systems (such as service calls), the "POD Outgoing IP address" is used as the source IP address. Use these addresses when allowing traffic from B2C Commerce in the receiving side's firewall settings.
Refer to the following Knowledge Articles for the list of POD Outgoing IP addresses:
The hyphenated hostname used for the Business Manager URL (e.g., production-ap01-example.demandware.net) is routed through the Cloudflare CDN, so it resolves to a Cloudflare IP address.
Specific IP addresses are managed by Cloudflare and can be verified using nslookup or dig commands. Refer to the following for verification methods and IP address ranges:
A fixed IP address is assigned to the Business Manager hostname format, which uses periods as separators (e.g., production.ap01.example.demandware.net). This IP address is used as the source IP address when sending emails from the instance using the Mail.send() method.
Refer to the following Knowledge Article for details:
For storefronts where the embedded CDN is enabled (such as in Production environments), the CNAME record for the site's custom domain (e.g., www.example.com) points to the embedded CDN provider's (Cloudflare) domain. Therefore, the resolved IP address will be a dynamic IP address from Cloudflare.
You can verify this IP address using nslookup or dig commands.
Example:
$ dig +noall +answer www.example.com
www.example.com. 300 IN CNAME commcloud.prod-abcd-example-com.cc-ecdn.net.
commcloud.prod-abcd-example-com.cc-ecdn.net. 300 IN A 103.21.244.1
Note: The above is an example. This applies only when an external CDN is not configured in front of the B2C Commerce embedded CDN.
Refer to the following external document for Cloudflare IP address ranges:
005232538

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.