# IP Address Lists # Google # IP ranges that Google makes available to users on the internet ### Unique `ipv4Prefix` values: 8.8.4.0/24 8.8.8.0/24 8.34.208.0/20 8.35.192.0/20 23.236.48.0/20 23.251.128.0/19 34.0.0.0/15 34.2.0.0/16 34.3.0.0/23 34.3.3.0/24 34.3.4.0/24 34.3.8.0/21 34.3.16.0/20 34.3.32.0/19 34.3.64.0/18 34.4.0.0/14 34.8.0.0/13 34.16.0.0/12 34.32.0.0/11 34.64.0.0/10 34.128.0.0/10 35.184.0.0/13 35.192.0.0/14 35.196.0.0/15 35.198.0.0/16 35.199.0.0/17 35.199.128.0/18 35.200.0.0/13 35.208.0.0/12 35.224.0.0/12 35.240.0.0/13 57.140.192.0/18 64.15.112.0/20 64.233.160.0/19 66.22.228.0/23 66.102.0.0/20 66.249.64.0/19 70.32.128.0/19 72.14.192.0/18 74.125.0.0/16 104.154.0.0/15 104.196.0.0/14 104.237.160.0/19 107.167.160.0/19 107.178.192.0/18 108.59.80.0/20 108.170.192.0/18 108.177.0.0/17 130.211.0.0/16 136.22.160.0/20 136.22.176.0/21 136.22.184.0/23 136.22.186.0/24 136.124.0.0/15 142.250.0.0/15 146.148.0.0/17 152.65.208.0/22 152.65.214.0/23 152.65.218.0/23 152.65.222.0/23 152.65.224.0/19 162.120.128.0/17 162.216.148.0/22 162.222.176.0/21 172.110.32.0/21 172.217.0.0/16 172.253.0.0/16 173.194.0.0/16 173.255.112.0/20 192.158.28.0/22 192.178.0.0/15 193.186.4.0/24 199.36.154.0/23 199.36.156.0/24 199.192.112.0/22 199.223.232.0/21 207.223.160.0/20 208.65.152.0/22 208.68.108.0/22 208.81.188.0/22 208.117.224.0/19 209.85.128.0/17 216.58.192.0/19 216.73.80.0/20 216.239.32.0/19 ### Unique `ipv6Prefix` values: 2001:4860::/32 2404:6800::/32 2404:f340::/32 2600:1900::/28 2605:ef80::/32 2606:40::/32 2606:73c0::/32 2607:1c0:241:40::/60 2607:1c0:300::/40 2607:f8b0::/32 2620:11a:a000::/40 2620:120:e000::/40 2800:3f0::/32 2a00:1450::/32 2c0f:fb50::/32 # Global and regional external IP address ranges for customers' Google Cloud resources \- \*\*Sync Token\*\*: 1729973139818 \- \*\*Creation Time\*\*: 2024-10-26T13:05:39.818865 \### Prefixes \#### Africa-South1 \- \*\*IPv4 Prefixes\*\*: \- 34.1.208.0/20 \- 34.35.0.0/16 \- 34.152.86.0/23 \- 34.177.50.0/23 \- 34.80.0.0/15 \- \*\*IPv6 Prefix\*\*: 2600:1900:8000::/44 \#### Asia-East1 \- \*\*IPv4 Prefixes\*\*: \- 34.80.0.0/15 \- 34.137.0.0/16 \- 35.185.128.0/19 \- 35.185.160.0/20 \- 35.187.144.0/20 \- 35.189.160.0/19 \- 35.194.128.0/17 \- 35.201.128.0/17 \- 35.206.192.0/18 \- 35.220.32.0/21 \- 35.221.128.0/17 \- 35.229.128.0/17 \- 35.234.0.0/18 \- 35.235.16.0/20 \- 35.236.128.0/18 \- 35.242.32.0/21 \- 104.155.192.0/19 \- 104.155.224.0/20 \- 104.199.128.0/18 \- 104.199.192.0/19 \- 104.199.224.0/20 \- 104.199.242.0/23 \- 104.199.244.0/22 \- 104.199.248.0/21 \- 107.167.176.0/20 \- 130.211.240.0/20 \- \*\*IPv6 Prefix\*\*: 2600:1900:4030::/44 \#### Asia-East2 \- \*\*IPv4 Prefixes\*\*: \- 34.92.0.0/16 \- 34.96.128.0/17 \- 34.104.88.0/21 \- 34.124.24.0/21 \- 34.150.0.0/17 \- 35.215.128.0/18 \- 35.220.27.0/24 \- 35.220.128.0/17 \- 35.241.64.0/18 \- 35.242.27.0/24 \- 35.243.8.0/21 \- \*\*IPv6 Prefix\*\*: 2600:1900:41a0::/44 \#### Asia-Northeast1 \- \*\*IPv4 Prefixes\*\*: \- 34.84.0.0/16 \- 34.85.0.0/17 \- 34.104.62.0/23 \- 34.104.128.0/17 \- 34.127.190.0/23 \- 34.146.0.0/16 \- 34.157.64.0/20 \- 34.157.164.0/22 \- 34.157.192.0/20 \- 35.187.192.0/19 \- 35.189.128.0/19 \- 35.190.224.0/20 \- 35.194.96.0/19 \- 35.200.0.0/17 \- 35.213.0.0/17 \- 35.220.56.0/22 \- 35.221.64.0/18 \- 35.230.240.0/20 \- 35.242.56.0/22 \- 35.243.64.0/18 \- 104.198.80.0/20 \- 104.198.112.0/20 \- \*\*IPv6 Prefix\*\*: 2600:1900:4050::/44 \#### Asia-Northeast2 \- \*\*IPv4 Prefixes\*\*: \- 34.97.0.0/16 \- 34.104.49.0/24 \- 34.127.177.0/24 \- 35.217.128.0/17 \- 35.220.45.0/24 \- 35.242.45.0/24 \- 35.243.56.0/21 \- \*\*IPv6 Prefix\*\*: 2600:1900:41d0::/44 \#### Asia-Northeast3 \- \*\*IPv4 Prefixes\*\*: \- 34.0.96.0/19 \- 34.22.64.0/19 \- 34.22.96.0/20 \- 34.47.64.0/18 \- 34.50.0.0/18 \- 34.64.32.0/19 \- 34.64.64.0/22 \- 34.64.68.0/22 \- 34.64.72.0/21 \- 34.64.80.0/20 \- 34.64.96.0/19 \- 34.64.128.0/22 \- 34.64.132.0/22 \- 34.64.136.0/21 \- 34.64.144.0/20 \- 34.64.160.0/19 \- 34.64.192.0/18 \- 35.216.0.0/17 \- \*\*IPv6 Prefix\*\*: 2600:1901:8180::/44 \#### Asia-South1 \- \*\*IPv4 Prefixes\*\*: \- 34.0.227.0/24 \- 34.47.128.0/17 \- 34.93.0.0/16 \- 34.100.128.0/17 \- 34.104.108.0/23 \- 34.124.44.0/23 \- 34.152.64.0/22 \- 34.153.58.0/23 \- 34.153.250.0/23 \- 34.157.87.0/24 \- 34.157.215.0/24 \- 34.177.32.0/22 \- 35.200.128.0/17 \- 35.201.41.0/24 \- 35.207.192.0/18 \- 35.220.42.0/24 \- 35.234.208.0/20 \- 35.242.42.0/24 \- 35.244.0.0/18 \- \*\*IPv6 Prefix\*\*: 2600:1900:40a0::/44 \#### Asia-South2 \- \*\*IPv4 Prefixes\*\*: \- 34.0.0.0/20 \- 34.104.120.0/23 \- 34.124.56.0/23 \- 34.126.208.0/20 \- 34.131.0.0/16 \- 34.153.32.0/24 \- 34.153.224.0/24 \- \*\*IPv6 Prefix\*\*: 2600:1900:41b0::/44 \#### Asia-Southeast1 \- \*\*IPv4 Prefixes\*\*: \- 34.1.128.0/20 \- 34.1.192.0/20 \- 34.2.16.0/20 \- 34.21.128.0/17 \- 34.87.0.0/17 \- 34.87.128.0/18 \- 34.104.58.0/23 \- 34.104.106.0/23 \- 34.124.42.0/23 \- 34.124.128.0/17 \- 34.126.64.0/18 \- 34.126.128.0/18 \- 34.128.44.0/23 \- 34.128.60.0/23 \- 34.142.128.0/17 \- 34.143.128.0/17 \- 34.153.40.0/23 \- 34.153.232.0/23 \- 34.157.82.0/23 \- 34.157.88.0/23 \- 34.157.210.0/23 \- 35.185.176.0/20 \- 35.186.144.0/20 \- 35.187.224.0/19 \- 35.197.128.0/19 \- 35.198.192.0/18 \- 35.213.128.0/18 \- 35.220.24.0/23 \- 35.234.192.0/20 \- 35.240.128.0/17 \- 35.242.24.0/23 \- 35.247.128.0/18 \- \*\*IPv6 Prefix\*\*: 2600:1900:4080::/44 \#### Asia-Southeast2 \- \*\*IPv4 Prefixes\*\*: \- 34.34.216.0/21 \- 34.50.64.0/18 \- 34.101.18.0/24 \- 34.101.20.0/22 \- 34.101.24.0/22 \- 34.101.32.0/19 \- 34.101.64.0/18 \- 34.101.128.0/17 \- 34.128.64.0/18 \- 34.152.68.0/24 \- 34.153.44.0/24 \- 34.153.236.0/24 \- 34.157.254.0/24 \- 35.219.0.0/17 \- \*\*IPv6 Prefix\*\*: 2600:1901:8170::/44 \#### Australia-Southeast1 \- \*\*IPv4 Prefixes\*\*: \- 34.40.128.0/17 \- 34.87.192.0/18 \- 34.104.104.0/23 \- 34.116.64.0/18 \- 34.124.40.0/23 \- 34.128.36.0/24 \- 34.128.48.0/24 \- 34.151.64.0/18 \- 34.151.128.0/18 \- 35.189.0.0/18 \- 35.197.160.0/19 \- 35.201.0.0/19 \- 35.213.192.0/18 \- 35.220.41.0/24 \- 35.234.224.0/20 \- 35.242.41.0/24 \- 35.244.64.0/18 \- \*\*IPv6 Prefix\*\*: 2600:1900:40b0::/44 \#### Australia-Southeast2 \- \*\*IPv4 Prefixes\*\*: \- 34.0.16.0/20 \- 34.1.176.0/20 \- 34.104.122.0/23 \- 34.124.58.0/23 \- 34.126.192.0/20 \- 34.129.0.0/16 \- \*\*IPv6 Prefix\*\*: 2600:1900:41c0::/44 \#### Europe-Central2 \- \*\*IPv4 Prefixes\*\*: \- 34.0.240.0/20 \- 34.104.116.0/22 \- 34.116.128.0/17 \- 34.118.0.0/17 \- 34.124.52.0/22 \- \*\*IPv6 Prefix\*\*: 2600:1900:4140::/44 \#### Europe-North1 \- \*\*IPv4 Prefixes\*\*: \- 34.88.0.0/16 \- 34.104.96.0/21 \- 34.124.32.0/21 \- 35.203.232.0/21 \- 35.217.0.0/18 \- 35.220.26.0/24 \- 35.228.0.0/16 \- 35.242.26.0/24 \- \*\*IPv6 Prefix\*\*: 2600:1900:4150::/44 \#### Europe-North2 \- \*\*IPv4 Prefixes\*\*: \- 34.51.128.0/17 \- 34.153.46.0/23 \- 34.153.238.0/23 \- \*\*IPv6 Prefix\*\*: 2600:1900:42a0::/44 \#### Europe-Southwest1 \- \*\*IPv4 Prefixes\*\*: \- 34.0.192.0/19 \- 34.157.44.0/23 \- 34.157.172.0/23 \- 34.164.0.0/16 \- 34.175.0.0/16 \- \*\*IPv6 Prefix\*\*: 2600:1901:8100::/44 \#### Europe-West1 \- \*\*IPv4 Prefixes\*\*: \- 8.34.208.0/23 \- 8.34.211.0/24 \- 8.34.220.0/22 \- 23.251.128.0/20 \- 34.14.0.0/17 \- 34.22.112.0/20 \- 34.22.128.0/17 \- 34.34.128.0/18 \- 34.38.0.0/16 \- 34.52.128.0/17 \- 34.53.128.0/17 \- 34.62.0.0/16 \- 34.76.0.0/14 \- 34.118.254.0/23 \- 34.140.0.0/16 \- 35.187.0.0/17 \- 35.187.160.0/19 \- 35.189.192.0/18 \- 35.190.192.0/19 \- 35.195.0.0/16 \- 35.205.0.0/16 \- 35.206.128.0/18 \- 35.210.0.0/16 \- 35.220.96.0/19 \- 35.233.0.0/17 \- 35.240.0.0/17 \- 35.241.128.0/17 \- 35.242.64.0/19 \- 104.155.0.0/17 \- 104.199.0.0/18 \- 104.199.66.0/23 \- 104.199.68.0/22 \- 104.199.72.0/21 \- 104.199.80.0/20 \- 104.199.96.0/20 \- 130.211.48.0/20 \- 130.211.64.0/19 \- 130.211.96.0/20 \- 146.148.2.0/23 \- 146.148.4.0/22 \- 146.148.8.0/21 \- 146.148.16.0/20 \- 146.148.112.0/20 \- 192.158.28.0/22 \- \*\*IPv6 Prefix\*\*: 2600:1900:4010::/44 \#### Europe-West10 \- \*\*IPv4 Prefixes\*\*: \- 34.1.160.0/20 \- 34.32.0.0/17 \- 34.152.80.0/23 \- 34.177.36.0/23 \- \*\*IPv6 Prefix\*\*: 2600:1901:81f0::/44 \#### Europe-West12 \- \*\*IPv4 Prefixes\*\*: \- 34.1.144.0/20 \- 34.17.0.0/16 \- 34.157.124.0/23 \- 34.157.250.0/23 \- \*\*IPv6 Prefix\*\*: 2600:1901:81b0::/44 \#### Europe-West2 \- \*\*IPv4 Prefixes\*\*: \- 34.39.0.0/17 \- 34.50.192.0/18 \- 34.89.0.0/17 \- 34.105.128.0/17 \- 34.127.186.0/23 \- 34.128.52.0/22 \- 34.142.0.0/17 \- 34.147.128.0/17 \- 34.153.128.0/18 \- 34.157.36.0/22 \- 34.157.40.0/22 \- 34.157.168.0/22 \- 35.189.64.0/18 \- 35.197.192.0/18 \- 35.203.210.0/23 \- 35.203.212.0/22 \- 35.203.216.0/22 \- 35.214.0.0/17 \- 35.220.20.0/22 \- 35.230.128.0/19 \- 35.234.128.0/19 \- 35.235.48.0/20 \- 35.242.20.0/22 \- 35.242.128.0/18 \- 35.246.0.0/17 \- \*\*IPv6 Prefix\*\*: 2600:1900:40c0::/44 \#### Europe-West3 \- \*\*IPv4 Prefixes\*\*: \- 34.0.224.0/24 \- 34.0.226.0/24 \- 34.40.0.0/17 \- 34.89.128.0/17 \- 34.104.112.0/23 \- 34.107.0.0/17 \- 34.118.244.0/22 \- 34.124.48.0/23 \- 34.141.0.0/17 \- 34.157.48.0/20 \- 34.157.176.0/20 \- 34.159.0.0/16 \- 34.179.0.0/16 \- 34.181.0.0/17 \- 35.198.64.0/18 \- 35.198.128.0/18 \- 35.207.64.0/18 \- 35.207.128.0/18 \- 35.220.18.0/23 \- 35.234.64.0/18 \- 35.235.32.0/20 \- 35.242.18.0/23 \- 35.242.192.0/18 \- 35.246.128.0/17 \- \*\*IPv6 Prefix\*\*: 2600:1900:40d0::/44 \#### Europe-West4 \- \*\*IPv4 Prefixes\*\*: \- 34.1.224.0/19 \- 34.12.0.0/16 \- 34.13.128.0/17 \- 34.32.128.0/17 \- 34.34.0.0/17 \- 34.90.0.0/15 \- 34.104.126.0/23 \- 34.124.62.0/23 \- 34.141.128.0/17 \- 34.147.0.0/17 \- 34.153.45.0/24 \- 34.153.237.0/24 \- 34.157.80.0/23 \- 34.157.92.0/22 \- 34.157.208.0/23 \- 34.157.220.0/22 \- 35.204.0.0/16 \- 35.214.128.0/17 \- 35.220.16.0/23 \- 35.234.160.0/20 \- 35.242.16.0/23 \- \*\*IPv6 Prefix\*\*: 2600:1900:4060::/44 \#### Europe-West6 \- \*\*IPv4 Prefixes\*\*: \- 34.65.0.0/16 \- 34.104.110.0/23 \- 34.124.46.0/23 \- 35.216.128.0/17 \- 35.220.44.0/24 \- 35.235.216.0/21 \- 35.242.44.0/24 \- \*\*IPv6 Prefix\*\*: 2600:1900:4160::/44 \#### Europe-West8 \- \*\*IPv4 Prefixes\*\*: \- 34.0.160.0/19 \- 34.153.38.0/24 \- 34.153.230.0/24 \- 34.154.0.0/16 \- 34.157.8.0/23 \- 34.157.121.0/24 \- 34.157.136.0/23 \- 34.157.249.0/24 \- 35.219.224.0/19 \- \*\*IPv6 Prefix\*\*: 2600:1901:8110::/44 \#### Europe-West9 \- \*\*IPv4 Prefixes\*\*: \- 34.1.0.0/20 \- 34.155.0.0/16 \- 34.157.12.0/22 \- 34.157.140.0/22 \- 34.163.0.0/16 \- \*\*IPv6 Prefix\*\*: 2600:1901:8120::/44 \#### Global \- \*\*IPv4 Prefixes\*\*: \- 34.8.0.0/16 \- 34.36.0.0/16 \- 34.49.0.0/16 \- 34.54.0.0/16 \- 34.95.64.0/18 \- 34.96.64.0/18 \- 34.98.64.0/18 \- 34.102.128.0/17 \- 34.104.27.0/24 \- 34.107.128.0/17 \- 34.110.128.0/17 \- 34.111.0.0/16 \- 34.116.0.0/21 \- 34.117.0.0/16 \- 34.120.0.0/16 \- 34.128.128.0/18 \- 34.144.192.0/18 \- 34.149.0.0/16 \- 34.160.0.0/16 \- 35.186.192.0/18 \- 35.190.0.0/18 \- 35.190.64.0/19 \- 35.190.112.0/20 \- 35.201.64.0/18 \- 35.227.192.0/18 \- 35.241.0.0/18 \- 35.244.128.0/17 \- 107.178.240.0/20 \- 130.211.4.0/22 \- 130.211.8.0/21 \- 130.211.16.0/20 \- 130.211.32.0/20 \- \*\*IPv6 Prefix\*\*: 2600:1901::/48 \#### ME-Central1 \- \*\*IPv4 Prefixes\*\*: \- 34.1.32.0/20 \- 34.18.0.0/16 \- 34.157.126.0/23 \- 34.157.252.0/23 \- \*\*IPv6 Prefix\*\*: 2600:1901:81c0::/44 \#### ME-Central2 \- \*\*IPv4 Prefixes\*\*: \- 34.1.48.0/20 \- 34.152.84.0/23 \- 34.166.0.0/16 \- 34.177.48.0/23 \- \*\*IPv6 Prefix\*\*: 2600:1900:5400::/44 \#### ME-West1 \- \*\*IPv4 Prefixes\*\*: \- 34.0.64.0/19 \- 34.157.90.0/23 \- 34.157.216.0/23 \- 34.165.0.0/16 \- 34.19.128.0/17 \- \*\*IPv6 Prefix\*\*: 2600:1901:8160::/44 \#### NorthAmerica-Northeast1 \- \*\*IPv4 Prefixes\*\*: \- 34.20.0.0/17 \- 34.47.0.0/18 \- 34.95.0.0/18 \- 34.104.76.0/22 \- 34.118.128.0/18 \- 34.124.12.0/22 \- 34.128.37.0/24 \- 34.128.42.0/23 \- 34.128.49.0/24 \- 34.128.58.0/23 \- 34.152.0.0/18 \- 35.203.0.0/17 \- 35.215.0.0/18 \- 35.220.43.0/24 \- 35.234.240.0/20 \- 35.242.43.0/24 \- \*\*IPv6 Prefix\*\*: 2600:1900:40e0::/44 \#### NorthAmerica-Northeast2 \- \*\*IPv4 Prefixes\*\*: \- 34.0.32.0/20 \- 34.104.114.0/23 \- 34.124.50.0/23 \- 34.124.112.0/20 \- 34.130.0.0/16 \- 34.152.69.0/24 \- 34.157.255.0/24 \- \*\*IPv6 Prefix\*\*: 2600:1900:41e0::/44 \#### NorthAmerica-South1 \- \*\*IPv4 Prefixes\*\*: \- 34.2.0.0/20 \- 34.51.0.0/17 \- 34.153.42.0/23 \- 34.153.234.0/23 \- 34.39.128.0/17 \- \*\*IPv6 Prefix\*\*: 2600:1900:4290::/44 \#### SouthAmerica-East1 \- \*\*IPv4 Prefixes\*\*: \- 34.95.128.0/17 \- 34.104.80.0/21 \- 34.124.16.0/21 \- 34.151.0.0/18 \- 34.151.192.0/18 \- 35.198.0.0/18 \- 35.199.64.0/18 \- 35.215.192.0/18 \- 35.220.40.0/24 \- 35.235.0.0/20 \- 35.242.40.0/24 \- 35.247.192.0/18 \- \*\*IPv6 Prefix\*\*: 2600:1900:40f0::/44 \#### SouthAmerica-West1 \- \*\*IPv4 Prefixes\*\*: \- 34.0.48.0/20 \- 34.104.50.0/23 \- 34.127.178.0/23 \- 34.153.33.0/24 \- 34.153.225.0/24 \- 34.176.0.0/16 \- \*\*IPv6 Prefix\*\*: 2600:1901:4010::/44 \#### US-Central1 \- \*\*IPv4 Prefixes\*\*: \- 8.34.210.0/24 \- 8.34.212.0/22 \- 8.34.216.0/22 \- 8.35.192.0/21 \- 23.236.48.0/20 \- 23.251.144.0/20 \- 34.0.225.0/24 \- 34.9.0.0/16 \- 34.10.0.0/16 \- 34.13.68.0/22 \- 34.16.0.0/17 \- 34.27.0.0/16 \- 34.28.0.0/14 \- 34.33.0.0/16 \- 34.41.0.0/16 \- 34.42.0.0/16 \- 34.44.0.0/15 \- 34.46.0.0/16 \- 34.55.0.0/16 \- 34.56.0.0/14 \- 34.60.0.0/15 \- 34.63.0.0/16 \- 34.66.0.0/15 \- 34.68.0.0/14 \- 34.72.0.0/16 \- 34.118.200.0/21 \- 34.121.0.0/16 \- 34.122.0.0/15 \- 34.128.32.0/22 \- 34.132.0.0/14 \- 34.136.0.0/16 \- 34.153.48.0/21 \- 34.153.240.0/21 \- 34.157.84.0/23 \- 34.157.96.0/20 \- 34.157.212.0/23 \- 34.157.224.0/20 \- 34.170.0.0/15 \- 34.172.0.0/15 \- 34.177.52.0/22 \- 35.184.0.0/16 \- 35.188.0.0/17 \- 35.188.128.0/18 \- 35.188.192.0/19 \- 35.192.0.0/15 \- 35.194.0.0/18 \- 35.202.0.0/16 \- 35.206.64.0/18 \- 35.208.0.0/15 \- 35.220.64.0/19 \- 35.222.0.0/15 \- 35.224.0.0/15 \- 35.226.0.0/16 \- 35.232.0.0/16 \- 35.238.0.0/15 \- 35.242.96.0/19 \- 104.154.16.0/20 \- 104.154.32.0/19 \- 104.154.64.0/19 \- 104.154.96.0/20 \- 104.154.113.0/24 \- 104.154.114.0/23 \- 104.154.116.0/22 \- 104.154.120.0/23 \- 104.154.128.0/17 \- 104.155.128.0/18 \- 104.197.0.0/16 \- 104.198.16.0/20 \- 104.198.32.0/19 \- 104.198.64.0/20 \- 104.198.128.0/17 \- 107.178.208.0/20 \- 108.59.80.0/21 \- 130.211.112.0/20 \- 130.211.128.0/18 \- 130.211.192.0/19 \- 130.211.224.0/20 \- 146.148.32.0/19 \- 146.148.64.0/19 \- 146.148.96.0/20 \- 162.222.176.0/21 \- 173.255.112.0/21 \- 199.192.115.0/24 \- 199.223.232.0/22 \- 199.223.236.0/24 \- \*\*IPv6 Prefix\*\*: 2600:1900:4000::/44 \#### US-Central2 \- \*\*IPv4 Prefixes\*\*: \- 34.22.0.0/19 \- 35.186.0.0/17 \- 35.186.128.0/20 \- 35.206.32.0/19 \- 35.220.46.0/24 \- 35.242.46.0/24 \- 107.167.160.0/20 \- 108.59.88.0/21 \- 173.255.120.0/21 \- \*\*IPv6 Prefix\*\*: 2600:1900:4070::/44 \#### US-East1 \- \*\*IPv4 Prefixes\*\*: \- 34.23.0.0/16 \- 34.24.0.0/15 \- 34.26.0.0/16 \- 34.73.0.0/16 \- 34.74.0.0/15 \- 34.98.128.0/21 \- 34.112.0.0/16 \- 34.118.250.0/23 \- 34.138.0.0/15 \- 34.148.0.0/16 \- 34.152.72.0/21 \- 34.177.40.0/21 \- 35.185.0.0/17 \- 35.190.128.0/18 \- 35.196.0.0/16 \- 35.207.0.0/18 \- 35.211.0.0/16 \- 35.220.0.0/20 \- 35.227.0.0/17 \- 35.229.16.0/20 \- 35.229.32.0/19 \- 35.229.64.0/18 \- 35.231.0.0/16 \- 35.237.0.0/16 \- 35.242.0.0/20 \- 35.243.128.0/17 \- 104.196.0.0/18 \- 104.196.65.0/24 \- 104.196.66.0/23 \- 104.196.68.0/22 \- 104.196.96.0/19 \- 104.196.128.0/18 \- 104.196.192.0/19 \- 162.216.148.0/22 \- \*\*IPv6 Prefix\*\*: 2600:1900:4020::/44 \#### US-East4 \- \*\*IPv4 Prefixes\*\*: \- 34.11.0.0/17 \- 34.21.0.0/17 \- 34.48.0.0/16 \- 34.85.128.0/17 \- 34.86.0.0/16 \- 34.104.60.0/23 \- 34.104.124.0/23 \- 34.118.252.0/23 \- 34.124.60.0/23 \- 34.127.188.0/23 \- 34.145.128.0/17 \- 34.150.128.0/17 \- 34.157.0.0/21 \- 34.157.16.0/20 \- 34.157.128.0/21 \- 34.157.144.0/20 \- 34.181.128.0/17 \- 34.182.128.0/17 \- 35.186.160.0/19 \- 35.188.224.0/19 \- 35.194.64.0/19 \- 35.199.0.0/18 \- 35.212.0.0/17 \- 35.220.60.0/22 \- 35.221.0.0/18 \- 35.230.160.0/19 \- 35.234.176.0/20 \- 35.236.192.0/18 \- 35.242.60.0/22 \- 35.243.40.0/21 \- 35.245.0.0/16 \- \*\*IPv6 Prefix\*\*: 2600:1900:4090::/44 \#### US-East5 \- \*\*IPv4 Prefixes\*\*: \- 34.1.16.0/20 \- 34.157.32.0/22 \- 34.157.160.0/22 \- 34.162.0.0/16 \- \*\*IPv6 Prefix\*\*: 2600:1901:8130::/44 \#### US-East7 \- \*\*IPv4 Prefixes\*\*: \- 34.104.56.0/23 \- 34.127.184.0/23 \- 34.161.0.0/16 \- 35.206.10.0/23 \- \*\*IPv6 Prefix\*\*: 2600:1901:8150::/44 \#### US-South1 \- \*\*IPv4 Prefixes\*\*: \- 34.0.128.0/19 \- 34.157.46.0/23 \- 34.157.174.0/23 \- 34.174.0.0/16 \- \*\*IPv6 Prefix\*\*: 2600:1901:8140::/44 \#### US-West1 \- \*\*IPv4 Prefixes\*\*: \- 34.11.128.0/17 \- 34.19.0.0/17 \- 34.53.0.0/17 \- 34.82.0.0/15 \- 34.105.0.0/17 \- 34.118.192.0/21 \- 34.127.0.0/17 \- 34.145.0.0/17 \- 34.157.112.0/21 \- 34.157.240.0/21 \- 34.168.0.0/15 \- 34.182.0.0/17 \- 35.185.192.0/18 \- 35.197.0.0/17 \- 35.199.144.0/20 \- 35.199.160.0/19 \- 35.203.128.0/18 \- 35.212.128.0/17 \- 35.220.48.0/21 \- 35.227.128.0/18 \- 35.230.0.0/17 \- 35.233.128.0/17 \- 35.242.48.0/21 \- 35.243.32.0/21 \- 35.247.0.0/17 \- 104.196.224.0/19 \- 104.198.0.0/20 \- 104.198.96.0/20 \- 104.199.112.0/20 \- \*\*IPv6 Prefix\*\*: 2600:1900:4040::/44 \#### US-West2 \- \*\*IPv4 Prefixes\*\*: \- 34.20.128.0/17 \- 34.94.0.0/16 \- 34.102.0.0/17 \- 34.104.64.0/21 \- 34.108.0.0/16 \- 34.118.248.0/23 \- 34.124.0.0/21 \- 35.215.64.0/18 \- 35.220.47.0/24 \- 35.235.64.0/18 \- 35.236.0.0/17 \- 35.242.47.0/24 \- 35.243.0.0/21 \- \*\*IPv6 Prefix\*\*: 2600:1900:4120::/44 \#### US-West3 \- \*\*IPv4 Prefixes\*\*: \- 34.22.32.0/19 \- 34.104.52.0/24 \- 34.106.0.0/16 \- 34.127.180.0/24 \- 35.217.64.0/18 \- 35.220.31.0/24 \- 35.242.31.0/24 \- \*\*IPv6 Prefix\*\*: 2600:1900:4170::/44 \#### US-West4 \- \*\*IPv4 Prefixes\*\*: \- 34.16.128.0/17 \- 34.50.160.0/19 \- 34.104.72.0/22 \- 34.118.240.0/22 \- 34.124.8.0/22 \- 34.125.0.0/16 \- 35.219.128.0/18 \- \*\*IPv6 Prefix\*\*: 2600:1900:4180::/44 \#### US-West8 \- \*\*IPv4 Prefixes\*\*: \- 34.37.0.0/16 \- 34.128.46.0/23 \- 34.128.62.0/23 \- \*\*IPv6 Prefix\*\*: 2600:1900:4280::/44 # Mail Server IP Ranges # Mimecast - Email Security Cloud Gateway - Data Centers & URLs ## Considerations - When a user enters their email address into Mimecast's Administration Console or an API client, a global resource determines the user's parent account location. This resource provides a 302 redirect to the correct location, ensuring uninterrupted service. These endpoints are available at all Mimecast data centers. - Outbound HTTPS traffic from your network may be observed to an IP address outside your Mimecast region. To avoid disruption, allow outbound HTTPS connections to these locations. No email is transmitted using this method. - Your region may be somewhere other than where you are physically located. It is where your data is located. For example, a company with European offices may host its data in North America. - You must ensure that all connections are allowed access to the ports for the networks listed and mapped to the correct destination on your network. - To prevent disruption to your service, it's important to ensure that: - You allow connections to the appropriate ports from your region's entire Mimecast IP Ranges. - They are mapped through to the correct destination on your network. ## Global Application Resources ### Global Application URL
ApplicationURL
Administration Console[https://login.mimecast.com](https://login.mimecast.com/)
Mimecast Personal Portal[https://webmail.mimecast.com](https://webmail.mimecast.com/)
Mimecast API[https://api.mimecast.com](https://api.mimecast.com/)
Service Monitor[https://monitor.mimecast.com/Account/Login](https://monitor.mimecast.com/Account/Login)
Mimecast E2E, Customer Managed Migration [https://\*.mimecast.com](https://%2A.mimecast.com/)
### Protocol Connection Ports The following list shows the most common connection types and the general ports used for each protocol. Also included are the standard connection ports for Mimecast Applications:
ProtocolDefault PortUsage
Simple Mail Transfer Protocol (SMTP)25Send Connectors, SMTP Journaling, user application SMTP Services.
Post Office Protocol (POP3)110POP Journaling, user application POP Services.
Post Office Protocol Secure (POP3S)995
Lightweight Directory Access Protocol (LDAP)389Directory Synchronization
Lightweight Directory Access Protocol Secure (LDAPS)636
HyperText Transfer Protocol (HTTP)80Downloading Strip and Link attachments, Mimecast Synchronization Engine (MSE) with Office 365 hybrid environments. Mimecast for Outlook also authenticates using this port.
HyperText Transfer Protocol (HTTPS)443Access to the Administration Console, Mimecast Personal Portal, Mimecast Mobile, Mimecast for Outlook, and Mimecast Synchronization Engine, Mimecast E2E, Customer Managed Migration.
### Mimecast Website To ensure that your users can always log in to the Mimecast website, it is recommended to permit traffic to the Mimecast website IP ranges:
LocationIP AddressCIDRNetmask
Data Center 1146.101.202.134/32255.255.255.255
146.101.202.135/32255.255.255.255
Data Center 281.145.134.178/32255.255.255.255
81.145.134.173/32255.255.255.255
## Regional IP Addresses, Network Ranges, and Application URLs ### Europe (Excluding Germany) #### IP Addresses and Network Ranges
**Note:**When entering IP ranges, it is essential to note that Microsoft 365 limits the CIDR you can use on the Connection Filter (e.g., 205.139.110.0/23 or 185.58.84.0/22). We recommend breaking up the ranges so they end in/24 as a workaround.
NetworkIP Address RangeNetmask
193.7.204.0/24193.7.204.1to193.7.204.254255.255.255.0
193.7.205.0/24193.7.205.1to193.7.205.254255.255.255.0
195.130.217.0/24195.130.217.1to195.130.217.254255.255.255.0
91.220.42.0/2491.220.42.1to91.220.42.254255.255.255.0
185.58.84.0/24185.58.84.1to185.58.84.254255.255.255.0
185.58.85.0/24185.58.85.1to185.58.85.254255.255.255.0
185.58.86.0/24185.58.86.1to185.58.86.254255.255.255.0
185.58.87.0/24185.58.87.1to185.58.87.254255.255.255.0
207.82.80.0/24207.82.80.1to207.82.80.254255.255.255.0
#### IP Addresses/Network Ranges for Non-SPF Email Traffic Where messages are being sent from accounts with envelope addresses not registered as internal domains, Mimecast routes through separate ranges:
RegionIP Address Range 1IP Address Range 2
Europe (excluding Germany)185.58.87.40to185.58.87.49185.58.84.40to185.58.84.49
#### Application URLs
ApplicationURL
Administration Console[https://login-uk.mimecast.com/u/login?gta=administration](https://login-uk.mimecast.com/u/login?gta=administration)
Mimecast Personal Portal[https://webmail-uk.mimecast.com/m/portal/login/#/login](https://webmail-uk.mimecast.com/m/portal/login/#/login)
Mimecast API[https://eu-api.mimecast.com](https://eu-api.mimecast.com/)
Mimecast Secure Messaging Portal \*\*\*[https://login-uk.mimecast.com/m/secure](https://login-uk.mimecast.com/m/secure)
**Note:**\*\*\* The Mimecast Secure Messaging Portal URL should only be used by Mimecast customers. Non-Mimecast customers can access the portal by clicking the link in the notification message.
#### Targeted Threat Protection (TTP) Suppose you have integrations parsing messages for Mimecast-rewritten URLs or decoding Mimecast-rewritten URLs. In that case, these integrations must know Mimecast's Targeted Threat Protection URL patterns. Relevant integration types include SOAR, XDR, and custom scripts using the [Get Message Part](https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/ "https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/") or [Decode URL](https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/ "https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/") API endpoints.
RegionDestination Domain
Europe (excluding Germany)
[url.uk.m.mimecastprotect.com](http://url.uk.m.mimecastprotect.com/)
### Germany #### IP Addresses and Network Ranges
**Note:**When entering IP ranges, it is essential to note that Microsoft 365 limits the CIDR you can use on the Connection Filter (e.g., 205.139.110.0/23 or 185.58.84.0/22). We recommend breaking up the ranges so they end in/24 as a workaround.
NetworkIP Address RangeNetmask
194.104.108.0/24194.104.108.1to194.104.108.254255.255.255.0
194.104.109.0/24194.104.109.1to194.104.109.254255.255.255.0
194.104.110.0/24194.104.110.1to194.104.110.254255.255.255.0
194.104.111.0/24194.104.111.1to194.104.111.254255.255.255.0
147.28.34.0/24147.28.34.1to147.28.34.254255.255.255.0
147.28.35.0/24147.28.35.1to147.28.35.254255.255.255.0
51.163.158.0/2451.163.158.1to51.163.158.254255.255.255.0
51.163.159.0/2451.163.159.1to51.163.159.254255.255.255.0
62.140.7.0/2462.140.7.1to62.140.7.254255.255.255.0
62.140.10.0/2462.140.10.1to62.140.10.254255.255.255.0
#### IP Addresses/Network Ranges for Non-SPF Email Traffic Where messages are being sent from accounts with envelope addresses not registered as internal domains, Mimecast routes through separate ranges:
RegionIP Address Range 1IP Address Range 2
Germany (DE-Grid)51.163.159.40to51.163.159.4962.140.10.40to62.140.10.49
#### Application URLs
ApplicationURL
Administration Console[https://login-de.mimecast.com/u/login?gta=administration](https://login-de.mimecast.com/u/login?gta=administration)
Mimecast Personal Portal[https://webmail-de.mimecast.com/m/portal/login/#/login](https://webmail-de.mimecast.com/m/portal/login/#/login)
Mimecast API[https://de-api.mimecast.com](https://de-api.mimecast.com/)
Mimecast Secure Messaging Portal \*\*\*[https://login-de.mimecast.com/m/secure](https://login-de.mimecast.com/m/secure)
**Note:**\*\*\* The Mimecast Secure Messaging Portal URL should only be used by Mimecast customers. Non-Mimecast customers can access the portal by clicking the link in the notification message.
#### Targeted Threat Protection (TTP) Suppose you have integrations parsing messages for Mimecast-rewritten URLs or decoding Mimecast-rewritten URLs. In that case, these integrations must know Mimecast's Targeted Threat Protection URL patterns. Relevant integration types include SOAR, XDR, and custom scripts using the [Get Message Part](https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/ "https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/") or [Decode URL](https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/ "https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/") API endpoints.
RegionDestination Domain
Germany
[url.de.m.mimecastprotect.com](http://url.de.m.mimecastprotect.com/)
### United States of America #### IP Addresses and Network Ranges
**Note:** When entering IP ranges, it is essential to note that Microsoft 365 limits the CIDR you can use on the Connection Filter (e.g., 205.139.110.0/23 or 185.58.84.0/22). We recommend breaking up the ranges so they end in/24 as a workaround.
NetworkIP Address RangeNetmask
170.10.132.0/24170.10.132.1to170.10.132.254255.255.255.0
170.10.133.0/24170.10.133.1to170.10.133.254255.255.255.0
170.10.128.0/24170.10.128.1to170.10.128.254255.255.255.0
170.10.129.0/24170.10.129.1to170.10.129.254255.255.255.0
170.10.130.0/24170.10.130.1to170.10.130.254255.255.255.0
170.10.131.0/24170.10.131.1to170.10.131.254255.255.255.0
207.211.31.0/25207.211.31.1to207.211.31.127255.255.255.128
207.211.30.0/24207.211.30.1to207.211.30.254255.255.255.0
205.139.110.0/24205.139.110.1to205.139.110.254255.255.255.0
205.139.111.0/24205.139.111.1to205.139.111.254255.255.255.0
216.205.24.0/24216.205.24.1to216.205.24.254255.255.255.0
63.128.21.0/2463.128.21.1to63.128.21.254255.255.255.0
#### IP Addresses / Network Ranges for Non-SPF Email Traffic Where messages are being sent from accounts with envelope addresses not registered as internal domains, Mimecast routes through separate ranges.
Region
United States of America (US-Grid)207.211.30.40to207.211.30.49205.139.111.40to205.139.111.49
#### Application URLs
ApplicationURL
Administration Console[https://login-us.mimecast.com/u/login?gta=administration](https://login-us.mimecast.com/u/login?gta=administration)
Mimecast Personal Portal[https://webmail-us.mimecast.com/m/portal/login/#/login](https://webmail-us.mimecast.com/m/portal/login/#/login)
Mimecast API[https://us-api.mimecast.com](https://us-api.mimecast.com/)
Mimecast Secure Messaging Portal \*\*\*[https://login-us.mimecast.com/m/secure](https://login-us.mimecast.com/m/secure)
**Note:**\*\*\* The Mimecast Secure Messaging Portal URL should only be used by Mimecast customers. Non-Mimecast customers can access the portal by clicking the link in the notification message.
#### Targeted Threat Protection (TTP) Suppose you have integrations parsing messages for Mimecast-rewritten URLs or decoding Mimecast-rewritten URLs. In that case, these integrations must know Mimecast's Targeted Threat Protection URL patterns. Relevant integration types include SOAR, XDR, and custom scripts using the [Get Message Part](https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/ "https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/") or [Decode URL](https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/ "https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/") API endpoints.
RegionDestination Domain
United States of America (US-Grid)
[url.us.m.mimecastprotect.com](http://url.us.m.mimecastprotect.com/)
### United States of America (USB) #### IP Addresses and Network Ranges
**Note:**When entering IP ranges, it is essential to note that Microsoft 365 limits the CIDR you can use on the Connection Filter (e.g., 205.139.110.0/23 or 185.58.84.0/22). We recommend breaking up the ranges so they end in/24 as a workaround.
NetworkIP Address RangeNetmask
170.10.150.0/24170.10.150.1to170.10.150.254255.255.255.0
170.10.151.0/24170.10.151.1to170.10.151.254255.255.255.0
170.10.152.0/24170.10.152.1to170.10.152.254255.255.255.0
170.10.153.0/24170.10.153.1to170.10.153.254255.255.255.0
170.10.154.0/24170.10.154.1to170.10.154.254255.255.255.0
170.10.155.0/24170.10.155.1to170.10.155.254255.255.255.0
170.10.156.0/24170.10.156.1to170.10.156.254255.255.255.0
170.10.157.0/24170.10.157.1to170.10.157.254255.255.255.0
#### IP Addresses / Network Ranges for Non-SPF Email Traffic Where messages are being sent from accounts with envelope addresses not registered as internal domains, Mimecast routes through separate ranges.
RegionIP Address Range 1IP Address Range 2
United States of America (USB-Grid)
170.10.150.40
to
170.10.150.49
170.10.152.40
to
170.10.152.49
#### Application URLs
Field / OptionDescription
Administration Console [https://login-usb.mimecast.com/u/login/?gta=apps#/login](https://login-usb.mimecast.com/u/login/?gta=apps#/login)
Mimecast Personal Portal[https://webmail-usb.mimecast.com/m/portal/login/#/login](https://webmail-usb.mimecast.com/m/portal/login/#/login)
Mimecast API[https://usb-api.mimecast.com](https://usb-api.mimecast.com/)
Mimecast Secure Messaging Portal \*\*\*[https://login-usb.mimecast.com/m/secure](https://login-usb.mimecast.com/m/secure)
**Note:**\*\*\* The Mimecast Secure Messaging Portal URL should only be used by Mimecast customers. Non-Mimecast customers can access the portal by clicking the link in the notification message.
#### Targeted Threat Protection (TTP) Suppose you have integrations parsing messages for Mimecast-rewritten URLs or decoding Mimecast-rewritten URLs. In that case, these integrations must know Mimecast's Targeted Threat Protection URL patterns. Relevant integration types include SOAR, XDR, and custom scripts using the [Get Message Part](https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/ "https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/") or [Decode URL](https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/ "https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/") API endpoints.
RegionDestination Domain
United States of America (USB-Grid)
[url.usb.m.mimecastprotect.com](http://url.usb.m.mimecastprotect.com/)
### Canada #### IP Addresses and Network Ranges
**Note:**When entering IP ranges, it is essential to note that Microsoft 365 limits the CIDR you can use on the Connection Filter (e.g., 205.139.110.0/23 or 185.58.84.0/22). We recommend breaking up the ranges so they end in/24 as a workaround.
NetworkIP Address RangeNetmask
170.10.144.0/24170.10.144.1to170.10.144.254255.255.255.0
170.10.145.0/24170.10.145.1to170.10.145.254255.255.255.0
170.10.146.0/24170.10.146.1to170.10.146.254255.255.255.0
170.10.147.0/24170.10.147.1to170.10.147.254255.255.255.0
170.10.148.0/24170.10.148.1to170.10.148.254255.255.255.0
170.10.149.0/24170.10.149.1to170.10.149.254255.255.255.0
216.145.216.0/24216.145.216.1to216.145.216.254255.255.255.0
#### Application URLs
ApplicationURL
Administration Console[https://login-ca.mimecast.com/u/login?gta=administration](https://login-uk.mimecast.com/u/login?gta=administration)
Mimecast Personal Portal[https://webmail-ca.mimecast.com/m/portal/login/#/login](https://webmail-uk.mimecast.com/m/portal/login/#/login)
Mimecast API[https://ca-api.mimecast.com](https://eu-api.mimecast.com/)
Mimecast Secure Messaging Portal \*\*\*[https://login-ca.mimecast.com/m/secure](https://login-uk.mimecast.com/m/secure)
**Note:**\*\*\* The Mimecast Secure Messaging Portal URL should only be used by Mimecast customers. Non-Mimecast customers can access the portal by clicking the link in the notification message.
#### Targeted Threat Protection (TTP) Suppose you have integrations parsing messages for Mimecast-rewritten URLs or decoding Mimecast-rewritten URLs. In that case, these integrations must know Mimecast's Targeted Threat Protection URL patterns. Relevant integration types include SOAR, XDR, and custom scripts using the [Get Message Part](https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/ "https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/") or [Decode URL](https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/ "https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/") API endpoints.
RegionDestination Domain
Canada (CA-Grid)
[url.ca.m.mimecastprotect.com](http://url.ca.m.mimecastprotect.com/)
### South Africa #### IP Addresses and Network Ranges
NetworkIP Address RangeNetmask
41.74.192.0/2441.74.192.1to41.74.192.254255.255.255.0
41.74.193.0/2441.74.193.1to41.74.193.254255.255.255.0
41.74.194.0/2441.74.194.1to41.74.194.254255.255.255.0
41.74.195.0/2441.74.195.1to41.74.195.254255.255.255.0
41.74.196.0/2441.74.196.1to41.74.196.254255.255.255.0
41.74.197.0/2441.74.197.1to41.74.197.254255.255.255.0
41.74.198.0/2441.74.198.1to41.74.198.254255.255.255.0
41.74.199.0/2441.74.199.1to41.74.199.254255.255.255.0
41.74.200.0/2441.74.200.1to41.74.200.254255.255.255.0
41.74.201.0/2441.74.201.1to41.74.201.254255.255.255.0
41.74.202.0/2441.74.202.1to41.74.202.254255.255.255.0
41.74.203.0/2441.74.203.1to41.74.203.254255.255.255.0
41.74.204.0/2441.74.204.1to41.74.204.254255.255.255.0
41.74.205.0/2441.74.205.1to41.74.205.254255.255.255.0
41.74.206.0/2441.74.206.1to41.74.206.254255.255.255.0
41.74.207.0/2441.74.207.1to41.74.207.254255.255.255.0
#### IP Addresses / Network Ranges for Non-SPF Email Traffic Where messages are being sent from accounts with envelope addresses not registered as internal domains, Mimecast routes through separate ranges.
RegionIP Address Range 1IP Address Range 2
South Africa (ZA-Grid)41.74.202.40to41.74.202.4941.74.207.40to41.74.207.49
#### Application URLs
ApplicationURL
Administration Console[https://login-za.mimecast.com/u/login?gta=administration](https://login-za.mimecast.com/u/login?gta=administration)
Mimecast Personal Portal[https://webmail-za.mimecast.com/m/portal/login/#/login](https://webmail-za.mimecast.com/m/portal/login/#/login)
Mimecast API[https://za-api.mimecast.com](https://za-api.mimecast.com/)
Mimecast Secure Messaging Portal \*\*\*[https://login-za.mimecast.com/m/secure](https://login-za.mimecast.com/m/secure)
**Note:**\*\*\* The Mimecast Secure Messaging Portal URL should only be used by Mimecast customers. Non-Mimecast customers can access the portal by clicking the link in the notification message.
#### Targeted Threat Protection (TTP) Suppose you have integrations parsing messages for Mimecast-rewritten URLs or decoding Mimecast-rewritten URLs. In that case, these integrations must know Mimecast's Targeted Threat Protection URL patterns. Relevant integration types include SOAR, XDR, and custom scripts using the [Get Message Part](https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/ "https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/") or [Decode URL](https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/ "https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/") API endpoints.
RegionDestination Domain
South Africa (ZA-Grid)
[url.za.m.mimecastprotect.com](http://url.za.m.mimecastprotect.com/)
### Australia #### IP Addresses and Network Ranges
**Note:**When entering IP ranges, it is essential to note that Microsoft 365 limits the CIDR you can use on the Connection Filter (e.g., 205.139.110.0/23 or 185.58.84.0/22). We recommend breaking up the ranges so they end in/24 as a workaround.
NetworkIP Address RangeNetmask
103.96.20.0/24103.96.20.1to103.96.20.254255.255.255.0
103.96.21.0/24103.96.21.1to103.96.21.254255.255.255.0
103.96.22.0/24103.96.22.1to103.96.22.254255.255.255.0
103.96.23.0/24103.96.23.1to103.96.23.254255.255.255.0
170.10.134.0/24170.10.134.1to170.10.134.254255.255.255.0
170.10.135.0/24170.10.135.1to170.10.135.254255.255.255.0
103.13.69.0/24103.13.69.1to103.13.69.254255.255.255.0
124.47.150.0/24124.47.150.1to124.47.150.254255.255.255.0
124.47.189.0/24124.47.189.1to124.47.189.254255.255.255.0
180.189.28.0/24180.189.28.1to180.189.28.254255.255.255.0
216.145.217.0/24216.145.217.1to216.145.217.254255.255.255.0
#### IP Addresses/Network Ranges for Non-SPF Email Traffic Where messages are being sent from accounts with envelope addresses not registered as internal domains, Mimecast routes through separate ranges.
RegionIP Address Range 1IP Address Range 2
Australia (AU-Grid)103.96.20.40to103.96.20.49103.96.22.40to103.96.22.49
#### Application URLs
ApplicationURL
Administration Console[https://login-au.mimecast.com/u/login?gta=administration](https://login-au.mimecast.com/u/login?gta=administration)
Mimecast Personal Portal[https://webmail-au.mimecast.com/m/portal/login/#/login](https://webmail-au.mimecast.com/m/portal/login/#/login)
Mimecast API[https://au-api.mimecast.com](https://au-api.mimecast.com/)
Mimecast Secure Messaging Portal \*\*\*[https://login-au.mimecast.com/m/secure](https://login-au.mimecast.com/m/secure)
**Note:**\*\*\* The Mimecast Secure Messaging Portal URL should only be used by Mimecast customers. Non-Mimecast customers can access the portal by clicking the link in the notification message.
#### Targeted Threat Protection (TTP) Suppose you have integrations parsing messages for Mimecast-rewritten URLs or decoding Mimecast-rewritten URLs. In that case, these integrations must know Mimecast's Targeted Threat Protection URL patterns. Relevant integration types include SOAR, XDR, and custom scripts using the [Get Message Part](https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/ "https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/") or [Decode URL](https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/ "https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/") API endpoints.
RegionDestination Domain
Australia (AU-Grid)
[url.au.m.mimecastprotect.com](http://url.au.m.mimecastprotect.com/)
### Offshore #### IP Addresses and Network Ranges
**Note:**When entering IP ranges, it is essential to note that Microsoft 365 limits the CIDR you can use on the Connection Filter (e.g., 205.139.110.0/23 or 185.58.84.0/22). We recommend breaking up the ranges so they end in/24 as a workaround.
NetworkIP Address RangeNetmask
193.7.206.0/24193.7.206.1to193.7.207.254255.255.255.0
193.7.207.0/24193.7.207.1to193.7.207.254255.255.255.0
147.28.32.0/24147.28.32.1to147.28.32.254255.255.255.0
147.28.33.0/24147.28.33.1to147.28.33.254255.255.255.0
213.167.75.0/24213.167.75.1to213.167.75.254255.255.255.0
213.167.81.0/24213.167.81.1to213.167.81.254255.255.255.0
#### IP Addresses/Network Ranges for Non-SPF Email Traffic Where messages are being sent from accounts with envelope addresses not registered as internal domains, Mimecast routes through separate ranges:
RegionIP Address Range 1IP Address Range 2
Offshore213.167.75.240to213.167.75.249213.167.81.240to213.167.81.249
#### Application URLs
ApplicationURL
Administration Console[https://login-je.mimecast.com/u/login?gta=administration](https://login-je.mimecast.com/u/login?gta=administration)
Mimecast Personal Portal[https://webmail-je.mimecast.com/m/portal/login/#/login](https://webmail-je.mimecast.com/m/portal/login/#/login)
Mimecast API[https://je-api.mimecast.com](https://je-api.mimecast.com/)
Mimecast Secure Messaging Portal \*\*\*[https://login-je.mimecast.com/m/secure](https://login-je.mimecast.com/m/secure)
**Note:**\*\*\* The Mimecast Secure Messaging Portal URL should only be used by Mimecast customers. Non-Mimecast customers can access the portal by clicking the link in the notification message.
#### Targeted Threat Protection (TTP) Suppose you have integrations parsing messages for Mimecast-rewritten URLs or decoding Mimecast-rewritten URLs. In that case, these integrations must know Mimecast's Targeted Threat Protection URL patterns. Relevant integration types include SOAR, XDR, and custom scripts using the [Get Message Part](https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/ "https://integrations.mimecast.com/documentation/endpoint-reference/archive/get-message-part/") or [Decode URL](https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/ "https://integrations.mimecast.com/documentation/endpoint-reference/targeted-threat-protection-url-protect/decode-url/") API endpoints.
RegionDestination Domain
Offshore
[url.je.m.mimecastprotect.com](http://url.je.m.mimecastprotect.com/)
### USPCOM #### IP Addresses and Network Ranges
**Note:**When entering IP ranges, it is essential to note that Microsoft 365 limits the CIDR you can use on the Connection Filter (e.g., 205.139.110.0/23 or 185.58.84.0/22). We recommend breaking up the ranges so they end in/24 as a workaround.
NetworkIP Address RangeNetmask
170.10.138.0/24170.10.138.1to170.10.138.254255.255.255.0
170.10.139.0/24170.10.139.1to170.10.139.254255.255.255.0
170.10.140.0/24170.10.140.1to170.10.140.254255.255.255.0
170.10.158.0/24170.10.158.1to170.10.158.254255.255.255.0
#### Application URLs
ApplicationURL
Administration Console[https://login.mimecast-pscom-us.com](https://login.mimecast-pscom-us.com/)
Mimecast Personal Portal[https://login.mimecast-pscom-us.com](https://login.mimecast-pscom-us.com/)
Mimecast API[https://uspcom-api.mimecast-pscom-us.com](https://uspcom-api.mimecast-pscom-us.com/)
Mimecast Secure Messaging Portal \*\*\*[https://login.mimecast-pscom-us.com](https://login.mimecast-pscom-us.com/)
**Note:**\*\*\* The Mimecast Secure Messaging Portal URL should only be used by Mimecast customers. Non-Mimecast customers can access the portal by clicking the link in the notification message.
## Mimecast URL Scanning Activity

When monitoring IP addresses associated with clicked links in your environment, you may observe activity that does not originate from Mimecast-owned IP addresses or IP addresses listed on this page. As part of the Mimecast threat detection stack, the URL scanning layer can utilize various 3rd party vendors whose IP ranges are subject to change and are not tracked or disclosed by Mimecast. Furthermore, Mimecast employs anonymization techniques to prevent threat actors from recognizing and evading our scanners. To protect Mimecast customers, the associated IP addresses will not be disclosed.

# MailChimp - IP Address Ranges to Trust If you happen to use mailchimp and you don't want your emails coming back to you as being tagged as "spoofing" messages (ie: going to quarantine), you can add to your trusted senders list the IP ranges belonging to mailchimp. **The original IP ranges belonging to MailChimp:** - 205.201.128.0/20 - 198.2.128.0/18 - 148.105.0.0/16 Unfortunately, Proofpoint doesn't allow putting in anything bigger than a /24 so we had to break down their IP ranges into /24's **You can find the list below:** 205.201.128.0/24 205.201.129.0/24 205.201.130.0/24 205.201.131.0/24 205.201.132.0/24 205.201.133.0/24 205.201.134.0/24 205.201.135.0/24 205.201.136.0/24 205.201.137.0/24 205.201.138.0/24 205.201.139.0/24 205.201.140.0/24 205.201.141.0/24 205.201.142.0/24 205.201.143.0/24 198.2.128.0/24 198.2.129.0/24 198.2.130.0/24 198.2.131.0/24 198.2.132.0/24 198.2.133.0/24 198.2.134.0/24 198.2.135.0/24 198.2.136.0/24 198.2.137.0/24 198.2.138.0/24 198.2.139.0/24 198.2.140.0/24 198.2.141.0/24 198.2.142.0/24 198.2.143.0/24 198.2.144.0/24 198.2.145.0/24 198.2.146.0/24 198.2.147.0/24 198.2.148.0/24 198.2.149.0/24 198.2.150.0/24 198.2.151.0/24 198.2.152.0/24 198.2.153.0/24 198.2.154.0/24 198.2.155.0/24 198.2.156.0/24 198.2.157.0/24 198.2.158.0/24 198.2.159.0/24 198.2.160.0/24 198.2.161.0/24 198.2.162.0/24 198.2.163.0/24 198.2.164.0/24 198.2.165.0/24 198.2.166.0/24 198.2.167.0/24 198.2.168.0/24 198.2.169.0/24 198.2.170.0/24 198.2.171.0/24 198.2.172.0/24 198.2.173.0/24 198.2.174.0/24 198.2.175.0/24 198.2.176.0/24 198.2.177.0/24 198.2.178.0/24 198.2.179.0/24 198.2.180.0/24 198.2.181.0/24 198.2.182.0/24 198.2.183.0/24 198.2.184.0/24 198.2.185.0/24 198.2.186.0/24 198.2.187.0/24 198.2.188.0/24 198.2.189.0/24 198.2.190.0/24 198.2.191.0/24 148.105.0.0/24 148.105.1.0/24 148.105.2.0/24 148.105.3.0/24 148.105.4.0/24 148.105.5.0/24 148.105.6.0/24 148.105.7.0/24 148.105.8.0/24 148.105.9.0/24 148.105.10.0/24 148.105.11.0/24 148.105.12.0/24 148.105.13.0/24 148.105.14.0/24 148.105.15.0/24 148.105.16.0/24 148.105.17.0/24 148.105.18.0/24 148.105.19.0/24 148.105.20.0/24 148.105.21.0/24 148.105.22.0/24 148.105.23.0/24 148.105.24.0/24 148.105.25.0/24 148.105.26.0/24 148.105.27.0/24 148.105.28.0/24 148.105.29.0/24 148.105.30.0/24 148.105.31.0/24 148.105.32.0/24 148.105.33.0/24 148.105.34.0/24 148.105.35.0/24 148.105.36.0/24 148.105.37.0/24 148.105.38.0/24 148.105.39.0/24 148.105.40.0/24 148.105.41.0/24 148.105.42.0/24 148.105.43.0/24 148.105.44.0/24 148.105.45.0/24 148.105.46.0/24 148.105.47.0/24 148.105.48.0/24 148.105.49.0/24 148.105.50.0/24 148.105.51.0/24 148.105.52.0/24 148.105.53.0/24 148.105.54.0/24 148.105.55.0/24 148.105.56.0/24 148.105.57.0/24 148.105.58.0/24 148.105.59.0/24 148.105.60.0/24 148.105.61.0/24 148.105.62.0/24 148.105.63.0/24 148.105.64.0/24 148.105.65.0/24 148.105.66.0/24 148.105.67.0/24 148.105.68.0/24 148.105.69.0/24 148.105.70.0/24 148.105.71.0/24 148.105.72.0/24 148.105.73.0/24 148.105.74.0/24 148.105.75.0/24 148.105.76.0/24 148.105.77.0/24 148.105.78.0/24 148.105.79.0/24 148.105.80.0/24 148.105.81.0/24 148.105.82.0/24 148.105.83.0/24 148.105.84.0/24 148.105.85.0/24 148.105.86.0/24 148.105.87.0/24 148.105.88.0/24 148.105.89.0/24 148.105.90.0/24 148.105.91.0/24 148.105.92.0/24 148.105.93.0/24 148.105.94.0/24 148.105.95.0/24 148.105.96.0/24 148.105.97.0/24 148.105.98.0/24 148.105.99.0/24 148.105.100.0/24 148.105.101.0/24 148.105.102.0/24 148.105.103.0/24 148.105.104.0/24 148.105.105.0/24 148.105.106.0/24 148.105.107.0/24 148.105.108.0/24 148.105.109.0/24 148.105.110.0/24 148.105.111.0/24 148.105.112.0/24 148.105.113.0/24 148.105.114.0/24 148.105.115.0/24 148.105.116.0/24 148.105.117.0/24 148.105.118.0/24 148.105.119.0/24 148.105.120.0/24 148.105.121.0/24 148.105.122.0/24 148.105.123.0/24 148.105.124.0/24 148.105.125.0/24 148.105.126.0/24 148.105.127.0/24 148.105.128.0/24 148.105.129.0/24 148.105.130.0/24 148.105.131.0/24 148.105.132.0/24 148.105.133.0/24 148.105.134.0/24 148.105.135.0/24 148.105.136.0/24 148.105.137.0/24 148.105.138.0/24 148.105.139.0/24 148.105.140.0/24 148.105.141.0/24 148.105.142.0/24 148.105.143.0/24 148.105.144.0/24 148.105.145.0/24 148.105.146.0/24 148.105.147.0/24 148.105.148.0/24 148.105.149.0/24 148.105.150.0/24 148.105.151.0/24 148.105.152.0/24 148.105.153.0/24 148.105.154.0/24 148.105.155.0/24 148.105.156.0/24 148.105.157.0/24 148.105.158.0/24 148.105.159.0/24 148.105.160.0/24 148.105.161.0/24 148.105.162.0/24 148.105.163.0/24 148.105.164.0/24 148.105.165.0/24 148.105.166.0/24 148.105.167.0/24 148.105.168.0/24 148.105.169.0/24 148.105.170.0/24 148.105.171.0/24 148.105.172.0/24 148.105.173.0/24 148.105.174.0/24 148.105.175.0/24 148.105.176.0/24 148.105.177.0/24 148.105.178.0/24 148.105.179.0/24 148.105.180.0/24 148.105.181.0/24 148.105.182.0/24 148.105.183.0/24 148.105.184.0/24 148.105.185.0/24 148.105.186.0/24 148.105.187.0/24 148.105.188.0/24 148.105.189.0/24 148.105.190.0/24 148.105.191.0/24 148.105.192.0/24 148.105.193.0/24 148.105.194.0/24 148.105.195.0/24 148.105.196.0/24 148.105.197.0/24 148.105.198.0/24 148.105.199.0/24 148.105.200.0/24 148.105.201.0/24 148.105.202.0/24 148.105.203.0/24 148.105.204.0/24 148.105.205.0/24 148.105.206.0/24 148.105.207.0/24 148.105.208.0/24 148.105.209.0/24 148.105.210.0/24 148.105.211.0/24 148.105.212.0/24 148.105.213.0/24 148.105.214.0/24 148.105.215.0/24 148.105.216.0/24 148.105.217.0/24 148.105.218.0/24 148.105.219.0/24 148.105.220.0/24 148.105.221.0/24 148.105.222.0/24 148.105.223.0/24 148.105.224.0/24 148.105.225.0/24 148.105.226.0/24 148.105.227.0/24 148.105.228.0/24 148.105.229.0/24 148.105.230.0/24 148.105.231.0/24 148.105.232.0/24 148.105.233.0/24 148.105.234.0/24 148.105.235.0/24 148.105.236.0/24 148.105.237.0/24 148.105.238.0/24 148.105.239.0/24 148.105.240.0/24 148.105.241.0/24 148.105.242.0/24 148.105.243.0/24 148.105.244.0/24 148.105.245.0/24 148.105.246.0/24 148.105.247.0/24 148.105.248.0/24 148.105.249.0/24 148.105.250.0/24 148.105.251.0/24 148.105.252.0/24 148.105.253.0/24 148.105.254.0/24 148.105.255.0/24 # Sendgrid - Approximate list of the IP addresses that the domain sendgrid.net allows email to be sent from according to their SPF record 50.31.32.0/19 (8192 addresses) 149.72.0.0/16 (65536 addresses) 159.183.0.0/16 (65536 addresses) 167.89.0.0/17 (32768 addresses) 168.245.0.0/17 (32768 addresses) 192.254.112.0/20 (4096 addresses) 198.21.0.0/21 (2048 addresses) 198.37.144.0/20 (4096 addresses) 208.117.48.0/20 (4096 addresses) 223.165.113.0/24 (256 addresses) 223.165.115.0/24 (256 addresses) 223.165.118.0/23 (512 addresses) 223.165.120.0/23 (512 addresses) # ClickDimensions 66.240.227.4/32 66.240.227.9/32 66.240.227.18/32 66.240.227.21/32 63.143.57.132/32 63.143.57.137/32 63.143.57.146/32 63.143.57.149/32 135.84.216.160/32 135.84.216.224/32 135.84.217.32/32 135.84.217.96/32 34.245.210.9/32 34.245.210.10/32 34.245.210.11/32 34.245.210.12/32 34.245.210.13/32 34.245.210.14/32 34.245.210.15/32 34.245.210.16/32 213.206.105.68/32 213.206.105.69/32 213.206.105.70/32 213.206.105.73/32 213.206.105.74/32 213.206.105.75/32 213.206.105.76/32 # Intuit.com - Quickbooks 199.16.139.16/32 199.16.139.17/32 199.16.139.18/32 199.16.139.20/32 199.16.139.21/32 199.16.139.22/32 199.16.139.23/32 199.16.139.24/32 199.16.139.25/32 199.16.139.26/32 199.16.139.27/32 206.108.40.10/32 206.108.40.11/32 206.108.40.12/32 206.108.40.13/32 206.108.40.14/32 206.108.40.15/32 206.108.40.16/32 206.108.40.17/32 206.108.40.18/32 206.108.40.28/32 206.108.40.7/32 206.108.40.8/32 206.108.40.89/32 206.108.40.9/32 206.108.40.90/32 206.108.40.91/32 206.108.40.92/32 206.154.105.172/32 206.154.105.173/32 206.154.105.174/32 206.154.105.175/32 206.154.105.176/32 206.154.105.177/32 206.154.105.178/32 206.154.105.179/32 # TalentPro - Payroll Service 149.72.137.232/32 149.72.188.204/32 167.89.1.65/32 168.245.47.229/32 # Constant Contact 208.75.123.0/24 205.207.106.0/24 # Zoom - Email Server IPs
2024-09-12 20:03:12
---
You may receive emails from Zoom regarding notifications, activation emails, password resets, and more. - Account-related notifications will come from **no-reply@zoom.us**. - Support ticket emails will come from **customercare@zoom.us**. While most mail servers receive Zoom's emails within a few minutes, some mail servers may take 30 minutes or longer. ## Zoom's email server IPs If your email is managed by your organization, you can ask them to ensure **no-reply@zoom.us**, as well as the following IP addresses, are allowed by your company's email server: ``` 134.224.168.131/32 134.224.168.132/32 149.72.21.92/32 149.72.32.163/32 149.72.59.154/32 149.72.112.79/32 149.72.122.209/32 149.72.134.114/32 149.72.163.203/32 149.72.185.127/32 149.72.191.243/32 149.72.196.70/32 149.72.196.77/32 149.72.198.96/32 149.72.198.100/32 149.72.199.144/32 149.72.249.102/32 149.72.73.235/32 159.183.141.227/32 159.183.146.28/32 159.183.146.37/32 159.183.146.41/32 159.183.150.18/32 159.183.151.211/32 159.183.151.213/32 159.183.156.108/32 159.183.179.39/32 159.183.187.77/32 159.183.192.104/32 159.183.198.7/32 159.183.198.70/32 159.183.204.195/32 159.183.220.232/32 159.183.220.239/32 167.89.93.232/32 168.245.118.48/32 170.114.15.172/32 170.114.15.173/32 170.114.15.174/32 170.114.15.175/32 170.114.15.176/32 170.114.15.177/32 170.114.15.178/32 170.114.15.179/32 170.114.15.180/32 170.114.15.181/32 170.114.15.182/32 170.114.15.183/32 170.114.15.184/32 170.114.15.185/32 170.114.15.186/32 170.114.15.187/32 170.114.15.188/32 170.114.15.189/32 170.114.15.190/32 170.114.15.191/32 170.114.15.192/32 170.114.15.193/32 170.114.44.124/32 170.114.44.125/32 ```
![warning icon](https://assets.zoom.us/generic-images/common-buttons-and-icons/outline/warning-element-icon.png)

Exercise caution if you receive a suspicious or unexpected email appearing to come from Zoom that’s not from one of the IPs listed above. If you receive a suspicious email from Zoom, you can report it by [submitting a request](https://zoom.us/trust-form) to Zoom’s Trust & Safety team. To help prevent fraudulent or suspicious emails, we encourage organizations to consider enabling a DMARC (Domain-based Message Authentication, Reporting, and Conformance) policy that rejects emails that fail DKIM and SPF.

## How to troubleshoot not receiving emails from Zoom - Check the spam or junk folder on your email service, as some services may mistakenly mark these emails as spam. - If your email is managed by your organization, you can ask them to ensure **no-reply@zoom.us**, as well as the [IP addresses listed above](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0060106#h_14948552511321726171317257), are allowed by your company's email server. - Chat with us, mentioning “not receiving emails”. Our chatbot can help guide you through troubleshooting steps if you’re still not receiving emails from Zoom.
# iCIMS - Mailservers ## US, Canadian, and EU Mail Hosting Environments iCIMS systems allows for users to send emails to any recipient with a profile within the system. The email will be sent from an iCIMS server using one of the IP addresses listed below. If your company only allows emails from specific senders on its firewall, it may be necessary to allowlist the following ranges below, to ensure successful delivery. iCIMS follows best practice recommendations regarding email delivery using Optimistic TLS, SPF, DKIM and DMARC. - All iCIMS email sending domains are origin controlled with SPF. - All iCIMS email display domains are authenticated with 2048 bit DKIM keys. - All iCIMS email domains are further authenticated with DMARC reject policies.
IPv4 NetworkIPv4 IP Range
162.247.160.0/21162.247.160.1 - 162.247.167.254
### Sending Domains The first thing your recipients see when they open your email is your address in the From: field, also known as the Friendly From or the Visible Sender. The Sending Domain is the domain portion of this email address. The sending domains that iCIMS uses are as follows: - **For ATS customers hosted in US and Canada**: *@[talent.icims.com](http://talent.icims.com/)* - **For ATS customers hosted in EU**: *@[talent.icims.eu](http://talent.icims.eu/)* - **For most non-ATS iCIMS products**: *@[icims.com](http://icims.com/)* ### Bounce Domains The first thing a receiving mail server will see when they receive an email from an iCIMS system is the bounce email address, also known as the Return-Path or the Envelope Sender. The Bounce Domain is the domain portion of this email address. This email address is typically hidden and only visible in the full email source headers. The bounce domain that iCIMS uses are as follows: - **For US and Canadian hosting environments**: *@[bounces.icims.com](http://bounces.icims.com/)* - **For EU hosting environments**: *@[bounces.icims.eu](http://bounces.icims.eu/)* **Notes:** - The IP addresses listed above are dedicated to iCIMS customer email traffic only. - iCIMS does not require all customers to add the entire range above to your allowlist. However, adding to your allowlist may be necessary if iCIMS is sending as your email domain. - If iCIMS is sending email as your domain and you wish to allow this behavior, please reference the [Configuring Email Authentication](https://care.icims.com/s/article/Configuring-Email-Authentication?r=31&ui-chatter-components-aura-components-forceChatter-feeds.ToggleFollow.getChatterFollowModel=1&ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1&ui-communities-components-aura-components-forceCommunity-richText.RichText.getParsedRichTextValue=1&ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&ui-force-components-controllers-recordGlobalValueProvider.RecordGvp.getRecord=1&ui-self-service-components-controller.ArticleTopicList.getTopics=1&ui-self-service-components-controller.ArticleView.getArticleHeaderDetail=1) article. - If iCIMS is sending emails as your domain and you do not wish this to continue, bi-directional email must be re-enabled in your iCIMS system. Submit a case to iCIMS Technical Support to make sure these default settings are enabled. - iCIMS cannot provide a single IP address for customer email traffic. - iCIMS prefers TLS for SMTP traffic where the receiving mail server supports TLS but is unable to require TLS for any specific customer. # Canva - Mailserver IP Ranges ## **Email IP Addresses** If needed, institutions can allow all static Canvas Email IP addresses. When Email IP addresses are allowlisted, the entire list of IP addresses should be allowlisted. The variety of IP addresses ensure a specific IP is not overloaded and activity can be distributed across various data centers as needed. This recommendation also applies to adding international IP addresses as well. **Note:** The IP list may be updated at any time. **Customers hosted in Canada** 99.79.19.152/32 52.60.179.121/32 23.249.209.14/32 23.249.209.15/32 **Customers hosted in Ireland (DUB) or Frankfurt (FRA)** 54.240.89.126/32 54.240.89.127/32 54.240.89.128/32 54.240.89.129/32 54.240.89.130/32 **Customers hosted in Singapore (SIN) or Sydney (SYD)** 69.169.235.184/32 69.169.235.186/32 69.169.235.185/32 **Customers hosted in Virginia (IAD) or Oregon (PDX)** 23.249.221.108/32 23.249.221.109/32 23.249.221.110/32 23.249.221.111/32 23.249.221.112/32 23.249.221.113/32 23.249.221.114/32 23.249.221.115/32 23.249.221.116/32 23.249.221.117/32 23.249.221.118/32 23.249.221.119/32 23.249.221.120/32 23.249.221.121/32 23.249.221.122/32 23.249.221.123/32 23.249.221.124/32 23.249.221.125/32 23.249.221.126/32 23.249.221.127/32 54.240.127.159/32 54.240.127.60/32 54.240.127.61/32 54.240.127.62/32 54.240.127.63/32 54.240.127.64/32 54.240.127.65/32 54.240.127.66/32 54.240.127.67/32 54.240.127.68/32 54.240.14.1/32 54.240.14.100/32 54.240.14.102/32 54.240.14.103/32 54.240.14.105/32 54.240.14.107/32 54.240.14.128/32 54.240.14.130/32 54.240.14.131/32 54.240.14.139/32 54.240.14.154/32 54.240.14.188/32 54.240.14.198/32 54.240.14.199/32 54.240.14.2/32 54.240.38.184/32 54.240.38.185/32 54.240.38.186/32 54.240.38.187/32 54.240.38.188/32 23.249.221.12/32 23.249.221.202/32 54.240.68.117/32 54.240.68.118/32 54.240.68.119/32 54.240.68.120/32 54.240.68.121/32 54.240.68.123/32 54.240.76.81/32 54.240.76.83/32 54.240.76.85/32 54.240.76.87/32 54.240.76.88/32 54.240.76.92/32 54.240.76.96/32 # Full IP Lists # iCIMS - Full IP List
## iCIMS IP Addresses and Domains to Allow This article provides the iCIMS network IP addresses (and other relevant IP addresses) and domains that customers should allow.
# Overview
A number of iCIMS' Talent Cloud products leverage designated IP addresses and domains that iCIMS recommends customers (or their integration partners) allow, including: - iCIMS Applicant Tracking, including career sites - iCIMS Onboarding, including new hire portals - iCIMS Connect (Legacy CRM), including portals - iCIMS Text Engagement - iCIMS Video Interviews - iCIMS Language Assessments - SkillSurvey This article provides IP addresses and domains that iCIMS recommends that customers allow for the products listed above, as well as other relevant information. It is intended to be consumed by the responsible party in charge of internal network configurations and email policies for your organization. If your organization allows designated IPs, please bookmark and revisit this article regularly to stay informed with IP ranges and addresses that may be added or removed at any time. Note that some items listed below differ depending on the data center that your organization is hosted in (US & Canada or EU). These items are indicated below. This article contains the following sections. Click on a section title to jump to the section of the article. - [iCIMS HTTP & HTTPS Access](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#http) - [iCIMS Mail Servers](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#mail) - [US, Canadian, and EU Mail Hosting Environments](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#mail-usca) - [IP Addresses for Integration Traffic into Your Organization's Network](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#integration) - [US & Canadian Hosting Environments](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#integration-usca) - [EU Hosting Environment](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#integration-eu) - [IP Addresses for Integration Traffic Out of Your Organization's Network](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#IPAddressesOutOf) - [US & Canadian Hosting Environments](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#USCAIPAddressesOutOf) - [EU Hosting Environment](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#EUIPAddressesOutOf) - [SFTP Sites](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#sftp) - [US & Canadian Hosting Environments](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#SFTP-USCA) - [EU Hosting Environment](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#SFTP-EU) - [Other IP Addresses & URLs](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#other) - [IP Addresses for iCIMS Release Communication Emails](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#release-comm) - [Text Engagement IP Addresses](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#tr_ip) - [iCIMS Applicant Tracking's Interview Scheduling Feature](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#InterviewScheduling) - [SkillSurvey Domains & IP Addresses](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#SkillSurvey) - [Salesforce IP Addresses & URLs](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#sf_ip) - [Cloudflare, Inc. IP Addresses](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#cloudflare) - [Removed iCIMS IP Addresses](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#removed-icims-ip) - [Article Updates](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#article_updates) ---
# iCIMS HTTP & HTTPS Access
iCIMS recommends that customers have *\*.[icims.com](http://icims.com/)* added to their allowlist, rather than a subnet of iCIMS IP addresses. (There is no current solution to allowlist your users' HTTP and HTTPS traffic based solely on IP addresses.)
**Notes:**
- Adding iCIMS IP ranges for HTTP and HTTPS traffic to your allowlist is insufficient because of the content delivery network that iCIMS uses. The content delivery network's IP addresses are dynamic and constantly changing. You may observe a current IP for this content, but there is no guarantee for the durability of those IP addresses. - If the login box appears gray, this may be caused by improper allowlisting. - Programs known to block our content delivery network include: Websense, Barracuda Networks. - If your career sites have been created by iCIMS staff using the magic-branding tool, the only option for allowlisting is a wildcard allowlist of *\*.[i.icims.com](http://i.icims.com/)*. There are no IP or hostname specific options to allowlist magic-branding traffic. - If you are unable to add *\*.[icims.com](http://icims.com/)* to your allowlist and must add specific hostnames (beyond your specific system and career site URLs), iCIMS recommends adding these CDN hostnames to your allowlist: - [cdn00.icims.com](http://cdn00.icims.com/) - [cdn01.icims.com](http://cdn01.icims.com/) - [cdn02.icims.com](http://cdn02.icims.com/) - [cdn03.icims.com](http://cdn03.icims.com/) - [cdn04.icims.com](http://cdn04.icims.com/) - [cdn05.icims.com](http://cdn05.icims.com/) - [cdn06.icims.com](http://cdn06.icims.com/) - [cdn07.icims.com](http://cdn07.icims.com/) - [cdn08.icims.com](http://cdn08.icims.com/) - [cdn09.icims.com](http://cdn09.icims.com/) - [cdn13.icims.com](http://cdn13.icims.com/) - [cdn31.icims.com](http://cdn31.icims.com/) - Customers who use Social Distribution might also have [social.icims.com](http://social.icims.com/) added to their allowlist. ---
# iCIMS Mail Servers ## US, Canadian, and EU Mail Hosting Environments
iCIMS systems allows for users to send emails to any recipient with a profile within the system. The email will be sent from an iCIMS server using one of the IP addresses listed below. If your company only allows emails from specific senders on its firewall, it may be necessary to allowlist the following ranges below, to ensure successful delivery. iCIMS follows best practice recommendations regarding email delivery using Optimistic TLS, SPF, DKIM and DMARC. - All iCIMS email sending domains are origin controlled with SPF. - All iCIMS email display domains are authenticated with 2048 bit DKIM keys. - All iCIMS email domains are further authenticated with DMARC reject policies.
IPv4 NetworkIPv4 IP Range
162.247.160.0/21162.247.160.1 - 162.247.167.254
### Sending Domains The first thing your recipients see when they open your email is your address in the From: field, also known as the Friendly From or the Visible Sender. The Sending Domain is the domain portion of this email address. The sending domains that iCIMS uses are as follows:
- **For ATS customers hosted in US and Canada**: *@[talent.icims.com](http://talent.icims.com/)* - **For ATS customers hosted in EU**: *@[talent.icims.eu](http://talent.icims.eu/)* - **For most non-ATS iCIMS products**: *@[icims.com](http://icims.com/)*
### Bounce Domains The first thing a receiving mail server will see when they receive an email from an iCIMS system is the bounce email address, also known as the Return-Path or the Envelope Sender. The Bounce Domain is the domain portion of this email address. This email address is typically hidden and only visible in the full email source headers. The bounce domain that iCIMS uses are as follows:
- **For US and Canadian hosting environments**: *@[bounces.icims.com](http://bounces.icims.com/)* - **For EU hosting environments**: *@[bounces.icims.eu](http://bounces.icims.eu/)*
**Notes:**
- The IP addresses listed above are dedicated to iCIMS customer email traffic only. - iCIMS does not require all customers to add the entire range above to your allowlist. However, adding to your allowlist may be necessary if iCIMS is sending as your email domain. - If iCIMS is sending email as your domain and you wish to allow this behavior, please reference the [Configuring Email Authentication](https://care.icims.com/s/article/Configuring-Email-Authentication?r=31&ui-chatter-components-aura-components-forceChatter-feeds.ToggleFollow.getChatterFollowModel=1&ui-comm-runtime-components-aura-components-siteforce-qb.Quarterback.validateRoute=1&ui-communities-components-aura-components-forceCommunity-richText.RichText.getParsedRichTextValue=1&ui-communities-components-aura-components-forceCommunity-seoAssistant.SeoAssistant.getSeoData=1&ui-force-components-controllers-recordGlobalValueProvider.RecordGvp.getRecord=1&ui-self-service-components-controller.ArticleTopicList.getTopics=1&ui-self-service-components-controller.ArticleView.getArticleHeaderDetail=1) article. - If iCIMS is sending emails as your domain and you do not wish this to continue, bi-directional email must be re-enabled in your iCIMS system. Submit a case to iCIMS Technical Support to make sure these default settings are enabled. - iCIMS cannot provide a single IP address for customer email traffic. - iCIMS prefers TLS for SMTP traffic where the receiving mail server supports TLS but is unable to require TLS for any specific customer. ---
# IP Addresses for Integration Traffic into Your Organization's Network ## US & Canadian Hosting Environments
Integration partners or customers who need to open their firewall for inbound SFTP/HTTP/HTTPS traffic from the iCIMS network should allowlist the following.
### All Products
Required for customers hosted in the US or Canada and subscribed to any iCIMS product.
IPv4 NetworkIPv4 IP RangeNotes
34.224.35.80/3234.224.35.80
34.230.218.185/3234.230.218.185
52.5.81.230/3252.5.81.230
52.39.216.234/3252.39.216.234
52.40.164.17/3252.40.164.17
52.43.152.110/3252.43.152.110
52.73.132.79/3252.73.132.79
52.201.74.58/3252.201.74.58
52.203.54.122/3252.203.54.122
54.71.223.122/3254.71.223.122
162.247.160.0/21162.247.160.1 - 162.247.167.254
#### US Authentication (Log In) Required for authentication (log in) for customers hosted in the US and subscribed to any iCIMS product.
IPv4 NetworkIPv4 IP RangeNotes
44.208.253.77/3244.208.253.77updated 1/9/2023
52.22.31.220/3252.22.31.220 updated 1/9/2023
52.70.205.183/3252.70.205.183updated 1/9/2023
52.203.168.120/3252.203.168.120updated 1/9/2023
54.160.91.230/3254.160.91.230updated 1/9/2023
### Canada Hosting Environment Required for customers hosted in Canada subscribed to any iCIMS product.
IPv4 NetworkIPv4 IP RangeNotes
20.43.8.233/3220.43.8.233
35.182.19.201/3235.182.19.201
35.182.76.61/3235.182.76.61
52.60.144.70/3252.60.144.70
75.2.18.154/3275.2.18.154updated 1/13/2021
99.83.212.130/3299.83.212.130updated 1/13/2021
#### Canada Authentication (Log In) Required for authentication (log in) for customers hosted in Canada and subscribed to any iCIMS product.
IPv4 NetworkIPv4 IP RangeNotes
3.98.47.26/323.98.47.26updated 10/26/2022
35.182.150.3/3235.182.150.3updated 10/26/2022
52.60.104.197/3252.60.104.197updated 10/26/2022
### iCIMS Video Interviews & iCIMS Language Assessment Required for customers subscribed to iCIMS Video Interviews or iCIMS Language Assessment and hosted in the US or Canada. The IPs correspond to the hostname: [api.qualify.talentplatform.us](http://api.qualify.talentplatform.us/).
IPv4 NetworkIPv4 IP RangeNotes
44.237.8.163/3244.237.8.163added 6/3/21
54.163.134.53/3254.163.134.53added 6/3/21
54.174.200.125/3254.174.200.125/32added 6/3/21
54.186.232.248/3254.186.232.248added 6/3/21
54.245.238.143/3254.245.238.143added 6/3/21
100.24.100.56/32100.24.100.56added 6/3/21
## EU Hosting Environment
Integration partners or customers who need to open their firewall for inbound SFTP/HTTP/HTTPS traffic from the iCIMS network should allowlist the following.
### All Products Required for customers hosted in the EU and subscribed to any iCIMS product.
IPv4 NetworkIPv4 IP RangeNotes
35.156.72.166/3235.156.72.166updated 6/3/2021
52.29.139.117/3252.29.139.117updated 6/3/2021
52.208.71.204/3252.208.71.204updated 6/3/2021
52.215.252.239/3252.215.252.239updated 6/3/2021
162.247.160.0/21162.247.160.1 - 162.247.167.254added 3/1/2023
#### EU Authentication (Log In) Required for authentication (log in) for customers hosted in the EU and subscribed to any iCIMS product.
IPv4 NetworkIPv4 IP RangeNotes
3.76.2.30/323.76.2.30updated 11/4/2022
3.125.254.102/323.125.254.102updated 11/4/2022
18.156.44.93/3218.156.44.93updated 11/4/2022
#### EU Azure Hosting Environment Required for customers hosted in EU Azure only and subscribed to any iCIMS product.
IPv4 NetworkIPv4 IP RangeNotes
35.156.57.135/3235.156.57.135added 1/13/2021
### iCIMS Video Interviews & iCIMS Language Assessment Required for customers subscribed to iCIMS Video Interviews or iCIMS Language Assessment and hosted in the EU. These IPs correspond to the hostname: [api.qualify.talentplatform.eu](http://api.qualify.talentplatform.us/).
IPv4 NetworkIPv4 IP RangeNotes
18.194.47.183/3218.194.47.183added 6/3/2021
18.194.129.86/3218.194.129.86added 6/3/2021
18.198.111.118/3218.198.111.118added 6/3/2021
52.30.24.67/3252.30.24.67added 6/3/2021
54.247.45.9/3254.247.45.9added 6/3/2021
63.35.128.82/3263.35.128.82added 6/3/2021
#### EU Azure Hosting Environment Required for customers subscribed to iCIMS Video Interviews or iCIMS Language Assessment and hosted in EU Azure.
IPv4 NetworkIPv4 IP RangeNotes
20.199.9.20/3220.199.9.20added 6/3/2021
20.199.81.177/3220.199.81.177added 6/3/2021
40.66.32.94/3240.66.32.94added 6/3/2021
---
# IP Addresses for Integration Traffic Out of Your Organization's Network ## US & Canadian Hosting Environments / [api.icims.com](http://api.icims.com/)
Integration partners and customers leveraging [api.icims.com](http://api.icims.com/) may need to allowlist traffic out of their network. In this case, the following should be allowed: - Outbound IPs - 34.211.79.9/32 - 34.231.88.90/32 - Outbound protocol/ports - https/443
## EU Hosting Environment / [api-eu.icims.com](http://api-eu.icims.com/)
Integration partners and customers leveraging [api-eu.icims.com](http://api-eu.icims.com/) may need to allowlist traffic out of their network. In this case, the following should be allowed: - Outbound IPs - 35.158.141.71 - 34.250.110.226 - Outbound protocol/ports - https/443 ---
# SFTP Sites ## US & Canadian Hosting Environments
Customers hosted in the US or Canadian data center should add *[sftp.icims.com](http://sftp.icims.com/)* or the following two IP ranges to their allowlist: - 162.247.162.200/29 - 162.247.163.200/29 SFTP is designated through Port 22, which utilizes the secure file transfer protocol. **Notes:** - Some customers may still reference *[ftp.icims.com](https://community.icims.com/s/article/ftp.icims.com)*, this is the same endpoint and is still supported, but the primary hostname is *[sftp.icims.com](http://sftp.icims.com/)*. - iCIMS does not support FTPS or FTP.
## EU Hosting Environment
Customers hosted in the EU Data Center should add *[sftp.icims.eu](http://sftp.icims.eu/)* or the following two IP ranges to their allowlist: - 162.247.164.200/29 - 162.247.165.200/29 SFTP is designated through Port 22, which utilizes the secure file transfer protocol. **Note:** iCIMS does not support FTPS.---
# Other IP Addresses & URLs ## IP Addresses for iCIMS Release Communication Emails
iCIMS routinely sends emails to customers during releases. To ensure delivery of these emails, it is recommended that customers add the following IP addresses to their allowlist: - 192.28.145.59
## Text Engagement IP Addresses
Emails sent by Text Engagement (such as invitations and password reset emails) are sent from . To ensure delivery of these emails, it is recommended that customers with Text Engagement products add the following IP addresses to their allowlist: - 35.163.132.52/32 - 35.163.148.163/32 - 52.27.44.190/32 - 52.35.191.75/32 - 147.253.209.13/32 - 147.253.209.96/32 - 147.253.210.103/32 - 147.253.215.97/32
## iCIMS Applicant Tracking's Interview Scheduling Feature
As part of iCIMS Applicant Tracking (ATS), the Interview Scheduling feature allows customers to connect their organization’s calendar through Cronofy, a subprocessor of iCIMS. Customers who use Interview Scheduling may consider allowlisting the From Cronofy to External Servers IPs listed in Cronofy’s resource: [Does Cronofy provide fixed IP addresses for calendar service traffic?](https://docs.cronofy.com/calendar-admins/faqs/fixed-ips/) **Notes:**- The link is to a third-party resource that is not maintained by iCIMS and is subject to change. - Only the From Cronofy to External Servers IPs are applicable. - [iCIMS Mail Servers](https://community.icims.com/s/article/iCIMS-IP-Addresses-and-Domains-to-Allow#mail) are not applicable.
## SkillSurvey Domains & IP Addresses The sending domains that SkillSurvey uses for the Reference, Career Readiness, and Source products are as follows:
- *@[skillsurvey.com](http://skillsurvey.com/)* - *@[reference.skillsurvey.com](http://reference.skillsurvey.com/)* - *@[source.skillsurvey.com](http://source.skillsurvey.com/)*
It is recommended that customers with SkillSurvey products add the following IP addresses to their allowlist:
IPv4 NetworkIPv4 IP RangeNotes
54.240.33.206/3254.240.33.206Added 3/13/23
54.240.36.140/3254.240.36.140Added 3/13/23
54.240.37.137/3254.240.37.137Added 3/13/23
54.240.37.239/3254.240.37.239Added 3/13/23
149.72.71.85/32149.72.71.85Added 3/13/23
149.72.255.182/32149.72.255.182Added 3/13/23
149.72.121.200/32149.72.121.200Added 3/13/23
159.183.138.49/32159.183.138.49Added 3/13/23
159.183.171.171/32159.183.171.171Added 3/13/23
159.183.199.167/32159.183.199.167Added 3/13/23
198.2.187.101/32198.2.187.101Added 3/13/23
198.2.187.129/32198.2.187.129Added 3/13/23
## Salesforce IP Addresses & URLs The iCIMS Knowledge Base, a collection of how-to and general information for iCIMS customers, is hosted on the Salesforce platform. For information about Salesforce's recommended IP addresses, please refer to the following Salesforce page: [https://help.salesforce.com/apex/HTViewSolution?id=000003652](https://help.salesforce.com/apex/HTViewSolution?id=000003652) The URL used by iCIMS Community site & Knowledge Base is: [https://community.icims.com/s/](https://community.icims.com/s/).
## Cloudflare, Inc. IP Addresses API calls to [login.icims.com](http://login.icims.com/), [login.icims.ca](http://login.icims.ca/), and [login.icims.eu](http://login.icims.eu/) are sent from Cloudflare, Inc. IP addresses. For a full list of Cloudflare, Inc. IP ranges, review the following link: [https://www.cloudflare.com/ips/](https://www.cloudflare.com/ips/). **Note:** This website is not maintained by iCIMS.
# Removed iCIMS IP Addresses *This section contains IP addresses that have been removed from use. Information will remain for approximately 6 months.* The following IP addresses are no longer in use by iCIMS systems and no longer require allowlisting:
IPv4 NetworkIPv4 IP RangeDate RemovedNotes
13.77.159.69/3213.77.159.693/1/23Previously required for customers hosted in the US subscribed to any iCIMS product
34.253.65.199/3234.253.65.1993/1/23Previously required for customers hosted in EU Azure only.
52.190.26.179/3252.190.26.1793/1/23Previously required for customers hosted in the US subscribed to any iCIMS product
75.2.68.49/3275.2.68.493/1/23Previously required for customers hosted in the US subscribed to any iCIMS product
75.2.113.138/3275.2.113.1383/1/23Previously required for customers hosted in the EU and subscribed to any iCIMS product
99.83.177.62/3299.83.177.623/1/23Previously required for customers hosted in the US subscribed to any iCIMS product
99.83.181.78/3299.83.181.783/1/23Previously required for customers hosted in the EU and subscribed to any iCIMS product
All OVH IPsAll OVH IPs3/1/23All IPs removed that were previously required for customers subscribed to iCIMS Video Interviews or iCIMS Language Assessment and hosted in OVH in the EU
# Canva - Full IP List
Canvas Domain, Email, and Server Management
This document lists the domains and IP addresses used in various areas of Canvas.
---
Many K12 schools and some higher education institutions need to restrict the websites that students can visit while on campus and want to manage Canvas’ resources. Future changes may require additional configurations. Institutions that use Canvas domain, email, or server resource management should thoroughly test their firewalls to avoid instability. ## **Canvas Core Domains** Whenever possible, Canvas uses a subdomain of <domain>.instructure.com to host additional resources. This behavior allows institutions to allow \*.instructure.com and cover a range of services that Canvas provides. Some of the built-in functionality of Canvas is accessed via a separate URL that will also need to be allowed: **Browser Security**
- \*.canvas-user-content.com
**Canvas Guides**
- \*.canvaslms.com
**Canvas Images/File Storage (except Media)**
- \*.inscloudgate.net/ - instructure-uploads.s3.amazonaws.com - instructure-uploads-2.s3.amazonaws.com - instructure-uploads-eu.s3.amazonaws.com - instructure-uploads-apse1.s3.amazonaws.com - instructure-uploads-apse2.s3.amazonaws.com - instructure-uploads-fra.s3.amazonaws.com - instructure-uploads-pdx.s3.amazonaws.com - Instructure-uploads-yul.s3.amazonaws.com
**Canvas Media Storage**
- \*.instructuremedia.com - notorious-prod.s3.amazonaws.com - notorious-prod-apse1.s3.amazonaws.com - notorious-prod-apse2.s3.amazonaws.com - notorious-prod-eu.s3.amazonaws.com - notorious-prod-fra.s3.amazonaws.com - notorious-prod-pdx.s3.amazonaws.com - notorious-prod-yul.s3.amazonaws.com
**Conferences - BigBlueButton basic integration**
- \*.blindsidenetworks.com
**DocViewer**
- canvadocs.instructure.com
**Gravatar Images (Profile Pictures)**
- \*.gravatar.com
**Office 365 Integration**
- office365-iad-prod.instructure.com
**Google Docs Integration**
- docs.google.com
**Google Drive Integration**
- drive.google.com
**Import Scripts and Canvas Resources**
- \*.cloudfront.net
**Rich Content Editor Math Equations**
- instructure.codecogs.com
**Support Help**
- \*.canvaslms.com
## **Quizzes and Outcomes Domains** Quizzes and Outcomes URLs follow a similar pattern to Canvas URLs with the addition of the Amazon Web Services (AWS) region (IAD, PDX, YUL, DUB, FRA, SYD, SIN). Also, Quizzes has two application URLs instead of just one. For institutions unsure about which region to use for an account, please contact Canvas Support or a Customer Success Manager.
- kinesis.\*.amazonaws.com - \*.cloudfront.net - \*.learnosity.com - \*.quiz-api-<region>-prod.instructure.com - \*.quiz-lti-<region>-prod.instructure.com - \*.quiz-api-<region>-beta.instructure.com - \*.quiz-lti-<region>-beta.instructure.com - \*.outcomes-<region>-prod.instructure.com
## **Email Notification IP Addresses** SMTP allows any computer to send email claiming to be from any source address. Spammers and phishing often use this to forge email addresses, making it more difficult to trace a message back to its sender and easy for spammers to hide their identity in order to avoid responsibility; they even dupe users into disclosing private information in response to an email. ## **Verification Systems** Canvas uses SPF, which is an email validation system designed to prevent email SPAM and phishing by detecting and preventing email spoofing. SPF allows administrators to specify which hosts (IP addresses, computers) are allowed to send mail from a given domain by creating specific SPF records in the DNS. Mail exchangers then use the DNS to verify mail from a given domain is being sent by a sanctioned host. Canvas also uses DomainKeys Identified Mail (DKIM) to sign mail. DKIM associates our domain name to an email message, thereby allowing Canvas to claim responsibility for the message (sign the message). The digital signature is validated by recipient. Responsibility is claimed by a signer (instructure.com), independently of the message's actual authors or recipients, by adding a DKIM-Signature: field to the message's header. The verifier recovers the signer's public key using the DNS, and then verifies that the signature matches the actual message's content. If customers cannot receive email notifications from Canvas, emails are typically being sent to the Spam folder. To correct this behavior, update spam settings to allow emails from instructure.com. ## **Email IP Addresses** If needed, institutions can allow all static Canvas Email IP addresses. When Email IP addresses are allowlisted, the entire list of IP addresses should be allowlisted. The variety of IP addresses ensure a specific IP is not overloaded and activity can be distributed across various data centers as needed. This recommendation also applies to adding international IP addresses as well. **Note:** The IP list may be updated at any time. **Customers hosted in Canada** 99.79.19.152 52.60.179.121 23.249.209.14 23.249.209.15 **Customers hosted in Ireland (DUB) or Frankfurt (FRA)** 54.240.89.126 54.240.89.127 54.240.89.128 54.240.89.129 54.240.89.130 **Customers hosted in Singapore (SIN) or Sydney (SYD)** 69.169.235.184 69.169.235.186 69.169.235.185 **Customers hosted in Virginia (IAD) or Oregon (PDX)** 23.249.221.108 23.249.221.109 23.249.221.110 23.249.221.111 23.249.221.112 23.249.221.113 23.249.221.114 23.249.221.115 23.249.221.116 23.249.221.117 23.249.221.118 23.249.221.119 23.249.221.120 23.249.221.121 23.249.221.122 23.249.221.123 23.249.221.124 23.249.221.125 23.249.221.126 23.249.221.127 54.240.127.159 54.240.127.60 54.240.127.61 54.240.127.62 54.240.127.63 54.240.127.64 54.240.127.65 54.240.127.66 54.240.127.67 54.240.127.68 54.240.14.1 54.240.14.100 54.240.14.102 54.240.14.103 54.240.14.105 54.240.14.107 54.240.14.128 54.240.14.130 54.240.14.131 54.240.14.139 54.240.14.154 54.240.14.188 54.240.14.198 54.240.14.199 54.240.14.2 54.240.38.184 54.240.38.185 54.240.38.186 54.240.38.187 54.240.38.188 23.249.221.12/32 23.249.221.202/32 54.240.68.117/32 54.240.68.118/32 54.240.68.119/32 54.240.68.120/32 54.240.68.121/32 54.240.68.123/32 54.240.76.81/32 54.240.76.83/32 54.240.76.85/32 54.240.76.87/32 54.240.76.88/32 54.240.76.92/32 54.240.76.96/32 [**Full list pulled via SPF on (12-10-24)**](https://dmarcian.com/spf-survey/?domain=canva.com) 103.151.192.0/23 108.177.8.0/21 108.177.96.0/19 108.179.144.0/20 130.211.0.0/22 139.180.17.0/24 141.193.184.128/25 141.193.184.32/27 141.193.184.64/26 141.193.185.128/25 141.193.185.32/27 141.193.185.64/26 143.244.80.0/20 148.105.8.0/21 158.247.16.0/20 159.112.242.162/32 159.135.228.10/32 166.78.68.221/32 167.89.46.159/32 167.89.64.9/32 167.89.65.0/32 167.89.65.100/32 167.89.65.53/32 167.89.74.233/32 167.89.75.126/32 167.89.75.136/32 167.89.75.164/32 167.89.75.33/32 172.217.0.0/19 172.217.128.0/19 172.217.160.0/20 172.217.192.0/19 172.217.32.0/20 172.253.112.0/20 172.253.56.0/21 173.194.0.0/16 18.208.124.128/25 185.12.80.0/22 188.172.128.0/20 192.161.144.0/20 192.237.159.42/32 192.237.159.43/32 198.2.128.0/18 198.2.128.0/24 198.2.132.0/22 198.2.136.0/23 198.2.145.0/24 198.2.177.0/24 198.2.178.0/23 198.2.180.0/24 198.2.186.0/23 199.127.232.0/22 199.255.192.0/22 205.201.128.0/20 205.201.131.128/25 205.201.134.128/25 205.201.136.0/23 205.201.139.0/24 206.55.144.0/20 209.85.128.0/17 216.139.64.0/19 216.198.0.0/18 216.221.160.0/19 216.239.32.0/19 216.58.192.0/19 23.249.208.0/20 23.251.224.0/19 23.251.237.159/32 23.251.237.160/29 23.251.237.168/30 23.253.182.103/32 23.253.183.145/32 23.253.183.146/32 23.253.183.147/32 23.253.183.148/32 23.253.183.150/32 3.210.190.0/24 3.93.157.0/24 35.190.247.0/24 35.191.0.0/16 54.174.52.0/24 54.174.57.0/24 54.174.59.0/24 54.174.60.0/23 54.174.63.0/24 54.240.0.0/18 54.240.64.0/19 54.240.96.0/19 64.233.160.0/19 66.102.0.0/20 66.249.80.0/20 69.169.224.0/20 72.14.192.0/18 74.125.0.0/16 76.223.128.0/19 76.223.176.0/20 ## **LDAP** Most LDAP servers are not publicly available and are protected by firewalls. Canvas admins can create an allowed list of firewall exceptions to connect to their LDAP server. Canvas designates a set of servers and their associated static IP addresses to simplify these firewall exception rules. For institutions unsure about which region to use for an account, please contact Canvas Support or a Customer Success Manager. **Note:** The IP list may be updated at any time. **CANADA** 52.60.71.96 prod ca-central-1a 52.60.54.125 prod ca-central-1b 52.60.193.95 nonprod ca-central-1a 52.60.42.222 nonprod ca-central-1b **FRANKFURT** 52.29.85.26 = nat1 (prod) eu-central-1a 52.29.84.246 = nat2 (prod) eu-central-1b 18.185.69.114 = nat3 (prod) eu-central-1c 52.29.95.79 = nat1 (nonprod) eu-central-1a 52.29.119.13 = nat2 (nonprod) eu-central-1b 18.184.239.128 = nat3 (nonprod) eu-central-1c **IRELAND** 46.51.199.181 = nat1-a (prod) eu-west-1a 46.51.199.184 = nat1-b (prod) eu-west-1b 46.51.199.187 = nat1-c (prod) eu-west-1c 54.229.62.101 = nat1 (nonprod) eu-west-1a 54.229.61.11 = nat2 (nonprod) eu-west-1b 54.229.62.136 = nat3 (nonprod) eu-west-1c **OREGON** 50.112.155.19 = nat1 (prod) us-west-2a 50.112.155.17 = nat2 (prod) us-west-2b 50.112.138.16 = nat3 (prod) us-west-2c 34.212.202.226 = nat1 (nonprod) us-west-2a 54.70.178.34 = nat2 (nonprod) us-west-2b 34.210.5.133 = nat3 (nonprod) us-west-2c **SINGAPORE** 54.255.173.119 = nat1 (prod) ap-southeast-1a 54.255.173.249 = nat2 (prod) ap-southeast-1b 52.74.23.74 = nat3 (prod) ap-southeast-1c 54.255.177.29 = nat1 (nonprod) ap-southeast-1a 52.77.73.203 = nat2 (nonprod) ap-southeast-1b 54.179.60.151 = nat3 (nonprod) ap-southeast-1c **SYDNEY** 54.79.101.198 = nat1 (prod) ap-southeast-2a 54.79.104.239 = nat2 (prod) ap-southeast-2b 54.206.13.66 = nat3 (prod) ap-southeast-2c 54.79.80.35 = nat1 (nonprod) ap-southeast-2a 13.55.54.243 = nat2 (nonprod) ap-southeast-2b 54.66.224.5 = nat3 (nonprod) ap-southeast-2c **VIRGINIA** 184.72.117.210 = nat1-b (canvasprod) us-east-1b 107.23.48.136 = nat1-c (canvasprod) us-east-1c 107.23.49.116 = nat1-e (canvasprod) us-east-1e 107.21.12.41 = nat1 (test/beta) us-east-1 54.208.19.142 = nat1 (futureprod) us-east-1b 54.208.31.242 = nat2 (futureprod) us-east-1c 54.208.28.84 = nat3 (futureprod) us-east-1e 54.208.2.214 = nat1 (futurenonprod) us-east-1b 54.208.5.44 = nat2 (futurenonprod) us-east-1c 54.208.27.95 = nat3 (futurenonprod) us-east-1e **SHARED SFTP (PDX)** 52.41.151.176 us-west-2a 35.164.144.191 us-west-2b 54.71.241.59 us-west-2c