ioTORQ EMIS

This document presents the domain names and IP that should be whitelisted by a client in their network to allow telemetry data to be exported from the site and for users to access the application.

For access to the application by tablets, phones and desktop computers, the following wildcard domains should be whitelisted to allow HTTP traffic on port 80 and 443:

<code>*.ingest.sentry.io</code> (used for telemetry and error reporting)

- <code>*.iotorq.com</code>
- <code>*.ingest.sentry.io</code> (used for telemetry and error reporting)

If it's not possible to use wildcard domains, then the following domains should be whitelisted on port 80 and 443:

Client customer domain: &lt;client&gt;.iotorq.com (ex: panevo.iotorq.com)

- Client customer domain: &lt;client&gt;.iotorq.com (ex: panevo.iotorq.com)
- activity.iotorq.com
- 478411.ingest.sentry.io

Note that these domains don't have a static IP and their IP can change over time.

The application uses Intercom for in-app messaging and support. The following domains must be whitelisted on <b>port 443 (HTTPS)</b> for the messenger widget to function properly:

<code>*.intercom-attachments-1.com</code>

<code>*.intercom-attachments-2.com</code>

<code>*.intercom-attachments-3.com</code>

<code>*.intercom-attachments-4.com</code>

<code>*.intercom-attachments-5.com</code>

<code>*.intercom-attachments-6.com</code>

<code>*.intercom-attachments-7.com</code>

<code>*.intercom-attachments-8.com</code>

<code>*.intercom-attachments-9.com</code>

<code>*.au.intercom-attachments.com</code>

- <code>*.intercom.io</code>
- <code>*.intercom-messenger.com</code>
- <code>*.intercomcdn.com</code>
- <code>*.intercomcdn.eu</code>
- <code>*.intercomassets.com</code>
- <code>*.intercomassets.eu</code>
- <code>*.intercomusercontent.com</code>
- <code>*.intercom-attachments-1.com</code>
- <code>*.intercom-attachments-2.com</code>
- <code>*.intercom-attachments-3.com</code>
- <code>*.intercom-attachments-4.com</code>
- <code>*.intercom-attachments-5.com</code>
- <code>*.intercom-attachments-6.com</code>
- <code>*.intercom-attachments-7.com</code>
- <code>*.intercom-attachments-8.com</code>
- <code>*.intercom-attachments-9.com</code>
- <code>*.intercom-attachments.eu</code>
- <code>*.au.intercom-attachments.com</code>
- <code>intercom.help</code>
- <code>intercom-sheets.com</code>
- <code>www.intercom-reporting.com</code>

If wildcard domains are not supported, the following explicit domains must be whitelisted:

- <code>app.intercom.io</code>
- <code>widget.intercom.io</code>
- <code>via.intercom.io</code>

- <code>api.intercom.io</code>
- <code>api.eu.intercom.io</code>
- <code>api.au.intercom.io</code>
- <code>api-iam.intercom.io</code>
- <code>api-iam.eu.intercom.io</code>
- <code>api-iam.au.intercom.io</code>
- <code>api-ping.intercom.io</code>

<code>nexus-websocket-a.intercom.io</code>

<code>nexus-websocket-b.intercom.io</code>

<code>nexus-europe-websocket.intercom.io</code>

<code>nexus-australia-websocket.intercom.io</code>

<code>*.intercom-messenger.com</code> (real-time messaging - wildcard required)

- <code>nexus-websocket-a.intercom.io</code>
- <code>nexus-websocket-b.intercom.io</code>
- <code>nexus-europe-websocket.intercom.io</code>
- <code>nexus-australia-websocket.intercom.io</code>
- <code>*.intercom-messenger.com</code> (real-time messaging - wildcard required)

<code>messenger-apps.eu.intercom.io</code>

<code>messenger-apps.au.intercom.io</code>

- <code>messenger-apps.intercom.io</code>
- <code>messenger-apps.eu.intercom.io</code>
- <code>messenger-apps.au.intercom.io</code>

<code>static.au.intercomassets.com</code>

- <code>js.intercomcdn.com</code>
- <code>fonts.intercomcdn.com</code>
- <code>static.intercomassets.com</code>
- <code>static.intercomassets.eu</code>
- <code>static.au.intercomassets.com</code>

<code>downloads.au.intercomcdn.com</code>

- <code>downloads.intercomcdn.com</code>
- <code>downloads.intercomcdn.eu</code>
- <code>downloads.au.intercomcdn.com</code>

<code>uploads.intercomusercontent.com</code>

- <code>uploads.intercomcdn.com</code>
- <code>uploads.intercomcdn.eu</code>
- <code>uploads.au.intercomcdn.com</code>
- <code>uploads.eu.intercomcdn.com</code>
- <code>uploads.intercomusercontent.com</code>

<code>video-messages.intercomcdn.com</code>

- <code>gifs.intercomcdn.com</code>
- <code>video-messages.intercomcdn.com</code>

- <code>*.intercom-attachments-1.com</code>
- <code>*.intercom-attachments-2.com</code>
- <code>*.intercom-attachments-3.com</code>
- <code>*.intercom-attachments-4.com</code>
- <code>*.intercom-attachments-5.com</code>
- <code>*.intercom-attachments-6.com</code>
- <code>*.intercom-attachments-7.com</code>
- <code>*.intercom-attachments-8.com</code>
- <code>*.intercom-attachments-9.com</code>
- <code>*.intercom-attachments.eu</code>
- <code>*.au.intercom-attachments.com</code>

- <code>intercom.help</code>
- <code>intercom-sheets.com</code>
- <code>www.intercom-reporting.com</code>

Some Intercom domains use both HTTPS and WebSocket Secure (WSS) protocols over port 443. If your firewall requires explicit WebSocket protocol approval, ensure that WebSocket upgrade requests are allowed for the domains listed in the WebSocket Connections section above

Firewall Configuration

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

Firewall Configuration

Application Access

Intercom Messenger Widget

Option 1: Wildcard Domains (Recommended)

Option 2: Explicit Domains

Core Services

API Endpoints

WebSocket Connections

Messenger Apps

Static Assets & CDN

Downloads

Uploads

Media Content

File Attachments

Help & Reporting

WebSocket Protocol Note