Allowing Opensense traffic through your network proxy or firewall

Overview

If your organization uses a secure web gateway or proxy, such as Forcepoint, Zscaler, or a similar tool, some Opensense services may be blocked or inspected. This can stop the Outlook add-in from loading, or cause errors when users try to sign in. Allowing specific Opensense domains through your network lets the add-in load the scripts it needs, and communicate with our platform reliably.

Some organizations also restrict outbound IP ranges. If that applies to your environment, see Opensense IP addresses for whitelisting.

When you might need this

Whitelisting is recommended if users have issues such as:

• The Opensense Outlook add-in doesn’t load.
• Error messages, such as 403 responses, during login or script initialization.
• The Opensense web dashboard works on external networks, but not on the corporate network.
• Certificate verification errors caused by SSL inspection tools.

Only inside your network?

If these symptoms occur inside your network but not outside it, your proxy or firewall may be intercepting Opensense traffic.

Domains that must be allowed

Allow these domains through your proxy or firewall, and exempt them from SSL inspection.

Core domains

Must be fully allowed for the Outlook add-in to work: www.sendergen.com, outlook.opensense.com, and opensense-outlook.s3.amazonaws.com.

Wildcard domains

Cover current and future subdomains: *.sendergen.com and *.opensense.com.

Adding both the explicit domains and the wildcard entries gives complete coverage, and reduces future maintenance. To copy all five:

www.sendergen.com
outlook.opensense.com
opensense-outlook.s3.amazonaws.com
*.sendergen.com
*.opensense.com

Why this is required

The Opensense Outlook add-in loads web resources, and communicates with our backend services. Proxies that block or intercept this traffic can:

• Interrupt authentication.
• Block critical scripts from loading.
• Replace SSL certificates, which causes validation failures.
• Return 403 responses before the traffic reaches Opensense.

Exempting the domains listed above prevents these issues, so the add-in can work normally.

After you update your settings

Once your proxy or firewall is updated:

1. Restart Outlook.
2. Open the Opensense add-in.
3. Sign in again, if prompted.
4. Confirm that all features load without errors.
5. Go to the Opensense dashboard (app.opensense.com) to check that access works consistently on the internal network.

If everything loads correctly, the configuration is complete.

Need more help?

If issues continue after these changes, your team may use layered security tools that also need updates. We can help by reviewing network logs, or by providing connection tests tailored to your environment. Contact help@opensense.com.

What’s next

• Opensense IP addresses for whitelisting
• Troubleshooting the Outlook Add-in