Skip to main content

IP addresses and domains

Simplesat's IP addresses and domains, and when your firewall, proxy or geo-filter needs to allow them.

Simplesat connects to your systems from five IP addresses, and your team's browsers reach it on simplesat.io domains. Unless something on your side blocks traffic from Simplesat, you can skip the addresses.

Simplesat's IP addresses

  • 54.216.242.254

  • 18.202.111.236

  • 99.81.99.204

  • 54.216.226.109

  • 54.217.132.208

Allow all five, even if your logs only show one. Some are Simplesat's servers and some run its integrations, so which address you see depends on what's connecting.

Heads up: These addresses are all on Amazon Web Services in Ireland. If your geo-filter blocks traffic from there, add them as exceptions.

When you need to allowlist them

Setup

Who connects to whom

Allowlist the addresses?

A self-hosted or on-premise helpdesk

Simplesat connects to your system

✅ If your firewall filters incoming traffic

Webhooks and Send data to API endpoint

Simplesat connects to your endpoint

✅ If your firewall filters incoming traffic

A cloud helpdesk or other tool connected through an integration

Simplesat's integration connects to your tool

✅ If your tool restricts access by IP address

Embedded surveys and widgets on your website

Your visitors' browsers connect to Simplesat

❌ Nothing to allowlist

The Simplesat API

Your system connects to Simplesat

❌ Nothing to allowlist

For the addresses and domains Simplesat sends survey emails from, see Email domains & deliverability.

Simplesat's domains

If your network filters web traffic by domain, allow *.simplesat.io, or each of these:

Domain

What it's for

app.simplesat.io

The Simplesat app

api.simplesat.io

The app's data, and the Simplesat API

survey.simplesat.io

Survey pages your customers open

cdn.simplesat.io

Images, files and the web embed script

auth.simplesat.io

Signing in with Google

integration.simplesat.io

Sign-in windows when you connect an integration

Troubleshooting

My integration returns an error, and I think your IP addresses are being blocked

A blocked connection usually times out, or ends with a message from your firewall rather than from the tool. If that's what you see, check that all five addresses are allowed.

These errors mean the two systems reached each other and something else went wrong:

  • A 400 with a validation message

  • A 401 or 403 saying the token or credentials are invalid

  • A 404

  • A message in Simplesat that says undefined

If a colleague on your network can use the integration, the addresses aren't being blocked. The same goes if your endpoint is sending back a response.

Once you've ruled out a block, contact us with the exact error and the name of the integration.

My endpoint isn't receiving data from Send data to API endpoint

First, check that your firewall allows all five addresses. If it does, your endpoint may actually be receiving the data and rejecting it, which doesn't always show up on your side. Contact us with the time the data should have arrived, and we'll check the integration's run history for what Simplesat sent and what your endpoint answered.

Some of my team can't load Simplesat at work

A web filter or proxy on your network may be blocking one of Simplesat's domains. Allow *.simplesat.io, or each of the domains listed above.

FAQ

Where is Simplesat hosted?

On Amazon Web Services in Ireland. Security & privacy covers where your data is stored and how it's protected.

Who has to allowlist the addresses: us, Simplesat or the other tool?

Whoever runs the system that receives the connection. For your own firewall or self-hosted helpdesk, that's your IT team. For a cloud tool that restricts access by IP address, it's an admin in that tool. There's nothing to allowlist on Simplesat's side.

Can we restrict access to Simplesat to our own IP addresses?

Simplesat has no IP restriction setting. If your team signs in with single sign-on, though, your identity provider's access rules apply to every sign-in. Single sign-on is covered in Login methods and single sign-on.

Did this answer your question?