Network requirements for your app
The domains, IP addresses and ports to allowlist so a company network can use your published app, and which ones depend on the features your app uses.
If people will use your app from a company network, its IT department may ask which domains and ports to allow through the firewall or web filter. This page is the list for a published Floot app. Send it to them as it is.
Always needed
Everything uses HTTPS (or secure WebSockets) on TCP port 443, with TLS 1.2 or newer. Plain HTTP on port 80 only redirects to HTTPS.
| Host | What it is for |
|---|---|
Your app's own address: <name>.floot.app and any custom domain | The app itself: its pages, its backend (/_api), its scripts and styles (/_assets), its public files (/_cdn) and its visitor analytics (/_floott). Allow both the floot.app address and the custom domain: when a custom domain is set, the floot.app address redirects to it. |
floot.com | The visitor analytics script (floot.com/t.js) and, for an app without its own icon, the default icon. Not needed if you turn visitor analytics off. |
floot-client-app-storage.s3.us-east-1.amazonaws.com | File uploads, and opening private files. Public files load from your app's own address instead. |
Your app's own address is served from these fixed IPv4 addresses, for a firewall that filters by IP: 3.173.23.154, 3.173.22.154, 3.173.21.154. Floot does not publish an IPv6 address for apps. The other hosts on this page run on AWS, Google, Microsoft, Cloudflare or Stripe addresses that change, so allow those by name.
Needed only for some features
| Host | Needed when your app uses |
|---|---|
realtime.floot.com (secure WebSocket, wss://) | Live updates (realtime) |
floot.com and accounts.google.com | Sign in with Google through Floot. With your own Google client, only accounts.google.com |
oauth.floot.com and login.microsoftonline.com | Sign in with Microsoft, and letting users connect their Google or Microsoft account |
floot.com and challenges.cloudflare.com, plus the Google, GitHub or Microsoft sign-in page a person uses | Publish privately: visitors sign in to Floot before the app opens |
| Stripe's domains: see Stripe's list | Payments, subscriptions or a billing portal |
*.awswaf.com | The setting that asks visitors from cloud servers to prove they are human. A company web proxy that runs in the cloud can be what triggers the check |
assets.floot.app | Images and icons in older projects whose addresses still point there |
fonts.googleapis.com and fonts.gstatic.com | Rarely: Google Fonts are normally copied into your app when you publish. These are needed only if that copy failed, or if your app's code loads fonts some other way |
The browser's own push service (for example fcm.googleapis.com for Chrome, *.notify.windows.com for Edge) | Web push notifications |
Any outside service your app's own code calls from the browser (a map, a video host, an API) needs its own entry. Ask your assistant to list the outside services your app loads in the browser.
Mobile apps
The iOS and Android apps Floot builds carry their pages inside the app and call your app's <name>.floot.app address, even when the app has a custom domain. They do not load floot.com/t.js. Uploads, live updates, sign-in and payments use the same hosts as above.
Email your app sends
Your app's email is sent by Amazon SES from your own verified sending domain, signed with DKIM and covered by SPF (include:amazonses.com). A company mail filter that allowlists senders should allow your sending domain. Until you verify a domain, your app's email goes only to you, from emailservice.floot.com — see Email.
Your backend calling the company's systems
This page is about people reaching your app. If your app's backend must call a system inside the company's network, its calls come from changing AWS addresses. To send them from a short fixed list of addresses the company can allow, use Fixed outbound IP.