Note: General firewall information for all OpenSesame Plus publishers can be found here.

If you or your team members will be creating Simon courses from restrictive or high-security IT environments—such as those found in banking, healthcare, or government settings—it might be necessary to allow content delivery from our dedicated Simon servers.

If you’re unsure whether allowing Simon subdomains is needed, we recommend proceeding with creating courses to verify that your network is already configured to allow Simon content. If course creation does not work, your IT team may need to assist.

If you know that your IT environment has security restrictions, see the following breakdown of content delivery addresses for Simon.

Note: These addresses represent servers whose primary function is to deliver content upon receiving specific requests from Simon. They may not display a viewable website when accessed directly by a browser.

Wildcard domain

If your IT team is comfortable with allowing “ * ” wildcard characters, all of the following Simon subdomains can be covered by a single entry:

https://*.heysimon.com

Subdomains for taking Simon courses

If allowing a wildcard character is not an option on your network, please ask your IT team to allow these subdomains for everyone who will be creating or taking Simon courses:

https://assets.heysimon.com
https://course.heysimon.com
https://launch.heysimon.com

Subdomains for creating Simon courses

In addition, any team members who create courses with Simon will also need access to these subdomains:

https://ams.heysimon.com
https://asset-api.heysimon.com
https://auth.heysimon.com
https://authx.heysimon.com
https://authoring.heysimon.com
https://course-api.heysimon.com
https://manager.heysimon.com
https://translation.heysimon.com

If you have further questions, our Support team is here to help at support@heysimon.com.