Firewalls and filters can block access to domains used by Atomi and the 3rd party services it depends on. This article is written to assist School Administrators and IT professionals to correctly configure their network firewall. We've included an extensive list of domains that school users will require access to in order to use Atomi.
Please note: In order to future-proof your setup for the addition of new Atomi services we highly recommend you whitelist all subdomains of getatomi.com in addition to the domains listed below. This can often be done by adding the record *.getatomi.com to your whitelist.
Your school's users will need to be able to access all the following domains in order to use Atomi.
getatomi.com
learn.getatomi.com
nucleus.getatomi.com
analytics.getatomi.com
thorium.getatomi.com
segment-cdn.getatomi.com
segment-api.getatomi.com
cdn.segment.com
api.segment.io
wistia.com
embed-fastly.wistia.com
embedwistia-a.akamaihd.net
embedwistia-b.akamaihd.net
embed-ssl.wistia.com
fast.wistia.com
fast.wistia.net
pipedream.wistia.com
distillery.wistia.com
api-iam.intercom.io
intercom.io
intercom.com
intercomcdn.com
js.intercomcdn.com
15uprpztc0-dsn.algolia.net
cb-downloads-prod.s3.amazonaws.com
browser.sentry-cdn.com
m.stripe.com
js.stripe.com
q.stripe.com
To avoid issues we recommend adding the following additional wildcards:
*@mg.getatomi.com
*.wistia.com
*.sentry.io
*.sentry-cdn.com
*.segment.com
*.algolia.net
*.intercom.io
*.intercomcdn.com
*.intercom.com
*.stripe.com