The following IP addresses are considered as Giosg public addresses.
| Host | IP | Purpose |
|---|---|---|
| service.giosg.com | 178.63.128.65 178.63.179.193 178.63.219.113 178.63.227.217 |
HTTP(s) traffic |
| api.giosg.com | 178.63.128.65 178.63.179.193 178.63.219.113 178.63.227.217 |
HTTP(s) traffic |
| messagerouter.giosg.com | 178.63.128.66 178.63.179.194 178.63.219.114 178.63.227.218 |
HTTP(s) / Websocket traffic |
| out.giosg.com | 178.63.128.65 | Connections from giosg to out |
IP addresses of all domains mentioned above will be dynamically picked from the following subnets and may change without preliminary notice in bounds of the following subnets:
| Subnet |
|---|
| 178.63.128.64/29 |
| 178.63.179.192/29 |
| 178.63.219.112/29 |
| 178.63.227.216/29 |
If your organisation is using outbound IP filtering, please add all the IP addresses and subnets listed above to the outbound firewall’s allowed IP list in order to use Giosg services.
If your organisation has set up a service accepting HTTP queries from Giosg in automated manner (e.g. webhooks), please allow also inbound traffic coming from out.giosg.com domain’s IP address(es) to that service.
In case your firewall/IPS supports filtering based on domains rather than IP addresses, please allow outbound traffic to the domains mentioned above and inbound traffic from out.giosg.com for the services requiring that.
For more information and details, visit our giosg for developers - site.