Please find below the list of URLs that your IT team should allow to ensure full functionality of our SaaS platform.

In some cases, we have included wildcard entries (e.g., *.example.com). This is done to account for dynamic subdomains or evolving infrastructure (such as live support chat, static styling, or external microservices) that may use varying hostnames under a common domain. The use of wildcards is a standard and safe practice in SaaS environments, ensuring that your users can consistently access all necessary services without interruption.

Each URL in the list is accompanied by a brief justification to explain its purpose and necessity. If you have any questions or need further clarification, please don’t hesitate to reach out via the chat or emailing to support@akur8.com.

We have observed that certain clients may encounter issues accessing our platform due to browser adblockers. If you experience any difficulties, please ensure that your adblocker is disabled for our site.

Additionally, if you have already confirmed that the necessary URLs are whitelisted and are still experiencing problems, do not hesitate to contact us. We’re here to help and will be happy to assist you further.

Intercom is Akur8’s chosen provider for live chat support and user engagement. It is a widely trusted and industry-recognized platform used by thousands of organizations, including those with stringent security and compliance requirements. Intercom maintains rigorous security practices and holds various certifications (such as SOC 2 Type II and ISO 27001), ensuring that data protection and service integrity meet high enterprise standards.

In our configuration, Intercom assets are typically served from a small, well-defined set of domains. While it's technically possible to enumerate each route individually, we recommend using a wildcard (*) in the route definitions (e.g., *.intercom.io, static.intercomassets.eu) for operational simplicity and to ensure compatibility with all required subresources now and in the future.

This approach aligns with Intercom’s documentation and best practices, and it avoids potential issues caused by incomplete route lists due to updates or expansion of services on their end. The two domains mentioned above are verified and sufficient for Akur8's use of Intercom, covering scripts, widget rendering, and content delivery.

We encourage reviewing Intercom’s security documentation and this technical reference page for more detailed information on domain usage and safe integration practices.

About (2.), from a security standpoint, cdn.auth0.com is an official subdomain owned and operated by Auth0 (now part of Okta), a well-established provider of secure identity solutions. This domain serves static, non-executable image content and is isolated from Auth0’s application logic, minimizing risk. The proxying via wp.com is a read-only operation and does not introduce executable code into your application environment.

About (5.), to ensure proper functionality of our geo mapping features, please make sure the following URLs are whitelisted. These resources are used by Plotly to render interactive maps and are hosted by Carto, a trusted map service that helps display geographic information, like streets, cities, and labels, on interactive maps. It provides the background maps (called basemaps) that we use in our dashboards and visualizations.

We don’t recommend whitelisting each of the following URLs, as subject to change; they just serve as an example so you can get an idea of what is being loaded.

All of these resources are essential to visualize an accurate geographic map in AKUR8. They are served by Carto’s official content delivery infrastructure and are safe to whitelist within your firewall or proxy settings.