> For the complete documentation index, see [llms.txt](https://docs.pushpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pushpulse.com/platform/it-configuration-instructions.md). # IT Configuration Instructions Firewall Rules **IPs and Domain Names** Unfortunately it is impossible for PushPulse to publish a set of IP addresses for the cloud based service as our service is elastic and IP addresses are reassigned dynamically as a normal part of our service. You may also have to allow list the following addresses to ensure the device is able to communicate to your corporate network: \*.pushpulse.com\ \*.ably.io\ \*.ably-realtime.com The Apps communicate via https, therefore port 443 must be open. **Email Notifications and Alerts**\ To be sure our emails always make it to your inbox, please add the following emails to your email allow list.\ \ \*@pushpulse.com\ \*@\*.pushpulse.com\ \ \
Push Notifications the following ports must be open so that the PushPulse apps can receive push notifications: Android: Ports 5228, 5229, and 5230 iOS: Ports 443 and 5223 For iOS, the Apple Push Notification Servers (APNS) use load balancing. So your devices won't always connect to the same public IP address for notifications. It's best to allow access to these ports on the entire 17.0.0.0/8 address block, which is assigned to Apple. For more information see . For Android, Google Cloud Management (GCM) doesn't provide specific IPs. So you should allow your firewall to accept outgoing connections to all IP addresses contained in the IP blocks listed in Google's ASN of 15169. For more information see